Quote:
Originally Posted by MustardOrMayo
I can't go further without a full system image to recover from
|
You already have the images on your device.
will show you addresses. For example on my ares:
Code:
CMDLINE: console=ttyS2 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyS2 init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00002000@0x00006000(wbf),0x00002000@0x00008000(misc),0x00008000@0x0000a000(resource),0x0000a000@0x00012000(kernel),0x00010000@0x0001c000(boot),0x00010000@0x0002c000(recovery),0x00038000@0x0003c000(backup),0x00040000@0x00074000(cache),0x00002000@0x000B4000(kpanic),0x00333000@0x000B6000(system),0x00008000@0x003E9000(metadata),0x00002000@0x003F1000(baseparamer),0x00020000@0x003F3000(radical_update),-@0x00413000(userdata)
With these addresses you can backup your whole system (there's no point downloading
userdata using rkflashtool):
Code:
rkflashtool r 0x00002000 0x00002000 > uboot.img
rkflashtool r 0x00004000 0x00002000 > trust.img
rkflashtool r 0x00006000 0x00002000 > wbf.img
rkflashtool r 0x00008000 0x00002000 > misc.img
rkflashtool r 0x0000a000 0x00008000 > resource.img
rkflashtool r 0x00012000 0x0000a000 > kernel.img
rkflashtool r 0x0001c000 0x00010000 > boot.img
rkflashtool r 0x0002c000 0x00010000 > recovery.img
rkflashtool r 0x0003c000 0x00038000 > backup.img
rkflashtool r 0x00074000 0x00040000 > cache.img
rkflashtool r 0x000B4000 0x00002000 > kpanic.img
rkflashtool r 0x000B6000 0x00333000 > system.img
rkflashtool r 0x003E9000 0x00008000 > metadata.img
rkflashtool r 0x003F1000 0x00002000 > baseparamer.img
rkflashtool r 0x003F3000 0x00020000 > radical_update.img