ZTE Z995 Overture custom recovery

Search This thread

METDeath

Senior Member
Jun 15, 2010
101
10
EDIT: Here's the recovery thread.

Original post:

So, let me preface this with the following statements:

I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices

So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1

Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root     root              1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6

I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img

I then used the CWM Recovery Builder to build a basic recovery.

I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory

flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory

flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory

So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16

Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.

I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.

So if someone wouldn't mind pointing me in the right direction, that would be awesome.
 
Last edited:
  • Like
Reactions: chongbos

METDeath

Senior Member
Jun 15, 2010
101
10
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!

Also, if you could get me /proc/config.gz, that would be awesome.

Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.

It was literally two days outside of the return to store window too.
 
Last edited:
  • Like
Reactions: chongbos

cooldudezach

Member
Dec 29, 2013
47
15
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.

It was literally two days outside of the return to store window too.

If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off :)
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?

---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------

So, let me preface this with the following statements:

I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices

So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1

Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root     root              1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6

I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img

I then used the CWM Recovery Builder to build a basic recovery.

I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory

flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory

flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory

So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16

Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.

I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.

So if someone wouldn't mind pointing me in the right direction, that would be awesome.

I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it. :)
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy :)
 
Last edited:
  • Like
Reactions: chongbos

METDeath

Senior Member
Jun 15, 2010
101
10
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off :)
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?

---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------



I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it. :)
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy :)

Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.

I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.

Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
 
Last edited:
  • Like
Reactions: chongbos

cooldudezach

Member
Dec 29, 2013
47
15
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.

I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.

Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.

Thanks! So does your phone boot normally, or does it bootloop? I wasn't sure when you wrote that if you were just referring to the recovery boot or not. FTM is integrated with boot.img, which is why i am confused lol.
I'm just trying to figure out what's wrong exactly so I can get your phone up and running.
If you want to hop into irc chac #zte8930 on freenode, that's where I hang out, and where the devs for this group of phones also hangout. :)
 
  • Like
Reactions: chongbos

chongbos

Member
Aug 24, 2012
9
1
Xiamen
weibo.com
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.

I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.

Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.

is that can be use?i want to transplant a msm8960 device's rom so i need a custom recovery.
 

METDeath

Senior Member
Jun 15, 2010
101
10
is that can be use?i want to transplant a msm8960 device's rom so i need a custom recovery.

Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
 
  • Like
Reactions: chongbos

chongbos

Member
Aug 24, 2012
9
1
Xiamen
weibo.com
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.

so..can i flash this .img to my z995? is that offical or custom?

ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)



thanks.sorry for my poor english!

---------- Post added at 10:13 AM ---------- Previous post was at 10:09 AM ----------

Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.

oh,i have been focus on this forum for a long time,and now i have found it.thank u a lot.

---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------

Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.

I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.

Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.

btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.

can u help me?only transplant i9003's custom recovery can take it easy.


thanks. sorry for my poor english!
 

METDeath

Senior Member
Jun 15, 2010
101
10
so..can i flash this .img to my z995? is that offical or custom?

ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)

btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.

can u help me?only transplant i9003's custom recovery can take it easy.


thanks. sorry for my poor english!

The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.

I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.

Your English is actually better than some native English speakers, so keep up the practice and good work!
 

chongbos

Member
Aug 24, 2012
9
1
Xiamen
weibo.com
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.

I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.

Your English is actually better than some native English speakers, so keep up the practice and good work!

hah,it's really funny to met u.
i will back contact u~~~~


thanks.
 

DeathGrind

Senior Member
Dec 20, 2010
155
34
Hmmmm METdeath, perhaps you could enlighten me (pm) the whereabouts of said recovery and other useful info.

If wanted a custom recovery and ROM on this phone since day 1 . I kinda gave up on any hope for it. Please any information to lead me in the correct direction would be greatly appreciated.
 
  • Like
Reactions: chongbos

xcaleber503

New member
Jan 19, 2015
1
0
Hello Help PLZ!!

Hello, I have a softed bricked zte overture z995. I saw in one of your replies you are familiar with reflashing this ROM. Is there any possible way that you can help guide me in fixing this problem? I'm not too familiar with all the concepts. I will be forever grateful!!! THanks!

~Caleb
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.

