{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still waiting for that kernel source, so we found some more recoveries to at least do in that time. I know it's nothing new and exciting yet, and as much as I like bringing cool stuff like this I'm just as bored with recoveries as you guys probably are. Hope it satisfies your needs for content until Orbic finally decides it wants to release the kernel source for this thing like it's legally obligated to do. Believe me, I REALLY want to stop doing just dirty ports for this thing and get down to business with some real source, but I'm kinda screwed out of that now since they refuse to release it
This is BatikRecovery. It's an Indonesian fork of TWRP with a pretty sweet theme actually. Check out more about them on their GitHub page HERE
WHAT WORKS/DOESNT WORK:
Gonna be the same as all the other ones probably... phone shows up as a Redmi 3s because of the nature of dirty ports, and oem/vendor won't mount but everything else should (if data doesn't you need to flash the disable-verity zip and factory reset)
This recovery was supposed to come with a bunch of tools as it came in a flashable zip that contained the image and the tools to all be installed at once. However, because of how dirty ports work, unfortunately the tools are left out. There's not much I can do about this until we get the proper source to build our own stuff with
DOWNLOADS:
LINK TO BATIK RECOVERY DIRECTLY
LINK TO THE REST OF THE REPO TO SEE ALL OUR OTHER STUFF
Again I can't give source code for anything unfortunately because we're working with dirty ports here (because we ourselves have no source code for the phone or we'd be doing this the right way) but please feel free to use any and all of my images on the repo above for anything you want. It's a community effort here to get this phone pulled away from the dark side of the force
THANKS TO:
Team Orbic as usual
Team Batik for that sweet banner image I'm using, that's not mine that I made that's the official one that came from their GitHub page. Pretty cool!
XDA user @zhantech for making Batik for the Redmi 3s which we ported it from. Check out the original thread for it HERE
Carliv Image Kitchen for letting me do all these gnarly dirty ports
Reserved (screenshots coming and more details)
Related
Samsung has oppened a GIT repository for our phone 2 days ago (more convenient than the usual sources tarballs), as you can see on this page : https://opensource.samsung.com/guest/listMyCommunity.do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the repository : git://opensource.samsung.com/p_411
I am sorry buddy but can u tell me that how it will be beneficial for us??? Sorry I have dont have knowledge about this but want to know eagerly about this.
Instead of messing with the tarballs used by Samsung to provide the GPL parts of kernel & co, they opened a git repository, which is more convenient to retrieve the source code. (Try Google if you want more informations )
It's good for the kernel devs, and source on the repository might be more up to date than the actual tarball provided by Samsung (can't verify, I'm at work)
means now kernal coding will be more convinient to kernal coders??
can add TV-OUT with this source code?
As I understand, the stuff in there is already spreaded in the web. It's just a repository good for starters, isn't?
Does coderworkx can find anything relevant for CM (that he does not already have/know)?
u mean to say that we have the access to the opencore, kernels and rom now? thats a great thing if thats what happend.
I think this can be of very good help...i see some omap3 stuff and camera stuff
This isn't helping !
These files do we have a 4 months now.
Oh then the same old source files
Sent from my GT-I9003 using XDA App
thanks a lot!
I think code has already had most of the files created/grabbed before this was released. Which is somewhat depressing :\ because this may be considered useless
How can you tell if it was the same exact files? Maybe it just looks the same for the most part because it is the source after all but maybe the official release has some more stuff or some updated files that will make the kernels and roms work properly...
Just hoping for that CM7 to work flawlessly. hehe
Same date of old fiorano.. Same files
Inviato dal mio GT-I9003 usando Tapatalk
I think skin will explain this better.
So I'm currently coding a One click AIO rom cooker for ALL OFFICIAL CM supported devices (if it's on the CyanogenMod Downloads page, it'll be included).
Pretty much all you have to do is:
1) Download the folder from my github (link will eventually be included in the thread)
2) select your device
3) Select your version of CM (CM7, CM9 or CM10). IF IT IS SUPPORTED OFFICIALLY (a one click compile CM10 for a HTC Wildfire is outside my coding knowledge and patience level)
4) Set Options (Name your mod, Compile a custom kernel or use stock, copy the rom to your SD card and reboot to recovery, etc)
5) hit go!
It will:
Set up your Linux install (should work for Ubuntu and Debian)
Download the CM Source
Download the required files for your specific device (provided it can be found in the CM repository)
Build the rom
If selected compile Kernel and then recompile including the new Kernel
Copy the rom to an easy folder for you to send to your SD card (or have it do it for you)
Should be easy to update, just repo sync, then recompile (I think)
Easy debugging. All errors are automatically logged to a easy to find file.
What does everyone think of this? I'm aiming to have it released around Christmas, At least a beta version (may not support all devices out of the box, but I will keep working to add more (I need to test each and every device to make sure the cooker works). This will be released under some open source license (currently researching)
Here's a screenshot of what I have working so far (not much but it's a start). It's based on the layout of Android Kitchen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Info:
~ This project was originally started by me a long time ago, its been in different locations as different things, and its been written in many different styles.
~ So what is it? Well its a bash script/scripts/project/modular-project (this is how fragmented it is ) that were working on to be an all in one shell based application, currently we have a tonne of features in it and alot in our minds but we just need to get it down in the script.
~ So why post about it here if its still super alpha and not even 100% working!? Well cause we need developer help, anyone who wants can pm me or post here and ill add you with read access to our repo's , from there on you can create pull requests and help us refactor and clean up code.
~ Currently the project maintainers consist of me and @DeicPro , theres also @luca020400 who's contributed to cleaning up alot of the code. So we would love anybodys help! Even if you cant be on github constantly creating pull requests, at least pm me and ask to join the "dev" group since we can chill + it looks super cool to have a busy project
Source:
https://github.com/HybridMod
Setup:
~ This is the setup guide, you can either use the google repo tool guide and setup and use via that way, however you wont be able to do anything via git that way... The recommended way is below.
Recommended way:
Code:
mkdir -p ~/Scripts/HybridMod/
Code:
cd ~/Scripts/HybridMod/
Code:
git clone https://github.com/HybridMod/roomservice
Code:
cd roomservice
Code:
./repo_sync.sh
Now the repo_sync.sh will take care of cloning all the necessary scripts and etc...
Additional Notes:
Anyways thanks for the help if you do help, and enjoy!
banner-credits: idk , found on the google imgs, plis dont sue me ;-;
FAQ
Q: Do penguins have knees?
A: http://bfy.tw/LLo
reserved ^^
With Google releasing monthly patches (which I believe is a good thing!), it's become a bit of a chore to install updates, especially so if, like me, you have a modified device stopping you installing OTA updates.
I wanted to do something to make it a bit quicker, so I made Nexus Flash! I guess you can think of it as minimal ADB & Fastboot packaged with a GUI.
I've decided I don't like the GUI layout, and I'm pretty sure most will agree, so I've already started working a new layout, bug fixes, and adding some extra features which I'm sure some may find helpful like an update manager (so you don't have to go to Github every time there's a new version), another example is a way to boot an image file too, for instance, Chainfire's CF-Auto-Root.
Currently, there isn't much validation of user input, so please only use it as intended for now. It shouldn't break your device if you don't use it correctly since ADB has built in measures to validate files to some degree at least.
However, I have to say, this program is provided without ANY warranty or guarantee. Using this program is at your own risk. I have tested this on my own Nexus 5X and it works perfectly.
The source code is released under the GNU GPL (General Public Licence) and can be found on Github.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prerequisites for Windows:
You'll need the .Net framework 4.5.2 installed (Windows 10 already has this).
Prerequisites for Android device:
Your device must have an unlocked bootloader.
You must have USB debugging enabled.
You'll also need the Android ADB USB drivers installed too.
Guides can be easily found by searching for them, there's plenty of them around!
Links:
Binary - Github releases
Source code - Github
Issues or feature suggestions - please direct them to Github (preferred). Or simply create a comment on this thread.
Release notes
Version 1.0.0
Initial release!
I've had to delay writing the new update for this (because life gets in the way), but I promise I will get an update out ASAP!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Vendor Image: Removed Due To Request
Firstly, thank you for taking your time in making this post, @The_Pacific_gamer.
Are you a developer?
What do you mean by "crack into a vendor image", what did you do there (if any changes)............please elaborate.
Also this work is of @Lyuu not yours.
Lyuu has been developing Treble for athene since quite some time now.
Q) Why do you think she didn't release treble here on XDA? Was she dumb or does she not know how to make a thread?
A) No, because it's not ready to use yet. Lyuu once hard bricked her device while working on treble and that's the reason it has been paused now till Official Oreo comes out.
Please take this down or consider yourself reported as this treble is not stable for use (its still developing) and can hard brick the device too.
Your Request is favored
Heeth21 said:
Firstly, thank you for taking your time in making this post, @The_Pacific_gamer.
Are you a developer?
What do you mean by "crack into a vendor image", what did you do there (if any changes)............please elaborate.
Also this work is of @Lyuu not yours.
Lyuu has been developing Treble for athene since quite some time now.
Q) Why do you think she didn't release treble here on XDA? Was she dumb or does she not know how to make a thread?
A) No, because it's not ready to use yet. Lyuu once hard bricked her device while working on treble and that's the reason it has been paused now till Official Oreo comes out.
Please take this down or consider yourself reported as this treble is not stable for use (its still developing) and can hard brick the device too.
Click to expand...
Click to collapse
The Links and instructions were removed in your favor
The_Pacific_gamer said:
Vendor Image: Removed Due To Request
Click to expand...
Click to collapse
The_Pacific_gamer said:
The Links and instructions were removed in your favor
Click to expand...
Click to collapse
So I had to close your thread since it has no use now.
Wood Man
Senior Moderator