Develop Bugs

[Root][Bootloader] BurritoRoot3 - The whole enchilada. Easy root edition

For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery

Would you support the archos G9 devices

jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?

I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D

I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.

AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now

Quit following me around jcase

Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?

I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.

notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry

jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.

Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!

I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated

My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.

Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889

[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?

did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue

You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?

b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen

wrong - switch back to normal boot and use the utility

cm9 terminal emulator adb issue

I run the following commands
su
adb shell
daemon not running, starting it now on port 5038
daemon started successfully
error: device not found.
any suggestions?

Replug usb cable after adb daemon start on PC or try to get adb when phone in CWM...

scott0 said:
I run the following commands
su
adb shell
daemon not running, starting it now on port 5038
daemon started successfully
error: device not found.
any suggestions?
Click to expand...
Click to collapse
Er... you're running adb _inside_ the phone?

aremcee said:
Er... you're running adb _inside_ the phone?
Click to expand...
Click to collapse
i'm guessing that's the issue.

scott0 said:
i'm guessing that's the issue.
Click to expand...
Click to collapse
ADB is used to connect to android devices. So unless you have another android plugged to your P930, running adb on the phone is pointless

hey thanks.
i guess i am way off track, i want to restore the phone's original recovery image (at some point in the future) and am tired of dealing with adb/windows on my PCs.
i was under the impression this could be done via terminal emulator/adb.

scott0 said:
hey thanks.
i guess i am way off track, i want to restore the phone's original recovery image (at some point in the future) and am tired of dealing with adb/windows on my PCs.
i was under the impression this could be done via terminal emulator/adb.
Click to expand...
Click to collapse
Well... yes, you need adb to connect to the phone, but terminal emulator is already running on the phone.

i see, well, i was hoping to be able to temporarily go back to the stock recovery to do OTA updates and such, it appears it won't be as cut&dry as i was hoping. i assumed that since adb is installed and running on the device via terminal emulator that it could be used to push/pull the stock recovery image onto the phone.

scott0 said:
i see, well, i was hoping to be able to temporarily go back to the stock recovery to do OTA updates and such, it appears it won't be as cut&dry as i was hoping. i assumed that since adb is installed and running on the device via terminal emulator that it could be used to push/pull the stock recovery image onto the phone.
Click to expand...
Click to collapse
You're still not getting it: The only purpose of "adb shell" is to connect you to the phone; terminal emulator is a direct shell already on the phone.

i simply want to flash the original recovery image to the phone without using a PC.
it was my understanding that this is possible via terminal emulator, does anyone know if this is possible and if so, could you point me in the right direction to learn how to do that?
thanks!

scott0 said:
i simply want to flash the original recovery image to the phone without using a PC.
it was my understanding that this is possible via terminal emulator, does anyone know if this is possible and if so, could you point me in the right direction to learn how to do that?
thanks!
Click to expand...
Click to collapse
Just use Terminal emulator in your phone and add manually the following commands to flash original images (put them on sd-card before):
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27

super, thank you Machzelet!
i will give that a whirl this weekend.
here's how i think it will go
images to sd card
restore backed up original rom va rom manager
open up terminal emulator, run the commands above
reboot
update with OTA update
easy breezy?

Why would you even bother updating? The changes in the OTA update will eventually appear in custom ROMs anyway.

do i rly need to provide a reason for wanting to fiddle around with my phone? on a dev board? lolz

[Q] Kindle Fire 2 - Black Screen / No LED /Brick?

HI All,
i have a major problem hoping one of you might be able to give me a little help. I looked through tons of posts and threads however have trouble finding an answer.
I rooted my Kindle fire 2. No Problem here. However I have been experiencing severe problmes in installing a bootloader or a recovery. So after clicking my way trough the internet and trying nearly every method there is i came to this one:
i executed the follwing commands over adb (yes adb was working fine)
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
getting the follwowing output
D:\.android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
/dev/block/mmcblk0p5: write error: No space left on device
129+0 records in
128+0 records out
65536 bytes transferred in 0.038 secs (1724631 bytes/sec)
1|[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.097 secs (2228494 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ reboot
reboot
reboot: Operation not permitted
1|[email protected]:/ $ adb reboot
adb reboot
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ exit
exit
D:\.android>adb reboot
So after rebooting nothing happens. The screen just stays black. I get no LED when i plug the device into the pc or charger. I even tried hardrestes (pressing the button for 20 sec) but nothing. Adb wont work anymore and iam slowly starting to get frustrated. I know I should not have tried a method other than the ones discussed in this forum but after trying so much even goomanager did not work i just though "**** it" lets give it a go. So here I am. Bricked device and not a clue what to do. I also tried the Kindle Fire Unbrick Utility V1.1!
I am running win XP Pro or Mac OS whatever is better to get this sorted out. I am looking forward to hearing from you.
Your desperate Androidschima

Just as a start- do you have a kindle fire TWO?
1. The recovery you flashed isn't correct
2. The kindle fire UNBRICK tool doesn't exist for this device.
3. I'm pretty sure the partition structure you are using is from a different device also.
4. No idea what u-boot.bin is... Doesnt apply to this device
5. Goomanager WONT work.... Our recovery isnt there
Essentially it looks like you flashed the wrong TWRP to the wrong partition.
As of right now.... I dont think it cam be fixed with the tools we have.
The only thing i can suggest is to use a fastboot cable and hope it goes into fastboot mode... But i have a feeling that wont work
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
Just as a start- do you have a kindle fire TWO?
1. The recovery you flashed isn't correct
2. The kindle fire UNBRICK tool doesn't exist for this device.
3. I'm pretty sure the partition structure you are using is from a different device also.
4. No idea what u-boot.bin is... Doesnt apply to this device
Essentially it looks like you flashed the wrong TWRP to the wrong partition.
As of right now.... I dont think it cam be fixed with the tools we have.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Im pretty sure it is a KF2. It was shipped at xmas 2012. I used openrecovery-twrp-2.4.1.0-blaze.img to flash.
Any chance if i get a factory cable?

androidschima said:
Im pretty sure it is a KF2. It was shipped at xmas 2012. I used openrecovery-twrp-2.4.1.0-blaze.img to flash.
Any chance if i get a factory cable?
Click to expand...
Click to collapse
WHERE did you get the recovery? Not from the kf2 forums for sure.
Maybe with a factory cable, but i think you trashed the partitions by using the wrong ones.. Maybe for the kf1? Its possible you may have overwritten fastboot
Edit: IF you get it working again there are TWO and ONLY two methods to put recovery on our device. I recommend the first one.
1. http://forum.xda-developers.com/showthread.php?t=2106463
2. http://forum.xda-developers.com/showthread.php?t=2100963
Edit2: and here is a link to others that did something's similar:
http://forum.xda-developers.com/showthread.php?t=2141914
Edit3: and HERE is the info you need to restore back to stock IF you can get in to fastboot.
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
WHERE did you get the recovery? Not from the kf2 forums for sure.
Maybe with a factory cable, but i think you trashed the partitions by using the wrong ones.. Maybe for the kf1? Its possible you may have overwritten fastboot
Edit: IF you get it working again there are TWO and ONLY two methods to put recovery on our device. I recommend the first one.
1. http://forum.xda-developers.com/showthread.php?t=2106463
2. http://forum.xda-developers.com/showthread.php?t=2100963
Edit2: and here is a link to others that did something's similar:
http://forum.xda-developers.com/showthread.php?t=2141914
Edit3: and HERE is the info you need to restore back to stock IF you can get in to fastboot.
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Thank you ever so much for your fast reply. I will look into the mentioned links! Thanks a million!

:) Re: [Q] Kindle Fire 2 - Black Screen / No LED /Brick?
androidschima said:
Thank you ever so much for your fast reply. I will look into the mentioned links! Thanks a million!
Click to expand...
Click to collapse
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
androidschima said:
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Click to expand...
Click to collapse
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.

soupmagnet said:
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.
Click to expand...
Click to collapse
That's kind of what I thought too... Glad to have an expert confirm it, but sorry dude is SOL.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Time to RMA
mindmajick said:
That's kind of what I thought too... Glad to have an expert confirm it, but sorry dude is SOL.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like it is time to send it back to Amazon. That is pretty bricked.

soupmagnet said:
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.
Click to expand...
Click to collapse
Any Chance of Amazon finding out that i acted like a noob dumb ass and bricked my device?
If no - i still could send it back could i not?

Just ship it back. usually amazon will send out a new one. Just say it doesn`t come on when you try to start it..

[Q&A] FireTV Full Bootloader Unlock

Q&A for FireTV Full Bootloader Unlock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for FireTV Full Bootloader Unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Worked perfectly for me. Just wanted to say thanks!

Stuck at CHMOD step...
I've rooted my Fire TV, but when I try to unlock the bootloader I can't get past the step:
chmod 755 /data/local/tmp/aftv-full-unlock
I've tried on both OSX and Windows. It tell me that "No such file or directory". I know that the file is on the FireTv, bc when I issue a Pull command through adbFire, it gives a list of files in that directory on the Fire TV, and aftv-full-unlock is one of them.
I do have BusyBox installed and I granted permission in SuperSU
My version is 51.1.0.1_user_510055620
What am I missing here...?

RuffRhyno said:
I've rooted my Fire TV, but when I try to unlock the bootloader I can't get past the step:
chmod 755 /data/local/tmp/aftv-full-unlock
I've tried on both OSX and Windows. It tell me that "No such file or directory". I know that the file is on the FireTv, bc when I issue a Pull command through adbFire, it gives a list of files in that directory on the Fire TV, and aftv-full-unlock is one of them.
I do have BusyBox installed and I granted permission in SuperSU
My version is 51.1.0.1_user_510055620
What am I missing here...?
Click to expand...
Click to collapse
I don't know your level of experience so I'm going back to basics.
You mentioned that you tried in Windows and OSX.
Where exactly are you issuing the command?
Are you in the adb shell?
Did you type 'adb shell' after pushing the file to the FTV?

After full unlocking of boot loader and using an ssh server on the firetv, when I connect I am stuck with a root prompt. is there a way to step down the shell to manage package installations. for some reason "pm" command is not functioning correctly with root. I wish to use this for remote administration, I suppose, using the commands "start adbd" and "stop adbd" from within an ssh term session and then connecting to adb port might suffice but I would prefer to keep adb service stopped since it is not password protected. campuses are always full of prowlers and pranksters at all times. thanks

Hey Guys,
I have followed all steps and rebooted my FireTV using "adb reboot bootloader". The FireTV did reboot on command and has stopped on the white Amazon logo. I then unplugged the usb A to A cable and rebooted the device via hard reset. The FireTV did start up normally upon plugging the device back in the AC adapter.
My main concern is if I did in fact fully unlock the bootloader. After rebooting the FireTV there was no other information on the command prompt after running the command "adb reboot bootloader" so this is why I question it. I did enter command "adb shell" which then gives me "[email protected]".
Just a noob (I know you heard that before) looking for reassurance. Thank you in advance. You all do amazing work!

mozzer27 said:
Hey Guys,
I have followed all steps and rebooted my FireTV using "adb reboot bootloader". The FireTV did reboot on command and has stopped on the white Amazon logo. I then unplugged the usb A to A cable and rebooted the device via hard reset. The FireTV did start up normally upon plugging the device back in the AC adapter.
My main concern is if I did in fact fully unlock the bootloader. After rebooting the FireTV there was no other information on the command prompt after running the command "adb reboot bootloader" so this is why I question it. I did enter command "adb shell" which then gives me "[email protected]".
Just a noob (I know you heard that before) looking for reassurance. Thank you in advance. You all do amazing work!
Click to expand...
Click to collapse
That is normal and yes your root is fully unlocked if you get [email protected] when adb shell command is being sent.

Could this be used on the fire TV stick? version 54.1.0.2_user_102018720?

I still have a sealed german fire tv, which came with 51.1.3.0_user_513010720, for which no software root is known.
After having studied the unlock-code at the original Fire HDX thread and the modified tool for the Fire TV I wonder if the following might be possible.
From the hdx thread the first steps:
Code:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
create a file unlock.img with following content:
0xmmssssssss
where mm=manfid and ss=serial
encrypt it with my vortox fork of signing tool at
https://github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
This seems identical, what the routine at https:// github.com/androidrbox/aftv-full-unlock/blob/master/jni/aftv-full-unlock.c does.
rbox said:
For now, this requires root. Apparently, the IDs that are required for this can be gotten through fastboot, so if someone can figure that out, then brand new Fire TVs with 51.1.0.2 or older can be unlocked and have recovery installed before booting the first time.
Click to expand...
Click to collapse
For what exactly is root necessary? You can get the manfid and serial without root.
The fire-tv-tool then base64 encodes the signed result from cuber.
Code:
snprintf(idme_cmd, sizeof(idme_cmd), "idme unlock_code %s\n", bptr->data);
system(idme_cmd);
That should be also possible without uid 0.
Before I brick my fire tv. I wondered if someone could shed some light, if I might succeed trying
a) using cuber manually to sign the unlock data, base64-encode it and unlock my bootloader with idme unlock
b) using cuber manually to sign the unlock data and use ./fastboot flash unlock unlock.signed like it is possible with the Fire HDX-devices.
After that I could fastboot boot twrp and finally get root and downgrade. Possible or did I miss something?

The bootloader on your fire tv is not vulnerable to this exploit so it is not going to work. That is the reason "Fire TVs with 51.1.0.2 or older" is stated.

adb after full-unlock-bootloader
Can someone please help me? AFTER installing unlocked bootloader, when connected to fire tv via adb, I no longer get a pop up window for Superuser request: Adb on the fire tv. I need to know if that is normal and if ADB automatically gets SuperSu rights?
PS: Adb still works fine just no popup asking me for Superuser request or a pop up saying saying Adb has been granted permission. Thanks

Hey guys I was able to install latest recovery on 8520, my ? is, when I go to check unlock status I still get [email protected], I thought you couldnt install recovery if loader was locked, and am I safe to install boot menu

goodbye hppalm said:
Hey guys I was able to install latest recovery on 8520, my ? is, when I go to check unlock status I still get [email protected], I thought you couldnt install recovery if loader was locked, and am I safe to install boot menu
Click to expand...
Click to collapse
You most probably have a partial not a full unlock bootloader, that is why. CWM only needed a partial bootloader and so is boot menu however go ahead a fully unlock it, will help you later if for some reason box gets bricked.

Ty bula for comments, I think I screwed my firetv, by the thread it said if u have recovery working everything should be fine, I tried the boot menu, now stuck on white logo and no response, is it hard bricked now

Downgrading AFTV using a Mac
PLEASE HELP!
Has there been any update to AFTVnews posting titled "How to manually upgrade or downgrade the amazon fire tv". The instructions are old (June 2014)and don't seem to work. I've searched the internet and can't seem to find any way to downgrade AFTV before unlocking the bootloader.
Also, I can't find anything detailing how to use adbfire in order to downgrade AFTV.
In addition, I found information on how to downgrade AFTV firmware, but nothing for Mac users.
Your help would be greatly appreciated!!

i used the guides on aftvnews.com to unlock the bootloader on my original firetv. they worked great and I was using a mac

I'm running Pre-rooted 51.1.4.0_user514006420 and I'm fairly certain I need to update my Clockwork which is why i'm trying to follow the unlock guide online to fully unlock from following instructions.
However I hit a dead wall when just getting the process going. I've been stuck here long ago and I'm not revisiting this same issue once again.
When running the command.
Code:
[email protected]:/ adb push aftv-full-unlock /data/local/tmp/
My return is
Code:
adb push aftv-full-unlock /data/local/tmp/
cannot stat 'aftv-full-unlock' : No such file or directory
1|[email protected]:/ $
I have the file in the adb directory as instructed.
I really hope someone has some insight. I can't go beyond this version unless figured out to maintain root and when getting to this current firmware I'm on my FireTV doesn't ever sleep anymore.
Thanks!

May I suggest using this utility to automate the procedure?
http://forum.xda-developers.com/showthread.php?t=2736774

is this for aftv2 also???
i'm rooted at 5.2.1 r2 . twrp 3.0.0 recovery . disabled all updates app and blocked address in router setting.
if yes i should downgrade to 5.0.5.1?
thanx

htchd2fix said:
is this for aftv2 also???
i'm rooted at 5.2.1 r2 . twrp 3.0.0 recovery . disabled all updates app and blocked address in router setting.
if yes i should downgrade to 5.0.5.1?
thanx
Click to expand...
Click to collapse
No

FireTV 2nd Generation looping on updating to latest software screen

Hi all,
Absolutely frustrated by my 2nd Gen FireTV 4K - just been stuck on the installing the latest software screen and gets to the end to loop to a white Amazon logo for about a second to back to installing. Been doing this for ages
1. Tried to ADB but can’t connect - the IP address only stays up for a while plus ADB debugging maybe off…
2. Tried the keyboard method, Alt I print screen, doesn’t work.
3. Changed HDMI cables and ports, no idea how that makes a difference
4. Restarted my router, again don’t know how that makes a difference
5. Held the various buttons on remote and that doesn’t work either.
Absolutely ruined my Sunday afternoon
Trying all this, anybody with an idea of what I could do next would be great as it just keeps getting stuck in this install, restarts itself and then repeats again!
Picture attached. Usually takes about 2-4 mins, then restarts for a short while to this again and starts again, freezes , then suddenly completes.

You could try unlocking it, and using TWRP to reflash it
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
If you don't want to go down that road, you can use the command adb wait-for-device to wait until ADB is ready and then automatically send a command. For example:
adb wait-for-device && adb logcat > logcat.txt
This will automatically dump logcat as soon as adb becomes available. Then you can look through the log for whatever is causing the problem etc.
I'm not sure if the Android factory reset works on FireTV, you can try
adb wait-for-device && adb shell "recovery --wipe_data"
Or
adb wait-for-device && adb shell "input keyevent KEYCODE_FACTORY_RESET"

Finnzz said:
You could try unlocking it, and using TWRP to reflash it
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
If you don't want to go down that road, you can use the command adb wait-for-device to wait until ADB is ready and then automatically send a command. For example:
adb wait-for-device && adb logcat > logcat.txt
This will automatically dump logcat as soon as adb becomes available. Then you can look through the log for whatever is causing the problem etc.
I'm not sure if the Android factory reset works on FireTV, you can try
adb wait-for-device && adb shell "recovery --wipe_data"
Or
adb wait-for-device && adb shell "input keyevent KEYCODE_FACTORY_RESET"
Click to expand...
Click to collapse
Hi Finzz,
Thanks for your reply, wasn’t expecting anyone to get back to me on this to be honest!
I tried sudo ADB connect with the ip address that shows up on ipconfig /getethaddr but didn’t work. It seems the continuous reboots also knocks out the connection.
I don’t think ADB was enabled on the firetv so I can’t ADB connect anyway…
I’ll check the guide you posted now, thanks
Regards,
Jesal

Finnzz said:
You could try unlocking it, and using TWRP to reflash it
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
If you don't want to go down that road, you can use the command adb wait-for-device to wait until ADB is ready and then automatically send a command. For example:
adb wait-for-device && adb logcat > logcat.txt
This will automatically dump logcat as soon as adb becomes available. Then you can look through the log for whatever is causing the problem etc.
I'm not sure if the Android factory reset works on FireTV, you can try
adb wait-for-device && adb shell "recovery --wipe_data"
Or
adb wait-for-device && adb shell "input keyevent KEYCODE_FACTORY_RESET"
Click to expand...
Click to collapse
I have standard firetv firmware, will
The TRWP work and unbrick work? Doubt I have a usb cable A-A too. Will USB C to
A work?

jespat88 said:
I have standard firetv firmware, will
The TRWP work and unbrick work? Doubt I have a usb cable A-A too. Will USB C to
A work?
Click to expand...
Click to collapse
Oh ok, I thought you might be using a USB cable to make your ADB connection attempt. The device must be getting pretty far in the boot process if it's even making a momentary WiFi connection.
I don't think the method used in that link can be blocked by Amazon. It's made possible by a simple hardware short.
You would be using this to load TWRP from a computer onto your device, to allow you to reflash it, and wipe data if needed. It would work with the stock Amazon firmware.
You will need to buy/obtain that USB A to USB A cable for your computer to communicate with the FireTV. They are a few bucks on Amazon:
https://www.amazon.com/USB3-0-VCZHS-Double-Enclosures-Laptop/dp/B089ZZW425/
You could probably even get one for cheaper if you search around on Amazon/eBay.