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.
Related
I'm Linux & BSD literate, and used to administering servers, compiling programs and kernels from source. I've also managed to root and flash my Magic, following advice found here. What I'd like to do is gather up some info on how to build ROMs for the Sapphire platform.
I'm already poking around the Android Wiki FAQ and the Dream dev forum on this site. There's quite a bit of info there but some of it is out of date and I've not found much that's Sapphire-specific. I also plan to take apart the .zip files released by Haykuro and others and compare/diff configs to get a feel for things.
My intent is to put together enough info to allow anyone to pull apart a released ROM and replace the dialler, add some language support or some extra apps, maybe make some other simple changes.
What I need is any pointers on:
1. Sapphire-specific info.
2. Any danger of bricking my Magic by messing around with home-made ROMs.
3. Anything else that might be useful.
Hopefully I'll be able to put together a rudimentary HowTo for the wiki, which others can add some fine-tuning and extra info to.
Thanks for any input.
I think this is a very good idea!
It would simplify things if everybody would understand how exactly custom ROMs are created.
1 - Be aware that there are different Magic HW versions...
2 - I don't think you can brick your magic as long as you make backups via nandroid.
3 - A few things I think should be in the wiki :
- how to completely setup a linux environment and which applications you need to be able to build custom ROMs.
- Explain how the android OS is working, explain what boot, hboot, recovery, system is, how the partitions work, etc..
- What are test-keys, what is the difference with and release-keys.
- How to sign.
- How to dump the recovery.img, boot.img without having root access.
- What to change into the recovery.img and boot.img to get root.
- How create an update.zip
- How to make backups with nandroid and how to restore them..
Agreed think this would be a fantastic idea, unfortunately it seems like the people in the know are not willing to share any of their knowledge =o(
Do keep us up to date as to what you find by dissecting the ROMs, had a look the other day briefly but didn't have time to play yet,
Also waiting for info/confirmation that as long as you just flash bad roms its not possible to brick your phone only if you play with SPL's and such
fxn said:
Agreed think this would be a fantastic idea, unfortunately it seems like the people in the know are not willing to share any of their knowledge =o(
Click to expand...
Click to collapse
Oh, I'm sure the knowledge is scattered around the place - sharing is one thing, bothering to document is quite another!
The only thing I don't expect to find openly shared is traceable leaked material, and frankly I can live without that.
Hello all,
Updating android-x86 variant could be accomplished via OTA updates, and/or
another bootable installer, however wouldn't having the ability to 'flash'
customizations via a GRUB like interface be beneficial as well?
I feel for testing purposes that this could be beneficial. Having the
ability to rework the source without having to do a clean install every
time could provide a more accurate method for testing. This would also be
good for devs, who want to modify their actual system rather than a virtual
one.
I have little knowledge of android building, however I am vaguely familiar
with C and java. I have the source downloaded and I am reviewing it, in the
case that people will find this worthwhile, I will (hopefully) be able to
contribute to the cause.
Again, if I am completely off base here, please inform me. I am just trying
to help the cause!
Thanks all for future inputs. :good:
korg bootable recovery ( may be useful) : http://sourceforge.net/p/android-x86/korg_bootable_recovery/ci/master/tree/
Source thread : http://grokbase.com/t/gg/android-x86/143w3yx749/grub-based-recovery-similar-to-cwm
bump
no idea?
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
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.
I am not completely new to rooting my android device's however I had two questions I was hoping someone could answer for me. 1, How do you find binaries beyond what is currently in BusyBox and 2. What are the skills I need to learn to begin to understand creating my own programs, or magisk modules to try and tackle a larger project as I have reached about to the end of the line for just using the already available tools and want to try my hand at actually developing something.