yashsingh1/xdaforums huggingface dataset:
[Android Software Development] hawkeyexp:
THX for feedback - tried out but no luck...
[Android Software Development] Epirex:
Hi guys, me again

I tried add new mountpoints for f2fs in the ROM and Kernel but don't work. I have softbrick :(

curiously after of format /data with f2fs, I flash CM11 and my apps were installed O.o like if never had formatted

Is possible that mkfs.f2fs not working? can be the flags are broken?
[Android Software Development] Hikari no Tenshi:
Hi.

I compiled TWRP 2.8.7.0 for Lenovo S650 ROW (mt6582), but reboot buttons "system" & "recovery" don't work. If I try to reboot to system or reboot recovery, phone just shutting down. After manual restart screen goes flickering and I can see a phantom image of twrp under bootlogo, bootanimation and running android system.

How can I fix it?

Thanks in advance.
[Android Software Development] vampirefo:
For reboot to system apply patch from post 631, remove boot to recovery from your from your twrp options.
[Android Software Development] vampirefo:
You need to create the mount point in your init.rc

example

export PATH /sbin:/system/bin
export LD_LIBRARY_PATH .:/sbin:/system/lib
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard

mkdir /boot
mkdir /recovery
mkdir /fastboot
#mkdir /ESP
mkdir /internal_sd
mkdir /external_sd
mkdir /sd-ext
mkdir /datadata
mkdir /system
mkdir /data
mkdir /cache
mkdir /sideload
[Android Software Development] Hikari no Tenshi:
Thanks for reply.

I have removed parameter RECOVERY_SDCARD_ON_DATA := true and now it showing "Data" & "Internal Storage".

Is there any side effect of removing this parameter?
[Android Software Development] vampirefo:
Should be ok.
[Android Software Development] someone755:
I am having the weirdest issues with TWRP right now. I'm using AOSPA-L's lollipop-mr1 branches, and cm-12.1 device trees for the Sony Xperia Z3C.

The ROM builds and works, as does CWM Touch that compiles with it. Replacing bootable/recovery with TWRP gives some errors (e.g. minui/minui.h does not exist), that's why I must clone the TWRP repo to bootable/recovery-twrp (which also means using the "RECOVERY_VARIANT := twrp" flag).

Here's the deal though -- flashing the recovery image next to a custom cm-12.0 kernel (keep in mind the recovery is built from 5.1 branches), it works but it shows as "MultiROM TWRP" (even has a few MultiROM-specific buttons!), despite having cloned the repo from omnirom.

The next weird thing is that when booting the recovery alongside the ROM it was built with (AOSPA-L), it results in a black screen that slightly and slowly but periodically flickers.

I've searched everywhere for similar issues, but nothing of the sorts is documented anywhere. I don't even know how to troubleshoot parts of the issue! Any help would be greatly appreciated!

My device trees' BoardConfigs: z3c (this is also the device tree used for the AOSPA-L build), shinano-common
[Android Software Development] :
That flag helps to properly handle /data/media. Make sure that when you "wipe" or "restore" your data partition that it does not wipe out your "internal storage" should it be fused to /data/media. I would actually be curious if it does not by you removing that flag. I personally took a different approach to play it safe.
[Android Software Development] cognitive:
Hi,

I have already build and bumped twrp 2.8.6.0 for the LG Gk F220k. It runs good on bootloader 4.4.2 but have security error on bootloader 5.0.

Please guide me how to pass this error!
[Android Software Development] Hikari no Tenshi:
Can You tell me how did You managed to fix this properly?
[Android Software Development] :
http://xdaforums.com/showpost.php?p=61577016&postcount=303

See attachments for Device Tree. Look at BoardConfig.mk and twrp.fstab.
[Android Software Development] SdtBarbarossa:
Hello guys,

at the moment im trying to build a recoveryimage for i9305

the size is too large (9 mb) but the partition can only hold 8MB ...what can i do?
[Android Software Development] ladalgigi:
Hello guys

Is there someone here that can build twrp for my device. It's xperia M2 (D2303). I've tried but to be honest, too noob and I don't understand everything so if someone...

Thanks in advance

ladalgigi
[Android Software Development] :
Currently TWRP supports fsflags but using fsflags in twrp.fstab does not work because they are being improperly handled within partition.cpp and partitions.hpp.

An example for twrp.fstab would be:

/internal_sd ext4 /data/media/0 flags=display="Internal Storage";usermrf;backup=1;wipeingui;fsflags="bind"

Then, in the BoardConfig.mk file:

TW_INTERNAL_STORAGE_PATH := "/data/media/0"
TW_INTERNAL_STORAGE_MOUNT := "sdcard"
RECOVERY_SDCARD_ON_DATA := true

﻿

The above should technically allow the TWRP build to wipe, restore, or backup the internal sd located in /data/media/0 without tampering with anything else on the data partition. However, fsflags is being improperly handled and not binded so therefore it is trying to be mounted as if it were it's own block when it is merely a subdirectory.

In partition.cpp at line 409 you will find

:

bool TWPartition::Process_FS_Flags(string& Options, int Flags)

It needs to be changed to:

bool TWPartition::Process_FS_Flags(string Options, int &Flags)

And in partitions.hpp at line 95 you will find

:

bool Process_FS_Flags(string& Options, int Flags);

It needs to be changed to:

bool Process_FS_Flags(string Options, int &Flags);

By making those two simple changes you will find that fsflags are no longer improperly handled and the above example would work perfectly in the twrp.fstab file.

---------- Post added at 12:35 PM ---------- Previous post was at 12:29 PM ----------

I tried explaining this issue to Dees_Troy over on their Google community but he basically acted as if I didnt have a freaking clue what I was talking about so screw it haha. I can maintain TWRP for myself.

---------- Post added at 01:12 PM ---------- Previous post was at 12:35 PM ----------

Optimize the png images and that should shave some off on your size. Their is a commit on gerrit waiting review where all images being used in TWRP are reduced in size by optimizing them to help save space for such cases as yourself.
[Android Software Development] SdtBarbarossa:
thats my commit....still not enought reduction :(
[Android Software Development] :
Oh snap haha. Nice to meet ya lol.

Have you consider this:

https://github.com/kormoc/imgopt/blob/master/imgopt

I wouldn't recommend ImageMagick or GraphicsMagick as it has been know to enlarge their sizes from time to time. They can be a bit touchy if not used just right.
[Android Software Development] SdtBarbarossa:
Thank you will try it!
[Android Software Development] _that:
A Google+ community is not the best place to discuss code changes (and PMs to me here on XDA are neither - I'm not a TWRP maintainer). Sometimes it takes a second attempt to get your point across, especially if your first explanation is not crystal clear. In my answer to your PM I asked to to submit your patch to Gerrit, which for some reason you appear to avoid at all costs.

It's true that TWRP can use and wipe emulated internal storage even without adding it to the fstab (but not backup and restore), and that there is a bug in the Process_FS_Flags code.

Open issues with your patch:

- Should both parameter be references? If not, why?

Open issues with adding internal storage to fstab:

- What happens when a user tries to back up internal storage to itself?

Remember that any code change must not only fix your particular issue but also not cause new problems.

---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------

- Use LZMA or XZ compression for ramdisk and probably kernel.

- Build a smaller kernel by removing stuff from defconfig, e.g. networking or device drivers.
[Android Software Development] :
Will get back to this later on. Babysitting now that the wife has left for work, and it's July 4th :D

Simple, do not do it. There are A LOT of things people can do while in TWRP that could easily wreak havoc. In such cases, this comes down to the maintainer of that device to properly and logically decide what is best suited for that device. As I stated in my PM to you; the MT2-L03 build writes the TWRP backup to the external sd. So, backing up the internal sd wouldn't be an issue in this case. For others, that may be different. Again, it comes down to the maintainer. A mere example.

And to make this clear regarding code, etc etc,

this is XDA

- For developers by developers. So if discussing development work has become officially unsatisfactory here then the priorities and it's original foundation has lost it's way IMHO.

I avoid gerrit because that is another account to keep track of which I don't care to do.
[Android Software Development] :
To make the function work on the actual parameter passed we pass its reference to the function as seen in my changes. So, my answer would be yes.

- Lacking more details. I apologize.
[Android Software Development] Hikari no Tenshi:
Hi all.

Can anyone tell me how to use fstab flag symlink=?

Couldn't find any examples on Google.

Thanks in advance.
[Android Software Development] corphish:
Can anybody tell me the size of the following binaries after you have successfully built a recovery and its working?

out/target/product/<device>/recovery/root/sbin/teamwin
/out/target/product/<device>/recovery/root/twrp

TIA
[Android Software Development] SdtBarbarossa:
it is different depends on resolution and included stuff....

hey corphish for wich device you wanna build? im on i9305 atm
[Android Software Development] corphish:
Old Samsung Galaxy Star, device resolution is 240x320, but I am using 320x480.

And I am trying to compile old TWRP v2.5 on CM10.2 tree (ya its all outdated, but neither my pc has enough power build new ones, nor enough space to store the sources).

In my case, those 2 bins are 1 and 0 byte respectively.

Although, recovery.img is made (10.2MB), when I flash it, stuck at boot logo. :(
[Android Software Development] SdtBarbarossa:
i pm you
[Android Software Development] meta1984:
anybody knows how/can downgrade firmware ? I have 070 installed and need 62b
[Android Software Development] NeoLogY:
Assuming you're using Sony, I think it's better to ask in your device thread. Or in XperiFirm if its Xperia.

This one is for developing TWRP thread.
[Android Software Development] Araca:
make: *** no rule to make Target »/home/arcaca/android/twrp/out/target/product/hwp7/obj/EXECUTABLES/recovery_intermediates/recovery«,
benötigt von »/home/arcaca/android/twrp/out/target/product/hwp7/recovery/root.ts«, zu erstellen. Schluss.

can someone help with this one ?
[Android Software Development] _that:
Post more info... what Android tree (and which version) did you use, what was your lunch command, what was your make command, etc.
[Android Software Development] Araca:
here.

arcaca@arcaca-GE60-0NC-GE60-0ND:~/android/twrp$ lunch omni_hwp7-userdebug

arcaca@arcaca-GE60-0NC-GE60-0ND:~/android/twrp$ time make -j8 recoveryimage

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.4.4

TARGET_PRODUCT=omni_hwp7

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=cortex-a9

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.16.0-43-generic-x86_64-with-Ubuntu-14.04-trusty

HOST_BUILD_TYPE=release

BUILD_ID=KTU84P

OUT_DIR=/home/arcaca/android/twrp/out

====================================

make: *** Keine Regel vorhanden, um das Target »/home/arcaca/android/twrp/out/target/product/hwp7/obj/EXECUTABLES/recovery_intermediates/recovery«,

benötigt von »/home/arcaca/android/twrp/out/target/product/hwp7/recovery/root.ts«, zu erstellen. Schluss.

make: *** Auf noch nicht beendete Prozesse wird gewartet …

host Executable: checkseapp (/home/arcaca/android/twrp/out/host/linux-x86/obj/EXECUTABLES/checkseapp_intermediates/checkseapp)

real	0m36.087s

user	3m17.646s

sys	0m18.414s

using the twrp 4.4.4 tree from github with no changes, also did resync but didn't helped
[Android Software Development] Android-Andi:
device tree? Try "breakfast DEVICE && make clean && make recoveryimage"
[Android Software Development] Araca:
trying now with breakfast

device tree is here

https://github.com/araca/p7_twrp

EDIT:

Same error
[Android Software Development] :
The device tree is built to be used in conjunction with Omnirom. If trying to build against CM you may have errors.

Anyways, assuming you have your Omnirom environment setup properly, open the terminal and change directories to the root of the Omnirom source.

Type and enter:

. build/envsetup.sh

Type and enter:

lunch

Verify that you see, omni_hwp7-userdebug, in the list displayed on your terminal per reference to vendorsetup.sh seen in the Device Tree you shared. If you see it then continue on.

Type and enter:

omni_hwp7-userdebug

Type and enter:

make recoveryimage

Wait until the build is finished should it build successfully. If it fails then refer to your device tree and update it as needed according to the errors which direct back to it.

Also, in your boardconfig.mk file you are using, DEVICE_RESOLUTION. For now it will work, but the new flag is, TW_THEME. The old flag will be officially discontinued in the near future.

See this commit for more information about the new flag.
[Android Software Development] Araca:
ok i had no omni tree but now i have :)

Recovery.img is now building but not booting because of init.recovery.*.rc is missing i think ... i searched in google/xda but i dont' know how to fix this.....

here the log.:

and also thx

Install: /home/arcaca/android/omni/out/target/product/hwp7/recovery/root/sbin/teamwin

----- Making recovery filesystem ------

Copying baseline ramdisk...

Modifying ramdisk contents...

cp: der Aufruf von stat für »/home/arcaca/android/omni/out/target/product/hwp7/root/init.recovery.*.rc“It is not possible : File or directory not found

make: [/home/arcaca/android/omni/out/target/product/hwp7/recovery/root.ts] Fehler 1 (ignoriert)

sed -i 's/ro.build.date.utc=.*/ro.build.date.utc=0/g' /home/arcaca/android/omni/out/target/product/hwp7/recovery/root/default.prop

sed -i 's/ro.adb.secure=1/ro.adb.secure=0/g' /home/arcaca/android/omni/out/target/product/hwp7/recovery/root/default.prop

----- Made recovery filesystem -------- /home/arcaca/android/omni/out/target/product/hwp7/recovery/root

----- Making uncompressed recovery ramdisk ------

/home/arcaca/android/omni/out/host/linux-x86/bin/mkbootfs /home/arcaca/android/omni/out/target/product/hwp7/recovery/root > /home/arcaca/android/omni/out/target/product/hwp7/ramdisk-recovery.cpio

----- Making recovery ramdisk ------

/home/arcaca/android/omni/out/host/linux-x86/bin/minigzip < /home/arcaca/android/omni/out/target/product/hwp7/ramdisk-recovery.cpio > /home/arcaca/android/omni/out/target/product/hwp7/ramdisk-recovery.img

----- Making recovery image ------

/home/arcaca/android/omni/out/target/product/hwp7/recovery.img maxsize=17031168 blocksize=135168 total=13029376 reserve=270336

----- Made recovery image: /home/arcaca/android/omni/out/target/product/hwp7/recovery.img --------
[Android Software Development] :
Device Tree doesn't have that file. You technically do not need it since most of that information used in that file can be found in init.rc. However, should you decide to make it and add some stuff to it then inside the recovery folder create another folder and name it, etc. Put the init.recovery.*.rc file there. Inside the recovery folder you will see Android.mk. Open it up and copy then paste the following at the end of the file. Rebuild.

include $(CLEAR_VARS)
LOCAL_MODULE:= init.recovery.qcom.rc
LOCAL_MODULE_TAGS:= optional eng
LOCAL_MODULE_CLASS:= ETC
LOCAL_SRC_FILES:= etc/init.recovery.qcom.rc
LOCAL_MODULE_PATH:= $(TARGET_ROOT_OUT)
include $(BUILD_PREBUILT)

But just so you know, it isn't always needed. I can make a build using the 5.1 branch with or without it and TWRP will still boot up for me.
[Android Software Development] Araca:
ok :)

i forget to translate this line in english

make: [/home/arcaca/android/omni/out/target/product/hwp7/recovery/root.ts] error 1 (ignore)

has this something to say ?
[Android Software Development] _that:
That means the error was non-critical and has been ignored.

Hint: prefix your make command with "LC_MESSAGES=C " to get readable messages. :)
[Android Software Development] :
Learn something new everyday.
[Android Software Development] jimbomodder:
How can I change rotation from landscape to portrait con T210 running V-2.8.2.0

Sent from my GT-I9195
[Android Software Development] Android-Andi:
It's not possible to change from landscape to portrait.

I asked the same question when i started compiling for Tab 2, but a kernel dev told this would need a big change in kernel source to use portrait ui.

Idk if a landscape theme can be adjusted to emulate a portrait ui - maybe that's the point where you can start playing around since you can use a ui.zip to overlay the included default theme.
[Android Software Development] jimbomodder:
Dam, well thanks for info

Sent from my GT-I9195
[Android Software Development] Araca:
thx all i have managet to boot in to twrp :)

i had to change my init.rc because the old one was from 4.4.4

but now i have 3 Bugs and hope someone can help me again with this...

because i'm new to this and do not know where to start..

1 . twrp does not show any partion ( it says invalid block but fstab is right?)

2. twrp has orange colour? instead of blue

3. theme is not loading (because of bug 1?)

DEVICE TREE

thx in advance
[Android Software Development] :
Recovery log would help with issue number one.

As for issue number two, look at BoardConfig.mk for:

TARGET_RECOVERY_PIXEL_FORMAT := "RGB_8888"

The above may need to be changed if your device shows it as orange.
[Android Software Development] Phatboyj420:
[MENTION=912474]Dees_Troy[/MENTION]

I'm currently researching so as to bring TWRP to the AT&T Galaxy S4 ZOOM C105a

As it sits there is only Root available for said device HERE

The " S4 C-105a " runs via a " 4212 dual core Exynos chip " and has an " LTE Radio "

Its running stock on 4.2.2 but is upgradeable via AT&T OTA Only to 4.4.2 I do not yet know if it can be upgraded and retain or re-obtain ROOT.

There is Zero factory firmware availability either through AT&T or Samsung Except through OTA

However from my 16-GB C-105a I have made a full dd Dump of the entire mmcblk0, as well as all the device partitions dumped separately for the Factory Stock 4.2.2 AUCUAMJ2 firmware " Rooted obviously "

I currently have 2 of these devices, one for use, and 1 to dev on if necessary.

Right now this is definitely above my ability but I am more than motivated to learn all that is necessary

to bring this to fruition " unless you might know someone better suited to take this on? "

Question 1-of many but to start

1. Is this even possible for said device?

2. will the possibility of running twrp on said device after updating to 4.4.2 or not be impeded by a locked bootloader or would the bootloader have to be unlocked whether it be 4.2.2 or 4.4.2?

3. as there is probably no source in the tree for said device what device if any could be used to obtain the vendorsetup.sh?

4. " some what the same ? as #3 ", but how do I go about figuring out what device would be best to emulate for the flag settings for the .boardconfig.mk file?

