Twrp .img file to big for flashing?

Search This thread

isetnt

Senior Member
Feb 13, 2016
110
46
tyresö
Kennyd.cf
Realme X50 Pro
So I recently got a moto x style (pure) running android 6.0 marshmallow and have unlocked the bootloader. But when trying to flash twrp 3.1 I get this message
target reported max download size of 536870912 bytes
sending 'recovery' (34102 KB)...
OKAY [ 1.141s]
writing 'recovery'...
(bootloader) Image size exceeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.205s

Is there anyway to fix this and how can I fix it?
 
Last edited:

isetnt

Senior Member
Feb 13, 2016
110
46
tyresö
Kennyd.cf
Realme X50 Pro
Your recovery partition (mmcblk0p32) should be about 11264 blocks @ 4096kB per block so ~46.14MB... more than enough room for TWRP with 40%+ to spare.

What is the command you entered EXACTLY and can you boot TWRP successfully?

Code:
fastboot boot twrp-3.1.1-0-clark.img

No i can not boot it trough fastboot boot twrp-3.1.1-0-clark.img it just reboots as normal.
 

Sagar_1401

Senior Member
Sep 10, 2015
549
114
Navi Mumbai India
Never encountered this issue.. i think maybe there might be some less storage remaining on your device?? Try uninstalling some apps,imgs and try again!
Hopefully should work
 

isetnt

Senior Member
Feb 13, 2016
110
46
tyresö
Kennyd.cf
Realme X50 Pro
What is the output of "fastboot getvar all"? (Mask out IMEI please)?

When doing it I get this output
(bootloader) version: 0.5
(bootloader) version-bootloader: 6016
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA44904I9X
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 8D13D20B0B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 10-16-2014
(bootloader) sku: XT1095
(bootloader) iccid: 8901260002767386677
(bootloader) cust_md5: 94CDE6B08D9D17B4BF64FA14E8B18163
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 28 12:23:55 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/victara_tmo/victara:6.0/M
(bootloader) ro.build.fingerprint[1]: PE24.49-18/20:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.11.18.victara_tmo
(bootloader) ro.build.version.full[1]: .tmo.en.US
(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[0]: MSM8974BP_42352121.25.09.24R VICTARA_T
(bootloader) version-baseband[1]: MO_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g389e46b (hudsoncm@
(bootloader) kernel.version[1]: ilclbld87) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Nov 3 16:55:43 CST 2015
(bootloader) sdi.git: git=MBM-NG-V60.16-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V60.16-0-gfd10553
(bootloader) rpm.git: git=MBM-NG-V60.16-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V60.16-0-g04e322b
(bootloader) aboot.git: git=MBM-NG-V60.16-0-g496ce05
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: unknown
 

acejavelin

Inactive Recognized Contributor
Last edited:
  • Like
Reactions: thejase

isetnt

Senior Member
Feb 13, 2016
110
46
tyresö
Kennyd.cf
Realme X50 Pro
Last edited:

acejavelin

Inactive Recognized Contributor
Okay so I got the right img and it flashes but when doing fastboot boot recovery.img it just restarts as normal. Should i flash a custom boot img?
I don't know the intricacies of that device... Some devices you can't boot recovery directly with fastboot and that's normal

Honestly you should go to the Moto X 2014 area and read or ask there. Not trying to blow you off, you are just more likely to get right answers there.
 
  • Like
Reactions: SteveHebe

debojyotidey

Senior Member
Apr 3, 2015
111
7
Durgapur
Your recovery partition (mmcblk0p32) should be about 11264 blocks @ 4096kB per block so ~46.14MB... more than enough room for TWRP with 40%+ to spare.

What is the command you entered EXACTLY and can you boot TWRP successfully?

i got the same error as him while flashing stock rom for XT1550.tried everything, but the boot,recovery and modem(yes now there is no signal) won't flash.
 

dzidexx

Senior Member
Nov 9, 2015
1,694
522
Lublin, Poland
Last edited:

debojyotidey

Senior Member
Apr 3, 2015
111
7
Durgapur
i flashed the twrp by squid.i can flash twrp successfully, and even boot in twrp,flash roms and stuffs using twrp and then boot into that rom too.problems arise when i flash stock recovery, boot,modem.thing is, the size of those (say boot.img is abt 16MB, when i try to flash it using fastboot,the size which is getting flashed(shown by sending...) is abt 32MB.it's very strange,but also the only thing i can relate to the error message i get 'Image size exceeded partition limits'.

---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------

i flashed the twrp by squid.i can flash twrp successfully, and even boot in twrp,flash roms and stuffs using twrp and then boot into that rom too.problems arise when i flash stock recovery, boot,modem.thing is, the size of those (say boot.img is abt 16MB, when i try to flash it using fastboot,the size which is getting flashed(shown by sending...) is abt 32MB.it's very strange,but also the only thing i can relate to the error message i get 'Image size exceeded partition limits'.
now if i flash roms using the twrp,since modem isn't there (after execution of fastboot erase modem..... command,i don't recall exactly) rom is working with exception of modem stuffs.
 

debojyotidey

Senior Member
Apr 3, 2015
111
7
Durgapur
You downloaded & upacked stock from here:
https://mirrors.lolinet.com/firmware/moto/osprey/official/RETASIA/
Flashed modems/baseband this way:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

And now you haven't any sim or wifi?
Did you try to flash stock boot.img in twrp? @debojyotidey
the problem started when i went to flash stock.not from your link though.by seeing the file size in the link you provided i can say it might be the same file.the thing is that when i tried to flash the boot,recovery and modem they showed that 'Image size exceeded partition limits'.so when i observed the file size that was getting flashed(say stock recovery which is about 16MB),it showed that the size of the file getting flashed is 32MB.this is very strange. however, when i tried flashing twrp which is 8156KB,it showed that the file size getting flashed is 8156KB.
so even when the boot,recovery and modem steps failed to get flashed(flash partition gpt.bin and bootlader not getting flashed i know the reason) i tried booting, which obviously didn't boot.so next i flashed twrp and then a custom rom,it booted!! but everything related to modem,like wifi,sim,etc were broken.i think it is expected. also now the software status is showing 'modified'.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Your recovery partition (mmcblk0p32) should be about 11264 blocks @ 4096kB per block so ~46.14MB... more than enough room for TWRP with 40%+ to spare.

    What is the command you entered EXACTLY and can you boot TWRP successfully?

    Code:
    fastboot boot twrp-3.1.1-0-clark.img
    1
    (bootloader) product: victara

    (bootloader) sku: XT1095
    Your problem is clear, you don't have a Moto X Pure/Style, you have a Moto X 2nd Gen or Moto X 2014 (which is sometimes called "Pure" but it's different), try this one: https://twrp.me/devices/motorolamotox2014.html
    1
    Okay so I got the right img and it flashes but when doing fastboot boot recovery.img it just restarts as normal. Should i flash a custom boot img?
    I don't know the intricacies of that device... Some devices you can't boot recovery directly with fastboot and that's normal

    Honestly you should go to the Moto X 2014 area and read or ask there. Not trying to blow you off, you are just more likely to get right answers there.