NEW - Lollipop - wasser firmware 3.0.6 for Minix Neo X7

[Pollies]

Download boot failed

Hi Wasser...i've got a serieus problem. I think. I come from fin 1.8...and tried to install your rom. After installing your rom...the system was booting and i got the first question.....was is your country. the standard mouse was not working so i couldn't select the country. So i installed the rom agian, but the same problem. I did an erase and tried to install for the 3th time....but now i've got a Download boot failed error.

I don't what to do.....because i think system is clean (after erase) and i can't install. Do you have any suggestions?

---update---
i tried to update to stock version X7_20131231 (v 008) and there it stops with error Maskrom fail

[danfozzy]

Try this for me.

Download this file http://flumpster.lolcakes.com/androi...oduct_7a18.zip and extract it.

Place the Vendor_0c40_Product_7a18.kl in system/usr/keylayout and set permissions RW R R (644).

Restart the machine and see if any of the buttons work.

just tried it. no joy, theres no difference from before i added your a2 layout

[Guest]

MINIX XBMC won't work on this rom (all hw acceleration is disabled). I'm using Beyond XBMC myself and have no problems with 1080p videos. Try the stock video player. If you get stutter on that, there is some deeper issue at play.

Molle, would disabled hw acceleration be the potential problem I'm also having with HBO go and Showtime apps streaming stuttering badly? Is no HW accel a choice that Wasser can make on the rom or is a kitkat thing?

I didn't have any stuttering on these two streaming apps under 008, 007e, 006 stock roms or finless roms. Only have a problem with them on Wassers kitkat rom.

Thanks as I've been trying to get these two apps (along with vol+/- issue) going so I can move to this rom.

[Guest]

Hi Wasser...i've got a serieus problem. I think. I come from fin 1.8...and tried to install your rom. After installing your rom...the system was booting and i got the first question.....was is your country. the standard mouse was not working so i couldn't select the country. So i installed the rom agian, but the same problem. I did an erase and tried to install for the 3th time....but now i've got a Download boot failed error.

I don't what to do.....because i think system is clean (after erase) and i can't install. Do you have any suggestions?

---update---
i tried to update to stock version X7_20131231 (v 008) and there i stock with error Maskrom fail

See post #47 on page 3 of this thread. I'm not sure if what you are saying is the same issue but following those instructions, I was able to flash back to stock no problem. Just need to push and hold the power button the whole time without letting go until all steps are done and the reboot starts.

[Flumpster]

just tried it. no joy, theres no difference from before i added your a2 layout

If that isn't working then go to play store and download terminal emulator and keyevent display.

With the A2 plugged in go into terminal emulator and type lsusb

It will give you an output. Look at the end of the row at each device and one will be the id for your A2 that corresponds to the kl file I gave you. Is yours the same id?

Next you want to go into keyevent display and click on the buttons that don't work and look at what the scancode is for each of the buttons that don't work. If they are not displaying anything on key press then it will need to be fixed in kernel. If they show scancodes then in can be fixed.

[Pollies]

See post #47 on page 3 of this thread. I'm not sure if what you are saying is the same issue but following those instructions, I was able to flash back to stock no problem. Just need to push and hold the power button the whole time without letting go until all steps are done and the reboot starts.

Thanks man...it works .....now i'm back on stock. The questions is....what did i wrong during the installation of this rom? Why was my mouse not working?

[danfozzy]

If that isn't working then go to play store and download terminal emulator and keyevent display.

With the A2 plugged in go into terminal emulator and type lsusb

It will give you an output. Look at the end of the row at each device and one will be the id for your A2 that corresponds to the kl file I gave you. Is yours the same id?

Next you want to go into keyevent display and click on the buttons that don't work and look at what the scancode is for each of the buttons that don't work. If they are not displaying anything on key press then it will need to be fixed in kernel. If they show scancodes then in can be fixed.

the device and id match with my a2 and your file, ill have a go with the keyevent now

edit:

menu button - 60
multi window - 240
mute button - 113
app locker button - 59

nothing happens pressing these buttons, but the above codes come up on the keyevent viewer app but they come up twice, like ive pressed it twice?

[Guest]

Thanks man...it works .....now i'm back on stock. The questions is....what did i wrong during the installation of this rom? Why was my mouse not working?

That I can't help with. One thing to realize is that the wasser batch flash tool doesn't point to where all the new boot loader and img's are in the subdirectories of the zip file Wasser posted. So you need to manually go in and point each line time in the batch flash tool to the correct file in the various subdirectories of wasser provides. If you don't manually do this, it may be using some of your old 1.8 finless components along with some new wasser components which won't work together.

Also make sure to use the correct V2 something boot loader which is included somewhere in his download as well.

