Develop Bugs

[Q] Kindle Fire with 6.3 Help with Rooting Please

Hi,
I am a total noob. I don't even know the proper expressions for this whole thing.
So this is my case:
I am outside the US and bought the Kindle Fire with a 6.3 firmware, couple of days ago.
Being curious about what it all can do, created a fake account with a test credit card as I read somewhere in the net.
Then downloaded the KFU 0.9.5 and rooted the device, everything went according to the plan, so I thought.
Then I discovered I had to use something called Market Opener to install other apps. But this Market Opener never worked.
So I found out that I had to change permissions. But this cannot happen as I get that message that adb services can not run in production builds etc. whatever that may mean.
So I downloaded Android SDK, followed the instructions installed it but I still cannot get into the root and change folder permissions. Sometimes it recognizes the device, sometimes not and when it does it tells me the same thing as above.
Then I would need some .apk to do the thing on the device but I cannot install those as I don't have the Market Opener or the Google Play and I cannot get those if I don't have superuser permissions to change things in Folders.
Basically I have been spending the last 3 days in searching the net for answers but to no avail.
So, can someone help me please? What I need to do is being able to install some apps including Market Opener / Google Play and being able to watch Amazon VOD. Is this possible?
Please bear in mind that I have no clue of the specific language, i.e. I don't know what flash is and how to do it nor I know how to do a backup and restore or how to reset everything in the original state.
SO if some of you have the patience to help, please advice me with some noob language so that I can understand.
Thanks in advance for the help that will come

Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.

brainchow said:
Are you looking to put a custom rom on it or just root? If you're looking to keep Amazon services, you can put MoDaCo's rom on it, which is just like your kindle out of the box with a few extra bells and whistles. There are alot of guides floating around on how to get ADB working. There's an excellent beginners guide in the General section that I highly advise checking out.
Noob terms: if you want to keep the Amazon experience, I reccomend MoDaCo. Look for it in the development fourms.
Click to expand...
Click to collapse
Thanks for ur answer.
I have read a lot of guides out there but I seem not to be able to get the ADB working as I always get the message I gave in the original post plus the fact that sometimes it recognizes the device and sometimes not.
I have read the beginners guide which was excellent but without the ADB working there is little I can do I suppose.
As I wrote, I want to play with the device to see what it is able to do and want to use the Amazon VOD if possible. I.e. I would like to be able to use Google Play to get apps on will and still keep the Amazon services. Would that be possible with the MoDaCo staff?
Ok. I downloaded the MoDaCo staff.
Must I reset the kindle to the factory settings before I install that? If yes, how?
And how do I flash it?

Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium

a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.

soupmagnet said:
Make sure you are in fact rooted.
You seem like you know enough about adb to try the following commands.
adb shell
ls /system/xbin
Look for a file called "su" in the list
Then...
ls /system/app
Look for a file called "Superuser.apk"
A lack of either of these means you're not rooted and may be the source of your problems
If you are trying to change system file permissions through adb...
adb root
adb remount
adb shell chmod blah /blah/blah/yadayada
Just don't literally type "blah /blah/blah/yadayada"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Thank you for your answer.
I would gladly follow your advice but the adb does not find my device. I don't know whether this is normal and if I must reboot my PC.
The kfu also gives me an offline status...

brainchow said:
a factory reset won't really help you because you're basically replacing the operating system. pretty sure all amazon services are working with modaco. to install it, look around for a guide on how to install something called firefirefire (FFF) and TWRP. pretty sure that can all be done with kfu in a couple clicks. then copy the modaco zip onto your kindle, go into the wipe menu and clear out system, cache, dalvik cache, and data (factory reset), then go into install and choose the modaco zip. reboot and you should be set.
Click to expand...
Click to collapse
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?

