Develop Bugs

[Request]$ -- Modify zergRush to Not Need Build.prop File

I have a request with a small donation as a reward. I'm not rich, but I can reward with some beer money.
I have managed to somehow delete my build.prop file while rooted and then managed to un-root my device. Naturally, I rebooted.
My request is for anyone with a bit of extra time to modify zergRush so that it does not look to a build.prop file to verify the android version.
If there are any other ideas on how to root a bricked Fire without a build.prop file, be my guest.
My hope is that once I am able to re-root my device, I will be able to mount /system/ as writeable and then be able to push in a build.prop file. However, obviously, until that happens I cannot put in a build.prop file.
If you have any questions I pretty much let it all out on the "How to unblock your kindle" thread.
If no one is able to do this I would understand. This is obviously beyond my technical expertise but I do appreciate any efforts or even suggestions. Even if there's no attempts made here, it is still shocking how much help is given on this forum.
EDIT: I was able to get my hands on a valid system.img and then flashed the system.img to my system partition. Doing so corrected my build.prop and my device became bootable. Thanks for all the help.

Did it update to 6.2 while in the midst of your needing around?

what does your device do?
Does it show under adb devices?

ajq said:
Did it update to 6.2 while in the midst of your needing around?
Click to expand...
Click to collapse
I updated to 6.2 on Tuesday. I have followed the directions on the "UNBRICK your kindle" thread. I have done that successfully. However, because my build.prop is missing, I can no longer re-root using zergRush. I believe that fastboot as directed in that thread restores the kindle to factory settings. I'm not quite sure if factory settings is 6.2 or if it goes all the way back to 6.0.

death2all110 said:
what does your device do?
Does it show under adb devices?
Click to expand...
Click to collapse
This is the post I created in the "How to unbrick your kindle" thread. It should answer most questions. I can use adb shell on the device but I cannot mount anything and SU responds "permission denied".
----from the other thread----
I am in a similar situation and am trying to work through it. I thought I rooted my device but when I restarted it, it didn't fully load. I've successfully done all of the steps listed in the OP but am still suck in a black screen (it's lit...but it's black) loop.
I believe I have deleted my build.pop file but have a backup listend as build.prop.bak. However, the device is trying to load and is failing. I need to rename my build.prop.bak as the primary build.prop. I have tried to access SU through ADB but am getting "permission denied" almost as if my device wasn't rooted.
I have tried to mount system as RW but I am also getting permission denied.
Any advice. Here is my /system/
:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>cd \KindleFireRoot\files
C:\KindleFireRoot\files>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ cd /system/
cd /system/
$ ls -l
ls -l
drwxr-xr-x root root 1970-01-01 00:00 lost+found
drwxr-xr-x root root 2011-12-01 19:03 app
drwxr-xr-x root shell 2011-12-01 19:03 bin
drwxr-xr-x root root 2011-11-30 01:16 etc
drwxr-xr-x root root 2011-11-30 01:16 fonts
drwxr-xr-x root root 2011-11-30 01:16 framework
drwxr-xr-x root root 2011-11-30 01:16 lib
drwxr-xr-x root root 2011-11-30 01:16 media
drwxr-xr-x root root 2011-11-30 01:16 tts
drwxr-xr-x root root 2011-11-30 01:16 usr
drwxr-xr-x root shell 2011-11-30 01:16 vendor
drwxr-xr-x root shell 2011-12-01 19:03 xbin
-rw-r--r-- root root 2143 2008-08-01 12:00 build.prop.bak
$
EDIT: I have tried to re-root through the method provided as well as superoneclick root, but both have failed because no android system is being recognized. This may have to do with the lack of a proper build.prop on my device.
EDIT2: I figure the above might not be enough information so I will now post what I have done so far to get it bricked, and what I have already tried.
1. I tried the rooting method on rootkindlefire.com and it seemed successful. I then was able to set /system/ as RW via root explorer. I copied a modified build.prop file that is available in the android development forums. However, unfortunately, I believe I may have edited the name of this file or done something wrong in handling it accidentally. Regardless, I pasted this file in the /system/ folder and renamed my original build.prop file to build.prop.bak. I then restarted my kindle fire. Now, it shows the kindle fire screen for a second and then goes black entirely. It is still on (the screen is lit), but the screen is black. It then remains like this until I do a hard reset and then it repeats this process.
2. I have tried to access SU but have been unable to do so. I have been unable to mount system as RW using the instruction a page back. In both situations I get the "permission denied" response from the command line.
3. Everytime I try to root using the method provided in the OP, I get a message saying that it can't find android 2.2 or 2.3
4. I am unable to root again using super click for the same reason.
5. I have otherwise been able to follow all of the steps in the OP successfully, but to no avail. My screen goes black after it shows the kindle fire screen for a couple seconds.
6. Any suggestions would be very very helpful. From my amateur amount of knowledge, it seems to me that I don't have a build.prop in my /system/ but am unable to rename or access my build.prop.bak so that I can set it as the regular bootable build.prop. This is because, even though I thought I had it rooted, I am unable to set the /system/ directory as writable.
7. ANY SUGGESTIONS OR HELP WOULD BE GREAT!

Just as a disclaimer: I acknowledge I'm a moron for not verifying everything when I pushed in a build.prop file into my /system/ folder and restarted. No need to call me names

For those who know a bit more than me...
Would pushing the 6.2 update (or any of the downloadable firmware) to the kindleupdates folder in the sdcard and then rebooting fix my problem? I remember reading that the updates re-writes the build.prop which would fix my situation.
Of course, do you need root permissions to be able to write to the sdcard? I only ask this because I can not get the sdcard to actually show up on my desktop. I would need to push it via terminal or adb shell.
Anyone know if this would work?

I am beginning to realize that I may actually still have root, but since I can't boot up the phone, I can't fill out the superuser access dialog that usually comes up when a program tries to access superuser. I had root before I caused the build.prop problems, but figured that I had somehow lost it when I tried to access SU from ADB. Anyone know of a way to bypass this access dialog?

I checked the root status with OneClickRoot after OTA reported my KF was still rooted (just to be sure) and then re-installed Superuser and pushed the necessary Android APKs back to /system/app and it was working again.

damianarnold said:
I checked the root status with OneClickRoot after OTA reported my KF was still rooted (just to be sure) and then re-installed Superuser and pushed the necessary Android APKs back to /system/app and it was working again.
Click to expand...
Click to collapse
How did you re-install Superuser if you're not able to fully boot up the KF? To be clear, when I try to root with superoneclick it says i'm rooted (and if i try and continue it fails...) but whenever I type in adb shell and then su I get "permission denied."

ejrubin said:
How did you re-install Superuser if you're not able to fully boot up the KF? To be clear, when I try to root with superoneclick it says i'm rooted (and if i try and continue it fails...) but whenever I type in adb shell and then su I get "permission denied."
Click to expand...
Click to collapse
My Fire was fully booted up. Did you remove and reinstall Superuser?

damianarnold said:
My Fire was fully booted up. Did you remove and reinstall Superuser?
Click to expand...
Click to collapse
Don't think our KF were in the same state. I don't have a build.prop to boot my KF into so I can't manage superuser at all (I do, however, have a totally useless build.prop.bak that is sitting there in the directory. ) I have the superuser.apk in there so it seems as though I'm rooted but I still can't get into SU via adb.

Can't get Write access to /System or /SDCard
ejrubin said:
Don't think our KF were in the same state. I don't have a build.prop to boot my KF into so I can't manage superuser at all (I do, however, have a totally useless build.prop.bak that is sitting there in the directory. ) I have the superuser.apk in there so it seems as though I'm rooted but I still can't get into SU via adb.
Click to expand...
Click to collapse
Still having the exact same problem! Was able to get the build.prob.bak pulled from /system but can't rename it and push it back to hopefully get this working again.
I am starting to think I may have to send this KF back soon if I don't get it working again.
Any help anyone can provide would be great.

I'm thinking since we are able to get into fastboot, do any developers know if it is possible to push in a new system.img via fastboot? This would solve our build.prop problems no? Any developers know if this is possible?

I would like to compile zergRush myself, but I don't know how to compile Android binary.
It seems require linux to do so.

Can you adb push to the sdcard?
Sent from my DROID Pro using XDA App

JackpotClavin said:
Can you adb push to the sdcard?
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
No , I think the sdcard is not yet mount. Tried cd sdcard and it's not possible.
Is it possible to mount it without root? Cause when we try to mount system folder it's permission denied.
And I'm afraid the system won't run the official update even the patch is inside the sdcard folder.
I think ejrubin's idea on how to fix our bricked kindle fire is completely right , we just need either one of the following :
1. A zergRush binary won't check the build.prop to let us run root and mount the system folder
2. Since we can get into fastboot, I think we need a correct update.zip or system.img to fix it. Any idea to build it from kindle's official update?

Well try "mount sdcard" in the shell. If you can push the update, you can idme bootmode into 0x5001 and it'll take the update in recovery mode
If that doesn't work I'll give a custom zerg a shot
Edit: I got it. If you wanna flash my clockwork build in fastboot and set the fastboot to boot into recovery, you can access your /system through recovery, I do it all the time
It'll be a fastboot flash recovery <the name of the recovery.img I'll post later when I get home>
From there you will have to:
Adb shell
Mount system
Mv /system/build.bak /system/build.prop
Sent from my DROID Pro using XDA App

JackpotClavin said:
Well try "mount sdcard" in the shell. If you can push the update, you can idme bootmode into 0x5001 and it'll take the update in recovery mode
If that doesn't work I'll give a custom zerg a shot
Edit: I got it. If you wanna flash my clockwork build in fastboot and set the fastboot to boot into recovery, you can access your /system through recovery, I do it all the time
It'll be a fastboot flash recovery <the name of the recovery.img I'll post later when I get home>
From there you will have to:
Adb shell
Mount system
Mv /system/build.bak /system/build.prop
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
If i just type "mount sdcard" it cannot recognize the command.
if try to mount it with -t and mount it to other folder, it just say permission denied.
Of course I wanna flash your clockwork build!!
Would you mind to guide us with all the step when you're ready? Because I'm quite new to root android machine.
Really thanks for your help!!!!!!!!!!!!!!!!

Yeah **** sorry guys can this wait till tomorrow? Sorry I said tonight, I got side tracked tonight
Sent from my DROID Pro using XDA App

[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!

[Q] Downgrade Issue.

Hello All,
Purchased an Amazon Fire TV from Amazon, it shipped in one day and I have been toying with it for the last few hours. Rooting was easy, as was installing SU, Busybox, Stickmount etc.. However, I am not to the point to where I want to install a custom recovery so I can update to the latest firmware without loosing root. The instructions say I need to downgrade to an earlier firmware in order to do this. My problem is that every time I reboot into recovery it says "Update was not successful" and It boots back to the same version that I started with.
The version I have now is 5.1.1.1.0 fully rooted w/ Busybox. I don't know exactly what I am doing wrong. I have both pushed the update.zip to the AFTV, and I have also put it on a thumb drive. I have tried earlier versions then the one recommended in the guide that I was following. All of this to no avail.
Please help.
Thank you.

Anybody? I was up till little after 3 AM trying to figure this out. Factory reset, re-rooted, nothing seems to work. Has anyone else had this issue?

I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.

roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Just tried the mirror. That ended in the same result. I am going to try re-installing Busybox again to see if that has any change.

roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?

brotherandyslb said:
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?
Click to expand...
Click to collapse
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.

nyder said:
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.
Click to expand...
Click to collapse
Ok,
Lets start from the top:
Factory Reset
Watch Video
Sign into Amazon Prime
So no to parental controls
Go to developer options and turn it to on so I can use ADB
Connect with ADB
adb install towelroot
go into towelroot and root
adb install supersu
go into supersu and let it update
adb install busybox
go into busybox and install it and let it symlink
adb the command to turn off updates
Then I follow the guide over at aftvnews.com to downgrade
Download the firmware version you wish to install from the software page
Rename the downloaded file to update.zip
Connect to your Fire TV using ADB
(If you don’t know how, follow up to Step 4 Part 2 in our Windows or Mac guide)
Run the command: adb shell
Run the command: su
(If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
Run the command: chmod 777 /cache
Run the command: chmod 777 /cache/recovery
Note: If
you see a message saying “No such file or directory”, then run the following two commands:
mkdir /cache/recovery
chmod 777 /cache/recovery
Run the command: cd /cache/recovery
Run the command: echo --update_package=/cache/update.zip > command
Run the command: exit
Run the command (yes, again): exit
Run the command: adb push update.zip /cache
(This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache)
Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery
At this point your fire TV should restart and begin installing whichever firmware version you selected.
Click to expand...
Click to collapse
At this point the AFTV restarts and proceeds to install the new firmware about 1/4 way thru it gives the error message and then restarts.

[Guide] Disabling Auto-Updates on Fire Phone

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

I tried this and it worked for me. Thanks!

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

[Q] Unable to perform any su commands in adb shell

FireTV, Fire OS 5.0.5 (537174420) (developer preview)
I have tried every guide, I can push apps and install via adb, and I can access shell via adb, but I can't perform any su commands in the shell, it says su not found, or no permission etc for other commands, so I can't manually upgrade/downgrade or do anything as everything has one of these commands in there at some point, anyone know what I need to do to unlock this? I've currently just reset it to factory defaults for now. Also I've tried kingroot and tr and they both won't root/unlock the device.
Thanks in advance,
para

paradoxiumwind said:
FireTV, Fire OS 5.0.5 (537174420) (developer preview)
I have tried every guide, I can push apps and install via adb, and I can access shell via adb, but I can't perform any su commands in the shell, it says su not found, or no permission etc for other commands, so I can't manually upgrade/downgrade or do anything as everything has one of these commands in there at some point, anyone know what I need to do to unlock this? I've currently just reset it to factory defaults for now. Also I've tried kingroot and tr and they both won't root/unlock the device.
Thanks in advance,
para
Click to expand...
Click to collapse
I just ran into the same issue on both of my boxes the last couple days. Im not sure why I cant get root access either but the good thing is the disabling of the OTA updates sticks after you command it, regardless if you lose root. What I did was just re flash the pre rooted ROM. Kind of a pain but it only takes a couple mintues. After I did that, root access was back!