yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Sudarshankakoty:
Haha. :laugh:

I am so hard... So curious.... And I am working day and night for compiling custom mods for this device, including custom ROM, recovery etc. But main problem is my manufacturer is not releasing the kernel sources for this device, so no development exists for it.

Well.. The TWRP script is for MTK device, will this work for sc7731 soc ?

I have CM13 sources, but when giving mka recoveryimage, gives me this error
[Android Software Development] Matt07211:
I am not sure what is wrong, but it seems like Maybe some file are missing??? I am not sure though, you need someone with experience with this to help. Also notice the "//" on one of the last lines. Not sure how it would affect anything.
[Android Software Development] kirito9:
You need to use a service like pastebin for your logs, no one will be able to help with just a screenshot. I used to be like you but it was an ineffective way to get help.

Also, this script won't for Spreadtrum devices. Search on github for your processor and see if it turns up any results for a device tree.

If it does, clone it and make necessary changes to match your device. Compile again and try. Why are you building on CM13 tho?
[Android Software Development] Sudarshankakoty:
Why I am compiling ? 1. My device didn't get update after lollipop. I need Marshmallow for few more features including theme.

2. I want to learn how to compile from source

3. How android works

4. Help others by compiling custom recovery

Why I am getting stuck ?

1. Device and kernel resources are not available in github

2. Building TWRP with CM13 Sources
[Android Software Development] kirito9:
Yeah, it's better to build on OMNI. You can use prebuilt kernel for cm13 I think.

I find nothing wrong with what you do. I admire your determination. Not sure what could your problem be.
[Android Software Development] Sudarshankakoty:
How to use prebuilt kernel ? I think I have to write a script to extract it from my stock firmware
[Android Software Development] kirito9:
It says it all on the first post....i.e the reason for the name of the thread. You can use an app like Flashify to extract your boot.img then Carliv Image Kitchen to extract the boot.img to get the kernel (boot.img-kernel). Rename it to kernel and read the first post again for the flag to use prebuilt kernel (hint hint).
[Android Software Development] Hacker432:
If you want you can use this twrp device tree as example

https://github.com/Hacker432-Y550/twrp_cm_y550/tree/TWRP-3.0.2.0?files=1
[Android Software Development] kirito9:
Would this work for a Spreatrum device?

EDIT: I guess he won't have to use everything...just edit out the stuff he doesn't have. I think SPD uses dt.img so this is good.
[Android Software Development] Sudarshankakoty:
Only device tree is sufficient ? Using prebuilt kernel will be enough right ?
[Android Software Development] Matt07211:
Prebuilt kernel is enough. Not sure about the device trees being sufficent. But it's a good starting ground
[Android Software Development] Hacker432:
Yes it's a good starting

Prebuilt kernel is sufficient(dt image too if your device use it)
[Android Software Development] Matt07211:
[MENTION=7448137]Sudarshankakoty[/MENTION]

