I'm stuck with BT problems... GRRRR
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
Minix X5 4.2.2 ROM with HLS streaming
Collapse
X
-
Great it worked for both of you!
I'm stuck with BT problems... GRRRRPlasma: Panasonic TX-55ST60E
HTPC: LC-Power 1320mi :: Sapphire PURE WHITE Fusion E350 :: 4GB DDR3 :: SSD Corsair Nova 2 [SO] :: 4TB [Storage] || Android PC: Minix X5
powered by Win7 :: XBMC Gotham :: SABnzbd :: CouchPotato :: SickBeard
-
Originally posted by nxg View PostHey thanks alot! I did exactly that and it worked! ...just installed Netflix from Google Play store and all working fine in 1080
The odd thing about this is that I did have the same combination of files in the finless flasher before, but they were all scattered across my desktop in different folders. All I did was move all the 006 1080 stock files except the system.img into one folder in my D:\ harddrive root, copied Karel's 0.9 system.img into the same folder, cleared nand and flashed rom. Boots fine without recov and system seems alot faster and smoother overall (but that's from the last 15 minutes). So the only difference was moving all the files into one folder and putting it in the root of the hd. What Charley8900 said, it's probably something with pathnames with spaces and such..weird tho because I never got any errors before when flashing with finless.
Thanks a million Karel! (and everyone else for the help) Finally Netflix on a big screen in the living room againwoohoo
BUT still, the files in the zip in the first post is the same combination of stock and the HLS system.img as you both used. So why didn't it work?
Did you select the bootloader and .img files MANUALLY in the finless flash tool? (if the files are not in "D:\X5_4.2.2_HLS_720p\ROM\" you have to select them one by one.)
Comment
-
I think it's just a windows directory issue...when I loaded all the files from the root of the harddisk instead of my windows user desktop, it did work. The weird thing is, that everything flashes fine and you get no errors in the whole flashing routine at all.
I think the finless flasher somehow has a problem with complex or deeper pathnames to the files
Comment
-
Originally posted by nxg View PostI think it's just a windows directory issue...when I loaded all the files from the root of the harddisk instead of my windows user desktop, it did work. The weird thing is, that everything flashes fine and you get no errors in the whole flashing routine at all.
I think the finless flasher somehow has a problem with complex or deeper pathnames to the files
So maybe the lesson is not to unpack the zip file to the desktop and run the program from there, BUT instead unpack it to c:\ or d:\
Did other people that had "reboot to recovery" issues also unpacked to the desktop? Please let me know so I can mention it explicitly in the readme! If so then I can fix the big package for X5 X5mini and G4.
Comment
-
Originally posted by karel View PostI flashed the .img files from the "D:\X5_4.2.2_HLS_720p\ROM\" directory with now issues at all.
So maybe the lesson is not to unpack the zip file to the desktop and run the program from there, BUT instead unpack it to c:\ or d:\
Did other people that had "reboot to recovery" issues also unpacked to the desktop? Please let me know so I can mention it explicitly in the readme! If so then I can fix the big package for X5 X5mini and G4.
then added your system.img to ghe same dir.
ran flashtool, and manually pointed every single file, including te v22 file. And your system.img. Remove nand. Flashed...working...
so only put them all togother in a subdir... But the finless is in a different dir on the same level...
Hope this helps... Can sent a printscrn of the subdir, so you van see what files... But believe me, every file from the original rom, and your system.img as stranger....
Comment
-
Minix X5 4.2.2 ROM with HLS streaming
Originally posted by Charley8900 View PostNo, what i did was unpack the minix verdion on c:/fx. Then moved al the files from c:/fx/temp/android to e deep subdir on d:, to a new subdir.
then added your system.img to ghe same dir.
ran flashtool, and manually pointed every single file, including te v22 file. And your system.img. Remove nand. Flashed...working...
so only put them all togother in a subdir... But the finless is in a different dir on the same level...
Hope this helps... Can sent a printscrn of the subdir, so you van see what files... But believe me, every file from the original rom, and your system.img as stranger....
Comment
-
ya none of the mini would boot for me tried both boxes just to boot screen the recovery. OK so i have a lot of boxes to test this weekend. so If I unpack into dir then move all to a different directory your saying it works when doing that way? Because i copied to sub directory and got same on the mini the x5 worked anyone tried on mini yet?Last edited by scooter2014; 31 May 2014, 14:19.Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.
Comment
-
Well Karal the results for the x5 are great stable and fast, Maybe a re build to unpack and keep separate and lose the cwm boot, The mini i havent been able to get past the cwm boot, I tried even your first build, ill try re packing dir and un packing minix rom when i get a chance, so many new boxes flooding out now!
Dont give up on it almost thereMany devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.
Comment
-
I'll try to repack from the kasty rom changing only system.img with lib/modules from kasty's and try bt again...
sent from my Nexus⁴Plasma: Panasonic TX-55ST60E
HTPC: LC-Power 1320mi :: Sapphire PURE WHITE Fusion E350 :: 4GB DDR3 :: SSD Corsair Nova 2 [SO] :: 4TB [Storage] || Android PC: Minix X5
powered by Win7 :: XBMC Gotham :: SABnzbd :: CouchPotato :: SickBeard
Comment
What's Going On
Collapse
There are currently 1453 users online. 0 members and 1453 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment