How to install twrp from official TWRP App
after rebooting just wait for the black screen, don't panic, it's the boot process
The TWRP.img You gave is Compiled By me for realme C11/12, Since realme C11/12/15 ( mtk Edition ) are same it worked in C15 & I know About that, Please try to Give Credits to original Owner of the Compiled ROM/Recovery, I've verified md5 checksum too, its same, Edit The post with proper credits, Thanks
@bass_deso THREAD CLOSED and the formerly attached twrp.img removed.
It seems you haven't credited the original developer of the recovery that you posted. Even if it had been your development TWRP is licensed under GPLv3 i.e. you were required to provide a link to your source.
Please advise the moderaors team (best via the report function) to re-open the thread when ready to credit the devloper of the TWRP and to mention where you obtained it from. If the original location does not obtain a link to source you'd be required to provide that link.
XDA Forum Rules (excerpt):
...
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or to a Moderator. We are here to help!
...
Click to expand...
Click to collapse
Related
The following are reasonable formats that are suggested when posting a new ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel they must provide a link to the kernel on XDA (if available) or a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available).
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external websites home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
The following are reasonable formats that are suggested when posting a new ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel they must provide a link to the kernel on XDA (if available) or a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available).
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external websites home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
Hello,
I want to become maintainer for Lineage OS for specific device (I will buy the device to maintain).
Could someone plz explain me the process of becoming the maintainer and pre-requisites for it?
I had a look at teamoctos/join-our-team/ but it will be helpful if someone explains all those steps in it.
--
Thanks
I'm not sure about this but however:
First of all you will have to build device tree for that device (I guess that device isn't supported at the moment, if is than you can contribute to that repo on github via pull requests and wait for them to approve change) and that device tree works without lethal bugs. Also you'll need kernel that won't make you much troubles because manufacturer probably published sources (they had to). And when you make it work than you can try to conntact them about joining team, if they accept new devs, because I read somwhere about how to make CM support device officialy they mention only they support devices they own, they not mention anything about joining team if I remember well. It's best that you conntact them and ask I'm sure there is way for that.
alpesh.valia said:
Hello,
I want to become maintainer for Lineage OS for specific device (I will buy the device to maintain).
Could someone plz explain me the process of becoming the maintainer and pre-requisites for it?
I had a look at teamoctos/join-our-team/ but it will be helpful if someone explains all those steps in it.
--
Thanks
Click to expand...
Click to collapse
Unless a specific thread states otherwise (which will provide you with the individual or location to do so), the XDA Forums isn't where you request this.
Regarding the Official LineageOS, though, the XDA Forums isn't where you request this either, here's the only location (at this time) to where you can find what you're looking for.
1) Go to the following link:
http://wiki.lineageos.org/faq.html
2) Scroll down to the following question (without quotes):
"My device is not officially supported, but I’d really like to give LineageOS a try. Can you support my device?"
3) It is there that you'll find the information you're looking for as well as the E-Mail address to where you can send them the information.
Good Luck!
Sent from my SCH-I535 using XDA Free mobile app
This version of GCAM is stable
Everything working
Need to replace te .XML file
Mod Edit : Links Removed.
( Download from here) #GCAM
Download the XML file
Mod Edit : Links Removed.
All you need to do is simply install the GCAM
Go to setting> advance > save XML configuration
Simple name it and save it
Then go to internal storage> Google camera> camera configuration > paste the downloaded XML file ( don't delete any other XML files) > exit
Now open camera and double tap on camera between shutter button and front cam
It will ask for restore XML
Restore the new save XML ( downloaded)
Camera starts automatically (means applied new configuration)
Hit like if you do
Thanks
NOTE:-
[ I am not the developer] just sharing his work
Mod Edit
2 Threads on same topic / reposting is not allowed and there is already a thread here dedicated for gcam
May I remind you XDA Forum Rules #12
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
Thread Closed.
jackeagle
Forum Moderator
This Google website offers frequently updated daily GSI builds of AOSP, where code changes from literally any contributor to the Android Open Source Project are built and hosted on Google Servers.
Branch Grid
ci.android.com
The FAQ states that there is a two factor security system in place to ensure the added code is genuine and safe.
Reviewers check the added code and make sure it's consistent with Google Guidelines.
Verifiers build the changes and verify it if everything checks out.
That's basically it.
Meaning the code inside those images ready for download on ci.android.com has only been vetted by a single reviewer, before a verifier builds them for testing and it is hosted as an artifact.
I understand that these img files are not meant to be used by anyone, but it still seems a little crazy to me that Google would publicly host an image file of AOSP which could potentially be downloaded or even flashed by anyone, while the code inside has basically undergone 0 scrutiny.
@tablet_seeker Thread closed as duplicate of
Malicious Code in GSI Images From Google's Developer AOSP Branch?
This Google website offers frequently updated daily GSI builds of AOSP, where code changes from literally any contributor to the Android Open Source Project are built and hosted on Google Servers...
forum.xda-developers.com
Welcome to XDA! I hope you'll always get the support you require. However, please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation, and remember you agreed to adhere to the forum rules when you registered a few days ago.
Regards
Oswald Boelcke
Senior Moderator