yashsingh1/xdaforums huggingface dataset:
[Advantage X7500, MDA Ameo ROM Development] LTxda:
Guys talk to me tomorrow. It's all good.
[Advantage X7500, MDA Ameo ROM Development] Johnston411:
Nice job

Nice work midget.

Looking forward to having a go at the kitchen.
[Advantage X7500, MDA Ameo ROM Development] wgary:
Oh pulleeze. Let's have some drama -- It was my idea, oh no you dident, it's mines all mine -- Like I don't get enuff o' this shipe at work. :)
[Advantage X7500, MDA Ameo ROM Development] fards:
handbags at dawn..

Please ladies don't smudge your mascara..
[Advantage X7500, MDA Ameo ROM Development] lpsi2000:
I thought this build was 5.2.1908?
[Advantage X7500, MDA Ameo ROM Development] spacecat:
ITS ALONSO and HAMILTON at TEAM ATHENA !

PK the young upstart rookie in his first season leading the championship

Midget the reigning world champ fighting back

great stuff :)
[Advantage X7500, MDA Ameo ROM Development] lpsi2000:
@Midget and PK,

Have you guys seen this new discovery?

http://xdaforums.com/showthread.php?t=331094

@Midget,

It would be nice to incorporate this in your kitchen. When would you release the kitchen and this ROM?
[Advantage X7500, MDA Ameo ROM Development] LTxda:
Um no, not a competition. Sorry chap.
[Advantage X7500, MDA Ameo ROM Development] Olipro:
I agree, not to mention that Alonso's a dickwad.
[Advantage X7500, MDA Ameo ROM Development] spacecat:
err.......joke guys :(
[Advantage X7500, MDA Ameo ROM Development] Midget_1990:
yes i ahve been using it, very useful, but no need for it to be in a kitchen as it re-locates modules and as of yet we cannot create modules and the ones there would be already relocated by me :D

is that meaning me or the real one ;)
[Advantage X7500, MDA Ameo ROM Development] Olipro:
the real one, you're not a dickwad.

you're a cockbag :P
[Advantage X7500, MDA Ameo ROM Development] toyfreak:
So True...

Off topic, but I do not care for Alonso, either... Hamilton is a breath of fresh air and F1 needed it. Too bad about our boy Scott Speed, though... I would have liked to see him in a more competitive ride.
[Advantage X7500, MDA Ameo ROM Development] beginner:
come on, I never imagine in xda this comments. If this is the sense we are losing the way of this web.

that's comparative is not very good. too much influence from manipulated press do people be on the side publicity is interested. should be possible to deal if everything at your home is manipulated???

I expect don¡t have to move to other forum, put your energy in other way, is more intelligent -sorry my english, non british-
[Android Software Development] MSF Jarvis:
Thanks sir for the suggestions. I can see I've included the descriptions for most of them already, but I'll be sure to attribute to and add the rest tomorrow. I would be grateful if you could shed some light on the ones I've marked "NEED HELP"
[Android Software Development] Android-Andi:
I've done those stuff offline from your gist[emoji14]have seen this thread after that but maybe you like the way i showed the defines as it's setup the way you would do in your BoardConfig.mk.

Haven't done those flags i am not sure about myself, maybe [MENTION=4878287]_that[/MENTION] or [MENTION=912474]Dees_Troy[/MENTION] can bring light to some of them.

Gesendet von meinem LG-H815 mit Tapatalk
[Android Software Development] bigsupersquid:
This thread is a great idea.

Especially with the update to twrp 3.0 with new flags.

I've been lucky enough to be able to guess/puzzle out/grab from other device trees enough to build and use the recovery on my personal devices, but information like this is very helpful to have consolidated.

Thanks for sharing.
[Android Software Development] MSF Jarvis:
Yeah, I just didn't have enough time to beautify it. Will gradually do so.
[Android Software Development] SdtBarbarossa:
TW_CUSTOM_THEME := /path/to/theme/

this one is used to replace the stocktheme with a different one (like material-play)

the theme will be directly in ramdisk

TW_INCLUDE_INJECTTWRP := true — adds ability to inject TWRP into some Samsung boot images for Samsung devices that have recovery as a second ramdisk in the boot image

