{
"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"
}
Using CIFS on Fire Nexus ROM and CM-12.1
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
General
- This is a guide which describes what is required to have working CIFS shares.
- All information and steps are mandatory
Prerequisites for Installation
- Download SuperSU-2.65 Stable
- Download Patched version of CIFSManager v1.5a
Setting up Prerequisites
1. Disable Privacy Guard (Root Access) in Developer Settings
2. Install SuperSU 2.65 Stable Version
3. Reboot
4. Install the patched version of CIFSManager 1.5a
Setting Up CIFSManager
1. Open CIFSManager and click on the 3 vertical dots in the bottom right hand corner
2. Click Settings
3. Click on Mount point prefix
4. In the dialog box enter the following:
Code:
/data/media/0/shares
5. Press <OK> on the dialog box
6. Tick the checkbox against the option "Load cifs module"
7. Tick the checkbox against the option "Load via insmod"
8. Click on the "Path to cifs.ko[:<modpath>]* option.
9. In the dialog box change the text to be the following:
Code:
/system/lib/modules/cifs.ko:/system/lib/modules/md4.ko:/system/lib/modules/nls_utf8.ko
10. Press <OK> on the dialog box
11. Press the back button to return to the main screen
12. That's the hard bit done.
13. Reboot
Mounting a shared folder
1. In a file manager on your tablet with root access
2. Browse to /data/media/0 and create a folder called "shares"
3. Browse to the newly created shares folder
4. Now create a folder for your new share, I'll use "music" as an example
5. Now go back to CIFSManager and click on the 3 vertical dots in the bottom right hand corner
6. Select the "Add New Share..." option
7. In the Share Path enter <ip address>/<share name>, for example
Code:
192.168.1.250/music
8. Now click on the "Username" field
9. The "Mount Point" field above should have auto-populated with
Code:
/data/media/0/shares/music
10. Enter the "Username" and "Password"
11. In the "Options" field enter the following text:
Code:
rw,file_mode=0777,dir_mode=0777,iocharset=utf8,context=u:object_r:rootfs:s0
12. Click the "Save" button, you will then have returned to the main screen
13. Finally click on the share to activate it.
Thanks
- @Chainfire for SuperSU
- @f3d0r for CIFSManager
- @DualJoe for patching CIFSManager
- @bseos and @glimmling - Fix for empty app-mounted directories
Wicked!!! Your the Man! Cant wait to try it!!
Somebody want to fill us newbs in on what this does and the benefits?
riverstyxxx said:
Somebody want to fill us newbs in on what this does and the benefits?
Click to expand...
Click to collapse
With cifs you can mount any shares exposed to your network by the Windows fileserver you have at home, for example.
riverstyxxx said:
Somebody want to fill us newbs in on what this does and the benefits?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=cifs
I just tried this on my Fire 7 with a fresh install of CM but I cannot play any of my music files. I can use the file manager to copy the file to my internal storage but when I try to play them directly from the dir the music app says "IO Error" and VLC simply says "<filename> cannot be played!". Any suggestions?
false_chicken said:
I just tried this on my Fire 7 with a fresh install of CM but I cannot play any of my music files. I can use the file manager to copy the file to my internal storage but when I try to play them directly from the dir the music app says "IO Error" and VLC simply says "<filename> cannot be played!". Any suggestions?
Click to expand...
Click to collapse
I have the same issue, I looking into it but don't have a diagnosis yet
ggow said:
I have the same issue, I looking into it but don't have a diagnosis yet
Click to expand...
Click to collapse
Awesome. Thanks for looking into it!
Please help a NOOB
using a firetablet 7 inch, nexus rom, fresh install after first section seems to run ok I get stumped at create /data/media/0/shares.
Using file explorer I can't find /data/media/0 ??
Is there an app like foldermount that does this more automagically ?? or maybe a script file that someone could write....RootJunky. ??
PLZ
ggow said:
Code:
/system/lib/modules/cifs.ko:/system/lib/modules/md4.ko:/system/lib/modules/nls_utf8.ko
Click to expand...
Click to collapse
Thanks, that does it - it would be nice to have an updated apk that search-inserts these modules on its own though... it's not like typing on the android screen keyboard is l lot of fun :-\ and I only stumbled upon the solution after some searching around.
Related
I have a nook simple touch reader, I installed android with a sd card following these instructions
--------------------------------------------------------
For Windows users:
Run WinImage.exe (Right click, Run as Administrator)
Select Disk from the menu and select "Restore Virtual Hard Disk Image...".
Select your SDCard from the list and click OK.
In the Open dialog box select "All Files" in the lower right file type box, browse to nookhoney.img, select, and click Open.
--------------------------------------------------------
When I rebooted it was a screen that allowed me to choose two options, one was "ADW"(I suppose that is android) and "Home" (usual nook). I selected "Home" and made a tick on the box to make it default. Now I do not know how to go to android from the nook "Home".
Could you help me, please?
Don't know about nookhoney.img - I used MinimalTouch.
I have a faint symbol on the right hand of the screen. Touching the symbol makes a faint menu pop up.
@niaosan: That's Button Savior, it will get you back to the Launcher, but won't change the preference.
@genoxygen: I'm not familiar with nookhoney.img
Some folks have Nook Touch Tools or Nook Color Tools which have functions for changing activity preferences.
Do you have ADB to your Nook?
I just do this stuff by hand.
Code:
adb pull /data/system/packages.xml
Then edit the XML taking the "guts" out of <preferred-activities>
That is, deleting the lines between, but leave <preferred-activities> and </preferred-activities> alone.
Code:
adb push packages.xml /data/system/
genoxygen said:
Could you help me, please?
Click to expand...
Click to collapse
Are you sure you are speaking about the Nook Simple Touch (black and white ebook reader), and not about the Nook Color or the Nook Tablet? nookhoney is for the Nook Color. They are supported in different sub-forums.
My nook is the "simple touch reader" and the software android software is touchnooter-2-1-31.
Sorry about the confussion.
-------------------------------------------------------
I observed I have a button on the screen, to right, I pressed that button, and there are 5 options.
-three cercles
when pressing them, it shows me another menu, to choose a telephone, a camera and a seacrh option.
-arrow
Superuser Request. Button Savior is requesting Superuser access.
I pressed Allow, but I do not know what is its utility.
-four squares
- a house
goes to nook home
- a power down button
does not do nothing
-------------------------------------------------------
I pressed all those button but none of them takes me to android. What could I do next?
Did I installed correctly android to my device with these instructions?
--------------------------------------------------------
For Windows users:
Run WinImage.exe (Right click, Run as Administrator)
Select Disk from the menu and select "Restore Virtual Hard Disk Image...".
Select your SDCard from the list and click OK.
In the Open dialog box select "All Files" in the lower right file type box, browse to touchnooter-2-1-31.img, select, and click Open.
--------------------------------------------------------
"House" is going to Nook stock Home because you selected the wrong activity.
My advice is as above or use one of the "Nook Tools".
By the way, you didn't install android, because it was already in there. You were allowed to bypass the restricted Barnes&Noble reader part and run your STR as a full android e-reader/tablet.
509A ndivTi
I do not know how to use adb, although I have it installed on my Windows OS...
------------------
What could I do? Should i...?
- Restore my nook firmware, installing n2T-Recovery_0.1.rar http://forum.xda-developers.com/showthread.php?t=1289233
- Install touchnooter-2-1-31
- Choose "adk" instead of "home", should I make it default or not? If made default, can I go easily to nook "home"? Or there will be the same problem like the one I had?
------------------
{
"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"
}
You can always get back to the Nook Home page (unless you deleted it like I did ).
The adb you want is in the Android SDK. http://developer.android.com/sdk/installing.html
You can use it over Wifi or USB. The USB needs drivers on your desktop though.
The file is adb.exe
It should be in something like C:\Program Files\Android\SDK\platform-tools
Code:
adb connect 192.168.1.27 [i]or whatever[/i]
adb shell
ls
Thank you so much. Finally I did it.
Note that I'm not referring to the write issues which I'm well aware of.
But it seems that the new kitkat file picker can't detect my SD card at all, even when 'show advanced devices' is enabled.
For example, in VLC and Adobe reader , the library no longer shows my SD card.
Same goes for Quickoffice : the file picker only let's me select from my internal storage.
Samsung apps as well as power amp and music apps seem to work fine though.
Does anyone else experience this too? It really blows as my 64gb card is now a paperweight...
I had the same problem, take a look at this page: http://forum.xda-developers.com/showthread.php?t=2617921
It worked for me.
trenzterra said:
Note that I'm not referring to the write issues which I'm well aware of.
But it seems that the new kitkat file picker can't detect my SD card at all, even when 'show advanced devices' is enabled.
For example, in VLC and Adobe reader , the library no longer shows my SD card.
Same goes for Quickoffice : the file picker only let's me select from my internal storage.
Samsung apps as well as power amp and music apps seem to work fine though.
Does anyone else experience this too? It really blows as my 64gb card is now a paperweight...
Click to expand...
Click to collapse
Bluesbrother020 said:
I had the same problem, take a look at this page: http://forum.xda-developers.com/showthread.php?t=2617921
It worked for me.
Click to expand...
Click to collapse
Does that make the external SD card show in apps that use the File Picker as well? I'm currently unrooted and I don't wish to root unless I'm sure it'll be solved. I don't need the write access which the hack was supposed to enable.
This is what I'm referring to:
{
"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"
}
My problem was that Calibre could not write to the ExtSdCard.. I was also not so keen to root, but I thought I give it a go:
I can't give a page, but search for: "root-i9505xxufnb8-android-442-kitkat" and it wend smoot. After that I change the xml and the problem with Calibre was solved. So conclusion: I don't know or that was the same problem, but now the Apps can write to the extsdcard again.
trenzterra said:
Does that make the external SD card show in apps that use the File Picker as well? I'm currently unrooted and I don't wish to root unless I'm sure it'll be solved. I don't need the write access which the hack was supposed to enable.
Click to expand...
Click to collapse
Thanks for the feedback!
Could you help me try the following and see if you get the same results as my screeenshot above?
1. Open QuickOffice
2. Click 'Open a file'.
3. In the following file picker, tap the Menu icon, then go to Settings.
4. Tick 'Show Advanced Devices'
5. Now in the file picker, does it show only 'Internal storage' or both Internal and external storage shows up?
Thank you!
You forgot stap 0... install QuickOffice
As you see at the second screenshot... Intern+media =2.63 free, ext. SD-kaart 3.38 free, so yes.. both are show up
trenzterra said:
Thanks for the feedback!
Could you help me try the following and see if you get the same results as my screeenshot above?
1. Open QuickOffice
2. Click 'Open a file'.
3. In the following file picker, tap the Menu icon, then go to Settings.
4. Tick 'Show Advanced Devices'
5. Now in the file picker, does it show only 'Internal storage' or both Internal and external storage shows up?
Thank you!
Click to expand...
Click to collapse
Bluesbrother020 said:
You forgot stap 0... install QuickOffice
As you see at the second screenshot... Intern+media =2.63 free, ext. SD-kaart 3.38 free, so yes.. both are show up
Click to expand...
Click to collapse
Thank you! I actually assumed QuickOffice was installed by default on KitKat, haha.
Can anyone who is unrooted help me confirm this issue?
trenzterra said:
Can anyone who is unrooted help me confirm this issue?
Click to expand...
Click to collapse
I am not concerned because I stay with 4.3 but i read this explanation in order to better understand.
http://www.androidcentral.com/kitkat-sdcard-changes
Thanks. Fixed my problem
trenzterra said:
Thanks for the feedback!
Could you help me try the following and see if you get the same results as my screeenshot above?
1. Open QuickOffice
2. Click 'Open a file'.
3. In the following file picker, tap the Menu icon, then go to Settings.
4. Tick 'Show Advanced Devices'
5. Now in the file picker, does it show only 'Internal storage' or both Internal and external storage shows up?
Thank you!
Click to expand...
Click to collapse
I followed the steps and got the internal storage.
I'M NOT RESPONSIBLE IF ANTHING GOES WRONG USING THIS METHOD!!! IT'S ONLY ONE THAT WORKED FOR ME, SO I'M JUST SHARING IT FROM MY EXPERIENCE! USE AT YOUR OWN RISK!!!
Hi everyone!
So, i was looking for root my new I8200N. Only way to do it is with VRoot/iRoot chinese application, but it installs Kinguser instead of SuperSu or Superuser. In my experience it's like half root coz many apps doesn't fully work with it. I tried everything i could find but nothing worked. I finally found solution so if you have troubles, here we go:
All requirements in attachment, just unrar it!
1. Install SAMSUNG USB Drivers (Recommended reboot!)
2. On AD (Android Device) go to | Settings > More > About | then press about 10 times on version number to unlock developer features. See at screenshot.
Then go back and enter developer settings. Check USB debugging, OK.
{
"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"
}
3. Connect your AD with USB to PC and finish driver installation if needed in Device Manager.
4. Install VRoot and open it
Between this two, mobile will ask something with long address. Just check remember for this PC or something like that and Allow/OK.. And for white windows, go to Deny or something like that. It's something about Google Play...
On PC press "Root" when becomes available.
Just wait a minute and phone will reboot and it should be rooted. It should be like this:
Optional: You can delete chinese apps that comes installed, you just need "Kinguser".
5. Settings > More > Security | check "Unknown Sources" and OK.
6. Copy Lucky Patcher to AD and install it. Open it and when Kinguser ask for permission, go to Allow. Update if available.
7. In Lucky Patcher go to | Toolbox > Patch to Android > Check:
- Signature Verification status always True
- Disable .apk Signature Verification
- Disable Signature verification in the package manager
Apply
AD will reboot, if not then reboot after it finished.
8. Copy "kinguser.apk" from attachment to AD and install it. Open it and when asks you for update, CANCEL it!
9. Unrar "mrw" from attachment and whole folder copy to AD. I found easier paste it in device than SDcard coz of address we'll gonna need later.
10. Install Terminal from Google Play. https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
11. Open Terminal, type "su" (without quotes) and press enter. When promted for root access, Authorize/Allow it.
12. Now type "sh /storage/emulated/0/mrw/root.sh" (Without quotes). I pasted mrw folder in root of AD, so address is like that one in quotes. You can put it somewhere else, just type correct address. Then press enter. If any error or something comes up, just go for OK or what ever you got and don't worry it's normal. After few seconds, you will be promted for root access from SuperSU, Allow it!
Phone will reboot. Update SuperSU binary and app if needed.
Congratz! You are rooted with SuperSU!
I successfully rooted 2 devices with this method.
Happy rooting!
Just to highlight issues with this, vroot will install apps on your pc without you knowing even after uninstalling.
Also you can completely remove kingroot and replace with supersu by using another mod found on this forum.
You will need an app to mount system as read writable on boot. See the playstore.
Sent from a stolen phone!
That was the only way i could found that really works for me. Days i've been searching for root and this is only i could get working.
To XDA's mods and admins:
I didn't post this thread using DevDB because I had to select a device... from an empty list.
Do you like to waste your time using ADB in text mode? Me neither.
I want to present Yeti FSExplorer - Windows app that will improve your Android device's file managing experience.I wrote it in C# and it needs .NET Framework 4.5 in order to work.
It looks like this (screenshots inside):
{
"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"
}
Click to expand...
Click to collapse
My main goal was to create a PC-like file managing experience and here's what FSExplorer can do:
create new files and folders
delete existing files and folders
batch copy and move files (supported by the file queue)
download and upload files (drag&drop supported)
quick download and open a file from your device (only double-click needed)
check and set permissions (3-digits, e.g. 644)
remember where have you been (this means you can go back, up and further like in Windows Explorer; up to 15 last places)
connect to your ADB WiFi-enabled device
list your device's partitions
work in root mode (SU) (working for every command except download/upload)
Click to expand...
Click to collapse
What do you need?
In order to get Yeti FSExplorer working you need to sell your property and buy a license have ADB installed. This means it has to be accessible for this program. You can either put it somewhere and make proper changes in system's PATH or simply download this and extract to a folder containing FSExplorer.
You'll also need .NET Framework 4.5 or above, so Windows XP is not supported. Sorry for that.
Click to expand...
Click to collapse
Changelog & downloads
Even though it is considered stable version, there can be bugs as in every software. I'm not responsible for any data loss, damage or problems this program caused.
Current version: 1.2 (June 2 2015)
Download link: MEGA, DropBox
Changelog:
1.2:
- fixed and improved IP addresses recognition (thanks, gidano!)
- (probably, needs more testing) fixed directory listing in root mode
- changed About&Credits window style
-------------------------
1.1:
- add "Partitions Info" feature
- fixed handling of "device not found"
- a bit improved error handling
- fixed program's icon
-------------------------
1.0:
- initial version
Click to expand...
Click to collapse
Got any problems? Any feedback?
Any feedback is greatly appreciated. I'm almost sure that there are language mistakes (also the silly ones) I should fix.
If you run into any problems, see any bugs, I'd like to see a message from you, describing the issue, your device and steps to reproduce.
Click to expand...
Click to collapse
Credits:
TheSpecial1 (@ Android.com.pl) for motivating
Mark James (famfamfam.com) for "Silk" icon set (licensed under CCA 2.5)
gidano for reporting bugs
Reserved...
And one more, just in case.
Hi,
I'm in trouble, the app does not work for me...
My S4 with CM12.1 ROM with root and busybox.
What else can I do?
Update: I'm sorry dude! I would like to use the program, but very weak the support! You do not visit in this direction...
gidano said:
Hi,
I'm in trouble, the app does not work for me...
My S4 with CM12.1 ROM with root and busybox.
What else can I do?
Update: I'm sorry dude! I would like to use the program, but very weak the support! You do not visit in this direction...
Click to expand...
Click to collapse
Sorry for replying that late - there were things independent of me and I wasn't able to analyze the source code for (probably) my mistakes so I could explain it here.
Thank you for reporting this.
When trying to connect to your device using ADB WiFi, do NOT write ":5555", the only thing you need is the IP address as 5555 is the only most used ADB WiFi port. If you try to connect to, for example, 12.34.56.78:5555, nothing is done. Then:
1. If connection is established, FSExplorer will refresh itself, trying to list directory "/".
2. If it isn't, you'll get an error message.
Once again, sorry for delay and not clarifying this thing in this program.
Edit:
I'm working on IP address recognition fix now. There's also one more bug (listing in root mode). These two fixes will be included in version 1.2 of FSExplorer.
Edit2:
Version 1.2 is up. I'd like to know if this version works better with your device.
Sorry...
Today I received a notice by e-mail on this topic!
Now it works! Thank you for your work!
Nice to know!
Feature requests and more bug reports are welcome as much as opinions about this app.
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