yashsingh1/xdaforums huggingface dataset:
[Android Software Development] elektrik2001:
another dumb question:

fatal: Couldn't find remote ref refs/heads/twrp-5.1

Is what I get when I type the repo init -u git://github.com/CyanogenMod/android.git -b BRANCH
[Android Software Development] TimSchumi:
CyanogenMod repo has no branch called twrp-5.1
[Android Software Development] MSF Jarvis:
You need the repo at github.com/lj50036/platform_manifest_twrp_omni

All credits for this minimal twrp buildable source to [MENTION=5123642]lj50036[/MENTION]. Great work sir!
[Android Software Development] elektrik2001:
yes, thanks, and if I followed the directions and weren't brain-dead I wouldn'thave half the problems I'm having <embarrassed>
[Android Software Development] serajr:
Mininal sources:

What's the size of download stuff (after repo sync)? Thanks in advance!
[Android Software Development] Deltadroid:
Just to lend a hand here...

Here is an example of my local manifest for the omnirom android-6.0 branch that should save about 30Gigs of disk space (since it removes all the projects that are not required to build twrp). This manifest requires an x86_64 build machine.

https://github.com/syphyr/cm_build_scripts/blob/master/local_manifests/local_manifests_omni_6.0.xml

Please let me know if you notice that more projects can be removed.
[Android Software Development] Smart walkie:
TWRP Consultant Required *HELP wanted*

Hello,

I need to learn how to do this and hope someone can help me.

1) Setup the required environment on my EC2 instance. (maybe you can even make a communit AMI so everyone can quickly start an instance with Omni etc already downloaded)

2) Show me how to compile TWRP for different devices. (MTK devices with ROM and stock recoveries available)

I am a newbie developer. I understand GIT, linux commands etc but really need to focus on getting these devices out the door on the sales side.

Donations/Paid Consulting arrangement can be discussed. please drop me an email at wenhan@smartwalkietalkie.com
[Android Software Development] MSF Jarvis:
This one has been brought down, the branch got force pushed with full omnirom-6.0 sources. Use Deltadroid's local manifest from below

Thanks for the help! lj50036 weaned off Android development so this was needed!
[Android Software Development] serajr:
So that's why the download never ends! Thank you!!

Thank you so much. I'll check it out!
[Android Software Development] yhguo:
This is a very helpful thread! Does this TWRP tutorial also apply to Android Wear devices?
[Android Software Development] JJoovvee:
more...

How did you get your device sources?

It would be nice to describe it as an example.

Why is this link broken? Https://www.google.it/url?sa=t&rct=j...6ltZvbVyzW9ybw

Can not you become more clear for beginners?
[Android Software Development] opticyclic:
The link is broken because it was a redirect to the CyanogenMod wiki which has shutdown.

The LineageOS (CyanogenMod fork/successor) wiki is not complete yet so you can get the info from the Wayback Machine in the meantime.

https://web.archive.org/web/20160421185935/https://wiki.cyanogenmod.org/w/Doc:_porting_intro

Certain sources should be made available due to the GPL and you can request them from the manufacturer of your device.

e.g. ZTE has a site here http://opensource.ztedevice.com/ and Sony has a site here http://developer.sonymobile.com/downloads/xperia-open-source-archives/ but not all manufacturers are as forthcoming and you have to pester them
[Android Software Development] KYROoo:
help

pls some1 could do me a twrp or a rom? i know it took alot of trys for you ppl and fails i would try it but since my device dont have a rom or a twrp/cwm for it i cant finde it no where im aafraid of it fails and briks my phone and i cant get it back :rolleyes:
[Android Software Development] Bornstud:
Which device do u have?
[Android Software Development] KYROoo:
i have an hisense c1
[Android Software Development] Bornstud:
Readback your device and get stock recovery.img and boot.img

Then pm me.

I will built twrp if I can do.
[Android Software Development] KYROoo:
how do i do that actualy?
[Android Software Development] Bornstud:
With SP flash tool

Search on google about same.
[Android Software Development] KYROoo:
sp flash tool work on qualcom sapdragon too? or is only for mtk?
[Android Software Development] DJKristy:
I think for mtk
[Android Software Development] JJoovvee:
Why do not they create twrp and custom ROMs and distribute them?

Although this is a step-by-step post, it is difficult for a novice to create a twrp of his device by looking at it.

I bought a device called asus_x550, and although it sold a lot, it did not come out twrp or custom ROM for over two years.

I think the engineer of the company who made this phone can easily make twrp or custom ROM by looking at this post. Why do not they do it?

I am very sorry that none of the people who bought this phone can make twrp or custom ROM for this phone.
[Android Software Development] teemo:
A company will always be busy developing the next thing. Why should they help people with NOT buying their next device by making your old phone live longer?

Forget the idea that it is difficult to build. It only take time and interest and a little brain as OP say. If you reeaallyy want it, then make it [emoji6]
[Android Software Development] JJoovvee:
hello~ haha..

Do not you buy a company's product again that does a good after-sales service?

I tried to make a twrp based on this post.

It is not as easy for beginners as an expert like you think.

If it is accomplished by some novice effort, why did not the asus_x550's twrp and custom ROM come out yet?

If you can do this easily, is there no intention to create a twrp and custom ROM for the asus_x550?
[Android Software Development] M.A.P:
I am not having kernel source for my device, can I use my device tree? In device tree there is stock kernel included can I build like that? I only got vendor and device tree, so I heard it is possible that you can compile twrp using stock kernel file without having kernel sources, if it is yes can anyone guide me? Thanks in advance.
[Android Software Development] TimSchumi:
If there is a prebuilt kernel included in your device tree, you could try that. If it doesn't work, you have no other option to ask the Manufacturer for the kernel source
[Android Software Development] M.A.P:
It should work as I tried but getting errors. I'm sure that those errors are not related to prebuilt kernel as other people with kernel sources are also getting that error when trying to compile. One thing is when trying to compile. BUt I'm getting only one error related to prebuilt kernel here it is:

build/core/tasks/kernel.mk:161: * Using prebuilt kernel binary instead of source *

build/core/tasks/kernel.mk:162: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED * build/core/tasks/kernel.mk:163: * Please configure your device to download the kernel * build/core/tasks/kernel.mk:164: * source repository to kernel/HTC/620G build/core/tasks/kernel.mk:165: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building build/core/tasks/kernel.mk:166: * for more information * build/core/tasks/kernel.mk:167: ***************************************************************

I'm sure that I can bypass that kernel error but don't know how. Any one who can help with this? I'll post other errors but first I should fix the prebuilt kernel error. I'm using cm full sourcecode as the device tree is for cm 13. Actually it is for HTC desire 816g but mine is 620G. The files are made by ahmed hady. Both devices are very similar, so I edited few files. There is prebuilt kernel in Ahmed Hady 's source too.
[Android Software Development] TimSchumi:
This is not an Error, it's just a simple warning
[Android Software Development] TimSchumi:
1) Please upload your logs to pastebin/hastebin/etc. in the future and just share the link here.

2) The 'errors' from base_rules.mk:559 and the ones from kernel.mk are not errors but warnings and they are totally fine.

3) The only error is in the last few lines concerning SELinux. May you be able to give links to the device/kernel/vendor trees you are using?

4) Your busybox seems to be corrupted. May you run the following commands from your source root?

rm -rf external/busybox
repo sync external/busybox
[Android Software Development] M.A.P:
1. Ok, will upload in pastebin next time.

2.Thanks man, I thought they are errors and worried a lot.

3.Well, I'm not using the device tree as it is as it is for 816g for I changed few files and did few edits in .mk files accroding to my device 620G. The source and vendor files are from Ahmed Hady's github repository. There is prebuilt kernel in Ahmed Hady's source, So I changed that, changed few files in rootdir which are in my boot img. In vendor files i changed few libs and files in etc folder. I'm Rom porter, so I'm familiar with that. But figured out that they are very same including libs! The only things I find different are kernel. My source and kernel are uploaded here and I'm giving links for Ahmed Hady's source. 816g source: https://github.com/Ahmed-Hady/android_device_htc816g/tree/cm-13;

vendor: https://github.com/Ahmed-Hady/android_vendor_htc_mt6592. Vendor is too large too upload but there is nothing really changed there just replaced few libs that already exist and replaced firmware and wifi folder, So I don't think there should be a issue regarding that.

4.I'm getting error for that command repo external/busbox. Here it is: error: project external/busybox not found. I'm using CyanogenMod full source and yes I added recovery manually as in guide by downloading twrp and placing in bootable/recovery-twrp folder and deleted existing recovery folder.
[Android Software Development] TimSchumi:
Hm, I can't find the offending SEPolicy line right now. TWRP shouldn't need any custom policies anyways.

Anyways, TWRP shouldn't need any blobs (maybe except for things concerning encryption). Also, building TWRP from inside the CyanogenMod source was always glitchy imho, I prefer the TWRP minimal tree which can be found in the other TWRP thread. There you also can use a very small device tree.
[Android Software Development] M.A.P:
Can we use cm 13 device tree for that? As it is the only device tree available for me. I don't think I can use minimal sources as I'm having cm 13 files instead of cm 14.1 sources which is needed for lineage os 14.1 minimal source. I'm also stuck with TWRP 3.0.1.0 as the last possible version. I found out that sepolicy is causing error, a line is causing. In external/sepolicy/Android.mk this line is causing error: "@mkdir -p $(dir $@)". Any idea how to fix that?
[Android Software Development] TimSchumi:
For the TWRP minimal tree (which is based on omnirom) you just need some basic device information, a fstab and a kernel (either prebuilt or source). Here is the example device tree which you only need to fill in your device information: https://github.com/lj50036/android_device_vendor_codename

The line you mentioned is not the one causing the error but the one printing it
[Android Software Development] M.A.P:
Thanks for the info will try your method and will update the situation.

Yeah, figured it later that it is issue in vendor/cm/external/sepolicy/su.te file.
[Android Software Development] TimSchumi:
Yeah, but the problem is that the policies from vendor/cm shouldn't be changed. You should remove the conflicting stuff from the sepolicies in your device tree
[Android Software Development] M.A.P:
Yep. I followed your instructions and successfully made recovery image but I need to make recovery image included with mtk header as my phone comes with mtk header. Can you help?
[Android Software Development] TimSchumi:
No, unfortunately not, I have no experience with MTK headers
[Android Software Development] M.A.P:
No problem man. You brought me this far thanks a lot for that. I'll research regarding that.

---------- Post added at 06:26 AM ---------- Previous post was at 05:51 AM ----------

I figured it out we need to also place bootimg.mk files which also came with my device's cm device tree which is having commands to make mtk header.
[Android Software Development] M.A.P:
After some tinkering with .mk files and also creating mtk header, I finally compiled recovery img but it is not working on my phone, it just reboots the phone into android os. So to investigate that I tried to unpack recovery img, then I came to know that the compiled ramdisk is not in gz format, I think that is the reason why my phone is not booting into recovery. Can you help me with that? Thanks in advance.
[Android Software Development] TimSchumi:
I don't think that it is the compression. Are you sure your custom mk file is linked correctly?
[Android Software Development] M.A.P:
Yes it is configured properly in BoardConfig.no "BOARD_CUSTOM_BOOTIMG_MK" := PATH TO THE FILE(Gave original path). Is there anything to do with java 8? I didn't follow the step you need to do before using make recovery image command for java 8 is that the problem?
[Android Software Development] TimSchumi:
Remove the " around BOARD_CUSTOM_BOOTIMG_MK and try again.

Also, I'm definitely not the right guy to ask about Custom Bootimg scripts or MTK devices
[Android Software Development] M.A.P:
I didn't add " around that argument, I added in the post to make the command visible. Didn't add that in brackets my bad.
[Android Software Development] M.A.P:
I successfully compiled twrp, what I did is I used bootimg.mk file from redmi note 3g omni twrp device tree as the one I used before came with cm and now it is compiled and even unpacking it shows everything correct like mtk header and ramdisk in gz but when trying to boot into recovery mode I get black screen for a sec and the phone just reboots and reboots like a loop.
[Android Software Development] TimSchumi:
Just like I said, I am not the right one to ask about this stuff. Ask an expert for your phone chipset
[Android Software Development] kirito9:
I have a good bit of experience with MTK processors. What do you need? Can you provide a link to your device tree?
[Android Software Development] M.A.P:
My device is not having device tree so I'm actually using a device tree of a similar device with few modifications in .mk files and also few files. I'm taking Ahmed Hady's desire 816g device tree as base as mine is 620g they are very similar in mount points, cpu, RAM and many other things so, simply 816g has 5.5 screen instead of 5 but same res and has better camera. Recovery has nothing to do with screen inches and camera. Vendor files needed few edits in lib files, I'm a ROM porter so I'm familiar with libs. I'm uloading my source here. Actually Ahmed Hady's source is cm 13 so I used that configuration and took the example device tree for omni as reference and built it and used bootimg.mk from redmi note3g omni rom device tree as that file is different for every rom. Source.zip is the cm13 device tree by editing Ahmed Hady's tree and Omni.zip is the omni source that I made for omnirom taking my modified cm device tree and sample device tree.
[Android Software Development] kirito9:
Cool, I'll check out your tree later today. I actually don't use omni for mtk as it almost never works for me. Same issue you get I got while building. Omni also makes the recovery bigger and I don't know for the life of me where those extra files come from. I use cm to do all my builds of recoveries from cwm-twrp. TWRP team said cm isn't as compatible with twrp source as omni is but I fixed the conflicts and now I have a working twrp :").
[Android Software Development] M.A.P:
Thanks man. Oh I'm new to compiling so I don't know about omni not working with mtk, thanks for the info as I'm still wondering why my phone is rebooting in a loop without booting into recovery when all files are present. Yeah, I noticed few extra files after compiling too like .ranchu files which are not present in twrp most of the time. Now I understand why Ahmed Hady made device tree for cm and not for omni. I used cm full sources rather than minimal sources, for some reason minimal sources are changed to lineage os and if I select cm13, full source is getting downloaded. No problem for me spending extra data though but still wondering. When I'm trying to compile recovery using cm I'm getting sepolicy error. Have you faced this issue anytime when compiling? Thanks in advance.
[Android Software Development] kirito9:
I do not know either why the recovery reboots and I never thought about getting a log to troubleshoot the problem. I just used CM and forgot about omni. I think I got sepolicy error but that could be related to the full device tree you're using. I use a minimal device tree that's only for making recoveries so I ran into less errors.
[Android Software Development] M.A.P:
Can you tell me how you solved sepolicy error? Cause I want to build ROMS too, yeah sure I can port them but I want to compile for my device. I think for now minimal device tree should be good so can you give me the structure of minimal device tree so that I can make one. Thanks in advance.
[Android Software Development] kirito9:
What is your chipset version? I solved the sepolicy error but eliminating it from the device tree altogether, you may also have a different error. I can't exactly say but just don't use a full device tree to build for now. Remember you ported that tree so you may have copied/deleted something that wasn't supposed to be there.
[Android Software Development] M.A.P:
Mine is mt6592 octa core soc. You mean we should remove sepolicy folder from device tree? Thanks in advance.
[Android Software Development] kirito9:
You can remove the folder and edit out the lines from the BoardConfig.mk. This tree is CM11 based but it should work with CM13. It's MT6572, so just do the basic porting to MT6592 and make the necessary changes to the mount points.

https://github.com/chijure/android_device_alcatel_yariss
[Android Software Development] M.A.P:
Thanks man. I'll try both of them but first I need to download sources again. First I'll try the device tree you provided, If I face any errors I'll post it here. I'll use vendor files for my device and I think that should be ok.
[Android Software Development] kirito9:
Vendor isn't needed to build twrp.
[Android Software Development] M.A.P:
Thanks for the info I'll ignore it then.
[Android Software Development] M.A.P:
I tried with the device tree you provided and got this error: "make: *** No rule to make target '/home/maanush/lineage/out/target/product/620G/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by '/home/maanush/lineage/out/target/product/620G/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.".
[Android Software Development] kirito9:
Post the entire log on pastbin.com.
[Huawei Watch] crosph:
Here's an odd one. Maybe my search terms are iffy, but I can't find anyone else with this issue.

When I uninstall the app on my phone for a watch face, Android will often (almost always) crash when that app/face gets uninstalled from the watch.

I say "Android" because the watch itself doesn't crash and reboot, but Android restarts (ie back to the boot-animation but not back to the bootloader).

I'll try and reproduce this with adb connected and see if I can glean some logs... that'll likely clear it up for me, but I'll post my findings here in case someone else has the same problem.
[Huawei Watch] WarCow:
I've noticed similar behaviour also, but only if im currently using that watch face and then uninstall it from the phone. If i switch to another one beforehand, nothing happens.

It also seems to happen with other apps, though I can't see a similar pattern there, it happens whether or not I'm using it, and often not at all.
[Huawei P9 Questions & Answers] askzeev:
brand new Huawei P9 EVA-019 simfree open to any network

can't put Hebrew in a keyboard

any help ?
[Galaxy Note 4 Q&A, Help & Troubleshooting] digitalchaos1980:
Hi guys and gals, have a quick question. I have a N910V Verizon variant Note 4 and had been running the Emotion r21 kernel on my highly modified but otherwise factory TW 5.1.1 rom. I have been looking for a kernel that works and has f2fs support because I want to try it out. Today I found an awesome kernel, the AEL 5.1.1. Ed. 3.10.101 kernel for the N910F/G dated March 16, 2016. I cannot find anywhere that says this kernel may or may not have f2fs support. Does anyone know if it does??

Chuck
[Galaxy Note 4 Q&A, Help & Troubleshooting] Rajada:
If you have the phone and the kernel, you can try, Or not?
[Galaxy Note 4 Q&A, Help & Troubleshooting] digitalchaos1980:
Yea I guess I can always try it and restore back if it doesn't work. Might just do that later :)

Chuck

--------------------------SOLVED----------------------------

OK well I did a Nandroid backup, changed /data and /cache partitions to f2fs filesystem and restored my data backup and boy the system did NOT like that, so I'm guessing this kernel doesn't yet support f2fs. It would be nice if I could somehow add the support to it in the existing kernel. Does anyone know possibly how I could achieve that??

Chuck
[Galaxy Note 4 Q&A, Help & Troubleshooting] Rajada:
ael is a kernel without public sources, so, you cant have any trust in this kernel.

Some time ago, I used a kernel with f2fs in note 3, and honestly I did not see any advantage.

However if you want to try f2fs, my advice is, leave the ael kernel for children, its not a serious thing, and compile your own kernel.

It is not difficult to make a kernel with f2fs, from what I remember in note 3, the major difficulty was in changing the ramdisk.

Currently I have no time for these activities, but maybe in a few weeks I can have some free time for this.
[Galaxy Note 4 Q&A, Help & Troubleshooting] digitalchaos1980:
Thanks for the reply. That sucks about not trusting this kernel. I've been running it close to a week now and actually like it better than the Emotion kernel I was running. It is so smooth and battery life has been great, even with a mild overclock! If I could ask, what would I not be able to trust about this one? Anyways, I might look into compiling my own kernel but I've never done one. I am a power user so I wouldn't be scared to try lol. If you do end up trying in the coming weeks then I honestly would appreciate it but you don't have to on my account :)

Chuck
[Galaxy Note 4 Q&A, Help & Troubleshooting] Rajada:
I refuse to use a kernel without public sources. you use what you think is best for you.

but it was you, who said, that the ael kernel supports f2fs but that does not work. It seems to be a untrusted kernel.
[Galaxy Note 4 Q&A, Help & Troubleshooting] digitalchaos1980:
No, I didn't say it supports f2fs. I said that I was looking for a kernel that supports f2fs and I couldn't find anywhere that lists the features of the AEL kernel so I could see if it does support f2fs. Since I couldn't find a list of features or a changelog, I decided to try it and see if the support was there, but it wasn't :/

Chuck
[HTC 10 Questions & Answers] mgdking:
I have had my 10 for some time now & have of course charged it several times. Well last night for the first time when I plugged my 10 in I was presented with this new screen I have never seen before? Enclosed is the screen shot. I have used nothing but the orginal cord & charger it came with and nothing else. Before this screen started doing this it would just show the red led light and that was it. Can someone tell me what this is and if I can modify this somewhere in the settings? If I do change anything will I still be getting the fast charging that I have grown to love? Iam still stock running next launcher & a few zooper widgets is all. There is nothing within next launcher or zooper settings regarding this? Anyone have any idea?
[HTC 10 Questions & Answers] mgdking:
Iam also wondering where the ads within this new screen come from as well if someone could answer that as well?
[HTC 10 Questions & Answers] squ89r97:
definitely a third party app adding lock screen ads. Es file manager or something.

Delete an app or two and keep going until it stops.
[HTC 10 Questions & Answers] mgdking:
But I haven't installed anything new since this started? That's whats mind boggling? Here is another screenshot of an option it gives me if a tap the upper right corner.