Installing older build over newer build on the M8

[adch]

I'm trying to install lifeforce rom but got an error can't install package over newer build. Is there anyway around it?

Thanks

[Finless]

ZIP edify script needs to be edited to remove the assertion check, then zip needs to be resigned.

Bob

[TMx]

copy zip file only to the sd card and try again ,select update from external source ,select card from recovery menu it should work..

[Finless]

copy zip file only to the sd card and try again ,select update from external source ,select card from recovery menu it should work..

LifeForce left the assertion script in his ROM. It checks the build date in build.prop of the existing ROM and if it is newer will fail.

(!less_than_int(1399861930, getprop("ro.build.date.utc"))) || abort("Can't install this package (Mon May 12 10:32:10 CST 2014) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "k200" || abort("This package is for \"k200\" devices; this is a \"" + getprop("ro.product.device") + "\".");


There are 2 ways to solve this.
1) Edit the edify script and remove this check altogether.
2) Root the existing ROM then edit build.prop ro.build.date.utc and make this utc date lower than the date it is looking for in the script which is 1399861930


Bob

[TMx]

LifeForce left the assertion script in his ROM. It checks the build date in build.prop of the existing ROM and if it is newer will fail.

(!less_than_int(1399861930, getprop("ro.build.date.utc"))) || abort("Can't install this package (Mon May 12 10:32:10 CST 2014) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "k200" || abort("This package is for \"k200\" devices; this is a \"" + getprop("ro.product.device") + "\".");


There are 2 ways to solve this.
1) Edit the edify script and remove this check altogether.
2) Root the existing ROM then edit build.prop ro.build.date.utc and make this utc date lower than the date it is looking for in the script which is 1399861930


Bob

second option seems the easier one thanx Bob

[TMx]

LifeForce left the assertion script in his ROM. It checks the build date in build.prop of the existing ROM and if it is newer will fail.

(!less_than_int(1399861930, getprop("ro.build.date.utc"))) || abort("Can't install this package (Mon May 12 10:32:10 CST 2014) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "k200" || abort("This package is for \"k200\" devices; this is a \"" + getprop("ro.product.device") + "\".");


There are 2 ways to solve this.
1) Edit the edify script and remove this check altogether.
2) Root the existing ROM then edit build.prop ro.build.date.utc and make this utc date lower than the date it is looking for in the script which is 1399861930


Bob

I have tried the Build.prob Edit but Not worked ...

changed all dates to 2013 and Utc Date to 1399861929 (1 Lower than Lifeforce) but Still Refuses to install the Lifeforce Firmware...

[Finless]

I think I know why! It is not checking build.prop in /system
It is checking it in recovery!

Are you using the AML autoscript and the recovery.img from the lifeforce ROM?
If recovery is on SDcard it uses that and not the recovery flashed to NAND.

Bob

[TMx]

SDcard contains 3 files REcovery.img+romzip+factoryupdate.aml and Toothpick method...

Removed Recovery.img ,Tried again but same error

[Finless]

Hmmm, what you need is a old recovery on sdcard. I think....
I am pretty sure it's checking build.prop that is in recovery and you need a older recovery so the assertion script in lifeforce ROM will see it is newer.

Bob

[TMx]

Hmmm, what you need is a old recovery on sdcard. I think....
I am pretty sure it's checking build.prop that is in recovery and you need a older recovery so the assertion script in lifeforce ROM will see it is newer.

Bob

Yes Mr Magician, You've done it again

Recovery.img from very old firmware is the right answer

[Finless]

Yes Mr Magician, You've done it again

Recovery.img from very old firmware is the right answer

Glad I could help...

Personally Custom ROMs should not have an assertion script in them so this problem does not happen.
I remove them from mine PERIOD.

However trying to go back to old stock ROM's will always be a problem as they always have an assertion script. It's useless in my opinion but they do it anyway to KEEP people from going in reverse. STUPID


Bob

[worlmer]

M8 square no sound and no remote after update with s82b firmware

I have a M8 sqare 16Gb, after flashing a newer firmware from S82b/M8 S82B_107k4_sdcard.rar, more than 31500 antutus but no sound and no remote.

Reflashing with old M8 Firmware from 16.6.14 -> no update, newer firmware installed.

Recovery no posibillity to wipe system.

I have installed TWRP for M8.

Wipe System, update says updatefile is not for K200, is for S82B.

What can i do ?

How i can install the old recovery.img ?

Thanks

[Guest]

Download Stock Recovery M8 here post #90:

http://www.freaktab.com/showthread.php?15651-NEW-TWRP-for-Beelink-S82b-Tronsmart-S89/page5&p=212633#post212633

I have a M8 sqare 16Gb, after flashing a newer firmware from S82b/M8 S82B_107k4_sdcard.rar, more than 31500 antutus but no sound and no remote.

Reflashing with old M8 Firmware from 16.6.14 -> no update, newer firmware installed.

Recovery no posibillity to wipe system.

I have installed TWRP for M8.

Wipe System, update says updatefile is not for K200, is for S82B.

What can i do ?

How i can install the old recovery.img ?

Thanks

[worlmer]

After editing the update-script , signature failure

Thanks for the recovery.zip.

I have a new problem, after editing the update-script to supress the date and version query, abort - signature failure for whole zip file.

Its possible to "resign" a zip file ?

Thanks

[Guest]

try

http://www.freaktab.com/showthread.php?15498-Modifying-XBMC-help

Thanks for the recovery.zip.

I have a new problem, after editing the update-script to supress the date and version query, abort - signature failure for whole zip file.

Its possible to "resign" a zip file ?

Thanks