Hello everyone. As you know, ever since the whole stagefright bug thing and google & other companies said they will be launching regular OTA updates on a monthly basis.
I'm using window 8.1 x64
Android version Lollipop 5.1.1 LMY48B
USB debugging and MTP are ENABLED.
My nexus 5 is NOT rooted, I have some system apps DISABLED from app settings, I HAD CUSTOM recovery (latest twrp) to use teenf00t's (Nexus 5 real volume booster).
But now STOCK recovery is flashed and volume xml paths files were set back to default
NO CUTOM ROM's or anything else.
Still couldn't use OTA update normally :(
And since I can't download & flash a whole new system img and back up & restore my data just for a 10 mb update every month, I need to ADB sideload the OTA update , and here comes the problem .
Obviously, when my nexus is connected when it's turned on or in bootloader, nothing is wrong. As soon as I get into recovery mode and the device becomes undetected.
I tried EVERYTHING I could find which is :
1- Got the latest Minimal ADB & Fastboot installed
2- Used latest ADB & drivers 15 seconds installer
3- Latest google USB drivers
4- Lg united mobile driver
5- Manually assign composite ADB interface driver to nexus in "portable devices" when it's connected in recovery mode.
6- Modify "android_winusb.inf" file with the hardware ID of the nexus found in the inactive "composite ADB interface" driver when connected in recovery, and installing it using advanced windows 8 boot to remove digital signature verification requirement :
In the x64 & x86 "nexus generic" tab of inf file I replaced this line :
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
with this :
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&REV_0232&MI_01
7- I tried different USB ports
8- Made sure ADB runs in compatibility mode with windows 8 but its process still shows "ADB 32"
And ofc, when removing or installing drivers or ADB, I made sure the previous ones were uninstalled and restarted pc when necessary.
What the hell can I do for this damn thing to work ??!! :eek: :mad:
I'm using window 8.1 x64
Android version Lollipop 5.1.1 LMY48B
USB debugging and MTP are ENABLED.
My nexus 5 is NOT rooted, I have some system apps DISABLED from app settings, I HAD CUSTOM recovery (latest twrp) to use teenf00t's (Nexus 5 real volume booster).
But now STOCK recovery is flashed and volume xml paths files were set back to default
NO CUTOM ROM's or anything else.
Still couldn't use OTA update normally :(
And since I can't download & flash a whole new system img and back up & restore my data just for a 10 mb update every month, I need to ADB sideload the OTA update , and here comes the problem .
Obviously, when my nexus is connected when it's turned on or in bootloader, nothing is wrong. As soon as I get into recovery mode and the device becomes undetected.
I tried EVERYTHING I could find which is :
1- Got the latest Minimal ADB & Fastboot installed
2- Used latest ADB & drivers 15 seconds installer
3- Latest google USB drivers
4- Lg united mobile driver
5- Manually assign composite ADB interface driver to nexus in "portable devices" when it's connected in recovery mode.
6- Modify "android_winusb.inf" file with the hardware ID of the nexus found in the inactive "composite ADB interface" driver when connected in recovery, and installing it using advanced windows 8 boot to remove digital signature verification requirement :
In the x64 & x86 "nexus generic" tab of inf file I replaced this line :
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
with this :
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&REV_0232&MI_01
7- I tried different USB ports
8- Made sure ADB runs in compatibility mode with windows 8 but its process still shows "ADB 32"
And ofc, when removing or installing drivers or ADB, I made sure the previous ones were uninstalled and restarted pc when necessary.
What the hell can I do for this damn thing to work ??!! :eek: :mad:
Aucun commentaire:
Enregistrer un commentaire