Help I think I bricked my J22 TV Dongle

[Teutonic]

So I'm brand new to this android TV dongle flashing scene and it would seem I bricked my device. Currently it has nothing displaying on the screen and when I turn it on, my windows 7 PC can't see it connected at all when I try to connect to it with the OTG usb cable. Here's what happened:

1. I downloaded the CX-919 4.4.2 Finless 2.0 Beta files.
2. Connected my J22 device to my windows 7 PC with the OTG usb cable.
3. PC recognized the device and I installed the drivers with no problems.
4. Opened the ROM Flash Tool 137 in the folder and it displayed at the bottom "Found RKAndroid Rock USB".
5. I then clicked the button "reboot to flash mode". It failed and did nothing. So as per the instructions in the readme file I ran RKBatchTool.exe.
6. Clicked on the "Switch" button and it rebooted the device into flash mode.
7. Next went back to Finless ROM Flash tool and clicked on "Erase NAND (IDB)". So far so good, it erased wit no problems.
8. Left all the options in the window as default, then clicked on "Flash Rom".
9. It started doing things and after about 10 seconds it threw an error "Error File Download".
10. So I clicked on Erase NAND (IDB) again to erase the partition and start again.
11. Clicked on Flash ROM again and it threw an error immediately "Error File Download (IDB)".

So then I started to panic and stupidly decided to try power cycling my J22. Now I am unable to get my Windows PC to see the device plugged into it. So am I out of luck and just bricked this device for good? Or do I have some options here to try?

Thank you for your time.

EDIT: So I guess I was slightly pre-mature on saying I couldn't get the J22 device to be recognized by windows. I found a youtube video where a guy shorted some pins on his hardbricked android device and was able to get it working again. So I thought what the hell? why not try it? It worked! I just used a paperclip to short out random pins on the nand flash chip until the blue light blinked. I then unplugged it, then plugged it back in and bam! windows recognized it again. So Now my question is, what did I do wrong before and how can I get the finless rom installed properly?

[NomenNescio]

Oeps... didn't make a backup of the stock rom?

[Teutonic]

Nope afraid not. Yep I'm an idiot lol (I wasn't really sure how to back it up though, I guess I didn't do enough research before hand). So Where I'm at right now is I got the device to be seen in windows and in the Finless ROM Flash tool, but when I try to flash an official ROM I downloaded from geekbuying.com for my model, it gives me an error "downloading IDB failed". I tried different mini USB cables. I tried connecting with the regular USB port, and i've tried using the RK Android tool and it gives the same error. At this point I'm at a loss. I hope there's something I'm just missing here, since it would really suck to have bricked my j22 permanantly 2 days after I received it lol.

[NomenNescio]

I still don't know how to make a (nandroid?) backup of the stock rom so no flashing for me yet.
In the stock rom there is a folder called cyxtech in sys so I think a stock rom has to work on our J22's.
Maybe you can get into the recovery the way used for tablets and phones? Found this on Geekbuying Blog:

Hello! I just wanted to share some information on how to uodate firmware on the mk908 WITHOUT a windows pc. You can dowoad the update zip and rename it update.zip and put it in the root directory of a microsd card. Put the card into the mk908′s microsd slot and power it on while holding the update button. After 20 seconds or so, the recovery menu will come up on the screen. You can install the new firmware from this menu. You will need a usb keyboard or a wireless keyboard receiver plugged into the standard usb port (not the otg!) to operate the mk908′s recovery menu. I downloaded the last update on my phone, and just used it’s microsd card to update the mk908. Didn’t even need a pc

[Teutonic]

Thank you for that post. I'm not really sure if it will work in my situation though as the whole nand flash drive was erased before trying to flash the rom. So I think the J22 is just an empty shell at the moment. I don't think it has a recovery partition to fall back on. I will definitely try this though as I don't really have anything else to try lol.

[Teutonic]

