View Single Post
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#1348
Originally Posted by juiceme View Post
Started to hack on it, just for fun

It was actually fairly easy to extract the rootfs from APE, now I need just tweak that a bit and try to repack it into a kernel image and see what happens
mmh... it seems that most intresting things are happening inside a binary "/usr/sbin/softupd" that init calls as the last thing.

What I did is I extracted that and naturally, uploaded it to my N9 and ran it as root
Scared the s**t out of me, that one...

RM696-21-3:~#
RM696-21-3:~#
RM696-21-3:~# ./softupd
[14519.192718] Creating 1 MTD partitions on "omap2-onenand":
[14519.192840] 0x000000000000-0x000001000000 : "tmp"
[14519.230529] Creating 2 MTD partitions on "omap2-onenand":
[14519.230651] 0x000000000000-0x000000100000 : "tmp"
[14519.241851] 0x000000100000-0x000000340000 : "config"
[14519.271820] Creating 6 MTD partitions on "omap2-onenand":
[14519.271942] 0x000000000000-0x000000100000 : "bootloader"
[14519.277404] 0x000000100000-0x0000003c0000 : "config"
[14519.287719] 0x0000003c0000-0x0000013c0000 : "kernel"
[14519.288146] 0x0000013c0000-0x0000015c0000 : "log"
[14519.299133] mtdoops: Attached to MTD device 3
[14519.299224] 0x0000015c0000-0x00001e000000 : "var"
[14519.302978] 0x00001e000000-0x000020000000 : "moslo"
FATAL: Error inserting g_softupd (/lib/modules/2.6.32.54-dfl61-20121301/g_softupd.ko): Device or resource busy
FATAL: Error inserting g_nokia (/lib/modules/2.6.32.54-dfl61-20121301/g_nokia.ko): Device or resource busy
Cannot find device "upnlink0"
ifconfig: SIOCGIFFLAGS: No such device
phonet: interface `upnlink0' not found
BB5 bb5_rdc_cert_read return value. LIB: 0x00000019 (Inappropriate ioctl for device)
BB5 bb5_rdc_cert_read return value. ROM: 0xFFFFFFFF (UNKNOWN)
BB5 bb5_rdc_cert_read return value. PA: 0xFFFFFFFF (UNKNOWN)
BB5 sec_get_locks return value. LIB: 0xFFFFFFFF (Unknown error 4294967295)
BB5 sec_get_locks return value. ROM: 0x0000000A (SEC_ROM_RET_FAIL)
BB5 sec_get_locks return value. PA: 0xFFFFFFFF (UNKNOWN)
Simlock certificate check: 473 SUCCESS ret val: 0
Image lock is open

^C^C

RM696-21-3:~#

Looking at that I really thought now I've blown it big time...
it seems the sneaky bit of software went and repartitioned my MTD just like that... whooooo!
Well, did it also clear it? hopefully not.... no way to check but reboot and see if it comes back alive....

...and it did (phewwww....)

Now I need to experiment a bit with that if I can get anything worthwhile out of it.
Too bad there's probably no source available for softupd.
 

The Following 6 Users Say Thank You to juiceme For This Useful Post: