MK902 - KitKat 4.4 - SMIC717394 Rom V1

[Are G. Bee]

Yes you did . (Good link) i will steal those when ever you post them and not feel bad lol . i didnt use any of those files i installed the drivers and then windows still didnt see device. I checked device manager it showed as yellow so clicked on it said permissions issue, clicked on update driver from windows update. then re booted. Loaded mk902 selected connect to pc in device manager. this time it asked me to connect as mass storage did so checked windows its there working and had access from windows opened files transfered so all working in windows, box not so much, ill load mount to see if that resolved tonight and post screens for the others.

I was up late and tried so many different things to get the drivers in installed so who knows i may have missed a step ( Totally understand others frustrations with this issue now after going through it myself so also followed up with emails to see if proper windows 8 drivers can be made up>)


will try and mount drive in xbmc tonight and see what happens then.


later.

I'm not sure if I get you? :P are you saying that it works as a mass storage device on Windows but it isn't mounting on the MK902 locally?

If so, one thing to note was that using mount -t ntfs or ntfs-3g does not work. You need to initiate the mount using ntfs-3g as the command, something like: ntfs-3g -o rw /dev/block/sda1 /mnt/usb_storage/USB_DISK0/Media

With regards to adb, I can get it to show up only in TWRP, but without system being able to mount I'm not sure how to get the Superuser.apk into /system/app?

[scooter2014]

ok Connected and root installed and i re did root because of the driver issue just to make sure not screwed i think ill install your cwm (what ver is it?) and once thats installed start ntfs. ( I powered down system a few times ) just to make sure that i didnt lose the driver again and each time re loaded to connect to pc works every time now.

easiest way to get superuser is just root with kinko android root installs it and works pretty flawlessly.

[scooter2014]

OK ALL STILL GOOD AFTER ROOT

http://www.filefactory.com/file/6ye5dqdgxnml/com.arctablet.arctools.apk

Did cwm with arctool worked fine.

[Are G. Bee]

[ATTACH=CONFIG]6322[/ATTACH][ATTACH=CONFIG]6323[/ATTACH]
OK ALL STILL GOOD AFTER ROOT

http://www.filefactory.com/file/6ye5dqdgxnml/com.arctablet.arctools.apk

Did cwm with arctool worked fine.

Good to hear. Ya I was able to get it working at 1080p on my Samsung Smart, but because of the compat issue with my Toshiba I was unable to see anything when I switched over. Instead I used an alternate version from leolas which appears to be 720p by default. Given that the CWM interface is text-based, I doubt I'll be missing much quality...and at least if at any point I get stuck with a 720p-only TV I'll still have a hope! The version on it is v6.0.3.1...

With regards to the drivers, I think I give up! There really is no explanation why they install fine and show as working, but still not detect the device when running 'adb devices'? Maybe I'll try mounting /system in ubuntu instead and toss in the root files that way..?

Bu that's all for another day. For now I'm back to 4.2 V2 so I can get to my drive in the meantime

[scooter2014]

Instruction of connect Win8 PC with RIKOMAGIC device

When you download firmware from www.rikomagic.com, you can operate as below instruction if your pc is Win8 and it cannot detect rikomagic device,FYI:

1.Driver signature verification should be disabled at first (Restart by pressing the shift key when restarting and select advanced options and, when it has restarted, please press F7 or 7 key)
2.Install driver:driver fileà Driver Install. Exeà right button àinstall
3.Connect the device in flash mode
4.Windows will tell you there is problem with device
5.In devices manager check the usb hub at which it is connected (for each hub, right button, properties, energy manager),and then disable that usb hub ,device will be installed now.
6.Add the parameter SUPPORTLOWUSB=true at the config.ini file which in batch tool (once opened with a text reader it easy to see where to add,it’s after 38 line if you cannot find in config.ini file)
7.Restart the batch tool, the device is recognized but the upgrade process will take a little more time.







Thanks to Michelle from Ricomagic.

[Are G. Bee]

Instruction of connect Win8 PC with RIKOMAGIC device

When you download firmware from www.rikomagic.com, you can operate as below instruction if your pc is Win8 and it cannot detect rikomagic device,FYI:

