yashsingh1/xdaforums huggingface dataset:
[Android Software Development] DevUt:
New Error :

Install: /home/devut/a/android/system/out/target/product/endeavoru/recovery/root/sbin/recovery
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
+/home/devut/a/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=9017344 reserve=88704
error: +/home/devut/a/android/system/out/target/product/endeavoru/recovery.img too large (9017344 > [8650752 - 88704])
make: *** [/home/devut/a/android/system/out/target/product/endeavoru/recovery.img] Error 1
make: *** Deleting file `/home/devut/a/android/system/out/target/product/endeavoru/recovery.img'
[Android Software Development] MSF Jarvis:
Your recovery partition is a bit small then. You'll need to check what all compression methods does your kernel support and then cherry-pick the suitable change from a repo like my official TWRP device tree : https://GitHub.com/TeamWin/android_device_htc_pico
[Android Software Development] DevUt:
need a little more HOW-TO as im new to all this

---------- Post added at 09:42 AM ---------- Previous post was at 09:33 AM ----------

would this do?

https://github.com/teemodk/android_...mmit/f6c5e90227ee19509358181051104f1c1f04e301
[Android Software Development] MSF Jarvis:
If this is the device you're building for, then you just need to cherry-pick this change : https://github.com/TeamWin/android_device_htc_pico/commit/611e674bb398bf4e212671c7d523f9837be36efc

Into your device tree, making suitable adjustments. And make sure to use the same kernel source you linked me to, because it has LZMA support baked in already.
[Android Software Development] DevUt:
i making HTC ONEX X endeavoru
[Android Software Development] MSF Jarvis:
Bingo. Just pick the commit and lunch with -eng rather than -userdebug(idiotic for TWRP build, honestly) and then mka recoveryimage. It should not throw this error now. Maybe a make clean before this won't hurt too :)
[Android Software Development] DevUt:
I have developed a habit of make clean

And I have made this commit https://github.com/DevUt/android_ke...mmit/6d7eeda001e1b2ed67f729514a1a688018a0be4e

---------- Post added at 10:26 AM ---------- Previous post was at 10:02 AM ----------

build/core/tasks/kernel.mk:282: warning: overriding commands for target `/home/devut/a/android/system/out/target/product/endeavoru/kernel'
build/core/Makefile:46: warning: ignoring old commands for target `/home/devut/a/android/system/out/target/product/endeavoru/kernel'
make: *** No rule to make target `/customrecoveryimg.mk'. Stop.
[Android Software Development] MSF Jarvis:
Has to be an issue with the paths. Lemme check and get back to you in just a minute. Would be helpful if you could upload your device tree with the commit i told merged and throw me a link.
[Android Software Development] DevUt:
I manually copied the commit

Including the BoardConfig

Including the customrecovery.mk

And also did this :

make clean
lunch cm_endeavoru-eng
mka -j5 recovery image
[Android Software Development] MSF Jarvis:
Link to device tree please
[Android Software Development] DevUt:
https://github.com/DevUt/android_device_htc_endeavoru?files=1
[Android Software Development] Android-Andi:
Typo

customrecoveryimg.mk (in BoardConfig)

Vs

customrecoveryimage.mk (Filename)

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] DevUt:
Check again I actually added this commit from my phone me original work is in PC and everything is fine in that

In using a compressed source of cm 13 by Digi Goon

I have just copied my device tree from git and then added it to device then made changes in it
[Android Software Development] Android-Andi:
Looks fine now

