Database Info

Sbf issues win7 x64

I am getting an error when trying to sbf my Xoom where it is saying it fails to communicate with the RAM Downloader. I am running Win 7 x64. I have tried putting the files in the rsd folder, root of C, even My documents, nothing is working. I have also set it up to run as administrator to no avail. I have attached the error log if it helps anyone.
19:59:02, April 15, 2011 Line: 1633 ERROR: MA type 0 is not supported. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp Device ID: 0
20:02:34, April 15, 2011 Line: 1633 ERROR: MA type 0 is not supported. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 612 ERROR: Interface BP: Error checking the RAM Downloader. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 321 ERROR: Interface BP: Error jumping to RAM Downloader File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 1190 ERROR: Phone[0000]: Flash failed. File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp Device ID: 0
20:04:56, April 15, 2011 Line: 597 ERROR: Flash failure: Interface BP: Error checking the RAM Downloader. (Error Code: 9f), Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp Device ID: 0

[Q][JB on msm8960]qcom propritary adreno driver fails while android(JB) is booting

Dear All,
I am porting JB for QCom's msm8960 architecture (specifically for APQ8060A boards). I have downloaded several MSM8960
specific Code aurora releases and compiled them for msm8960. I have also downloaded Adreno user space drivers binaries.
After successful compilation when I run the Android image on the board, But a graphics related issue occurs.
'/system/bin/bootanimation' is not able to display anything on the screen and receives error while executing
eglSwapBuffers. Following are the Android 'main' logs for the error.
...
E/libEGL ( 515): eglApi.cpp : [eglSwapBuffers] dp->disp.dpy:1, s->surface:1
W/Adreno200-EGLSUB( 515): <GetBackBuffer:2172>: handle base address is NULL
W/Adreno200-ES20( 515): <gl2_surface_swap:43>: GL_OUT_OF_MEMORY
W/Adreno200-EGL( 515): <qeglDrvAPI_eglSwapBuffers:3477>: EGL_BAD_ALLOC
E/libEGL ( 515): [eglSwapBuffers] result = 0
...
W/Adreno200-EGLSUB( 515): <GetBackBuffer:2172>: handle base address is NULL
W/Adreno200-EGL( 515): <qeglDrvAPI_eglSwapBuffers:3477>: EGL_BAD_ALLOC
E/BootAnimation( 515): [BootAnimation.cpp][android] retval of eglSwapBuffers = 0
W/Adreno200-GSL( 515): <gsl_ldd_control:225>: ioctl code 0x40040921 (IOCTL_KGSL_SHAREDMEM_FREE) failed: errno 22 Invalid argument
...
Please let me know if any one of you has faced such problem.
I was doubting that Adreno user space drivers which I downloaded explicilty from QCom's website are not compatible with
the Android release, Therefore I tried with several Android releases but nothing works and shows the same error always.
Regards,
Nitin

aosp kitkat4.4 nexus 7(deb) not boot

hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional

[msm8939][meizu][camera]dlopen failed: could not load library "libcam.meiyan.so" need

[msm8939][meizu][camera]dlopen failed: could not load library "libcam.meiyan.so" need
Hello,
Could you please help me?
Platform:meizu m1note msm8939
I ported from flyme to miui.
The camera has problem.
I got the error:
dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so";
caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
About symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl",
I found it at:
m463c/rom/update/system $ g CBeautyShot
Binary file ./lib/libarcsoft_beauty_shot.so matches
Binary file ./lib/libcam.meiyan.so matches
And I push them to my phone.
But I still get the error.
Who can help me? Thank you very much.
I have been debugging for several days.
01-02 08:17:52.901 I/libmdmdetect( 351): Found internal modem: modem
01-02 08:17:52.901 E/QC-QMI ( 272): qmi_client [272]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 E/QC-QMI ( 351): qmi_client [351]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 I/ThermalEngine( 288): Sensor:tsens_tz_sensor3:80000 mC
01-02 08:17:52.941 E/HAL ( 276): load: module=/system/lib/hw/camera.msm8916.so
01-02 08:17:52.941 E/HAL ( 276): dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so"; caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
01-02 08:17:52.941 E/CameraService( 276): Could not load camera HAL module
01-02 08:17:52.941 I/mediaserver( 276): ListenService instantiated
01-02 08:17:52.941 V/ListenService( 276): instantiate entered
01-02 08:17:52.941 V/ListenService( 276): getInstance entered, mNumInstances currently 0
Eismog
my-mail:[email protected]

