cm14 build fails because
system/out/target/common/obj/APPS/ValidityService_intermediates/classes.dex isnt there but in my cm13 folder that folder isnt too how can i get that file/folder to get my build working
Related
anyone know where to find this lib for the kf2?
/system/lib/libnetcmdiface.so
aparently it being missing is why my rom wont finish booting logcat attached
bump lol
i see it in the bowser-common common.mk file...but i dont see it called out anywhere in the otter-common.mk file (if that makes any sense)
line 31 below
https://github.com/KFire-Android/android_device_amazon_bowser-common/blob/jb-mr1/common.mk
but its not anywhere
https://github.com/KFire-Android/android_device_amazon_otter-common/blob/jb-mr1/common.mk
Hi, I have a KFHD 7", and I have been able to locate stock libs inside of the update files such as "update-kindle-7.3.0_D025_3013320.bin" that you can download from Amazon- I don't know if that is a stock lib for your device or not, but if so, find the correct update version on Amazon's software update page, unarchive it and look inside the directory tree for system/libs and you'll see them all there. I hope this helps a little bit-
I am not responsable of any damage in your phone​Hi i have create this aow.wim images with ROOT bin and uncheked not to used BT and GSM in android apps but I cant copy it so system32/aow.wim
Can someone test it and put how to copy the image to pohne and most important if it works and if it is rooted you need to install SuperSU or others apps but bins are there...
Install route WINDOWS/System32/aow
Download:
http://www.mediafire.com/download/n68tle0kzd29b3e/aow.wim
For now i am tired of thinking i will try next day if i got time for it to copy to phone and try iif it works
This most likely won't work. The aow.wim on the system has extra headers that have Android-specific metadata attached to it. I see that you most likely just copied the contents out of it and then created a NEW wim, as it's impossible to commit changes to the aow.wim that comes with the update due to it complaining about WIMBoot.
snickler said:
This most likely won't work. The aow.wim on the system has extra headers that have Android-specific metadata attached to it. I see that you most likely just copied the contents out of it and then created a NEW wim, as it's impossible to commit changes to the aow.wim that comes with the update due to it complaining about WIMBoot.
Click to expand...
Click to collapse
I run dism comands and one ofgf them was create image from folder that was the previously one extract from phone and mod and it give me ok and the aow.wim image but now i dont know how to put it in system32 to try it
werty100 said:
I run dism comands and one ofgf them was create image from folder that was the previously one extract from phone and mod and it give me ok and the aow.wim image but now i dont know how to put it in system32 to try it
Click to expand...
Click to collapse
I not 100% sure if i'm correct in saying this but I don't think there is actually any method of putting the new aow.wim into the AOW folder, as using MTP or the built in file explorer either returns Permission error on unknown error respectively and @snickler has found that you cannot write to that directory using his SFTP method.
Plus @ADeltaX has managed to get root 2/3 working but project astoria doesnt allow two apps to overlay each so you cannot grant root access as there is no superSU pop-up. So he is working on modding superSU.
Just turn off "Protection against false touches" or smth like that in SuperSU (Settings)
I'm currently running a home build of the 13.0 branch on my HTC One m7, and I'm now trying to build 14.1 for it. When extracting the proprietary blobs, extract-files.sh reports that it can't find the following files:
Code:
/system/etc/firmware/widevine.b00
/system/etc/firmware/widevine.b01
/system/etc/firmware/widevine.b02
/system/etc/firmware/widevine.b03
/system/etc/firmware/widevine.mdt
/system/vendor/lib/libuiblur.so
A quick ls /system/etc/firmware as root from the terminal on my phone reveals that, indeed, there are no files named "widevine.*" in that directory. I also do not have libuiblur.so.
If I stubbornly continue with brunch anyway, the build fails immediately because those files are missing. I figure there must be some way to obtain those files without flashing an existing 14.1 build, and indeed it looks like extract-files.sh is capable of grabbing them from an expanded ROM, so I downloaded and unpacked the latest official nightly. I figure system.new.dat is the system image, but I'm unable to mount it; dmesg reports
Code:
EXT4-fs (loop0): bad geometry: block count 475135 exceeds size of device (168078 blocks)
So basically, I'm still more or less at a loss on how to get those proprietary blobs, bar the overkill solution of flashing an existing build. Any help would be greatly appreciated!
Thanks in advance.
EDIT: after some more digging, I discovered that the system image is not something you can just mount right away; instead you can use sdat2img to convert it into a proper disk image that can be mounted. extract-files.sh can then grab the files from the mount point (note that you have to name the mount point 'system' and pass its parent directory to the script).
I wonder what you end up doing to fix it and if you ended using CM13 blobs for 14.1? Your answer will be appreciated to test some things in order to restart official support.
I am trying to find what generates the updater-script that is put in the zip files during compile. I want to add some extra commands to it to fix an issue. I cant seem to find any template or file that generates it.
Does anyone know where the file is located.
also how would i include gapps in my lineage build so that i dont have to flash opengapps every time i wipe the device or install my compiled lineage.
hi, i followed this guide
https://forum.xda-developers.com/showthread.php?t=1863547
Is that guide still working ?
followed step by step but the kernel and the device/lge dont get automatically downloaded when i repo sync. Only vendor.
Also when i do breakfast it doesn't work , breakfast still see the path of my other repo and asks to find the device in a file not included in that guide.
Lastly of course brunch won't work without those files.....
The device i try build for is h815.
Thank you in advanced.
EDIT:
Could also copy paste the whole thing from the other repo i have here and only use the paranoid packages. That way i will still build paranoid , but ofc thats not the way i want to do it.
kessaras said:
hi, i followed this guide
https://forum.xda-developers.com/showthread.php?t=1863547
Is that guide still working ?
followed step by step but the kernel and the device/lge dont get automatically downloaded when i repo sync. Only vendor.
Also when i do breakfast it doesn't work , breakfast still see the path of my other repo and asks to find the device in a file not included in that guide.
Lastly of course brunch won't work without those files.....
The device i try build for is h815.
Thank you in advanced.
EDIT:
Could also copy paste the whole thing from the other repo i have here and only use the paranoid packages. That way i will still build paranoid , but ofc thats not the way i want to do it.
Click to expand...
Click to collapse
One way around this problem is to have your device tree on github and add it to the dependencies file either in the device repo, or add a (device_code_name).mk file to the vendor/pa/products/. Look at an existing device folder there for an example.