~ All my work, news etc. on http://andi34.github.io ~
[Android Software Development] MSF Jarvis:
Ahh, now I remember, [MENTION=5158920]kirmaniarslan[/MENTION] missed this typo, I cherry-picked it and missed it too. Dees_Troy fixed this one on the TWRP Jenkins but I guess it never got pushed to GitHub.
[Android Software Development] DevUt:
[MENTION=6552280]MSF Jarvis[/MENTION] I think I would open a errors thread soon in which I will add all the errors I encountered and I how I solved it would you also like to take part in it ?
[Android Software Development] MSF Jarvis:
Most definitely I will. Isnt that why there's a thread for TWRP Flags? (I made and maintain it, ofc)
[Android Software Development] DevUt:
Not just twrp from repo sync to that out dir
[Android Software Development] MSF Jarvis:
Go ahead, mention me when you need help. I'll reserve a couple of posts to put in my stuff too ;)
[Android Software Development] DevUt:
I would do it tomorrow in some where 12 /1/2/3 pm Indian time
[Android Software Development] MSF Jarvis:
I'll be ready to snazz my posts ;)
[Android Software Development] DevUt:
new error :

Install: /home/devut/a/android/system/out/target/product/endeavoru/recovery/root/sbin/recovery
----- Making uncompressed recovery ramdisk ------
/home/devut/a/android/system/out/host/linux-x86/bin/mkbootfs /home/devut/a/android/system/out/target/product/endeavoru/recovery/root > /home/devut/a/android/system/out/target/product/endeavoru/ramdisk-recovery.cpio
----- Compressing recovery ramdisk with lzma ------
if [ -e /home/devut/a/android/system/out/target/product/endeavoru/ramdisk-recovery.cpio.lzma ] ;\
then \
rm /home/devut/a/android/system/out/target/product/endeavoru/ramdisk-recovery.cpio.lzma ; \
fi;
/usr/bin/lzma /home/devut/a/android/system/out/target/product/endeavoru/ramdisk-recovery.cpio
----- Making recovery image ------
/home/devut/a/android/system/out/host/linux-x86/bin/mkbootimg --kernel /home/devut/a/android/system/out/target/product/endeavoru/kernel --ramdisk /home/devut/a/android/system/out/target/product/endeavoru/ramdisk-recovery.img --cmdline "androidboot.selinux=permissive" --pagesize 2048 --output /home/devut/a/android/system/out/target/product/endeavoru/recovery.img
/home/devut/a/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=6520832 reserve=88704
----- Made recovery image: /home/devut/a/android/system/out/target/product/endeavoru/recovery.img --------
find: `/home/devut/a/android/system/out/target/product/endeavoru/recovery/root/res': No such file or directory

zip error: Nothing to do! (/home/devut/a/android/system/out/target/product/endeavoru/system/etc/recovery-resource.dat)
make: *** [/home/devut/a/android/system/out/target/product/endeavoru/system/etc/recovery-resource.dat] Error 12

#### make failed to build some targets (08:04 (mm:ss)) ####
[Android Software Development] MSF Jarvis:
Your recovery image should have been created, so ignore these errors for now.
[Android Software Development] DevUt:
new error IM KING OF ERRORS

sending 'recovery' (6368 KB)...
FAILED (remote: unknown command)
finished. total time: 1.029s

sending 'recovery' (6368 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[Android Software Development] vampirefo:
Your bootloader is locked?
[Android Software Development] DevUt:
Gh

Nah buddy it is the problem with the recovery im kinda flashaholic

---------- Post added at 03:27 PM ---------- Previous post was at 03:18 PM ----------

I have found the solution and will apply soon
[Android Software Development] MSF Jarvis:
fastboot erase recovery ? This your solution?
[Android Software Development] DevUt:
no see on pg 55 on this thread
[Android Software Development] klabit87:
I have looked all over and haven't found a solution yet.

This is my error

My first time really getting a working recovery to build in Omni sources.

I can build fine in CM13 but I really prefer Omni.

Also when I build in CM13 for some reason it doesnt use my twrp.fstab.

I will flash the recovery and have no options for storage and can't backup/restore as well as the recovery think I have no OS installed bc it cant see my storage.

Any help/input would be greatly appreciated.

Thank you for your time.

EDIT::

Ok, I think i just need to concentrate getting it to work properly in CM13 sources.

So my problem is it shows no storage at all when I build it.

I have my twrp.fstab in the device tree and everything so not sure whats wrong.

See photos for details.
[Android Software Development] NepoRood:
Link to device tree?
[Android Software Development] klabit87:
Yes here it is.

https://github.com/CyanogenMod/android_device_samsung_kltevzw/tree/cm-13.0?files=1

It does not include an fstab. But I have extracted the one from official build and used it. And same result.

I changed the locations to block numbers instead of by-name as well and there is no change.

Twrp still sees it as by-name.

Thanks.
[Android Software Development] ABHISHARMAKMJ:
dear sir, i hv samsung galaxy grand2 sm-g7102 and i m using twrp v3.0.0 and resurrection remix rom v5.6.9. plz provide me latest twrp v 3.0.2 for my phone
[Android Software Development] DarkFrenzy:
I had this issue. Because of twrp.fstab.

It was not in /etc folder, so I manually added it to etc.folder than it worked.

Is u r twrp.fstab in etc folder?
[Android Software Development] klabit87:
No it is not but I will definitely try that thanks!
[Android Software Development] NepoRood:
Ok, can you pull the recovery.log and provide the recovery.fstab?
[Android Software Development] klabit87:
It has no way of storing the log and adb won't connect either.

I will be getting the previous suggestion soon as I can though.

Thank you
[Android Software Development] vampirefo:
Your BoardConfig.mk needs to have a flag for the fstab.

mine is like this

TARGET_RECOVERY_FSTAB := device/yifang/NXA8QC116/etc/twrp.fstab
[Android Software Development] klabit87:
Thanks very much. I found out why it never changed for me.

It was inheriting the wrong fstab because of inheriting qcom/common things. I will be changing that like you have yours though.

Thank you for your time
[Android Software Development] DevUt:
I have successfully compiled the recovery but now the phone dosent boot into recovery

STEPS:

I compiled the recovery

i flashed it

i clicked to boot into recovery

HTC logo appeared

Black screeen for 2 secs

again HTC logo and it goes into normal state

by normal state i mean it boots into the rom
[Android Software Development] NepoRood:
Did you look around in the recovery root folder, make sure everything packed properly?

out/target/product/codename/recovery/root

Make sure the recovery.fstab is located in the "etc" folder, and make sure you got the proper init.rc and any other files required for your ramdisk.
[Android Software Development] lj50036:
You have a link to the device tree ?

Thx Josh
[Android Software Development] DevUt:
Check my device tree https://github.com/DevUt/android_device_htc_endeavoru?files=1
[Android Software Development] lj50036:
Can you unload the compiled recovery ?

Post me a link here or send me a PM with the link...

Thx Josh
[Android Software Development] DevUt:
Yes I can I will post it here but please can you wait a little
[Android Software Development] DevUt:
[MENTION=5039374]ij500036[/MENTION]

Here is my last_kmsg uploading the recovery.img soon
[Android Software Development] DevUt:
[MENTION=5123642]lj50036[/MENTION] I deleted the recovery image can you analyse the device tree P.S we also have a init. recovery. rc
[Android Software Development] NepoRood:
[MENTION=7401277]DevUt[/MENTION], just compile another one and upload that
[Android Software Development] DevUt:
Hey is there any flag to point out the recovery.rc?
[Android Software Development] lj50036:
Yes, but without having all the needed info, I cannot do much.....

Thx Josh
[Android Software Development] DevUt:
What is the flag?
[Android Software Development] lj50036:
Its not the same thing man, WITHOUT THE NEEDED INFO, I cannot help.

Thx Josh
[Android Software Development] DevUt:
Actually I think I found my trouble I had separate init.recovery.rc and my boadconfig.mk did not point to it
[Android Software Development] teemo:
Hi [MENTION=7401277]DevUt[/MENTION]

Just a heads up if you are not aware.

You cannot go permissive from command line. Or to be specific, you cannot change the command line for the "S-ON" HOX.

It will always get bootparams from bootloader. Only way to fool it that I know is via kexec ;)

If selinux need to be permissive, do it from init ( I am not sure CM13 tree will let you do this, but other people around here do know how to work around it).

# Boot/Recovery image settings
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
[Android Software Development] kenymccornick:
Hey man, how can I get that material theme? Did you compile TWRP with it? If so, how can do the same? :D Thanks in advance!
[Android Software Development] MSF Jarvis:
TW_CUSTOM_THEME := path/to/extracted/custom/theme/zip

Put this into your BoardConfig when you find the theme(I recommend [MENTION=2719389]z31s1g[/MENTION]'s uber cool material ones) and run a build. It should work.

Cheers,

MSF Jarvis
[Android Software Development] kenymccornick:
Appreciate the info, thanks man! Can I then put the contents anywhere I want? Say bootable/recovery-twrp/themes/theme-name for example? And thanks again, I checked the theme you mentioned and looks like the one I was asking for is z31s1g's material dark :good:
[Android Software Development] MSF Jarvis:
Told ya, z31s1g's a whiz with TWRP themes, he even did the stock theme. About the location query, no, the best place for the theme is in your device tree. Make a separate twrp-theme folder and just plonk it down there ;)
[Android Software Development] kenymccornick:
He definitely is, it's just beautiful! Gotcha, thanks again :)
[Android Software Development] klabit87:
Looks like Jarvis already answered but that is the theme that comes with the source for the version of twrp that I'm building.

And I don't know where is at currently. Haven't looked at it
[Android Software Development] followmsi:
Hi .. we are building TWRP for Pixel C .. it´s working quite good already.

One thing is missing -> data partition de/encryption via TWRP.

A tester has reported that he gets changing black screen - twrp logo - black screen .. for a few seconds.

After maybe 10 - 15 seconds he gets finally the password prompt for decryption .. but it fails to decrypt.

In a previous compile, where the fstab was not changed "VENDOR -> mounttodecrypt" the password prompt came up directly.

No black screens, just the password prompt ... but according to the old logs .. TWRP was NOT able to find the keymaster module.

Now, with "mounttodecrypt" (vendor) we are coming closer ... but it still fails to decrypt.

And has black screens .. :(

Here are the logs ..

I:Can't probe device /dev/block/mmcblk0p7
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p7', current file system: 'ext4'
get_crypt_ftr_info crypto key location: '/dev/block/platform/700b0600.sdhci/by-name/MD1'
I:Using automatic handling for /data/media emulated storage device.
I:Setting up '/data' as data/media emulated storage.
I:Created '/sdcard' folder.
I:Backup folder set to '/data/media/TWRP/BACKUPS/serialno'
I:Settings storage is '/data/media'
I:Device is encrypted with the default password, attempting to decrypt.
crypt_ftr->fs_size = 112941056
Using scrypt with keymaster for cryptfs KDF
Invalid hex string
Failed to convert passwd from hex, using passwd instead
keymaster module name is TLK Keymaster1 HAL
keymaster version is 256
Found keymaster1 module, using keymaster1 API.
Signing safely-padded object
__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 posixrules!
Starting TWRP 3.0.2-0 on Mon Jun 6 17:06:36 2016

Here is the full log ... http://pastebin.com/p4LW0ChC

The "black screen problem" and the logs with restarting TWRP after "Signing safely-padded object" ..

Sounds like crashing ?

The TWRP for Pixel C is normal Android recovery.img .. and just a chromeos (vboot) signing ontop.

SuperSU v2.72+ is also supporting the "vboot" part now.

"libc++" and "libkeymaster_messages.so" are already linked into the recovery.img.

Do you have an idea how to solve this encryption problem on Google Pixel C ?

Thanks
[Android Software Development] DevUt:
im having this weird sepolicy error

/home/devut/a/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/devut/a/android/system/out/target/product/endeavoru/obj/ETC/sepolicy_intermediates/policy.conf
/home/devut/a/android/system/out/host/linux-x86/bin/checkpolicy: loading policy configuration from /home/devut/a/android/system/out/target/product/endeavoru/obj/ETC/sepolicy.recovery_intermediates/policy_recovery.conf
device/htc/tegra3-common/sepolicy/drmserver.te:2:ERROR 'syntax error' at token 'allow' on line 13788:
allow drmserver knv_device:chr_file { { getattr open read ioctl lock } { open append write } };
#line 1 "device/htc/tegra3-common/sepolicy/drmserver.te"
checkpolicy: error(s) encountered while parsing configuration
make: *** [/home/devut/a/android/system/out/target/product/endeavoru/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
device/htc/tegra3-common/sepolicy/drmserver.te:2:ERROR 'syntax error' at token 'allow' on line 14042:
allow drmserver knv_device:chr_file { { getattr open read ioctl lock } { open append write } };
#line 1 "device/htc/tegra3-common/sepolicy/drmserver.te"
checkpolicy: error(s) encountered while parsing configuration
make: *** [/home/devut/a/android/system/out/target/product/endeavoru/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery] Error 1
[Android Software Development] DevUt:
Here's it the recovery.img
[Android Software Development] MSF Jarvis:
There's a typo in drmserver.te file, at least that's what the error says.
[Android Software Development] DevUt:
I overcame that but now I have uploaded the recovery.img would you check?
[Android Software Development] DarkFrenzy:
Is touch fine in aroma installer ? I m having problem with aroma installer because touch is not working fine there in twrp it works .

Have u tested aroma installer?
[Android Software Development] DevUt:
make: *** No rule to make target `/home/devut/CM13/android/system/out/target/product/endeavoru/system/xbin/busybox', needed by `/home/devut/CM13/android/system/out/target/product/endeavoru/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin'. Stop.
make: *** Waiting for unfinished jobs....
Generated: (/home/devut/CM13/android/system/out/target/product/endeavoru/android-info.txt)
make: Leaving directory `/home/devut/CM13/android/system'

make: *** No rule to make target `/home/devut/CM13/android/system/out/target/product/endeavoru/system/xbin/busybox', needed by `/home/devut/CM13/android/system/out/target/product/endeavoru/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin'. Stop.
make: *** Waiting for unfinished jobs....
Generated: (/home/devut/CM13/android/system/out/target/product/endeavoru/android-info.txt)
make: Leaving directory `/home/devut/CM13/android/system'
[Android Software Development] MSF Jarvis:
Clone GitHub.com/cyanogenmod/android_external_busybox branch cm-13.0 at external/busybox and compile again
[Android Software Development] DevUt:
This is from your non repo :p
[Android Software Development] MSF Jarvis:
That's [MENTION=5123642]lj50036[/MENTION]'s problem. I told him about the missing busybox on day one when he asked me to test it out.
[Android Software Development] lj50036:
https://github.com/lj50036/platform_manifest_twrp_cm/blob/twrp-13.0/default.xml#L60

https://github.com/lj50036/platform_manifest_twrp_cm/commit/2eb966b735ed9e86d75af3a79a651ecd37cc9019

Made the commit way back on Apr 15

Just love pointing the finger at others :D

Thx Josh
[Android Software Development] MSF Jarvis:
Hey! That's still not my fault. I sync sources, compress them, and upload. Anyways, [MENTION=7401277]DevUt[/MENTION], you know what to do.
[Android Software Development] DevUt:
So I think he didn't merge it :silly: [MENTION=6552280]MSF Jarvis[/MENTION] thanks for the help btw
[Android Software Development] MSF Jarvis:
:(

There's no such thing as a "merge" in repo. When you repo sync, first the manifest is updated by a git pull, then repo parses that manifest XML and syncs up all sources mentioned there.
[Android Software Development] DevUt:
Oh I thought manifest is not updated in any case until done manually!
[Android Software Development] MSF Jarvis:
*blinding flash of light infuses DevUt with knowledge*
[Android Software Development] kentuckyjosh:
TWRP for Blu Studio 5.0 II D532u

I'm searching for a way to load TWRP on a Blu Studio 5.0 II D532u, Anyone know where I can find it or help make one? I would love to get away from Jelly Bean 4.2.2
[Android Software Development] edzamber:
Hi all,

I'm running twrp 3.0.2.0 on S6 Edge G925F.

Does someone know how to fix screenshot colors ?

Bad tint...

Many Thanks,

Cheers,

Ed.
[Android Software Development] kentuckyjosh:
What do you need?
[Android Software Development] MSF Jarvis:
Flashing TWRP won't make you "get away from Jelly Bean 4.2.2" unless someone has a ROM made for your device. Wait, who builds a ROM without a working recovery first??

We don't need anything, you do. Common sense and the understanding that this thread is what teaches you how to compile TWRP for your device.
[Android Software Development] pcwizzy37:
Why do you want to go away from jb 4.2.2? 4.2.2 is the best OS in my opinion. I love Holo!
[Android Software Development] kentuckyjosh:
To get more options and apps
[Android Software Development] pcwizzy37:
What apps don't work with 4.2.2? The only app I have seen is incompatible is MotorTrendOnDemand. CyanogenMod 10.1 has plenty of options! You can get even more with Xposed!
[Android Software Development] Startrek852:
But he can't use either of those without a recovery. And also, I don't like Holo, I really prefer Material. It's so much better! prepares for war
[Android Software Development] pcwizzy37:
Is the ROM he using stock Android, or does it have an overlay? Material sucks! Ugly, Difficult, RAM hog, CPU hog, among other things.
[Android Software Development] Startrek852:
I don't know, I assume stock. And, I admit that Holo ROMs are faster, but I like the look of Material so much more.
[Android Software Development] Van.Fanel:
For Marshmallow devices, should the value for RECOVERY_SDCARD_ON_DATA be true?
[Android Software Development] DevUt:
new one
[Android Software Development] lj50036:
What am I doing with this recovery ?

Thx Josh
[Android Software Development] DevUt:
Check this one this is also not working i applied that recovery.rc you told
[Android Software Development] lj50036:
O my, :D

There is a lot going on here, now it seems the init.rc and init.recovery.*.rc at the same..

Your twrp.fstab is in the root of the ramdisk, rather then in /etc

and I cannot for the life of me figure out why there is an Android.mk in the root of the ramdisk ?

Thx Josh
[Android Software Development] DevUt:
The init.recovery. rc of omni imports logd.rc and .another .rc

For the logd.rc there is the Android.mk

And I know nothing about the twrp.fstab

Edit : i saw recovery.fstab in etc is same as twrp.fstab
[Android Software Development] vampirefo:
You do know, you can unpack recovery.img change ramdisk how you want then repack recovery.img
[Android Software Development] DevUt:
i even tried that moving twrp to etc
[Android Software Development] DevUt:
[MENTION=5123642]lj50036[/MENTION] i found that [MENTION=912474]Dees_Troy[/MENTION] has build twrp 3.0.2 for lg p880 that has same chipset

------——----------------------------------------------------------------------------------------------

[MENTION=5153662]Android-Andi[/MENTION] os there substitute of this Commit? I heard it causes problem on mka bacon

https://gerrit.omnirom.org/#/c/11468/
[Android Software Development] edzamber:
Hi,

Does someone know what part in ramdisk is driving mtp connection in TWRP Recovery ?

I mean i use TWRP Recovery [MENTION=4898097]arter97[/MENTION] but mtp is broken : i can see phone files but drag and drop with my computer doesn't working, it loose connection if i drop any files. I would like replace mtp drivers from a working one twrp 3.0.2.0 version.

Many Thanks.