Develop Bugs

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!

Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.

Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz

I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?

Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.

confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus

error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz

djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm

mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App

edit: got it thanks

Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium

whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?

bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?

oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks

so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it

|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,

Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat

when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be

When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

Flashing Gio from ODIN with .tar.md5

I dowloaded my stock firmware from samfirmware.com and now i would like to flash it. It is a single tar.md5 package. I would like to known how to flash it. I searched, but it was not much help to me. Do i use the single package option in ODIN?
- i have never used odin, but i have flashed alot of roms so im not completely stupid when it comes to this stuff.

Yes, one package

Once you have Odin
To do so
The file "GIO_v0.1.ops"
You will find in the package of Odin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You put the file you downloaded md5
How do you see "PASS!" disconnect and if appears
"Close serial port and wait until rebooting" a disconnect, and wait until the phone turns on, of course, disconnect the cable.
It says Samsung on the phone remove the battery and enter the Recovery Menu
select "wipe"
select reboot
READY
I already have the new rom

Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?

AlwaysDroid said:
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
Click to expand...
Click to collapse
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium

Cant find?
voetbalremco said:
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Im trying to flash a file called S5660MUGKG3_S5660MBMCKG3_BMC. When ever i try to one package i cant seem to find it? Can anyone help me with this?

Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
How do I unzip it? Can I use winrar and extract?

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
Yay I got it!
Thanks for your help!
Is it fine if it says 1 (COM10) ? and also its keeps on showing the boot animations over over... wont go further and on odin it says pass. should i keep on waiting or is somthing wrong? is it bricked?

1 (COM10) is simply to indicate the serial port number assigned to your phone by Windows and the Samsung USB driver in Odin.
Your phone is boot looping, some might consider this a soft brick. My best guess is that you previously installed a ROM that formatted your /data and /cache partitions from the stock RFS format to ext4 instead. The stock 5660M ROM doesn't support ext4.
Reboot in the stock recovery, either with "adb reboot recovery" or by using the home and power keys simultaneously.
From there, wipe user data and cache, or something similar I don't recall the exact wording, but I do remember they were two separate commands.
Reboot, should work now. Use ddms (part of the Android SDK) to see what's going on under the hood if you feel like it.
I take it computers are a relatively new thing for you to ask how to unzip files. My best advice: make very regular backups and read instructions carefully. Losing data is not cool. Losing someone else's data is worse. (I'm guessing you're on the family computer here...)

[Q] Wiped OS need help to sideload zip file

I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.

I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version

You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.

sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?

I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.

sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.

sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse

merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.

Uninstalled Rom, don't have zip on sd. Help!

Ok, so I thought I still had the zip on my device after not being able to recall my gesture pattern lock. I could still access the device by logging into through my google account however I couldn't change the lock itself without doing a system wipe.(To my knowledge)
So now I'm stuck in TWRP with no rom to flash to my device, when I connect my nexus 7 to a notebook (win7) I do not get the MTP connection to drag and drop a rom over.
Everything I seemed to try in the ToolKit as well has been unsuccessful, can someone give me a step by step on how to push,flash,install PAC back onto my device and remove this headache of mine.
Thanks in advance!

DeeSlivers said:
Ok, so I thought I still had the zip on my device after not being able to recall my gesture pattern lock. I could still access the device by logging into through my google account however I couldn't change the lock itself without doing a system wipe.(To my knowledge)
So now I'm stuck in TWRP with no rom to flash to my device, when I connect my nexus 7 to a notebook (win7) I do not get the MTP connection to drag and drop a rom over.
Everything I seemed to try in the ToolKit as well has been unsuccessful, can someone give me a step by step on how to push,flash,install PAC back onto my device and remove this headache of mine.
Thanks in advance!
Click to expand...
Click to collapse
For future reference, I think you can send and email to your google account to reset your gesture lock.
If you want to flash a rom onto your device just use the toolkit. Should find what you need in Advanced utilities.

Where is the advanced utilities in the tool kit? you must have the wording wrong.
Wish I knew about the reset prior to the this mess >.<

DeeSlivers said:
Where is the advanced utilities in the tool kit? you must have the wording wrong.
Wish I knew about the reset prior to the this mess >.<
Click to expand...
Click to collapse
He is referring to this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the 4 items you will need to sideload P.A.C if you don't have them already.
http://goo.gl/QBnwND
http://goo.gl/jG0M9a
http://goo.gl/DEUHBC
http://goo.gl/WvFjl6

TWRP works with adb. Plug it in to your computer with the adb tools installed, run adb devices, you should see it listed. Change to the folder with your ROM zip, do adb push <rom>.zip /sdcard and it'll be on your device. No fuss, no muss.
Sent from my Nexus 7 using Tapatalk 4

This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager.

Username invalid said:
This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager.
Click to expand...
Click to collapse
Thanks I'm wiping the drivers and attempting your method! I'll be back with questions if I have any.:cyclops:

There we go, I had to use a different link in order to download the Minimal ADB And Fastboot Kit.
From there I was able to push the rom onto the device no problem what so ever thanks everyone!

DeeSlivers said:
For some reason the link you provided for ADB and Fastboot doesn't work. My device does show up as a ADB device in the device manager. However I'm still unsure how exactly I push or flash a rom from the notebook to the device itself.
Also his verison of ToolKit isn't what I been using, I have the terminal like green font'd 2013 toolkit by skipsoft is what I have outdated and no longer used or?
Click to expand...
Click to collapse
Yust use this command:
Code:
adb push (your rom file name) /mnt/sdcard/
Then go to flash menu and you will se your rom in your internal sd card

Ok, so I managed to re-flash my rom back on no problems at all. But problem with that is the gesture lock is still active.
Can someone give me a method to remove this from the account?

Try aroma file manager to delete gesture. Key
Sent from my GT-P3100 using xda app-developers app

sukkukikku said:
Try aroma file manager to delete gesture. Key
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Can you further explain this method?

Your device is rooted or not
Sent from my GT-P3100 using xda app-developers app

sukkukikku said:
Your device is rooted or not
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
Have you read the thread what so ever..?
Yes the device is rooted, it's running PAC Rom newest Nightly.
The issue is, everytime I load the device I get the gesture lock which I don't have the correct information to. I want to reset the password back to a pattern or pin. Cause as of this point it requires me to login to my google account every time I fail to put the gesture in, meaning unless I have access to the wifi zone my device can't be logged into.

You need to install cwm recovery mode. You need to download aromafm1.80.zip file from net. It will be 1.4 mb. Place the file in external SD card. Go into recovery mode. Mount all partitions in advanced section. Then go to the file in SD card in recovery mode and flash the zip file there. Aroma file manager will open. Then go to data/system/gesture.key and delete that key. And reboot device. Pattern will appear but if you draw any pattern., the device will be unlocked
Sent from my GT-P3100 using xda app-developers app

i kinda get ya ,least ur not stuck in recovery same day buyin the bloody thing. my lil mistake of puttin folder instead of zip into internal storage now has me pullin hair out. why cant u just plug bk into pc and it opens the internal folder up.

sukkukikku said:
You need to install cwm recovery mode. You need to download aromafm1.80.zip file from net. It will be 1.4 mb. Place the file in external SD card. Go into recovery mode. Mount all partitions in advanced section. Then go to the file in SD card in recovery mode and flash the zip file there. Aroma file manager will open. Then go to data/system/gesture.key and delete that key. And reboot device. Pattern will appear but if you draw any pattern., the device will be unlocked
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
You're telling me a several step process to "work around" the issue, instead of actually fixing it which isn't what I been asking.

It will remove the pattern lock
Sent from my GT-P3100 using xda app-developers app

Reverting back to Fire OS from CM11

Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks

doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.

I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".

You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.

Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.

Can you add the link for the thread you used to revert back from CM11 to FireOS?

paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2

Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.

iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...

Is the update.bin file in a different directory?

Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks

iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:

Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!

Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?