[ROOT]Help with 7.3.1 KFHD 7" - 7" Kindle Fire HD Q&A, Help & Troubleshooting

So I have run into several problems using several different methods, none of which have worked properly and I really need some help. Now, I am by no means stupid when it comes to computer stuff but I am not a programmer nor any sort of software engineer. I understand much of the command line stuff and some simple code but I don't understand why nothing I have tried is working. So let me list the problems I've run into in my attempts to root my KFHD 7":
Root Many Android:
I am using v28 (which I believe is the latest and is reported to work on my device hardware and software).
I am unable to run the batch file as an administrator which I believe is the problem that results in the "permission denied" errors when trying to push the packages like superuser and busybox.
I am certain I have followed the tutorial to the letter so I don't know where I am going wrong. I can open the command window as an admin and cd to the C:\Root and run the batch but that doesn't fix the permissions errors.
Qemu:
I am using the latest version.
I select option 1 to root and it runs through the processes but nothing works and it just goes through several reboots so I am assuming it is running into the same issues as RMA, above.
KFFirstAide:
I am using the 64 bit as per my system. I run through option 21 to root my device using method 2 (Preferred).
It shows some success in that I can see the apps BusyBox Installer and Root Checker, however it does not push the rest of the packages necessary and this is evident by when it says I should receive a SuperSU or SuperUser popup, nothing happens and so the rest fails, though it says the root check passes in the final step.
So now I ask, is there a better way or something I am doing wrong with my Kindle Fire HD 7" 7.3.1?
Thanks in advance.

Related

help installing apk using terminal

ok i just updated to CM 5. and well none of my apps are there, now im trying
this following :
sh /sdcard/installapk.sh /sdcard/theapp.apk
and no luck i think i can b doing it wrong.
cant DL the app cause i dont have the market app ether
Download DroidExplorer and you can do a bulk install of all your apps straight to the sdcard. Works everytime!!!
Link is in my sig
yea but i have no market on the phone and i dont have adb set up on my pc is it possible trew terminal to install astro so i can go on from there?
If your market is not there then you failed to flash the gapps.
You need to flash those AFTER CM5 or BEFORE. I've heard it works different for some people. First time I flashed it, it was before. Now it's after. Before and after won't hurt.
i figured that but the link on CM page for gapps is not working for me
I'm not really sure what having the market working has to do with anything. Clearly you didn't even take the time to click the link in my sig and go to the DroidExplorer thread.
it seems like that is for computers 64bit and up i have 32
brios86 said:
it seems like that is for computers 64bit and up i have 32
Click to expand...
Click to collapse
Are you talking about DroidExplorer? I have it installed on my 10 year old Dell and it is definitely a 32 bit machine. I'm assuming you are talking about something else.
You can use busybox if you have the latest CM ROM installed which you do. Busybox is included in the ROM so you can run busybox commands from terminal.
Put the apps you want to install on the root of your sdcard just to make them easy to find. Once in terminal, su so you have a # symbol
Then
Code:
busybox install /sdcard/yourapp.apk /sd-ext/app
great now i am F*** i tried installing the debug phone ota file that was required for CM 4.x and now i have no recovery it comes out the phone with exclamation mark
trying the droid explorer now
no luck droidexplorer seems to view the device but nothing else
brios86 said:
no luck droidexplorer seems to view the device but nothing else
Click to expand...
Click to collapse
Well that makes sense considering Droid Explorer requires root...According to your post on the first page, you are seeing an exclamation point when booting into recovery which means you lost root access by flashing whatever it is you flashed. Time to start all over again.
There is an updated rooting post for the Dream over at theunlockr.com
ok now my thing is i cant have the phone on cause it will keep getting FC and after a few it reboots
im trying to set up ADB on my pc now will that help me fix this? the phone boots up and the it reboots on its owne
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
DirectMatrix said:
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
Click to expand...
Click to collapse
My whole point with the no market is if he would have flashed the gapps or found another way to get them he could have installed a file manager then installed the app off his sdcard.
This was a 1 - 2 minute procedure that he has not made an hour/s procedure.
I agree with droidexplorer, I use it quite constantly. However, if he would have correctly installed CM5 this issue would have never arisen.
As for OP, I strongly advise that you unroot and stick to stock. If you cannot successfully do this, there is a high chance you are going to brick and it's just not worth it.
this is not the first time i try this i have a understanding of what i am doing, for some reason i decided to try another sdcard and it magically booted fine, now the gapps link doesn't work for me, so i am trying to install astro threw terminal emulator (astro is on the root of the sdcard) so i can just install the rest of my apps
thank you busybox worked thank you so much
funny after all the stuff i tried i decided to try a diff sdcard and it booted fine and then changed back to the old sdcard and it works fine