I fixed it! I was able to find the correct stock firmware for my device and restore it through RKAndroidTool version 1.6. I had to short pins 6 and 7 on the NAND flash chip while powering the device up and then I was able to do a restore with the stock firmware image. I then was able to install an older version of finless ROM that had android 4.2.2 on it. It booted up no problems. So I then decided to try finless ROM with android 4.4 beta and it bricked it. Got the stupid download IDB failed error message when flashing. I am not sure what's doing it, but it must be one of the files in the finless ROM it doesn't like, but I have no way of knowing that without trying to use a different file for each one individually through trial and error, which would take forever. So I think I'll stick with the stock firmware since it actually performs better than the older version of finless ROM I tried out. Antutu for older finless version: 16615 and antutu for stock rom: 16718. So not a huge difference, but still a difference. I really wish I could get finless rom 4.4 beta working though as I like the 4.4 OS better than 4.2.

[NomenNescio]

Do you have a link for the stock firmware? In case I brick mine

[Teutonic]

The stock ROM that worked for me was from Bluetimes for their BT919 (same as our model) which I got from this thread: http://www.freaktab.com/showthread.p...-dan-Vsync-Fix

Here is the direct link to the stock firmware with other tools for flashing from that thread: http://www.sendspace.com/pro/dl/7bzbci

Here is a link to a video for how to short the pins and flash the stock firmware with RK Android Tool (I had to use version 1.6 or 1.7, for some reason 1.5 wasn't detecting my device): http://www.youtube.com/watch?v=sSjaB522QJs

After recovering the device with the stock firmware, I installed the finless 1.6a ROM and then replaced the kernel with the vsync and oc kernels from the post I linked above. I am proud to say I can now view 1080p content from my plex server on this device with no drop in frames or stuttering.

Final thought: don't recommend trying to install finless 2.0 4.4.2 kitkat rom at this point in time. It bricks my device every time I try it and i'm forced to short the pins out and recover with the stock firmware to revive it.

[NomenNescio]

Congrats!
Did you install finless 1.6a ROM or 1.6b?

And to be sure your device had the same ROM and kernel version als mine?

[0on]

MANY thanks for the info Teutonic!
Had the same problem as you; Wanted to install Bob's Finless 2.0 beta rom. Faced the same (IDB) problems.
I had to shorten pins 7 and 8 to enter 'MASK ROM mode' (Motherboard info: CYXTECH_RK3188_909 V1_1).
I will test my device later this evening with this 'BT919_1123' firmware, will let you know how it went.

-update-

Stick booted, but rebooted when accessing browser. Will (stress)test later.

-update2-
Antutu score: 16845 (I think). The BT919_1123 firmware (Update_bt919_rk3188_dongle_ap6210_131123.img) has quite some apps preinstalled, bit annoying since I'm used to other versions of the apps hehe (especially XMBC; XBMC Xaf 12.2 build was preinstalled). Cheers.

[Max One]

MANY thanks for the info Teutonic!
Had the same problem as you; Wanted to install Bob's Finless 2.0 beta rom. Faced the same (IDB) problems.
I had to shorten pins 7 and 8 to enter 'MASK ROM mode' (Motherboard info: CYXTECH_RK3188_909 V1_1).
I will test my device later this evening with this 'BT919_1123' firmware, will let you know how it went.[ATTACH=CONFIG]5618[/ATTACH]

-update-

Stick booted, but rebooted when accessing browser. Will (stress)test later.

I have the same stick and had the same problems like u. These sticks wont work with bootloader 2.0x, it will brick ur device. Sadly we are alone with that problem. No1 knows why these new bootloader bricking our devices. This also means we are stuck at JB for now maybe forever.

Edit: No we are not stuck. Try to flash with androidtool v2.1 and ure able to flash KK. No more IDB flash problems.

[apop]

EDIT: So I guess I was slightly pre-mature on saying I couldn't get the J22 device to be recognized by windows. I found a youtube video where a guy shorted some pins on his hardbricked android device and was able to get it working again. So I thought what the hell? why not try it? It worked! I just used a paperclip to short out random pins on the nand flash chip until the blue light blinked. I then unplugged it, then plugged it back in and bam! windows recognized it again. So Now my question is, what did I do wrong before and how can I get the finless rom installed properly?

Hi, I am new, but obviosly very succesfull in "breaking" these sticks, i menage it in less then ten days . So having problem with conection to PC ( sais "it not USB mass storage ) i can' move on. CAN YOU PLEASE GIVE ME LINK ON YOU TUBE you mentioned. Thanks.