1.Driver signature verification should be disabled at first (Restart by pressing the shift key when restarting and select advanced options and, when it has restarted, please press F7 or 7 key)
2.Install driver:driver fileà Driver Install. Exeà right button àinstall
3.Connect the device in flash mode
4.Windows will tell you there is problem with device
5.In devices manager check the usb hub at which it is connected (for each hub, right button, properties, energy manager),and then disable that usb hub ,device will be installed now.
6.Add the parameter SUPPORTLOWUSB=true at the config.ini file which in batch tool (once opened with a text reader it easy to see where to add,it’s after 38 line if you cannot find in config.ini file)
7.Restart the batch tool, the device is recognized but the upgrade process will take a little more time.

Thanks to Michelle from Ricomagic.

Thanks for the added information, although some of what is stated doesn't quite match up to what I see in Windows 8.1 x64?

If I'm remembering correctly, there are a few more options to click during step 1 that are missing from the process. I believe step 2 is meant to say "right-click 'DriverInstall.exe' and select 'Run as Administrator'"? Also in step 5 I was unable to find a tab under the hub properties named "Energy Manager"...although I did find a tab named "Power" where you will find a section "Attached devices", and the correct hub should say "Rockusb Device" under the Description column. Under step 6 I will assume by batch tool you mean the 'RKAndroidTool.exe' accompanying this release? If so, it does not appear to have a 'config.ini' file included as specified. There is however a 'config.cfg' file, but it appears to be encoded and does not clearly show where the ini-style line above should go? My assumption would be that the 'SUPPORTLOWUSB=true' actually belongs in the provided 'settings.ini' file? Also with regards to step 6, if I were to place it at line 38 of the 'settings.ini' file it would fall under the [RAM] section at the end, which seems a bit odd for a USB option? I would have expected it to be under the [SYSTEM] section, maybe under 'SUPPORTUSB11=1'?

For my own situation, I have already tried all of the above steps except 5-7. Step 5 doesn't seem relevant to me as I never had any real issues getting the device to be recognized in the first place. My only issue is with the adb command not seeing the MK902 when I run 'adb devices', or 'adb usb'? As I haven't tried adding the 'SUPPORTLOWUSB=true' line to the ini file yet so I will give that one a go, but I'm a bit skeptical as the file seems to be exclusive to flash tool and not adb directly.

thanks for the added information though

[scooter2014]

[QUOTE=Are G. Bee;171171]Good to hear. Ya I was able to get it working at 1080p on my Samsung Smart, but because of the compat issue with my Toshiba I was unable to see anything when I switched over. Instead I used an alternate version from leolas which appears to be 720p by default. Given that the CWM interface is text-based, I doubt I'll be missing much quality...and at least if at any point I get stuck with a 720p-only TV I'll still have a hope! The version on it is v6.0.3.1...

With regards to the drivers, I think I give up! There really is no explanation why they install fine and show as working, but still not detect the device when running 'adb devices'? Maybe I'll try mounting /system in ubuntu instead and toss in the root files that way..?