Have you tried using xauolus (not sure how to spell his name) unpack tools to try and unpack your boot.img yet?
[Android Software Development] Sudarshankakoty:
Yeah. I know how to unpack and repack these img partitions. I can unpack theme in both PC and Android device (using apktool)
[Android Software Development] Matt07211:
Does an dt.img file get produced when doing it? As it's an important file if your device requires it.
[Android Software Development] Sudarshankakoty:
I get a dt file in config folder while extracting a Boot.img
[Android Software Development] Matt07211:
Keep it and use it. dt file is a bunch of dtb files out together. (http://elinux.org/Device_Tree ) and it's use is to describe the hardware without coding it into the source code.
[Android Software Development] Sudarshankakoty:
Here is my device tree and info. Try to make anything (Recovery, MOD etc) with these and share with me.

Device Tree : https://drive.google.com/file/d/0B377TLFOgWdsRjlMMzFPbFdzV2s/view?usp=docslist_api

Device Details : https://www.dropbox.com/s/pwpgo7muawmekwf/Device Details.zip?dl=0

I am unable to make a single piece out of them. :eek:
[Android Software Development] Matt07211:
Better hope someone is nice enough to help. Becuse I can't sorry.
[Android Software Development] Sudarshankakoty:
Haha.. i can understand

---------- Post added at 04:35 AM ---------- Previous post was at 04:32 AM ----------

Hey, It worked. :good::rolleyes:
[Android Software Development] Matt07211:
Okay, what do you mean it worked? Did your phone boot up?
[Android Software Development] Sudarshankakoty:
Phone always used to boots up... I already had a TWRP 2.8.5.0 ported for my phone.

The compiled recoveries not working... Ported things works. but that's not the real fun. Compiled recoveries stuck in android logo and then reboot into system. But this time, recovery booted.
[Android Software Development] Matt07211:
So your own custom built recovery booted, that's awesome :) Did it only boot after adding the dt file? It will be the same for the boot file as well
[Android Software Development] Sudarshankakoty:
Yeah. That dt file gave soul to it. It's Eureka moment for me. ☺

---------- Post added at 05:05 AM ---------- Previous post was at 05:04 AM ----------

And credit also goes to you.... :good:
[Android Software Development] Matt07211:
Yea its a rather important file as it contains all the hardware information, and without it your software can't communicate with the hardware
[Android Software Development] Sharashchandra:
Hi,

My device is intex aqua speed HD

MT6582 android 5.0

please can u tell me how to compile TWRP using this script
[Android Software Development] MSF Jarvis:
That guide is the easiest possible method to follow the script, if you can't figure that out I'm sorry but you can't be helped :(
[Android Software Development] kirito9:
He already explained how to do it. [MENTION=4478781]yuweng[/MENTION] is the best at guides, if you cant follow then as [MENTION=6552280]MSF Jarvis[/MENTION] said, you can't be helped.

I'll still help tho :D What step are you stuck on? Getting a linux distro? :D
[Android Software Development] Sharashchandra:
I installed BBQLinux

And when I run this twrp script its always showing "internet status:down"

(even it is connected to internet)
[Android Software Development] skaox:
Still no answer for "internet status:down" !

Open the twrp script line 51 :

if curl --silent --head httx://xxx.google.com | grep k >/dev/null;then

replace by :

if curl --silent --head httx://xxx.google.com >/dev/null;then

sorry for the httx://xxx but it's my first post and for preventing spamming external links (http) are not allowed.

If like me you prefer using ubuntu instead of bbqlinux (archlinux)...

comment line 4 to 14 like here : github.com/MSF-Jarvis/AIO-TWRP-Compiler/blob/master/twrp

You also need to install the repo command who's include in the phablet-tools package :

sudo apt install phablet-tools

Thank you for the script good work :good:
[Android Software Development] MSF Jarvis:
I'd suggest sticking to AOSP's installation instructions for git-repo

mkdir ~/bin

# add to .bashrc
PATH=~/bin:$PATH

curl [url]https://storage.googleapis.com/git-repo-downloads/repo[/url] > ~/bin/repo

chmod a+x ~/bin/repo
[Android Software Development] skaox:
repo in Phablet-tools package (ubuntu 14.04) was version 1.21.

As with adb it's alo possible to replace (update) it in /usr/bin ;)

Thank you
[Android Software Development] Sharashchandra:
Hi

Iam getting this when I click on compile recovery

Set cache size limit to 26214400k

WARNING: device/intex/Aqua_Speed_HD/omni.dependencies file not found

At last its terminating with error1

And showing no recovery.img found

Plz help me

---------- Post added at 02:40 PM ---------- Previous post was at 02:33 PM ----------
[Android Software Development] Sharashchandra:
Hi

I used the script with BBQLinux

everything ok till compile twrp

When I choose compile twrp

Its not at all showing any buildtool or any other like in the screen shot

Its showing target thumb C++

target thumb C

target asm

atlast its showing no recovery.img found @ omni/out/target/product/aquaspeedHD

Please help mez

thank you
[Android Software Development] Andrzej_Andrzej:
AIO-TWRP-Compiler on BBQLinux and other distros

Does this AIO-TWRP-Compiler on BBQLinux work on debian ?

Somewhere I read that probably yes, I established ( I hope correctly BE) but when I run sh TWRP script, terminal stays black on command prompt (no errors receiving) and this main program window doen't open. Additionally is it also possible to download and sync sources for 7-Nougat or only for android 5 and 6.

regards,
[Android Software Development] ZawZaw:
Hi...friends,

How to add F2FS support TWRP in my own Build.

Now, I buit TWRP form omni source for Nexus 5X.

Please, help me.

•••
[Android Software Development] lightwars:
Your kernel has to support for f2fs,if not you can merge f2fs repo from kernel.org. make sure f2fs is enabled in your kernel defconfig.

Then add the flag "TARGET_USERIMAGES_USE_F2FS := true" to your BoardConfig.mk file. For me this worked.
[Android Software Development] ZawZaw:
OK Sir,

Thank You so Much.

I want to know

This mean "Need your Kernel support for F2FS" is

TWRP's inline Kernel?

or

Phone's Kernel?

I mean that

#example

In twrp source,

/kernel/lge/bullhead/

This kernel source's f2fs support?

Thanks!!!

•••
[Android Software Development] kirito9:
It's the same one, does your phone use a different kernel from twrp? If you compile the kernel with f2fs support on the main source then just use the prebuilt flag in BoardConfig.mk pointing to the f2fs compatible kernel or apply it to both if you're not sure which is which.

I don't see the need to apply it to both but whatever floats your boat :good:.
[Android Software Development] ZawZaw:
Thanks Sir. :D

•••
[Android Software Development] ZawZaw:
Hi...Sirs,

I can built F2FS support for Nexus 5X.

Thank You very Much for help.

•••
[Android Software Development] steadfasterX:
for all those not aware yet there's a new flag which uses vdc+vold (on system partition) for encryption/decryption:

Full details on how to use: https://github.com/omnirom/android_bootable_recovery/commit/71c6c50d0da1f32dd18a749797e88de2358c5ba1

Its meant as a fallback only though

[MENTION=6552280]MSF Jarvis[/MENTION] : you may want to add it to the OP..

sfX
[Android Software Development] flipinfin:
BoardConfig.mk changed to Android.mk ?

Forget it i misunderstood him at first
[Android Software Development] mightysween:
Hello,

Is anyone aware of a TWRP flag to enable the "FORMAT DATA" button on the wipe screen? It seems to be missing in my builds of 3.1.1-0 and I haven't been able to find any way to enable it.

Or, is the button contingent on a flag in fstab?
[Android Software Development] MSF Jarvis:
There is no flag or fstab entry that enables it AFAIK
[Android Software Development] mightysween:
Thanks. Building ground-up for the Moto X4 and I can't seem to find any reason it is missing... though it seems to be missing in code, too. So maybe need to resync with full Omni source.

In the meantime, everything else is coming along. Seems I just need to build a proper vendor tree to decrypt data -- a more useful solution anyway than formatting it. :)
[Android Software Development] DiamondJohn:
I'm pretty sure its a flag in the fstab. In the OP there are examples with "wipeingui", or do you have the wipe and the format button just isnt there
[Android Software Development] mightysween:
Thanks. Have tried with and without the "wipeingui" flag... same result. When enabled, of course, it does present the option to wipe /data (but fails to mount due to my encryption issue)

EDIT: actually, /data seems to have the wipe option regardless of that flag. Strange.
[Android Software Development] Isrgish:
I know this is an old thread but I haven't been able to find the info. anywhere else.

Is there a flag that csn set the backup location? My TWRP doesn't have a working GUI interface so I use the twrp command line interface. I would like to set the location to the external sd card. In the command line I can set it with "twrp set tw_storsge_path /external_sd". I'm looking for a way to have this automatically preset.
[Android Software Development] NepoRood:
Your Tool Doesn't Work!

Just Kidding :D (I remember that from the "Easy Magic" threads...)

I just wanted to say: You guys do some awesome work, and I'm truly appreciative of the fact that you still keep newbies, like myself, in mind. I've only just begun learning about Android, and 80% of what I now know (which is less than 1% of anything), came from this forum.

This thread about the flags helped me quite a bit to compile (from source) recoveries for my MT8127 tabs, one is flawless, the other I call "Franken'TWRP" (it ain't pretty, but it's functional). If it hadn't been for the tip about using swap_xy and flip_y (although, I had to flip_x) I'd probably be trying to work with this compiler right now.

Thanks Again, and Keep Up the Good Work!

PS, does this program "know" to swap or flip an axis? I'm just curious...
[Android Software Development] yuweng:
Haha, u r most welcome, my friend... :laugh: The reason i stop development on that tool is actually item 3 & 4... And fyi, that swap xy flip y flag was actually found out by a XDA member asking for help at the Compile PhilZ Touch thread then he went missing, i only found out about this flag when i read his previous post & found out he post his finding on his device thread that is full of newbies... i've seen many that post reply i did it, it works now or i found the solution or even edit their post to Never mind, found the answer, i really don't understand why many did that, even RDs do that, they should have post the solution on how they did it, only that would benefit others or as might as well don't reply at all... :rolleyes:

On your FrankenTWRP, Dees_Troy said that the mustard yellow color really wasn't that bad... :laugh:

