FireTV 1 (bueller) TWRP Recovery

[reiteravi]

test7 worked for me
:good:

 

[ldeveraux]

The boot_unlocked was for if you hadn't rebooted. You have to flash every single firmware image. You also need to do eject /dev/sdb at the end or whatever your device is.

ejecting is the key here, without it, still no boot. Rbox, maybe you can add this to the op rather than referencing a thread post each time. Also, try making the first step in red letters, accentuate it more. I get that people should read carefully, but many people assumed they had a fully unlocked bootloader and soft bricked their devices.

 

[deepasadish]

http://www.mediafire.com/download/dwpbkyvnmstb24p/bueller-twrp-test7.img

Okay, here is a test image. I tried to correct the crashing, but more importantly, it should bring up the ethernet much earlier, to make debugging easier if it still doesn't work.

just curious, what did you fix that made this work?

also, will you be linking this in the OP as the fixed/updated TWRP or is this a one off thing.

thanks for your awesome and quick fix.

 

[Pumilio]

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.

just curious, what did you fix that made this work?

also, will you be linking this in the OP as the fixed/updated TWRP or is this a one off thing.

thanks for your awesome and quick fix.

So he will make a proper release when he has time next week

 

[decayed.cell]

test7 worked for me
:good:

I've tried test7 and test8. I've tried flashing it in CWM as well and it doesn't work. At least ADB comes up when its in recovery now. I just can't get a display up directly connected to my TV or through my receiver. It flashes the TWRP logo but that's it. The power LED pulsates on and off

 

[lightning413]

I've tried test7 and test8. I've tried flashing it in CWM as well and it doesn't work. At least ADB comes up when its in recovery now. I just can't get a display up directly connected to my TV or through my receiver. It flashes the TWRP logo but that's it. The power LED pulsates on and off

I had all the same problems that everyone else is having with my FTV1's and I've been successful with 2 of them and working on the 3rd one now.

What I do is after ensuring the bootloader is unlocked, dd'ing the bueller-twrp file and doing 'adb reboot recovery', I just let it sit for a couple of hours and the ftv eventually goes into the twrp recovery.
I have no idea why this works but it has worked with 2 of them so far.

 

[deepasadish]

couple of hours

:fingers-crossed: may be i should try this!!!

 

[tdfsu]

Can I update twrp like below?

adb push C:\bueller-twrp-test8.img /sdcard/
dd if=/data/media/0/bueller-twrp-test8.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Ive upgraded fo Fire OS5 and fully unlocked, but twrp from the OP is unusable because I have a 720p display.

 

[YoColdRain]

Can I update twrp like below?

adb push C:\bueller-twrp-test8.img /sdcard/
dd if=/data/media/0/bueller-twrp-test8.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Ive upgraded fo Fire OS5 and fully unlocked, but twrp from the OP is unusable because I have a 720p display.

did you do test8 recovery img, which rbox posted page or so back, specifically for 720p.

 

[tdfsu]

did you do test8 recovery img, which rbox posted page or so back, specifically for 720p.

No, that's what I want to do. Just want to make sure my adb commands are correct.

 

[YoColdRain]

Can I update twrp like below?

adb push C:\bueller-twrp-test8.img /sdcard/
dd if=/data/media/0/bueller-twrp-test8.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Ive upgraded fo Fire OS5 and fully unlocked, but twrp from the OP is unusable because I have a 720p display.

No, that's what I want to do. Just want to make sure my adb commands are correct.

yea that should be fine. sometimes, your img file location may differ. For example, I had to do /data/media/bueller... even tho it was transferred to /sdcard/

 

[iniro]

rbox thanks thanks and thanks, I have my lovely aftv running again. I restored with linux instructions. Ubuntu live usb and in my case, aftv was on /dev/sdd. Then I re-flashed prerooted 5.0.5.1_r1. Now Im trying to get xposed working again. This rom is not to auto update not?
thx thx and thx again rbox.

 

[rbox]

rbox thanks thanks and thanks, I have my lovely aftv running again. I restored with linux instructions. Ubuntu live usb and in my case, aftv was on /dev/sdd. Then I re-flashed prerooted 5.0.5.1_r1. Now Im trying to get xposed working again. This rom is not to auto update not?
thx thx and thx again rbox.

You should always be blocking updates.

 

[aHcVolle]

Ok so here is my way to twrp & 5.0.5.1:

I was on an fully unlocked bootloader, latest cwm and latest FireOS3 update.
When i first flashed twrp it didn't show anything on my tv when booting to recovery (via the old bootmenu or via adb reboot recovery didn't matter)...
I tried the original twrp from op as well as test7 and test8.
There was no change in the recovery boot.
I've got my firetv connected to my tv via my receiver, when i changed the cables to connect my firetv to my tv directly i got the flashing twrp boot screen.
After this i connected my firetv to my hdmi monitor which gave me the twrp menu, where i couldn't do anything because i could only see "install" and "wipe" but i didn't know what so select after a selected the .zip file.

I remembered tdfsu posting the shell command to install the .zip file. Since i could see twrp's IP i tried connecting to it via adb which succeeded.
I installed 5.0.5.1 via the command

recovery --update_package=/sdcard/bueller-5.0.5.1-rooted_r1.zip

This took a few minutes after which the firetv rebooted (i guess this was on purpose).
I could see the new bootmenu (or i couldn't, i did look weird like twrp) and after that i got a black screen (after the white amazon logo did show).
I connected the firetv back to my TV but didn't get any output there.
Then i rebooted the firetv which did show me the new bootmenu (it did look normal).
I selected recovery which did boot to twrp like there has never been a problem at all...
I wiped cache & dalvik in twrp and did reboot the firetv.
After some optimizing it did boot perfectly to FireOS5.

Thanks to rbox and to the rest of the testers in here!

 

[lightning413]

:fingers-crossed: may be i should try this!!!

#3 is done.
I don't think it's coincidence that I've been able to replicate this in 3 different boxes.
To me it looks like the box keeps trying to boot into recovery and until it eventually does.

Definitely give it a shot, it can't hurt.

 

[sanjonny]

So I am the new minority. As stated before, I am on static ip address (no DHCP on network). I tried the new 8 file (yes unlocked bootloader and 51.whatever) and this time, instead of the flashing during booting as we had with the previous version, I get nothing after it tries to boot into recovery. It reboots, goes to the white screen, flashes once and then sits on white screen. I can restore back to CWM fine as before, but no boot into TWRP at all with the latest changes, so no bootloop, just white screen. I checked md5 and dd a few times and even copied it over again, just to make sure, but no luck. Pulling the plug brings me to boot menu and if I select recovery there, I also go to blank white screen.

 

[949BFN]

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

Thank you so much. That did the trick!

 

[MrLyle]

So initially I had the bootloop problem. Tried with the test8 img and got the white light blinking issue. After about 7 or 8 minutes of blinking, TWRP actually loaded. I tried installing 5.0.5.1_r1 but I got an error. Error 7 I believe it was. Couldn't unmount /system.
And now I can't load the old Kernel either. It's just stuck in the boot menu. I can choose recovery and go back to the blinking problem. When I do that I at least have adb access.

 

[deepasadish]

#3 is done.
I don't think it's coincidence that I've been able to replicate this in 3 different boxes.
To me it looks like the box keeps trying to boot into recovery and until it eventually does.

Definitely give it a shot, it can't hurt.

you da man!!! this worked. i simply left it in TWRP looping/blinking (~1 hour) and eventually entered TWRP.

everyone should try this!!!

---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------

So initially I had the bootloop problem. Tried with the test8 img and got the white light blinking issue. After about 7 or 8 minutes of blinking, TWRP actually loaded. I tried installing 5.0.5.1_r1 but I got an error. Error 7 I believe it was. Couldn't unmount /system.

i got same error too. try wiping dalvik and cache and then install.

 

[MrLyle]

you da man!!! this worked. i simply left it in TWRP looping/blinking (~1 hour) and eventually entered TWRP.

everyone should try this!!!

---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------



i got same error too. try wiping dalvik and cache and then install.

trying that now, but I have to wait for blinking to stop and for TWRP to actually load...Last time it took about 5 minutes, see how long it takes this time.