yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] Sus_i:
Still waiting for the parcel with my sloane box ;)

Is that extra test you mentioned included in the new zip from OP?

Haven't looked into the scripts for now, unfortunately no time... but I see that the zip gets fatter :p

What do you think, since I don't know the serial, is it better to do some backups (i.e. backup mmcblk0boot1) before proceed with the unbrick?

---------- Post added at 10:09 AM ---------- Previous post was at 09:24 AM ----------

In case the recovery froze during install, don't unplug it, try to restart the recovery with adb shell

killall recovery
[Fire TV Original Android Development] Rortiz2:
The extra test is not included haha.

No worries. You can run it without problems.

Good to know that is almost there :)

Cheers!
[Fire TV Original Android Development] Rortiz2:
Weird. Here using the one that comes with box works.

What are you using to short?

Cheers.
[Fire TV Original Android Development] Sus_i:
The same like for the sticks, a small fine ESD tweezers. The short works almost every time. Maybe it's the cable, idk.

I'll try another laptop and see what happens

---------- Post added at 09:09 PM ---------- Previous post was at 08:44 PM ----------

Hmm, ok, I tried it with my new laptop, usb3.

Script runs much faster than on my old laptop, but as soon as the error occurs, that fcuking led on the fireTV starts flashing.

Please, be sure to copy the recovery ramdisk into an usb or sdcard and connect it into the TV
[2019-10-24 20:57:44.476160] Waiting for bootrom
[2019-10-24 20:57:54.535043] Found port = /dev/ttyACM0
[2019-10-24 20:57:54.535579] Handshake
[2019-10-24 20:57:54.536087] Disable watchdog

* * * Remove the short and press Enter * * *

[2019-10-24 20:57:56.323811] Init crypto engine
[2019-10-24 20:57:56.344895] Disable caches
[2019-10-24 20:57:56.345400] Disable bootrom range checks
[2019-10-24 20:57:56.360689] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2019-10-24 20:57:56.369132] Send payload
[2019-10-24 20:57:56.841999] Let's rock
[2019-10-24 20:57:56.842580] Wait for the payload to come online...
[2019-10-24 20:58:00.403622] all good
[2019-10-24 20:58:00.404192] Check GPT
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/serial/serialposix.py", line 537, in write
n = os.write(self.fd, d)
OSError: [Errno 19] No such device

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "main.py", line 134, in <module>
main()
File "main.py", line 68, in main
switch_user(dev)
File "main.py", line 34, in switch_user
block = dev.emmc_read(0)
File "/root/Desktop/amonet-mt8173-sloane/modules/common.py", line 179, in emmc_read
self.dev.write(p32_be(idx))
File "/usr/lib/python3.7/site-packages/serial/serialposix.py", line 571, in write
raise SerialException('write failed: {}'.format(e))
serial.serialutil.SerialException: write failed: [Errno 19] No such device

Need to find another usb cable for a test :)
[Fire TV Original Android Development] Rortiz2:
Yup, that happened to CFKod ;)

Other cable to short did the trick. Try with other usb cable too.

It's a weird error. You almost have it ;)

Cheers!
[Fire TV Original Android Development] DanielF50:
I spent a good hour or so just shorting, re-running that script & getting the same error only to find that my cable was a bit funky and if I moved it a little bit, it would work perfectly.

I didn't have another USB-A to USB-A so I had to keep trying, but it did finally work, so yeah, trying another cable should do it for you... if all else fails, I also found that hitting "enter" as quickly as possible made a little difference sometimes.

On the plus side, I now have 2 rooted Fire TV's :D
[Fire TV Original Android Development] Sus_i:
Thanks. :good: :D

Yeah, must be the cable... or maybe a loose usb port.

I'll try that again, maybe on weekend :good:
[Fire TV Original Android Development] genica:
* * * Remove the short and press Enter * * *

[2019-10-24 21:39:30.430102] Init crypto engine

[2019-10-24 21:39:30.455370] Disable caches

[2019-10-24 21:39:30.455985] Disable bootrom range checks

