hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
Just got my 2nd gen in the mail today, started reading up on how to root 10.2.4, was feeling good about it, ready to get started and noticed that it was in the middle of upgrading to 10.2.6. guess I'll be following this thread, hope something comes along soon...
How To: Root the Kindle Fire 7" 2 with Windows - Version 10.2.6
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
inflicted_1999,
I am sorry to hear your frustrations around Rooting the Kindle Fire 2 version 10.2.6, this can be a bugger to Root. I have an idea that may help you. When you have a yellow triangle over MTP, this is a strong sign that the driver is not functional. When you have the combination of, one Android Composite ADB Interface with the yellow triangle over MTP, you have a driver failure. Having said this, none of the utilities will work until you have a functional driver. Just FYI Windows Media Player is not needed to get the Kindle to Root. Once you have successfully installed the driver Android Composite ADB Interface will change to Android ADB Interface and the MTP will change to Portable Devices > Kindle. You will also know the driver install was successful when you get a pop-up asking what to do with the Kindle Drive - like sync it with your MP3 collection.
If you already tried Part A for the driver, here are the key points:
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/show...php?p=36373627
A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle.
Please open an Administrative CMD Prompt and enter:
Code:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.
Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
This worked for me
inflicted_1999 said:
hi i have read numerous posts and tried many tutorials on here but cant seem to get anywhere with my kindle
fire i believe its a kindle fire 2nd gen as sytem version is 10.2.6
im using win xp on my pc and in device manager i have
kindle fire - android composite ADB interface
MTP has exclamation mark by it and wont load any drivers i have windows media player 11 installed.
it doesnt show up in my computer at all which i think is where the problem may lie
can anyone point me in the right direction on turning my kindle fire into an android device
and not amazon.... thanks in advance
Click to expand...
Click to collapse
I’m a n00b to this, but this worked for me. I had root than lost it because I didn’t disable auto update. The only way I could get root back is like this.
1. Use Prokennexusa steps to get your comp talking to your kindle, if you run win 7 or Vista make sure you heed the warning. Next find and download “Root_with_Restore_by_Bin4ry_v18” to your desktop and make two copies of it. The name of the folder does not matter you just need two copies of the program, I’ll explain in a minute. I don’t have a download link but it’s on the forum just search for it.
2. Pick one of the two “Root_with_Restore_by_Bin4ry_v18” to modify, you need to modify it to kick the kindle in the head and allow the original to work.open the folder of the one you want to modify and right click on the “RunMe.bat” and click edit. Highlight everything in it and delete. Then copy this in its place.
Code:
@echo off
COLOR 0A
echo ======================================================================
echo = This script will root your Android phone with adb restore function =
echo = Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
echo = Idea for Tablet S from Fi01_IS01 =
echo = (18.12.2012) v17 =
echo ======================================================================
echo.
:CHOICE
set nxt=0
set ric=0
echo Device type:
echo 1) Normal
echo 2) Special (for example: Sony Tablet S, Medion Lifetab)
echo.
echo x) Unroot
echo.
set /p type=Make a choice:
if %type% == 1 GOTO TEST
if %type% == 2 GOTO TABSMENU
if %type% == x GOTO UNROOT
echo.
echo Please Enter a valid number (1 to x)
echo.
GOTO CHOICE
:TEST
echo Checking if i should run in Normal Mode or special Sony Mode
echo Please connect your device with USB-Debugging enabled now
echo Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
stuff\adb.exe wait-for-device
stuff\adb.exe pull /system/app/Backup-Restore.apk . > NUL
stuff\adb.exe pull /system/bin/ric . > NUL
if EXIST ric (set ric=1) else (echo .)
if EXIST Backup-Restore.apk (GOTO XPS) else (echo .)
GOTO OTHER
:UNROOT
set /p unr=Really (y/n) ?
IF %unr% == n GOTO CHOICE
stuff\adb.exe push stuff\busybox /sdcard/Documents/busybox
stuff\adb.exe shell "chmod 755 /sdcard/Documents/busybox"
stuff\adb.exe shell "su -c '/sdcard/Documents/busybox mount -o remount,rw /system'"
stuff\adb.exe shell "su -c 'rm /system/xbin/su'"
stuff\adb.exe shell "su -c 'rm /system/app/Superuser.apk'"
GOTO FINISH
:TABSMENU
echo.
echo Special mode:
echo 1) Root
echo 2) Rollback
set /p tabtype=Make a choice:
if %tabtype% == 1 GOTO TABS
if %tabtype% == 2 GOTO TABS_RB
:TABS
echo.
echo Tablet S mode enabled!
echo.
GOTO START
:XPS
echo.
echo Found Sony Backup-Restore.apk
echo LT26,LT22 etc. mode enabled!
echo.
del Backup-Restore.apk
if %ric% == 1 (del ric) else (echo .)
set NXT=1
GOTO START
:TABS_RB
echo.
echo Tablet S Roll Back
echo.
echo Please connect device with ADB-Debugging enabled now....
stuff\adb.exe wait-for-device
FOR /F "tokens=1 delims=" %%A in ('stuff\adb.exe shell "if [ -d /data/app- ]; then echo 1 ; else echo 0 ; fi"') do SET tabs_app=%%A
if %tabs_app% == 1 GOTO TABS_RB_1
if %tabs_app% == 0 GOTO TABS_RB_2
:TABS_RB_1
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a/*"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while [ ! -d /data/data/com.android.settings/a/file99 ] ; do echo 1; done" > NUL
echo 1st RESTORE OK, hit ENTER to continue.
pause
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; [ -f /data/file99 ] && exit; done" > NUL
stuff\adb.exe shell "rm -r /data/file99"
echo Achieved! hit ENTER to continue.
echo.
pause
stuff\adb.exe shell "mv /data/system /data/system3"
stuff\adb.exe shell "mv /data/system- /data/system"
stuff\adb.exe shell "mv /data/app /data/app3"
stuff\adb.exe shell "mv /data/app- /data/app"
echo "Roll back compelted."
GOTO FINISH
:TABS_RB_2
echo.
echo.
echo "Roll back failed. /data/app- not found."
echo.
echo.
GOTO FINISH
:eek:THER
echo.
echo Normal Mode enabled!
if %ric% == 1 (del ric) else (echo .)
echo.
:START
stuff\adb.exe wait-for-device
IF %type% == 2 GOTO TABTRICK
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /sdcard/Documents/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /sdcard/Documents/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /sdcard/Documents/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /sdcard/Documents/busybox
if %ric% == 1 (stuff\adb.exe push stuff/ric /sdcard/Documents/ric) else (echo .)
IF %nxt% == 1 GOTO XPSTRICK
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device in 10 seconds!
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
GOTO NORMAL
:TABTRICK
stuff\adb.exe install -s stuff/Term.apk
stuff\adb.exe push stuff/busybox /sdcard/Documents/.
stuff\adb.exe push stuff/su /sdcard/Documents/.
stuff\adb.exe push stuff/Superuser.apk /sdcard/Documents/.
stuff\adb.exe push stuff/rootkittablet.tar.gz /sdcard/Documents/rootkittablet.tar.gz
stuff\adb.exe shell "chmod 755 /sdcard/Documents/busybox"
stuff\adb.exe shell "/sdcard/Documents/busybox tar -C /data/local/tmp -x -v -f /sdcard/Documents/rootkittablet.tar.gz"
stuff\adb.exe shell "chmod 644 /sdcard/Documents/VpnFaker.apk"
stuff\adb.exe shell "touch -t 1346025600 /sdcard/Documents/VpnFaker.apk"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/_su"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/su"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/onload.sh"
stuff\adb.exe shell "chmod 755 /sdcard/Documents/onload2.sh"
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a/*"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while [ ! -d /data/data/com.android.settings/a/file99 ] ; do echo 1; done" > NUL
ping -n 3 127.0.0.1 > NUL
echo 1st RESTORE OK, hit ENTER to continue.
pause
stuff\adb.exe shell "rm -r /data/data/com.android.settings/a"
stuff\adb.exe restore stuff/tabletS.ab
echo Please look at your device and click "Restore my data"
echo.
stuff\adb.exe shell "while : ; do ln -s /data /data/data/com.android.settings/a/file99; [ -f /data/file99 ] && exit; done" > NUL
stuff\adb.exe shell "rm -r /data/file99"
ping -n 3 127.0.0.1 > NUL
echo Achieved! hit ENTER to continue.
echo.
pause
stuff\adb.exe shell "/sdcard/Documents/busybox cp -r /data/system /data/system2"
stuff\adb.exe shell "/sdcard/Documents/busybox find /data/system2 -type f -exec chmod 666 {} \;"
stuff\adb.exe shell "/sdcard/Documents/busybox find /data/system2 -type d -exec chmod 777 {} \;"
stuff\adb.exe shell "mv /data/system /data/system-"
stuff\adb.exe shell "mv /data/system2 /data/system"
stuff\adb.exe shell "mv /data/app /data/app-"
stuff\adb.exe shell "mkdir /data/app"
stuff\adb.exe shell "mv /sdcard/Documents/VpnFaker.apk /data/app"
stuff\adb.exe shell "/sdcard/Documents/busybox sed -f /sdcard/Documents/packages.xml.sed /data/system-/packages.xml > /data/system/packages.xml"
stuff\adb.exe shell "sync; sync; sync"
echo Need to reboot now!
stuff\adb.exe reboot
ping -n 3 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
echo Unlock your device, a Terminal will show now, type this 2 lines, after each line press ENTER
echo /sdcard/Documents/onload.sh
echo /sdcard/Documents/onload2.sh
echo after this is done press a key here in this shell to continue!
echo If the shell on your device does not show please re-start the process!
stuff\adb.exe shell "am start -n com.android.vpndialogs/.Term"
pause
GOTO TABTRICK1
:TABTRICK1
stuff\adb.exe push stuff/script1.sh /sdcard/Documents/.
stuff\adb.exe shell "chmod 755 /sdcard/Documents/script1.sh"
stuff\adb.exe shell "/sdcard/Documents/script1.sh"
echo Almost complete! Reboot and cleanup.
stuff\adb.exe reboot
ping -n 3 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
stuff\adb.exe shell "su -c 'rm -r /data/app2'"
stuff\adb.exe shell "su -c 'rm -r /data/system2'"
stuff\adb.exe shell "su -c 'rm -r /sdcard/Documents/*'"
GOTO FINISH
:XPSTRICK
set %NXT%=0
echo Pushing fake Backup
stuff\adb.exe push stuff\RootMe.tar /sdcard/Documents/RootMe.tar
stuff\adb.exe shell "mkdir /mnt/sdcard/.semc-fullbackup > /dev/null 2>&1"
echo Extracting fakebackup on device ...
stuff\adb.exe shell "cd /mnt/sdcard/.semc-fullbackup/; /sdcard/Documents/busybox tar xf /sdcard/Documents/RootMe.tar"
echo Watch now your device. Select the backup named RootMe and restore it!
stuff\adb.exe shell "am start com.sonyericsson.vendor.backuprestore/.ui.BackupActivity"
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ......
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo.
echo Good, it worked! Now we are rebooting soon, please be patient!
ping -n 3 127.0.0.1 > NUL
stuff\adb.exe shell "rm -r /mnt/sdcard/.semc-fullbackup/RootMe"
stuff\adb.exe reboot
ping -n 10 127.0.0.1 > NUL
echo Waiting for device to come up again....
stuff\adb.exe wait-for-device
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/sdcard/Documents/busybox mount -o remount,rw /system && /sdcard/Documents/busybox mv /sdcard/Documents/su /system/xbin/su && /sdcard/Documents/busybox mv /sdcard/Documents/Superuser.apk /system/app/Superuser.apk && /sdcard/Documents/busybox cp /sdcard/Documents/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
:RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/sdcard/Documents/busybox mount -o remount,rw /system && /sdcard/Documents/busybox mv /sdcard/Documents/ric /system/bin/ric && chmod 755 /system/bin/ric && /sdcard/Documents/busybox mv /sdcard/Documents/su /system/xbin/su && /sdcard/Documents/busybox mv /sdcard/Documents/Superuser.apk /system/app/Superuser.apk && /sdcard/Documents/busybox cp /sdcard/Documents/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
GOTO FINISH
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
This is the original code with initial drop locations changed to insure the software gets on the device. close it and save changes.
Double click on “RunMe.bat” to launch on the modified one (it worked for me without using “run as Admin, as a matter of fact, it would not run with elevateded so just double click and follow the on screen instructions).
When it gets done you may see a flash of “kindle fire” on the screen, that’s because its stumbling (good thing) when you have this done run the original “Root_with_Restore_by_Bin4ry_v18” unchanged and follow all instructions.
You should be rooted after that. Load all your google apk’s and enjoy!:good:
I in no way take credit for the code, I just changed the drop location on a hunch and it worked, props to the developer, not me.
As always if you brick it, it’s on you. This worked for me
prokennexusa said:
inflicted_1999,
I am sorry to hear your frustrations around Rooting the Kindle Fire 2 version 10.2.6, this can be a bugger to Root. I have an idea that may help you. When you have a yellow triangle over MTP, this is a strong sign that the driver is not functional. When you have the combination of, one Android Composite ADB Interface with the yellow triangle over MTP, you have a driver failure. Having said this, none of the utilities will work until you have a functional driver. Just FYI Windows Media Player is not needed to get the Kindle to Root. Once you have successfully installed the driver Android Composite ADB Interface will change to Android ADB Interface and the MTP will change to Portable Devices > Kindle. You will also know the driver install was successful when you get a pop-up asking what to do with the Kindle Drive - like sync it with your MP3 collection.
If you already tried Part A for the driver, here are the key points:
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/show...php?p=36373627
A) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle.
Please open an Administrative CMD Prompt and enter:
Code:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Note: We have seen quite a few cases when the driver "fails to install". This message is normally erroneous and can usually be ignored. Plug in your Kindle, then look in the Windows Device Manager to see if the main driver installed.
Our friends at RevTV Created this video which outlines How to install ADB: How to Install ADB Video
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Click to expand...
Click to collapse
thanks for your help i have tried all the above options yet i still have a prob with MTP not doing anything and i cant see kindle in
mycomputer adb sees it as an attached device...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pic attached
of my device manager
Kindle Fire 2 7" - How To Install ADB Drivers On Windows
inflicted_1999 said:
thanks for your help i have tried all the above options yet i still have a prob with MTP not doing anything and i cant see kindle in
mycomputer adb sees it as an attached device...
pic attached
of my device manager
Click to expand...
Click to collapse
inflicted_1999,
We know this one. Once you get the driver installed, the following will happen:
MTP will change to Portable Devices > Kindle
Unknown will change to Kindle > Android ADB Interface
Now, how do you accomplish this task? Take these steps:
Take 3 minutes and watch this video, please: How to Install ADB Video
This video will help you to understand the manual installation method for the next driver. Please download: usb_driver
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Other Devices in the right pane.
5. Right-click Unknown Device and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9. Click Next to upgrade the driver. Sometimes this triggers MTP to update, if this happens stop here and begin the Root procedure as outlined here: http://forum.xda-developers.com/showthread.php?t=2069117 - otherwise proceed to step the next step to update MTP.
10. Locate and expand Other Devices in the right pane.
11. Right-click MTP and select Update Driver. This will launch the Hardware Update Wizard.
12. Select Install from a list or specific location and click Next.
13. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
14. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
15. Click Next to upgrade the driver.
Once the driver installs correctly, you will see a drive named "Kindle" in My Computer and there will be no more Yellow marks in Windows Device Manager.
prokennexusa said:
inflicted_1999,
We know this one. Once you get the driver installed, the following will happen:
MTP will change to Portable Devices > Kindle
Unknown will change to Kindle > Android ADB Interface
Now, how do you accomplish this task? Take these steps:
Take 3 minutes and watch this video, please: How to Install ADB Video
This video will help you to understand the manual installation method for the next driver. Please download: usb_driver
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Other Devices in the right pane.
5. Right-click Unknown Device and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9. Click Next to upgrade the driver. Sometimes this triggers MTP to update, if this happens stop here and begin the Root procedure as outlined here: http://forum.xda-developers.com/showthread.php?t=2069117 - otherwise proceed to step the next step to update MTP.
10. Locate and expand Other Devices in the right pane.
11. Right-click MTP and select Update Driver. This will launch the Hardware Update Wizard.
12. Select Install from a list or specific location and click Next.
13. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
14. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
15. Click Next to upgrade the driver.
Once the driver installs correctly, you will see a drive named "Kindle" in My Computer and there will be no more Yellow marks in Windows Device Manager.
Click to expand...
Click to collapse
sorry to be a complete pain whenever i try to update driver from the \usb_driver\ folder it says this location
doesnt contain information about your device....
Kindle Fire HD and 2 Root Problem - ADB Driver Problem
inflicted_1999 said:
sorry to be a complete pain whenever i try to update driver from the \usb_driver\ folder it says this location
doesnt contain information about your device....
Click to expand...
Click to collapse
inflicted_1999,
You are not being a pain, sometimes it takes several posts - I have seen up to 10 - to resolve a difficult situation. OK, so what is your Operating System?
Please drop to a Command and type the following:
Code:
ping 4.2.2.2
Does this respond with packets? If the response is something like "no internal or external command can be found...", then proceed to patch you computer using this post: http://forum.xda-developers.com/showthread.php?t=2086210 - when you are done please post "completed, moving on to Root" in that thread, not this one.
Finally, do you get an error when you install the original driver or did it install without error? Do you have ADB Enabled under the Device Tab? Do you have any security software installed like Norton Internet Security? Do you have plenty of free disk drive space?
prokennexusa said:
inflicted_1999,
You are not being a pain, sometimes it takes several posts - I have seen up to 10 - to resolve a difficult situation. OK, so what is your Operating System?
Please drop to a Command and type the following:
Code:
ping 4.2.2.2
Does this respond with packets? If the response is something like "no internal or external command can be found...", then proceed to patch you computer using this post: http://forum.xda-developers.com/showthread.php?t=2086210 - when you are done please post "completed, moving on to Root" in that thread, not this one.
Finally, do you get an error when you install the original driver or did it install without error? Do you have ADB Enabled under the Device Tab? Do you have any security software installed like Norton Internet Security? Do you have plenty of free disk drive space?
Click to expand...
Click to collapse
Hi mate thanks for helping... my laptop is running XP pro service pack 3
i get replies from pinging 4.2.2.2
the original drivers installed and said ready to use
i dont have any security software installed at all as its a fresh install, i installed win 7
before this copy of xp and had the same issues...
How To Root Kindle Fire 2 Software Version 10.2.6
inflicted_1999 said:
Hi mate thanks for helping... my laptop is running XP pro service pack 3
i get replies from pinging 4.2.2.2
the original drivers installed and said ready to use
i dont have any security software installed at all as its a fresh install, i installed win 7
before this copy of xp and had the same issues...
Click to expand...
Click to collapse
inflicted_1999,
OK, so we know the variables are OK, now let's dig into ADB, please open a command prompt:
Code:
adb kill-server
adb start-server
adb devices
If the commands work you need to remove the Android SDK prior to using Root MANY ANDROID. Please reply back with the progress.
prokennexusa said:
inflicted_1999,
OK, so we know the variables are OK, now let's dig into ADB, please open a command prompt:
Code:
adb kill-server
adb start-server
adb devices
If the commands work you need to remove the Android SDK prior to using Root MANY ANDROID. Please reply back with the progress.
Click to expand...
Click to collapse
hi mate those commands seem to work as i now have a command prompt with
list of devices attached
D026A024350CJH device
Root the Kindle Fire 2 with Windows - Noob (Simple) Version
inflicted_1999 said:
hi mate those commands seem to work as i now have a command prompt with
list of devices attached
D026A024350CJH device
Click to expand...
Click to collapse
inflicted_1999,
Beautiful, you are ready! First we MUST get rid of Android SDK since Root MANY ANDROID will fail with the SDK installed. So either go to Windows Add/Remove Programs and remove the Android SDK or use Windows Search - find the folder named "platform-tools", one you find it, rename it to "platform-tools-bak".
Once you have renamed or removed the SDK, then we can Root the Kindle Fire 2:
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18 folder.
Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v18 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
The forum notes can be found here: Root MANY ANDROID! Forum.
Root Step 2: When the Kindle reboots it will have Root.
Root Step 3: Please navigate to the Apps Folder and find Superuser on the Device, click to Launch Superuser, then Reboot.
You are now Rooted, you may move on to How to Install Google Play Store here: http://forum.xda-developers.com/showthread.php?p=35962244
prokennexusa said:
inflicted_1999,
Beautiful, you are ready! First we MUST get rid of Android SDK since Root MANY ANDROID will fail with the SDK installed. So either go to Windows Add/Remove Programs and remove the Android SDK or use Windows Search - find the folder named "platform-tools", one you find it, rename it to "platform-tools-bak".
Once you have renamed or removed the SDK, then we can Root the Kindle Fire 2:
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v18 folder.
Next Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v18 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v18 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v18 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
The forum notes can be found here: Root MANY ANDROID! Forum.
Root Step 2: When the Kindle reboots it will have Root.
Root Step 3: Please navigate to the Apps Folder and find Superuser on the Device, click to Launch Superuser, then Reboot.
You are now Rooted, you may move on to How to Install Google Play Store here: http://forum.xda-developers.com/showthread.php?p=35962244
Click to expand...
Click to collapse
that all seemed to work ok and i opened superuser etc... to load google play etc i need to see the kindle on win xp
dont i which i still cant unfortunately ... is there another way other than through my computer
is it worth me reloading with vista win 7 again or win 8 is that easier to connect than xp
How to Access Files Over WiFi - Kies Air - Attached
inflicted_1999 said:
that all seemed to work ok and i opened superuser etc... to load google play etc i need to see the kindle on win xp
dont i which i still cant unfortunately ... is there another way other than through my computer
is it worth me reloading with vista win 7 again or win 8 is that easier to connect than xp
Click to expand...
Click to collapse
inflicted_1999,
Great work inflicted_1999, so you did make it through your rooting problem, good job! OK, I have another idea to accress the Kindle but let's first identify what may be causing the mounting trouble. Can you please go into your windows System by pressing the Windows Key (found between the CTRL and ALT Keys) with the pause/break key - this keyboard shortcut will open the Windows System, next select the Windows Device Manager. What do you see here? You should see:
Kindle > Android ADB Interface
Portable Device > Kindle
If you see a yellow triangle, please reply with the identification of the Yellow Triangle like "Unknown Device".
The other option is to install the attached service Kies Air, it will allow you to access and upload files to your Kindle Fire HD and 2. This is a WiFi file manager.
Kies Air - Attached to this Thread
It’s time to share wirelessly!
Why not manage your mobile device via your Internet browser?
Kies Air is a application that enables you to easily manage contents saved on your device via PC internet or mobile browser using Wi-Fi technology.
Without having to connect any cables, within a browser you can use diverse function such as multimedia transfer, music listening, PIMS management, text message, file search, and so on.
Since Kies Air is an application for accessing mobile content from a PC or browser, the application has to read the content from the mobile device in order to carry out this function. To ensure that your data is secure and not shared without your consent, when you install/update an application, Kies Air will ask you to grant permission.
To access via PC or laptop:
1. Connect the mobile device and the PC or laptop to the same access point (Wi-Fi router)
2. Open Kies Air on the mobile device and tap Start
3. Kies Air on the mobile device will display a URL. Enter the URL in the browser on the PC or laptop
4. Kies Air will display a 4-digit PIN on the mobile device. When prompted, enter the PIN into the browser on the PC or laptop
5. The PC or laptop is now connected and you can access the content of your mobile device.
You can also create a desktop icon to connect to Kies Air more easily
After creating the desktop icon, you can access Kies Air without having to enter the URL into the browser on the PC or laptop
To access via another mobile device (e.g. device B accesses device A):
1. Connect both mobile devices (A and B) to the same access point (Wi-Fi router)
2. Open Kies Air on device A and tap Start
3. Open Kies Air on device B and shake the device twice. This will start a scan for device A
4. Device A will appear on the screen of device B. Tap on device A
5. Kies Air will display a PIN on device A. When prompted, enter the PIN on device B
If Kies Air is not installed on device B, enter the URL displayed by device A into the browser on device B.
If the motion feature is not supported on device B, press the menu key, and then tap Scan.
During installation, Kies Air requests permission to provide you with access to content or other required functions. Your data is only ever accessible within your local network and never sent to the Kies Air team, Samsung, or any other remote server.
prokennexusa said:
inflicted_1999,
Great work inflicted_1999, so you did make it through your rooting problem, good job! OK, I have another idea to accress the Kindle but let's first identify what may be causing the mounting trouble. Can you please go into your windows System by pressing the Windows Key (found between the CTRL and ALT Keys) with the pause/break key - this keyboard shortcut will open the Windows System, next select the Windows Device Manager. What do you see here? You should see:
Kindle > Android ADB Interface
Portable Device > Kindle
If you see a yellow triangle, please reply with the identification of the Yellow Triangle like "Unknown Device".
The other option is to install the attached service Kies Air, it will allow you to access and upload files to your Kindle Fire HD and 2. This is a WiFi file manager.
Kies Air - Attached to this Thread
It’s time to share wirelessly!
Why not manage your mobile device via your Internet browser?
Kies Air is a application that enables you to easily manage contents saved on your device via PC internet or mobile browser using Wi-Fi technology.
Without having to connect any cables, within a browser you can use diverse function such as multimedia transfer, music listening, PIMS management, text message, file search, and so on.
Since Kies Air is an application for accessing mobile content from a PC or browser, the application has to read the content from the mobile device in order to carry out this function. To ensure that your data is secure and not shared without your consent, when you install/update an application, Kies Air will ask you to grant permission.
To access via PC or laptop:
1. Connect the mobile device and the PC or laptop to the same access point (Wi-Fi router)
2. Open Kies Air on the mobile device and tap Start
3. Kies Air on the mobile device will display a URL. Enter the URL in the browser on the PC or laptop
4. Kies Air will display a 4-digit PIN on the mobile device. When prompted, enter the PIN into the browser on the PC or laptop
5. The PC or laptop is now connected and you can access the content of your mobile device.
You can also create a desktop icon to connect to Kies Air more easily
After creating the desktop icon, you can access Kies Air without having to enter the URL into the browser on the PC or laptop
To access via another mobile device (e.g. device B accesses device A):
1. Connect both mobile devices (A and B) to the same access point (Wi-Fi router)
2. Open Kies Air on device A and tap Start
3. Open Kies Air on device B and shake the device twice. This will start a scan for device A
4. Device A will appear on the screen of device B. Tap on device A
5. Kies Air will display a PIN on device A. When prompted, enter the PIN on device B
If Kies Air is not installed on device B, enter the URL displayed by device A into the browser on device B.
If the motion feature is not supported on device B, press the menu key, and then tap Scan.
During installation, Kies Air requests permission to provide you with access to content or other required functions. Your data is only ever accessible within your local network and never sent to the Kies Air team, Samsung, or any other remote server.
Click to expand...
Click to collapse
it still wont connect to the PC but i managed to get kies downloaded and on there and did it all via that..
amazing thanks so much for your help... i managed to do that then golauncher etc from this link http://forum.xda-developers.com/showthread.php?t=2069668 will this stop automatic updates from amazon or will i need to
do that manually
READ THIIS!
*this thread is for desire 510. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or unlocked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
*i have tested this on my gsm cricket desire 510 variant(a11_ul). let me know if you try it on a different variant,or if youd like to dump partitions and have me take a look
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
other useful threads:
remove your tampered banner: http://forum.xda-developers.com/desire-510/general/how-to-remove-tampered-banner-t3179866
mine too