NEW - MK908 Finless 1.8 ROM

[ffroms]

....
Hmmm, I know what that is then. They must have used an older recovery with a older flickering kernel in it!
I could easily fix that by recompiling recovery without a kernel in it!

Would you like to try that and see if it solves the flicker in recovery? If so I can wipe that up to test. I don't have flicker issues on any of my TV's so cant test.

Bob

I would be great. If you can put TWRP into recovery or CWM. What ever you prefer.
Thank you in advance.

[Finless]

I would be great. If you can put TWRP into recovery or CWM. What ever you prefer.
Thank you in advance.

I can do that..... I am now looking at yet another new release of this ROM from Beelink so I may come out with a 1.8A or 1.9 depending on what is in it.

Bob

[ffroms]

Great! Can't wait for it.
I'll test it as soon as you release it

[Finless]

OK I just did a 100% comparison of the 3/10 ROM and the 3/17 ROM from Beelink.

Boot.img is 100% the same....

Kernel is 100% the same.....

They did not even change build.prop and the date! Stock build.prop still says 204j2 dated 20140307

System.img the ONLY difference is in /media/audio/ringtone and /media/audio/notifications they had some duplicate file names for some sounds. The same file is there with a upper case first letter and a lower case one. like arcturus.ogg and Arcturus.ogg
NO BIG DEAL! Does NOT even effect how it works!!!!!

Recovery.img 100% the same.

So, there is no reason to do another ROM based on the 3/17 release because nothing is different other than the sounds files which again DO NOT cause any problem!


Bob

[ffroms]

Thanks for info.
Since you don't plan on building new ROM is there chance for new recovery with TWRP or CWM?
Oh, yes, could you tell me does this ROM use any goverment (smartass, ondemand...) for CPU and is it possible to change it and how?

Thank you again for all your hard work.

[freakkid]

Thanx Bob for this needed mod...However I keep getting download image failed in my Flasher status right after checking the kernel...notice the download states zip is 348 megs but I am getting 337 MB

re-downloaded zip twice, still no go..

By the way I am coming from Kitkat but it should not matter..

[Finless]

Thanx Bob for this needed mod...However I keep getting download image failed in my Flasher status right after checking the kernel...notice the download states zip is 348 megs but I am getting 337 MB

re-downloaded zip twice, still no go..

By the way I am coming from Kitkat but it should not matter..

Yes actually coming from KK back to JB is a problem. I brick my device EVERY TIME!

You have to put it in MASK ROM mode by shorting NAND pins. It's because of the loader.
PAIN in the ass but fact. The loader will not downgrade without MASK ROM mode

Bob

[canford]

Bo just a quickie how do you: MASK ROM mode by shorting NAND pins, thanks.

[Finless]

Bo just a quickie how do you: MASK ROM mode by shorting NAND pins, thanks.

I would repost this but right now I do not have time. Search UNBRICK.

Basically you have to take your device apart.
Find the NAND chip.
Short pins 8&9 on the chip with a pin. count down from the round DOT on the chip.
Plug in the device to USB OTG while shorting the pins.
ROM flash tool should say "MASK ROM"

Bob

[canford]

Thank you appreciate your time, is this the only way you can get this rom on or if someone has image for this rom can you use RKBatch tool.

[freakkid]

I would repost this but right now I do not have time. Search UNBRICK.

Basically you have to take your device apart.
Find the NAND chip.
Short pins 8&9 on the chip with a pin. count down from the round DOT on the chip.
Plug in the device to USB OTG while shorting the pins.
ROM flash tool should say "MASK ROM"

Bob

Thanx for the reminder Bob...everything is o.k....Antutu score was 18,800 w/stock kernel...Just to add to unbrick post, I shall quote you in one of your thread concerning downgrading from KitKat to Jellybean "...Now a warning to all going from kitkat back to JB.
DO NOT load up the JB ROM kit and erase NAND. Load up the KitKAt ROM kit, erase NAND, then exit. Now run the JB ROM kit and flash the ROM. This should keep you from hard bricking..

[canford]

Just a quick update, tried it in another usb port and no problems now, thought I would pass this along!

[Finless]

Now a warning to all going from kitkat back to JB.
DO NOT load up the JB ROM kit and erase NAND. Load up the KitKAt ROM kit, erase NAND, then exit. Now run the JB ROM kit and flash the ROM. This should keep you from hard bricking..

I never tried that! GOOD TO KNOW!

Thank you!

Bob

[nntvog]

Bob,I think there there is a problem with the parameter4gb. If I do the maths correctly, the user partition should be 0x009A4000 and not 0x009B4000.

I flashed the parameter4gb and doesnt boot. It show the boot screen with the red "freaktab.com ". There maybe some other problem. I changed to 0x009A4000 and still doenst boot.

[tlchuan]

Dear Bob,

ROM Flash tool_21 only found loader device even i have install the driver