Related
I've tried this twice already with a factory reset in between each try, and it's worked both times!
Attached is a bunch of files you will need to make this work.
Download the attached Zip file and extrat the contents to your desktop
Mount your G and upload the "G Tablet" folder to your G's internal SD card
Using AndRootFile or any other file manager that supports root access, mount as R/W, and copy the contents of G Tablet\permissions to System\etc\permissions.
Copy the contents of G Tablet\framework to System\Framework
Copy the contents of G Tablet\lib to System\lib
Copy all the APK's found inside G Tablet\APK into your system\app folder.
Install them in this order:
GoogleServicesFramework.apk
OneTimeInitializer.apk
SetupWizard.apk
Talk.apk
Vending.apk
Gmail.apk
Maps.apk
Make sure you remount it as R/O when you're done!
Restart your G, Connect to Wifi, then launch Market.
Follow the standard Google Account setup procedure and enjoy your newly installed Market.
PROOF THAT IT WORKS (the guide might be broken at some point though, see explanation below): http://www.youtube.com/watch?v=3dm2Kax8RQM
Someone please test this and let me know if you have any problems. Factory resetting doesn't delete any files I might have moved into the system folder so I might be missing something in this guide.
Feel free to donate to my beer fund if this helped you
Copying the following over from my thread over at Overclock.net (best computer enthusiast community, ever!)
Guides:
Setting Up ADB:
The ADB drivers do not recognize the Tegra hardware by default. You need to modify the USB inf file in order for it to recognize it and install the proper hardware.
Go to the usb_driver folder inside your Android SDK folder
Open up android_winusb.inf
Add the following under [Google.NTx86] and save (or if you prefer, download my pre-modified android_winusb.inf attached to the bottom of this post, and replace your existing android_winusb.inf with mine).
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
If you are running a 64 bit version of Windows, you need to add that code to the [Google.NTamd64] section as well.
Next, open a command prompt and type
Code:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
On your G, go to Settings -> Applications -> Development, and check "USB Debugging"
Plug in your USB cable, it will tell you that some drivers were not installed. That's okay! Point it to your usb_driver folder and it'll install the proper drivers.
Make sure ADB is working by opening a command prompt, navigating to your android sdk "tools" folder, and typing
Code:
adb devices
You should see a bunch of numbers if everything is set up correctly.
Click to expand...
Click to collapse
Rooting:
You need to have ADB fully working before proceeding. The easiest way to root is by using CLShortFuse's SuperOneClick. If you can spare the money, consider donating a buck or two to his beer fund
Connect your G and make sure USB debugging is enabled/ADB is working.
Extract the contents of SuperOneClickv1.5.2-ShortFuse.zip to a folder of your choice.
Run SuperOneClick.exe and click on Root. Wait for the process to finish, and you're rooted! Easy as pie.
Click to expand...
Click to collapse
Installing Launcher Pro/ADW:
It's actually really easy.
Download the Launcher Pro APK from here: http://www.launcherpro.com/apk/LauncherPro-0.8.1.1.apk
Connect your G and move the Launcher APK over to your Tablet's internal/external SD card.
Using whatever file manager you prefer (on your G), execute the Launcher Pro APK and install it.
Upon completion, hit the Home button and choose LauncherPro as your default launcher.
Reboot and feel the speed!
Click to expand...
Click to collapse
Fixes:
Wifi Fix:
If your Wifi "errors" upon enabling, try one of the following methods
Method 1:
Reboot. Seriously, it fixes the problem a large portion of the time.
Click to expand...
Click to collapse
Method 2:
Download Wefi from here: http://www.wefi.com/download/android/
Install the APK on your G.
Run WeFi, hit the menu button (button between back and home), and hit Settings
Make sure Automatic Startup is checked. Click on "Wi-Fi on WeFi start" and choose "Always Turn On"
Restart your G and pray.
Click to expand...
Click to collapse
Method 3: Master Reset (you will lose all your apps)
Go to settings -> Security and do a Factory Wipe.
This works only SOMETIMES, but is not a guaranteed fix, so only use this as a last ditch resort
Click to expand...
Click to collapse
nicely done, sir
Awesome job. OCN FTW
Fantastic.. worked like a champ!
Thanks!
Where did you find the USB drivers to mount the device?
Can i also include the contacts, mail, and calendar gapps?
mattmanion said:
Where did you find the USB drivers to mount the device?
Click to expand...
Click to collapse
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
insight3fl said:
Can i also include the contacts, mail, and calendar gapps?
Click to expand...
Click to collapse
Go for it, let us know what you find
r34p3rex said:
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
Click to expand...
Click to collapse
Do you know if there is a tutorial out there for installing the Root Explorer or Astro file manager on this thing? Sorry, I'm a newbie.
VERY NICE WORK!
FYI I reposted this on the slatedroid.com forum gave you credit and linked back to this thread. If you don't want it on there let me know and I will take it down.
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Does anyone know why live wallpapers aren't available?
tri0xinn said:
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Click to expand...
Click to collapse
I will look into that. The most likely reason is the lack of a unique Android ID.
does the regular nullsoft winamp show up for you?
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
Gunth you want me to help over Teamviewer?
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
insight3fl said:
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
Click to expand...
Click to collapse
You need to run each APK manually through Root Explorer (or any package installer of your choice). Placing them there does not do anything
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
I'm having the same issue Gunth so when you get it working let me know
Just finished up installing the apks. Got a problem though. Now my home and search buttons don't work. Also lost Airplane mode when powering off.
*EDIT* Just watched your video. I don't think that's a finicky button. I think this hack causes the problem.
*EDIT 2* Just did a reset. Home button and search work again. So, it's got to be the hack.
Doc
FIRST OF ALL, I CAN NOT BE HELD RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICE! PROCEED AT YOUR OWN RISK!!!
Now that we got that out of the way...
I have noticed that some people`s Marketplaces simply refuse to update by themselves (exactly what happened in my case) and as most of the people visiting this forums are not tech-savvy and simply want a step-by-step guide to get things working, I decided no harm can be done by me posting this info.
Installing Android SDK revision 8
First of all, you will need to have Android SDK (and ADB of course) installed with the drivers ready to go. In order to get the SDK installed go to the official Android website and download the latest revision (r08 at the time I posted this). You can download any of those files, but I prefer using the executable installer so I can make sure everything is at its place. Now, there are two major flaws with this whole process which have almost made me quit the whole process several times, but I got them sorted out and will help you solve them aswell.
FLAW #1: After beginning the installation process, the installer will prompt you to download a JDK (Java Developer Kit) in order to continue installation. Hit the "Visit sun.java.com" button and download the latest Java SE (currently this one). But before proceeding be sure to download the 32 bit one, as the Android SDK only recognises this version. I know it`s not a big deal, but I spent about two hours trying to figure out what the heck went wrong and it became quite frustrating.
Install the JDK, then the SDK. Once Android SDK is done, simply go ahead and launch SDK Manager (you can find it in Program Files\Android\android-sdk-windows\) and when you get to choose the packages to install, simply check "Accept All" and click "Install". Once it`s done, it`s time to download the drivers. Click "Available packages", tick "Third party Add-ons" and under "Google Inc. add-ons" you should find "Google Usb Driver package". Tick it and click "Install". IF YOU GET AN ERROR SAYING THAT PERMISSION WAS DENIED AND YOU ARE UNDER WINDOWS 7, COPY THE WHOLE "Android" FOLDER CONTAINING THE SDK TO YOUR DESKTOP (OR ANY OTHER PLACE) AND REPEAT THE STEPS ABOVE. I know it`s quite rudimentary, but it does its job. Once it`s done, a folder named "google-usb_driver" will be created under Android. Be sure to correctly copy it to the original location in case you had permission issues.
FLAW #2: Ever since Android SDK r08, Google decided to remove the ADB files so now they have to be manually placed in the folder. I have uploaded them for you, so click here to download them. Once downloaded, extract the archive to the "Android\android-sdk-windows\tools" folder.
OPTIONAL: Go to Start Menu, right click on Computer, click Properties. The System window will appear, where you need to go to "Advanced system settings". Once there, click on "Environment variables" and where it says "System variables", look for PATH. Once found, highlight it and click "Edit..." then add the line "C:\Program Files\Android\android-sdk-windows\tools;" at the end. Click "Ok", "Ok" and "Ok", then restart your computer.
Right now everything should be working as expected. Connect your HD2 to the PC via USB and hope for the best. If the drivers are working and it is recognized as a HTC device, open a command prompt and type "adb devices". If you get anything such as "List of devices attached" followed by some code such as "0123456789ABCDEF device", everything is working well. Good job, you just correctly and completely installed Android SDK on your PC!
If not...
Check your device manager and if you see any devices related to your HD2 having problems, simply right click on them and update the drivers with the ones downloaded earlier in the "google-usb_driver" folder then reboot your computer.
We`re all set! ...What now?
The whole process is actually quite simple. First of all, download the new 2.2.6 Marketplace and put it somewhere accessible, such as your desktop. Open a command prompt and enter the following:
Code:
adb remount
adb shell
rm /system/app/Vending.apk
This will basically delete the old Marketplace from your device.
Now go to the folder where you placed the new Marketplace, hold down Shift, right-click and select "Open command window here". A command prompt should pop up at the exact location. Now execute the following command:
Code:
adb push Vending.apk /system/app
And that is it! Now restart your device and try to run your Marketplace, it will load for half a minute or so then it will start normally. Enjoy!
I know this is rather a tutorial for installing the SDK, but I figured it would be useful to let everyone know how I managed to solve my problem. In case I skipped any steps or you notice anything wrong/wish to add anything, please feel free to do so!
If you feel my post has helped you in any way, do not hesitate to hit the "Thank" button!
Reserved post for further mini-tutorials.
At least on my r08 install if you install the platform tools component then adb will be available under the platform-tools directory (moved from the tools directory).
@OP
Did you test this on a non sense build?
This procedure will most likely not work with Cyanogenmod ROMs. That and I'd suggest you give the newest market version (2.2.7) instead. I'm not willing to destroy my ROM again by trying it on CM.
ive created a walkthru for rooting the htc thunderbolt, based off the easy root script.
the adb folder is already setup, sdk is there, and the downgrade and upgrade. where should i host the file that this forum will allow me to post?
BTW if your running 64bit windows 7 i have included the ADB drivers, but not 32bit. i think they are installed with 32bit windows, but im not certain.
let me know if anyone is interested.
DOWNLOAD > Link 1
if anyone has any trouble please just post here, ill be on all day.
these steps will only work with the DL i have linked. if anyone wants to PM me a mirror it'd be greatly appreciated
steps:
THIS ONLY WORKS WITH A Thunderbolt running 605.6 or 605.9 Firmware
1. copy the root folder to the C: drive.
2. first, install the android SDK in the ZIP file. reboot if needed. plug in your phone, ADB most likely will not install. once or if it fails, search for the driver manually in the ADB+driverX64 folder though device manager.
3. now run the oneclickroot.bat file. dont worry about the prerequisites, they are all setup in the root folder i had you copy to the C drive.
4. after you reboot, plug your phone in. make sure adb drivers are istalled and working.
5. run the oneclickroot.bat file again, and follow all the directions. if you follow the steps slowly and correctly, all will work fine.
************************************************** *******************
REMEMBER! when it tells you to rename some lare file to PG05IMG, that is the PG05IMG_downgrade file. just copy to the root of your SD card, and rename it to PG05IMG after it finishes copying.
also if things freeze up make sure u have USB debugging enabled. DO NOT UNPLUG THE PHONE. just disable and re-enable if it hangs up when it says "this process may take w while".
************************************************** *******************
Ive also added the kernal to OC the phone to 1.5Ghz, you can do that with rom manager, or though clockwork recovery if your familiar with it. if u do it just copy the zip to the root of your SD card on the phone
Might want to throw a disclaimer in there just to cover your ass. Just saying.
Sent from my ADR6400L using XDA App
Am i missing the link???
Am I missing the credit? Thread Locked
Someone please help me.
I already ahve a Rooted DHD. With clock mod receovery installed et.c.
(running Android HD)
but if anyone can tell me, I want to switch to Cynagenmod, Looks more good.
One there Wiki page, When installing the ADB.
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
Im stucked at the 11 and afterwards. I did everything like it, nothing happend, Plugged in the Mobile with the USB bugging mode and did everything what i can.
But it's not working out, please somebody help.
On my computer the SDK didn't install to c:/ by default; it landed in C:\Program Files\Android\android-sdk\platform-tools
You then have to change step 11 to:
In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. C:\Program Files\Android\android-sdk-windows\platform-tools;C:\Program Files\Android\android-sdk-windows\tools.
Click to expand...
Click to collapse
And 12 becomes:
The Google USB Driver package only supports select devices out-of-the-box, we will be downloading a modified file that should provide support for all CyanogenMod supported devices:
Download the modified driver inf file: Download
Unzip the file & inside you will see android_winusb.inf. Copy this file to C:\Program Files\Android\android-sdk-windows\extras\google\usb_driver\ replacing the "stock" android_winusb.inf.
Click to expand...
Click to collapse
Dan
I don't get it...why would you need to install Android SDK and ADB drivers to just go from ARHD to Cyanogenmod7?
anetam said:
I don't get it...why would you need to install Android SDK and ADB drivers to just go from ARHD to Cyanogenmod7?
Click to expand...
Click to collapse
No idea, boot into recovery, and wipe data then install from zip, and job done
Hey can you provide an update with how CM7 compares to ARHD 6 as I think i'm getting tired of ARHD. I keep finding little things in ARHD that annoy me but don't want to go through flashing again for no reason, yet
Sent from my HTC Desire HD A9191 using XDA App
First and foremost I AM NOT RESPONSIBLE FOR ANY HARD BRICKS,etc ,etc(Really hard to hard brick a kindle doing this unless you flash a weird rom package)
Now that thats cleared up, I have been seeing too many recovery bootloop bricks lately because I think the main tutorials people use haven't been updated(to mention you need to put a rom on the kindle beforehand now), so I thought why not write a tutorial that explains how to fix this problem since there are so many posts, that way we can just put a link to the tutorial in the peoples threads. So here we go!
Things you need to do this:
a micro-usb cable
patience
minimal command prompt experience
Instructions:
Boot your kindle into twrp (it should do this on its own at this point)
Make sure you have the adb drivers installed(they will need to be installed again if you flashed an older version of twrp), if not, update your drivers in the device manager with the ones in my signature.(See below if you don't know how to update your drivers)
Download the attached file and extract it somewhere
Put the rom and gapps in the folder you extracted the files to
Open a command prompt with admin privileges(start>all programs>accessories right click command prompt, hit run as admin)
CD into the directory where the extracted files are
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
As I said in the filename put either the rom or the gapps, but send both in two commands
At this point once the transfer is done unplug your kindle
If you are going from amazon to a cm based rom, at this point you should wipe system, cache, dalvik cache, and do a factory reset. If not just goto step 11.
Hit install, browse to the /sdcard folder and choose the rom and gapps files and flash them
Reboot and profit!
For people with driver issues that don't know how to install my driver:
Open the device manager
Find the device with a triangle next to it
Right click it and hit update driver
Choose the option that lets you search a folder for drivers by browsing
Choose the folder you extracted my drivers to
Let it search and install the drivers
Profit!
Note: If adb isn't picking up the kindle in recovery, try uninstalling the current kindle devices it detects first and then updating the drivers
It's about time someone posted a tutorial for how to fix this. Great job! This should be a sticky.
thanks
I had the same problem... the looping thing... you're tutorial saved me! thanks a lot.
rom and gapps
sry for my ignorance, but what do you mean with "rom and gapps"?
i explain what i've done:
i did everything in the guide to install twrp and 2nd bootloader.
i can acces in the twrp, but if i enter the reboot menu, if i push the botton "System", i had the boot loop problem (Kindle logo became orange and then blue forever)
Now the question is: where i find the rom and the gapps you're talking about?
You choose a ROM from the android development section for your model kindle, usually it tells what version of gapps(google apps) you need to flash with it. If it doesn't tell what gapps you need its pretty easy to tell, goo.im has the gapps posted for all versions of android, and have a chart telling which version goes with what os.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
*cannot read
When I go to push the file to the kindle I get a message in the command prompt saying *cannot stat 'rom.zip': no such file or directory.
I have the zip in the same folder as the adb file
Any suggestions?
Check the ROM name to make sure its not a typo? It should work. Make sure you didn't rename the ROM and add .zip because windows by default doesn't show extensions, so the filename might actually be ROM.zip.zip now if you did that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sigh, I was hoping my first post on XDA wouldn't be a help request, but here I am..
I agonized for hours over the directions in this tutorial, checked all the right boxes, but I ended up in the bootloop as described in the OP. I can get to TWRP fine, but nothing else. My ADB drivers along with the Android SDK package were installed and previously working fine. Now, of course, the device no longer has a driver in Windows. I followed the instructions here, carefully selecting the extracted folder containing the ADB files, and Device Manager tells me—
"Windows was unable to install your Kindle. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Click to expand...
Click to collapse
I tried a number of times to reboot both systems, uninstall the Kindle, try to pick it up again, etc., to no avail.
My device is a Kindle Fire HD 7" originally version 7.4.6. I made backups before I started as per the directions in the linked thread and I have my desired ROM and Gapp .zips all ready to go, I just can't get anything to the device. I'd prefer to avoid needing to get a factory cable, if possible.
Thanks for any help!
Edit: I've managed to get my .zip files to the /sdcard/ directory. For anyone stuck on the same problem I was, the instructions in this thread got my ADB drivers up and running again. The rest of the steps here worked fine at that point.
Oh good, someone finally made a tutorial for this.
Help please
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
CD means change directory, it does what it says, right now you are in your system32 folder so when you CD into the directory you extracted the zip file to you won't get that error. You should Google some command prompt basics.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks
Thank you for this guide, googled some basic CMD knowledge and now i have cyanogen. Cheers
gallowayj3 said:
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Extract the file in the first post to somewhere on your C drive. (I put it in the C drive directly so it was just c:\adb\.)
Check this: ht tp://coweb.cc.gatec h.edu/ice-gt/339 - remove the spaces.
That should help.
Do
cd..
until you have just c:/. Then type cd:/adb and it should put you in the right place. Then you can do adb push.
I just figured this out actually and did it.
HELP
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Sounds like an old twrp version I think, try downloading the latest twrp from android development for your device, It should have a flashable zip, just push it to your device and flash that, then reboot into recovery again and try flashing the ROM again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stuck
Hi guys .., when i typed adb push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard , it says
error: device not found.
i thing my pc didn't recognize my kindle. In device manager there ain't any devices not installed .
someone pls Help
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sorry for my stupid question. ) what is service manager?
stunts513 said:
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My bad I think my kindle autocorrected a word incorrectly. It was supposed to say device manager.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
i'm kind of newbie on rooting and installing ROMs.
http://www.youtube.com/watch?v=hUW6KARo8Y4
i tried this youtube instruction and after step 20 My kindle fire wouldn't start. Not even the kindle fire with blue color.
and also pc didn't recognize my kindle , maybe because of it won't power on.
/this instruction is for kindle fire HD 8.9 , i don't know my kindle is 7 inch/
In device manager can't find adb devices .. what should i do?