the second flag is quotes by dees_troy!

TW_NEW_ION_HEAP

this has sonething to do with 3.10 kernels and a different naming in /include/linux/ion.h ... like a switch between old heap_mask and new heap_id_mask
[Android Software Development] aicjofs:
Nice initiative with this thread, this has been oh say 2 years too long in the making haha.

TARGET_RECOVERY_FORCE_PIXEL_FORMAT

Not sure but I would imagine it overrides what TWRP detects nor do I see the difference between it and TARGET_RECOVERY_PIXEL_FORMAT. The only possible varible right now is RGB_565. BGRA_8888, RGBA_8888 and RGBX_8888 are not yet implemented.

TW_INPUT_BLACKLIST

Black list input devices that interfere with touch. For multiple input devices the delimiter is \x0a. You would basically build a special TWRP with TWRP_EVENT_LOGGING := true. Put it on the device and read the more verbose log to see what inputs you want to blacklist.

EDIT: Ah here is a copy of the wording I had in one of my xda posts about the subject and the commit link https://github.com/omnirom/android_bootable_recovery/commit/5742a40b87dfdc26df3bd9fe94197ae414ece546

and here is an example from my BoardConfig

TW_INPUT_BLACKLIST := "accelerometer\x0admard06\x0alis3dh_acc\x0alis3de_acc"

On a side note is there a link somewhere to fixing graphics issues induced in 3.0? I see a lot of talk about it but nothing substantial.
[Android Software Development] MSF Jarvis:
Not really. Slanty graphics can be fixed with linelength, but as such there's nothing on that front. You might wanna slap a recovery.log onto Dees_Troy at #twrp on webchat.freenode.net though.
[Android Software Development] yuweng:
Every version has new flags introduced & also flags deprecated...

TARGET_USES_LOGD => Source

TW_SCREEN_BLANK_ON_BOOT ( Deprecated on android-6.0 => Source, on some legacy devices, TWRP will not boot without this flag)

Use the_silver_searcher, its extremely fast ! :good:

cd ~/cm/bootable
ag -ia "[URL="https://gerrit.omnirom.org/#/c/16610/"]TW_INCLUDE_JPEG[/URL]" recovery/
recovery/minuitwrp/resources.cpp
34:#ifdef TW_INCLUDE_JPEG
256:#ifdef TW_INCLUDE_JPEG
361:#ifdef TW_INCLUDE_JPEG
367:#ifdef TW_INCLUDE_JPEG

recovery/minuitwrp/Android.mk
61:ifneq ($(TW_INCLUDE_JPEG),)
64: LOCAL_CFLAGS += -DTW_INCLUDE_JPEG
176:ifneq ($(TW_INCLUDE_JPEG),)

recovery/prebuilt/Android.mk
126:ifneq ($(TW_INCLUDE_JPEG),)

ag -ia "[COLOR="Blue"]TW_FLASH_FROM_STORAGE[/COLOR]" recovery/
recovery/Android.mk
262:#ifeq ($(TW_FLASH_FROM_STORAGE), true) [COLOR="Blue"]Making this the default behavior[/COLOR]
263: LOCAL_CFLAGS += -DTW_FLASH_FROM_STORAGE

As the code says, its already the default therefore you don't need to specify it again on BoardConfig.mk

ag -ia "[URL="https://gerrit.omnirom.org/#/c/14099/"]TW_INCLUDE_NTFS_3G[/URL]" recovery/
recovery/Android.mk
440:ifeq ($(TW_INCLUDE_NTFS_3G),true)

recovery/prebuilt/Android.mk
201:ifeq ($(TW_INCLUDE_NTFS_3G),true)

At the omnirom gerrit, you'll find all commits though you gotta search for it or try this or this for TWRP related

ag -ia "[COLOR="blue"]TW_BOARD_CUSTOM_GRAPHICS[/COLOR]" recovery/
recovery/minuitwrp/Android.mk
14:ifneq ($(TW_BOARD_CUSTOM_GRAPHICS),)
16: $(warning * TW_BOARD_CUSTOM_GRAPHICS support has been deprecated in TWRP. *)

ag -ia "[COLOR="Blue"]TW_DISABLE_TTF[/COLOR]" recovery/
recovery/minuitwrp/Android.mk
165:ifeq ($(TW_DISABLE_TTF), true)
167: $(warning * TW_DISABLE_TTF support has been deprecated in TWRP. *)

recovery/prebuilt/Android.mk
192:ifneq ($(TW_DISABLE_TTF), true)

BOARD_SUPPRESS_SECURE_ERASE := true
BOARD_SUPPRESS_EMMC_WIPE := true

Source, further explanation here

__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixr!

Fix tzdata on recovery.log => Source
[Android Software Development] MSF Jarvis:
[MENTION=4478781]yuweng[/MENTION] the script has really been thought over for a long time and you also have put in tons of work in it. Thanks for it man!
[Android Software Development] yuweng:
Thanks bro... :highfive: The script initially includes BE setup for Ubuntu that includes setting up of Python, Java, Make, Git, build packages, adb rules & etc, now its half the size bcos we don't need to do all that on BBQLinux... :cowboy: It has went thru alot of revision, i lost track, one has PhilZ Touch on it, one revision will detect the device info such as graphics resolution, emmc or /data/media device & etc, you can actually do wonders with adb shell, automated alot of stuff for BoardConfig.mk, all in all, this script has about 4 years of work in it... :cool:
[Android Software Development] MSF Jarvis:
4 YEARS!!!! [MENTION=912474]Dees_Troy[/MENTION], [MENTION=2638973]bigbiff[/MENTION], [MENTION=4878287]_that[/MENTION] this guy deserves a medal! And about the BE Setup, my good friend [MENTION=4869275]thewisenerd[/MENTION] had made an Android compiler which included a rather fancy dependencies check in a python program. I'll include it into AIO-TWRP-COMPILER as soon as I finish my school work for the week :cowboy:
[Android Software Development] yuweng:
Haha, they are all my Master Shifu's & they all have more experience than me on TWRP... :laugh: You are most welcome to add-in new features to it... :good:
[Android Software Development] MSF Jarvis:
Experience?? They're encyclopedias on TWRP. But it's worthless if every humbug on the planet wants to compile it and doesn't even know what "ls -R " is supposed to do :p You're being a great help to everyone. I'll try and get them to try this when I can make it compatible for people who have already downloaded the source :cowboy:
[Android Software Development] yuweng:
Actually its quite easy but then again any wrong BE setup will result in build error that's why i strongly recommends BBQLinux for starters, its as easy as Ubuntu to setup, i can guarantee many will like the UI, Thanks to RD codeworkx.... :good:

mkdir ~/omni
cp -[COLOR="Blue"]R[/COLOR]f /path-to-your-existing-omnirom-folder/.repo ~/omni
[COLOR="blue"]OR[/COLOR]
mkdir ~/cm
cp -[COLOR="blue"]R[/COLOR]f /path-to-your-existing-cm-folder/.repo ~/cm

Remark or delete these lines & it'll work... :cowboy:

Updates - Migrating source code .repo to BBQLinux

So far my experience is that only lrzip is able to compress & extract source code .repo folder without data corruption... :good: Just open Ubuntu Nautilus File Manager & delete everything on your cm or omnirom except the hidden folder .repo

This hidden .repo folder is where the actual source code are, zipping it will be enough for migration, a repo init & repo sync will have all the files extracted out on BBQLinux ... :cool:

sudo apt-get install lrzip
cd /path-to-your-existing-[COLOR="Blue"]omnirom[/COLOR]-or-[COLOR="blue"]cm[/COLOR]-folder
lrztar -l .repo [COLOR="Blue"]<= Will take 10 to 20 minutes depending on your PC CPU, RAM & HDD[/COLOR]
[COLOR="blue"][U]To unzip it[/U][/COLOR]
copy [COLOR="Blue"].repo.tar.lrz[/COLOR] to [COLOR="Blue"]~/omni[/COLOR] or [COLOR="blue"]~/cm[/COLOR] folder accordingly
cd [COLOR="Blue"]~/omni[/COLOR] or [COLOR="blue"]~/cm[/COLOR]
lrzuntar .repo.tar.lrz
[Android Software Development] Hacker432:
I don't know what it does but I compiled twrp(2.8.7.0 because twrp 3 doesn't want to work with my phone)In one month of work xD

I use Ubuntu and I had several issues

Luckily I can compile without problems now

Thanks for your work

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] MSF Jarvis:
AIO TWRP Compiler wiki

[MENTION=4478781]yuweng[/MENTION], I have started writing down the wiki for this script at the Github repository. Would be grateful if you started writing the things you have mentioned here in that as well, and I'll proof-read it later on and also keep writing things myself :cowboy:
[Android Software Development] MSF Jarvis:
Interesting...... I'll have a look at it in a couple of days and let you know if I manage to fix that issue.
[Android Software Development] Android-Andi:
Use build prop override if needed. I had same problem on unified tab2 tree, espresso-common didn't worked, i now use build prop override to get it work

https://github.com/andi34/device_samsung_espresso-common/blob/twrp/omni_espressocommon.mk#L37

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] Van.Fanel:
I'm using CM source. Can you guide me how to do it?
[Android Software Development] MSF Jarvis:
Just add that line and the one below it to your BoardConfig
[Android Software Development] Android-Andi:
espresso-common didn't worked so i changed it to espressocommon (breakfast won't fail now)

https://github.com/andi34/device_samsung_espresso-common/blob/twrp/omni_espressocommon.mk#L30

To display espresso-common in the end i added

https://github.com/andi34/device_samsung_espresso-common/blob/twrp/omni_espressocommon.mk#L30

You only need to adapt it.

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] zainifame:
My device doesn't have external storage it's nonremoveable memori, but have usb otg support

This flag :

TW_INTERNAL_STORAGE_PATH

TW_INTERNAL_STORAGE_MOUNT_POINT

TW_EXTERNAL_STORAGE_PATH

TW_EXTERNAL_STORAGE_MOUNT_POINT

How do i set that flag on my boardconfig.mk sir?
[Android Software Development] Van.Fanel:
I checked my device_lion5.mk and found out that there's an override line included already:

$(call inherit-product, build/target/product/full_base_telephony.mk)

# Time Zone data Credits to desalesouche => http://xdaforums.com/showpost.php?p=64850444&postcount=1204
#PRODUCT_COPY_FILES += \
#bionic/libc/zoneinfo/tzdata:recovery/root/system/usr/share/zoneinfo/tzdata

PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_MODEL="Alcatel_7049D" \
TARGET_DEVICE="Lion-5"

PRODUCT_NAME := full_lion5
PRODUCT_DEVICE := lion5

So it looks like that that takes care of it, huh?
[Android Software Development] NepoRood:
Those flags are self explanatory... But:

A = path/to/your/sdcard

B = mount/point/of/your/sdcard

Not Needed = Well, Not Needed

(since you have no external sd)
[Android Software Development] MSF Jarvis:
These flags have been deprecated since TWRP 3.0.2-0, I cannot edit my post thru XDA Labs, so haven't been able to remove it.

To add USB-OTG support you just need to add it to your twrp.fstab and TWRP will automatically pick it up. Might as well also specify flags=removable to suppress mounting errors when no USB is connected.
[Android Software Development] zainifame:
[MENTION=7237874]NepoRood[/MENTION], [MENTION=6552280]MSF Jarvis[/MENTION]

Thanks :D will try it soon
[Android Software Development] kirito9:
Necesito ayuda! I would like some assistance please :)

I'm working on a new device to built a TWRP recovery but I'm getting some problems and I've tried multiple tweaks. The device is an Alcatel Pixi Eclipse (A462C). I've searched everywhere on the internet trying to find any information on it but I'm just not finding anything.

It's supposedly a Qualcomm device with similar specs to the Alcatel Pixi 3 (4). I got that information from [MENTION=7559379]ReconZero[/MENTION] who I decided to assist in building the recovery.

His initial device tree was able to build the recovery but couldn't flash it? Not really sure, he didn't specify. I tried unpacking it with AIK by osm0sis but I got ramdisk is not in gzip format. Couldn't unpack with [MENTION=5186178]bluefirebird[/MENTION]'s (carliv) kitchen either.

The stock boot.img unpacks and repacks fine with carliv and osm0sis tools but to get it working in recovery build is baffling me.

The error that I'm getting is on pastebin. I tried using osm0sis and carliv scripts to build but always get that error. It's mainly in the (error: could not load device tree image '/cm12/device/alcatel/a462c/dt.img) I believe.

I wanted to try as many things as possible before asking for help but.....noob status still :)

My forked device tree is here btw : https://github.com/kirito96/android_device_alcatel_a462c

If I wasn't clear on anything above, please let me know so that I can update. Thanks

Regards,

kirito9
[Android Software Development] MSF Jarvis:
I sent a PR, which should fix the dt.img not found error, though I'm still wondering why does a QCOM device even need MTK headers....
[Android Software Development] kirito9:
Thanks, I'll build when I get back home. Tracfone probably? Lol not sure why it needs the MTK headers.
[Android Software Development] MSF Jarvis:
Sorry my bad, no MTK headers in there, I got confused a bit, the device tree should be cool now :)
[Android Software Development] Van.Fanel:
Here to bother everyone again. :D

I am trying to compile TWRP for someone else's device and I'm using [MENTION=4478781]yuweng[/MENTION]'s AIO again. I don't have the phone with me--just the stock recovery, boot and build.prop.

Is there any way to get past this step of the script:

Pls plug-in your Android device USB to the PC now
[Android Software Development] MSF Jarvis:
Not as of now. The script needs a major rework, I just haven't been able to find the time for it. You would be better off cloning https://GitHub.com/lj50036/android_device_vendor_codename and filling it up with the info you have from the device.
[Android Software Development] kirito9:
None there? So you were able to compile after your modification to the BoardConfig.mk? What source are you using btw.

EDIT: I was able to build successfully, time to test. Thanks :)
[Android Software Development] :
Are you sure it needs the mtk header? If the BoardConfig is right then this it is a qualcomm device and the mtk header is out of place.

BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=[COLOR="Red"]qcom[/COLOR]...

Also I never saw a mtk device with dt.img.

My advice: get rid of mtk stuffs for this device and use a qcomm device tree as template to fix build.
[Android Software Development] kirito9:
Yeah well I was out of options :laugh: I didn't know what was causing the recovery to not build so I realized that your kitchen could unpack the stock boot.img so I went to my old device tree where you said you updated perl scripts to that of your kitchen.

I'll remove all mtk stuff and do a normal build and see.

P.S I was able to build tho after merging [MENTION=6552280]MSF Jarvis[/MENTION]'s pull request.
[Android Software Development] MSF Jarvis:
Yeah, that error was ridiculously apparent :D if you want [MENTION=5123642]lj50036[/MENTION] (with some help from me ;)) created a TWRP device tree template. Hit me up on Hangouts and we may give that a shot on my server (just synced sources)
[Android Software Development] kirito9:
Sure, I won't mind :D
[Android Software Development] bbudh:
Hello,

Please help me, I got problem here.

First I had Lenovo A526 phone stuck in first logo. I used Sp Flash Tools & Stock Rom to fix, after all done the popup said Download OK but after restart it still stuck in logo. Later I've used ADB & TWRP recovery to install a custom rom, the message on phone said Installation Done ! Please Reboot ! Successful.

But at the end of line of installation, it's written:

E:Unable to mount '/cache'

E:Unable to mount '/data'

E:Unable to mount '/system'

Then I reboot and it still hang in logo

Please how to fix this? Thank you for your help.
[Android Software Development] MSF Jarvis:
First up, this is completely the wrong place for this. Secondly, I don't see your device officially supported, and I cannot provide help for unofficial builds.
[Android Software Development] mustang_ssc:
Hi. The scripts doesn't work for me, it says "internet status:down".

I have tried all the suggestions mentioned here but no one worked.
[Android Software Development] Tricobalt:
Are these scripts usable for compiling twrp for qualcomm chipsets?
[Android Software Development] MSF Jarvis:
They should be, but I haven't really tried.
[Android Software Development] ji5ji:
Hi to everybody.

Thank you very much for the information that I found. I managed to compile functional TWRP for Honor 6. I want to back up only the data without internal storage. How to exclude

data/media

from the backup? Which

flags

do I use? Here I could not find it. I tried to use the flag "

RECOVERY_SDCARD_ON_DATA := false

