FireTV 1 (bueller) TWRP Recovery

Search This thread

jlaing2607

New member
May 23, 2009
4
0
ATX
Ask and ye shall receive... This has the looping fix and a possible 720 fix.

Does anybody have TWRP test8 or test9 for download? Both of the Mediafire links are dead. I'm running AFTV gen 1 with latest clockwork and ROM version 51.1.6.3_516012020. I've tried 2 different TV/monitors but still getting the blinking/looping.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
Does anybody have TWRP test8 or test9 for download? Both of the Mediafire links are dead. I'm running AFTV gen 1 with latest clockwork and ROM version 51.1.6.3_516012020. I've tried 2 different TV/monitors but still getting the blinking/looping.
Asking for TWRP test 8 or 9 is like asking for a beta. TWRP v7 which is in the OP (First Post) is the Final version of all those "test". So that is what you need.

This is the best guide out there:

http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/

Make sure you do the Full boot loader Unlocking if possible too. Go thru all the prerequisite requirements one by one. Just replace the part about v6 to v7. In your stated case above you will only follow "Section 1: Fire TV 1 on 51.1.6.3 or older" & the TWRP file you will use is the TWRP image "July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)". Once TWRP is installed correctly. That means you can reboot to it using a USB keyboard. You are set. All future updates of TWRP will happen thru the PreRooted ROM (Unless stated otherwise by RBox).

Make sure you use MD5 files for hash checking anything you are flashing thru TWRP. It really helps with file integrity. You don't need to do a Factory Reset & NEVER DO A /SYSTEM wipe unless you are an expert. When ever you do a /SYSTEM wipe you have to flash a PreRooted ROM before rebooting or you will brick your FTV1. Flashing the PreRooted ROM will wipe /System for you. So you never have to go out of your way to do that. You can always do a Cache & Dalvik wipe of you are having any issues. Those can help. But are rarely needed. I myself keep a USB Stick with all the files I need just for updating my FTV1's. Makes things a lot simpler.

If you have ?'s or don't understand something ask NOW. A lot of folks that brick their FTV1's wait to ask for help in the middle of the process or after it's to late.
 
Last edited:

jlaing2607

New member
May 23, 2009
4
0
ATX
Asking for TWRP test 8 or 9 is like asking for a beta. TWRP v7 which is in the OP (First Post) is the Final version of all those "test". So that is what you need.

This is the best guide out there:

http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/

Make sure you do the Full boot loader Unlocking if possible too. Go thru all the prerequisite requirements one by one. Just replace the part about v6 to v7. In your stated case above you will only follow "Section 1: Fire TV 1 on 51.1.6.3 or older" & the TWRP file you will use is the TWRP image "July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)". Once TWRP is installed correctly. That means you can reboot to it using a USB keyboard. You are set. All future updates of TWRP will happen thru the PreRooted ROM (Unless stated otherwise by RBox).

Make sure you use MD5 files for hash checking anything you are flashing thru TWRP. It really helps with file integrity. You don't need to do a Factory Reset & NEVER DO A /SYSTEM wipe unless you are an expert. When ever you do a /SYSTEM wipe you have to flash a PreRooted ROM before rebooting or you will brick your FTV1. Flashing the PreRooted ROM will wipe /System for you. So you never have to go out of your way to do that. You can always do a Cache & Dalvik wipe of you are having any issues. Those can help. But are rarely needed. I myself keep a USB Stick with all the files I need just for updating my FTV1's. Makes things a lot simpler.

If you have ?'s or don't understand something ask NOW. A lot of folks that brick their FTV1's wait to ask for help in the middle of the process or after it's to late.

Thanks worked like a champ. It was late last night realized today I using 3.0.0.-6 instead of -7.
 

1jimmy007

Member
Mar 18, 2017
17
2
In tall twrp 3.0.0-7 recovery

Does anybody have TWRP test8 or test9 for download? Both of the Mediafire links are dead. I'm running AFTV gen 1 with latest clockwork and ROM version 51.1.6.3_516012020. I've tried 2 different TV/monitors but still getting the blinking/looping.

Install twrp 3.0.0-7 recovery, then jump to Bueller rom 5.2.1.2_r1. Have this rom in SD card before you do recovery change. And or have the 51.1.6.3 rom there too. I've learned to have a rom in SD card because I've lost or but had recovery and was able to bail out by load safe rom.

After good recovery change over and 5.2.1.2 rom. Then load SD card with latest 5.2.4.1_r1 and flash that if you like...
 

null0pointer

Member
Oct 26, 2009
14
0
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.

I'm in the same boat... any chance you could post a little more detail on how exactly you accomplished this?

Thanks.
 

Matt_7

Senior Member
Sep 9, 2012
98
8
Currently I have:
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)

How do I update to:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2) ?

Thanks.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
Currently I have:
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)

How do I update to:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2) ?

Thanks.
For FTV1's there are is No v2. TWRP v3.0.0-7 is the latest. And flashing the latest PreRooted ROM is the Method to update when an update becomes available.
 
Last edited:
  • Like
Reactions: Matt_7

Matt_7

Senior Member
Sep 9, 2012
98
8
For FTV1's there are is No v2. TWRP v3.0.0-7 is the latest. And flashing the latest PreRooted ROM is the Method to update when an update becomes available.

I've already flashed to 5.2.4.1_r2 yesterday but didn't install "July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)"...can I now:

1) adb push bueller_recovery_v2.zip /sdcard/
2) adb reboot recovery
3) In TWRP, select install bueller_recovery_v2.zip

Thanks.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
I've already flashed to 5.2.4.1_r2 yesterday but didn't install "July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)"...can I now:

1) adb push bueller_recovery_v2.zip /sdcard/
2) adb reboot recovery
3) In TWRP, select install bueller_recovery_v2.zip

Thanks.
Flashing 5.2.4.1_r2 already put the latest TWRP Recovery.

Trying to find what bueller_recovery_v2 you keep mentioning is.....

K, I see what your talking about... Will try to verify which version of the last TWRP Recovery the last PreRooted ROM comes with. My best guess is it is v2. I think @rbox just didnt noted in the changelog posts. But will try to verify that. Will let you know as soon as I find out.

Is everything working fine for you or is there something making sure v2 is what you got might fix ?
 
Last edited:

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
I've already flashed to 5.2.4.1_r2 yesterday but didn't install "July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)"...can I now:

1) adb push bueller_recovery_v2.zip /sdcard/
2) adb reboot recovery
3) In TWRP, select install bueller_recovery_v2.zip

Thanks.
K, so you almost had me confused.

There are only 2 official TWRP Recoveries for FTV1's. The original v3.0.0-6 & the latest v3.0.0-7.

If you already flashed any rooted FTV1 with a PreRooted FW released after July 4th, 2016. Then you have the latest FTV1 TWRP Recovery v3.0.0-7.

The v1 & v2 releases are different installers of TWRP specifically for those that rooted their FTV1's when on FireOS 5. It is what they use to flash TWRP the first time. The .IMG releases are for those upgrading from FireOS 3 on CWM to FireOS 5 & TWRP. Hence there is a .IMG for TWRP 3.0.0-6 & 3.0.0-7 & a v1 & v2 TWRP 3.0.0-6. & 3.0.0-7. This is also flashed only the first time.

Any TWRP upgrades after that are taking care in the PreRooted FTV1 ROM.

If you try to flash v2 onto a 5.2.4.1_r2 FTV1 at best nothing will happen & at worst you might mess your device up. You are already at the latest TWRP v3.0.0-7. Just reboot into TWRP. You should see your current version number in the upper left corner.

The only time anybody would manually/personally flash v2 is if you are staying on a pre July 4th, 2016 PreRooted ROM to run FireStarter/FireStooper & you still wish to upgrade your TWRP to the latest v3.0.0-7 without touching your PreRooted ROM. Very few folks check those boxes.
 
Last edited:
  • Like
Reactions: Matt_7

Matt_7

Senior Member
Sep 9, 2012
98
8
K, so you almost had me confused.

There are only 2 official TWRP Recoveries for FTV1's. The original v3.0.0-6 & the latest v3.0.0-7.

If you already flashed any rooted FTV1 with a PreRooted FW released after July 4th, 2016. Then you have the latest FTV1 TWRP Recovery v3.0.0-7.

The v1 & v2 releases are different installers of TWRP specifically for those that rooted their FTV1's when on FireOS 5. It is what they use to flash TWRP the first time. The .IMG releases are for those upgrading from FireOS 3 on CWM to FireOS 5 & TWRP. Hence there is a .IMG for TWRP 3.0.0-6 & 3.0.0-7 & a v1 & v2 TWRP 3.0.0-6. & 3.0.0-7. This is also flashed only the first time.

Any TWRP upgrades after that are taking care in the PreRooted FTV1 ROM.

If you try to flash v2 onto a 5.2.4.1_r2 FTV1 at best nothing will happen & at worst you might mess your device up. You are already at the latest TWRP v3.0.0-7. Just reboot into TWRP. You should see your current version number in the upper left corner.

The only time anybody would manually/personally flash v2 is if you are staying on a pre July 4th, 2016 PreRooted ROM to run FireStarter/FireStooper & you still wish to upgrade your TWRP to the latest v3.0.0-7 without touching your PreRooted ROM. Very few folks check those boxes.

Wow, luckily I didn't do anything yet!

One last question, now that the file "bueller_recovery_v2.zip" is at " /sdcard/" (adb push bueller_recovery_v2.zip /sdcard/), how do I delete it (to prevent accidentally executing it in the future). I've ES File Explorer, under what file/directory/folder is this /sdcard/?

Thanks.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
Wow, luckily I didn't do anything yet!

One last question, now that the file "bueller_recovery_v2.zip" is at " /sdcard/" (adb push bueller_recovery_v2.zip /sdcard/), how do I delete it (to prevent accidentally executing it in the future). I've ES File Explorer, under what file/directory/folder is this /sdcard/?

Thanks.
In ES File Explorer go to Local & Home on the left side menu. That zip file should be outside the folders towards the bottom.
 
Last edited:
  • Like
Reactions: Matt_7

Matt_7

Senior Member
Sep 9, 2012
98
8
In ES File Explorer go to Local & Home on the left side menu. That zip file should be outside the folders towards the bottom.

OK, got it!

Are the folders and files in that directory "Home" delectable? (most of the folders are empty) and I also see:
? bootmenu.img
? bueller-twrp_3.0.0.7.img
? PrimePhotosAppDisa bledState.
? recovery.img
bueller_recovery_v2.zip (I already deleted)

Thanks.
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
OK, got it!

Are the folders and files in that directory "Home" delectable? (most of the folders are empty) and I also see:
? bootmenu.img
? bueller-twrp_3.0.0.7.img
? PrimePhotosAppDisa bledState.
? recovery.img
bueller_recovery_v2.zip (I already deleted)

Thanks.
I usually don't like to tell folks to delete any files. Since I don't want to be held accountable for any bricking.

The best I can tell you is that since I use a USB Drive to flash things. And I've used TWRP to Factory Reset on one of my updates of my PreRooted ROM. The only file from your list I have in my SDCard directory is "PrimePhotosAppDisa bledState.". All the others I think where removed on my last Factory Reset if I am not mistaken or where installed from a USB Drive. Hence never uploaded to the internal SDCard.

If you plan to delete them. Just be ready with a USB Stick with the latest PreRooted ROM in case you need to reflash it. But I doubt it.
 
  • Like
Reactions: Matt_7

Matt_7

Senior Member
Sep 9, 2012
98
8
I usually don't like to tell folks to delete any files. Since I don't want to be held accountable for any bricking.

The best I can tell you is that since I use a USB Drive to flash things. And I've used TWRP to Factory Reset on one of my updates of my PreRooted ROM. The only file from your list I have in my SDCard directory is "PrimePhotosAppDisa bledState.". All the others I think where removed on my last Factory Reset if I am not mistaken or where installed from a USB Drive. Hence never uploaded to the internal SDCard.

If you plan to delete them. Just be ready with a USB Stick with the latest PreRooted ROM in case you need to reflash it. But I doubt it.

Got it! You are a smart guy:D.

Thank you very much for all your help and may you have a great day!
 

Y314K

Senior Member
Dec 29, 2008
1,498
488
Samsung Galaxy A32 5G
Got it! You are a smart guy:D.

Thank you very much for all your help and may you have a great day!
I just read a lot... The smart guys are RBox, Elias from AFTVNews, SymLinks, Nylm & countless others sharing what they code or figure or find out.

For us non-coders... I always say... SHARE THE KNOWLEDGE!! (Unless there is an embargo by the coder/maker)
 

swofra

Member
Feb 18, 2017
6
0
Hey all,
Snapshot for those who appreciate brevity (longer explanation below):
FIRE TV1 51.1.6.3 (516012020), loaded with CM 6.0.5.1.4a and a confirmed fully unlocked bootloader.
Normal boot sequence for this device is RBox's Boot Menu, then a couple flashes of snow/static, and then the Amazon OS loads.
Tried to install TWRP 3.0.0-7 so I could upgrade to OS5. Verified checksum of the TWRP good.
Failed to exit out of #root before entering "adb reboot recovery" after uploading TWRP.
Result is continuous reboot of snow/static - never gets to TWRP, boot menu or any screen.
Have not shut the device off or rebooted. Tried killall recovery, restoring TWRP, and restoring CM to no effect...now I can't even connect to the device.

More descriptive below:
Hope your day is going better than mine...thought I'd throw this out to the crowd and the experts to see if anyone else had seen this before: After attempting to upgrade FireOS 3 to 5 on my FIRE TV1 51.1.6.3 (516012020) all I get is a continuous reboot of snow...the static stuff that used to play on TVs after midnight back in the day before infomercials became a thing. No TWRP, no recovery screen, nothing, just several flashed of snow. Anyway, I was trying to install TWRP 3.0.0-7 onto my fully unlocked (and confirmed unlocked) bootloader. I also have CM 6.0.5.1.4a installed and confirmed that before starting as well. Downloaded the TWRP file, confirmed with checksum and did everything by the book until the end when I failed to exit out of root before entering "adb reboot recovery". On my usual bootup sequence I get a flash or two of "snow" after Rbox's v1.0 screen and before the amazon screen, but it last about 2 seconds.
This time when it started snowing I was concerned because it happened right away. I've never seen a screen of anything other than snow. I let it go a couple of times and then tried killall recovery as suggested in the front of this thread, which had zero effect. As recommended, I also have NOT rebooted (and still haven't). When I looked in adblink it said it was connected but connection status was recovery. I went back in root -- which gave me the hashtag but with a weird 6N after it instead of the word "root". Tried to reinstall TWRP and then CM to no effect....still just gives me the snow. troubleshot for a couple of hours with no success. Once when connected with adblink I hit Stop ADB. Now I can't even connect to it...still haven't powered it off though. Is there any hope for my little friend or did I slaughter him carelessly? Any help would be greatly appreciated.
 

swofra

Member
Feb 18, 2017
6
0
Update: It is now hung on the white amazon logo boot screen. I tried a couple of USB wired keyboards but they didn't have any effect. I saw that the favored keyboard was the Logitech k400, which isn't wired. What is the keyboard requirement? If they are keyboards with wireless USB dongle connections would they have to have been set up prior to any issues? Or can it be a wired keyboard with a USB connection but not all are compatible? Thanks in advance for any assistance you might be able to provide.
 

coolllman

Member
Mar 29, 2017
8
1
Hello! I have fire tv 1 with 51.1.6.3 rooted with dirtycow not bootloader fully unlocked, what i need to install twrp?
In this tread wrote on fire tv OS3 install twrp for only bootloader fully unlocked.

Update: I manualy update to 5.0.5 and rooted with kingroot, now i do install twrp!!!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 34
    It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.

    As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.

    Installing this requires root. If you are not rooted, figure that out first.

    Installation for Unlocked Bootloader
    1. Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
      Code:
      cat /proc/cmdline
      And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
    2. Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
    3. Copy the bueller-twrp_3.0.0-6.img file to /sdcard
    4. From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
      Code:
      dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
    5. From outside adb shell, reboot to recovery
      Code:
      adb reboot recovery
    6. TWRP should load, you can install a FireOS5 prerooted ROM now.

    Installation for Locked Bootloader
    1. This requires that you are on at least version 5.0.5 and rooted.
    2. Copy the bueller_recovery_vX.zip file to /sdcard
    3. From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
      Code:
      sh /data/media/0/bueller_recovery_vX.zip
    4. Reboot

    Notes
    This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.

    DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.

    USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.

    You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.

    ROMs
    Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.

    Installing zips
    You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.

    Stuck in a loop?
    If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.


    Source Code
    You can find the source code here:
    https://github.com/androidrbox/firetv-2ndinit
    https://github.com/androidrbox/android_bootable_recovery

    WARNINGS

    • It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
      Code:
      killall recovery
      to restart it
    • It is also extremely important to never reboot after wiping /system.


    Finally, thanks to everyone who has donated to me.

    Changelog and Downloads:
    • July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
      • This is the updated version with TWRP 3.0.0-7.
    • July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
    • May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
      • This is for use by people who have FireOS5 and are rooted.
      • This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
    • May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
      • This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
    8
    This test image worked for me but my tv is only 720p so the graphics overlap and it is VERY hard to use. Any chance of getting a version with a 720p theme instead?

    Ask and ye shall receive... This has the looping fix and a possible 720 fix.

    http://www.mediafire.com/download/uzvjvjb5ydvyja3/bueller-twrp-test8.img
    5
    Worked great!! Thanks so much for all your hard work!

    Okay. Well unfortunately bootmenu will still be jacked up. And I won't have time until next week to make a proper release with all these fixes... but it should keep you guys happy until then.
    4
    I can't imagine why a TV would cause TWRP to crash, but at this point I can't explain it.

    New TV did nothing, as you suspected.

    I did get it to work though, Here's what I did.
    Reflashed latest CWM
    Full wipe in CWM (Not sure if this was needed?)
    adb shelll WHILE IN CWM and flashed TWRP
    did adb reboot recovery and TWRP loaded, Now I flashed pre-rooted 5.0.5 rom
    4
    To anyone still experiencing the flashing problem and/or anyone who had it fixed with test8:

    http://www.mediafire.com/download/m84irafe8idoklm/bueller-twrp-test9.img

    Hopefully this fixes it?