Do You Check for App Updates Regularly?

Do you let app updates happen automatically or do you regularly check for them? We’re … more

Find The Best Apps With Google’s Picks & Other Tricks

The Google Play Store, weighing in with more than 1.4 million apps at last … more

Dynamic Pop for Note 4 (N910T & 910W8)

With the release of the Canadian Lollipop ROM for the Note 4, T-Mobile users can also enjoy the … more

Sunday Debate: Better to Buy Older or Newer Hardware?

Join us in a fun Sunday Debate on New vs. Old. Come with your opinions and feel … 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: 900
704 posts
Join Date:Joined: Sep 2012
Donate to Me
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
168 posts
Join Date:Joined: Oct 2013
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 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