FireTV 2 (sloane) Unbrick Image

Search This thread
By:
Advanced…
T

tech3475

Senior Member
Nov 4, 2013
93
10
errut said:
so i found an A-A-cable, but Post #1 didn`t work. It remaind "waitung for prloader"
The click was ok,when connected,my device was rooted before 5.05

Edit :moved folder with scripts of post #1 to overcome "waiting for Preloader"
but now i am stuck with :
Waiting for preloader...
Found port = COM4
Handshake complete!
Flashing unbrick image unbrick.img...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 0%
Click to expand...
Click to collapse

Bearing in mind it is slow, if it doesn’t progress beyond 0% then from my understanding that may mean you unfortunately have the patched preloader.

So may may need to use the alternative method.
 
D

Dulanjana Palamakumbura

Member
Apr 18, 2020
8
1
@rbox pls help me

I have fire TV stick 1st Gen and it is stuck in a bootloop and I can only see Amazon white logo and boot animation thats all

I haven't enable usb debugging :(

Pls help me to fix my device :)
 
Bertonumber1

Bertonumber1

Senior Member
May 17, 2020
884
266
Glasgow UK
Samsung Galaxy Tab A series
Samsung Galaxy S9+
Dulanjana Palamakumbura said:
I have fire TV stick 1st Gen and it is stuck in a bootloop and I can only see Amazon white logo and boot animation thats all

I haven't enable usb debugging :(

Pls help me to fix my device :)
Click to expand...
Click to collapse

Bin it and buy a 4k, montoya 1st generation cannot keep up with modern apps and lag terribly. Not worth wasting anytime on if you ask me. Buy a 4k you'll get one for 30 quid just now on amazon
 
Bertonumber1

Bertonumber1

Senior Member
May 17, 2020
884
266
Glasgow UK
Samsung Galaxy Tab A series
Samsung Galaxy S9+
errut said:
so i found an A-A-cable, but Post #1 didn`t work. It remaind "waitung for prloader"
The click was ok,when connected,my device was rooted before 5.05

Edit :moved folder with scripts of post #1 to overcome "waiting for Preloader"
but now i am stuck with :
Waiting for preloader...
Found port = COM4
Handshake complete!
Flashing unbrick image unbrick.img...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 0%
Click to expand...
Click to collapse

I'm having the exact same problem on Ubuntu 20.4, I tried windows 10 .bat script and I'm apparently missing a msvcr100.dll file. So had to revert to Ubuntu. Been stuck on 0% for half an hour now. Dunno what's happening.

I had twrp and couldn't get adb to connect, selected reboot recovery in twrp as it usually boots back into recovery. But instead I've bricked it like a proper donut.
I haven't any idea how to get round it, I tried doing the short again but it don't even appear "remove short and press enter" anymore, all I get is the handshake then serial protocol mismatch error straight away as soon as I plug dc voltage back in.
 
K

KB!

Senior Member
Feb 15, 2013
251
26
I am curious, what would happen if you run this on a non bricked device?

I have a Sloane that is currently on the newest 5.2.7.7 and I was wondering if I could use this method to revert back to something before 5.2.7.2.

Any help is appreciated.

Thanks in advance.
 
T

tech3475

Senior Member
Nov 4, 2013
93
10
Kbuskill! said:
I am curious, what would happen if you run this on a non bricked device?

I have a Sloane that is currently on the newest 5.2.7.7 and I was wondering if I could use this method to revert back to something before 5.2.7.2.

Any help is appreciated.

Thanks in advance.
Click to expand...
Click to collapse

Why would you want to downgrade?
 
H

H3llzno

New member
May 31, 2021
1
0
I am stuck at this point. Still won't boot.. Black screen slow flashing light. I did the slow write the first time and it was successful.. took about 2 hrs

Code: 
Waiting for preloader...
Found port = COM5
Handshake complete!
Injecting 2ndinit...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 100%
Reading 000000400: 100%
Opening the filesystem...
Reading 0058E0400: 100%
Reading 0058E0800: 100%
Locating the target file...
Reading 0058E8C00: 100%
Reading 0058E1000: 100%
Reading 0058E9000: 100%
Reading 0058E5000: 100%
Opening the target file...
error: source file is larger than target file!
Injecting 2ndinitstub...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 100%
Reading 000000400: 100%
Opening the filesystem...
Reading 0058E0400: 100%
Reading 0058E0800: 100%
Locating the target file...
Reading 0058E8C00: 100%
Reading 0058E1000: 100%
Reading 0058E9000: 100%
Reading 0058E5000: 100%
Opening the target file...
error: source file is larger than target file!
Press any key to continue . . .
 
S

Sus_i

Senior Member
Apr 9, 2013
1,871
824
H3llzno said:
I am stuck at this point. Still won't boot.. Black screen slow flashing light. I did the slow write the first time and it was successful.. took about 2 hrs
Click to expand...
Click to collapse

Try the new unbrick guide:
forum.xda-developers.com

[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 forum.xda-developers.com
 
You must log in or register to reply here.

Similar threads

R
FireTV 2 (sloane) Prerooted Stock Images [5.2.7.6_r1]
Replies
998
Views
243K
T
theistus
R
FireTV 1 (bueller) Prerooted Stock Images [5.2.7.3_r1]
Replies
2K
Views
352K
I
I_did_it_just_tmrrow
R
FireTV 2 (sloane) Recovery [v6] - 3.0.0-5
Replies
367
Views
109K
S
Sus_i
R
FireTV 1 (bueller) TWRP Recovery
Replies
566
Views
103K
T
TomandJonna
R
FireTV Stick (montoya) Prerooted Stock Images [5.2.7.3_r1]
Replies
183
Views
72K
V
vertycall

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 27
    R
    rbox
    This will help you unbrick a bricked FireTV 2. You must download the following:

    Extract all 3 zip files to the same directory.

    You must decide if you want to use unbrick.img or unbrick+ramdisk.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+ramdisk.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.

    Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.

    First, it will ask you which file you want to use, unbrick.img or unbrick+ramdisk.img. You must type the name of the image you want to use.

    Make sure the USB cable is connected and turn on the FireTV 2.

    Then it will start reading from the FireTV. Then it will prompt you with a warning:

    Code: 
    No target file specified.  Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>

    Type a 'y' and hit enter.

    It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
    View
    4
    R
    rbox
    jim16127 said:
    I am in a boot loop. Goes to amazon white logo. Light on FireTV2 turns orange then reboots into custom recovery but it automatically starts trying to mount partitions (one of them is cache) and it fails on all of them. Then moves along to the white amazon screen again and repeats the entire process. I ran the unbrick.img and the problem persists.

    I'm currently in the process of running unbrick+recovery.img method to see if it makes any difference. Should it? Is there anything that I may be overlooking?

    I'm fairly sure that the reason this happened is from checking ALL the check boxes in the format/wipe section of the custom recovery. After that these issues happened. Does that mean permabrick?
    Click to expand...
    Click to collapse

    That's odd.... what do you mean it automatically starts trying to mount the partitions and fails? Where does TWRP show that? If you are getting the orange light it sounds like maybe you wiped your boot partition and it's not actually going to TWRP but stock recovery?

    Extract the boot.img from the prerooted ROM and place it in the directory with the unbrick files. Run handshake and reboot to get it to handshake, then run this:

    Code: 
    mediatek_inject firetv2 YOURCOMPORT boot.img /boot -

    Replacing YOURCOMPORT with whatever handshake said your comport was. That should rewrite the boot image.
    View
    2
    R
    rbox
    jim16127 said:
    When going into advanced wipe after running those 2 commands. I included an attachment with the error updates.

    UPDATE: So after reading "/dev/block/platform/mtk-msdc.0/by-name/cache is apparently in use by the system; will not make a filesystem here!" I figured I should try to wipe system. It worked! So then I tried to wipe data and cache. They both worked! I'm not sure if that means I'm home free but the errors are gone. I haven't rebooted yet though.
    Click to expand...
    Click to collapse

    Well try to reboot and see what happens.
    View
    2
    R
    rbox
    jim16127 said:
    After using your cache.img the FireTV booted to TeamWIN. I selected Advanced Wipe ticked the cache and data then clicked the swipe bar in the bottom right to start the process. The picture shown is what happened next. I was still in the boot menu though. So I did it again received the same errors and clicked reboot. It warned me that I don't have an OS. Now I'm in the same boot loop again.

    I'm currently running your cache.img to get out of the boot loop again.

    Any other ideas for me to try?
    Click to expand...
    Click to collapse

    Connect via adb shell and run these 2 commands:

    Code: 
    mke2fs /dev/block/platform/mtk-msdc.0/by-name/userdata
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
    View
    2
    R
    rbox
    jim16127 said:
    Okay, I followed those instructions. Here is the updated errors. They're similar but different.
    Click to expand...
    Click to collapse

    You're getting that after doing advanced wipe AND rebooting? That's not right...
    View

New posts