As mentioned, most of the automation is actually using adb commands to detect what you have on your device, i've taken out quite a few from this script & there is no way to detect whether your device Touch is Flip X or Flip Y or there might be a way but i donno how... :o
[Android Software Development] MSF Jarvis:
[MENTION=4478781]yuweng[/MENTION], I would rather mash my buttons on CWM than have a mustard yellow TWRP
[Android Software Development] yuweng:
When i first built it for my brand new Intel X3 at that time, z31s1g was in the mid of merging the new theme & i thought it was the new color from Materialised Theme on official TWRP for landscape devices, i was using BGRA instead of RGBX... :o Really, it does looks great though... :laugh:

View attachment 3617732

View attachment 3617733

Updates

Want a color changing theme on TWRP3 then try fichl's theme, there is a video review there too... :good:
[Android Software Development] XxDishoxX:
Yuweng and his team are ................ I can't even describe them lol .. :D ... I will definitely try this tool ...

*hiting the thanks button with a very powerful click on the mouse and the mouse has broken*

---------- Post added at 09:34 AM ---------- Previous post was at 09:27 AM ----------

Man!! . you will be written in the history of development .... I'm not kidding .... One day you will see yourself at Wikipedia.
[Android Software Development] NepoRood:
I prefer TWRP because it can back up single partitions, my CWM is all or none (I didn't build it). Ya'll can get a look at Franken'TWRP, here, maybe it'll give you guys a laugh :p

PS, I'd try this program, but the tablet doesn't support ADB
[Android Software Development] yuweng:
Yours is at the right side, the one i've seen is on the top, there is some 5 to 10mm gap, may be you should get in touch with the team here at about 9am onwards... :cowboy: Updates : Now i remember, the Russian did fix it, they did something with the ui.xml then it'll aligned to the end...

Hmm, every Android device should have adb support, did you enable USB debugging or you can bypass it by remark or delete the lines here then key-in those info manually to device_(device-name).mk or omni_(device-name).mk.... :cool:
[Android Software Development] MSF Jarvis:
In your build.prop, look for persist.sys.usb.mode or something like that and it should not have adb in it. Put a comma and add 'adb' to that line. ADB should fire up. Also make sure you have enabled ADB through developer options
[Android Software Development] MSF Jarvis:
There's no team, he's a one man army :P
[Android Software Development] NepoRood:
Thanks for the input, but I tried that already. According to the manufacturer, this tab supports fastboot only, and the micro usb is for charging only. I even changed that in the build.prop, but it still didn't work.

It's not that big a deal, it's a cheap tablet, and I have working recoveries. Building CM seems to be a different story though, lol

Thanks Again
[Android Software Development] NepoRood:
Using the "watch" theme doesn't look near as bad, lol. I'll give editing the xml a shot, crossed my mind, but I know "Jack Snit" about coding, it's all guess work for me (change 1 value at a time, and see what happens :p) And yes, debugging is on, but, if you go to Settings and tap "Storage', then the little 3 dot button (in upper right hand corner) "USB computer connection" is grey'd out :confused:

PS, I did figure out how to put a personal "stamp" on my builds :D
[Android Software Development] NepoRood:
Only 44 Projects to Build TWRP...

I've tried several times with my on "minimal" manifest (I currently like using CM12.1, Omni just doesn't work for me :confused:) and failed.

[MENTION=4478781]yuweng[/MENTION], can you share what those projects would be, or a manifest, for using CM12.1? The full repo I have for CM is geared toward MTK devices, and I just picked up a new tab with an Allwinner A83 chip, and want to build TWRP for it.

Not a lot of room on my laptop for another full repo sync, and like I said, I just don't get along with Omni (no offense to their great work)

In the meantime, I'll keep trying to figure out what those "44 Projects" are :D

Thanks in Advance,

Nepo
[Android Software Development] MSF Jarvis:
[MENTION=7237874]NepoRood[/MENTION] I did hear rumours of [MENTION=5123642]lj50036[/MENTION] having a minimal CM manifest that needed (testing|competition)
[Android Software Development] NepoRood:
Thanks, I'd be happy to test it, as long as it's 12.1, I haven't had any luck with any else, lol. I did find a manifest on GitHub, but, it's for 13

I just cloned and ran the AIO, the "sync.log" file only shows 41 projects :confused:

EDIT:

EDIT2:

I made a manifest based on the AIO sync.log file, you can find it here (this link updated on 4-16-16)
[Android Software Development] yuweng:
My experience is mix for MTK, at one time only CM base repo works, at others times only OmniROM, now that i'm using Intel X3, all base repo works, if it doesn't then you'll have to try other base repo with TWRP older branch... :cowboy: Everything is stated clearly at the script, all you have to do is read it, put a remark here & remove the remark on cm-12.1... :cowboy: Earlier version does build on cm-12.1 but it won't boot, Thanks to Hacker432 for feedbacks, missing one project, now it'll boot & uses only 51 projects... :good: Just change the TARGET_CPU_VARIANT := cortex-a7 for your Allwinner A83 chip & update TWRP flags accordingly then it should boot... :fingers-crossed:

