FireOS isn't running, so anything you have installed there doesn't matter.
FireTV 1 (bueller) TWRP Recovery
- Thread starter rbox
- Start date
FireOS isn't running, so anything you have installed there doesn't matter.
Alternative launchers MIGHT be a common link for some who are having issues (though I don't know why.) Would this process also disable/uninstall xposed and some of rbox tv mods?
Getting the TWRP loop here too...
USB pull didn't work. Going to re-flash CWM and wipe all partitions and reinstall FireOS3 and try again
USB pull didn't work. Going to re-flash CWM and wipe all partitions and reinstall FireOS3 and try again
The USB plugging method didn't work for me either.
While I recovered my fireTV I used my 2nd pc screen as display, noticed the interlacing problem there too. The screen has a resolution of 1680x1050. It works fine on my tv though (1366x768)
http://imgur.com/Pb8XuKb (More like an overview, but display informations unreadable)
http://imgur.com/mO663vA (display informations readable, and yeah, awesome resolution...)
While I recovered my fireTV I used my 2nd pc screen as display, noticed the interlacing problem there too. The screen has a resolution of 1680x1050. It works fine on my tv though (1366x768)
http://imgur.com/Pb8XuKb (More like an overview, but display informations unreadable)
http://imgur.com/mO663vA (display informations readable, and yeah, awesome resolution...)
You know what... I do. Now that you mention that, I remember reading there was an issue with that. D'oh!
Thanks... Looks like I gotta try to see if TWRP Manager will get things installed for me, unless you have some type of workaround?
You know what... I do. Now that you mention that, I remember reading there was an issue with that. D'oh!
Thanks... Looks like I gotta try to see if TWRP Manager will get things installed for me, unless you have some type of workaround?
I can't say whether TWRP Manager will work or will do bad things... but the workaround to a nonworking 720/1080i TV is to use something 1080p.
OK... Thanks! I'll check my other TV and go from there. :good:
Flashfire
Wonder if Chainfire's Flashfire would work on AFTV? I flashed the latest TWRP to my phone with it.
https://play.google.com/store/apps/details?id=eu.chainfire.flash
Also, would it help if went to CWMR first and wiped Dalvik and Cache there?
Could we push the Rbox TWRP while the box is still in CWMR? Maybe that would alow the push at a lower level.
I am clueless so just asking.
Wonder if Chainfire's Flashfire would work on AFTV? I flashed the latest TWRP to my phone with it.
https://play.google.com/store/apps/details?id=eu.chainfire.flash
Also, would it help if went to CWMR first and wiped Dalvik and Cache there?
Could we push the Rbox TWRP while the box is still in CWMR? Maybe that would alow the push at a lower level.
I am clueless so just asking.
I have an added an extra step for people who think they have an unlocked bootloader to verify that it actually is unlocked.
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
So I got fastboot working, but I cannot flash and old recovery:
target didn't report max-download-size
sending 'recovery' (8596 KB)...
OKAY [ 0.283s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.316s
Am I bricked?
target didn't report max-download-size
sending 'recovery' (8596 KB)...
OKAY [ 0.283s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.316s
Am I bricked?
I can't even begin to understand how you box decided to lock itself.
I don't know. Your bootmenu is still there, so that means I must have been unlocked...right? I wiped cache via fastboot. Anything else to try?
USB HD worked for me
I could not get twrp to load and it kept flashing from the twrp logo to black screen and wouldn't load. I could reboot into FireOS 3 with the old bootmenu and everything seemed to still work so i pulled the power on my firetv.
I kept the usb dongle for my keyboard plugged directly into the firetv.
I waited for the bootmenu to come up and selected recovery, then I unplugged the usb dongle and plugged in a fat32 formatted 500gb toshiba HD and waited for the timer on the bootmenu to expire.
It then showed the TWRP logo and didn't go to a black screen and loaded into the recovery.
I did this twice and it worked both times
I tried this with a usb hub/sdcard reader with a 1gb microSD in it and it would not work.
Also my 500gb drive is a usb powered drive.
I could not get twrp to load and it kept flashing from the twrp logo to black screen and wouldn't load. I could reboot into FireOS 3 with the old bootmenu and everything seemed to still work so i pulled the power on my firetv.
I kept the usb dongle for my keyboard plugged directly into the firetv.
I waited for the bootmenu to come up and selected recovery, then I unplugged the usb dongle and plugged in a fat32 formatted 500gb toshiba HD and waited for the timer on the bootmenu to expire.
It then showed the TWRP logo and didn't go to a black screen and loaded into the recovery.
I did this twice and it worked both times
I tried this with a usb hub/sdcard reader with a 1gb microSD in it and it would not work.
Also my 500gb drive is a usb powered drive.
Last edited:
Bootmenu works? Why are you messing around with fastboot? What's not working?
Got it sorted. Currently flashing 5.0.5.1
Reflashed back to CWM
Wiped Data, Data/Media, Cache, Dalvik Cache, System.
Flashed last FireOS3 firmware.
Flashed TWRP again
Rebooted to recovery and worked perfect. Just did all the wipes again and now flashing the mentioned firmware.
There must be something somewhere that prevents TWRP from loading if it's not a clean install....
Thanks for all your work rBox!!!!
Reflashed back to CWM
Wiped Data, Data/Media, Cache, Dalvik Cache, System.
Flashed last FireOS3 firmware.
Flashed TWRP again
Rebooted to recovery and worked perfect. Just did all the wipes again and now flashing the mentioned firmware.
There must be something somewhere that prevents TWRP from loading if it's not a clean install....
Thanks for all your work rBox!!!!
Bootmenu comes up (version 1.0)
If I select recovery, 3.0.0-6 just flashes (tried usb stick trick, did not work, but don't have a hard drive)
If I select the normal mode, it just sits at amazon logo.
i think twrp is trying to find external storage so did you leave the usb stick in while it booted or take it out once the twrp screen comes up?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
34It'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
- Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!Code:cat /proc/cmdline - Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
- Copy the bueller-twrp_3.0.0-6.img file to /sdcard
- 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 - From outside adb shell, reboot to recovery
Code:adb reboot recovery - TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
- This requires that you are on at least version 5.0.5 and rooted.
- Copy the bueller_recovery_vX.zip file to /sdcard
- 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 - 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
to restart itCode:
killall recovery - 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
Ask and ye shall receive... This has the looping fix and a possible 720 fix.
http://www.mediafire.com/download/uzvjvjb5ydvyja3/bueller-twrp-test8.img5
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
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 rom4To 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? - Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone