Related
I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.
Hi everybody. I have a problem with rooting my kindle fire hd. I used this method Method1, Method2, Method3.
In first method all proces has been end sucesfull but my kindle nothing rooted (in superuser i don't see anything aplication.
In second method it's this same.
In third method I can't get permision to create data/local.prop
adb shell
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
Click to expand...
Click to collapse
What I do wrong? I have two superuser apps on my kindle but anything don't get root permision to my es file explorer. I buy this few days ago and I never install before root to my kindle.Please help me.
I restore to factory settings, install root from method1 and now device has been rooter. I don't know why in first time i can't set root to aplication. Now all is ok. You can close this topic
Rooting KindlefireHD 7.2.3
hi,
after i have typed echo 'ro.kernel.qemu=1' > /data/local.prop
kindle told me i have no persmission to do it. But remove hide tmp folder i can be able
anybody can help how to continue?
thanks
Rooting KindlefireHD 7.2.3 - success
dagelo said:
hi,
after i have typed echo 'ro.kernel.qemu=1' > /data/local.prop
kindle told me i have no persmission to do it. But remove hide tmp folder i can be able
anybody can help how to continue?
thanks
Click to expand...
Click to collapse
okey. So, after dancing with ... :cyclops: i was able to get root in my kindlefirehd. Unconfortable was that all this magic i did from my Windows 7 I wasnt able to do it from my gentoo. Dunno still why.
So, about rooting process in windows -> First problem was that adb.exe from both methods (in archve archive) didnt see my Kindle device, despite of fact that kindle storage presented in My computer. Every time i run adb.exe its told me that please insert device or device not visible for ADB.
Then, adb.exe devices returned me only empty output lines.
This problem was fixed by download Andloir SDK tools and copy ADB.EXE from platform-tools to the both unzipped directories from these rooting methods.
After completed first method my kindle was very slow. Second methond with Qemu solved it somehow
So, now i can edit some files via simple built-in texteditor. Also, TitanimBackup now installed on my device.
Also, there is a one note about linux. Especial for gentoo distribution with hardened kernel. Something (dont know still what exactly, maybe PaX configuration) causing that adb returns error :
PHP:
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If you run
PHP:
adb nodaemon server
it will show you exactly the reson what is wrong. In my case it was:
PHP:
error: Operation not permitted: cannot create input thread
.
Solving with command paxctl -m /path/to/file/adb
Hope somebody will found my note useful.
rooting kindle fire hd 8.9
I have tried all methods. Just factory reset and tried method 1,2 and 3 again. Method 2 give this message Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE] after the daemon loads. I am downloading the Android SDk to try and get the latest adb program. Maybe that will work. Any HELP!!:fingers-crossed:
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter.
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when tbe screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wsit till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate itand enjoy.
Pm me if you have any questions or just reply here.
Sent from my KFTT using XDA Premium HD app
Thanks!
Hinzman420 said:
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter.
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when tbe screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wsit till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate itand enjoy.
Pm me if you have any questions or just reply here.
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
It worked for me! Thank you!
Try this man
http://www.oneclickroot.com/tablet/kindle-fire-hd/
Sent from my SGH-T989 using Tapatalk 2
Your welcome I too had a horable time rooting until I pieced this together. Glad it helped
Sent from my KFTT using XDA Premium HD app
Hinzman420 said:
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter.
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when tbe screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wsit till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate itand enjoy.
Pm me if you have any questions or just reply here.
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
I hear you about this being a nightmare. I'm pretty sure got all pre-req, adb drivers and i've checked adb devices and the device appears but i keep getting system/bin/sh permission denied message.
what do i need to fix?
Widodude said:
I hear you about this being a nightmare. I'm pretty sure got all pre-req, adb drivers and i've checked adb devices and the device appears but i keep getting system/bin/sh permission denied message.
what do i need to fix?
Click to expand...
Click to collapse
Try deregistering your kindle and reinstall java then try rooting again. Dont ask why but this worked for me.
Sent From My Kindle HD Running Kinology Rom
Ive installed everything required in the http://forum.xda-developers.com/showthread.php?t=2049288 thread but when i follow in instructions It doesnt work so im either doing something wrong or its the adb not recognizing the device (even though under device manager it says adb interface). Can someone provide me with very noob instructions?
9099 said:
Ive installed everything required in the http://forum.xda-developers.com/showthread.php?t=2049288 thread but when i follow in instructions It doesnt work so im either doing something wrong or its the adb not recognizing the device (even though under device manager it says adb interface). Can someone provide me with very noob instructions?
Click to expand...
Click to collapse
Hi, I had a few problems getting mine rooted but after a lot of frustration I finally managed it...
I'll take it from your post that the ADB drivers went on smoothly.
My main issue was getting the Kindle to be recognised for ADB to work...can you do the following:
Connect your Fire and open an elevated Command prompt. Drill into Bin4ry Stuff folder. If it's on the root, here is what you'd type in the command prompt:cd C:\Root_with_Restore_by_Bin4ry_v18\stuff
next type:abd devices
This will start ADB and check to see if your is connected. Can you post back the output...
It says I have one device attached..doesnt that mean adb is recognizing my kindle? So after that step I would run the RunMe.bat as admin and choose number 1 for normal and I get a ton of code that doesnt work. (The system cannot find the path specified blah blah). Even when I run the RootQemu I get "I must install device specific drivers..." I dont know what is wrong
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
9099 said:
Ive installed everything required in the http://forum.xda-developers.com/showthread.php?t=2049288 thread but when i follow in instructions It doesnt work so im either doing something wrong or its the adb not recognizing the device (even though under device manager it says adb interface). Can someone provide me with very noob instructions?
Click to expand...
Click to collapse
I hope this helps. The following is step by step.
The problem "Device not Found" is usually driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
Download Qemu automated root 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 and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Immediatly proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk to /system/app. Using Root explorer app on the Fire (be sure it has Superuser Permissions). Change permissions on both to Owner: Read-Write, Group: Read and Others: Read. Install both GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Gplay3.8.17.apk to upgrade the the android market to the current Google Play market.
Play Step 8 Download google_apps - unzip to /sdcard/download
Play Step 9 Install Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have provided download links of these above noted files to this thread.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle
Thanks for this great guide, however I am a bit stuck at this stage. Just got a kindle fire HD today for christmas and straight away began to root it, however even though I have ended the adb.exe processes and renamed my android folder to platform-tools-temp I still get a "the system cannot find the path specified error" when running "Root with Restore by Bin4ry v18" even though I can detect the kindle using cmd --> adb devices when the android folder is platform-tools. Any advice you can give to allow it to detect my kindle fire?
I get to step 3, "Run RootQemu.bat from Qemu automated root"
And a little bit after the 1st reboot it says
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
:/
I have the kindle fire hd 7.2.3fw
Errors
Are you both running Windows 7? If yes, open a CMD Prompt "As Administrator", then navigate to each noted batch file. Also, you are using the software I provided through the above links?
prokennexusa said:
Are you both running Windows 7? If yes, open a CMD Prompt "As Administrator", then navigate to each noted batch file. Also, you are using the software I provided through the above links?
Click to expand...
Click to collapse
Yeah Windows 7, 64 bit. I have actually noticed that im getting permission denied errors when running the first batch file.
The device shows up if i do adb devices.
Hang on i will get the output from the cmd box
Quick question: Where do i find the Root Explorer app?
Windows 7 Security Issue
RincewindUK said:
Yeah Windows 7, 64 bit. I have actually noticed that im getting permission denied errors when running the first batch file.
The device shows up if i do adb devices.
Hang on i will get the output from the cmd box
Click to expand...
Click to collapse
Yep, pesky Windows 7. If you find your command prompt, you should be able to Right Hand Mouse click over the shortcut, then choose Run As Administrator - once you have an administrative prompt running, THEN you can navigate to each batch file using "cd".
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
mammolastan said:
Quick question: Where do i find the Root Explorer app?
Click to expand...
Click to collapse
If you do not have Google Play installed yet, then go to the Amazon App Store Search for Root Explorer. It should be free from Amazon too.
So i cleaned out all the drivers for the adb stuff. Factory reset the kindle and all that jazz.
Plugged in the kindle, looked in device manager and saw that it was showing as unknown thingy so i installed the drivers and they went through fine.
Renamed the folder in the android sdk. (
Got permission denied again on the 2nd bit of the qemu bat. Should i be ending the adb process when it says waiting for kindle after reboot?
Anybody else lose wifi, after rooting? It connects but the icon up top has an X on it. I have never seen this before
Sent from my Nexus 7 using Tapatalk 2
Windows 7 Security Issue
RincewindUK said:
So i cleaned out all the drivers for the adb stuff. Factory reset the kindle and all that jazz.
Plugged in the kindle, looked in device manager and saw that it was showing as unknown thingy so i installed the drivers and they went through fine.
Renamed the folder in the android sdk. (
Got permission denied again on the 2nd bit of the qemu bat. Should i be ending the adb process when it says waiting for kindle after reboot?
Click to expand...
Click to collapse
No, once the batch files are running they call to there own internal adb daemon. You do not want to kill these daemons.
So you are opening the CMD prompt "as administrator"? Then through the command prompt you are navigating to RunMe.bat?
You are NOT RH Mouse click over the batch file "as administrator", correct?
For some reason you can not directly run the batch files as administrator in Windows 7.
prokennexusa said:
No, once the batch files are running they call to there own internal adb daemon. You do not want to kill these daemons.
So you are opening the CMD prompt "as administrator"? Then through the command prompt you are navigating to RunMe.bat?
You are NOT RH Mouse click over the batch file "as administrator", correct?
For some reason you can not directly run the batch files as administrator in Windows 7.
Click to expand...
Click to collapse
The batch files are running fine, its more accessing the files on the kindle when its doing what ever it does, i know i have permissions to do anything on this computer. Trust me I do all sorts of weird programmy stuff on this machine.
I just let the Qemu run through regardless of some inital errors and it said it gave me root anyway. I'm gonna see if its correct.
---------- Post added at 02:25 AM ---------- Previous post was at 02:16 AM ----------
Yeah it's fully rooted. But the File Explorer app that people said was free on the amazon app store costs £5. Hmmm :/
ES File Explorer
RincewindUK said:
The batch files are running fine, its more accessing the files on the kindle when its doing what ever it does, i know i have permissions to do anything on this computer. Trust me I do all sorts of weird programmy stuff on this machine.
I just let the Qemu run through regardless of some inital errors and it said it gave me root anyway. I'm gonna see if its correct.
---------- Post added at 02:25 AM ---------- Previous post was at 02:16 AM ----------
Yeah it's fully rooted. But the File Explorer app that people said was free on the amazon app store costs £5. Hmmm :/
Click to expand...
Click to collapse
Good job!
They got popular, now they are charging for it. Oh well, go ahead and download the Root Browser Lite this should get the job done. Although, if you plan to do a lot of upgrades on the Kindle Root Explorer is one of the best.
---------- Post added at 05:45 PM ---------- Previous post was at 05:39 PM ----------
billydroid said:
Anybody else lose wifi, after rooting? It connects but the icon up top has an X on it. I have never seen this before
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
This is a bug, your wireless should be working fine.
I opened a discussion thread yesterday regarding this bug: http://forum.xda-developers.com/showthread.php?t=2064508
Judging by the feedback, they bug was first acknowledged in software version 7.2.3 and has been tied to another display bug, the GPS indicator.
No worries though, your wireless is working fine despite this erroneous indicator.
When it says move the apk's to /system/app, where is that? Do i need to use an ftp program or something?
I wish i could edit my posts sooner. Figured everything out, always seem to do that 10 seconds after posting on here.
APK Files - Root Explorer
RincewindUK said:
When it says move the apk's to /system/app, where is that? Do i need to use an ftp program or something?
Click to expand...
Click to collapse
The APK's are downloaded through the links I provided in the instructions. Once you have downloaded the APK's you move them around and install them using Windows Explorer and Root Explorer or similar application.
When your Kindle is plugged in, you will notice a Kindle drive in My Computer. You use this drive to get files from your PC to the Kindle, then you use Root Explorer on the Kindle to move them around and change file permissions.
Does this help?
Will try your steps on my girlfriends laptop on Thursday thank you so much
whats before this?
prokennexusa said:
I hope this helps. The following is step by step.
The problem "Device not Found" is usually driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Download Root MANY ANDROID! to your desktop. Extract to your desktop. This package includes updated adb daemons.
Download Qemu automated root 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 and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Immediatly proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk to /system/app. Using Root explorer app on the Fire (be sure it has Superuser Permissions). Change permissions on both to Owner: Read-Write, Group: Read and Others: Read. Install both GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Gplay3.8.17.apk to upgrade the the android market to the current Google Play market.
Play Step 8 Download google_apps - unzip to /sdcard/download
Play Step 9 Install Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have provided download links of these above noted files to this thread.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle
Click to expand...
Click to collapse
Do the instructions above start from the very beginning? You mention something about SDK platform-tools. I know i've seen that step in other threads, but its getting confusing (thanks for all of your help BTW). If there are steps before whats listed above, can you edit them back in? I feel like you can get everybody to the promised land if you can fill in a couple blanks. Thanks.
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
fiddystorms said:
Do the instructions above start from the very beginning? You mention something about SDK platform-tools. I know i've seen that step in other threads, but its getting confusing (thanks for all of your help BTW). If there are steps before whats listed above, can you edit them back in? I feel like you can get everybody to the promised land if you can fill in a couple blanks. Thanks.
Click to expand...
Click to collapse
Yes, these are the step-by-step in complete form. There are no steps before.
I got a new phone with a wood back and will be selling my old one soon. Is there an easy way to completely clone my old phone's contents onto my new one?
Could try doing an NAND backup on the old one. Then putting it in the same directory of the new one. The directory would be /twrp/backups/(some numbers assigned to be your phones ID)/backup name.
Your ID will change, but you should be able to use that backup to restore on the new phone.
Sent from my XT1060 using xda app-developers app
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
You might have to make an NAND on the new phone to have the recovery make the new filepath
Sent from my XT1060 using xda app-developers app
kkeller87 said:
Could try doing an NAND backup on the old one. Then putting it in the same directory of the new one. The directory would be /twrp/backups/(some numbers assigned to be your phones ID)/backup name.
Your ID will change, but you should be able to use that backup to restore on the new phone.
Sent from my XT1060 using xda app-developers app
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
You might have to make an NAND on the new phone to have the recovery make the new filepath
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Thanks. This requires root, right? I haven't rooted either of the phones, although I would if it sped this process up. It's something that I eventually want to do anyway.
beelbeel said:
Thanks. This requires root, right? I haven't rooted either of the phones, although I would if it sped this process up. It's something that I eventually want to do anyway.
Click to expand...
Click to collapse
Yea. Sorry. A custom recovery/safestrap is required. I kinda assume anyone who's on XDA has it. Without root I'm not entirely sure how to do it any other way than manually.
Sent from my XT1060 using xda app-developers app
Without root the best you can do is mybackup pro or titanium backup. They will back up app data but not the apps themselves. Get your new phone, download your apps, restore app data from mybackup.
I wrote this before, but this is how you can backup your apps and their data with a computer and without root. Moto X's have Motorola Migrate that can move over some settings.
This process can take a bit to explain, so sorry for the long post.
First, you'll need to install Oracle’s Java Development Kit, which the Android SDK requires. Download and install the 32-bit version. The Android SDK wants the 32-bit version, even if you're using a 64-bit version of Windows.
Next, download the Android SDK from Google. Extract the .zip folder to a location of your choosing, but remember where you put it. If you have the option to open extracted contents in a new window, do so.
Okay, now open the Android SDK Manager (you may have to open a subfolder or two) with administrative rights. You do this by right clicking on the .exe and choosing the option "Run as administrator". A window will pop up, click yes, and after a small wait, the SDK Manager will open.
Now within the SDK Manager, under the tools section, check the box for Android SDK Platform-tools and click Install. This can take some time depending on your Internet connection. Once installed, go back to the open window where you clicked the SDK Manager .exe and navigate to the folder named "Platform Tools". If you're unsure where this is, the SDK Manager has the path of install located near the top.
Now let's get the phone ready. If you can, charge your device to its fullest. Now go into the settings, scroll down to 'development options'. Near the top of this menu, make sure the toggle switch is in the 'on' position. Now scroll down to USB debugging, and tick the box. Tap "OK" when the message shows up. Now plug the smaller end of the USB cable (preferably the one that came with your phone) into the bottom of the phone and the other into an open USB port of your computer. It's best to use a 2.0 USB port (no blue end) and if on a desktop, a port located in the rear.
If your computer starts installing any drivers, let it do this. Once that's finished, go to the window with the Platform Tools folder open. You should see a few files, two named "ADB" and another "Fastboot". Now hold your Shift key, right click in an open area, and choose the option "Open command window here". You may release the shift key at this time.
We're almost done. To make sure your tablet is seen by the computer type:
Code:
adb devices
One device should be listed. If you see no devices, adb can’t communicate with your device because its driver isn't installed properly. In this case, go back to the SDK Manager and download the USB drivers. You may also need to restart your computer.
Assuming you're up and working, type:
Code:
adb backup -apk -shared -all -f C:\backup.ab
This backs up all the installed apps (APK files) and shared storage (SD card) data to the C:\backup.ab file on your computer.
After running this command, you'll have to agree to the backup on the device. You can also encrypt the backup with a password here, if you like (leave it blank if you don't want encryption). Depending on how much data there is to back up, this can take some time. The device will let you know when it's done.
Now for the restoration process:
On the new device, make sure USB debugging is enabled. On the computer, follow the same steps for opening the adb command window. Ensure adb can see the device, then type:
Code:
adb restore C:\backup.ab
On the device, you will need to confirm you want to do a full restore. If you encrypted the backup, enter in the password, then hit "Restore my data". If you didn't add encryption, then leave that area blank. Once the restoration is done, you're good to go.
Thanks for the replies.
Hikikomori-Otaku said:
I wrote this before, but this is how you can backup your apps and their data with a computer and without root. Moto X's have Motorola Migrate that can move over some settings.
This process can take a bit to explain, so sorry for the long post.
First, you'll need to install Oracle’s Java Development Kit, which the Android SDK requires. Download and install the 32-bit version. The Android SDK wants the 32-bit version, even if you're using a 64-bit version of Windows.
Next, download the Android SDK from Google. Extract the .zip folder to a location of your choosing, but remember where you put it. If you have the option to open extracted contents in a new window, do so.
Okay, now open the Android SDK Manager (you may have to open a subfolder or two) with administrative rights. You do this by right clicking on the .exe and choosing the option "Run as administrator". A window will pop up, click yes, and after a small wait, the SDK Manager will open.
Now within the SDK Manager, under the tools section, check the box for Android SDK Platform-tools and click Install. This can take some time depending on your Internet connection. Once installed, go back to the open window where you clicked the SDK Manager .exe and navigate to the folder named "Platform Tools". If you're unsure where this is, the SDK Manager has the path of install located near the top.
Now let's get the phone ready. If you can, charge your device to its fullest. Now go into the settings, scroll down to 'development options'. Near the top of this menu, make sure the toggle switch is in the 'on' position. Now scroll down to USB debugging, and tick the box. Tap "OK" when the message shows up. Now plug the smaller end of the USB cable (preferably the one that came with your phone) into the bottom of the phone and the other into an open USB port of your computer. It's best to use a 2.0 USB port (no blue end) and if on a desktop, a port located in the rear.
If your computer starts installing any drivers, let it do this. Once that's finished, go to the window with the Platform Tools folder open. You should see a few files, two named "ADB" and another "Fastboot". Now hold your Shift key, right click in an open area, and choose the option "Open command window here". You may release the shift key at this time.
We're almost done. To make sure your tablet is seen by the computer type:
Code:
adb devices
One device should be listed. If you see no devices, adb can’t communicate with your device because its driver isn't installed properly. In this case, go back to the SDK Manager and download the USB drivers. You may also need to restart your computer.
Assuming you're up and working, type:
Code:
adb backup -apk -shared -all -f C:\backup.ab
This backs up all the installed apps (APK files) and shared storage (SD card) data to the C:\backup.ab file on your computer.
After running this command, you'll have to agree to the backup on the device. You can also encrypt the backup with a password here, if you like (leave it blank if you don't want encryption). Depending on how much data there is to back up, this can take some time. The device will let you know when it's done.
Now for the restoration process:
On the new device, make sure USB debugging is enabled. On the computer, follow the same steps for opening the adb command window. Ensure adb can see the device, then type:
Code:
adb restore C:\backup.ab
On the device, you will need to confirm you want to do a full restore. If you encrypted the backup, enter in the password, then hit "Restore my data". If you didn't add encryption, then leave that area blank. Once the restoration is done, you're good to go.
Click to expand...
Click to collapse
Thanks for the detailed response. I actually use a mac, and I might have to do some research to see what parts of this process still apply. I may also just investigate other methods of transferring most (perhaps not all) of the data.
beelbeel said:
Thanks for the detailed response. I actually use a mac, and I might have to do some research to see what parts of this process still apply. I may also just investigate other methods of transferring most (perhaps not all) of the data.
Click to expand...
Click to collapse
This may help with getting adb to work on your Mac http://forum.xda-developers.com/showthread.php?t=1917237 Otherwise you could use an application like VMware Fusion to virtually run a Windows OS on your Mac. I know you can get evaluation copies of Windows to use that don't require a product key (they only work for 90 days though).
first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter
If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.
I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter
geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike
Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter
sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!