Related
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.
So for days I have tried to root this thing. I have tried in both Windows and Mac. Something must be going terribly wrong. At this point, there are only a handful of apps I would like to side load. Currently I am trying to install and use ADB. The problem I am having is an error that states over and over ADB server didn't ACK.
I have the ADB mode set up on the nook and can see the little android guy so that is good but I seem to not go anywhere beyond that. When I enter " cat ~/.android/adb_usb.ini" I get # ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0X1949
n0X2080
Which is correct I believe. next command I see to enter is the adb devices it is at this point I get the error.
I do have a Nook tablet (that had gotten broken) but I did have it rooted previously. Anyway. I have browsed. I have tried to burn sd cards (it simply will not boot from them.) Is there someone with tons of Mac exp that will help me please. I am truly to the point of returning this.
Surely I am missing something crucial.
Thanks in advance.
Mkb623 said:
So for days I have tried to root this thing. I have tried in both Windows and Mac. Something must be going terribly wrong. At this point, there are only a handful of apps I would like to side load. Currently I am trying to install and use ADB. The problem I am having is an error that states over and over ADB server didn't ACK.
I have the ADB mode set up on the nook and can see the little android guy so that is good but I seem to not go anywhere beyond that. When I enter " cat ~/.android/adb_usb.ini" I get # ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0X1949
n0X2080
Which is correct I believe. next command I see to enter is the adb devices it is at this point I get the error.
I do have a Nook tablet (that had gotten broken) but I did have it rooted previously. Anyway. I have browsed. I have tried to burn sd cards (it simply will not boot from them.) Is there someone with tons of Mac exp that will help me please. I am truly to the point of returning this.
Surely I am missing something crucial.
Thanks in advance.
Click to expand...
Click to collapse
First forget using ADB for rooting or installing apps. Go to my HD/HD+ CWM thread linked in my signature and either root or install Play Store store to get your apps. You cannot root 2.0.5 with ADB. But you can install apps without root.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
First forget using ADB for rooting or installing apps. Go to my HD/HD+ CWM thread linked in my signature and either root or install Play Store store to get your apps. You cannot root 2.0.5 with ADB. But you can install apps without root.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
Thanks! That makes me feel a bit less incompetent!
Melissa
leapinlar said:
First forget using ADB for rooting or installing apps. Go to my HD/HD+ CWM thread linked in my signature and either root or install Play Store store to get your apps. You cannot root 2.0.5 with ADB. But you can install apps without root.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
Also, I went over there and it will not allow me to comment. I guess because I am a new user. Anyway, do I leave them as zip files? That probably sounds dumb but Mac OS X automatically unzips so I guess I would need to zip them back. Do I just put them as zips onto the sd card and insert it? I am using a Memorex SD HC card 8 GB. Not sure it matters. It is the same card I used on my Nook tablet. Also, do you know if it makes a difference if I copy the files via terminal which really is not fantastic to work with -imo or can I just drag the files to the disk for copying?
You need to leave them as zips on the sd card.
As for Mac OS, no idea there, sorry.
ETA: on my Windows machine, I just dragged the zip file over to the sd card. So, I'm guessing that in Mac, as long as you get the files onto the sd card as zips, it doesn't matter how you get them onto the card.
Hello,
I tried to copy files into the internal storage of my KFHD from Windows 7. The copy process failed. Since I am not able to access the storage anymore.
I read the dir, but I can not remove or create new files.
I booted into TWRP und tried to fix permissions. I got an error message.
Any idea?
Regards
I'm a bit confused what you did so lemme say a few things, mounting internal storage in twrp doesn't work on second gen kindles last I checked. If you flashed cm and can't view the internal storage from windows, its because you need to uninstall the kindle portable device in the device manager and then let it scan for devices again so it can install the drivers that work with cm. Does this answer your question or am I way off base?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I think my description was not sufficient.
After installation of CM10.1 everything worked just fine. The device showed up in Windows.
I tried to copy CM10.2 and gapps to the KFHD USB drive, while doing that an error occured.
Since I do not have write access to the KFHD /sdcard anymore neither under Windows nor under TWRP.
Ah that is weird, I'd go with just pushing the files over adb and see if then problem still exists after upgrading. I have a tutorial that covers it in the kindle general section under something like recovery boot loop after flashing twrp/2nd boot loader, need to put a link to that in my signature...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hi,
I will try to push the CM zip file and the gapps to the "sdcard" directory using ADB.
I will report back tonight.
Hi all,
I'm new here, and I've been trying for the past few hours to root my Kindle Fire HD 7" so I can install a CM10.1 ROM and turn it into a google tablet. I've been searching the web for information, and I kept getting directed here so I decided I might as well join.
Anyway it seems the one method that works is the Bin4ry one, and I started following the instructions given on this site and others. However when I installed the driver, it said the installation was successful but when I clicked "Finish" a window popped up and told me the driver didn't install properly. Then I tried to execute the "Run Me" file, but it gave me this:
"Please connect device with enabled USB-debugging to your computer.
the system cannot find the path specified
doing a backup first, please confirm this on your device
the system cannot find the path specified
Done!"
Nothing happens on the Kindle Fire. But I checked the Device Manager, after I downloaded and installed a driver linked in a thread on this forum, it said the Kindle was USB-enabled interface. Anyone have any idea what the problem is, here? Thanks
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yep, USB-debugging is enabled. It's the same thing as enabling ADB, right? This is what I've done thus far. I'm running Windows 8, so I've disabled driver signature enforcement, and also installed the drivers. I've checked Device Manager---the system has recognized the Kindle as a Google Android ADB interface, and if I check adb devices in cmd prompt, the serial number of my Kindle is listed. Also created an adb_usb.ini file according to these instructions:
"open adb_usb.ini with notepad
(add on one line each!)
0x1949
0x006
save file."
The problem now is not that nothing happens on the Kindle when I run the root tool, I do get the option to restore data but it prompts me to enter a data encryption password. I researched this and a techleopard article said to enter my Amazon password, which I did but nothing happens. The data restore options (Restore or Do Not Restore) just grey out and the root tool just says "Running" for ever and ever. Tried some other root tools such as Quemp and Kindle Fire Utility, but neither worked and besides the more recent information I've seen have Bin4ry's as the only one that works on 7.4.6 which is the OS I am using.
EDIT: Okay, tried it again and for some reason this time the root tool ran successfully. I did a power reset, and ran a RootChecker, and it says it's rooted but I can't find the SuperUser app (the checker also could not find it). Was the root still successful?
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Heh, actually after a LOT of messing around, and perusing several articles across the web and on xda, I've got it working. KFU didn't brick anything, just didn't work. My only regret is that I now can't access the HD quality movies I'd bought from Amazon because Amazon only allows downloading to the Kindle and the Kindle only, and my internet isn't fast enough to stream HD.
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Blastyrant said:
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Click to expand...
Click to collapse
FlashFire can be sideloaded; no need to install the Play Store or any other Google components before/after rooting.
http://www.apkmirror.com/apk/chainfire/flashfire/
I can not get any driver installs to take. I have not been able to start the 5.1.2 downgrade to attempt rooting. This has become rather frustrating.
Installed the Kindle Fire USB Drivers and the device becomes recognized. When I plug it in an "auto run" pop-up appears. But I am unable to connect via ADB to begin to downgrade. I have USB debugging turned on and followed the instructions in the Root Junky video guide. After that I restored my system. I tried to associate the driver via Device Manager but am always unable. My Win7 machine is unable to find them when I search as per the many instructions I've read thus far. From what I've read and seen, I should have an option in the "let me pick from a list of device drivers on my computer" button that says "Android devices" or "mobile" and those (or anything even remotely like them) are never in the list.
I then ran the 15 sec ADB Installer v1.4.3. This copys 0 files, when in THIS video guide it shows it copying 4 files. When asked to "install the USB drivers" the program gives me an error log that says "Invalid command or parameter", which has something to do with DPInst_x64.exe. I do not have the permissions to post in the discussion thread for this tool to ask what I am doing wrong.
After that I tried THIS method. When I browse the extracted folder I get a message that "Windows was unable to install your Fire" and "Windows could not find driver software for your device".
WARNING Do not downgrade below 5.1.2. It has been confirmed to brick the device.
Here is a status update for anyone who is attempting to do the same thing and has been running into obstacles.
I uninstalled all of the drivers. I did this with a system restore. But you could just as easily do this manually. I've also seen some "wipe" tools online that claim to rip out all Android drivers, maybe try one of those if needed? Once they were gone I turned the Fire 7 ADB debug mode on. I then installed the Kindle drivers from Amazon. Then I plugged in the Fire 7 via USB and let it "install drivers". I checked Device manager and this time ADB was showing up. I then shut down the Fire, held volume down+power to boot into Recovery Mode. I had to then manually point the Fire in Device Manager to the correct drivers. Then I sideloaded the 5.1.2 firmware and it has flashed successfully. Next is Root and then CM12.1.
Here is what I did:
To start, it was running 5.1.3 out of the box. I never connected it to WIFI, never altered it, never updated it, etc. It was a stock Fire 7 Gen 5.
1. Delete all previous Amazon driver installations (if required)
2. Install THESE drivers (I'm on Win7)
3. Enable ADB debugging on your Fire tablet (Info can be found here)
4. Download and extract THESE ADB Fast Boot Files from Root Junkys.
5. Download the v5.1.2 OS build from HERE and then verify the SHA1 and MD5 checksums with THIS free online tool.
SHA1: 66B5423725B79CEB0D5866FA32FF414A99A4B50A
MD5: 5B0DCC957DEF3ACCFF58BF33794D6D88
6. Connect your powered-off (turned off, in the off state, etc) Fire 7 5th Gen tablet via USB and then hold volume down+power to boot into Recovery Mode.
7. (perhaps optional) If Fire is not listed as a usable device in Device Manager when in Recovery Mode (or has that warning icon next to it), you'll need to manually point it to the drivers you installed.
.....Select Other Devices > Fire and then Right Click it and choose Update Driver
.....Click the button to let you pick from a list of drivers on your computer. Find the Amazon device (Fire Device) in the list and then choose "from disk".
.....Navigate to the default driver install folder (C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers)
.....Select Android Composite ADB interface (this is for Stock ROM, recovery/adb sideload)
More info for step 7 can be found HERE under "Connecting Your Tablet to Your Computer"
8. Hold Select and Right Click anywhere in the extracted ADB Fast Boot Files folder and choose "Open Command Window Here" from the context menu.
9. In the command window type "adb sideload <path to the v5.1.2 firmware>"
.....IE: C:\Users\MyPC\Desktop\Amazon Fire\ADB FASTBOOT FILES WINDOWS>adb sideload "C:\Users\MYPC\Desktop\Amazon Fire\update-kindle-global-37.5.4.2_user_542168620.bin"
.....You can make this easier on yourself by typing "adb sideload " and then drag-drop the v5.1.2 file into the command widow and the correct path will be automatically populated for you.
.....Click Enter, and allow the process to run its course
You should now be running v5.1.2 stock firmware, which is fully rootable. Next up is rooting and then installing CM 12.1.
I'll start reading up on rooting from THIS thread. I'll make a post with what I did after I have it working.
Rooting...
I watched THIS Root Junkys tutorial video for gaining root access. The Super Tool successfully installed KingRoot, but that application is unable to root this device. So what I did was grab the most recent (as of today: v4.9.5) from THIS thread. I renamed that file to Kingroot.apk and replaced the old version found in the Super Tool "apps" directory. I then went through the normal installation procedure and have gained root. To verify this I blocked OTB updates and disabled lock-screen advertisements.
Next up is installing CM 12.1.
Installing Unofficial Cyanogenmod v12.1 (7/10/2016):
I used Root Junkys Super Tool to install Google Play. The tool does eveything for you so there is no need to type out the steps. You can get that tool HERE
Once Google Play was installed, I linked an account and downloaded/installed the current version of FlashFire.
To install CM 12.1 I followed the instructions in THIS thread.
Next up is tweaking CM to my liking and getting the Play store installed.
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Blastyrant said:
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Click to expand...
Click to collapse
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Davey126 said:
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Click to expand...
Click to collapse
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Blastyrant said:
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
Click to expand...
Click to collapse
Blastyrant said:
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Click to expand...
Click to collapse
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Davey126 said:
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
Click to expand...
Click to collapse
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Blastyrant said:
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Click to expand...
Click to collapse
Blastyrant said:
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Click to expand...
Click to collapse
Glad to hear all is well on both devices and that you are taking time to research and understand the 'why' behind the 'what' & 'how'. Makes the experience much more enjoyable IMO. Not to mention less error prone.
BTW - root procedures are identical for 5.1.1/5.1.2 but it's easy to think they are different reading through the hundreds of contributor posts, some with conflicting information.
I want to use Titanium Backup to backup/restore when it comes time to update CM 12.1. I downloaded it but it says "Root access: Failed". I then downloaded and installed Root Checker by Super User and it says I am rooted. It reports SU Found (/system/bin/su/system/xbin/su) and Busy Box is installed (/sbin, vendor/bin, /system/sbin, /system/bin, /system/xbin). I also ticked on Root access for apps in the Developer options of CM 12.1. I am assuming that I need SuperSU to provide root access to applications?
I installed SuperSU and on launch it asks to update the binary. This always fails. The link it provides takes me to http://supersu.com/insteadbinaryfile.html. It is here that I am getting confused.
Method 2: replace system/ Xbin with SU file, Steps : <-- Where to I obtain the SU file?
Step 1: Install Root.Explorer APK. <-- Is this the app by by Speed Software that cost $3.99?
Step 2: Rename Su to .SU
Step 3: Copy .SU to system/xbin
Step 4: Authorize Su (chmod 0777 .su) <-- I am unsure how to do this.
Step 5: delete the other SU files, such as ksu, etc. <-- etc means what exactly? What are the files I would need to delete?
Step 6: Rename.SU to SU
Step 7: Go back to the desktop to delete the other authorization apps <-- Which other authorization apps?
I feel like I am making something easy into something much harder. Any help would be greatly appreciated!
I uninstalled Titanium Backup and SuperSU. I then ticked off root for apps in developer settings, ticked it back on, and rebooted the device. Then I reinstalled SuperSU and this time clicked the "expert" button on first start. It installed and is working. Then I installed Titanium backup and that is also working. So looks like it was just an order of operations needed to solve my problem.
Revisiting this old thread. I am going to upgrade to the Fire Nexus ROM and post my steps.
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714