[2019-10-24 21:39:30.472444] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes

[2019-10-24 21:39:30.483216] Send payload

[2019-10-24 21:39:31.131266] Let's rock

[2019-10-24 21:39:31.132156] Wait for the payload to come online...

[2019-10-24 21:39:34.692430] all good

[2019-10-24 21:39:34.692931] Check GPT

[2019-10-24 21:39:35.963191] gpt_parsed = {'PRO_INFO': (1024, 254), 'NVRAM': (2048, 10240), 'TEE1': (12288, 10240), 'TEE2': (22528, 10240), 'lk': (32768, 2048), 'boot': (34816, 51200), 'recovery': (86016, 51200), 'KB': (137216, 2048), 'DKB': (139264, 2048), 'MISC': (141312, 1024), 'LOGO': (142336, 16384), 'EXPDB': (158720, 23296), 'system': (182016, 2477600), 'cache': (2659616, 512000), 'userdata': (3171616, 12098239), '': (0, 1)}

[2019-10-24 21:39:35.963439] Downgrade Preloader...

[319 / 319]

[2019-10-24 21:39:41.836529] Downgrade bootloader

[802 / 802]

[2019-10-24 21:39:54.861347] Reboot for continue with Preloader Stage

Start Preloader Stage in 3 seconds..

unbrick_firetv2.sh: 5: unbrick_firetv2.sh: [[: not found

unbrick_firetv2.sh: 7: unbrick_firetv2.sh: ./handshake.py: Permission denied

Flashing unbrick image...

cat: comport.txt: No such file or directory

unbrick_firetv2.sh: 10: unbrick_firetv2.sh: ./mediatek_inject.linux: Permission denied

Flash complete. Continue with bootrom-step.sh

Step 1 Complete. Unplug the TV and continue with bootrom-step.sh

Any thoughts on the problem?
[Fire TV Original Android Development] genica:
So I chmod 777 the files in the twrp folder and now getting this

* * * Remove the short and press Enter * * *

[2019-10-25 03:01:51.543919] Init crypto engine

[2019-10-25 03:01:51.569060] Disable caches

[2019-10-25 03:01:51.569699] Disable bootrom range checks

[2019-10-25 03:01:51.586333] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes

[2019-10-25 03:01:51.598054] Send payload

[2019-10-25 03:01:52.244285] Let's rock

[2019-10-25 03:01:52.245163] Wait for the payload to come online...

[2019-10-25 03:01:55.806094] all good

[2019-10-25 03:01:55.806532] Check GPT

[2019-10-25 03:01:57.080754] gpt_parsed = {'PRO_INFO': (1024, 254), 'NVRAM': (2048, 10240), 'TEE1': (12288, 10240), 'TEE2': (22528, 10240), 'lk': (32768, 2048), 'boot': (34816, 51200), 'recovery': (86016, 51200), 'KB': (137216, 2048), 'DKB': (139264, 2048), 'MISC': (141312, 1024), 'LOGO': (142336, 16384), 'EXPDB': (158720, 23296), 'system': (182016, 2477600), 'cache': (2659616, 512000), 'userdata': (3171616, 12098239), '': (0, 1)}

[2019-10-25 03:01:57.081022] Downgrade Preloader...

[319 / 319]

[2019-10-25 03:02:02.971199] Downgrade bootloader

[802 / 802]

[2019-10-25 03:02:16.053851] Reboot for continue with Preloader Stage

Start Preloader Stage in 3 seconds..

unbrick_firetv2.sh: 5: unbrick_firetv2.sh: [[: not found

Waiting for preloader...

Found port = /dev/ttyACM0

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in open

self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)

FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyACM0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "./handshake.py", line 89, in <module>

dev = serial.Serial(port, BAUD)

File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__

self.open()

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open

raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))

serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyACM0: [Errno 2] No such file or directory: '/dev/ttyACM0'

Flashing unbrick image...

cat: comport.txt: No such file or directory

Mediatek Inject, git version fa8d8f

error: ./mediatek_inject.linux <device> <comport> <source file> <target file> <selinux context>

Flash complete. Continue with bootrom-step.sh

Step 1 Complete. Unplug the TV and continue with bootrom-step.sh

Maybe different cables with do the trick
[Fire TV Original Android Development] Rortiz2:
Redownload amonet, I updated a few things. Also, don't chmod nothing.
[Fire TV Original Android Development] ForForkSake:
Does this work? I am free to give it a go tonight, as I've bricked mine again anyway... Twrp crashed during wipe system again.

. [MENTION=3991724]rbox[/MENTION] have you thought about newer twrp? :angel:
[Fire TV Original Android Development] Rortiz2:
lol the one in OP uses that method.

Regarding to TWRP you can clone pie repo and cherry-pick rbox's commits.

Cheers.
[Fire TV Original Android Development] ForForkSake:
Doh... Noted for next time

---------- Post added at 06:14 PM ---------- Previous post was at 06:00 PM ----------

Really? Might give it a go tonight
[Fire TV Original Android Development] ForForkSake:
❤️❤️ So easy
[Fire TV Original Android Development] genica:
It's frozen at waiting for preloader

sudo ./step-1.sh

Please, be sure to copy the recovery ramdisk into an usb or sdcard and connect it into the TV

[2019-10-25 22:05:44.679410] Waiting for bootrom

[2019-10-25 22:06:11.442966] Found port = /dev/ttyACM0

[2019-10-25 22:06:11.443705] Handshake

[2019-10-25 22:06:11.444498] Disable watchdog

* * * Remove the short and press Enter * * *

[2019-10-25 22:06:18.224701] Init crypto engine

[2019-10-25 22:06:18.250356] Disable caches

[2019-10-25 22:06:18.251171] Disable bootrom range checks

[2019-10-25 22:06:18.266291] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes

[2019-10-25 22:06:18.277017] Send payload

[2019-10-25 22:06:18.925480] Let's rock

[2019-10-25 22:06:18.926323] Wait for the payload to come online...

[2019-10-25 22:06:22.532254] all good

[2019-10-25 22:06:22.532708] Check GPT

[2019-10-25 22:06:23.821013] gpt_parsed = {'PRO_INFO': (1024, 254), 'NVRAM': (2048, 10240), 'TEE1': (12288, 10240), 'TEE2': (22528, 10240), 'lk': (32768, 2048), 'boot': (34816, 51200), 'recovery': (86016, 51200), 'KB': (137216, 2048), 'DKB': (139264, 2048), 'MISC': (141312, 1024), 'LOGO': (142336, 16384), 'EXPDB': (158720, 23296), 'system': (182016, 2477600), 'cache': (2659616, 512000), 'userdata': (3171616, 12098239), '': (0, 1)}

[2019-10-25 22:06:23.821300] Downgrade Preloader...

[319 / 319]

[2019-10-25 22:06:29.733927] Downgrade bootloader

[802 / 802]

[2019-10-25 22:06:42.851000] Reboot for continue with Preloader Stage

Start Preloader Stage in 5 seconds..

Waiting for preloader...

When I unplug it and plug it back in I get this

Found port = /dev/ttyACM0

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in open

self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)

FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyACM0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "./handshake.py", line 89, in <module>

dev = serial.Serial(port, BAUD)

File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__

self.open()

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open

raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))

serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyACM0: [Errno 2] No such file or directory: '/dev/ttyACM0'

Flashing unbrick image...

cat: comport.txt: No such file or directory

Mediatek Inject, git version fa8d8f

error: ./mediatek_inject.linux <device> <comport> <source file> <target file> <selinux context>

Flash complete. Continue with bootrom-step.sh

Step 1 Complete. Unplug the TV and continue with bootrom-step.sh
[Fire TV Original Android Development] genica:
It was the os because it's now running rbox debrick script. Maybe add a second reboot for the "waiting for preloader" may work better for slow computers. Just a suggestion

