Looks like I've bricked it.

[rad]

Glad its been Sorted
And you have bricked the box by trying to Flash Square M8 Firmware is that right?

I'd never admit that but yes. Lol

The weird thing is the firmware I flashed had the same name except for the date part as tronsmart show in thier 'how to flash' instructions on thier tronsmart.eu website.

K200-ota-[insert date here].zip

Or to be honest I wouldn't have tried it.

Lesson learned though and hopefully my mistake will stop others from trying.

Big respect to Finless Bob for helping me fix it, I just wish he'd told me about the shorting of the pins earler :-) also I nicked some of his instructions when writting the how to guide.

Busting open the vega and shorting pins is not for the faint of heart so don't be tempted to flash other firmware folks, just wait for the guys that know what they are doing to give you the correct ones.

I hope finless gets sent new boxes for free as I suspect folk buy bits of kit based on knowing he makes roms for them, I know I do.

[Lokie]

I'd never admit that but yes. Lol

The weird thing is the firmware I flashed had the same name except for the date part as tronsmart show in thier 'how to flash' instructions on thier tronsmart.eu website.

K200-ota-[insert date here].zip

Or to be honest I wouldn't have tried it.

Lesson learned though and hopefully my mistake will stop others from trying.

Big respect to Finless Bob for helping me fix it, I just wish he'd told me about the shorting of the pins earler :-) also I nicked some of his instructions when writting the how to guide.

Busting open the vega and shorting pins is not for the faint of heart so don't be tempted to flash other firmware folks, just wait for the guys that know what they are doing to give you the correct ones.

I hope finless gets sent new boxes for free as I suspect folk buy bits of kit based on knowing he makes roms for them, I know I do.

You know rad... Thats how all great rom devs start off. You break it, you fix it, you Frankenstein it, break it, fix it.... Eventually if you put enough energy and time into it then you become a expert and completely invisible with the device. Just a pitty things change fast and soon there will be better hw and the focus changes. Been there in the past but got little time these days. Maybe when i'm retired one day this kind of thing can keep the brain busy... Or cause the odd stroke or heart attack lol.

[rad]

You know rad... Thats how all great rom devs start off. You break it, you fix it, you Frankenstein it, break it, fix it.... Eventually if you put enough energy and time into it then you become a expert and completely invisible with the device. Just a pitty things change fast and soon there will be better hw and the focus changes. Been there in the past but got little time these days. Maybe when i'm retired one day this kind of thing can keep the brain busy... Or cause the odd stroke or heart attack lol.

I hope you don't think I'm retired, also wish I had the time though :-)

[Lokie]

I hope you don't think I'm retired, also wish I had the time though :-)

Lol no i was talking about myself in 20years time. To keep myself bussy. To then Brick all kinds of devices and figuring out how to unbrick. Good food for the brain.

Hell just imagine retirees on this forum lol.

[rad]

Lol no i was talking about myself in 20years time. To keep myself bussy. To then Brick all kinds of devices and figuring out how to unbrick. Good food for the brain.

Hell just imagine retirees on this forum lol.

I'd made a few .zip files with a couple of the .img files missing, I was going to try to flash but keeping the 5g drivers there, I tried the one with all the files first, I guess that was a bad idea. lol

If I ever get the time I will suss this out but I'm a windows guy so used to files actually saying what they do inside them rather than all this gobildygoog that is inside .img files. I suspect it's much and such but I need the correct programs installed, I've downloaded the android toolkit now so I will have a look and see if it makes any sense, I maybe need to read a bit more though in future.

I can guess that the .wps file told windows that there was something on the end of the usb cable and that the u-boot.bin made the sd card bootable, I also imagine shorting the pins forced it to boot from the sd card but other than that I am lost.

Hey it's working now though so all is good, it won't put me off trying roms for the guys and reporting back though, especially now I know how to fix it.

[TMx]

I do hope They Release SDCARD only Firmware Zip like M8 Square boxes has... Its a lot easier to install and you can change the things and compile it !
I have tried to extract that .img file but no success

[geekbuying]

HI rad

i take a few mins to read all of your post. sorry to hear that you brick your device.

i will try to help solve it.

if i ask the factory to offer the sd card flash firmware, like the M8 squad box, would it help?

or what u-boot.bin you need me offer?

let me know.

Eric
GEEKBUYING

[rad]

HI rad

i take a few mins to read all of your post. sorry to hear that you brick your device.

i will try to help solve it.

if i ask the factory to offer the sd card flash firmware, like the M8 squad box, would it help?

or what u-boot.bin you need me offer?

let me know.

Eric
GEEKBUYING

Hi Eric,

It's ok, we got it fixed thanks.

[Finless]

Just remember, I was the first to hard brick! Imagine doing that and not having anything to fall back on and figuring it out myself, like what pins to short!!!!

I was panicked at the time let me tell you! Especially after getting into flash mode only to find the flash would fail! I thought for sure it was toast!

Bob

[rad]

Just remember, I was the first to hard brick! Imagine doing that and not having anything to fall back on and figuring it out myself, like what pins to short!!!!

I was panicked at the time let me tell you! Especially after getting into flash mode only to find the flash would fail! I thought for sure it was toast!

Bob

How did you know the pins Bob, was it just from previous experience ?

[Finless]

How did you know the pins Bob, was it just from previous experience ?

Yes this had the same NAND chip as my Jynxbox so I traced them back to the small chip on the back of the board. Much easier then trying to short the small pins on the NAND chip!

I will probably solder a switch there so I can unbrick easier as you know I will be trying other ROMs

Bob

[no_spam_for_me]

I will probably solder a switch there so I can unbrick easier as you know I will be trying other ROMs

TOP idea ...

[sistro]

I've bricked... damn... I follow your "guide" just to 6% but i can't do more.
Please Help me!

I don't know if I've done everithing ok, my questions are:

"Open your vega and short out the 2 pins in the link below" https://drive.google.com/file/d/0B9B...it?usp=sharing

Q.: Just during boot, until windows recognize the item? Or during all the process?

"Do a normal attempt at flashing the first time etc. etc."

Q.: I've to unplug the box and restart for each step? Or I've to close and restart the program? Which option I've to select In the "usb burning tool"?

"At this point you no longer need to short out the pins, you can remove the SD card and you can restart and flash as normal and it works"

Q.: So... what I've to do?



I've...
1. created the uSD CARD with the tool, copied the two files (u-boot.bin 352kb and usb刷机工具说明.wps), putted in the box

2. booted first time, with short on pin, reset button pushed, and power untile windows recognize the box, then I leave it all, tried to flash just to the error and then power down (Selected Erase Flash, Normal Erase, Erase Bootloader)

3. as above, force the erase (Selected Erase Flash, Force Erase, Erase Bootloader)

4. as above, unchecking erase bootloader (Selected Erase Flash, Normal Erase, Unckeck Erase Bootloader)

5.?!

[Finless]

Keep trying different combinations of erase. I had the same problem but through some combination eventually it got past 5% then 6% and so on.

Bob

[sistro]

Keep trying different combinations of erase. I had the same problem but through some combination eventually it got past 5% then 6% and so on.

Bob

Tnx... Now my Box have new life!

In the last try I've changed the version of rom image and of the USB Burning Tool:
I've use booth by Tronsmar (even If I've a beelink)
- Tool: USB_Burning_Tool_v2.0.0.140306_Alpha_x86
- Rom: S89_105k4_tronsmart

So to unbrick I can confirm that the process is:

I've...
1. created the uSD CARD with the tool, copied the two files (u-boot.bin 352kb and usb刷机工具说明.wps), putted in the box

2. booted first time, with short on pin, reset button pushed, and power until windows recognize the box, then I leave it all, tried to flash just to the error and then power down (Selected Erase Flash, Normal Erase, Erase Bootloader): You'll have a stop at about 3%, turn off the device.

3. as above, force the erase (Selected Erase Flash, Force Erase, Erase Bootloader): You'll have a stop at about 5%, turn off the device.

4. as above, unchecking erase bootloader (Selected Erase Flash, Normal Erase, Unckeck Erase Bootloader): You'll have a stop at about 6%, turn off the device.

5.Remove the uSD card, boot with reset + power until windows recognize the box, then I leave it all: flash your rom image with the usb burning tool.

Thanks very much to everyone, I hope this thing will help someone.
Finless I can I'll send you a PM (it's possible in this forum, right?)