error (mismatched partition size)

Search This thread

amir58hz

Member
Sep 9, 2018
29
4
i have motorla xt1032 falcon
when flash it have error (mismatched partition size) i cannt flash recovery i can only "fastboot boot twrp.img"
My phone is formatted, but nothing is erased, the previous firmware and information remain. I did this with fastboot and Twrp, and the result was the same. I change the format of the partition in T, it says done, but the format does not change.
i want t change format type to ex4 but no changing only say do it
i thing my device is lock or lost it
please help
 

engage4

Member
May 17, 2013
45
14
Ignore mismatch partition size error and boot into recovery using vol key. then try to install SU then try formatting again.
If problem remains try restoring stock.
Otherwise EMMC error.
 

amir58hz

Member
Sep 9, 2018
29
4
Ignore mismatch partition size error and boot into recovery using vol key. then try to install SU then try formatting again.
If problem remains try restoring stock.
Otherwise EMMC error.
i cannt flash anything.when flash show error
i can only load boot twrp and cannot flash anything
now how instal SU?
in fastboot with this command i want to instal it but have error
fastboot flash zip superSu.zip


C:\adb>fastboot flash zip su.zip
(bootloader) has-slot:zip: not found
(bootloader) is-logical:zip: not found
Sending 'zip' (1156 KB) OKAY [ 0.058s]
Writing 'zip' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed

for flashing boot have this error
fastboot flash recovery twrp.img


C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (9456 KB) OKAY [ 0.358s]
Writing 'recovery' OKAY [ 0.229s]
Finished. Total time: 0.699s


 
Last edited:

engage4

Member
May 17, 2013
45
14
After flashing twrp do not reboot phone. just use vol button to enter recovery. otherwise stock recovery will overwrite twrp.
 

engage4

Member
May 17, 2013
45
14
Try flashing stock firmware using RSD lite or use xml to bat converter. If stock flashing also fails its probably emmc problem.
 

amir58hz

Member
Sep 9, 2018
29
4
Try flashing stock firmware using RSD lite or use xml to bat converter. If stock flashing also fails its probably emmc problem.
i do with rsd convertor but it have error too
boot loader slot not found in fastboot command error
my problem is it( bootloder slot not found) if it is fixed my problem will fix
 

amir58hz

Member
Sep 9, 2018
29
4

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA92903U33
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 180460020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Mar 6 1:38:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retgb/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPBS23.13-56-2/2:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.201.2.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.GB
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Feb 26 06:48:18 CST 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
Finished. Total time: 0.145s
 

engage4

Member
May 17, 2013
45
14
Your log looks good. use fastboot oem fb_mode_clear and check phone boots or not.
If not try flashing stock with same cid with another pc.
I think its windows driver fault.
 
Last edited:
  • Like
Reactions: amir58hz

engage4

Member
May 17, 2013
45
14
The last thing you may try is reflashing motoboot.img. But its too dangerous(probably you will end up with dead phone).
Iam not responsible if you end up with a brick.
 
  • Like
Reactions: amir58hz

Top Liked Posts