Forum switched to read-only as of 2020/06/01
|Latest product reviews|
I have an issue with my new minix neo x7 which goes something like this....
It came with v008 minix official rom and i thought I have a go a flashing a different image. I am using rkflashkit/ubuntu. I downloaded the "kasty-minix_neo_x7-422-20140101_008-rooted4" (else where in forum), ran rkflashkit, put the minix in flash mode. rkflashkit recognised the device, I selected the (unzipped) img file and 'System' as my target partition and hit flash.
The procedure appeared to work, first the download, then the verify. However, on restart, the device never get past the minix boot logo.
something must have worked though as i can now access the cwm recovery system (v4.2.01) if i try to put the x7 into flash mode (recovery button and power on). however, i can not get the device past the boot logo.
I downloaded the 008 official rom and reflashed using rkflashkit (system partition again) and after what appeared to be another succesful flash, I still cannot get past the boot logo. after the flash, the device was powered-on and left for +30minutes....
Also, on CWM recovery, the screen output doesn't quite fit on the hd tv it's plugged into so I cannot see the top or LHS of the CWM menu system, but can make out "apply update rom ext. storage" and also "rkimage from ext storage"- i've tried both of these with both the img files I have in root directory on usb stick in port 1, but it doesn't appear to find the files...
lastley, there is little bit of screen instability- there is a flash of a horizontal line every 1-2 seconds on the boot logo screen and the cwm screen- I think this is just due to the power levels on the hdmi but thought it worth a mention.
so, what am I doing wrong? I'm not overly concerned yet as as I can still enter CWM and still flash via rkflashkit... but...
1) using rkflashkit, should I have flashed the 'system partition'? (which one should I have flashed?)
2) is there something else I have to do (on phones that I have flashed, it's been advised to clear dalvik cache but I cannot see an option like that on the version of cwm I have)
3) how do I use the cwm to flash an image? what file needs to where? which 'exernal storage'?
4) any other ideas why my x7 is getting stuck at boot logo?
I found the quickshot rom (here:http://minixforums.com/threads/custom-rom-minix-neo-x7-quickshot-v2-rom-by-the-nitro-team.3838/) which offered a 'pc' installation rom and 'cwm' rom- so I guess there is a difference between them.
seeing as cwm is supposed to be easier (and from galaxy ace flashing it did seem to be) so I copied the whole cwm zip to a usb stick and stuck it in port 1 of the x7 and booted into cwm. however, I couldn't find a way to access the zip on the stick via the menu items I had use of. so either my cwm install had gone titsup or, again, i missed something.
I had more luck with the other (pc) installation file. on un-rar-ing, I found a few image files- misc, system, kernal et al which I flashed to their namesake partitions using rkflashkit. then reboot. The minix x7 has once again burst into life! hoorah!
and finally regarding the horizontal line flickering on screen (which I still had after I had succesfully reflashed with quickshot) i just changed the output to 720@60 and the flicker stopped occuring.
I'd still like to know what I did wrong in the first place though- where should i have flashed the single kasty img to? whould the whole kasty rom zip be copied to 'sdcard' on the x7, ie, to the internal sdcard before using cwm? other hints?
The proper way to flash our Kasty firmwares is to use Rockchip Batch Tool, as mentionned on each of our custom firmware pages.
I don't think a tool exist on Linux to flash firmware images in update.img style.
Easiest thing would be to get access to a Windows PC, it may also work with Windows emulated in a virtual box on Linux (not sure, you'll have to check).
Last option would be to split to update.img file and flash each separate image (boot.img, recovery.img, kernel.img, system.img...) and flash those using RkFlashKit on Linux.
due to lack of windows install img (and down to the fact my ubuntu-laptop is old and knackered) I cannot go down the window in vbox route...
but the spiltting up of update.img is interesting.... I had a search round tinternet but havent found anyway to split the kasty img- i tried the split_boot.py script (from http://linuxclues.blogspot.co.uk/2012/11/split-bootimg-python-android.html) but it seems thats wrong as the update.img is not a boot.img...
I tried unzipping, un-rar-ing but nothing could handle it
opening it textpad (text format) gives me the following info...
so i can see which img files are contained.
I'll have a look later to see if I can use this info to find something to split the update.img
Most Users Ever Online: 749
Currently Online: kontra007
Currently Browsing this Page:
Devices in use: Desktop (78), Phone (15), Tablet (1)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech