Nexus 6P Sim not Detected

[Anushree Ganjam]

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

[David Hacker]

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.

[Anushree Ganjam]

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

[bechts...@gmail.com]

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 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.).

[Anushree Ganjam]

Hi ,
Factory images are extracted now.
I got the vendor folder extracted. Should I copy this vendor folder to AOSP build tree?
Will this generate vendor.img?
Any changes to be made to generate vendor.img ? Or will this fall under the folder /system/vendor?


Regards
Anushree

[Anushree Ganjam]

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, bechts...@gmail.com wrote:

[bechts...@gmail.com]

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.

[Anushree Ganjam]

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

[bechts...@gmail.com]

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?

[Anushree Ganjam]

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.

[Anushree Ganjam]

Hi,
I flashed the generated binaries by removing the sim card. Still the CNEService crash exists.

* Ensure your wipe/format partitions when fastboot (-w flag)

flashed all the partitions using fastboot flash -w <partition> <partition.img>

Order followed:
fastboot flash -w boot boot.img
fastboot flash -w recovery recovery.img
fastboot flash -w system system.img
fastboot flash -w vendor vendor.img
fastboot flash -w userdata userdata.img
fastboot flash -w cache cache.img

Even flashed bootloader-angler-angler-02.45.img & radio-angler-angler-02.50.img as obtained from factory version MMB29Q.

* Double-check your repo tree is not corrupted (repo status)

Yes, it is not corrupted.
repo status shows only the changes done for symlink -- /system/vendor -> /vendor

* Double-check your sync repo tags are matching the target device

Yes, repo sync tag is android-6.0.1_r11 AOSP -- This is for Nexus 6P

* If you flash partitions manually ensure that you flash them all (prefer flashall fastboot command since you compile all of them)

I am making the builds on the server. So copying the images to my local pc and then flashing. So unable to use fastboot flashall

* 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  -- I am not flashing GAPPS. GAPPS does it mean Google Apps?

* Double check all changes/additions (except Huawei vendor files) you've made to vanilla sources

Only changes done are vendor files + changes done for symlink

I am building against the tag android-6.0.1_r11 -- MMB29Q - as mentioned earlier.

Any other changes have you made other than vendor files ? Have you not done symlink changes to vanila code ?
Thanks for your support. Please help me.

[Desconocido Nadie]

Hi Anushree, I had same problem with AOSP MMB29Q for Motorola Nexus 6. I fixed this issue changing google factory image's /system/vendor folder.
Regards.

[bechts...@gmail.com]

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.

[Anushree Ganjam]

Issue solved.
Sim is detected !
The mistake done was referring to system folder with .odex files instead of deoptimized odex during vendor generation.

Kudos !

[Desconocido Nadie]

Could you explain , step by step , how you solved the issue, please?

[Gautam Gandhi]

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

[Anushree Ganjam]

Hi,

As explained with the links already mentioned before, if we follow it should be good enough.

Here are the steps.

1. Create the symlink  /system/vendor --> /vendor 

Refer : https://github.com/CyanogenMod/android_build/commit/5edc9e08ca395769f975dd817c38784a68b166b5

2. Creating our own vendor image. 

First extract the factory system.img , vendor.img to get the vendor folder.

Refer : https://github.com/anestisb/android-prepare-vendor

3. Copy the extracted vendor to aosp build structure as vendor folder.

4. Make the build for angler, flash the images . Sim will be detected.

Thanks

[bechts...@gmail.com]

Just a small clarification. Step1 (manually add code to create vendor symlink) is not required. When compiling a vanilla AOSP tree with included vendor files generated from described step2, vendor symlink will be generated because of this.

The scripts to prepare the vendor files for new Nexus devices have been designed in such a way that vanilla AOSP builds can be created without any changes in the source code-base. If you've found a case where vanilla builds fail please raise a bug report at the git repo of the tool so I can investigate and work a solution.

[黃邦彥]

hello,
i use https://github.com/anestisb/android-prepare-vendor tool,
bug got some error message,
how can i fix it?
thx.

[*] Extracting 'angler-mhc19q-factory-f5a4e7a1.tgz'
[*] Unzipping 'image-angler-mhc19q.zip'
[*] Copying files from system parition ...
[*] Copying files from vendor partition ...
[*] Preparing environment for 'arm' ABI
[!] Boot classes extraction failed
[-] System partition de-optimization failed


Anushree Ganjam於 2016年3月5日星期六 UTC+8上午10時32分36秒寫道：

[Anushree Ganjam]

It worked well for me.
Please tell me which script are you running.

[Noam Maimon]

Hi,

I follow the process of anestisb's Github repository 'android-prepare-vendor'

The process (execute-all.sh) finished successfully, but on the way it log an error:

"Disk /tmp/android_img_extract.sMoQ3R/bullhead-mhc19j-factory-ef8341a4/images/vendor.img.raw doesn't contain a valid partition table"

when i copied the genreated 'Vendor' folder and put it in the AOSP root dir, and run make-j4 i got a compilation error:

"make: *** No rule to make target `vendor/lge/bullhead/proprietary/bin/qmuxd', needed by `out/target/product/bullhead/system/bin/qmuxd'. Stop."

i am running the 'android-prepare-vendor' scripts on virtual box ubuntu and the source compilation on MAC.

Does anyone know what this error means or can give me any clue how to resolve this issues and set my Nexus5X working with my compiled rom?
(i am android developer but this is my first time with building the source on real device)

i will appreciate any help,
Thanks in advance,

[Anushree Ganjam]

Hi,

Please find comments inline.

On Friday, April 15, 2016 at 9:38:56 PM UTC+5:30, Noam Maimon wrote:

Hi,

I follow the process of anestisb's Github repository 'android-prepare-vendor'

The process (execute-all.sh) finished successfully, but on the way it log an error:

"Disk /tmp/android_img_extract.sMoQ3R/bullhead-mhc19j-factory-ef8341a4/images/vendor.img.raw doesn't contain a valid partition table"

This is not a problem. Even I have seen this log during the extraction.

 

when i copied the genreated 'Vendor' folder and put it in the AOSP root dir, and run make-j4 i got a compilation error:

"make: *** No rule to make target `vendor/lge/bullhead/proprietary/bin/qmuxd', needed by `out/target/product/bullhead/system/bin/qmuxd'.  Stop."

This is the problem while copying the vendor files from one pc to another,  Please check in your ubuntu if vendor/lge/bullhead/proprietary/bin/qmuxd is generated. If yes, copy this file to Mac for your source compilation.

[cesarsandra oraya]

orayacesa...@gmail.com

cesarsandra

> --
> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> 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 android-buildi...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Noam Maimon]

Hi Anushree,

Thank you very much!
you right. while archiving the folder and send it via cloud, this file was left behind..
so i renamed the binary qmuxd file, and send it again. and it works!! the build succeeded, vendor.img created, and sim detected.
b.t.w i used only the second step, as bechts... said.

thanks a lot! you make my day.

[Jal Singh]

Hi Gautam,

Were you able to resolve the issue, as i am having the same problem.

Any help appreciated.

Thanks