", but it did not work. Here attach your

BoardConfig.mk.

LOCAL_PATH := device/huawei/mogolia

# Assert
# TARGET_OTA_ASSERT_DEVICE :=

# Platform
TARGET_BOARD_PLATFORM := hi3630

# Bootloader
TARGET_NO_BOOTLOADER := true

# Architecture
TARGET_ARCH := arm
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := generic

TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := H60

# Kernel
BOARD_KERNEL_BASE := 0x00600000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_KERNEL_CMDLINE := vmalloc=384M coherent_pool=512K mem=2044m@0x200000 psci=enable mmcparts=mmcblk0:p1(vrl),p2(vrl_backup),p7(modemnvm_factory),p18(splash),p22(dfx),p23(modemnvm_backup),p24(modemnvm_img),p25(modemnvm_system),p26(modem),p27(modem_dsp),p28(modem_om),p29(modemnvm_update),p31(3rdmodem),p32(3rdmodemnvm),p33(3rdmodemnvmbkp) user_debug=7 androidboot.selinux=permissive enter_recovery=1 enter_erecovery=0
BOARD_MKBOOTIMG_ARGS := --kernel_offset 0x00008000 --ramdisk_offset 0x03a00000 --tags_offset 0xffc00000
TARGET_PREBUILT_KERNEL := device/huawei/mogolia/recovery/kernel

# Partitions
BOARD_HAS_LARGE_FILESYSTEM := true
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_BOOTIMAGE_PARTITION_SIZE := 14680064
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 15728640
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1610612736
BOARD_USERDATAIMAGE_PARTITION_SIZE := 12635340800
BOARD_FLASH_BLOCK_SIZE := 4096

# TWRP
RECOVERY_VARIANT := twrp
TARGET_RECOVERY_FSTAB := $(LOCAL_PATH)/recovery/root/etc/twrp.fstab
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TWHAVE_SELINUX := true
TW_BRIGHTNESS_PATH := "/sys/devices/platform/hisi_fb.1048577/leds/lcd_backlight0/brightness"
TW_CUSTOM_BATTERY_PATH := "/sys/devices/fff34000.pmic/battery.90/power_supply/Battery"
TW_MAX_BRIGHTNESS := 255
BOARD_HAS_NO_SELECT_BUTTON := true
TW_SCREEN_BLANK_ON_BOOT := true
TW_EXCLUDE_SUPERSU := false

Thanks.
[Android Software Development] MSF Jarvis:
[MENTION=6491141]ji5ji[/MENTION] /data/media is never backed up by TWRP. And you have exclude the flag for SuperSU, default is false only so your flag doesn't really do much.
[Android Software Development] ji5ji:
Thanks.

Hmm, that's strange, because my TWRP backup "data / media" together with the data. I have a very simple device tree and can not figure out why this is so. :(

Here's my tree.

EDIT: It's basically the same finished tree that created

paulobrien

. I just wanted to create TWRP that backs only data and automated root.

Github - "TWRP-mogolia by paulobrien"
[Android Software Development] MSF Jarvis:
Sorry, but I refuse to read code off Google drive.
[Android Software Development] ji5ji:
Sure I understand. This code is essentially the same. https://github.com/TeamWin/android_device_huawei_mogolia?files=1

You would have helped me by. Thanks.
[Android Software Development] MSF Jarvis:
"Essentially the same" doesn't really help things. If it's same, why'd you have the code on Google Drive?
[Android Software Development] ji5ji:
Well where do I put it? On GitHub, when is code clone from paulobrien? I tried to do Twrp from scratch, but AIO compiler does not work for me. Displays the "internet status down" and even though I have manually synchronized repo, not see recovery.img in folder AIO-TWRP-Compiler. I'm more of a layman and I just wanted to understand the principle of how to build from source, edit TWRP own needs and so on.

EDIT: AIO compiler already working when I deleted everything in the folder "

AIO-TWRP-Compiler

":good:.
[Android Software Development] Sudarshankakoty:
What about spreadtrum devices ?
[Android Software Development] Matt07211:
Can you clarify this question a bit more. It's rather vague.

And hey, I'm seeing you everywhere at the moment. I admire your persistence at getting a custom Rom for your device working.