CX919 - 4.2.2 - Finless ROM 1.5

[DiSrUpTeR]

Re: NEW - CX919 - 4.2.2 - Finless ROM 1.5

I am working on it now. Maybe this week.

Bob

Nice will try not do disturb you

[paco2969]

NEW Finless 1.6 ROM ?

Any chance this one will have hulu + support right off the bat? I love the work you are doing but the universal hulu apk has terrible video quality. I do have XBMC 12.2 loaded on it but cant get it to work all it shows is ads. One other thing when I run a speed test I get around 30mbs but video buffers in XBMC all the time. I know that you are only working on the ROM but any insite would be appreciated. Last of all anyone get an Amazon instant video app to work on it yet?

Sorry for the Forum vomit, new to the mini pc world.

Thanks

[tucker973]

I am working on it now. Maybe this week.

I'm wondering if anyone can shed a little more light on why some CX919 devices don't work with the Finless ROM? Is this something that's likely to be fixed in upcoming versions, or is this device something I should write off and return to the manufacturer?

I appreciate all the time the devs put into this - I'm sure it's even more frustrating for them than it is for consumers when a device simply doesn't work even when, by all appearances, is exactly the same as other devices people have.

For the record, the only successful combination I've found for my device is the NEOMODE ROM and Sam321 kernel (but I have other issues with that - it's merely the only combo that will boot for me).

Unsuccessful combinations include (all @ 720p):
Finless w/ 2gb parameter, default 'simon' kernel
Finless w/ 4gb parameter, default 'simon' kernel
Finless w/ 2gb parameter, 'stock' kernel
Finless w/ 2gb parameter, 'jjh' 400mhz kernel
Finless w/ 2gb parameter, 'jjh' 800mhz kernel
Finless w/ 4gb parameter, 'jjh' 400mhz kernel
Finless w/ 4gb parameter, 'jjh' 800mhz kernel
NEOMODE with above kernels

Thanks again for all those putting time into this!

[edude]

I am working on it now. Maybe this week.

Bob

Will there be any USB touchscreen support with monitors like Dell 2314T? I hope so. So frustrating trying to get it to work and nothing works. Anyways great work and keep it up Bob

[peety]

Yep

I tried the other tool, and even downloaded version 1.7. I'm wondering if its because I'm using Win 8 x64 , is what's preventing me to reflash. I've tried everything, plugging in the ac port, plugging the normal usb port into my powered hub. Nothing.

When I open the alternate tool, I click on switch, or any button for that matter, everything fails.

Should I find a different OS? Any suggestions?

Yep. Most definate. Get on a different machine with another os. From what I have read. Win 8 is a issue. In your case with nothing showing. It may not be the problem. However, you have to try anything.

[tucker973]

Will there be any USB touchscreen support with monitors like Dell 2314T? I hope so. So frustrating trying to get it to work and nothing works. Anyways great work and keep it up Bob

edude, does the monitor have a USB-out port that you could plug into the full-sized USB port on the device? I would imagine the touchscreen monitor uses a basic HID profile that would work like a regular mouse on one of these. I'll confess I don't have much experience with touchscreen enabled monitors, though.

[spifey]

I respectfully disagree. I have a single-antenna Tronsmart CX919 purchased from GB fulfilled by Amazon. The Finless ROM with any of the supplied kernels does not work.

If you can't flash the cx-919 with Finless you will need to send it in for a replacement.
Or send it over to Finless and he can run some adb diagnostics on it to find out if maybe your boot loader stage b got corrupted. And to find out if the data is stored correctly or incorrectly. May want to consider offering him a small incentive to check it for you.

I'm thinking though during the flash process it hosed your page size somehow. May of been because of faulty drivers.

Not exactly sure if you have tried this or not. But it may be worth a try.

Feel free to swap your RK3188Loader with one that you know that works. And try to reflash it.
Uncheck everything but this.
These can be different sizes.
You never know. You might get lucky.

Also if you use the Rkflashtool post your log info. There may be something there that may shed the cause. (Might get lucky).

[tucker973]

If you can't flash the cx-919 with Finless you will need to send it in for a replacement.
Or send it over to Finless and he can run some adb diagnostics on it to find out if maybe your boot loader stage b got corrupted. And to find out if the data is stored correctly or incorrectly. May want to consider offering him a small incentive to check it for you.

I'm thinking though during the flash process it hosed your page size somehow. May of been because of faulty drivers.

I can get the device running just fine using the NEOMODE ROM and kernel from that package, but no other combinations work. The earlier version of that ROM was the first thing I actually got to run on my device, but this is the one I flashed today: http://www.freaktab.com/showthread.p...s-with-AP6210/

