FORUMS

Introducing Voices of XDA: Have Your Ideas Heard

By far the greatest assets we have at XDA-Developers are you, the developers, the eager … more

Unofficial Xposed For Lollipop Touchwiz With Flashable Zip

XDA Recognized Developer arter97 has released an unofficial build … more

YotaPhone 2 Pre-Order, Xperia Z1 Price Cut – XDA TV

Android Wear 5.1.1 OTA downloads are now available. That and much more news is … more

[FTF] Sony Xperia Z Lollipop Release

Sony rolled out a Lollipop update for Xperia Z just yesterday. If you still haven’t gotten … more
Post Reply Subscribe to Thread Email Thread

[Q] I can't compile recovery

24th April 2014, 05:08 PM |#11  
yashade2001's Avatar
OP Senior Member
Flag Ankara
Thanks Meter: 902
 
Donate to Me
More
Quote:
Originally Posted by jdegreef

Well, I assume it is correct as the rom compiles, is flashable and boot.
I have the feeling that recovery is broken in Omnirom.
Yesterday I build CM11 (nightly sources) for Galaxy Tab 2 (gt-p5100) and I get the same "No private recovery resources for TARGET_DEVICE p5100" message. BUT the rom is working AND the recovery too !
The fact that the recovery from Omnirom is not booting as therefore nothing to do with this message.
I'll keep on searching and, more important, learn
One month ago I didn't know anything about building a rom but I had some knowledge about compiling the Linux kernel.
Anyway thank you for your help.

Recovery from omni is twrp and buildin twrp is a little different
 
 
1st May 2014, 03:34 AM |#12  
Senior Member
Flag Brussels, BE
Thanks Meter: 56
 
More
Quote:
Originally Posted by yashade2001

Recovery from omni is twrp and buildin twrp is a little different

Yes, I notice that.
I've made progresses and been able to compile both cwm and twrp. Compilation goes without error, recovery.fstab, twrp.fstab and BoardConfig.mk seem correct and recovery is flashed on the right partition but the recovery doesn't boot. It either get stucked at the first Samsung logo, either bootlooping at that logo. I have no idea what could be the cause and, worst, I have no idea how to debug that...
Even the method with the extracted boot.img gives the same results.

Sent from my GT-P5100 using Tapatalk
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes