FireTV 2 (sloane) Unbrick Image

[CFKod]

Delete

 

[Lochy19]

Anybody has any update about this? It's really sad

 

[Sus_i]

I'm trying to get amazon to replace but they need the DSN.
Unfortunately I fit off ebay unboxed.

Anyone know how to find the DSN on a brick?

If you did an amazon login with this fireTV before, you can find the serial at the amazon website, take a look at your Account -> Digital Services and Device Support -> Manage Devices.

Since this box is most likely vulnerable to the amonet mtk exploid, a hardware unbrick/root solution should be possible, if someone with knowledge and time ports the 2gen FireTVStick root/unbrick solution... and a pad for the CLK line must be found too, don't know wether this pad is known. Maybe someone with a bricked box and a desolderd emmc can trace the clk emmc pad to a reachable pad, point or resistor at the board. With known pins for CLK, CMD, DAT0 etc, an emmc reader should work for unbricking too.

OK, maybe it's to much work (and offtopic, sorry), don't know

 

[CFKod]

If you did an amazon login with this fireTV before, you can find the serial at the amazon website, take a look at your Account -> Digital Services and Device Support -> Manage Devices.

Since this box is most likely vulnerable to the amonet mtk exploid, a hardware unbrick/root solution should be possible, if someone with knowledge and time ports the 2gen FireTVStick root/unbrick solution... and a pad for the CLK line must be found too, don't know wether this pad is known. Maybe someone with a bricked box and a desolderd emmc can trace the clk emmc pad to a reachable pad, point or resistor at the board. With known pins for CLK, CMD, DAT0 etc, an emmc reader should work for unbricking too.

OK, maybe it's to much work (and offtopic, sorry), don't know

Haha, well I'll be happy to send mine to someone.
I have a solder iron but no emnc or clue as to most of what you just mentioned lol

 

[diodanny]

My firetv2 has the same symptoms (no hdmi signal, slow flashing white light). I was on a pre-rooted build (5.2.1.1 then 5.2.4.0). I then tried to install 5.0.5, which is when everything got screwed up. Now no hdmi signal and I can't get to TWRP. I am working with the unbrick image, and recovery images. So far no luck in any combination. I will report back if I get it working, please also do the same.

i have the same problem

 

[tech3475]

Thanks for the image, I've sent a few bucks your way for saving me from my stupidity.

The only thing I might suggest is maybe adding to the first post maybe mentioning that those who originally used the USB A-A method and only used your images still have the old preboot and maybe include a script to reflash the boot partition (which was the issue in my case).

I know this is mentioned elsewhere in the forum (although I guessed it), but I could imagine someone missing this information.

 

[CFKod]

Thanks for the image, I've sent a few bucks your way for saving me from my stupidity.

The only thing I might suggest is maybe adding to the first post maybe mentioning that those who originally used the USB A-A method and only used your images still have the old preboot and maybe include a script to reflash the boot partition (which was the issue in my case).

I know this is mentioned elsewhere in the forum (although I guessed it), but I could imagine someone missing this information.

So I have a feeling I was initially stock 5.6.8 or 5.6.9
Used mtksu and in recovery flashed the pre rooted rom but upon flashing the system.img it crashed....

But because I now have the new preloader... It hangs when trying to flash anything at 0.00200000%

Can I not flash the boot.img which would have been on my fire tv 2?

 

[tech3475]

So I have a feeling I was initially stock 5.6.8 or 5.6.9
Used mtksu and in recovery flashed the pre rooted rom but upon flashing the system.img it crashed....

But because I now have the new preloader... It hangs when trying to flash anything at 0.00200000%

Can I not flash the boot.img which would have been on my fire tv 2?

I'm no expert, but probably not.

AFAIK the newer preloader blocks NAND access, at least for what 'we' want, so you wouldn't be able to write a new boot partition/downgrade the preloader.

 

[CFKod]

I'm no expert, but probably not.

AFAIK the newer preloader blocks NAND access, at least for what 'we' want, so you wouldn't be able to write a new boot partition/downgrade the preloader.

Amazon get kicks out of bricks, bunch of pricks. Why ??
I

 

[tech3475]

Amazon get kicks out of bricks, bunch of pricks. Why ??
I

Considering that they hate rooting to begin with, it's not too surprising.

What I don't get is why more companies don't include recovery modes since even OFW updates can cause bricks, similar to the iPhone or the 3DS/Switch.

 

[CFKod]

Considering that they hate rooting to begin with, it's not too surprising.

What I don't get is why more companies don't include recovery modes since even OFW updates can cause bricks, similar to the iPhone or the 3DS/Switch.

They are probably happy to just replace. No way will these be under warranty now.. I'll still see what they can do for me

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------

If you did an amazon login with this fireTV before, you can find the serial at the amazon website, take a look at your Account -> Digital Services and Device Support -> Manage Devices.

Yes got it from here. Cheers... Not sure what they will actually do for me... I'll see tomorrow

 

[bodomalo]

This thread is extrem longe to read, 22 pages

IS the solution from page 1 from 2016 still working?
Can someone unbrick a Fire TV box 2nd generation (its in a boot loope) - system is not changed, it just crashed and has a hdmi problem now (does not show anything, only the white amazon logo)

 

[mtidmarsh]

To help save my sanity, I wondered if someone may be able to confirm something for me and perhaps either stop me from wasting my time or point me in the right direction?

My (Sloane) rooted Fire TV 2 is no longer booting, it just freezes on the white Amazon logo and is unresponsive.
I have attempted numerous times to follow the steps in this post, but to no avail, despite trying on three different pc's.

When I run the 'unbrick_firetv2.bat' file, it just stops at "Waiting for preloader..."

