Rooted Hongmi - stock recovery won't let me flash TRWP.. Error: Partition table not match Installati


Lanky

Members
Oct 12, 2012
49
18
I just rooted my brand new TD Hongmi,

when i reboot to recovery and try to install the trwp .zip file i get the following message

Error: Partition table not match
Installation aborted.

I cannot flash the recovery .img file through moble uncle either, after flashing and rebooting to recovery, the stock recovery loads...

help is very much appreciated!!
 
i bought it in China,

and I can't flash anything, i get the same error message about the partition table not being matched..
 
Post the system screen op CPU-Z here, I can compare with mine.
It must say also 320 dpi and mt6589.
I assume you downloaded cpu-z by your self from the play store (not included already on your phone). You can also check resolution when making screenshot en check resolution on your pc.

Run also Antutu benchmark. Download it from the playstore and do not use the one if it was already included on your phone. Version Antutu should be 4.2
It is not always telling everything but give it a try. My score: 16056.
 
Last edited:
the hardware shows: mt6582

desnsity: 320dpi

i guess it's fake as the hardware is different?
 
the hardware shows: mt6582

desnsity: 320dpi

i guess it's fake as the hardware is different?

Sadly yes. Try Antutu and you will be sure.
Also make screenshot and check details on PC. I think it will show different resolution.
 
just ran the antutu benchmark test(downloaded from the MIUI marketplace)

i got 16809
 
just noticed Antutu says the internal SD is 1828.6MB..

It also says screen is 720x1280
CPU model: MTK MT6589T
320DPI
gpu: PowerVR SGX 544MP

Camera: 8.0 Mega pixels 3264x2448
Front camera: 1.2 mega pixels, 1280x960

video spec: 1080p

Android version: 4.2.1
 
just noticed Antutu says the internal SD is 1828.6MB..

It also says screen is 720x1280
CPU model: MTK MT6589T
320DPI
gpu: PowerVR SGX 544MP

Camera: 8.0 Mega pixels 3264x2448
Front camera: 1.2 mega pixels, 1280x960

video spec: 1080p

Android version: 4.2.1

Same as mine. I only have android 4.2.2.
Strange. You can also check in MobileUncleTools.
 
You have the TD version. You are not trying WCDMA roms ?

Differences I see: I have memory 2043.1 MB (I have WCDMA phone)
Assuming it is not fake then your memory is partioned different and that is causing the problem.
Did you use spflashtool ?

I think if you check your system storage under Settings you will see 1 GB instead of 2 GB.
 
Last edited:
Hi, yes i have the TD version.

I didn't try any new ROMs yet, i rooted, and tried to flash the new recovery and that's how this all started.

I didn't use spflashtool yet, is my phone fake or?
 
Hi, yes i have the TD version.

I didn't try any new ROMs yet, i rooted, and tried to flash the new recovery and that's how this all started.

I didn't use spflashtool yet, is my phone fake or?


Where did you get this recovery from ?
(link)
 
one thing i do remember doing is full wipe BEFORE flashing the new recovery after rooting, could this of messed up the partition tables?

i also noticed there is no serial number on the box to enter the code on xiaomi website :/
 
one thing i do remember doing is full wipe BEFORE flashing the new recovery after rooting, could this of messed up the partition tables?

i also noticed there is no serial number on the box to enter the code on xiaomi website :/

Full wipe is only formatting filesystems, no repartioning.

Serial number is on a little plastic film. You need to scratch with your nails the grey area to see the serial number.
 
To see the ROM partion you have to use a terminal emulator and use this command:

cat /proc/dumchar_info

In my case I see :

Part_Name Size StartAddr Type MapTo
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 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 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003400000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003700000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000004180000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002cb80000 2 /dev/block/mmcblk0p6
usrdata 0x0000000080000000 0x0000000034980000 2 /dev/block/mmcblk0p7
fat 0x0000000036180000 0x00000000b4980000 2 /dev/block/mmcblk0p8
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
 
Ok, thanks a lot for the help

the only problem is even if get teh correct recovery from the link u posted i wont be able to flash it due to the partition error


also, isn't my internal sd being 2GB confirmation it's fake?