FORUMS
Remove All Ads from XDA

[DEV]How to compile TWRP touch recovery

1,705 posts
Thanks Meter: 13,595
 
Post Reply Email Thread
5th September 2019, 12:50 AM |#4501  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Eamo5

@Dees_Troy Hi, I'm trying to compile TWRP for taimen using your provided wahoo trees. I was curious if there was a device tree available specifically for taimen, as I've manually made my own Omni device trees for taimen and have successfully compiled TWRP but I can't seem to get past the TWRP splash screen. I cant help but wonder if I'm missing something specifically for taimen from the (seemingly private) taimen trees used for official builds. Official builds have had broken decryption since August, hence I wanted to experiment with updating the provided sources from Google to see if I could get it working. I can only imagine you're very busy, but if you wouldn't mind taking the time to help out, it'd be greatly appreciated. My trees for wahoo and taimen are attached below. Thanks

https://github.com/Eamo5/android_dev...ts/android-9.0

https://github.com/Eamo5/android_dev...ts/android-9.0

I'm pretty sure that wahoo covers both walleye/taimen IIRC.
5th September 2019, 01:05 AM |#4502  
Eamo5's Avatar
Senior Member
Flag Melbourne
Thanks Meter: 2,314
 
Donate to Me
More
Quote:
Originally Posted by r3muxd

I'm pretty sure that wahoo covers both walleye/taimen IIRC.

You'd think so, but there's no omni_taimen.mk or omni_wahoo.mk or omni_walleye.mk for me to build with for any wahoo based devices.
5th September 2019, 02:55 AM |#4503  
Junior Member
Thanks Meter: 0
 
More
You need to create one, along with an androidproducts.mk and removing the "msm8998" "remove-project" line from your .repo manifest.

PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/omni_wahoo.mk

for androidproducts.mk and I can't find my old omni_wahoo file.
5th September 2019, 03:07 AM |#4504  
Eamo5's Avatar
Senior Member
Flag Melbourne
Thanks Meter: 2,314
 
Donate to Me
More
Quote:
Originally Posted by r3muxd

You need to create one, along with an androidproducts.mk and removing the "msm8998" "remove-project" line from your .repo manifest.

PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/omni_wahoo.mk

for androidproducts.mk and I can't find my old omni_wahoo file.

Oh I see. So to ensure I understand correctly, I *only* need to create an omni_wahoo.mk and this *does not* rely on me creating an omni_taimen.mk? I assumed I'd need to make omni makefiles specifically for taimen and that the provided TWRP trees for wahoo were fine without any extensive modifiations.
12th September 2019, 01:15 PM |#4505  
Junior Member
Thanks Meter: 7
 
More
i own redmi note 4. i was making TWRP device tree for other mobile so i looked in RN4(mido) DT for reference and i found this.

Cache size
Stock = 0x0010000000 = 268435456 = 256MB
TWRP DT = 0x0018000000 = 402653184 = 384MB
402653184 - 268435456 = 134217728 = 128MB <==

Userdata size
Stock = 57033595904
Stock(-16384) = 57033579520
TWRP DT = 58846081024
TWRP DT(-16384) = 58846064640
58846081024 - 57033595904 = 58846064640 - 57033579520 = 1812485120‬ <==

where do this extended size came from?

And one more question, do i need fstab.qcom when i use recovery.fstab?
14th September 2019, 09:59 PM |#4506  
Junior Member
Thanks Meter: 0
 
More
Por favor disponibilizem no aplicativo para o Multilaser MS60z &eacute; urgente
14th September 2019, 10:21 PM |#4507  
Frank Castle's Avatar
RC-RT Committee / Moderator Committee / Senior Moderator - "Si vis pacem, para bellum"
Thanks Meter: 57,444
 
1010101010
Donate to Me
More
Quote:
Originally Posted by 7Raatoo

Por favor disponibilizem no aplicativo para o Multilaser MS60z &eacute; urgente

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation.
15th September 2019, 09:00 PM |#4508  
Laikar_'s Avatar
Junior Member
Flag Barcelona
Thanks Meter: 7
 
More
I am getting "Unknown ARM architecture version: armv8-a." when trying to lunch, what am i missing/ doing wrong?
21st September 2019, 06:48 PM |#4509  
matteo0026's Avatar
Senior Member
Flag Treviso
Thanks Meter: 447
 
More
Hi guys, I updated with success TWRP to Oreo kernel for nappa and yamcha from TeamWin official sources. https://github.com/matteo0026/android_device_bq_nappa https://github.com/matteo0026/android_device_bq_yamcha Now, I have an ask. How can the recovery work well with Nougat 7.1 libs?
22nd September 2019, 03:27 PM |#4510  
Quote:
Originally Posted by matteo0026

Hi guys, I updated with success TWRP to Oreo kernel for nappa and yamcha from TeamWin official sources. https://github.com/matteo0026/androi...vice_bq_yamcha Now, I have an ask. How can the recovery work well with Nougat 7.1 libs?

It just does work, but i'd update yout twrp to 3.3.1, which i think is available starting on 8.0/8.1 build manifests
22nd September 2019, 03:33 PM |#4511  
Senior Member
Thanks Meter: 263
 
More
Quote:
Originally Posted by palmbeach05

It just does work, but i'd update yout twrp to 3.3.1, which i think is available starting on 8.0/8.1 build manifests

Hi,

The latest TWRP builds in all trees going back to 5.1.

TWP
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes