Hi Gautam, Were you able to resolve the issue, as i am having the same problem. Any help appreciated. Thanks
On Friday, 4 March 2016 21:27:18 UTC+5:30, Gautam Gandhi wrote: > > Anushree can you tell me how exactly did you created the symlink ? I > followed the above script > https://github.com/anestisb/android-prepare-vendor. Extracted to the root > directory. Everything worked but when i am making ota_update zip & trying > to sideload it i am getting error as below > *failed to mount /dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor > at /vendor : No such file or directory symlink : some symlinks failed* > > On Wednesday, March 2, 2016 at 9:50:36 PM UTC+5:30, Anushree Ganjam wrote: >> >> Issue solved. >> Sim is detected ! >> The mistake done was referring to system folder with .odex files instead >> of deoptimized odex during vendor generation. >> >> Kudos ! >> >> >> On Wednesday, March 2, 2016 at 12:00:41 AM UTC+5:30, [email protected] >> wrote: >>> >>> It seems that the vendor APKs de-optimized from factory images are >>> corrupted (missing entry-point classes). You can verify it with a quick >>> check for the missing classes with something like the following: >>> >>> $ out/host/linux-x86/bin/dexdump >>> vendor/huawei/angler/proprietary/priv-app/CNEService/CNEService.apk | grep >>> -E "Class descriptor.*com.quicinc.cne.CNEService" >>> Class descriptor : >>> 'Lcom/quicinc/cne/CNEService/CNEServiceApp$MyHandler;' >>> Class descriptor : 'Lcom/quicinc/cne/CNEService/CNEServiceApp;' >>> >>> If you don't have an output similar to the above it means that oat2dex >>> de-optimization process executed from "system-img-repair.sh" script has >>> failed. Have you noticed any error messages when executing the scripts to >>> prepare the vendor blobs from provided toolset? >>> >>> The first suspect for oat2dex errors is an incompatible system java >>> version. Run the following from "android-prepare-vendor" repo root to >>> verify: >>> >>> $ java -jar hostTools/Java/oat2dex.jar >>> >>> >>> If no errors are printed you need to run the extract scripts again and >>> check for printed/unhandled errors. >>> >>> >>> On Friday, 26 February 2016 18:50:27 UTC+2, Anushree Ganjam wrote: >>>> >>>> Hi, >>>> I got the crash log. >>>> It is related to libraries missing and No original dex files found for >>>> dex location /system/framework/qcrilhook.jar >>>> Attaching the crash log. >>>> >>>> For CNE Service : >>>> 01-01 22:53:03.230 E/AndroidRuntime(19375): Process: >>>> com.quicinc.cne.CNEService, PID: 19375 >>>> 01-01 22:53:03.230 E/AndroidRuntime(19375): java.lang.RuntimeException: >>>> Unable to instantiate application >>>> com.quicinc.cne.CNEService.CNEServiceApp: >>>> java.lang.ClassNotFoundException: Didn't find class >>>> "com.quicinc.cne.CNEService.CNEServiceApp" on path: DexPathList[[zip file >>>> "/system/priv-app/CNEService/CNEService.apk"],nativeLibraryDirectories=[/system/priv-app/CNEService/lib/arm64, >>>> >>>> /system/priv-app/CNEService/CNEService.apk!/lib/arm64-v8a, /vendor/lib64, >>>> /system/lib64]] >>>> >>>> >>>> For Phone crash: >>>> 01-01 22:53:03.428 E/AndroidRuntime(19359): Process: com.android.phone, >>>> PID: 19359 >>>> 01-01 22:53:03.428 E/AndroidRuntime(19359): java.lang.RuntimeException: >>>> Unable to instantiate receiver >>>> com.android.sdm.plugins.connmo.ConnmoReceiver: >>>> java.lang.ClassNotFoundException: Didn't find class >>>> "com.android.sdm.plugins.connmo.ConnmoReceiver" on path: DexPathList[[zip >>>> file "/system/framework/qcrilhook.jar", zip file >>>> "/system/priv-app/ConnMO/ConnMO.apk"],nativeLibraryDirectories=[/system/priv-app/ConnMO/lib/arm64, >>>> >>>> /vendor/lib64, /system/lib64]] >>>> >>>> >>>> >>>> Please help >>>> Thanks. >>>> >>>> On Friday, February 26, 2016 at 5:42:00 AM UTC+5:30, >>>> [email protected] wrote: >>>>> >>>>> Well, without any log entries there aren't much I can help with expect >>>>> some generic bits (see later bullets). Since you mention that the >>>>> CNEService service is crashing, and considering that it should kick-in >>>>> when >>>>> 3g/4g data is detected, the problem might be specific to your service >>>>> carrier. Try booting the device without the SIM card inserted and verify >>>>> that device is on a sane state (no crashes, no unexpected fatal/error >>>>> logs) >>>>> before re-inserting the SIM card (also monitor logcat while doing so). >>>>> >>>>> * Ensure your wipe/format partitions when fastboot (-w flag) >>>>> * Double-check your repo tree is not corrupted (repo status) >>>>> * Double-check your sync repo tags are matching the target device >>>>> * If you flash partitions manually ensure that you flash them all >>>>> (prefer flashall fastboot command since you compile all of them) >>>>> * If you flash GAPPS there are a couple of permission hacks that needs >>>>> to be applied so leave them out for the time being to ensure they don't >>>>> conflict >>>>> * Double check all changes/additions (except Huawei vendor files) >>>>> you've made to vanilla sources >>>>> >>>>> Just to let you know that I've recently compiled a >>>>> vanilla android-6.0.1_r11 AOSP userdebug build without any problems for >>>>> the >>>>> N6P using the vendor files generated from the previous script. Which tag >>>>> are you building against? >>>>> >>>>> >>>>> >>>>> On Thursday, 25 February 2016 17:42:44 UTC+2, Anushree Ganjam wrote: >>>>>> >>>>>> Hi, >>>>>> The Build is success now. >>>>>> vendor.img and system.img is generated. >>>>>> I used WITH_DEXPREOPT=false in BoardConfig.mk. Even symlink is >>>>>> created. /system/vendor ---> /vendor >>>>>> >>>>>> Once the generated images are flashed, There are 2 crashes >>>>>> continuously happening. >>>>>> >>>>>> 1. process com.android.phone has stopped. >>>>>> 2. com.quicinc.cne.CNEService has stopped. >>>>>> >>>>>> I am unable to collect the logs for this, since device is not getting >>>>>> detected in the pc. >>>>>> >>>>>> Please help how to solve. >>>>>> >>>>>> Regards >>>>>> Anushree >>>>>> >>>>>> >>>>>> >>>>>> On Tuesday, February 23, 2016 at 10:26:36 PM UTC+5:30, >>>>>> [email protected] wrote: >>>>>>> >>>>>>> Seems that your build failed to pre-optimize the apps under system >>>>>>> partition and that is why system.img has not been generated. Give it >>>>>>> another spin with less jobs (-j flag in make) in case you run out of >>>>>>> memory >>>>>>> in initial build. Also check from system running processes the status >>>>>>> of >>>>>>> java jack-server (it's safe to kill it since build process restarts it >>>>>>> if >>>>>>> not found). >>>>>>> >>>>>>> If problem persists disable DEX pre-optimization by setting the >>>>>>> "WITH_DEXPREOPT=false" flag when invoking make. >>>>>>> >>>>>>> >>>>>>> On Tuesday, 23 February 2016 17:58:07 UTC+2, Anushree Ganjam wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> I copied the generated vendor folder to AOSP build structure. >>>>>>>> Build failed. >>>>>>>> I am not sure what is the error though. >>>>>>>> Attaching the build failure logs. >>>>>>>> vendor.img was created. system.img is not created. >>>>>>>> Please help. >>>>>>>> >>>>>>>> Also attaching the radio logs to check why sim is not detected. >>>>>>>> Thanks >>>>>>>> >>>>>>>> On Tuesday, February 23, 2016 at 1:50:52 AM UTC+5:30, >>>>>>>> [email protected] wrote: >>>>>>>>> >>>>>>>>> AOSP building against recent Nexus devices (5x, 6p, 9) has been >>>>>>>>> evolved into a significantly more complex process since Google has >>>>>>>>> stopped >>>>>>>>> providing vendor blobs compatible with build system. >>>>>>>>> >>>>>>>>> Information here >>>>>>>>> <https://github.com/anestisb/android-prepare-vendor> explains the >>>>>>>>> problem with more details and provides an automation solution that >>>>>>>>> can work >>>>>>>>> with your Nexus 6p setup. More specifically in your case you're >>>>>>>>> missing >>>>>>>>> proprietary binaries from system partition related to radio >>>>>>>>> functionality >>>>>>>>> (qrild, ims app, etc.). >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, 22 February 2016 17:29:03 UTC+2, Anushree Ganjam wrote: >>>>>>>>>> >>>>>>>>>> Hi David, >>>>>>>>>> >>>>>>>>>> I tried the solution as mentioned in link >>>>>>>>>> https://github.com/CyanogenMod/android_build/commit/5edc9e08ca395769f975dd817c38784a68b166b5 >>>>>>>>>> >>>>>>>>>> Now /system/vendor is pointing to /vendor. >>>>>>>>>> Symlink is created. I flashed all the generated images + >>>>>>>>>> vendor.img >>>>>>>>>> But Even now i get "No sim card -- No service" . >>>>>>>>>> On the same Nexus 6P phone I flashed factory version of MMB29Q, >>>>>>>>>> sim is detected and Network is latched. >>>>>>>>>> >>>>>>>>>> Please help. >>>>>>>>>> Thanks for the support in advance. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> Anushree >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Saturday, February 20, 2016 at 5:43:10 AM UTC+5:30, David >>>>>>>>>> Hacker wrote: >>>>>>>>>>> >>>>>>>>>>> The AOSP build does not create a symlink form vendor to >>>>>>>>>>> system/vendor, for whatever reason it is ONLY created when you >>>>>>>>>>> build a >>>>>>>>>>> vendor image (internal google builds). You can manually create the >>>>>>>>>>> link or >>>>>>>>>>> there are some commits in other custom roms that make it at build >>>>>>>>>>> time. >>>>>>>>>>> >>>>>>>>>>> On Friday, February 19, 2016 at 10:14:42 AM UTC-5, Anushree >>>>>>>>>>> Ganjam wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> I have downloaded MMB29Q android-6.0.1_r11 - Marshmallow code >>>>>>>>>>>> for Nexus 6P. >>>>>>>>>>>> The AOSP code is build using lunch 17 (aosp_angler-userdebug) >>>>>>>>>>>> Build is success and I flashed all the images. >>>>>>>>>>>> Even the vendor.img is downloaded from Factory version of >>>>>>>>>>>> MMB29Q and flashed on the phone. >>>>>>>>>>>> Phone booted up and sim card is not detected. >>>>>>>>>>>> >>>>>>>>>>>> When I flash the MMB29Q factory version on same phone, the sim >>>>>>>>>>>> card is detected. >>>>>>>>>>>> But only In case of direct AOSP compilation, sim card is not >>>>>>>>>>>> detected . >>>>>>>>>>>> >>>>>>>>>>>> Please help me to solve this problem. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Regards >>>>>>>>>>>> Anushree >>>>>>>>>>>> >>>>>>>>>>> -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