Bu that's all for another day. For now I'm back to 4.2 V2 so I can get to my drive in the meantime [/QUOT


As per above, I got installed so i have access to root, I posted that mines rooted now with the program listed. (simple root program worked well) I have drive access in both windows and mk902 now. once i load my files ill test video. The statement is for the batch tool 1.7 not for rkandriod tool,

i took it you could not get root as stated above . i have root everything above worked and used program above to get root (kinko)

for item 5- read here. http://blogs.msdn.com/b/usbcoreblog/...commentmessage
(my comment for this to manufacture is a normal person would expect drivers to install and work in the most current operating system wouldnt they? Maybe a window 8.1 update driver install program or even better certified driver;>
6- I did not use the work around for the rkandriodtool. ( i dont use batch tool.) Mine flashed just fine and now i can see in xbmc and will post once finished (other things more important to me tonight as honey home lol.

[Are G. Bee]

Good to hear. Ya I was able to get it working at 1080p on my Samsung Smart, but because of the compat issue with my Toshiba I was unable to see anything when I switched over. Instead I used an alternate version from leolas which appears to be 720p by default. Given that the CWM interface is text-based, I doubt I'll be missing much quality...and at least if at any point I get stuck with a 720p-only TV I'll still have a hope! The version on it is v6.0.3.1...

With regards to the drivers, I think I give up! There really is no explanation why they install fine and show as working, but still not detect the device when running 'adb devices'? Maybe I'll try mounting /system in ubuntu instead and toss in the root files that way..?

Bu that's all for another day. For now I'm back to 4.2 V2 so I can get to my drive in the meantime

As per above, I got installed so i have access to root, I posted that mines rooted now with the program listed. (simple root program worked well) I have drive access in both windows and mk902 now. once i load my files ill test video. The statement is for the batch tool 1.7 not for rkandriod tool,

i took it you could not get root as stated above . i have root everything above worked and used program above to get root (kinko)

for item 5- read here. http://blogs.msdn.com/b/usbcoreblog/...commentmessage
(my comment for this to manufacture is a normal person would expect drivers to install and work in the most current operating system wouldnt they? Maybe a window 8.1 update driver install program or even better certified driver;>
6- I did not use the work around for the rkandriodtool. ( i dont use batch tool.) Mine flashed just fine and now i can see in xbmc and will post once finished (other things more important to me tonight as honey home lol.

Root is a no-go so far, I cannot do anything to it without adb detecting my device. None of the available tools like you suggested would even work because they all rely on it.

What's strange is that now that I am back to 4.2, I am still unable to use adb..? When testing out other roms I was able to root it before so I really don't have a clue what's going on now?

[hencke]

What's strange is that now that I am back to 4.2, I am still unable to use adb..? When testing out other roms I was able to root it before so I really don't have a clue what's going on now?

Try checking C:\Users\[Username]\ if there is an .android-folder. If there is one, that's where you want your modified adb_usb.ini. I attached my pre-modified one (just added 0x2207 to it so adb finds the device). Doing this I got adb to work even on the 4.4 ROM.

[smic717394]

I´m updating the rom to a V2_BETA, cleaned up a bit the rom, and rooted the rom using the ini.rc to ensure you dont loose the root by using other init.d scripts.

Its uploading now. I will post the link in 20 min

[smic717394]

This is the second version of the rom, still Beta, still allot of work. Whats new:

1.ROOT: Android 4.4.2 requires SU to run as a daemon now. Normal root is to run a script via the init.d, but in 4.4.2 means you loose root if messing with these scripts and some rooted apps will do. To prevent this from happening i started the daemon from the init.rc so there is no need to run scripts at boot.

2.Debloat: Remove as much junk as possible to create more space for apps and for faster boot.

3. init.d support: Added full init.d support so you can run your scripts.

4. Build.prop: Optimized Build.prop for better networking and video playback.

5. Kernel OC: Kernels are the same OC to 1.6, 1.7 (default) and 1.8. There is a new 1.6NOC version without the vsynk fix.

6.Wallpaper: Replaced the default wallpaper. I hope you guys like it.

7. Reboot: Fix the reboot app.




http://www.mediafire.com/download/96w06byh349lcs5/4.4_smic717495_V2.rar


I hope you enjoy it as much as I did preparing this rom. Thank you all.

Spacial Thank you to Petrus, 900supersport and scooter2014 for their support.

[scooter2014]

Great work on the root, Ill download later today and test , going to be hard to flash over the old one so says alot Smic Great running rom so far.

[INFIN1TY]

Thanks. Ill download it later and flash it when i got time for it.

[ynot123]

This is the second version of the rom, still Beta, still allot of work. Whats new:

1.ROOT: Android 4.4.2 requires SU to run as a daemon now. Normal root is to run a script via the init.d, but in 4.4.2 means you loose root if messing with these scripts and some rooted apps will do. To prevent this from happening i started the daemon from the init.rc so there is no need to run scripts at boot.

2.Debloat: Remove as much junk as possible to create more space for apps and for faster boot.

3. init.d support: Added full init.d support so you can run your scripts.

4. Build.prop: Optimized Build.prop for better networking and video playback.

5. Kernel OC: Kernels are the same OC to 1.6, 1.7 (default) and 1.8. There is a new 1.6NOC version without the vsynk fix.

6.Wallpaper: Replaced the default wallpaper. I hope you guys like it.

7. Reboot: Fix the reboot app.




http://www.mediafire.com/download/96w06byh349lcs5/4.4_smic717495_V2.rar


I hope you enjoy it as much as I did preparing this rom. Thank you all.

Spacial Thank you to Petrus, 900supersport and scooter2014 for their support.

Running it now on a MK802IV with d33 kernel kernel_kk_4.0_NOGPU_DRR.img (HD kernel at 1.6GHz, no ddr or GPU O/C, prevents double vision https://www.freak-tab.de/d33/kernel_...00_testers.zip ). Seems to be running well. Sound good, video good, antutu 17500, full 1080P on XBMC gotham beta 4 and MX Player. Not bad for a pretty crappy board. Keep up the good work.

[smic717394]

Thanks. on the MK902 I get over 19000

Sent from my GT-I9300 using Tapatalk