How to solve/fix bricked kindle fire,(solve the stuck on logo) and install adb - Kindle Fire General

How do I install the ADB drivers?
• By far, the easiest and best method of installing ADB drivers on a Windows OS based machine is to use the installer provided in the Kindle Fire Utility distribution.
• Find the latest version and download it to your computer or download this
http://www.mediafire.com/download/pezst5gbwmke4yt/KindleDrivers.exe
• You can extract the files to any place on your hard drive
• Open up the folder and you'll see an "install_drivers.bat" file among the contents. Windows may hide the ".bat" portion of the name, so it might just look like "install_drivers" in the folder. Disconnect the Kindle Fire from the computer (highly recommended) and then run the "install_drivers.bat" batch file. The installer will automatically check for the OS type (32 or 64 bit), and then install the appropriate drivers and configuration files.
• Don't worry too much about Windows not being able to verify the publisher of the drivers. The warning is there because the drivers have been repackaged for use in KFU and have not been signed. It's OK to just install the driver software anyway. If Windows refuses to install unsigned drivers, that feature must be disabled before continuing. The process differs for various Windows releases, so search Google and find a suitable method for your system.
(Eg-Wind8 -http://www.makeuseof.com/tag/how-can-i-install-hardware-with-unsigned-drivers-in-windows-8/
How can I verify the drivers are loading?
The Windows Device Manager is the key to determining the status of all the computer's devices and drivers. Right click on the "Computer" wherever you can find it (the Start menu, the Windows Explorer, etc.), select "Manage" from the menu and the "Computer Management" program will start up. From the left panel, select "Device Manager" in the "System Tools" category and the large pane in the middle will show a list of device types. Click on the triangle (or plus sign) next to a device type and a list will expand to show all the devices of that particular type.
Now, connect the Kindle Fire to the computer and keep an eye on the device list. Windows will give some device detection beeps and the list will refresh.
{
"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"
}
Before getting into the meaning of the table above, a small detail must first be covered. For adb to interact with the Kindle Fire, it must first have the "USB debugging" feature enabled. Without this feature, Windows will not even attempt to load the appropriate driver. The stock Kindle Fire software has this feature turned on at all times, but other ROMs must have "Settings -> Applications -> Development -> USB debugging" enabled. The rest of this document assumes normal mode has USB debugging enabled.
What can I do if the drivers won't load?
Windows can be very temperamental when it comes to device drivers. Don't assume the worst right away, but try rebooting the computer, disconnecting/reconnecting the device, and restarting the device in both modes. Fastboot in particular sometimes won't get detected by Windows on the first try and may require a reboot of the Kindle Fire.
If the Kindle Fire comes up as a different device or you get a "Code 10" error, you'll have to explicitly tell Windows what driver you expect to see for the device. The steps below are for Windows 7, but they should be very similar for earlier versions of Windows as well. The following may have to be performed twice, once for normal mode and again for fast boot mode. The steps below are listed for normal mode (and the fast boot equivalent in parentheses). Be sure to have tried installing the drivers using the batch file at least once or you will not be able to complete the process.
• Install this before this just in case.Connect the Kindle Fire in normal mode (fast boot mode) to the computer
• In the Device Manager, right click on the device and select "Uninstall"
• Check the "Delete the driver software for this device." box and press "OK"
• Disconnect the Kindle Fire, reconnect and reboot in normal mode (fast boot mode)
• The Device Manager should show "Other devices -> Kindle" ("Other devices -> kindle")
• Right click on "Kindle" ("kindle") and select "Update Driver Software..."
• Select "Browse my computer for driver software"
• Do not click the "Next" button, but select "Let me pick from a list of device drivers on my computer"
• Select "kindle" and then press the "Next" button
• Press the "Have Disk..." button
• Click the "Browse..." button, point it to the "C:\kfu\drivers\kindle" directory and press"Open"
• Press the "OK" button
• Uncheck the "Show compatible hardware" checkbox
• Select "Android Composite ADB Interface" ("Android ADB Interface") and press the "Next" button
• Select "Install this driver software anyway"
• Press the "Close" button
The device should now appear in the Device Manager.
(Source- http://ezkindle.blogspot.com/2013/04/how-to-unbrick-install-adb-verify.html )
How to use KFU after this?
• Open the “run” batch file
• Select 2 and hit enter
• Allow to install
• If an error appears……..eg-'Activating Fastboot (4002) then hard reset the kindle fire and repeat the above steps
voilà you have a rooted kindle fire:good:
Installing android store
• Install root explorer from your device
http://www.mediafire.com/download/pezst5gbwmke4yt/KindleDrivers.exe
• Then Follow instructions on video http://www.youtube.com/watch?v=rTkegVrnAvA

Related

[Guide] Drivers & RRU Errors Solved

This guide is for anyone having issues with their HTC Hero drivers. It is aimed at Windows users and the guide was performed on Windows 7 x64 but relevant to older systems with minor adjustments (use common sense).
Most of it will be pictures, i'll try to fill in the rest in future and give it some layout but for the most part this process is easier to see than describe. Very much a work in progress.
Note: Unplug your phone from your pc for these processes until told otherwise. Remove any version of HTC Sync prior to 2.0.33 before doing these processes.
Might Need Apps:
HTC Sync for Android v1.5
HTC Sync for Android v2.1
USB Deview
Remove Old Drivers:
1. Start USBDeview by running the exe in the zip file
2. Remove any drivers which read like the following:
3. Reboot your machine
Installing The Correct Drivers:
1. Install the latest version of HTC Sync (2.0.40 or 3.0.5422)
2. Reboot
3. Right Click on Computer in your start menu and choose "Manage"
{
"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"
}
4. Select Device Manager on the left hand side.
5. Plug your phone into the PC and let the drivers install (you should see changes in device manager in real time). Under "ADB Interface" you should now see "My HTC" as seen in the picture.
This is correct and you should move onto the "Bootloader Drivers" section below. If you don't see this then carry on.
6. Right click on whatever you get under "ADB Interface" and do the following:
- Choose Update Driver Software...
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- Have Disk
- Browse
- C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 (last folder may be different)
- Select "androidusb.inf"
- OK
- Next
- Finish
You should now have the correct HTC Hero drivers installed. Move onto bootloader drivers section.
Bootloader Drivers:
Note: assumes you have the latest version of HTC Sync installed prior to doing this and have followed the driver process above to arrive here.
1. Switch off your phone and then hold Volume Down when you press the Power On button (Vol Down + Power).
2. You should have a white screen with some coloured text and 3 android's on skateboards. This is bootloader mode.
3. Now plug your phone into your pc and watch device manager change (this can take a minute or two). If "ADB Interface" doesn't show up or you get an "Unknown Device" error (perfectly normal - i think) then press the Back button and wait a couple of minutes then press volume Down again. This switches to Fastboot mode and back to Bootloader mode. AFAIK the drivers are the same so you should be able to do this process in either mode. You should get the driver "HTC Bootloader" or similar in your device manager. You need to repeat the steps above to change that to My HTC instead.
4. Right click on whatever you get under "ADB Interface" and do the following:- - Choose Update Driver Software...
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- Have Disk
- Browse
- C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 (last folder may be different)
- Select "androidusb.inf"
- OK
- Next
- Finish
You should now have the correct HTC Hero bootloader drivers installed. This will allow you to correctly install a RRU from HTC.
Brilliant guide! I have added it to my sig!
Nice one, thanks
Wow this worked 100% installed perfectly
thanks

[GUIDE] How to root Elephone P7000

Preparation:
1. Make sure that your computer installed a driver
(Download link here )
2. Flash tool (SP flash tool recommended, download link here )
Please be careful and make sure that you have enough knowledge or we suggest that don't root your phone casualy.
1. Download the file from below link. you're going to save to somewhere you can remember it, for this tutorial, I'm going to use my desktop.
Dnowload link here
2. Unzip the file that you have downloaded just now.
3. Cope zipe file named "superSU_PRO_V2.49.zip" to your SD card and then turn off the phone.
4. Open flash tool, Click "scatter-loading" and choose the file named "p7000-recovery" which you have just saved in your computer.
{
"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"
}
5.Click download and then connect your phone with computer.
6. When you see a picture as below that means you have installed the third party recovery successfully.
7. Move out the battery and then put it back, press "power" + "VOL +" to enter recovery mode. ("VOL -" to choose, "power" to confirm)
http://bbs.elephone.hk/data/attachment/forum/201506/11/164351v74mw4840lullmwr.png
8. Choose "install zip" by pressing "VOL -" ,
9.Go to "choosezip from /sdcard"
10. Choose "superSU_PRO_V2.49.zip" , press "power" key to confirm.
11. Choose "yes-install superSU_PRO_V2.49.zip", press "power" key to confirm.
12. Congratulations!!! You have finished the whole process, now enjoy.
You can also root without flashing recovery.
1) Download and install SuperSU from Play Store, don't run it yet.
2) Enable USB Debugging and install ADB drivers.
3) Download this ZIP http://www37.zippyshare.com/v/SaH4NxFw/file.html , unzip to a folder and open command prompt in it.
4) Issue the following commands:
Code:
adb kill-server
adb root
adb connect localhost:5037
adb shell setenforce 0
adb shell mkdir -p /data/local/tmp/supersu/arm64
adb push su /data/local/tmp/supersu/arm64/
adb push supolicy /data/local/tmp/supersu/arm64/
adb push libsupol.so /data/local/tmp/supersu/arm64/
adb push update-binary-adb-arm64-v8a-21 /data/local/tmp/supersu/
adb shell chmod 0755 /data/local/tmp/supersu/update-binary-adb-arm64-v8a-21
adb shell /data/local/tmp/supersu/update-binary-adb-arm64-v8a-21
5) Don't reboot, run SuperSU, choose normal install, done.
Thanks
Thanks for all your work !
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
GCbard said:
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
Click to expand...
Click to collapse
If you can access adb (turn on debug mode in developer settings), then try my method above. No need to use preloader driver.
eLeKtriK EyE said:
If you can access adb (turn on debug mode in developer settings), then try my method above. No need to use preloader driver.
Click to expand...
Click to collapse
Thank you. I tried but the phone is not recognized as ADB. I have usb debugging checked and it still does not work. I even have all the drivers installed. Any suggestions?
Try with another computer, it must be windows 8 fault.
GCbard said:
Thank you. I tried but the phone is not recognized as ADB. I have usb debugging checked and it still does not work. I even have all the drivers installed. Any suggestions?
Click to expand...
Click to collapse
Download latest mtk droid tool's, i upload this some time's ago, this is Link.
https://mega.co.nz/#!2V9SRCRZ!xYn52zbVEfGze4zCyaUkfwStCUe0tt408IBpR-Tq-Fo
And here i add android commander. Try. For me working, but MTK DT no fully work
GCbard said:
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
Click to expand...
Click to collapse
i had the same issues when i first tried flashing the device, some moderator in the eleforum stated that's normal for the phone to act like that, because it will just detect to flash for 1.5 sec and then jump into charging mode
do this steps and should work fine
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device and it will start the flashing process.
you are done.
TopoX84 said:
i had the same issues when i first tried flashing the device, some moderator in the eleforum stated that's normal for the phone to act like that, because it will just detect to flash for 1.5 sec and then jump into charging mode
do this steps and should work fine
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device and it will start the flashing process.
you are done.
Click to expand...
Click to collapse
Thanks! It worked.
I tried it , once I click download. I don't see it downloading anything. 0 b/s and -0 bytes.
TopoX84 said:
do this steps and should work fine (add : turn phone off)
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device trough usb cable (phone still off)
6- then turn it on and it will start the flashing process.
you are done.
Click to expand...
Click to collapse
Worked fine here (added some steps), did not install it from sd card as it is still in the old phone :
choosed install zip from last folder and then move to the folder where it is ( vol + /- to scroll down, power to validate). I put it on download folder (on the phone memory), but of course you can put it anywhere you want !
Very smooth install, thx for the great tutorial
Help me
Followed all your directions, when I click on download, nothing happens
yeah same here when I press "Download" nothing happens (Windows 8.1 x32)
If I use one of these methods to root my P7000, enable Link2SD and then unroot it, can I retain the Link2SD features?
I want to be able to install/move apps onto the SD card but I don't really want or need a rooted phone in the long term.
Re upload recovery:
adf . ly/1NoLAj
(without the spaces)
Hi, could you anybody please reupload files with CWM and Supersu.zip? The link doesn´t work
Edit: Sorry, the link is working, error in my browser
download link has broken. T_T
I've got " the load scatter file is invalid" is there any way to get through this problem? I've already tried different versions of SP flashtool still got the same. Files downloaded from Devblaze who reuploaded them! The first post's links don't work.