I haven't had much time with it tonight, but it's running. Again, I have to respectfully disagree with your assertion that all single-antenna Tronsmart CX919 devices should be able to run the current Finless 1.5 ROM. This is not the case, and it's apparent that my device is not bricked - I can flash the Finless and assorted kernels with no errors, yet no HDMI output. I can then flip back over to that other ROM/kernel and it works. Been doing this for a week now.

If there's something that will help identify my device specifics, I'd be happy to provide it as long as someone can tell me what to provide.

Thanks for the help, I'm eager to learn more about what's going on with these devices.

[spifey]

I can get the device running just fine using the NEOMODE ROM and kernel from that package, but no other combinations work. The earlier version of that ROM was the first thing I actually got to run on my device, but this is the one I flashed today: http://www.freaktab.com/showthread.p...s-with-AP6210/

I haven't had much time with it tonight, but it's running. Again, I have to respectfully disagree with your assertion that all single-antenna Tronsmart CX919 devices should be able to run the current Finless 1.5 ROM. This is not the case, and it's apparent that my device is not bricked - I can flash the Finless and assorted kernels with no errors, yet no HDMI output. I can then flip back over to that other ROM/kernel and it works. Been doing this for a week now.

If there's something that will help identify my device specifics, I'd be happy to provide it as long as someone can tell me what to provide.

Thanks for the help, I'm eager to learn more about what's going on with these devices.

It's ok to disagree with me. GB has the Finless ROM included in on there CX919 blog.
To me it means that it should work on any CX-919 devices. Including clones. And should be under the warranty if you can't flash Finless or one of there other official roms they have.

Can you use the Rkflashtool to flash the finless release and post your log file for me? A directory log should be created with a time stamp text file inside. They may still be there unless you deleted the directory.

Really the only way to tell your device specifics is to rip the device in pieces and take a picture of everything. But you better hold off on that. Will violate your warranty.

[tucker973]

It's ok to disagree with me. GB has the Finless ROM included in on there CX919 blog....
Can you use the Rkflashtool to flash the finless release and post your log file for me? A directory log should be created with a time stamp text file inside. They may still be there unless you deleted the directory.

I understand that their blog post points to Finless, but if you look around the forum, there are several people having the same issue. There is clearly a separate version floating around - again, my order was from GB, so it's not a clone. In the meantime, I'm attaching my log from yesterday that'll show a couple different attempts.

Log2013-10-14.txt

[Finless]

They may have used different NAND chips on the one you have. Rockchip updates the loader for different NAND chips.

In the Neo ROM what is the version of the loader? If it is a newer version than what is in my 1.5 ROM then try using the loader from Neo ROM with mine.

Bob

[spifey]

I understand that their blog post points to Finless, but if you look around the forum, there are several people having the same issue. There is clearly a separate version floating around - again, my order was from GB, so it's not a clone. In the meantime, I'm attaching my log from yesterday that'll show a couple different attempts.

[ATTACH]3578[/ATTACH]

Confirming what Finless stated.

Nand Manufacturers are different.
Mine states:

0        8192MB    HYNIX

Yours:

0        8192MB    MICRON

Back to my suggestion of you swapping the RK3188Loader(L)_V1.XX.

I'm crossing my fingers toes and elbows for you tucker.
"Com'on, work damn you!"

[tucker973]

They may have used different NAND chips on the one you have. Rockchip updates the loader for different NAND chips.

In the Neo ROM what is the version of the loader? If it is a newer version than what is in my 1.5 ROM then try using the loader from Neo ROM with mine.

Bob

Hi, Bob, thanks for chiming in, I know you're busy with bigger fish to fry than my issue. The loader is an older version (1.2). I gave it a shot with that loader for the heck of it with default settings, and still nothing. Went back to the Neo, and it worked.

[spifey]

Hi, Bob, thanks for chiming in, I know you're busy with bigger fish to fry than my issue. The loader is an older version (1.2). I gave it a shot with that loader for the heck of it with default settings, and still nothing. Went back to the Neo, and it worked.

Try this one tucker.

http://www.freak-tab.de/leolas/RK3188Loader(L)_V1.24.zip

[tucker973]

Try this one tucker.
http://www.freak-tab.de/leolas/RK318...r(L)_V1.24.zip

Looks like that's the same one that's packed with the Finless. Tried both that and the one from the Neo package (version 1.2). I'll try a few more combinations of kernels and Finless tonight when I get a chance. Thanks again for all the help on this! I'm slightly less frustrated because I'm at least getting a functional device when I run the latest Neo ROM (the earlier Neo was booting but far from satisfactory). Still, though, I'd like to have options. I'm also just curious about getting this working and finding out what the issue is, because I hate mysteries like this!