Hey everybody, do any of you know where I can find the ADB driver for this phone? My flashtool driver pack doesn't have it and I can't find anywhere online unfortunately.
Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts
Monday, 19 October 2015
Friday, 16 October 2015
Building AOSP Marshmallow - are files still missing from the binary driver Zips?
Hi, i'm building AOSP Marshmallow to flash onto a Nexus 5 - are critical files still missing from the Binary drivers like they were for KitKat & Lollipop?
If so, is there a list of what files are missing from the zips, and where they should go once found? (I presume I need to find them in the system image still)?
If so, is there a list of what files are missing from the zips, and where they should go once found? (I presume I need to find them in the system image still)?
Saturday, 3 October 2015
[HELP!!!] My GP2 wont boot and usb driver fail to install
hi,
sorry for this but please help me? i had my gp2 for 2 years now then recently i decided to change its dpi then it happen it wont boot anymore. i was aware that this might happen but still i never had 2nd thought of doing it since i can always flash a new kdz and never install a custom recovery on it. I can still enter the download mode but the big problem is that it cant be detected by the computer i tried to give it a try on my friends computer and install the driver too but i have no luck still it cant be detected. So now my big problem is i can't flash a new kdz because of that. It fail to install LGE Android MTP Device driver and when i try to updated the driver manually it also fail with reason of Code 10. Please someone help me because ive been searching for days now on how can i make GP2 to be detected again and flash new kdz and revive it again.
Thank you in advance.
sorry for this but please help me? i had my gp2 for 2 years now then recently i decided to change its dpi then it happen it wont boot anymore. i was aware that this might happen but still i never had 2nd thought of doing it since i can always flash a new kdz and never install a custom recovery on it. I can still enter the download mode but the big problem is that it cant be detected by the computer i tried to give it a try on my friends computer and install the driver too but i have no luck still it cant be detected. So now my big problem is i can't flash a new kdz because of that. It fail to install LGE Android MTP Device driver and when i try to updated the driver manually it also fail with reason of Code 10. Please someone help me because ive been searching for days now on how can i make GP2 to be detected again and flash new kdz and revive it again.
Thank you in advance.
Wednesday, 30 September 2015
problem with the adb interface driver (install/uninstall drivers)
hi,
im having issues installing drivers for my oneplus 2 device.
here's what i've tried doing:
iv'e tried connecting the device with usb debugging and without. without usb debugging it finds the name of the device normally.
the first thing i've done is uninstall every driver that was resembled any phone, google or usb storage driver.
and tried to install the drivers from this tool: (which i think is the source of my problem i dont know how to remove this.)
it went ok with no problems, but it didn't find my device. (when i typed adb devices)
i've uninstalled the drivers again via programs and features and usbdeview tool (this time i've found older samsung device driver from regedit and removed it also).
rebooted (as every step of driver removal and install).
i've tried again with no luck.
so i've decided to install those drivers from the android sdk but when i've tried to install it from the device manager it shows up this:
i also tried downloading samsung drivers to see if it works. i saw in one of the threads that said it's ok to use them because they were universal too. (i removed it again from the regedit when i couldn't find the drivers)
i tried to use the oneplus one toolkit's for it's universal driver i thought maybe it will work
how can i fix this? i want to start over again clean. i can't find it in USBdeview or programs and features or regedit. what am i missing?
the photos are after trying to install the drivers from the sdk tool and uninstall it back with reboots several times now
+as im seeing in other threads, it supposed to be an android device and not adb interface.
+there is nothing else in the driver selection list that resembles any device
thanks to everyone who helps!
im having issues installing drivers for my oneplus 2 device.
here's what i've tried doing:
iv'e tried connecting the device with usb debugging and without. without usb debugging it finds the name of the device normally.
the first thing i've done is uninstall every driver that was resembled any phone, google or usb storage driver.
and tried to install the drivers from this tool: (which i think is the source of my problem i dont know how to remove this.)
it went ok with no problems, but it didn't find my device. (when i typed adb devices)
i've uninstalled the drivers again via programs and features and usbdeview tool (this time i've found older samsung device driver from regedit and removed it also).
rebooted (as every step of driver removal and install).
i've tried again with no luck.
so i've decided to install those drivers from the android sdk but when i've tried to install it from the device manager it shows up this:
i also tried downloading samsung drivers to see if it works. i saw in one of the threads that said it's ok to use them because they were universal too. (i removed it again from the regedit when i couldn't find the drivers)
i tried to use the oneplus one toolkit's for it's universal driver i thought maybe it will work
how can i fix this? i want to start over again clean. i can't find it in USBdeview or programs and features or regedit. what am i missing?
the photos are after trying to install the drivers from the sdk tool and uninstall it back with reboots several times now
+as im seeing in other threads, it supposed to be an android device and not adb interface.
+there is nothing else in the driver selection list that resembles any device
thanks to everyone who helps!
I can't install adb driver to xp sp3
I try Google USB but it's not work. When I try 15 second adb it's not work for xp. I need help. How can I install adb to xp sp3
Recent Broadcom driver for >4.4.4 ROMs
Said ahead, I would have posted this in http://forum.xda-developers.com/gala...-12-1-t3084287 where it belonged, since the bug was reproduced on that ROM, if it wasn't for that stupid "You must spam 10 times before you may properly report bugs" setting on this forum.
There appears to be some crashes in Chromium in >4.4.4 ROMs, related to this:
https://code.google.com/p/chromium/c...chromium&l=913
These crashes can be triggered by aggressive scrolling in either Chromium itself or any application utilizing libwebviewchromium.so. It will produce something along the lines of:
The "EGL_KHR_fence_sync" OpenGL extension is supposed to be fixed in all Broadcom based devices shipping with Android >4.4.4. Obviously this isn't the case with this platform, as the driver fix got never backported.
There is no point in reporting this upstream to the Chromium team. So .... what to do?
There appears to be some crashes in Chromium in >4.4.4 ROMs, related to this:
https://code.google.com/p/chromium/c...chromium&l=913
These crashes can be triggered by aggressive scrolling in either Chromium itself or any application utilizing libwebviewchromium.so. It will produce something along the lines of:
Code:
E/chromium( 4906): [ERROR:gl_renderer.cc(466)] Reached limit of pending sync queries.
--- snip, several repetions ---
E/chromium( 4906): [ERROR:gl_renderer.cc(466)] Reached limit of pending sync queries.
E/chromium( 4906): [ERROR:gl_fence_egl.cc(34)] Failed to get EGLSync attribute. error code:12300
E/chromium( 4906): [ERROR:gl_fence_egl.cc(50)] Failed to wait for EGLSync. error:EGL_BAD_PARAMETER
F/chromium( 4906): [FATAL:gl_fence_egl.cc(52)] Check failed: g_ignore_egl_sync_failures.
W/google-breakpad( 5032): -----BEGIN BREAKPAD MICRODUMP-----
W/google-breakpad( 5032): V WebView:45.0.2454.95
--- snip ---
F/libc ( 4906): Fatal signal 6 (SIGABRT), code -6 in tid 4961 (RenderThread)
I/DEBUG ( 146): property debug.db.uid not set; NOT waiting for gdb.
I/DEBUG ( 146): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 146): HINT: adb forward tcp:5039 tcp:5039
I/DEBUG ( 146): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 146): Build fingerprint: 'samsung/s2vepxx/s2vep:4.2.2/JDQ39/I9105PXXUBNG1:user/release-keys'
I/DEBUG ( 146): Revision: '5'
I/DEBUG ( 146): ABI: 'arm'
I/DEBUG ( 146): pid: 4906, tid: 4961, name: RenderThread >>> com.google.android.gm <<<
I/DEBUG ( 146): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 146): Abort message: '[FATAL:gl_fence_egl.cc(52)] Check failed: g_ignore_egl_sync_failures.
I/DEBUG ( 146): '
I/DEBUG ( 146): r0 00000000 r1 00001361 r2 00000006 r3 00000000
I/DEBUG ( 146): r4 52ea8dd8 r5 00000006 r6 00000016 r7 0000010c
I/DEBUG ( 146): r8 402c4de4 r9 52ea7ff4 sl 00000000 fp 000001eb
I/DEBUG ( 146): ip 00001361 sp 52ea7b48 lr 40280c59 pc 402a67fc cpsr 600f0010
I/DEBUG ( 146):
I/DEBUG ( 146): backtrace:
I/DEBUG ( 146): #00 pc 000397fc /system/lib/libc.so (tgkill+12)
I/DEBUG ( 146): #01 pc 00013c55 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 146): #02 pc 000149b3 /system/lib/libc.so (raise+10)
I/DEBUG ( 146): #03 pc 000110ed /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 146): #04 pc 0000f5cc /system/lib/libc.so (abort+4)
I/DEBUG ( 146): #05 pc 002b8bf9 /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.soThere is no point in reporting this upstream to the Chromium team. So .... what to do?
Subscribe to:
Posts (Atom)