Question A useless TWRP device tree I attempted to make - Samsung Galaxy A22 5G

Since nobody wanted to make a TWRP build for the A22 5G, I tried making one myself.
Being the genius I am, only having learned one programming language that won't be useful at all, this failed. I can't get it to build and have no idea how GitHub actions work. Also other issues, including possible missing/incorrect directories and values in various files. Since open-source is great, and forking is a thing, I'll put my repo here as a sort of shimmer of hope for anyone desperate for TWRP.
GitHub - CatFishing4Guyz/twrp_device_Samsung_A225G
Contribute to CatFishing4Guyz/twrp_device_Samsung_A225G development by creating an account on GitHub.
github.com
However, if you do become successful, give me most of the credits as well as other people mentioned in the README.md.

Related

Help setting up my first Kang

Hello everyone,
This morning I used repo to get cyanogenmod repository from github (10go!!!) and I was able to build cm from source for the first time.
I now have a pretty update-cm-7.2.0-RC0-glacier-KANG-signed.zip I could flash to my phone.
All credit go to CM team and to sykopompos' tutorial :
http://forum.xda-developers.com/showthread.php?t=915435
My next goal is to create a kang which is :
- A barebone CM7 (strip everything I can)
- minimalbread theme as default
I have a couple of questions and I'm seeking help.
1- What is the best way to work on some part of CM7 ? Fork each parts on github ? Use git manually or continue with repo ?
2- repo tool fetched everything from github. The device folder contains code for other phone than glacier. Can I delete them without issue ?
3- Do you have essential docs I could read to get familiar with folder structure, important config file, etc.
4- To learn, I'm searching easy modifications I can make. Any ideas ?
Some info :
I already have a github account and I'm working on Archlinux64.
Android SDK, eclipse and others dev tools are installed.
I'm a web developer (mainly J2EE / JSF) and I'm very familiar with Java.
Thanks for your help.
Regards.
Bump + Answer to myself and maybe some others seeking the same informations...
1- What is the best way to work on some part of CM7 ? Fork each parts on github ? Use git manually or continue with repo ?
Click to expand...
Click to collapse
Easiest : start with Kitchen on compiled zip.
To work on some part, I will fork them on github.
Example, I want to mod framework-res. Safer to work with git and rollback if I mess everything.
2- repo tool fetched everything from github. The device folder contains code for other phone than glacier. Can I delete them without issue ?
Click to expand...
Click to collapse
Next repo sync they will comeback...
3- Do you have essential docs I could read to get familiar with folder structure, important config file, etc.
Click to expand...
Click to collapse
Android website is cool but I'm still searching for more...
4- To learn, I'm searching easy modifications I can make. Any ideas ?
Click to expand...
Click to collapse
I will try to ship the ROM with custom host file (block pub) and other small goodies.

[DEV] Bash-script to update CyanogenMod and create backups from your PC

Hey XDA!
The past two days I've been working on a little project that automates the process of checking for available CyanogenMod-updates for my device through ADB.
At some point I decided not to write it device-specific so that everyone who needs it, could benefit from it.
I kept adding features like creating backups and moving them to your PC and eventually put it up on Github. Here's what I have now:
cmUpdater: https://github.com/heavyhdx/cmUpdater
Downloads available updates, creates and restores backups of your device and installs updates.
It requires TWRP for some features to work and all features need USB-debugging/ADB.
I feel like copying the description with all the features and everything from the github-page would be a bit redundant, so for more information just read it there or dive right into the code.
This is my first real development-project and any criticism from the experts here would be highly appreciated.
Thanks for your attention.

[Q] Informations for building a new Device tree for a unsupported Device

Hi Everybody,
I want to ask for some informations what is need to do to build SlimRom for a new device. I found a lot of informations about CM, but nothing is really in a way that I really know what I have to do at the end. So is there a Howto, which describes it a little bit more in detail? A lot of howtos was found which describe to get a build-system, and to generate something for a know device. But everybody then describes only: you have to get the vendor files, made your Board-config but only on a very high level.
What I did:
- set up a building-server on ubuntu.
- get Slim-Sources branch JB4.3, and build the version for galaxysmtd to be sure that the buildprocess is ok.
- get "Nonreallyfree"-Opensources from Samsung for my I8200, and try to put them in the right places, and try to implement all needed files in the device/samsung/i8200 folder.
Up to now I think I have everything in place more or less, but the system told me that there is no rule for make 'bacon', but lunch seems to work right with setting the variables...
Up to now I did not used the blobs of the devices. The question is, if that is needed if I have the sources from open Samsung?
I know, jb43 is not the newest, but I start here, because up to now the sources are based on that level, and the kernel have no selinux implemented... If this start point will work, then I will try to go ahead with higher versions... end goal will be Slimkat...
Any help is very much appreciated!!
BR
SP

[Q] Need Help with Compiling AOSP Nougat - Proprietary Binaries

So I've decided to give building Android a go, considering we've recently obtained the source code for the device in question (R1 HD) and no one else has done this yet for this device. I've been following this guide, since all the other guides I've found assume there is already a GitHub repo for your device. There's literally NOTHING out there regarding this device, aside from the kernel source we've obtained in the form of a .zip archive.
I've done everything up to and including pulling the 7.0.0 r1 source with the reop sync command, and I am now stuck on the Preparing to Build section. The first thing it talks about at this point is implementing proprietary binaries into my source. I have no idea where to find proprietary binaries for my R1 HD, let alone if they even exist out there to be implemented. Literally all I have regarding this device is the kernel source in a zip file. I can't find anything else out there nor do I really know what to look for.
Can anyone tell me what to do here? I've never compiled Android or even a kernel before, and I'd really like to get something out there for this device that others can base their work off of.

Where's TWRP again?

I haven't been on here in awhile, and have been happy running crDroid on my 8t although I don't update due to having to format data every time What I've lost track of though is exactly what is the reason why there is still no working TWRP for the 8t?......can someone refresh my memory please? Thanks!
Lots of issues with moving TWRP to Android 11 plus additional wrinkles in the way OnePlus implemented dynamic partitions mean it's taking a lot of effort to get TWRP working.
Bottom line: it's actively being worked on and it will be ready when it's ready.
GitHub - theincognito-inc/android_device_oneplus_kebab
Contribute to theincognito-inc/android_device_oneplus_kebab development by creating an account on GitHub.
github.com

Categories

Resources