Is there anyone who can help me?

Can't get mobile data working on AOSP for Pixel, please help!

I have compiled AOSP (android-7.1.1_r8) for my pixel and I am able to boot, however, mobile data is not working. I get the following message in the "logcat" every 5 seconds which I think may be related:
01-06 14:58:08.749 2503 2503 I libmdmdetect: No supported ESOC's found
01-06 14:58:08.753 2503 2503 I libmdmdetect: slpi subsystem located
01-06 14:58:08.753 2503 2503 I libmdmdetect: Found internal modem: modem
01-06 14:58:08.753 2503 2503 I libmdmdetect: modem subsystem found
01-06 14:58:08.758 2503 2503 I libmdmdetect: No supported ESOC's found
01-06 14:58:08.759 2503 2503 I libmdmdetect: slpi subsystem located
01-06 14:58:08.759 2503 2503 I libmdmdetect: Found internal modem: modem
01-06 14:58:08.759 2503 2503 I libmdmdetect: modem subsystem found
01-06 14:58:08.760 2503 2503 E QC-NETMGR-LIB: QC-NETMGR
I have the latest radio image. Any help would be greatly appreciated.

It seems netmgrd fails to start, from dmesg:
[ 3051.236076] c2 1 init: Starting service 'netmgrd'...
[ 3051.344711] c2 1 init: Service 'netmgrd' (pid 3714) exited with status 255
[ 3051.344840] c2 1 init: Service 'netmgrd' (pid 3714) killing any children in process group
every 5 seconds.
and no rmnet interface? hmmm
please help...

Okay, I used strace and found that persist.rmnet.data.enable was false and a config file /system/etc/data/netmgr_config.xml was missing. I used setprop to set persist.rmnet.data.enable to true. I also grabbed that config file from the stock rom and had aosp add it to my system image. It seems this keeps netmgr from crashing. Now I have an rmnet_data0 interface but I still can't get an IP. Progress? maybe but not sure...
Please help.

logcat -b radio yields:
01-10 07:43:14.385 1560 1708 D DC-1 : onConnect: carrier='Rogers LTE' APN='ltemobile.apn' proxy='' port=''
01-10 07:43:14.386 1560 1708 D RILJ : [3911]> SETUP_DATA_CALL 14 0 ltemobile.apn 0 IPV4V6 [SUB0]
01-10 07:43:14.388 607 755 E RILQ : (0/607): RIL[0][main] qcril_data_request_setup_data_call: unable to get dsi hndl
01-10 07:43:14.388 607 755 E RILQ : (0/607): RIL[0][main] qcril_data_request_setup_data_call: qcril_data_request_setup_data_call: EXIT with FAILURE
01-10 07:43:14.388 1560 1659 D RILJ : [3911]< SETUP_DATA_CALL DataCallResponse: {version=11 status=4100 retry=-1 cid=0 active=0 type= ifname= mtu=0 addresses=[] dnses=[] gateways=[] pcscf=[]} [SUB0]
01-10 07:43:14.389 1560 1659 E TelephonyMetrics: Unknown type:
any help would be appreciated.

Okay I figured it out.
There are two files that are present in the system image of the stock rom, /system/etc/data/dsi_config.xml and /system/etc/data/netmgr_config.xml these files must be present in your AOSP system image in order to have LTE.

Thanks for this, only helpful info I found on No Supported ESOCs. Allowed me to debug my problem and fix.