Reverting the Fire Phone back to stock - Amazon Fire Phone

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

Related

[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] Very Frustrated NOOOOOOOOOB

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

[Q] Kindle Fire 8.4.9 Root?

Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.
akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.
akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.
akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.
Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!

Bricked Fire Phone after unroot.

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

[GUIDE] Revert, rollback, or downgrade Nvidia Shield TV Experience Upgrade +DATA LOSS

NOTICE: Several users have reported issues downgrading from v7.2.x, so it might require some additional experimentation to downgrade from that version.
-
Missing your screenshot or twitch streaming functionality? Hate the new launcher layout w/ its tiny one row of icons and its numerous rows of psychologically-aggressive suggestion imposition?
Well, now you can stop cursing at Nvidia, because they provided a way (albiet, a highly technical and mostly-undocumented way), to load any version of their OS that you choose.
I've seen others wanting to downgrade (including myself), so I've collected the relevant steps which I used to successfully revert to an earlier version. This guide assumes a bit of technical working knowledge, so I apologize if you are one of the 'normal' people that Nvidia has bulldozed over...
All the usual "don't blame me for bricked devices" caveats apply.... please be careful, know what each step does! research each step!
Best of luck...
0 - prereqs
make sure your PC & nvidia shield are both plugged into a UPS, b/c a power failure during a flashing operation is not very pleasant.
make sure you have (or do get) the adb & fastboot binaries ("commands") for your computer
make sure that you get all your userdata off the device, because it will be erased by this process
1 - using a web browser
register for an nvidia developer account (which you will have an opportunity to do if you attempt the next step)
download the 6.3 'developer os' rom for your particular model
https: //developer.nvidia.com/shield-developer-os-images (sorry, noob filter won't allow the real/clickable url)​
NB: The 6.3 developer rom for the 2017 console is missing the userdata.img, there are currently no reports (on this thread) if a different userimage (pre-6.3 or for the 2015 version) works on the 2017 console (testers welcome!).
NB: if the cost of being identified as a developer offends you (i.e. yielding a name, company, email, etc), then you can probably dig up a link to the roms in the comments or elsewhere on the xda forums.
2 - on the device
enable developer mode by clicking the 'build' entry in settings->info
enable usb debugging in settings->developer-options
plug it into your computer using the usb port furthest from the hdmi port
3 - in a terminal
unzip the downloaded rom & cd into the resulting directory
edit the 'flash-all.sh' script to add the following line just before the final reboot:
fastboot flash userdata userdata.img​
#(this will add even more wall-time to the flashing process, but will clobber the already-erased newer 7.0 user partition data with the old)
adb reboot bootloader
fastboot oem unlock && ./flash-all.sh
NB: Now confirm your willingness to lose all your data. On the 2015 'pro' version of the console, this is accomplished by pressing (or holding) the nvidia logo 'button'... AND WILL TAKE NEARLY TWO HOURS. Others use the x/y/a/b buttons on the game controller connected to the usb port nearest to the hdmi port.
[... time passes ...]
NB: the 7.0 to 6.3 was a clean backstep for me, but if you are going between other versions, I can see that this script might stall in the middle if the device does not come back up with adb services available... in which case you will need to enter fastboot manually using a hardware method.
4 - Break TegraOTA
You have now flushed the correct version onto your device, but we can't complete the setup process... if you were to try, the final step would immediately and automatically start downloading & applying the latest (7.0) experience update! Therefore, we must neuter the updater itself.
Still in the terminal:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
5 - you should now be able to setup and pain-stakingly reconfigure your nvidia shield to the way it was before you blindly trusted an OEM update without doing extensive research beforehand.
PS: if you fear that netflix or amazon-video will at some point stop working because of this process, you might wish to "fastboot oem lock" the device (knowing that an unlock will erase your user-data, but having the developer rom means you can always get root access via adb).
I hope you find this useful.
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
rossbeck said:
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
Plex is NOT broken in 7.0 i use it everyday.
Builtfordtough1 said:
Plex is NOT broken in 7.0 i use it everyday.
Click to expand...
Click to collapse
I use it every day too... and since Plex v6.13, files fail to play after 3 seconds unless you run them a 2nd time.
It's a known issue that everyone is having due an acknowledged bug in exoplayer2 with certain containers like mkv. Since 7.0/oreo has plex v6.14 baked in as a system app, it's impossible to downgrade to v6.12 to get rid of the issue until Plex fixes it... and they've known about it for 2 months now. Since quantity has been their focus over quality lately, I'm not holding my breath for a fix.
The solution is to downgrade to 6.3, manually install plex v6.12, and turn off app updates.... so that's my plan.
rossbeck said:
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Osndok said:
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Click to expand...
Click to collapse
Ahhh, good call. I'll have him try a usb keyboard.
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
crazyscow said:
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
Click to expand...
Click to collapse
What command did the script stop at? and how 'stuck' are you (i.e. can you get to fastboot?).
I imagine that if you started with the wrong rom, it would likely fail to boot.
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
crazyscow said:
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
Click to expand...
Click to collapse
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
rossbeck said:
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
Click to expand...
Click to collapse
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Osndok said:
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Click to expand...
Click to collapse
So you did what to get userdata.img? Created it in TWRP or something? It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Thanks man
rossbeck said:
you did what to get userdata.img? ... It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
userdata.img is inside the ZIP from the nvidia developer website, as can be seen here:
Code:
$ jar tf nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted.zip | grep user
nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted/userdata.img
rossbeck said:
[the userdata.img] basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
No... not really. The userdata.img from the developer pack both (1) matches the 6.3 version (doesn't have any of the newer, potentially incompatible entries), and (2) has developer-mode & adb enabled by default.
So in addition to it probably just working better, flashing the userdata will let you get adb access, and thus break the OTA, and thus complete the setup w/o the update.
I thought it would boot up, but im still stuck on the android loading screen!
Ill try to reflash the rom again tonight.
update:
I got it to work now, without update having to update to 7.0.2
Code:
adb reboot bootloader
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot
//waiting for nvidia logo and the Windows PC to make the connection noise
//otherwise you can check by typing
adb devices
// if it shows something then continue
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot reboot
once it booted it up, i went thru the procedure of setting it up with my network and google account, then the window pop-up "downloading version 7.0.2" then i followed the guide in the first post
Code:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
after that it booted up into android 7 with not OTA update notification.
thank you!
hello, thanks for the contribution, but when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
lohengrim93 said:
when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
Click to expand...
Click to collapse
As I said in #13, I found the userdata.img inside the archive from nvidia (the 2015 "pro" version to be exact), and I don't know why it is missing from (at least) the 6.3 archive for the 2017 device.
If you are feeling adventurous, you can try downloading either of the 2015 zips, and use its userdata.img... maybe the 16gb one?
I would be eager to know if that works for you, since I'm unsure if the userdata.img can be mixed between different versions of the console...
JUST BE VARY CAREFUL to not mix up your directories and start flashing the wrong blobs & boots... that would be a recipe for a brickin', methinks.
crazyscow said:
I got it to work now, without ... having to update to 7.0.2
... i followed the guide in the first post...
after that it booted up into android 7 [without] OTA update notification.
thank you!
Click to expand...
Click to collapse
I'm quite pleased to hear that it worked for you... (my first success report!).
Adb root
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Insatiablejimmy said:
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Click to expand...
Click to collapse
You forgot to include (or even describe) the actual error message, so I can only guess as to what is wrong.
However, since "adb root" is the linchpin of the developer rom, I would assume that you did not flash a developer rom (or as indicated above concerning the 2017 model) are missing the "userdata.img", which could also cause this behavior.

Categories

Resources