Trouble Rooting Kindle Fire HD

i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Zponds360 said:
i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Click to expand...
Click to collapse
WARNING!!
Firstly your Using a Kindle Fire HD. That is different to the Kindle fire. Even with root I dont think your gonna be running Jelly Bean just yet. You will probably brick the device if you use a standard Kindle Fire ROM!!!!!!!!!!!!!!!!!!!!!
Ok first download and Install the Android SDK. Put it where its easy to find. I use c:\ . Once thats done open SDK manager and tick next to Android SDK Platform-tools and click the box for Install packages.
Once thats done See this page: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
This gives the most stable ADB I have found.
OK next see this thread. This is automated root. http://forum.xda-developers.com/showthread.php?t=1893838.
If that still doesnt work (It didnt for me and others). Watch this Video. http://youtu.be/CYDBoTtdvcE This is the manual method. For a bigger look at the code see this page: http://www.redmondpie.com/how-to-root-amazon-kindle-fire-hd-7-8.9-on-android-4.0.4-ics/
On this page the open quote looks like a tilde EDIT thats actually a grave accent...I always called it the tilde key. Its not just use the KB apostrophe ( ' ) wherever you see a quote!
Hope this helps and I hope I dont get into trouble for posting external Links. Just trying to help!

[Q] Kindle Fire 7" Root

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.

Fire 7 v5.1.3 - help getting started (Root, Flashing CM, etc)

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

ABD wont authorize on ubuntu 16.x

ok i had used the desktop version of kingroot to root the device, and despite my adb drives still refusing to work on windows it worked for both the tablets. but now when i plug it into ubuntu to start removeing kingroot and adding supersu i don;t get the aurthorizeation notafication and i have tried revoking all and disabling and re-enableing adb and restarting computer and tablets but now it just wont authorize. all these simple tutorials have turned out to be complete nightmares for me. i have never had such a difficult time hacking a single device in my life and that includes wiis psps other kindles eta.
Nightmare-Rex420 said:
ok i had used the desktop version of kingroot to root the device, and despite my adb drives still refusing to work on windows it worked for both the tablets. but now when i plug it into ubuntu to start removeing kingroot and adding supersu i don;t get the aurthorizeation notafication and i have tried revoking all and disabling and re-enableing adb and restarting computer and tablets but now it just wont authorize. all these simple tutorials have turned out to be complete nightmares for me. i have never had such a difficult time hacking a single device in my life and that includes wiis psps other kindles eta.
Click to expand...
Click to collapse
Don't know what to say...securing adb access/authorization has not been a high hurdle for most visitors to these pages including many with little/no technical background. Possible you have a finicky USB cable?
Once rooted the SuperTool is only needed to gracefully remove Kinguser. You could pop open the batch file and issue the relevant commands manually as needed. Blocking OTA involves renaming a single file. After that FlashFire can be sideloaded from APKMirror.
yea problem is that super tool is not working on linux it says it is working and success but dose nothing, i can't use the super tool on windows becasue adb drivers not installing despite folowing tutorials closly how to install i just run into problem with no what if that problem not solved. it really sucks howcome is this 5.1.2 so ****ing hard to hack root on. i would rather have to hack 30 wiis blind and 30 psps blind than this. it is just for some reason i keep running into errors. where normaly i run into no errors or common errors that a google search can fix. :/
Nightmare-Rex420 said:
yea problem is that super tool is not working on linux it says it is working and success but dose nothing, i can't use the super tool on windows becasue adb drivers not installing despite folowing tutorials closly how to install i just run into problem with no what if that problem not solved. it really sucks howcome is this 5.1.2 so ****ing hard to hack root on. i would rather have to hack 30 wiis blind and 30 psps blind than this. it is just for some reason i keep running into errors. where normaly i run into no errors or common errors that a google search can fix. :/
Click to expand...
Click to collapse
- sorry for your troubles
- not hard for most; many with no technical background have made it
- perhaps find a friend with a different host

Categories

Resources