I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.

Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    EDIT: Here's the recovery thread.

    Original post:

    So, let me preface this with the following statements:

    I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
    I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices

    So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1

    Code:
    ls -al /dev/block/platform/msm_sdcc.1/by-name
    lrwxrwxrwx root     root              1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
    lrwxrwxrwx root     root              1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
    lrwxrwxrwx root     root              1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
    lrwxrwxrwx root     root              1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
    lrwxrwxrwx root     root              1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
    lrwxrwxrwx root     root              1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
    lrwxrwxrwx root     root              1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
    lrwxrwxrwx root     root              1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
    lrwxrwxrwx root     root              1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
    lrwxrwxrwx root     root              1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
    lrwxrwxrwx root     root              1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
    lrwxrwxrwx root     root              1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
    lrwxrwxrwx root     root              1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
    lrwxrwxrwx root     root              1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
    lrwxrwxrwx root     root              1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
    lrwxrwxrwx root     root              1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
    lrwxrwxrwx root     root              1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
    lrwxrwxrwx root     root              1970-01-06 07:55 system -> /dev/block/mmcblk0p18
    lrwxrwxrwx root     root              1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
    lrwxrwxrwx root     root              1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
    lrwxrwxrwx root     root              1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
    lrwxrwxrwx root     root              1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
    lrwxrwxrwx root     root              1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6

    I then used:
    Code:
    dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img

    I then used the CWM Recovery Builder to build a basic recovery.

    I took that image, pushed to /sdcard/rec.img and tried the following as root:
    Code:
    flash_image recovery /sdcard/recv.img
    error scanning partitions: No such file or directory
    
    flash_image mmcblk0p16 /sdcard/recv.img
    error scanning partitions: No such file or directory
    
    flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
    error scanning partitions: No such file or directory

    So I tried dd instead:
    Code:
    dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16

    Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.

    I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.

    So if someone wouldn't mind pointing me in the right direction, that would be awesome.
    1

    If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!

    Also, if you could get me /proc/config.gz, that would be awesome.
    1
    If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!

    Also, if you could get me /proc/config.gz, that would be awesome.

    Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.

    It was literally two days outside of the return to store window too.
    1
    Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.

    It was literally two days outside of the return to store window too.

    If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off :)
    Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?

    ---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------

    So, let me preface this with the following statements:

    I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
    I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices

    So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1

    Code:
    ls -al /dev/block/platform/msm_sdcc.1/by-name
    lrwxrwxrwx root     root              1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
    lrwxrwxrwx root     root              1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
    lrwxrwxrwx root     root              1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
    lrwxrwxrwx root     root              1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
    lrwxrwxrwx root     root              1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
    lrwxrwxrwx root     root              1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
    lrwxrwxrwx root     root              1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
    lrwxrwxrwx root     root              1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
    lrwxrwxrwx root     root              1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
    lrwxrwxrwx root     root              1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
    lrwxrwxrwx root     root              1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
    lrwxrwxrwx root     root              1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
    lrwxrwxrwx root     root              1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
    lrwxrwxrwx root     root              1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
    lrwxrwxrwx root     root              1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
    lrwxrwxrwx root     root              1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
    lrwxrwxrwx root     root              1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
    lrwxrwxrwx root     root              1970-01-06 07:55 system -> /dev/block/mmcblk0p18
    lrwxrwxrwx root     root              1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
    lrwxrwxrwx root     root              1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
    lrwxrwxrwx root     root              1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
    lrwxrwxrwx root     root              1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
    lrwxrwxrwx root     root              1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6

    I then used:
    Code:
    dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img

    I then used the CWM Recovery Builder to build a basic recovery.

    I took that image, pushed to /sdcard/rec.img and tried the following as root:
    Code:
    flash_image recovery /sdcard/recv.img
    error scanning partitions: No such file or directory
    
    flash_image mmcblk0p16 /sdcard/recv.img
    error scanning partitions: No such file or directory
    
    flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
    error scanning partitions: No such file or directory

    So I tried dd instead:
    Code:
    dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16

    Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.

    I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.

    So if someone wouldn't mind pointing me in the right direction, that would be awesome.

    I figured I'd go ahead and answer you problems/questions here.
    First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it. :)
    When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
    Code:
    dd if=/dev/zero of=/dev/block/mmcblk0p16
    The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy :)