Database Info

Cm13 Question D850

Can someone explain why no Cm13 for d850 but for every other carrier? Use to be ATT always gets updates first.

Link to download
https://www.androidfilehost.com/?a=show&w=files&flid=42910
Link to thread
http://forum.xda-developers.com/lg-g3/general/cm13-lg-g3-test-builds-t3245744

underscorenorm said:
Link to download
https://www.androidfilehost.com/?a=show&w=files&flid=42910
Link to thread
http://forum.xda-developers.com/lg-g3/general/cm13-lg-g3-test-builds-t3245744
Click to expand...
Click to collapse
is it reliable ?

I need the external SD card, and Marshmallow is kinda weird with formatting as internal right now, so I didn't use it long, -I didn't any improvements to battery life either, so I wouldn't say it's great right now, but there are a few ROMs out there based on cm13.
FawkiDied said:
is it reliable ?
Click to expand...
Click to collapse

It's not that difficult...
Update:
Have built and posted CM13 ROM for d850 with working GPS. See this thread.
It's not terribly difficult to build your own "unofficial" CM13 ROM image for the d850. I did it this morning (12/19). I was surprised that most everything works, more or less, except for GPS which is still dead as a doornail.
The only difficult part of building CM yourself is the initial setup of a build environment. After that, any time you want the latest-and-greatest you just sync the environment to the latest changes, which takes maybe a minute, and then start the build – which can take a couple/few hours. Best done last thing before you go to bed. Cyanogenmod has good instructions here: https://wiki.cyanogenmod.org/w/Build_for_d850. When you follow the instructions to build CM-12.1 just substitute CM-13.0.
A few hints:
Your version of java
The CM13 build will fail with anything other than Oracle Java 1.7.xxx. No, it will not build with 1.8. No, it will not build with 1.6. No, it will not build with open openjdk or icedtea anything. I had to uninstall Oracle Java 1.8 to prevent its being used by default even though I had manually specified to use Oracle Java 1.7.
The vendor blobs
The instructions will say at one point to extract the vendor proprietary blobs from your current version of CM13. Huh? Not too helpful there. Use the blobs that TheMuppets has pulled together on github. https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-13.0. Additional hint: It's a whole lot easier to download the zip than it is to set up a proper git environment to retrieve them. Using git is like taking a howitzer out to hunt rabbits, in this case.
Installing
Copy the newly created .zip image from $OUT to your phone storage by your favorite means. Also copy over a version of gapps for CM13 (Android 6). First, manually wipe system. Then flash your new CM13 image and a CM13 compatible version of gapps at the same time. If you don't then the upgrade from 12.1 to 13 will fail when CM13 starts. Apparently Google Play Store is launched, and if it is not CM13 (Android 6) compatible it will repeatedly abort during the upgrade process. You can find several configurations of gapps for CM13 here: http://opengapps.org/. The "mini" for Android 6 works great for me. If you do this then it seems possible to do the upgrade "dirty"; that is, wiping cache and delvik but not apps and data. That saves a whole lot of time not having to restore that stuff. (Yeah, I can hear the incoming rounds now.)
Rebuilding after first build
I didn't use ccache at first, hoping to avoid additional complexity the first few builds. However, it works great, reducing rebuild time to just over ten minutes on subsequent builds after its first use. Use ccache.
Also, I created a super-simple shell script to initiate a rebuild. It's run from android/system/
Code:
#!/bin/bash
# sync with repository and initiate rebuild using ccache
# see https://wiki.cyanogenmod.org/w/Build_for_d850
repo sync
source build/envsetup.sh
breakfast d850
export USE_CCACHE=1
prebuilts/misc/linux-x86/ccache/ccache -M 50G
croot
brunch d850
echo "end of rebuild script"
Good luck, and let's hope a maintainer for cm13 d850 shows up soon!

Teach me to build the lineageos 17.1 for oneplus 7 pro,i will pay you dollars

Dears,
I need to download the lineageos 17.1 source code and build the system then install it into the device Oneplus 7pro to boot success.
I meet some issues that make me can not complete it. If anyone can help me to finish the work, i will pay you dollars.
The system : lineageos 17.1
the device: oneplus 7pro
Thanks very much!

Its really simple actually. What you need is a PC running Ubuntu, Debian Linux or derivate. You will need at least 200-300GB free disk space and you should have 8GB of RAM and a decent CPU.
If you have all of the above you simply follow the build instructions for guacamole (OnePlus 7 Pro) on this link.
https://lineageos.github.io/lineage_wiki/devices/guacamole/build
You will need basic Linux knowledge to have some understanding of what all the commands does on the system.
When done, simply copy the zip to the device, make sure you have correct version of TWRP and follow the installation guide for A/B partition installation, also it's required to do factory reset of device when moving from OxygenOS to LineageOS.
Is this for some school project or something? Else you can find daily builds for guacamole made by my buildbot here (yesterday's build apparently failed for guacamole) - > https://lineageos.wickenberg.nu

pitrus- said:
Its really simple actually. What you need is a PC running Ubuntu, Debian Linux or derivate. You will need at least 200-300GB free disk space and you should have 8GB of RAM and a decent CPU.
If you have all of the above you simply follow the build instructions for guacamole (OnePlus 7 Pro) on this link.
https://lineageos.github.io/lineage_wiki/devices/guacamole/build
You will need basic Linux knowledge to have some understanding of what all the commands does on the system.
When done, simply copy the zip to the device, make sure you have correct version of TWRP and follow the installation guide for A/B partition installation, also it's required to do factory reset of device when moving from OxygenOS to LineageOS.
Is this for some school project or something? Else you can find daily builds for guacamole made by my buildbot here (yesterday's build apparently failed for guacamole) - > https://lineageos.wickenberg
Click to expand...
Click to collapse
You're information is wrong. First off all 8gb ram pc is nowhere near enough. You need at least 16gb with at least a 4gb swapfile to build Android 10. If you don't meet just these requirements your pc will just freeze and shut down when you build. And you don't NEED a pc you can build roms right on your phone with a Google cloud vm. I build with both pc and phone all the time. And according to his op his already started a build but has ran into some build errors. I don't know why people respond to things without fully reading them first.
---------- Post added at 07:28 PM ---------- Previous post was at 07:23 PM ----------
suking89 said:
Dears,
I need to download the lineageos 17.1 source code and build the system then install it into the device Oneplus 7pro to boot success.
I meet some issues that make me can not complete it. If anyone can help me to finish the work, i will pay you dollars.
The system : lineageos 17.1
the device: oneplus 7pro
Thanks very much!
Click to expand...
Click to collapse
{Mod edit}

I really appreciate this other rude person who slams down on us sleep deprevated parents that are just trying to give some advice in the few minutes we have between the rounds of parenting. [emoji12][emoji1787]
Jokes aside, sorry for not reading your entire post, I wasn't 100% attentive at the moment, business as usual with human puppys around [emoji28]
Any rudeness aside, I thing you should really listen to Blackcrane as he can probably teach you a lot about compiling LineageOS 10. One thing I do know is that 48GB and no swap is enough to build both LOS16 and LOS17 at the same time, it never hurts with more RAM. [emoji4]

[ROM] [Unofficial] [Stable] GrapheneOS 10 Pre-Rooted

**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
GrapheneOS is an open source privacy and security focused mobile OS with Android app compatibility. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. Currently it is based on AOSP.
Link: (Mod Edit: Link removed)
Important information:
1. This ROM does NOT include Gapps or Google Play Service and hasn't Signature Spoofing Support. If you rely on the mentioned things this Rom isn't for you.
2. I take the official releases, modify the install script and include a pre-patched Magisk boot image. I'm not in contact with the GrapheneOS dev which is the reason why i mark this ROM as Unofficial.
3. Due of point two: Please don't ask questions on the official channels as reddit. Leave comments etc here on this thread.
4. You need a unlocked bootloader to flash this rom and must have adb+fastboot installed on your computer. If this is not the case download it from here: https://developer.android.com/studio/releases/platform-tools
I plan to make unofficial releases when new official builds are available.
Features:
AOSP 10
Built-in Firewall
Built-in local backup function (it's not working on all Apps; some doesn't support it)
Improved MAC Randomization
Hardened Kernel
Expanded Permissions (sensors)
Force calls to 4G only
Bugs
- Receiving text over verizon sim doesn't work reliable. Thx @wolfu11 for reporting.
Download: (Mod Edit: Link removed)
Installation:
Notice 1: The First-time installation will wipe your data. Backup first (i recommend this too when you follow the update instructions to be safe)
Notice 2: I recommend to have the newest stock firmware before the First-time installation
First-time installation:
1. Download the zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all_first_install.bat for Windows or flash-all_first_install.sh for Linux
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Install the Magisk Manager App
10. Be happy with a rooted GrapheneOS
Update:
Notice: I assume that fastboot+adb is still installed on your computer.
1. Download the newest zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all.bat for Windows or flash-all.sh for Linux
If your computer asks you to overwrite the current files in the plattform-tools folder, confirm it.
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Start the system once. This need a few more time than the first installation cause the data partition remains. Be patient.
6. Install the Magisk Manager App
7. Be happy with a rooted GrapheneOS
Sources:
https://github.com/GrapheneOS
https://grapheneos.org/releases
https://github.com/GrapheneOS/kernel_google_coral
https://github.com/GrapheneOS/device_google_coral-kernel
All Credits go to:
- The GrapheneOS team
- wolfu11 for reporting the verizon bug and testing the windows scripts
- and topjohnwu for his amazing Magisk
Created: 09.08.2020
Based on: Android 10
Updated: 21.08.2020
Current Version: 2020.08.07.01

Changelog from 09.08.2020
New Release: 2020.08.03.22
SHA3-512 Hash for Complete zip:
Code:
773c67b8571927c6f884a98ee67a10f96c3a759e34f925f7a8aaab7c19a4ca6b1ff53bb6dc500b4fe7c306b73853189a1c559889df6d9b4f2e8a90258d3d26c9
SHA3-512 Hash for Unpatched boot.img:
Code:
9b584f6941d37f60a7ed17ec4108b7bf484c3cbf1b63f2be6af1e59f452ed1d06e1b64704785d6ca3b38a3c09c8f29657f88c757bda993df509ef001d9842f00
Changes:
full 2020-08-01 security patch level
full 2020-08-05 security patch level
rebased onto QQ3A.200805.001 release
fix secondary stack hardening when a non-page-size multiple stack size is specified
fix picking up previous build date when doing incremental builds
Vanadium: update Chromium base to 84.0.4147.89
Vanadium: update Chromium base to 84.0.4147.105
Vanadium: update Chromium base to 84.0.4147.111
Vanadium: remove Chromium logo in chrome://version
kernel (Pixel 4, Pixel 4 XL): read-only data expansion

Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. I patched the boot.img which come with GrapheneOS in the zip with Magisk and then replaced the original GrapheneOS boot.img in the zip with the patched version.

Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.

dhacke said:
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. It isn't needed anymore to flash Magisk separately from the zip. I replaced the stock boot.img in the zip with the pre-patched one.
Click to expand...
Click to collapse
Just a heads up - you really aren't meant to pre-patch a boot image for Coral/Flame, as you are only meant to patch the boot image from your own individual device, as per the man topjohnwu himself
See: https://twitter.com/topjohnwu/status/1272136975022084097?s=19

Can you supply the unpatched boot img?
Thank you

wolfu11 said:
Can you supply the unpatched boot img?
Thank you
Click to expand...
Click to collapse
Done. Look here: (Mod Edit: Link removed)
I added an SHA3-512 Hash for file checking,too (see changelog from 11.08.2020).

Changelog from 15.08.2020
New Release: 2020.08.07.01
SHA3-512 Hash for Complete zip:
Code:
f3a2b088e0ec503296d5a2527a3766951cb2a3ccd1955ced14d304222e76ed3f341dd9d84b6e186a534eddac335065b756c1fdc89d0f1db3985314424e7f9eea
SHA3-512 Hash for unpatched boot image:
Code:
11abb901511ce8e39911bc951be4b1a349158c5d8389e74766942159c0f83aa9730ed39d8c8ae6c3cc66be559e3c165b5d4f35e0962d20a7be0b1532673a0287
Changes:
SELinux policy: fix executing apk libraries as executables for third party applications
Installation Notices:
From 2020.08.03.22 => No wipe needed. Just take the update scripts and let the right one running (see OP).
From Stock Rom => Use the install_first scripts. Be aware: This will wipe your data
Apart from that i recommend to make a backup first always (to be safe).

Wireguard Kernel integration
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?

[email protected] said:
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
Click to expand...
Click to collapse
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke

dhacke said:
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
Click to expand...
Click to collapse
Just need to add this to local_manifest for WG support
If unfamiliar with local_manifest, it's located in /.repo/local_manifests/ - it'll be the only file in that dir, often it's called room service.xml but it could be something like graphene_manifest.xml. Either way, it'll be the only file there and it'll be an XML - add those lines above to it and sync and you should have WireGuard support.
<remote name="zx2c4" fetch=https://git.zx2c4.com/>
<project remote="zx2c4" name="android_kernel_wireguard" path="kernel/wireguard" revision="master" sync-s="true" />

dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............

wolfu11 said:
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
Click to expand...
Click to collapse
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.

dhacke said:
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
Click to expand...
Click to collapse
I will try it when I get home today thank you

wolfu11 said:
I will try it when I get home today thank you
Click to expand...
Click to collapse
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.

wolfu11 said:
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
Click to expand...
Click to collapse
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you

wolfu11 said:
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
Click to expand...
Click to collapse
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.

dhacke said:
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
Click to expand...
Click to collapse
That script worked thanks

wolfu11 said:
That script worked thanks
Click to expand...
Click to collapse
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel

dhacke said:
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
Click to expand...
Click to collapse
No problem i'm happy to test. unfortunately the still is an issue with texting on verizon which is what i use this phone on. the texts send but receiving them is not reliable. I tested on an att sim and it didn't have an issue so it's something on verizon's end.

OnePlus 8 (instantnoodle) - ROM Installer [Linux Only ATM]

instantnoodle-tools-cli-main​Hey all!
I've started this project to allow people to use their devices longer, right now with a focus on the OnePlus 8, but eventually spreading to more devices. These scripts are currently for Linux Ubuntu/Debian distros only, but I plan on expanding support to other systems as well. Below is a link to all the files you will need to start using the scripts for beta testing on Linux machines. The only three ROMs available at the moment are Lineage OS 18.1 (with or without Google), ShapeShift OS v2.6, and Pixel Experience, but, again, more ROMs will be supported. I also plan to include troubleshooting support for frequent issues that can be fixed.
GitHub - kyg203/Android-Tools-CLI-
Contribute to kyg203/Android-Tools-CLI- development by creating an account on GitHub.
github.com
setup.sh - this script installs all of the tools and software for the next scripts to use for flashing. Please initiate this script first time and every week or so to keep tools up-to-date and fresh.
autotools.sh - This is the main script you will be executing. The rest will be executed from here. Do not execute any others manually to ensure you don't break anything.
rom-installer.sh - ROM chooser script. downloads the ROM of your choice and extracts the fastboot images from the payload.bin file. Do not execute from here.
In each ROM folder, there will be an info "readme" file. These files basically serve as a directory listing, allowing you to find the project page on XDA/GitHub/Website, look at any known bugs before you flash, and see any special install instructions. Please check these files regularly!
I will be focusing on perfecting the process on the command line on Ubuntu and Debian based distros first before I begin supporting more distros and operating systems. feel free to leave comments about the project below and begin porting your device into the project!
<---------- WARNING ---------->
// THIS IS STRICTLY IN ALPHA TESTING
// USE AT YOUR OWN RISK AND ALWAYS BACKUP YOUR DATA
<---------- WARNING ---------->
<---------- REQUIREMENTS ---------->
YOUR DEVICE MUST BE BOOTLOADER UNLOCKED
PUT THIS FOLDER IN ROOT (~) aka Home
PATIENCE - This project is still in the process of setting up and may produce errors. Feel free to contact me or anyone on XDA to help you with any issues or answer your questions.
BACKUP YOUR DATA - Backup all of your data even before you unlock your bootlaoder, because as soon as it is unlocked the device is wiped. Be prepared and you have been warned.
<-------------- RECOMMENDATIONS ------------>
I highly recommend you root your phone and leave Lineage Recovery or Pixel Experience Recovery on the device. This generally makes troubleshooting faster and easier. Plus, it allows you to backup your persist.img in the chances it does get corrupted. I will be adding a tool to backup and restore this image for you.
If enough support comes through, I will make a Telegram and Discord for this project specifically for support.

This is a really exciting concept and thank you very much for your efforts thus far.

UPDATE [2020-06-03]
- Added a new folder hierarchy to organize the mess a bit
- The entire project does not create anymore folders inside or outside of the branch
- Trying to leave a small footprint, so deletes all .img's, .bin's, and any other files immediately after usage.
- Updated README (and above)
- Brought support for ShapeShift OS (v2.6 Sceptile)
- Trying out an info file in each ROM folder to highlight features, issues, support, and information. Still working on gathering more information.
Hope everyone is doing well! If anyone has tried it out yet, even an older version, did it work for you and how was the overall process?

Can this be already used or not yet ?

dan20063 said:
Can this be already used or not yet ?
Click to expand...
Click to collapse
Yep! Only works on Ubuntu based systems.
Download the folder, execute setup.sh (as sudo) and then execute autotools.sh (as sudo).

You're "average Linux user" (ik basically a meme at this point) will have no issue installing a ROM manually instead, and would most likely prefer the control and ease of mind of the manual way. Especially because they still need to download and get an understanding of ADB/Fastboot and its commands since that's necessary for unlocking the bootloader.
With that being said I'm glad you made this, looking forward to further development, and I'm downloading now to test and for S&G.

Yeah, that's true. I just wanted to get it going and working on Linux where I'm a bit more comfortable and then switch it to Windows once I have a Windows device. I definitely added a bootloader unlock, but that obviously only works for unlocked devices

Nice work!
Thanks for your time, effort and sharing.

Just updated the autotools project!
What's new?
-- Updated all the available custom ROMs and custom recoveries
-- Shorted a couple of scripts to reduce folder size
-- New backup_persist.sh script - self explanatory. Everytime you run this script, it erases the previous backup, so be careful about executing this one!
-- New restore_persist.sh script - self explanatory - Uses the last made backup of your persist.img!
If you want multiple backups of the persist, maybe for different versions of Android, you will need to go in and rename those files separately. To do this from the terminal, just type "mv persist.img new-name-of-file-here.img" or you can rename the file from your local file manager.

Just a reminder: this project is open source! Please port it to support your own device! I'll be finishing up the OnePlus 8 by this weekend and then working towards my Pixel 6 when it comes in by Christmas.

Compiling Custom Recovery with GitHub Workflows

If you don't have a Linux device or don't have enough storage space to compile Custom Recovery, then maybe the following link can help you.
- Visit my GitHub repository and Fork it
(https://github.com/VThang51/ROM_Recovery-Builder)
-(Don't forget to read the README.md)
- Custom Recovery versions are supported:
+ OrangeFox-RP Builder (Fixing Bug)
+ PitchBlack-RP Builder
+ RedWolf-RP Builder
+ SkyHawk-RP Builder
+ TeamWin-RP Builder
- If the compilation is successful, please comment below. Just like TWRP, I also want to hear your story

Nice but i need to learn how to build twrp first haha
Guan Yu said:
Nice but i need to learn how to build twrp first haha
Click to expand...
Click to collapse
Nice, If you have a device tree and make sure it doesn't fail. I will guide you haha

I'm trying this out right now with the oneplus 7 pro 5g since there's like no development active on this specific model

TechX1991 said:
I'm trying this out right now with the oneplus 7 pro 5g since there's like no development active on this specific model
Click to expand...
Click to collapse
Make sure your Device tree is not corrupted. Because when it fails, it will have to start over and it takes at least 20-60 minutes

VThang0511 said:
Make sure your Device tree is not corrupted. Because when it fails, it will have to start over and it takes at least 20-60 minutes
Click to expand...
Click to collapse
I was using device trees from Lineage's github, but seems 3 devices i've tried so far all fail with
fatal: Remote branch master not found in upstream origin, error exit code 128

TechX1991 said:
I was using device trees from Lineage's github, but seems 3 devices i've tried so far all fail with
fatal: Remote branch master not found in upstream origin, error exit code 128
Click to expand...
Click to collapse
Haha, This error is quite rare if you double check the options. This error says your Branch is not "master" (It's just the Branch name on my URL). Double check the Branch name on GitHub.If you don't know, send me the device tree link and I'll compile it for you

VThang0511 said:
Haha, This error is quite rare if you double check the options. This error says your Branch is not "master" (It's just the Branch name on my URL). Double check the Branch name on GitHub.If you don't know, send me the device tree link and I'll compile it for you
Click to expand...
Click to collapse
just my luck, I get the "rare" error multiple times lol it was more for the learning of it that I was doing this. TWRP is available for the 3 devices I tried (op 7 pro 5g, op 8t and op 6t), but wanted to learn to do it so I can try it on lesser known devices like asus zenphone 1 or razer phone 2