its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
---------- Post added at 07:53 PM ---------- Previous post was at 07:51 PM ----------
GreekCY said:
Thanks again for the fast answer. I am impressed!
Doesn't the FFF and the TWRP get installed automatically with the kfu?
Click to expand...
Click to collapse
haha, no problem .
if FFF was installed, you should see a picture of fire in a caution sign or an android logo over the kindle fire logo when you boot it up. if all you see is kindle fire, then you don't have fff. im pretty sure you need fff to get into twrp. if fff is installed, you should be able to hop into fastboot and install twrp if it's not installed yet.

brainchow said:
its most likely your computer. a reboot might help. if not, how did you install the drivers? are you using a mac or pc? try installing the drivers that came bundled with KFU.
if you're using a PC, go into device manager and see if something about android ADB pops up. if not, it's your drivers.
Click to expand...
Click to collapse
I am using a PC ( a netbook, don't laugh, I'm on vacation!!)
I installed the drivers using the install_bat from the kfu.
In device manager I see Android Phone and underneath Android Composite ADB Interface...

interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.

If adb has trouble recognizing your device, it means it's a driver issue. Either Windows, KFU or a combination of the two causes the drivers to fail for some reason.
Uninstall/delete your current drivers in device manager (may require reboot)
Turn your Kindle off
Reinstall drivers
Turn your Kindle on
Retry adb commands
Sent from my Amazon Kindle Fire using xda premium

brainchow said:
interesting. check my previous post and see if you have FFF installed. adb should be working fine if device manager can find it. if you can, run adb devices into cmd and see if it picks up your kindle. not sure if the stock rom has a development switch in the settings.. if there's an option to enable usb debugging, make sure that is on. if not, just try moving usb ports and running adb devices.
Click to expand...
Click to collapse
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!

GreekCY said:
I have FFF as I see the fire in a caution sign (yellow triangle thing right?)
ADB still doesn't pick my kindle after a PC restart.
No usb debugging available in the stock rom.
I will uninstall and reinstall the drivers from device manager.
Thanks again for your prompt help. I am oblidged!
Click to expand...
Click to collapse
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.

brainchow said:
that's fantastic... if you have FFF, try pressing the power button a couple times as it turns on and see if you can get into recovery. you shouldn't need adb now. if you can get into recovery, just wipe and flash the new rom. if you don't, you can use fastboot to install it.
Click to expand...
Click to collapse
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
And in which directory should I transfer the MoDaCo Rom?

GreekCY said:
Ok...I reinstalled the drivers
now ADB gets the kindle
I do adb shell
then ls / system /xbin
no such file or directrory
the same goes with the
ls / system / app
But if I give su I get
su
#
Now what?
Click to expand...
Click to collapse
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
SU (substitute user) in shell is different from the su binary
Make sure you are typing "L"s, not "i"s then /system/xbin
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I really do type "L"...still ls/system/xbin: not found

modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.

brainchow said:
modaco can go anywhere in the kindle.. just copy it somewhere. then press the power button a couple times when FFF comes up and see if you can get into twrp.
Click to expand...
Click to collapse
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!

GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
Space between ls and /system/xbin and no other spaces
It IS there, your Kindle wouldn't work otherwise
Sent from my Amazon Kindle Fire using xda premium

GreekCY said:
I really do type "L"...still ls/system/xbin: not found
Click to expand...
Click to collapse
if you want to use adb, should be ls /system/xbin. make sure you put the space after the ls. i would still recommend flashing modaco nevertheless... that shouldn't need adb. just maybe fastboot if your recovery isnt installed.
---------- Post added at 08:59 PM ---------- Previous post was at 08:57 PM ----------
GreekCY said:
Guys? I just installed ModaCo and it seems it works fine. Google Play seems to work and all my data are still there (I mean the books I uploaded). If this is right then.... THANKS TO ALL OF YOU SO MUCH!!!!
Drinks are on me! Now I go to sleep! Will keep you informed!!!
Thanks again!!!!
Click to expand...
Click to collapse
no problem... enjoy
i would still recommend wiping data and the two caches to ensure that it's bug free. but if everything works fine, so be it.
have fun

[Q] [ROOT ERROR] KF 6.3.1 using KFU V0.9.6

I have been trying to root my KF 6.3.1 using the KFU 0.9.6
When I connect it shows
Status : Online
BootMode : 4000
I proceed to 'install permanent root with superuser'
It runs a lot of code...
which has a lot of error messages in it...
Finally... it shows SUCCESS...
The SU app also gets installed on the device...
But I tried to run apps that require rooted device and they give an error message saying 'your device needs to be rooted.'
Attaching output of root operation with the message.
Experts and Gods - please help!
NOTE --
Currently using Windows 7 as laptop OS
ADB drivers seem to be working correctly because I'm also able to push install apps on the device using the "adb install xyz.apk" method.
The device shows as Android Phone > Android Composite USB Interface in device manager.

do you have allow installation from unknown sources checked? And you say that device manager shows android composite usb interface? it should say android composite adb interface.
---------- Post added at 12:57 AM ---------- Previous post was at 12:52 AM ----------
shift+ right click on the tools folder in the kfu and open in command then type adb devices if its return by a string of numbers that shows your device connected

It's not downloading the files... second person it happens to.
If you're going to try downloading them manually, do so from files\files.log and make sure the hashes match those present in that same file, to avoid issues.
Get the ones called openrecovery-twrp-blaze-2.1.1.img and fff-u-boot_v1.4a.bin.
Place the downloaded files in recovery (make that folder if it doesn't already exist) with the names twrp.img and fff.bin, respectively.
Or just go with the manual method for rooting: http://forum.xda-developers.com/showthread.php?t=1568340
And then install TWRP and FFF separately. FFF is particularly important to have an extra layer of protection.
Also, have a read here: http://forum.xda-developers.com/showthread.php?t=1552547

Stuck with same problem, please help me.
Iam a newb . I am also stuck with same problem .It says rooted succesfully but its not rooted. please help me how to root kindle fire firm ware 6.3.1 manually . iam unable to understand how to do in windows7.
Thanks in advance.

Try redownloading kindle fire utility seems its missing some parts also you must be connected to the internet for it to fetch the required files

I am having the same problem. I ran the KFU, it didn't install TWRP or FFF but gave the message at the bottom that SU had been installed.
Couldn't actually use any programs that required root.
I went and tried to run the KFU from C:/ (first mistake, I did not move it to C:/ before executing), but now it does even less than the first time around, it looks like everything is failing.
Also, I downloaded and dropped the TWRP and FFF files in the recovery folder, that appears to work but the MD5 checksums are not adding up. It appears that the KFU cannot find the files.txt to see where to download the recovery files, nor to confirm the checksum.
So I tried to do it the manual way, I can get as far as running the fastboot flash commands. They get "OKAY" for both twrp and fff. Now I am expecting the kindle to reboot, but it just sits there, in fastboot mode. When I try to run a reboot command, it says no device.
Ideas?

JDBeck23 said:
So I tried to do it the manual way, I can get as far as running the fastboot flash commands. They get "OKAY" for both twrp and fff. Now I am expecting the kindle to reboot, but it just sits there, in fastboot mode. When I try to run a reboot command, it says no device.
Ideas?
Click to expand...
Click to collapse
Hope you at least checked the hashes first.
Are you going with adb reboot or fastboot reboot? If you're in fastboot mode, "fastboot reboot" is the one to use.

Dasanko said:
Hope you at least checked the hashes first.
Are you going with adb reboot or fastboot reboot? If you're in fastboot mode, "fastboot reboot" is the one to use.
Click to expand...
Click to collapse
Hashes?? hahahah oops!
I actually made it past that part, I rebooted manually, it booted to fff, I kicked it to recovery mode with the power button and then performed a backup. Ran the next few commands with no problems.
I got to the part where I change the check_rooted file... when I run the mv command it tells me "Read-only file system".
EDIT!
I realized that I needed to go back into recovery mode to run the mv command. fastboot 5200 command, and rebooted... now I have twrp on the KF, I run the mv command again, but this time it says "no such file or directory". I hopped into the adb shell and cd'd over to the system/bin directory and did an ls command. Sure enough, it appears to be empty. But when I boot it up in normal mode, and cd over to /system/bin, it's full of files, including check_rooted.... So this is where I am at, I do not have a "check_rooted.bak" file in my bin directory, so I haven't quite finished rooting the KF.
EDIT again
OK, I suck at this, (obviously), I just needed to remount the system file and perform the command again and it worked... I now have check_rooted.bak
So I have completed all of the commands successfully, I have Superuser installed, and can access root in recovery mode no problem... but when I select root explorer in ES File Explorer, it tells me that it cannot be used on this device. What should I do next?

I think you may be missing steps, as you haven't mentioned copying the su binary.
Have a read here: http://forum.xda-developers.com/showthread.php?t=1568340 (just skip all the fastboot mode parts, head straight to copying the su binary)

You were absolutely right... I was using that thread as a guide, and mounted the steps and pushed the file, but never confirmed that it moved over... did it again, and done! Thanks!

MD5 doesnt match while doing manually.
I tried doing manually by downloading the files and renaming and pasting in the directory "Recovery" , but while rooting it says md5 doesnt match.
Please help me how to get rid of the problem. How to make md5 match.
I have tried all the ways to do rooting and iam very unsuccessfull.

Prithvirajbilla said:
I tried doing manually by downloading the files and renaming and pasting in the directory "Recovery" , but while rooting it says md5 doesnt match.
Please help me how to get rid of the problem. How to make md5 match.
I have tried all the ways to do rooting and iam very unsuccessfull.
Click to expand...
Click to collapse
What are you getting a md5 mismatch on?
---------- Post added at 05:40 AM ---------- Previous post was at 05:37 AM ----------
Thepooch said:
What are you getting a md5 mismatch on?
Click to expand...
Click to collapse
If your intention is to just flash a rom you dont have to root just simply use kfu to send fff and twrp if you wish Sometime I can assist you
---------- Post added at 06:04 AM ---------- Previous post was at 05:42 AM ----------
I could send you my copy of kfu with the files predownloaded and you can try that

md5 doesnt match while installing twrp.
Thepooch said:
What are you getting a md5 mismatch on?
---------- Post added at 05:40 AM ---------- Previous post was at 05:37 AM ----------
If your intention is to just flash a rom you dont have to root just simply use kfu to send fff and twrp if you wish Sometime I can assist you
---------- Post added at 06:04 AM ---------- Previous post was at 05:42 AM ----------
I could send you my copy of kfu with the files predownloaded and you can try that
Click to expand...
Click to collapse
I have tried manually ,but it says md5 doesnt match while installing twrp . My aim is to flash a rom on kindle fire. I have tried on friends computer on which he did his kindle fire rooting, It has already downloaded the files in recovery folder . on his computer i got "adb server is out of date , killing adb server " this statement several times and finally it said md5 doesnt match while insatlling twrp.
Please help me how to root.
thanks in advance

Prithvirajbilla said:
I have tried manually ,but it says md5 doesnt match while installing twrp . My aim is to flash a rom on kindle fire. I have tried on friends computer on which he did his kindle fire rooting, It has already downloaded the files in recovery folder . on his computer i got "adb server is out of date , killing adb server " this statement several times and finally it said md5 doesnt match while insatlling twrp.
Please help me how to root.
thanks in advance
Click to expand...
Click to collapse
I could assist you

what to do ?
Thepooch said:
I could assist you
Click to expand...
Click to collapse
Please say me how to root , steps which OS i have to use. I have both ubuntu and Windows. Please say me the steps to do it. if u can please send me the files

Hi,
Anybody can help? I am facing the same situation.
-tried reinstalling drivers, and redownloading kfu 0.9.6, restarting the com too
- somehow the md5 doesn't match all the time.
-attached in the picture is the error message
Thank you

After using ur file and putting into the 'recovery' folder, there is still the same error, below is the full log. I tried redownloading it and trying again, still can't. The file size is at 5568kb.

OK delete the one I gave you out of the recovery folder and try again twrp was whacked out for awhile today now it should download the new version if you delete it out of the folder

done! thanks

[Guide] Disabling Auto-Updates on Fire Phone

DISCLAIMER: THIS METHOD WORKS ON THE FIRE TV, AND MAY NOT WORK FOR THE FIRE PHONE. IT HAS WORKED FOR ME, BUT I TAKE NO RESPONSIBILITY FOR ANY DAMAGE CAUSED TO ANY DEVICES. USE AT YOUR OWN RISK.
I searched around and couldn't find a way to do this on my own. Some threads suggest deleting system files to get this to work, but I found you can disable OTA updates on the Fire Phone the same way you can with the Fire TV.
You need to have root access to the phone, which requires both:
A) Downgrading your phone to 3.5.0, and installing the ADB. Which you can read about in the first part of B1ackByte's guide HERE.
B) Using towelroot to get root access HERE (Click the symbol, download the apk and run it.)
After you have the ADB and drivers installed on your system, and your phone has been downgraded to 3.5.0, you MUST choose
"Wipe Data and Factory Reset" in the recovery menu before rebooting your phone. If you do not, you can get a couple glitches and hangs... nothing major, but you'll still have to boot into recovery to do the wipe and finish the process.
After you're downgraded, rebooted, and rooted... Install the latest version of SuperSu from HERE then REBOOT AGAIN!!! If you don't, SuperSu might not take over properly.
Open CMD or Command prompt as an administrator, and navigate to where you have the adb.exe, then issue these commands:
adb start-server
adb shell
su
Click to expand...
Click to collapse
Your phone will then ask you to grand permissions to the adb console, click "grant" or "accept" (Depending on the version of SuperSU you have.)
Then Type:
pm disable com.amazon.dcp
Click to expand...
Click to collapse
You should see an output message that says "Package com.amazon.dcp new state: disabled"
And Voila! OTA updates are turned off.
EDIT: I've also read a couple guides about how people have used the Fire HD FirstAide package to install google apps and maintain root, but that process didn't work for me. The Fire Phone (or mine, at least) doesn't come with busybox, and the FirstAide script relies on busybox. You can manually install busybox into the system files of the Fire Phone and give it system permissions, but that is outside the scope of this tutorial.
Also, even after manually installing busybox and granting root permissions to the adb shell running the commands, the script still fails to copy some files because the filesystem isn't EXACTLY the same as the Fire HD. (I may be wrong on this, but I just couldn't get the process to work due to some missing folders on my end.)

I tried this and it worked for me. Thanks!

is that possbile to downgrade 4.6.6 to 3.5 reply quick please guys

Reverting the Fire Phone back to stock

If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550

th3rmite said:
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
When I boot to recovery and adb sideload there is no adb device when I type adb devices.
Windows 7 64bit.
Cool I found easy solution...I downloaded this program and runned it when phone was in sideload mode, it installed drivers and voila
http://adbdriver.com/downloads/

everything is still installed and camera still doesnt work
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed

ianedward said:
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
Click to expand...
Click to collapse
Since it is official update it won't perform factory reset...

ianedward said:
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
Click to expand...
Click to collapse
you need to wipe the device after flashing the new rom

C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-35.4.6.6_u
er_466000820.bin
loading: 'update-kindle-35.4.6.6_user_466000820.bin'
* cannot read 'update-kindle-35.4.6.6_user_466000820.bin' *
---------- Post added at 09:15 AM ---------- Previous post was at 08:25 AM ----------
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-juniper-35.
4.6.3_user_463001420.bin
loading: 'update-kindle-juniper-35.4.6.3_user_463001420.bin'
* cannot read 'update-kindle-juniper-35.4.6.3_user_463001420.bin' *
C:\Program Files\Minimal ADB and Fastboot>adb sideload update.bin
loading: 'update.bin'
* cannot read 'update.bin' *
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
i download many files but all BIN files fails to sideload

aamszia said:
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-35.4.6.6_u
er_466000820.bin
loading: 'update-kindle-35.4.6.6_user_466000820.bin'
* cannot read 'update-kindle-35.4.6.6_user_466000820.bin' *
Click to expand...
Click to collapse
You should be able to manually update your phone to Fire OS 4.6.6 by following the steps at this link: Update Your Fire Phone Software.

jack9955 said:
You should be able to manually update your phone to Fire OS 4.6.6 by following the steps at this link: Update Your Fire Phone Software.
Click to expand...
Click to collapse
Fire phone stucked on recovery .. only option i have is by sideload . .. and sideload is not working for me ..
i have downloaded 5 firmwares .. but same error in all files ..
.....

aamszia said:
Fire phone stucked on recovery [...]
Click to expand...
Click to collapse
Please stick to asking questions for one problem in one thread at a time, thank you.
I replied in the other thread (bricked fire phone / sideloading by ADB), since it's more related to your questions.

aamszia said:
Fire phone stucked on recovery .. only option i have is by sideload . .. and sideload is not working for me ..
i have downloaded 5 firmwares .. but same error in all files ..
.....
Click to expand...
Click to collapse
If you mean you are stuck in Safestrap recovery, then follow @ggow post to flash Fire OS. The links you will need for the flashable images are here and here.
If you are not stuck in Safestrap recovery and your phone is still under warranty, you may want to contact Amazon for a replacement phone.

jack9955 said:
If you mean you are stuck in Safestrap recovery, then follow @ggow post to flash Fire OS. The links you will need for the flashable images are here and here.
If you are not stuck in Safestrap recovery and your phone is still under warranty, you may want to contact Amazon for a replacement phone.
Click to expand...
Click to collapse
i am stuck on Stock Recovery ...

Is there anyway to boot in to safestrap recovery and not the stock recovery. I have a back up on safestrap boot stuck on amazon screen and I can omly get im to stock recovery.

th3rmite said:
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
Please help me when i type adb sideload "filname.bin" , It gives me an error cannot read "filname.bin" ??
Please tell me how could i fix this ??

Hussain_97 said:
Please help me when i type adb sideload "filname.bin" , It gives me an error cannot read "filname.bin" ??
Please tell me how could i fix this ??
Click to expand...
Click to collapse
Did you have any luck reviving your phone?

why not just factory reset using the official recovery? this seems like an awful lot of extra work :|

i am stuck on Stock Recovery elso with my phone .
i test sideload tool give me his msg on CMD windows after type add sideload commend
C:\tools>adb sideload c:/tools/rom.bin
opening 'c:/tools/rom.bin'...
connecting...
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

@amr1406
try to find Android SDK Platform-tools v 25.0.3

Adb sideload fail?

i tried to sideload update.bin yesterday but in cmd it said "can't read update.bin". I checked adb drivers by typing "adb devices" and i worked. There's no errors during download process. I tried to put .bin file from download, desktop and C:/ but still not success. Can you help me?

The easiest (laziest ^^) way is to put the .bin file in the ADB folder. This way, you don't have to type the full path.

Bingo Bronson said:
The easiest (laziest ^^) way is to put the .bin file in the ADB folder. This way, you don't have to type the full path.
Click to expand...
Click to collapse
Thanks much! Now i want to ask you a question: when i sideloaded successfully i went to stock fire os. i installed gg play and could download app too. Now i can't. i go to gg play app it show only a loading circle and never complete. i tried to wipe data by titinium backup and reinstall 4 apk but still stuck at that circle. Can you help me?

Sorry, I haven't used Google Play & services in a long time on Fire OS, so my infos on that are not up to date.
I will test the microG framework on Fire OS soon and report back, but this is a method for advanced users, since it requires more preparation & some maintenance from time to time.
You already know the thread for Google Play on the Fire Phone, it contains the most recent information but there still can be a dozen reasons why it doesn't work on your device right now, too many possibilities.