---------- Post added 26-10-2019 at 12:15 AM ---------- Previous post was 25-10-2019 at 11:51 PM ----------

So is it not possible to flash the system partition while in download mode? I'm just thinking it would be faster and you can skip preloader mode all together
[Fire TV Original Android Development] Rortiz2:
You can. But will take days :))

Cheers.
[Fire TV Original Android Development] DanielF50:
Just curious - if switched out the files in /bin for 5.0.5 files exclusively, you think 5.0.5 pre-rooted would boot? I'm just trying to figure out a way to get more space in /system so that I can flash most of tvstock gapps & cba with resizing partitions with gparted :p
[Fire TV Original Android Development] Rortiz2:
Not a good idea... RPMB stills here and checks for versions... If you flash 5.0.5 files the device will refuse to boot..

Cheers.
[Fire TV Original Android Development] genica:
So I flashed the debricked+ramdisk and it still won't boot into twrp. It's just stuck at the Amazon white logo. I've tried both .img files and it flashed without errors. Any suggestions?
[Fire TV Original Android Development] DanielF50:
Ah, so around 5.2.6.8 would be the earliest you could go to?
[Fire TV Original Android Development] Rortiz2:
Yeah and you put the ramdisk in a USB/Sdcard?
[Fire TV Original Android Development] genica:
I have ramdisk-recovery.cpio.lzma on the sdcard
[Fire TV Original Android Development] Rortiz2:
Did you flashed boot.img?
[Fire TV Original Android Development] -KampfGurke-:
Can i downgrade and root a FireTV2 which is on 5.7.2.1 with that method?
[Fire TV Original Android Development] Rortiz2:
This method installs TWRP and then you can flash a prerooted ROM so yep. Will Root it.
[Fire TV Original Android Development] genica:
Yes sir, I may need to wait for a full bootloader unlock to come around to recover this thing
[Fire TV Original Android Development] Rortiz2:
No. This is weird. If you get Amazon Logo you can still unbrick it.. what format does have the Sdcard/USB?
[Fire TV Original Android Development] genica:
Fat32
[Fire TV Original Android Development] Rortiz2:
I assume the ramdisk is in the root directory no?

Cheers.
[Fire TV Original Android Development] genica:
Yes, but I flashed the unbrick+ramdisk image. It should've worked regardless
[Fire TV Original Android Development] Rortiz2:
Can you msg me in telegram or discord?

I have some tests to do;)

Cheers!
[Fire TV Original Android Development] genica:
Yeah, message me on discord
[Fire TV Original Android Development] toybits:
I am getting this error please help...

joseph@joseph-IdeaPad-U430-Touch:~/Desktop/amonet-mt8173-sloane$ sudo ./step-1.sh

Please, be sure to copy the recovery ramdisk into an usb or sdcard and connect it into the TV

[2019-10-26 23:42:13.184055] Waiting for bootrom

[2019-10-26 23:42:34.810430] Found port = /dev/ttyACM0

[2019-10-26 23:42:34.810920] Handshake

[2019-10-26 23:42:34.811522] Disable watchdog

* * * Remove the short and press Enter * * *

[2019-10-26 23:42:42.168422] Init crypto engine

[2019-10-26 23:42:42.188076] Disable caches

[2019-10-26 23:42:42.188472] Disable bootrom range checks

[2019-10-26 23:42:42.204384] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes

[2019-10-26 23:42:42.206936] Send payload

[2019-10-26 23:42:42.736235] Let's rock

[2019-10-26 23:42:42.736912] Wait for the payload to come online...

[2019-10-26 23:42:46.297585] all good

[2019-10-26 23:42:46.297819] Check GPT

[2019-10-26 23:42:47.565756] gpt_parsed = {'PRO_INFO': (1024, 254), 'NVRAM': (2048, 10240), 'TEE1': (12288, 10240), 'TEE2': (22528, 10240), 'lk': (32768, 2048), 'boot': (34816, 51200), 'recovery': (86016, 51200), 'KB': (137216, 2048), 'DKB': (139264, 2048), 'MISC': (141312, 1024), 'LOGO': (142336, 16384), 'EXPDB': (158720, 23296), 'system': (182016, 2477600), 'cache': (2659616, 512000), 'userdata': (3171616, 12098239), '': (0, 1)}

[2019-10-26 23:42:47.565919] Downgrade Preloader...

Traceback (most recent call last):

File "main.py", line 134, in <module>

main()

File "main.py", line 80, in main

flash_binary(dev, "../bin/preloader_old.img", 0)

File "main.py", line 29, in flash_binary

dev.emmc_write(start_block + x, data[x * 0x200:(x + 1) * 0x200])

File "/home/joseph/Desktop/amonet-mt8173-sloane/modules/common.py", line 202, in emmc_write

raise RuntimeError("device failure")

RuntimeError: device failure
[Fire TV Original Android Development] Rortiz2:
That error means that there's bad comunication with the box and the PC. Use a different cable or port.

Cheers.
[Fire TV Original Android Development] Rortiz2:
[MENTION=5213625]Sus_i[/MENTION] did you managed to get it working?

If you still have problems I have an easier method to try. My goal is flash unbrick.img with bootrom-step.sh since it's like 1,4MB ;)

Cheers!
[Fire TV Original Android Development] Sus_i:
Unfortunately I had no time this weekend. Maybe I start tomorrow an attempt... :good:
[Fire TV Original Android Development] Rortiz2:
Ok no problem :)

If you want to try the "new" method that does all in one step and doesn't require downgrade:

https://mega.nz/#!W1tmBYBK!WzbDamY73k1r4SCcyRf6AUIJhYKamsimNnkVO1G-Bsw

Cheers!
[Fire TV Original Android Development] toybits:
Can i use this new version to unbrick my fire tv 2? Or is this a different one? Thanks. Btw when you say try a different cable do you mean usb cable or material for shorting?
[Fire TV Original Android Development] Rortiz2:
Yeah try this version.

I mean the cable for connect it. But better to change ports first. Be sure to use a 2.0 one.

Cheers!
[Fire TV Original Android Development] toybits:
I will try this new version. But I need the step-1.sh from the old one right? How will the command be? sorry new to this kinds of things. Thanks again
[Fire TV Original Android Development] Rortiz2:
No need of step-1.sh.

Just run:

sudo ./bootrom-step.sh

and connect the device.

Cheers!
[Fire TV Original Android Development] toybits:
I get stuck with downgrade preloader (2/319) then error. I tried 3 different cables and used 3 different PC on both usb 2.0 and usb 3.0, but still get the same error. Can it be my fire tv is really done and fried? Or as long as it responds with the shorting it still can be unbricked. I will buy a new usba to usba cable. Thanks.
[Fire TV Original Android Development] genica:
The new script ran perfectly fine without any errors. However, it's still stuck at the Amazon logo. I don't know what's up with damn this thing
[Fire TV Original Android Development] Rortiz2:
This is very weird... How you bricked it last time?

It was stuck at flash system?

Cheers!
[Fire TV Original Android Development] Sus_i:
Thank you. :good:

I've tried the new and the old package, but my box always boots just a few seconds after releasing the short, regardless how fast I press enter... same behavior if I don't press enter.

I'm going to buy a new usb cable...

Edit: Seems that my box (i.e. the bootrom) doesn't receive the start command, which prevent any booting from flash.
[Fire TV Original Android Development] genica:
It froze halfway flashing the system. The debricked image hasn't worked since. What about reformatting the system partition?
[Fire TV Original Android Development] mattress:
Hey all ... complete newbie here. Stuck on white amazon logo bootloop. Here's what I've done:

I've had a rooted FireTV2 since kingroot or whatever was the big thing. rooted, and installed twrp and never did anything except watch netflex until yesterday. I think somehow it tried to update itself, and I came home to no display, and a slowly fading on/off white light.

well ... I spent most of today learning everything I could about this thing ... took it apart, shorted pins, ran Ubuntu live, did all the steps, was able to boot into TWRP recovery again, and I through the latest pre-rooted stock image on the sd card and tried to flash it. at first, I was having the "no cache" problem, so I shared internet over ethernet to the thing, and was able to run adb commands to it to fix that part. I flashed the image, wiped cache, and have tried everything I can, but I'm stuck with a white amazon logo on the screen for around 30 seconds before rebooting. over and over. Any ideas guys? I don't know what to do next...
[Fire TV Original Android Development] Rortiz2:
Weird... Does it boots as Preloader Mode of you don't short?

Tried with that new cable?

Cheers!
[Fire TV Original Android Development] Rortiz2:
You wiped all the partitions? Cache/system/data?

Also be sure that the prerooted ROM that you're flashing lis the latest.
[Fire TV Original Android Development] Rortiz2:
Updated OP with easier method.
[Fire TV Original Android Development] Sus_i:
Yeah, after shorting the script finds the bootrom, tells to remove the short... I release the short and press enter, then three to seven seconds and the box boots. It's always the same, also if I don't press enter...

I assume the handshake with the bootrom didn't work (maybe the cable?) and the box boots the preloader.

Haven't tried a new cable, I'll do that soon, but have to buy one first ;)
[Fire TV Original Android Development] Rortiz2:
Yup, I think it's the cable then...

Cheers!
[Fire TV Original Android Development] brick00444:
Thank you for any help and thank you for all you have done. After several tries I was able to get through the flashing and it will boot to the screen that wants to pair a remote. It is stuck on the screen that asks for remote. When I try to pair a remote the light flashes on the box but stays on the looking for remote screen. I have tried using a different remote that has a usb dongle without any luck also. Do you have any ideas on how to fix this problem? Maybe a way to bypass that screen?
[Fire TV Original Android Development] Rortiz2:
You have two options:

Restore a backup from another person that already done the Setup Wizard

Enable ADB tought recovery, and disable SetupWizard.

Cheers!
[Fire TV Original Android Development] brick00444:
How do I enable ADB through recovery? I also have a working box. Do I just do a backup of the good one and then flash that backup from TWRP?
[Fire TV Original Android Development] Rortiz2:
Yeah backup option is probably better then.

Cheers!
[Fire TV Original Android Development] DanielF50:
Have you tried holding down the "Home" button for 10 seconds, right next to the box, then again, and again until it finds it? Normally works for me after a few attempts (and/or a battery change).
[Fire TV Original Android Development] brick00444:
Got it going after reflashing again. I did try to connect a few times then connected. Thanks! now have another working box.
[Fire TV Original Android Development] DanielF50:
Great news! :D
[Fire TV Original Android Development] brick00444:
Just want to THANK the people that help us underlings get by. THANK YOU VERY MUCH!
[Fire TV Original Android Development] toybits:
My fire tv stopped working recently and stopped booting. At first it was on bootloop. Then it slowly just boots to amazon logo then shut down. Then it slowly stopped show any signs of life as it barely turns on. So i tried the unbricking method but always get stuck with downgrade preloader 2/319 and error. So I tried two new usba cable from amazon but still getting stuck with download preloader. Does anyone experience this when trying to unbrick? Will appreciate any help. Im thinking my fire tv has a permanent damage with its chip because on how it slowly died and cannot get past preloader stage with unbricking.
[Fire TV Original Android Development] Sus_i:
or maybe the power brick dies...
[Fire TV Original Android Development] Rortiz2:
It's pretty weird.

Did you have any luck?

Enviado desde mi WAS-LX1A mediante Tapatalk
[Fire TV Original Android Development] toybits:
But why does it still respond when I short it if the power brick is dead? Is it possible to still short it even there is no current coming in the board? Thanks
[Fire TV Original Android Development] Sus_i:
Maybe it's a bit weak and/or unstable, not completely dead.

If you short the pin (and the CPU doesn't boot), it needs not much power.

It's only a supposition, idk.

[MENTION=8978978]Rortiz2[/MENTION] No, I'm waiting, cable isn't arrived...