Mod 4.0.3 can I sew with 2.6.3 right away? Or first beta2?
Anticipating the remaining questions - is it possible with MIUI, LeWa, etc. - VM 4.0.3 firmware for FT is complete, i.e. contains images for ALL the partitions to be flashed and has its own body memory markup. You can sew with
any current firmware with
any markup. And even raise a brick.
I made NVRAM backup, I can use the Flash tool, the only thing that worries me is how to get it back if I don’t like it? I now have vredniy mod v 2.6.3 + carliv touch recovery + I also did redevelopment, so that under the proposals there would be 4.9 GB (I don’t remember which way).
teenpsb, Before flashing you can do the following:
1.1. Save current markup (MBR, EBR1, EBR2, PMT, scatter).
1.2. Make nandroid backup from recovery, including sections nvram, uboot, logo, sec_ro (I don’t remember anymore, but I didn’t add sec_ro backup to CTR)
1.3. Save on the BB data from the internal flash drive (if any)
If redevelopment was done only for USRDATA, then for rollback to VM 2.6.3
2.1. you sew through the October October FT, replacing the markup files from section 1.1 (MBR, EBR1, EBR2, scatter) and recovery.img from section 1.2 or the one from which you set yourself CTR.
2.2. Loads in recovery, format / data and / emmc
2.3. You recover in recovery from backup (p. 1.2.)
2.4. Pouring data from the BB to the internal USB flash drive (if any)
A - x93-07, what are the sizes of boot, recovery and systems in your scatter? I just have a redevelopment, I want to compare with yours.
For everyone who is interested in markup in VM 4.0.3 and too lazy to download all the firmware
Memory Markup in VM 4.0.3
root @ JY-G4 \ G5: / # cat / proc / dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000600000 0x000000000000000000 2 / dev / misc-sd
mbr 0x0000000000080000 0x000000000000000000 2 / dev / block / mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 / dev / block / mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 / dev / block / mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 / dev / block / mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 / dev / block / mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 / dev / block / mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 / dev / block / mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 / dev / block / mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 / dev / block / mmcblk0
bootimg 0x0000000001000000 0x0000000002180000 2 / dev / block / mmcblk0
recovery 0x0000000001000000 0x0000000003180000 2 / dev / block / mmcblk0
sec_ro 0x0000000000600000 0x0000000004180000 2 / dev / block / mmcblk0p4
misc 0x0000000000080000 0x0000000004780000 2 / dev / block / mmcblk0
logo 0x0000000000300000 0x0000000004800000 2 / dev / block / mmcblk0
ebr2 0x0000000000080000 0x0000000004b00000 2 / dev / block / mmcblk0
expdb 0x0000000000a00000 0x0000000004b80000 2 / dev / block / mmcblk0
android 0x0000000048000000 0x0000000005580000 2 / dev / block / mmcblk0p5
cache 0x0000000007e00000 0x000000004d580000 2 / dev / block / mmcblk0p6
usrdata 0x0000000081e00000 0x0000000055380000 2 / dev / block / mmcblk0p7
fat 0x000000066f980000 0x00000000d7180000 2 / dev / block / mmcblk0p8
bmtpool 0x0000000000000000 0x00000000ff9f00a8 2 / dev / block / mmcblk0
Part_Name: Partition name you should open;
Size: size of partition
StartAddr: Start Address of partition;
Type: Type of partition (MTD = 1, EMMC = 2)
MapTo: actual device you operate
Post has been editedlion567 - 17.09.14, 13:15