5. Will you, or anyone else knowledgeable on the subject, please assist me in any way that you feel might help me to get the ball rolling for the S4 ZOOM C-105a

Also anyone willing to collaborate please hit me up there is a similar call-out in my sig. below

As far as the lunch thing goes

" I personally prefer Breakfast LOL. "

Thanks in advance,

and GOD BLESS

YOU, XDA, and TWRP,

Phatboyj

...... ......
[Android Software Development] Lrs121:
If you want twrp youll need either an unlocked bootloader or a way to bypass the lock on the bootloader.

you can restore to stock using kies. you can also capture the stock file from the temp folder when doing the restore and can also go through the process just go get the stock file and cancel the process before its written to your phone.
[Android Software Development] :
Hey guys, so I have a device resolution of 480x800 (widthxheight). For the TW_THEME flag in BoardConfig.mk I use portrait_hdpi. Now, I know that flag is for 1080x1920 so know need to inform me of this.

The issue is found with portrait_mdpi, for 480x800. The ui.xml is jacked up and when I boot TWRP the images as well as the text contents are all over the screen overlapping one another. With portrait_hdpi TWRP looks great after being automatically scaled. I decided to diff both ui.xml files for both resolutions and that is when I noticed that for portrait_mdpi it is missing some stuff.

To verify, I ported the ui.xml from 1080x1920 over to 480x800 and TWRP worked like a charm.

Anyone else experiencing this issue for portrait_mdpi or has my repo gone crazy hahaha? [MENTION=4878287]_that[/MENTION], [MENTION=912474]Dees_Troy[/MENTION], have any of you maybe noticed this?
[Android Software Development] Phatboyj420:
Thanks, but there is No Kies firmware for the C-105a, but you might be right in one respect.

I may be able to snag the OTA update before the flash process. Honestly though that is the least of my concerns. I was basically just sharing info about the availability, or lack there of for the stock firmware.

Does anyone know of a similar device running the exynos 4212 with the bootloader reach-around /unlock/workaround

Although in its current state, running " 4.2.2 JB " I'm not convinced that the bootloader is locked

but, I am quite sure that if i were to take the OTA of kitkat 4.4.2

So if I'm not mistaken as long as I retain the JB 4.2.2 BL. I should be OK Right?
[Android Software Development] gcappa:
Hi There, can someone help me compile TWRP for the Samsung Note 4 Duos SM-N9100... with stock firmware N9100ZHU1BOF2 touchwiz lollipop 5.01

I have the recovery .img file that will work, but don't know how to compile a flashable tar file.
[Android Software Development] yuweng:
Long time ago i help a fellow XDA friend thats where i discover BOARD_HAS_FLIPPED_SCREEN, total 16 combinations, one of them should work on your device but i donno how it will work out on the latest as now it uses scaling... :cowboy:

BOARD_HAS_FLIPPED_SCREEN
RECOVERY_TOUCHSCREEN_SWAP_XY
RECOVERY_TOUCHSCREEN_FLIP_X
RECOVERY_TOUCHSCREEN_FLIP_Y

Not long ago, a XDA member feedback that he is able to use ui.zip made with SHM AKA ModdingMyMind's tool but you gotta trial & error it yourself... :laugh:

Yeoh Master Shifu SHM, same thing here, everything overlapping, Master Shifu Dees_Troy must've accidentally deleted that line, more info here... :p Its harder to test nowadays, previously i can test all lower resolutions on my 480x854 devices then one day got nothing else better to do, i built it for my old armv6 320x480 device...

You can check with below command... :cowboy:

adb reboot-bootloader [COLOR="blue"]or[/COLOR] adb reboot bootloader [COLOR="blue"]or[/COLOR] adb reboot fastboot
fastboot getvar all

(bootloader) unlocked: NO
[Android Software Development] Phatboyj420:
You can check with below command... :cowboy:

adb reboot-bootloader [COLOR="blue"]or[/COLOR] adb reboot bootloader [COLOR="blue"]or[/COLOR] adb reboot fastboot
fastboot getvar all

(bootloader) unlocked: NO

Thanks I'll Definately give this a run later today

For now, just for the sake of argument, let's say it is locked what would be the next logical step?

To port safestrap?

Thanks in advance,

Phatboyj
[Android Software Development] yuweng:
For most Android devices, its fastboot oem unlock but its best that you do some research first, what can be done on yours, every Android device is unique... :cowboy: