[Guide] Unlock your bootloader - Galaxy Tab 10.1v Android Development
WARNING
This process will factory reset your device and wipe the internal memory.
You do this at your own risk. I advise you NOT TO DO THIS as there are risks involved, including, but not limited to, bricking your brand new tablet and renderingit useless. You also may void the warranty. I take NO RESPONSIBILITY for any damage. Again, if you decide to follow these steps, it is entirely at your own risk
Prepare:
If you're a Windows user, you might want to refer here. Chainfire has posted an updated stock ROM which does the unlocking for you. If you're a Linux user, you could try flashing Chainfires image using Heimdall but AFAIK, this has not been tested.
Method 1
Download and install the JAVA SDK from here http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download the Android SDK from here http://developer.android.com/sdk/index.html
Follow the instructions here to download the USB drivers http://developer.android.com/sdk/installing.html
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your "<PATH TO ANDROID SDK>\tools" folder
***Do not leave any blank lines before the first “;”
Code:
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
Now to get started…
1) Power off your tablet
2) Hold the VOLUME DOWN button and press the POWER button (your tablet will power on and you will see the BACKUP and USB icons)
3) Use VOLUME DOWN to select the USB icon, and then press VOLUME UP to confirm the selection.
4) You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
5) If Windows doesn’t automatically detect the device, go to device manager and find the ‘Fastboot’ device. Right-click and select update driver, choose to manually install and browse to the “<PATH TO ANDROID SDK>\extras\google\usb_driver\” folder.
6) Open a command prompt and do
Code:
cd "<PATH TO SDK FOLDER>\tools"
fastboot devices
7) Confirm that your device is detected. If it says “waiting for device”, you need to check that the drivers are installed correctly.
8) In the Command window, type:
Code:
fastboot oem unlock
9) On your Tab, Use the VOLUME DOWN button to select YES and then press VOLUME UP to confirm
10) VIOLA! You are unlocked. Note that these instructions are a work-in-progress. As always, your questions and comments are welcome. OSX / Linux instructions coming soon!
Linux Instructions (thanks to Draco32)
Get your Tab into fastboot mode;
1) Power off your Tab and power it back on while holding VOLUME DOWN
2) Highlight the USB icon by pressing VOLUME DOWN
3) Press VOLUME UP to confirm your selection (Fastboot Mode)
4) Download the Tegra 2 compatible fastboot (attached to this post) and put it somewhere in your path (eg /usr/bin)
5) Plug your device into the PC using the provided USB cable.
6) Open a terminal and type
Code:
fastboot devices
this will list the device but it will be a strign of numbers
7) type
Code:
fastboot oem unlock
your tab will then have a yes no option to unlock the bootloader select yes with VOLUME DOWN, and press VOLUME UP to confirm
8) Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Now that you're done head over here to get root access.
EDIT:
ORIGINAL POST:
Guide for unlocking is here:
http://411technology.wordpress.com/
If you power off your device and power it on again using the volume rocker (NOT THE POWER BUTTON), you get the OEM unlock Screen.
Looks like we might have an unlockable bootloader. If so, I love this thing even more now!
Im off to play with it now. Will be back to post pics shortly. Text from the screen is below
Left:
ODIN3 Download Mode
(Protocol v2)
Reason: Force Key
Secure Mode: Secure
Check Signature: Check
OEM Lock: Lock
Waiting USB Cable...
Click to expand...
Click to collapse
Right Hand Side:
Unlock Bootloader?
-------------------------------
If you unlock the bootloader.....
Click to expand...
Click to collapse
(continues on with crap about the risks etc)
Will post pics shortly. Time to break this thing
Fastboot Windows Driver INF File (Galaxy Tab 10.1/v ONLY!)
Code:
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[Google.NTamd64]
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Correct the title - instead of unlockable should be unlocked.
BTW, what's the advantage?
bcmobile said:
EDIT:
Guide for unlocking is here:
http://411technology.wordpress.com/
If you power off your device and power it on again using the volume rocker (NOT THE POWER BUTTON), you get the OEM unlock Screen.
Click to expand...
Click to collapse
It would appear the SGT 10.1v is another Samsung device with a "3 button recovery" lottery. I have been trying every combo of hardware keys from powered off state on mine and am unable to get the screen you have descibed.
I can however get into a "download mode" (Picture of an android dude doing "road works" and a flashing USB symbol with the word "Downloading") on my device - by pressing the power button and then an instant later pressing the left side of the volume rocker (doesn't seem to work if you press them simultaniously).
Hopefully a smart cookie will figure out a way to put a different firmware in with Odin to enable these options on devices like mine (much like the 3BR fix for the SGS).
Edit - Nevermind, got into it. For me it was Press Power, then an instant later volume left and hold both. When you see a screen with a android dude and a usb symbol - pressing right volume gives you the unlock screen, pressing right volume highlights the USB then pressing right volume to select it puts the device in "fastboot" mode.
Woo hoo!!
myself11 said:
Correct the title - instead of unlockable should be unlocked.
BTW, what's the advantage?
Click to expand...
Click to collapse
Since it is not shipped as unlocked, I actually think unlockable is more appropriate
Advantage is that you can flash unsigned ROMs - no hacks required. This is normally only found on the Nexus handsets so it's a pretty big deal for Devs / hackers.
Hi Guys,
I am unable to get the fastboot drivers working. I can install them correctly. ADB devices appears in device manager but when i type i get nothing back. It's like the fastboot device is not connected?
Do i need a newer version of the SDK?
For some reason SDK manager is not working on my PC at work so i am using an older sdk version.
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot devices
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot oem unlock
< waiting for device >
^C
Draco32 said:
Hi Guys,
I am unable to get the fastboot drivers working. I can install them correctly. ADB devices appears in device manager but when i type i get nothing back. It's like the fastboot device is not connected?
Do i need a newer version of the SDK?
For some reason SDK manager is not working on my PC at work so i am using an older sdk version.
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot devices
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot oem unlock
< waiting for device >
^C
Click to expand...
Click to collapse
If you look at the response from "fastboot devices" command it cannot see any devices.
Post your anroid_winusb.inf (\android-sdk-windows\extras\google\usb_driveranroid_winusb.inf) may just be entered in wrong section/misspell
Also what state is it in? your device might just not be in fastboot
P.S. update your SDK no reason not to
Android Driver
Hey,
I'm using the Nexus S driver thats probably the issue. It reads like this at present.
Can you upload the Google USB drivers as the SDK doesn't seem to be working for me.
--------------------android_winusb.inf------------------------------------------
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Yer that looks correct for a 32bit-OS but if your running 64bit-OS put it under "Google.NTamd64"
Also make sure you follow the guide bcmobile post to the letter to get into fastboot
Power off your tablet
Press the VOLUME DOWN button (your tablet will power on and you will see the BACKUP and USB icons)
Use VOLUME UP to select the USB icon, and then press VOLUME DOWN to select it.
You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
If your computer doesn't automatically detect the device, go to device manager and find the 'Fastboot' device. Right-click and select update driver, choose to manually install and browse to the "C:\android-sdk-windows\extras\google\usb_driver\" folder.
Click to expand...
Click to collapse
50-3 said:
Yer that looks correct for a 32bit-OS but if your running 64bit-OS put it under "Google.NTamd64"
Also make sure you follow the guide bcmobile post to the letter to get into fastboot
Click to expand...
Click to collapse
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Draco32 said:
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Click to expand...
Click to collapse
Well if you have the right driver file config and in fastboot only thing left i can think of is that windows hasn't been told to use the driver
If your computer doesn't automatically detect the device, go to device manager and find the 'Fastboot' device. Right-click and select update driver, choose to manually install and browse to the "C:\android-sdk-windows\extras\google\usb_driver\" folder.
Click to expand...
Click to collapse
Or it's an old version of SDK tools but i do think that is it.
Anyway sorry i couldn't have been more help
Draco32 said:
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Click to expand...
Click to collapse
Go into device manager and find the fastboot device. Right click and uninstall it. Unplug the tab and Reboot your PC. Put your tab into fastboot mode before reconnecting
Thanks for pointing out the vol up / down error. I had the old galaxy tab which had them the other way around since it was designed to be used in portrait mode. Ill correct it in the guide later tonight.
Sent from my GT-P7100 using XDA Premium App
bcmobile said:
Advantage is that you can flash unsigned ROMs - no hacks required. This is normally only found on the Nexus handsets so it's a pretty big deal for Devs / hackers.
Click to expand...
Click to collapse
Noob question: but we will still need devs that cook ROM's, right? It isn't as simple as grab Google's update and install it on 10.1v, is it?
myself11 said:
Noob question: but we will still need devs that cook ROM's, right? It isn't as simple as grab Google's update and install it on 10.1v, is it?
Click to expand...
Click to collapse
Unfortunately no, But if were lucky the Devs will push them out quickly
Hi Everyone,
Just to let you know i managed to unlock the bootloader. I used ubuntu linux and fastboot method to get it unlocked.
Get your Tab into fastboot mode;
1. Power + Volume Down
2. Highlight the USB icon by pressing Volume Down
3. Press Volume Up to select the USB icon (Fastboot Mode)
Download the Tegra 2 compatible fastboot from this threadhttp://forum.xda-developers.com/showthread.php?t=1055754;
1. Plug your device into the PC using the provided USB cable.
2. open a terminal and type fastboot devices this will list the device but it will be a strign of numbers
3. type "fastboot oem unlock" your tab will then have a yes no option to unlock the bootloader select yes with Volume Up
5. Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Cheers,
Draco
A little off-topic, but didn't want to open a new topic: is australian radio version different from european version?
Draco32 said:
Hi Everyone,
...
5. Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Click to expand...
Click to collapse
Hi everybody,
I received my 10.1v yesterday (Vodafone, Germany) and have noticed that it allready boots with an unlocked padlock. Does this mean that I have an allready unlocked Tab? This is strange ...
smack said:
Hi everybody,
I received my 10.1v yesterday (Vodafone, Germany) and have noticed that it allready boots with an unlocked padlock. Does this mean that I have an allready unlocked Tab? This is strange ...
Click to expand...
Click to collapse
Cool!
Yes that should mean it's unlocked. Apparently the 10.1 is shipping unlocked as well so I guess I shouldn't be surprised.
If you want to be sure, go into fastboot mode using steps 1-4 above and it should say:
Lock State: UNLOCKED
...on the fastboot screen
unlucky, if I Hold the VOLUME DOWN button and press the POWER button , the tablet goes to the normal UI, I cannot understand.......
I did not see anything about BACKUP and USB icons
For those who are having diffficulties unlocking the bootloader, follow all steps mentioned in the guide, and then enter the device in USB mode but don't plug it to the pc.
Open the cmd and type:
cd "<PATH TO SDK FOLDER>\tools"
fastboot devices
fastboot oem unlock (and it will appear a notification saying waiting for device)
Only nows, in USB mode, plug the tab to the PC.
After that choose in the tab "yes" and your bootloader is unlocked.
Hope this could help!
Related
Modify android_winusb.inf for the 70b IT with ADB
If you have the new 7 It with android 3.2 or android 2.2 for use ADB add on your android_winusb.inf Search [Google.NTx86] Search ;Archos Gen8 Add those two lines %SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1569 %CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1569&MI_01 and also Search [Google.NTamd64] Search ;Archos Gen8 Add those two lines %SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1569 %CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1569&MI_01 and save the file ! Enjoy !!
Tell me if this guide will work (usb driver guide)
It should work, however I'm not sure because my archos is at the factory for repair. please tell me if the guide looks accurate or if it will work. Based the guide off of one from google, one from archos, and took a peak at quinnys. I used the usb drivers from archos and not the one from quinny's post because I think they are the same.. Guide based for windows 7 i put <device> because i dont know how the device appears in device manager, if you know how it appears please let me know
STEP 1: Install adb driver Step 1: Download and extract adb_winusb_driver to a location you will remember. Step 2: On your G9, go into Settings IF you are running Honeycomb: press Applications > Development and check the box "USB debugging" and accept the warning IF you are running Ice Cream Sandwich: press Devolper Options and check the box "USB debugging" and accept the warning Step 2: Connect your G9 to your computer's USB port. Step 3: Right-click on Computer from your desktop or Windows Explorer, and select Manage. Step 4: Select "Devices" or "Device Manager" in the left pane. Step 5: Locate and expand Other device in the right pane. Step 6: Right-click the <device> and select "Update Driver Software..." This will launch the Hardware Update Wizard. Step 7: Select "Browse my computer for driver software" Step 8: Type the path to wherever you extracted the drivers you just downloaded (i.e. C:\adb_winusb_driver\usb_driver) in the box below "Search for driver software in this location:" Step 9: Click Next to install the driver. If you get a notification that says driver is not signed or something similar, continue anyways. It should not harm your device or PC. Step 9: Close any open window you are not using and open a command prompt (press winkey+r or type in cmd in startmenu search) Step 10: Once a command prompt window is open, type (one line at a time. Press enter after each line) Code: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini" adb kill-server adb devices
anyone?
1. It will be clearer if you'd use 'a) honeycomb' and 'b) ICS' instead of 'if you are running....' 2. Does linked driver has both pid's for honeycomb and isc in .inf file? they are different (1621 and 1629 IIRC) Tapatalked from Xperia Arc S
gen_scheisskopf said:
1. It will be clearer if you'd use 'a) honeycomb' and 'b) ICS' instead of 'if you are running....'
2. Does linked driver has both pid's for honeycomb and isc in .inf file? they are different (1621 and 1629 IIRC)
Tapatalked from Xperia Arc S
Click to expand...
Click to collapse
this is the inf
Code:
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
; Archos Gen7
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1361
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1361&MI_01
; Archos HT
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1401
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1401&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1407
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1407&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1409
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1409&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_140B
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_140B&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_140E
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_140E&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1431
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1431&MI_01
;Archos Gen8
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1569
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1569&MI_01
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1501
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1502&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1504&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1506&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1507&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_150A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1511
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1512&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1514&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1516&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1517&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1519&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_151A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1521
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1522&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1524&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1526&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1527&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1529&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_152A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1531
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1532&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1534&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1536&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1537&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1539&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_153A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1541
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1542&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1544&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1546&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1547&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1549&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_154A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1551
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1552&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1554&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1556&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1557&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1559&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_155A&MI_01
[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
; Archos Gen7
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1361
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1361&MI_01
; Archos HT
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1401
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1401&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1407
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1407&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1409
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1409&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_140B
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_140B&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_140E
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_140E&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1431
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1431&MI_01
;Archos Gen8
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1569
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1569&MI_01
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1501
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1502&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1504&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1506&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1507&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_150A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1511
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1512&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1514&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1516&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1517&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1519&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_151A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1521
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1522&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1524&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1526&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1527&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1529&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_152A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1531
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1532&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1534&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1536&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1537&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1539&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_153A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1541
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1542&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1544&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1546&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1547&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1549&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_154A&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1551
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1552&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1554&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1556&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1557&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1559&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_155A&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Nice to get new guide to do this but i just cant get this work Step 10 just wont work. I have installed sdk manager and allmost everything from it etc. I will try now to reboot my computer and uninstall everything about android if this wont work and try again.
Shano56 said: this is the inf Click to expand... Click to collapse Looks good Matenlee said: Nice to get new guide to do this but i just cant get this work Step 10 just wont work. I have installed sdk manager and allmost everything from it etc. I will try now to reboot my computer and uninstall everything about android if this wont work and try again. Click to expand... Click to collapse Did you add path to adb location to environment variables? Shano56, it would be good to add explicit instructions about this (for both linux and windoze). I know it's stated in SDK docs but...
gen_scheisskopf said: Looks good Did you add path to adb location to environment variables? Click to expand... Click to collapse Now i have situation that i have Archos 80 G9 with 4.0.5 (newest official firmware) and windows 7 pc with no installed programs etc. installed for android. Now im going to just follow the guide and install the driver. If i need to do something else too why won´t it read in guide? Would be nice to get this work so i can go to step 2 because i would like to root the device.
Matenlee said: If i need to do something else too why won´t it read in guide? Would be nice to get this work so i can go to step 2 because i would like to root the device. Click to expand... Click to collapse Because how to get adb working "everywhere" in system is written in SDK docs. RTFM people.
gen_scheisskopf said: Because how to get adb working "everywhere" in system is written in SDK docs. RTFM people. Click to expand... Click to collapse Would be easyer to say this clear because there can be more first time android users than me Now i have driver installed but going to download that android sdk and istall it because now it says cant find path at step 10 EDIT: downloaded Android SDK manager and put it install those 9 things it wanted to. So what next? Do i need to install something from that software or install something else to get this work? Shano56 i will go trought all these guides and will give the feedback how to make this so easy that my kind of idiots will survive this. EDIT1: When i try to do Step1 and copy that first line to cmd it says nothing. When i copy second and third it says "The command is not recognized as an internal or external command, program or batch file." (not sure is that but you sure know what i mean. I have diffirent language and just used google translator. Still stuck at the same point :/ Would be super nice to get this work today because im receiving memory card tomorrow and would like to use my device. EDIT2: GOT IT WORK! http://forum.xda-developers.com/showthread.php?t=1413293&page=3 had to follow those rules. I moved the android file folder to C:\ from the program files where it usually put it. Had to copy the folder from android folder to get it like that guys guide and other guy questions.
@Gen i was planning on tut for system path next thanks for reminding me though, i'll get to it asap Matenlee said: Shano56 i will go trought all these guides and will give the feedback how to make this so easy that my kind of idiots will survive this. EDIT1: When i try to do Step1 and copy that first line to cmd it says nothing. When i copy second and third it says "The command is not recognized as an internal or external command, program or batch file." (not sure is that but you sure know what i mean. I have diffirent language and just used google translator. Still stuck at the same point :/ Would be super nice to get this work today because im receiving memory card tomorrow and would like to use my device. EDIT2: GOT IT WORK! http://forum.xda-developers.com/showthread.php?t=1413293&page=3 had to follow those rules. I moved the android file folder to C:\ from the program files where it usually put it. Had to copy the folder from android folder to get it like that guys guide and other guy questions. Click to expand... Click to collapse thank you! and the reason you get it to work when you put it in c:\ is because it's not in the system path yet. i'm going to write up a tutorial in a bit for that
[Q][KFHD7]Can't mount /data
Alright, So I'll admit I messed up the whole process and I'm basically trying to unbrick it at this point. I installed TWRP 2.4.4.0 on my KFHD 7" wiped everything then realized I never pushed the fioles to flash onto the KF before I did this. After messing around with my adb drivers for a while (I had to spoof them and add values to the android_usb.inf for it to even show up now) I can use adb while in TWRP and it shows my device as "recovery" I was able to push files to it earlier, but now I can't mount "/data" which is where I pushed those files earlier. I do have a stock-boot.img a stock-recovery.img and a stock-system.img (Or at least I hope, Idk if it got wiped) I'm not all to familiar with adb or fastboot commands to know what I can do to get anything back or at least get /data back. If any of y'all could help me out, that'd be great, otherwise I now have a really expensive paper-weight. 1 more thing. I don't have ADB when I'm in fastboot. It shows up as an "Android composite ADB interface" in Device manager, but when I run adb (even after restarts) it never shows up in adb devices. Once again I had to spoof that driver because it was showing up as "Unknown Device' (I checked hardware ID's and it was the kindle 0x1949 that I installed the drivers for) KFFA Isn't seeming to work, I've tried there drivers as well, no dice while the Kindle is in TWRP or in Fastboot. I have the SDK and my own custom ADB Drivers installed, If you want me to post the .inf here for reference, I can. EDIT: Okay, I've really screwed up, i flashed the stock boot, now all I get is a orange kindle fire logo. and so far IDK how to get into recovery. The logo doesn't animate at all, I'm guessing I have no OS installed, I think I just bricked it for good, unless I can get into a fastboot. HELP!!!
Android_usb.inf These are reflected in both NTx86 and NTamd64 Code: ;Kindle Fire #These are the HW ID's for Amazon Kindle Fire OS %SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006 %CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01 ;Kindle Fire #These are the HW ID's for Fastboot %SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0007 %CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0100 ;Kindle Fire HD 7 #These are the HW ID's for TWRP %SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216
Solved: Problem whit odin fail & secure download enable
- - WORKING IN ALL VARIANT NOTE 5 - - Flashing your smartphone via Odin , But ODIN could Not recognize the phone and the blue box doesnt appear - - - Unlock the boot loader you need to have the ADT with all the packages installed and configured. Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options. Download Modaco’s Superboot files and save them to your computer. Once downloaded, extract it by right clicking and extract all. On your phone, click on Settings > Developer Options > Turn USB Debugging On. Plug the device in to your computer via USB cable. Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area. Now, select open command window here. In the command prompt, type the following with hitting enter at the end of each line. - - Copy and page in cmd: adb-windows reboot bootloader fastboot-windows oem unlock and wait for the device to reboot (no necesary) In case you phone not restart : reboot.... Then you turn on the phone Then you power off on the phone Then install your current firmware: .md5 optional: Galaxy Note Series Firmware and enjoy LINK : https://mega.nz/#F!iIE0yYqQ!2nskXbsvwWMn1OBM1LXm8A - - VIDEO TUTORIAL - - Credits: @Adil_mac
wow thanks ... is this means I can downgrade to 5.1.1 ?
when i type in cmd adb-windows reboot bootloader the phone reboots on normal user and the tut video not available can u make one please
Vídeo not reproducing.
{
"cpn": "eqo_KnbfUuNy8rKd",
"vct": "0.000",
"vd": "NaN",
"vpl": "",
"vbu": "",
"vpa": true,
"vsk": false,
"ven": false,
"vpr": 1,
"vrs": 0,
"vns": 0,
"vec": null,
"vvol": 1,
"state": "80",
"debug_error": {
"errorCode": "api.invalidparam",
"errorDetail": "invalidVideodata.1",
"message": "Se produjo un error. Vuelve a intentarlo más tarde.",
"messageKey": "YTP_ERROR_GENERIC_WITHOUT_LINK"
},
"relative_loudness": "0.000",
"0sz": false,
"op": "",
"yof": false,
"dis": "",
"gpu": "Mali-T760",
"cgr": true,
"debug_playbackQuality": "unknown",
"debug_date": "Mon Apr 03 2017 20:11:07 GMT-0600 (CST)"
}
Link is broken
[KEYLAYOUT] Hungarian keyboard for Droid 4
Hungarian has 9 special characters: áéíóöőúüű. Using this tutorial I remapped the keylayout as follows: 1. 'sym' + 'a' = 'á' 2. 'sym' + 'e' = 'é' 3. 'sym' + 'i' = 'í' 4. 'sym' + 'o' = 'ó' 5. 'sym' + 'u' = 'ú' 6. 'sym' + '7' = 'ü' 7. 'sym' + '8' = 'ű' 8. 'sym' + '9' = 'ö' 9. 'sym' + '0' = 'ő' Shift & capslock gives you the capital ÁÉÍÓÖŐÚÜŰ, of course. For the changes to take effect, you have to have root access, and replace the following 7 original files in the /system/usr folder to my 7 attached modified files (in zip) using Cyanogenmod / Lineage OS file manager app (or any other root explorer app, e.g. the premium version of File Expert): 1. /system/usr/keylayout/Generic.kl 2. /system/usr/keylayout/omap4-keypad.kl 3. /system/usr/keylayout/qwerty.kl 4. /system/usr/keychars/Generic.kcm 5. /system/usr/keychars/omap4-keypad.kcm 6. /system/usr/keychars/qwerty.kcm 7. /system/usr/keychars/qwerty2.kcm Don't forget to set the permissions of all the 7 new files using the above mentioned tutorial as follows: OWNER: READ & WRITE GROUP: READ ALL: READ After that, restart your Droid 4 - you'll have a fully functional HUNGARIAN layout physical keyboard.