As the saying too many cooks spoil the broth this is especially true for TWRP, its boots today but may not boot tomorrow when new commits is merged bcos it may not be compatible for your device either wait for it to be fixed or contact Teamwin directly but this rarely happens as TWRP is using jenkins, any build error, they are the first one to know... :cowboy:

Haha, there is no competition, one of the reason i didn't share mine earlier is that Part-Source needs constant updating, thats one thing i hate to do... :laugh:

Updates

[MENTION=7237874]NepoRood[/MENTION] Just move your CM .repo to ~/cm & edit the script to use cm-12.1 & it'll work...

mkdir -p ~/cm
mv -rf /path-to-your-existing-cm-folder/.repo ~/cm
[COLOR="blue"]E.g.[/COLOR]
mv -rf /home/NepoRood/android/system/[COLOR="blue"].repo[/COLOR] ~/cm
[Android Software Development] NepoRood:
lol, that's a very close example! No offense to your wonderful tool, but I'm going to continue to give it a go on my own, for now.

I modified my "manifest" to download around 200 projects, way more than I need, for sure, but I don't need anything that's missing ;)

Please note, I will use your tool, before I go without TWRP...
[Android Software Development] NepoRood:
The Road So Far...

Ok, so, building on my own is "failing" :mad:

I decided to use the AIO script, to do a comparison. However, using CM13 or Omni 6 ("partial" for both), I get errors...

Using the "Compile TWRP" option:

Pls select (Y/y or N/n) ? Y

/home/nepo/AIO-TWRP-Compiler/twrp: line 688: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
/home/nepo/AIO-TWRP-Compiler/twrp: line 691: build/envsetup.sh: No such file or directory
/home/nepo/AIO-TWRP-Compiler/twrp: line 692: lunch: command not found
make: *** No rule to make target `recoveryimage'. Stop.

No recovery.img found at ~/cm/out/target/product/X10 !

Scroll back up to see error message or refer to
/home/nepo/Desktop/TWRP/compile.log for more info . . .
[Android Software Development] yuweng:
You are missing a few files, refer to Miscellaneous Tips => Sync corruption, you may have to rm -rf then repo sync a few times & after all corrupted files has been totally removed, re-synced then only all those missing files will be correctly auto-extracted out...

Updates

Use attached updated script...
[Android Software Development] NepoRood:
New script says it's for BBQ Linux only...

I have the ISO for that, so I'm going to install it to 128G usb stick I have, and give it a shot
[Android Software Development] NepoRood:
After talking with [MENTION=4478781]yuweng[/MENTION], I decided to post my current issue here, in case some one else runs across this problem:

My A83 (DragonTouch X10) device just hangs at the boot logo, TWRP won't boot. I'm sure that I'm just missing something, or Allwinner is just as screwed up as MTK, lol

My device tree (Link Removed)

Any help would be appreciated, as I'd really like to get TWRP on it.

Thanks,

Nepo

PS, the AIO script didn't work either...
[Android Software Development] yuweng:
First of all, did you tried... :cool:

2nd - Notice your custom init.rc doesn't have the below...

3rd - Your twrp.fstab is not in the correct formatting compare to this... :cowboy:

Last, i've unpack your device closes sibling, they have a few insmod at the init.rc, may be that the reason it doesn't boot on your build... :cowboy: Try port it over, it should boot on your device... :fingers-crossed:
[Android Software Development] NepoRood:
Following the "steps" above:

1st: Yes, I did, but I was using Carliv's kitchen to unpack/repack (don't know if that matters), but it did boot stock recovery after repacking

2nd: I'd have swore I added that already (again, I blame switching from Ubuntu to BBQ) but, It's been added again

3rd: I'd thought of that before, the reason I didn't change was because of this: When flashing recovery, the path /dev/block/by-name/recovery works just as well as /dev/block/nandf (which is the recovery partition)

Last: I never thought to unpack someone elses image for a comparison :silly:

Conclusion: still doesn't boot, lol I did everything above, one step at a time, doing a build after each step:

Added "Export Path" to init.rc, changed recovery.fstab to "nandX" instead of "by-name", added my insmod files to init.rc

I found another, older TWRP for Allwinner, I'm going to get the AIK (so I don't have to reboot back and forth) and unpack it...

PS, I haven't pushed changes to git yet

EDIT: other recovery was a bust too, no new info :(