I don't know whether this is because the FireTV doesn't have USB Debugging enabled (even though it hasn't booted that far) or if perhaps because the drivers are incorrect, or if it's just because it's totally goosed.
I am running Windows 10 and have installed the MT6577 drivers.
When I connect the Fire to the PC, it recognises is as MTP USB Device under 'Portable Devices' rather than either FireTV, or ADB device. Can someone tell me whether this is in fact the problem? (in MTP mode and not ADB) or should that work fine and it is another problem?

If I start the ADB server and look for devices, it doesn't find any.

I have tried to removing the MT6577 drivers and installing the Universal ADB driver but when I connect the Fire TV, it still shows up at MTP USB Device.

I'm going round in circles and not sure whether it's just driver related, or whether it really is the device and I just need to give in and get over it!

Thanks,
Matt

 

[tech3475]

To help save my sanity, I wondered if someone may be able to confirm something for me and perhaps either stop me from wasting my time or point me in the right direction?

My (Sloane) rooted Fire TV 2 is no longer booting, it just freezes on the white Amazon logo and is unresponsive.
I have attempted numerous times to follow the steps in this post, but to no avail, despite trying on three different pc's.

When I run the 'unbrick_firetv2.bat' file, it just stops at "Waiting for preloader..."

I don't know whether this is because the FireTV doesn't have USB Debugging enabled (even though it hasn't booted that far) or if perhaps because the drivers are incorrect, or if it's just because it's totally goosed.
I am running Windows 10 and have installed the MT6577 drivers.
When I connect the Fire to the PC, it recognises is as MTP USB Device under 'Portable Devices' rather than either FireTV, or ADB device. Can someone tell me whether this is in fact the problem? (in MTP mode and not ADB) or should that work fine and it is another problem?

If I start the ADB server and look for devices, it doesn't find any.

I have tried to removing the MT6577 drivers and installing the Universal ADB driver but when I connect the Fire TV, it still shows up at MTP USB Device.

I'm going round in circles and not sure whether it's just driver related, or whether it really is the device and I just need to give in and get over it!

Thanks,
Matt

The Preloader is completely different to ADB and runs before Android, so it wont matter.

To be clear you're running the bat file, plugged in the Fire TV via USB and only then turning on the Fire TV?

Also, bear in mind this will only work if you have an older versions of the preloader, in my case I originally hacked via the preloader method and only ever used rbox's ROMs.

 

[mtidmarsh]

The Preloader is completely different to ADB and runs before Android, so it wont matter.

To be clear you're running the bat file, plugged in the Fire TV via USB and only then turning on the Fire TV?

Also, bear in mind this will only work if you have an older versions of the preloader, in my case I originally hacked via the preloader method and only ever used rbox's ROMs.

Thanks for the quick response.
So the fact that I cannot connect via ADB is completely unrelated then as it wouldn't have got this far in the boot cycle...

Yes that's exactly the order I'm doing unfortunately.

Do you know whether there is anything else I can try, or an alternative method? (is there a working method for a later preloader in case this is the issue?)

Thanks,
Matt

 

[tech3475]

Thanks for the quick response.
So the fact that I cannot connect via ADB is completely unrelated then as it wouldn't have got this far in the boot cycle...

Yes that's exactly the order I'm doing unfortunately.

Do you know whether there is anything else I can try, or an alternative method? (is there a working method for a later preloader in case this is the issue?)

Thanks,
Matt

Reading earlier posts from when mine was semi-bricked, the error a newer preloader produces is that it wont write to NAND.

IIRC, if you successfully enter preloader mode you shouldn't see the Amazon logo.

Do you hear the 'connect' sound on your computer when you plug device into your computer and turn it on? Has the A-A cable worked with other devices?

AFAIK, the only other method is a hardmod which I think someone else posted on this site.

 

[mtidmarsh]

Reading earlier posts from when mine was semi-bricked, the error a newer preloader produces is that it wont write to NAND.

IIRC, if you successfully enter preloader mode you shouldn't see the Amazon logo.

Do you hear the 'connect' sound on your computer when you plug device into your computer and turn it on? Has the A-A cable worked with other devices?

AFAIK, the only other method is a hardmod which I think someone else posted on this site.

Yes I do hear the 'connect' sound from the computer when I turn on the Fire TV.
I think this the cable that I have successfully used previously (it's USB3 - that won't make any difference will it?)

I have just tried it on a laptop (same cable) and I have got slightly further (but not much!), I now get to this point:

Waiting for preloader...
Found port = COM4
Handshake complete!
Flashing unbrick image unbrick.img...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 0%

But it sits at 0% and doesn't progress. I have the lzma and recovery images on FAT32 formatted SDCard in the FireTV.

Not sure if the above proves anything more or gives anything else to try?

Thanks again for your help...
Matt

 

[tech3475]

Yes I do hear the 'connect' sound from the computer when I turn on the Fire TV.
I think this the cable that I have successfully used previously (it's USB3 - that won't make any difference will it?)

I have just tried it on my work laptop (same cable) and I have got slightly further (but not much!), I now get to this point:

Waiting for preloader...
Found port = COM4
Handshake complete!
Flashing unbrick image unbrick.img...
Mediatek Inject, git version fa8d8f
Locating the partition...
Reading 000000200: 0%

But it sits at 0% and doesn't progress. I have the lzma and recovery images on FAT32 formatted SDCard in the FireTV.

Not sure if the above proves anything more or gives anything else to try?

Thanks again for your help...
Matt

Try the slower method, but if that doesn't work then AFAIK it likely means you have the newer preloader which blocks this.

Unfortunately there's no other method I'm aware of besides a hardmod as of now.

 

[mtidmarsh]

Sorry, can you explain what the slower method is, or point me to a post?

 

[tech3475]

Sorry, can you explain what the slower method is, or point me to a post?

It’s where you use “unbrick+ramdisk.img”.