![]() |
2013-06-20
, 20:02
|
|
Community Council |
Posts: 664 |
Thanked: 1,648 times |
Joined on Apr 2012
@ Hamburg
|
#2
|
![]() |
2013-06-20
, 21:00
|
Posts: 73 |
Thanked: 16 times |
Joined on May 2012
@ THESSALONIKI GREECE
|
#3
|
Following this instruction, I searched for libflashplayer.so and found it in /opt/adobe-flashplayer/libflashplayer.so.
Now when I search for "31302e31" in a hexeditor, I can't find that number. I guess it differs from N900. Any help?
![]() |
2013-06-21
, 14:15
|
|
Community Council |
Posts: 664 |
Thanked: 1,648 times |
Joined on Apr 2012
@ Hamburg
|
#4
|
sed -i 's/10_1_105_6/11_*_***_*/' /opt/adobe-flashplayer/libflashplayer.so
|
2013-07-01
, 08:06
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#5
|
OK, here's something that might work, but is prone to render your device MALF (need to reflash), because of aegis file protection:
You could of course copy that file to PC, open it with a hexeditor, search for "10_1_105_6" and edit to a higher value. Make sure to only overwrite characters and not change the file length.Code:sed -i 's/10_1_105_6/11_*_***_*/' /opt/adobe-flashplayer/libflashplayer.so
Actual version on N9 is 10.1.105.6, not sure which higher versions might work, here's a list: http://helpx.adobe.com/flash-player/...-versions.html
EDIT: Some furter info I gathered on IRC:
After editing, refhashlist has to be re-signed. There is even a refhashlist.pl perl script somewhere on the forum that could do the magic for you if your not that familiar with aegis magic.
Basicly after edit, you just take sha1sum of the new library, update the checksum in refhashlist file and then resign the refhashlist to avoid malf.
Would this work? Anybody willing to test?
The Following User Says Thank You to For This Useful Post: | ||
![]() |
2013-07-01
, 08:44
|
|
Community Council |
Posts: 664 |
Thanked: 1,648 times |
Joined on Apr 2012
@ Hamburg
|
#6
|
Do you know that /opt/adobe-flashplayer/libflashplayer.so is protected by aegis or is it just a guess? libflashplayer.so comes in optional package so I doubt there's any protection.
For a quick test I just moved libflashplayer.so to another filename on my main n9 and the phone works just fine. Exited shell and then renamed it back without any issues in normal devel-su root. If you tried to do that to an aegis protected system file (for example /etc/init.d/rcS) the file would be locked and you'd have to disable aegis validation with aegisctl before you could rename it back. (and yes you'd need to update refhashlist if the file was changed.)
My suggestion is to simply take backup of the library in case hexediting goes wrong:
and then replace the original file with a one that has modified flash version string in it.Code:# cp /opt/adobe-flashplayer/libflashplayer.so /opt/adobe-flashplayer/libflashplayer.so.bak
![]() |
2013-07-01
, 10:10
|
|
Posts: 956 |
Thanked: 2,628 times |
Joined on Nov 2011
|
#7
|
adobe-flashplayer R 39 opt/adobe-flashplayer/libflashplayer.so S 15 com.nokia.maemo H 40 b38e7706479854fdc9b047bbfcb20deb96007b6b A 0 0 33261 P 6
![]() |
2013-08-04
, 14:29
|
|
Community Council |
Posts: 664 |
Thanked: 1,648 times |
Joined on Apr 2012
@ Hamburg
|
#8
|
![]() |
2013-08-04
, 15:04
|
|
Posts: 6,436 |
Thanked: 12,701 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#9
|
![]() |
2013-08-04
, 15:16
|
|
Community Council |
Posts: 664 |
Thanked: 1,648 times |
Joined on Apr 2012
@ Hamburg
|
#10
|
I wonder if somebody already came across an equivalent of tweakflash for the N9? - Like this for N900.
Or at least how to do it manually?
Nokia 5110 > 3310 > 6230 > N70 > N9 BLACK 64GB
Hildon Foundation Board member
Maemo Community e.V. co-creator, founder and director since Q4/2016
Current Maemo Community Council member
Last edited by Win7Mac; 2013-06-20 at 20:36.