[Tutorial] [SP] [Windows] Installing all drivers

Driver installation for the Xperia SP (on Windows)
For Windows 8, 8.1 or 10 (skip bcdedit stuff if you are on Windows 7, Vista or XP):
Since Windows 8, Microsoft added a new "security" feature where unsigned drivers do not get installed. Our phone drivers are not signed that's why I didn't manage to install FlashTool drivers. You can "bypass" this by enabling test-signing mode. Just follow these steps:
Right-click on the start menu, select command promt (as Administrator) and enter this:
Code:
bcdedit -set nointegritychecks on
bcdedit -set testsigning on
Now you can install all unsigned drivers.
ADB Drivers
ADB stands for Android Debug Bridge and can be used to interact with the phones file system.
Download the Universal ADB Driver from here. Your device needs to be connected while installing the drivers.
Flashmode and Fastboot Drivers
Flashmode is used to flash firmware (Pre-installed Sony "ROM") and kernels (Pre-installed Sony kernel).
Fastboot is mainly used to flash kernels and system partitions. But it also has other powerful tools.
You should have FlashTool installed, if not download it from here and install it. After installing FlashTool open it, wait until it's done loading and close it. Now follow these steps:
1. Open the folder where you installed FlashTool (usually in C:\FlashTool\) and go in the "drivers" folder and open the "Flashtool-drivers.exe" file.
2. Select "Fastboot" and "Flashmode" drivers and click on install. Select "Install anyways" when asked.
PC Companion
PC Companion installs all official (USB) drivers and has many features like importing/exporting contacts, photos and a lot more. But in this tutorial I will only show how to install the drivers
The driver will get installed once you plugin your phone (without Flashmode or Fastboot). Download PC Companion from here.
Now connect your phone (without Flashmode or Fastboot) to your PC via USB while FlashTool is open. Wait a moment (30 seconds) so FlashTool can find your device and install phone-drivers and after that close FlashTool and also disconnect your phone.
Now open the command promt again and enter this to disable test-signing mode because it isn't very safe to keep test-signing mode enabled as other malware-software can be installed.
Code:
bcdedit -set nointegritychecks off
bcdedit -set testsigning off
Now you have all drivers installed. Disconnect your phone from your PC or charger. Now shut down your phone:
For unbricked phones:
Hold the power button and select shut down.
For bricked phones:
{
"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"
}
Take off the back cover and hold on the "Off" hole.
Button Pressed and hold for 5 seconds | resets the battery, its like removing the battery and putting it back in.
Button Pressed and hold for 6-10 seconds | will power off hard, device will power down (wait until it vibrates 3x and quickly let go).
Your phone must be off Now you have the option to:
Go into Flashmode and flash stock firmware (to recover if you are bricked or if you just want your stock firmware back):
Open FlashTool
Hold the volume up key (don't let go) and connect to your PC. If you see a green light, you did it right.
Go into Fastboot mode and flash a custom kernel (with recovery):
Open FlashTool
Hold the volume down key (don't let go) and connect to your PC. If you see blue light, you did it right.
Boot normally:
Hold the power button for 3 seconds and boot normally.
If I helped you, leave a "Thank" and if you have a question just ask
Nice method.
There's also an alternative where you go into windows 8's recovery menu. ( for me its spamming F8 during start up.) There you can choose an option called change the way windows starts up or something and can disable driver signature check for that one particular boot.
But, nevertheless this one is a better and easier way
Sent from my Xperia SP using Tapatalk
# Updated
This thread only showed how to get into "Testsigning" mode to install the drivers on Windows 8, 8.1 and 10. But now I've added the installation instructions for ADB Drivers, Flashtool/Fastboot drivers and USB-drivers and the instructions for the usage.
You forgot to add win7 to Vista and XP
Deleunes254 said:
You forgot to add win7 to Vista and XP
Click to expand...
Click to collapse
Thanks, updated post again.
- Added Windows 7 to Vista and XP
- Fixed Image displaying
Code:
bcdedit /set nointegritychecks off
bcdedit -set TESTSIGNING OFF
after disable test-signing mode need reboot again or not ?
because when TESTSIGNING ON need reboot.
TMates said:
bcdedit /set nointegritychecks off
bcdedit -set TESTSIGNING OFF
after disable test-signing mode need reboot again or not ?
because when TESTSIGNING ON need reboot.
Click to expand...
Click to collapse
Yes you do need to reboot to deactivate testsigning mode.
Universal ADB driver doesn work on Windows 10 x64...
vaci_h said:
Universal ADB driver doesn work on Windows 10 x64...
Click to expand...
Click to collapse
New version of drivers works fine. Link in first post is old. Check actual version at http://adbdriver.com/downloads/
Links and commands updated.
I bricked my xsp while following this method.. When i turn on my device the LED bar lights up rather strange colour, before shutting itself down again..
Man, thanks a lot
Btw, for me, testmode got activated only after rebooting my PC. I think it's good to mention, as I was stumbling for some minutes.
Peace

Install Google Apps from another Device

Purpose
This guide is for anyone that does not want to trust downloaded APKs from someone else's guide. This guide is intended to walk you through the process of exporting the necessary android package files (APK) from a device you already trust with your Google credentials.
Requirements
- Android Development bridge. (ADB)
- An android device with working Google apps
- MyAppSharer and OI File Manager installed on Android Device
- Kindle Fire ADB drivers installed on PC
- APKs
- com.google.android.gms.apk
- com.google.android.gm.apk
- GoogleLoginService.apk
- GoogleServicesFramework.apk
- com.android.vending.apk
- Optional
- org.openintents.filemanager.apk
- com.lastpass.lpandroid
Notes
I tried this with APKs from a Galaxy Note 4 running Android 5.0.1. This failed to install GoogleServicesFramework with the error of `INSTALL_FAILED_DEXOPT`. I feel that this Fire OS is based on an older android version, that will require older APKs.
The devices used for examples in this guide:
- VZ Droid Razr HD running Android 4.4.2
- Kindle Fire 7 (2015 Edition) Running Fire OS 5.1.1
Assumptions
- Android SDK tools is installed on a Windows 7 PC
- The source of the Google APK's is guide is called the Android Device
- Your target Kindle Fire is not rooted and freshly wiped.
- That you know what APKs are and what they are used for.
- That your computer is already setup to talk to your Android device for file transfer.
- the ADB command is accessible from the command line. ie. `\Program Files (x86)\Android\android-sdk\platform-tools\` in your PATH.
- You will allow the Play store to update any components it deems necessary.
- ADB drivers for Kindle-Fire are working on your PC and USB debugging is already turned on.
- Fire OS 5.1.1
Directions
1. Create a directory on the Android Device in Download called PlayApps.
2. open MyAppSharer on the Android Device and type near the magnifying glass. This should filter the list.
note: "Ensure that the switch is on APK and not Link.
3. Select the Google Play Store and Google Play Services apps. Then Tap the < share button.
{
"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"
}
4. Tap the Export to SD card button.
5. Scroll to Find your Download directory
6. Tap on your PlayApps Directory.
7. Then tap the OK button.
8. Repeat the above five steps for Gmail.
9. Open OI File manager on the Android device and tap the House icon.
10. Tap the system directory. Note: that some devices may have a .system (dot system) directory. This is not the directory you are looking for.
11. Tap the Priv-App Directory. Note: Some devices put all the system apps in their own directories here, others do not.
12. Scroll and look for GoogleServicesFramework.apk or GoogleServicesFramework directory.
13. Long press on GoogleLoginService.apk.
14. Scroll down and tap on GoogleServicesFramework.apk. Note: this should select both of them.
15. Tap the Hamburger menu, then tap copy. Note: that the bottom of the screen will read 1 item to copy.
16. Tap the House button again.
17. Scroll, find and tap on the sdcard directory.
18. Scroll, find and tap on the Downloads directory.
19. Scroll, find and tap on the PlayApps directory.
20. Tap on the Clipboard icon. This will paste the app here.
21. You should now have five apk files in your PlayApps directory.
22. Using a USB cable, connect your android device to your PC.
23. Copy the PlayApps directory to your desktop.
24. Unplug the android device and plug in your kindle file.
25. Copy the PlayApps directory to the kindle
26. Launch a command prompt. use `CD` to change directory to the PlayApps directory on your PC.
27. Type the command adb devices. Note: If you receive a pop-up on the kindle called Allow USB debugging?, check the box for Allows allow, and tap OK.
28. Type the following commands.
adb install com.google.android.gms.apk
adb install GoogleLoginService.apk
adb install GoogleServicesFramework.apk
adb install com.android.vending.apk
adb install com.google.android.gm.apk
adb reboot
31. Login with your google credentials.
note: I also copy the APK for lastpass.
Resources
Kindle Fire Drivers - This guide is slightly outdated.
You only need to Select the Kindle USB driver from the extra Category. you can ignore the other items that it shows you to select.
https://developer.amazon.com/public...ing-up-the-ADB-Driver-for-Kindle-Fire-Devices
http://forum.xda-developers.com/showthread.php?t=1349902
http://forum.xda-developers.com/ama...google-framework-playstore-t3216122?nocache=1
USB Debugging
- SEttings > Device Options > Tap Serial Number 10 Times.
- Tap Developer options.
- Tap Enable ADB.
- Restart Kindle
- Force windows device manager to accept new driver.
Reserved
Works like a charm, thank you!
Am i able to remove all the apk´s in case of using warranty? How to do it?
Greetings
Yes. I personally wipe devices before warranty repair. They'll be gone after that. It will keep adb debugging turned on.
Sent from my SM-N910V using Tapatalk

Google Nexus 4 MTP mode not recognized by Windows 10 (Manual Fix)

Hello N4 Owners/Users.​
lately I've been working on IOS & iCloud Activation Lock Security, which is a Job I honestly do not wish you have, because is not a great business at all but, going more deep in this post I'm glad to post it because I've been trying to send iCloud Accounts stored on a PDF at my Nexus 4, a device that I've purchased last month at eBay and is incredible how this device with Unofficial ports runs faster and without bugs, of course using PURE Nexus ROM.
first things first, I must specify that I was sideloading ZIP's, APK, ROMS through ADB SIDELOAD commands, so that the first sign of a properly working USB Port, I didn't noticed yet that I was unable to set up my device as MTP and transfer photos or WhatsApp Folder to my PC.
2 weeks later I've noticed that MTP was not working, even changing "Charge Option" to "Transfer Files" so I just put my knowledge on going, the first thing was download the USB driver at Google SDK webpage, which delivers USB Drivers apart instead with the whole SDK, I've just proceed to download it, I've installed it and for my surprise the MTP was still not working...
what do now ?​
Steps:​
1. Download the proper driver designed by google
Google Nexus 4 Drivers.
2. Make sure your PC is not on secure boot, for this you should reboot your PC and enter to BIOS Setup to make sure secure boot is not activated, if it is, please turn it off.
3. reboot again and let your PC boot, you may notice that the boot sequence UI display a little messed up, but is normal.
4. go to UWP Settings and Select "UPDATE & SECURITY"> "RECOVERY"> "Advance startup" and hit at "Restart Now"
5. your PC is going to restart again & you'll see a menu of likely 10 or 9 options, we need deactivate the option 7.
7). Disable Driver Signature Enforcement.
Click to expand...
Click to collapse
doing this your PC will restart again or maybe it just boot the Windows or UEFI Logo.
6. Find & Run CMD as administrator and execute the code below.
bcdedit /set TESTSIGNING ON
Click to expand...
Click to collapse
Restart your PC Again.
wait, you need the MTP or really are you craying for such restarts?
okay, that's what I though.
7. Disable ADB on your device and connect it to PC, Open device manager and look for "Android ADB Interface"
8. Right Click on the device and select "Update driver", Select "Browse My Computer for driver software"
9. locate drivers folder you've already downloaded following this guide and after that, you must have this screen
{
"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"
}
Select "Let me pick from a list of available drivers on my computer"
If are 2 MTP entries, install them and reboot your PC, and that's all people, MTP working.
Now go back at CMD as Administrator and set this
bcdedit /set TESTSIGNING OFF
Click to expand...
Click to collapse
Now Restart and enter at BIOS, restore secure boot, done!
Hit "thanks" button if this helped you recovering MTP Access and your PC at your N4.

Categories

Resources