Related
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
jma9454 said:
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
Click to expand...
Click to collapse
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
I have witnessed one demo unit that was completely unrootable even with the use of a factory cable. So at the end it was only good for parts and the motherboard unusable.
soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
That`s pretty much what I experienced with the demo unit that would not root, it simply would not enter fastboot no matter which approach I took. I can take a look for you but I feel it`s pretty much a moot point if it wont enter fastboot. Power the device off, open a terminal
Code:
fastboot -i 0x1949 getvar product
hit enter, when it says waiting for device, plug the kindle in. if it does not enter fastboot and return product: kindle you are dead in the water.
jma9454 said:
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
Click to expand...
Click to collapse
I've really gotta start reading the names on these posts
jma9454 said:
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
Click to expand...
Click to collapse
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
In my opinion, your best bet would be to forgo the VM, forget about the dilapidated WinXP computer and figure out a way to boot your Win7 computer into Ubuntu from a USB stick. You are dealing with way too many variables to effectively determine exactly where things are going wrong.
I 'fixed' two demo KF's, messed up a lot on the first (lucky I didn't brick it).... On the second, I used a fast boot cable and installed TWRP, had a JB ROM on it in 15 minutes.
Try this.... Send TWRP to it using the command line, when it says 'waiting on device', open another window and get it to reboot in fastboot mode. On the first KF I found the utility would only put it in fast boot for a few seconds, but it was long enough to write TWRP if you did it this way.
Not sure why some won't work at all, maybe Amazon got smart on the demo units.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
soupmagnet said:
I've really got to start reading the names on these posts
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
Click to expand...
Click to collapse
The above statement took place from USB boot, not VMware. Also, like I said, I attempted to set it into fastboot and it just booted regularly. I tried several times with different cables and ports with no success.
Sent from my Amazon Kindle Fire using Tapatalk HD
I will stick with my original idea no fastboot = no fun. You cant push FBmode manually because installation from unknown sources is disabled by default on a large percentage if not all demo units. Regardless if the device doesn`t enter fastboot not much you can do. Taking advantage of the small window of fastboot at boot is risky if the write time isn`t long enough to get it sent and written but it could be your best bet. IMO I would not attempt this with the bootloader only recovery no harm no fowl.
Hello, I Have a Kindle Fire 1st Gen. I Had CM 10.1 on it. I was attempting to put AOSP back on it for My Wife. I did I Noobish Move at 4 am half asleep, I Did NOT go into advanced mode in TWRP and uncheck DATA in the Wipe tab. So This Screwed me "Bricked" Message comes up in TWRP when rebooting, says ( NO OS ) . I have Tried Kindle unbrick utility with no success when clicking on "Stuck at Logo" in utility I get this Error ...> PIC Attatched!>
I then Tried Using android-sdk ( I have went in and edited the files that need to be edited in program files/android...> File_android_winusb as well as in .android folder in the appdata location) Along with CMD & I get a Error So far into the process of Resetting Kindle OS. Pic Attatched as well. It Seems Like I have something missing ?!?!?
I somewhat Suck at CMD, I don't have much experience with it, so Please go slow on me,when Giving advise....
Thanks In Advance!!
If you still have access to TWRP, use it to mount your sdcard to USB.
soupmagnet said:
If you still have access to TWRP, use it to mount your sdcard to USB.
Click to expand...
Click to collapse
I Tried That. I See the Device But when double clicking, It will not let me access it.
Butt Nugget said:
I Tried That. I See the Device But when double clicking, It will not let me access it.
Click to expand...
Click to collapse
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
soupmagnet said:
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
Click to expand...
Click to collapse
My Kindle is a 1st Gen. I'm not sure If I understand what You are talking about when You say "send Commands/devices" If Your talking about in CMD I Get all the way to Seeing my Device Serial Number for Kindle. The when I type "adb shell" I get a error saying (Failed: No such file or directory <2> - ) You can see this in the screen shot I attached to this thread..
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
soupmagnet said:
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
Click to expand...
Click to collapse
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver. So Sounds possibly what I tried is totally different from what Your asking if i done? If So, Could You Explain step by step thee method with new roms or send me in the right directions 2 a how to link or video? Anything I would appreciate GREATLY! :fingers-crossed:
Butt Nugget said:
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver.
Click to expand...
Click to collapse
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
soupmagnet said:
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
Click to expand...
Click to collapse
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Butt Nugget said:
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Click to expand...
Click to collapse
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
I am attempting to understand what u are saying But I'm thinking ur not giving full step after step instructions OR this Version I have (v2.6.0.0) differs from Yours, Because there is No such OPTION as ADB PUSH..... I have ADB sideload (under Advanced Tab) which only wipes Cashe.. I've looked in every single area in TWRP and see nothing of anything You are talking about, other than "MOUNT" obviously.
soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
While Searching Google for Help I seen this..> http://forum.xda-developers.com/showthread.php?t=2361144
I'm bout to install a Pc with Linux and try pushing it that way.. Have not tried that.
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunt Thnx... You Helped breaking it down. I just used KFU and Fixed this within 3 minutes.. Thnx Man!:good:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
larryb1951 said:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
Click to expand...
Click to collapse
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
frustrated kindle nooooob
stunts513 said:
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
Click to expand...
Click to collapse
Revision: Well it appears some how i Have my kindle rooted if i run root checker it says it is and busybox you answered my question about twrp and a second bootloader so i guess i will wait for an update hopefully soon not sure how i accomplished this bc the last thing i did was a factory restore but i have run root checker and it says it ok. my next question is can i still load google store with the stock loader until a fix comes for twerp and 2nd bootloader??????thanxxxxxxx ps whats the old proceedure?
You can still use the Google play store as long as it is rooted, also as to the method there are 2, one is for people not familiar with command line, while the other is purely from command line. While I am completely comfortable with command line myself, I used the fire flash method, the only thing you have to make sure you don't skip is the part where you check the box either above or beside the red warning text or you will have a nice red screen brick on reboot that usually you can recover from. Somehow people don't see that checkbox. Either way the bootloader has to be downgraded first, if you do it the command line way you will definitely want to md5sum the file to make sure it is a perfect downloaded copy of the original or risk a hard brick. The guides on how to do it are here:
Fireflash
Command Line
Sent from my Amazon Kindle Fire HD using Tapatalk
Very Frustrated NOOOOOOOOOB
What should I charge to replace kfhd8-freedom-boot-8.4.6.img like my version 8.4.8
boris_m80 said:
What should I charge to replace kfhd8-freedom-boot-8.4.6.img like my version 8.4.8
Click to expand...
Click to collapse
you don't theres not a newer verison out yet, just use the old one and put the rom you want to flash on it ahead of time so when it bootloops you can flash anothe rrom instead.
stunts513 said:
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
Click to expand...
Click to collapse
Dam I should've read this before i tried to do mine.
It was 8.4.8 and its stuck on the twrp now coz i used the old freedomboot image with it.
If anyone could tell me a way to revert back to amazon or just get out of this loop i would be very grateful. thanks!
Adb push.... See my pm that explains further.
Sent from my Amazon Kindle Fire HD using Tapatalk
only Partly frustrated noob
stunts513 said:
you don't theres not a newer verison out yet, just use the old one and put the rom you want to flash on it ahead of time so when it bootloops you can flash anothe rrom instead.
Click to expand...
Click to collapse
Well I have the rooting down and the playstore down ive done it so many times as well as restore and factory resets now my problem is
1. first i can boot to fastboot by using adb commands but if i try to boot to fast boot using for instance KFFirstAide it just sits at waiting for device but i can command fast boot and reboot to normal from ADB . Fast boot commands dont work any fix for that.
2. I have tried to load the google aps using the tutorial both automatically and manually but cant seem to get them to work during automatic it returns with not enough disk spave for half the aps and trying to do it manually there are about 6 apks it will not let me move to system aps folder and will not let me move any of the lib.so files to system/lib says copy or move failed no reason given any body have any ideas about this thx i have have done and half not lol i see a restore again in my future if i dont get this figured out. Tried to ask in the KFFirstaide Thread but i think they are gone???????
BTW kindle fure hd 8.9 8.4.8 rooted and playstore and ES3 installed THANX
You probably didn't mount the system partition as read write before you attempted to copy. BTW Don t use the MV command across partitions, it doesn't work correctly for some reason last I checked. If you are doing this from an adb or uneven if you aren't, run this:
Code:
adb shell
su
mount -o rw,remount /system
Now copying files to system should work.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You probably didn't mount the system partition as read write before you attempted to copy. BTW Don t use the MV command across partitions, it doesn't work correctly for some reason last I checked. If you are doing this from an adb or uneven if you aren't, run this:
Code:
adb shell
su
mount -o rw,remount /system
Now copying files to system should work.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks again u always have the answers how about the fast boot issue any ideas?
I'm a little confused as to what it's doing but maybe I didn't read far back enough(also I had a almost complete post in tapatalk, came back half an hour later to finish and bumped the back button and cleared my post... OK let's see if I can finish this post without throwing my kindle across the room...) Alright first things first, if it's going into fastboot and your commands aren't worming with it keep in mind you have to install the adb driver again when it goes into fastboot. If it already doesn't show up as jem or tate or w/e and shows up as an adb device when in fastboot then remember this: fastboot commands have to be prefixed on kindles with "-i 0x1949", like so "fastboot -i 0x1949 getvar product". Hope that helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I'm a little confused as to what it's doing but maybe I didn't read far back enough(also I had a almost complete post in tapatalk, came back half an hour later to finish and bumped the back button and cleared my post... OK let's see if I can finish this post without throwing my kindle across the room...) Alright first things first, if it's going into fastboot and your commands aren't worming with it keep in mind you have to install the adb driver again when it goes into fastboot. If it already doesn't show up as jem or tate or w/e and shows up as an adb device when in fastboot then remember this: fastboot commands have to be prefixed on kindles with "-i 0x1949", like so "fastboot -i 0x1949 getvar product". Hope that helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
well let me see if i can explain better using firstaide if i run diagnostic and boot to fastboot it goes in to fastboot and boots out using adb commands and if i send a fastboot command while it is off it boots into fastboot but if i run option thats says if kindle can respond to simple fastboot commands it says i have a damaged
*********************************************************
* This Option Will Use A Fastboot To Command To Simply *
* Query The Kindle To Display It's System Informtion *
* This Simple Non-Destructive Command Is A Good Way To *
* Determin If Fastboot Is Enabled And If The Kindle Is *
* Responding To Simple Commands. If The Kindle Responds *
* To This Command It Is Safe To Proceed With Other *
* Fastboot Commands. *
*********************************************************
Press any key to continue . . .
*************************************************
* OK Here We Go, We Are Beginning The Process! *
The system cannot find the file specified.
*The Kindle Is Not Responding To Simple Fastboot*
* Commands. Check The Device Manager For Yellow *
* Traingles. If You See One Or Two Traingles *
* Post The Screen Shot In Our Thread. You May *
* A Damaged Recovery Partition. *
*************************************************
< waiting for device >
and thats what i get. Thx
oh and still cant copy those files for google aps procedure just dont get it i can copy some of the apks to the system/aps folder and change permission so system must be rw but there are 7 of them i cant and cannot move any of the lib files at all to the system/lib folder im perplexed
This is why I do things manually... I get more technical output. Shift + right click kffa's folder and hit "open command prompt here"(or something like that. )Type "fastboot -i 0x1949 getvar product" and press enter while your kindle is in fastboot. See if it responds.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
This is why I do things manually... I get more technical output. Shift + right click kffa's folder and hit "open command prompt here"(or something like that. )Type "fastboot -i 0x1949 getvar product" and press enter while your kindle is in fastboot. See if it responds.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
C:\KFFirstAide>fastboot -i 0x1949 getvar product
< waiting for device >
thats the result!
Sounds like its either not showing up or is a driver issue then. If it doesn't show up while in fastboot, that's usually bad. If it doesn't show up, I believe you should be able to reflash the bootloader from inside whatever os is on it as long as it is rooted. Wouldn't suggest doing that unless you have to.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Sounds like its either not showing up or is a driver issue then. If it doesn't show up while in fastboot, that's usually bad. If it doesn't show up, I believe you should be able to reflash the bootloader from inside whatever os is on it as long as it is rooted. Wouldn't suggest doing that unless you have to.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
well i can boot to fastboot using adb if i need be so really not sure there is a real problem unless i have to use fast boot command then it will fail but as long as i have the option to boot to fast boot using ADB maybe im better off leaving things alone ?
larryb1951 said:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
Click to expand...
Click to collapse
Im in your same situation, just got the same exact kindle with 8.4.8. Would you mind telling me which tutorial you finally used that worked? I have been rooting and putting custom roms on my galaxy s4 for a year, jailbreaking iphones for years, etc., but this rooting the kindle is just driving me crazy trying to figure out what instructions to follow that dont leave me with an expensive brick. All I really want to do is be able to install google play store and apps, and change the background and/or lockscreen wallpaper... Thanks,..
Solange82200 said:
Im in your same situation, just got the same exact kindle with 8.4.8. Would you mind telling me which tutorial you finally used that worked? I have been rooting and putting custom roms on my galaxy s4 for a year, jailbreaking iphones for years, etc., but this rooting the kindle is just driving me crazy trying to figure out what instructions to follow that dont leave me with an expensive brick. All I really want to do is be able to install google play store and apps, and change the background and/or lockscreen wallpaper... Thanks,..
Click to expand...
Click to collapse
welli have rooted my kindle hd about 25 times now seem, to have no problem with that and added the play store. I used the KFFirstAide Tutorial works like a champ as far as as background and lock screen thats beyound my minimal knowledge but i believe you will need to add a custom rom t for that and i am not brave enough yet to try that im sure one of the really smart hackers could answer that. I have been able to get individual apps to load but i didnt have any luck with the install google aps part of that tuturial but the rest works fine. Good Luck
Yeah I prefer custom ROMs any day over Amazon's os. The fireflash method is the easiest as it doesn't involve any command line at all. Though it seems most people for get to check off the box next to downgrade bootloader because the warning text telling you that you need to makes it hard to notice the check box... This results in a pita to fix because we have to get into fastboot. I think I heard its even worse on 8.9 inch models when this happens because sometimes the bootloader won't show up as a fastboot service briefly and since fastboot cables don't work on 8.9 models they were screwed. But I don't tend to worry about these kinda things.
As for the wallpaper, the fix in my signature should do it, its a little buggy. Sometimes it causes peoples status bar to disappear, not sure why, assuming the dalvik cache and cache need to be cleared in such a case.
Sent from my Amazon Kindle Fire HD using Tapatalk
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???
OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?
schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.
rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.
Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.
Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT
While trying to get Android Pay to work I removed root from my phone using the option in Kingroot's menu and then restarted. Now FireOS doesn't load and doing a factory restart from recovery doesn't do anything either.
I thought I'd just sideload 4.6.3 and restart from scratch, but when I connect my phone in 'sideload from adb' mode from recovery I only get a "Fire" device in device manager. After a minute it gets an error "Device Cannot Start"
Manaully scanning for hardware changes doesn't give me my "Android Composite Device ADB Interface"
Sounds like you don't have the ADB drivers installed correctly. See this post:
http://forum.xda-developers.com/showpost.php?p=62844581&postcount=14
Thank You. That's exactly what was wrong.
I didn't think was would be the problem since I had used that 15 second adb installer last night to get adb working before I messed everything up this morning.
In recovery mode I'm sure it connected to my computer as a different device!
Thanks again.
ekztal said:
Thank You. That's exactly what was wrong.
I didn't think was would be the problem since I had used that 15 second adb installer last night to get adb working before I messed everything up this morning.
In recovery mode I'm sure it connected to my computer as a different device!
Thanks again.
Click to expand...
Click to collapse
No problem. Glad it worked out.
cannot read update.bin
Hi
I have the same problem with my phone. I have downloaded 1.2 gb 4.46.3 fire os update but I am not able to push the package after detecting my fire phone in adb sideload method.
cannot update.bin error was thrown by cmd prompt.
How can I recover my phone . Pls help.
Androidhari said:
Hi
I have the same problem with my phone. I have downloaded 1.2 gb 4.46.3 fire os update but I am not able to push the package after detecting my fire phone in adb sideload method.
cannot update.bin error was thrown by cmd prompt.
How can I recover my phone . Pls help.
Click to expand...
Click to collapse
The problem could be the filename. Microsoft Edge and Internet Explorer download the 4.6.3 update as a .zip file. If your folder options are not set to display all files extensions, go to Veiw> Options> Change folder and search options> View>. Uncheck "Hide extensions for known file types" and click OK. Check the filename for update.bin, if the filename is update.bin.zip, changing it to update.bin should correct your problem.
If the fielname is correct, the file path could be the problem. Try entering the complete path to the file, use quotes around the file path if there are any spaces in the file path (for me the file path is: "C:\Program Files (x86)\Minimal ADB and Fastboot\update.bin").
If you still can't install the update, then see Problem with "cannot read update.bin" in 4.6.4 to 4.6.3 downgrade on how to use Safestrap to install update 4.6.3.
Hi
Even my phone is bricked but when I try to sideload update.bin , cmd prompt throwing error as " cannot update.bin". My fire phone is identified by windows 10 with adb drivers.
Can someone suggest how can we fix this issue?
Thanks
---------- Post added at 01:45 PM ---------- Previous post was at 01:35 PM ----------
Thanks, I will try what you had suggested on windows 10 but I can not use safestrap as except " amzon" logo I can not see anything after power on so I am getting to apply update from ADB using buttons. So how can I install safestrap and king root without turning on browser on mobile.
Thanks
Androidhari said:
Thanks, I will try what you had suggested on windows 10 but I can not use safestrap as except " amzon" logo I can not see anything after power on so I am getting to apply update from ADB using buttons. So how can I install safestrap and king root without turning on browser on mobile.
Thanks
Click to expand...
Click to collapse
You won't be able to install Safestrap or Kingroot unless you can bootup your Fire Phone, so sideloading the update is your only option. It appears that your ADB drivers are installed correctly, just to be sure, see DePingus's post.
Thanks, it worked. My fire phone is up.
Hi a little help if you will please.
I've rooted then installed safestrap. Done back up, factory reset then Flashed c11 rom. All looked great. Made up with the ROM but I've tried to use kingroot to root again but it won't work. I can get in to safestrap recovery but says it's inactive. I've tried to search for the fix but can't find anything directly for my problem just how to root with kingroot. Any help would be great. Thanks.
Can't unbrick it.... tried everything
Hi guys, I installed CyanogenMod on my fire phone and it worked for a while... then started rebooting, but before I could do anything it was just rebooting all the time, then I did a hard reset on fire phone and after that... only adb sideload, safestrap was gone... but... adb works fine, everything gets installed, but after rebooting amazon fire phone is lost in a endless rebooting cycle (just shows up the amaozn logo... if powered via USB it tries to do something else, amazon logo shows up for maybe 2-3s longer....
Boys... did I brick my phone forever? Thanks
Hannes