Can't say if any of this was your issue but just in case it wasn't obvious (which it wasn't initially for me).

[smokie171]

same issue with remote

That I can't help with. One thing to realize is that the wasser batch flash tool doesn't point to where all the new boot loader and img's are in the subdirectories of the zip file Wasser posted. So you need to manually go in and point each line time in the batch flash tool to the correct file in the various subdirectories of wasser provides. If you don't manually do this, it may be using some of your old 1.8 finless components along with some new wasser components which won't work together.

Also make sure to use the correct V2 something boot loader which is included somewhere in his download as well.

Can't say if any of this was your issue but just in case it wasn't obvious (which it wasn't initially for me).

You have to use stock remote, keyboard will not work on initial setup. I had the same troubles attempting to flash out of kitkat 4.4. Had to push power button in the entire time. Was getting message waiting for mask rom to start. I have heard others with similar problems flashing back. I went back to finless 1.7 which i seem to run the best on, but first i flashed back to minix stock rom 4.2 just to be safe. Glad you were successful as well.

Kevin

[Mr Dasher]

Cooking up a 720p O/C kernel

Hey Wasser,

Thanks for taking the X7 to the next level. I don't suppose you could find it in your heart to cook up a 720p O/C kernel for us poor people who are stuck with 720p monitors.

Thanks,

D

[Molle]

Molle, would disabled hw acceleration be the potential problem I'm also having with HBO go and Showtime apps streaming stuttering badly? Is no HW accel a choice that Wasser can make on the rom or is a kitkat thing?

MINIX XBMC includes checks to ensure it's running on a genuine MINIX device with a MINIX firmware. It these checks fail, the player refuses to even install. Flumpster has created a patched version which runs just on Finless ROMs. It will install on Wasser's ROM but with all h/w acceleration disabled.

Try Flumpster's Beyond XBMC Beta2. It works wery well with this ROM.

[Molle]

Wasser,

The ROM seems to enable "Strict Mode" which makes a red square flash around the screen on some occasions. This feature can be disabled with the following build.prop settings:

persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1

The definition for "Strict Mode" is: "Flash screen when apps do long operations on main thread".

[Batfink32]

Re: KitKat-4.4.2 for Minix X7

Wasser,

The ROM seems to enable "Strict Mode" which makes a red square flash around the screen on some occasions. This feature can be disabled with the following build.prop settings:

persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1

The definition for "Strict Mode" is: "Flash screen when apps do long operations on main thread".

So that's what it is!? Thanks Molle

Sent from my Nexus 5 using Tapatalk

[Pluto]

Oh finally, Molle you are an amazing troubleshooter my friend, a key person around here . I mentioned the red box earlier but it did not seem to be happening elsewhere, and I've noted that it happened strictly with browsers.

PS, I've been using the latest kernel, and had shutdowns and restarts. Last night while watching a movie, it literary restarted, went dark, boot animation came on, all this with Audio from the movie in the background, and it didn't even stop for about 10 seconds. Another problem, with every video play i seem to be interrupted every 13 minutes, precisely 13 minutes. I was streaming 10GB> 1080p material through a 100mbit ethernet from my SMB notebook, i am doubting on the new AV/Firewall my company installed (McAfee), but i could reopen the movie straight away, but the hang crashed every video player.

And the weirdest thing, and i kept repeating it, and this must be a surprise from google. A few days ago, a random restart showed the Google TV, both text and icon/logo, the thing is, it crashed and got stuck there, and i hate myself for not taking a picture. WHAT does this mean? What is google sensing in RK?

[Batfink32]

Re: KitKat-4.4.2 for Minix X7

Oh finally, Molle you are an amazing troubleshooter my friend, a key person around here . I mentioned the red box earlier but it did not seem to be happening elsewhere, and I've noted that it happened strictly with browsers.

PS, I've been using the latest kernel, and had shutdowns and restarts. Last night while watching a movie, it literary restarted, went dark, boot animation came on, all this with Audio from the movie in the background, and it didn't even stop for about 10 seconds. Another problem, with every video play i seem to be interrupted every 13 minutes, precisely 13 minutes. I was streaming 10GB> 1080p material through a 100mbit ethernet from my SMB notebook, i am doubting on the new AV/Firewall my company installed (McAfee), but i could reopen the movie straight away, but the hang crashed every video player.

And the weirdest thing, and i kept repeating it, and this must be a surprise from google. A few days ago, a random restart showed the Google TV, both text and icon/logo, the thing is, it crashed and got stuck there, and i hate myself for not taking a picture. WHAT does this mean? What is google sensing in RK?

I also had a restart when watching a movie using Wassers ROM and kernel, the film started stuttring the the box completely restarted. Also when downloading more than 1 app from the Play store the box restarts. I have to say though, picture quality and movie playback is stunning with KK. So much better than 4.2.


Sent from my Nexus 5 using Tapatalk