Database Info

[Q]How to install Flash ClockworkMod Recovery on M701 (Apad)?

Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.

Custom Recovery Image
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.

Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.

Adb push issues
Clookeno said:
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.
Click to expand...
Click to collapse
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?

read only file
adb shell mount -o remount,rw /dev/block/mtdblock3 /system

The /nand folder needs to be read-writeable....since you use z4root go into temporary root and the push the file into /nand folder

Locobox said:
Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.
Click to expand...
Click to collapse
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....

poole699 said:
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?
Click to expand...
Click to collapse
poole699,
I have tried everything you can think of to put CM6 on the 2.2 Haipad firmware (which is really a modded 2.1) and had no luck. Either the system directories are all messed up or they locked the ability to edit it somehow. If you figure it out let me know because i have wanted to try it for a while.
I have a working team telechips 2.2 with market and correct orientation settings but it took ALOT of trial and error. If you go that route make sure you back-up your pointercal file because if you do not you will likely have to go back to an official release, save it, and try the telechips mod again...
Good luck

Clookeno said:
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....
Click to expand...
Click to collapse
Thanks again for the info, but I'm not familiar with ADB. The procedure seems difficult for me hope this thread helps a lot of other users!
Again thanks for the response.

M701 Screen Flip
Hi guys, I've got a bit of a problem with my M701 tablet. I did a factory reset the other day and now the digitizer is inverted. The screen works fine but when I touch the top it senses the bottom & left = right.
This is a complete pain in the arse.
I plugged the unit into a keyboard via the usb port as a workaround until I could get into it to try to resolve the issue but I'm now stuck in a loop at the sign in to google bit. Every time I sign in it takes me back to the sign in page.
This is also a complete pain in the arse.
It doesn't have clockworkmod installed and so when I tried to install update.zip as per the above post, it comes up with 'E:Failed to verify whole-file signature' error message and aborts.
Again, a complete... you get the picture...
So, I'm slightly frustrated with it to say the least and was wondering if any of you intelligent types could either point me in a suitable direction that doesn't involve the bin. Or a window...
Many thanks in advance.

Help
Locobox said:
Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.
Click to expand...
Click to collapse
How were you able to root your apad with Z4? I was not able to find the setting to activate the USB Debugging?
Thanks,
~b

is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?

ljohnso16 said:
is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?
Click to expand...
Click to collapse
I'm not sure if this of help to you, but I have a M701 2Gb (probable fake version), I've messed around with the basics on my exploring Android type thread:
http://forum.xda-developers.com/showthread.php?t=1004824
I've put recovery on both 2.1 and 2.3 roms (need different versions). Any other q's then let me know, I don't know much yet but learning the best i can.
A very useful place for info on the M701 is here:
http://www.androidtablets.net/forum/groups/11-haipad-m701-m701-r.html

Help me dump file backup LG LS996?

hi all
bricking my phone after flash rom TOT
Can you help me dump file backup?
unbrick my phone
my phone: LS996
adb commands dump
adb shell
su
dd if = / dev / block / mmcblk0 of = / sdcard / dump.img bs = 1024 count = 2.048 million
Click to expand...
Click to collapse

Please help me

If you are unable to get a shell and view the different partitions, probably not a good sign. There are a few utilities for data recovery, but most are going to require functioning ADB with root access to be able to recover anything. And my experience with that has not been great. You can of course image the file system if you have root access and can get to a shell, as you show above. What is going on here? Are you able to get into recovery? ADB shell? Root access? More info needed please!

lyphe said:
If you are unable to get a shell and view the different partitions, probably not a good sign. There are a few utilities for data recovery, but most are going to require functioning ADB with root access to be able to recover anything. And my experience with that has not been great. You can of course image the file system if you have root access and can get to a shell, as you show above. What is going on here? Are you able to get into recovery? ADB shell? Root access? More info needed please!
Click to expand...
Click to collapse
My phone hard brick driver qualcomm 9008
i write full partition to emmc not ok
so I need 1gb or 2gb full backup dump to load the eMMC
you have ls996 please help dump backup
thanks

even i bricked my LS996
androidhero.vn said:
my phone hard brick driver qualcomm 9008
i write full partition to emmc not ok
so i need 1gb or 2gb full backup dump to load the emmc
you have ls996 please help dump backup
thanks
Click to expand...
Click to collapse
even i bricked my ls 996 plzzzzzz help

bump mine is bricked too

Hi I just flashed zv5 tot over official zv7 & my phone is not even turning on , seems like a dummy phone , can I do anything to get it back to life please , please help please

seems like no one unbricked the ls996 yet . correct ?

Sunnyartwani said:
seems like no one unbricked the ls996 yet . correct ?
Click to expand...
Click to collapse
Can you help me creat dump file backup?
my phone is hard birck
model: LS996
adb commands backup for file dump
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/dump_ls996.img bs=512 count=2000000
Click to expand...
Click to collapse
thank you!

Stock and Rooted system.img files for H81010b

I am currently running the H810 using the H81010b firmware. I made a backup of my system.img, rooted it, and then flashed the rooted img file to my device successfully. There is another thread in this section where the OP states that the b version he posted does not work/was reported to bootloop someone's device. So I'm posting mine since it does work, and also my stock image if anyone on H81010b wants to go back to stock. You can find them on my Google Drive here:
https://drive.google.com/folderview?id=0B_6vrGzPIkXlMEJhdXVkcVl3U2s&usp=sharing
Here is the hash/md5 info of each file:
Code:
rootedsystem.zip
CRC32: AA14482B
MD5: FDD6E3EE35D1064BAA32D8F1CE129FF9
SHA-1: 2596B99A0A3E4453B0F41D909C69D082143A9CEB
system.zip
CRC32: D74F4F31
MD5: 665B4D237EBCB00A51FEF0BEE53A7E1E
SHA-1: EA74981E2ADC038FF7453D41A998E9B65CFF70EE
Feel free to make a mirror of these files whoever wants to!!!!
INSTRUCTIONS
Just unzip them to your INTERNAL STORAGE and from download mode do:
Code:
dd if=/data/media/0/[COLOR="Blue"]rootedsystem.img[/COLOR] bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
Then when it's done it will bring you back to the "#" prompt, then just type LEAVE and press enter and your phone will reboot. As stated here:
http://forum.xda-developers.com/g4/...on-root-lg-t3164765/post62028523#post62028523
Please MAKE SURE to set the "rootedsystem.img" filename in the command above to match the name of the file you want to flash after unzipping them!!!!
Remember UNZIP THE FILES FIRST!!!!!!!!!!!!!!!!!!!!! And unzip them to your internal storage.
DO NOT FLASH THE ZIP FILES DIRECTLY!!!!!!!!!!!
Also from what I understand this will ONLY WORK if you are already using the same firmware (H81010b).
DO NOT flash this over a different version firmware!!!!
Also, proceed at YOUR OWN RISK!!! I am not responsible if this bricks your device, causes your house to fall into a sinkhole, makes your cat have babies, etc.. usual disclaimer.
In general my rooted system.img file is probably not really needed since people can create their own if they have a working phone using the instructions on this thread:
http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2 and would be the preferred method since you're using your own system.img file you created directly from your own phone, although in theory it should be exactly the same as my system.img file.
However my stock system.img of the H81010b might be of more use to some people who maybe didn't make a backup of their system.img file and want to return to stock
I have also successfully been able to mount these images in windows via "Linux Reader" found here http://www.diskinternals.com/linux-reader/ ! Have fun.

Thank you, I've been searching everywhere for a confirmed H81010b root. I saw the root injection method but it again referred to a post that didnt list the dd code for the 10b. I was actually just downloading the kdz file to flash it to another version just to be able to root it. I'm still pretty novice to this, so any less steps i can possibly mess up is nice too.

Oh my gosh it works, really thank you!

ISoleda said:
Oh my gosh it works, really thank you!
Click to expand...
Click to collapse
You're welcome ?

disclaimer: I've never rooted a phone.
This part is unclear. Can you elaborate?
from download mode do:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=6so on and so forth
I found instructions for getting into download mode. What program do I use to send those commands to the phone?
EDIT: nevermind. I found the LG Root tool that does this.

I'm noob
What do you mean with "this will ONLY WORK if you are already using the same firmware"? So, if I'm in the H81010o version it will simply not work?
If not, can I first downgrade my phone to your "normal" version with LGUP and then flash the rooted image? I'm just a bit confused

Leviathan555 said:
What do you mean with "this will ONLY WORK if you are already using the same firmware"? So, if I'm in the H81010o version it will simply not work?
If not, can I first downgrade my phone to your "normal" version with LGUP and then flash the rooted image? I'm just a bit confused
Click to expand...
Click to collapse
You have to already be on the B firmware otherwise you will brick. I don't remember if it's possible to downgrade to b from o.

link not available
Does anyone has this rooted for H81010b ? the link does not exist anymore.

link invalid

please upload again as the link no longer is working please !

@petermg could you explain how did you view/find the numbers bs=8192 seek=65536 count=579584
bs = write bytes per block?
seek = start point?
count = length?
could you make an example in terminal ( line of code ) to find this address points?
thanks in advance!

b8engl said:
@petermg could you explain how did you view/find the numbers bs=8192 seek=65536 count=579584
bs = write bytes per block?
seek = start point?
count = length?
could you make an example in terminal ( line of code ) to find this address points?
thanks in advance!
Click to expand...
Click to collapse
I didn't. I got it from here:
https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765

[GUIDE] Convert ASUS ZenPad 3S 10 Z500M (P027) from CN to WW

Convert your ZenPad 3s 10 from CN to WW firmware​
This guide will show you how to flash the WW firmware to your ZenPad Z500M that came preloaded with the CN (China) ROM. Up until recently, this was problematic because the CN firmware, as well as the 13.x series in general, is locked down. It does not provide flashing access via the common methods like unlocking+fastboot, recovery or SP Flash Tool. But thanks to a MediaTek temporary root tool invented by some evil genius, it's now possible to upgrade your CN ZenPad to the latest WW ROM. It's well known that this variant comes with Google apps and is fully unlockable and rootable.
DISCLAIMER
Any procedures described in this thread are done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from software bugs.
REQUIREMENTS
An ASUS ZenPad Z500M (P027) tablet with 13.x firmware
Either:
A PC with ADB installed to interact with your device, or
A terminal emulator app
Familiarity with ADB (if using PC) and basic Linux shell commands
Familiarity with the Thanks button under XDA posts
INSTRUCTIONS
Read and understand this whole procedure before you start. This is about as dangerous as installing a full OTA update, and you would have to try hard to mess it up in a way that your device cannot be recovered. But keep in mind that it is a possibility. Make sure your battery has decent charge or plug it into the charger.
Go to Amazing Temp Root for MediaTek ARMv8 and read the directions on how to open a root shell in ADB or a terminal emulator app, and make sure you understand them. Download the latest release of mtk-su. Support the developer.
Download and unzip the recovery image to your tablet. Link below.
Open a root shell and flash the image to your recovery partition with:
Code:
dd if=recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery bs=1048576
You may need to specify the full path of the img file.
Download the latest 14.x WW firmware from ASUS' support site. Link below.
Put the official zip package in the root of your internal storage. Rename the file by changing the letters "WW" to "CN". That is, rename UL-P027-WW-14.0210.1806.33-user.zip to UL-P027-CN-14.0210.1806.33-user.zip. This has to be done in the same boot session as the recovery flashing step.
At this point, the OS updater should detect the file, prepare the upgrade and ask you to reboot. Confirm that you want to reboot to install. Make sure that you have succeeded step 4.
Your tablet will reboot and automatically install the WW 14.x package. You may need/want to do a factory reset after this.
Alternative method to zip file autodetection: reboot to recovery and do an adb sideload install.
NOTES
Do not try to install any 13.x firmware package using this method. That's because if something goes wrong and your device fails to boot, you would not be able to get root access to repair it. It may be next to impossible to recover it. The 13.x releases are locked down, unlike the 14.x (Android 7) ones.
If for any reason you reboot your tablet after doing the dd flashing step but before successfully installing the 14.x ROM, your original recovery will get restored. You will have to flash it again before trying the upgrade.
Do not try to downgrade from a 14.x FW to 13.x via TWRP. It is a fact that this will make your tablet unbootable because the 13.x packages do not provide all the necessary images.
DOWNLOAD
WW-13.x Recovery Image
ASUS Z500M firmware downloads
CREDITS
Thanks to @lemon0o for successfully testing this method. :good:

Read-only file system error - way out?
Hi diplomatic,
Thanks a lot for sharing this beautiful method. I had two of these tablets with CN firmware and had pretty much given up on them until now.
Edit 2: I successfully used the adb sideload method to update to WW firmware. The autodetect did not work for me.
Original post:
I have had success with steps 1-4 (UID 0, selinux: permissive),
but when I am trying to paste the downloaded firmware file in root folder ( / ) I get the error Read-only file system. I pasted the renamed firmware file in /sdcard/ but the autodetection doesn't work.
I tried remounting root '/' with
Code:
mount -o rw,remount /
I was then able to paste the renamed firmware file (WW to CN) to (root) / . The autodetection still doesn't work.
Is there a guide you can point me to for adb sideload install? I have exposure to linux but haven't explored android innards much. I will keep looking.
Thanks again, really hoping I am able to make this work!

@bkmiictian, I'm glad you figured it out. (And finally have someone respond after like 8 months. ) But FWIW, the upgrade package should go into your internal shared storage to be detected. It's just following the standard installation procedure for Asus. Nothing to do with the root dir of the file system.

diplomatic said:
@bkmiictian, I'm glad you figured it out. (And finally have someone respond after like 8 months. ) But FWIW, the upgrade package should go into your internal shared storage to be detected. It's just following the standard installation procedure for Asus. Nothing to do with the root dir of the file system.
Click to expand...
Click to collapse
I had similar issues, was not clear what to do, how to make it recognized.
Here I found great detailed explanation on the asus website (can't put full link as I'm newbie support/FAQ/1011948/ )
Apart from that, great guide !! Thanks a lot!!
Spent hours before that finding a way to either root it or install Google Apps. Tried all rooting apps I could find ...

thanks for the details procedure
Please all noted the file should place under "internal shared storage" not root as seen in adb.
Details steps as provide by Asus in its FAQ:
FAQ/1011948

Hi, Thanks so much for the tutorial.
I'm also having issues with the Z500M with CN firmware.
I followed the steps until getting the selinux: permissive message on ADB.
But I'm lost on what to do with the Recovery.img & the WW 14.x firmware
I copied the files into the root directory, but I don't understand what to do next.
Edit:
Found the procedure to manually install the firmware update from Asus.
Disconnected the USB cable & it told me there was a new update.
After updating, it restarted and showed an android with the message "installing system update" but then it just gave an Error.
Then it restarted saying System update failed. Unknow error. System was restored to previous configuration.
I guess I'm doing something wrong...

I think my issue may be Step 4.
dd if=recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery bs=1048576
You may need to specify the full path of the img file.
Click to expand...
Click to collapse
That command does not seem to work.
ADB says "No such a file or directory"
If I try with this command I get an error too.
dd if=/root/recovery.img of=/dev/block/platform/mtk-msdc.0/11>
dd: /root/recovery.img: Permission denied

danielfd said:
I think my issue may be Step 4.
That command does not seem to work.
ADB says "No such a file or directory"
If I try with this command I get an error too.
dd if=/root/recovery.img of=/dev/block/platform/mtk-msdc.0/11>
dd: /root/recovery.img: Permission denied
Click to expand...
Click to collapse
Yes, this is the main point of this procedure. Where did you extract recovery.img? If it's, say, in your internal storage, you may need to specify
dd if=/storage/emulated/0/recovery.img of=/dev/block.....
Only reboot to install the FW if you have succeeded with this step.

diplomatic said:
Yes, this is the main point of this procedure. Where did you extract recovery.img? If it's, say, in your internal storage, you may need to specify
dd if=/storage/emulated/0/recovery.img of=/dev/block.....
Only reboot to install the FW if you have succeeded with this step.
Click to expand...
Click to collapse
Thanks Diplomatic
The new code seems to work for me.
dd if=/storage/emulated/0/recovery.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery bs=1048576
Click to expand...
Click to collapse
I still get an Error when I try to update to the WW firmware.
Will try the whole process from the beginning.
EDIT:
It worked!
Thanks a lot Diplomatic!
I made a factory reset to the tablet & followed again the steps & the update was successful.

So if I had 14x on Android 7, can I just move to the twrp recovery part of the forum, why not just manually update to 14x from 13x if 14x can be unlocked? Am I missing something?

Need help pulling boot and recovery images.

I have a device that has not been officially released yet so no images are available. I am trying to pull the boot and recovery images from the device so I can root and build twrp for it. That way when it is officially released it will be available. From there I would like to build a custom ROM or GSI.
I have read a lot of information and cannot seam to locate the correct location of the boot or recovery images. I have a prerooted GSI so I have root access to pull the images. The GSI with root has problems on my device. I have found a working GSI but I need my boot image to root it.
If someone could help me out pulling the boot and recovery images I would be greatly appreciative. I mostly figure out a lot of things on my own by searching and trying. I just cannot seam to figure this one out. Location of the images is the biggest problem.

Well, the boot and recovery partitions aren't mounted when Android is actually running.
The location of both the recovery.img and the boot.img is partition-layout dependent: possible partiton layouts are MTD ( read: Memory Technology Device ), EMMC ( read: Embedded Multimedia Card ) and MMC ( read: Multimedia Card ).

jwoegerbauer said:
Well, the boot and recovery partitions aren't mounted when Android is actually running.
The location of both the recovery.img and the boot.img is partition-layout dependent: possible partiton layouts are MTD ( read: Memory Technology Device ), EMMC ( read: Embedded Multimedia Card ) and MMC ( read: Multimedia Card ).
Click to expand...
Click to collapse
Thanks for your reply. I believe I have read about payload dumpers that can do this? I have not been able to figure it out though. What would be the easiest way to pull them?

Can anyone explain how to go about this?

Never have occupied with payload ...
FYI:
A phone's NAND-flash chip is parted into physical blocks what are called block devices: hence you have to find out the name of the block device where recovery and/or boot is located. Take note these names ( e.g. /dev/block/XXX ) are different on phones.
Once you got the names, and IF PHONE IS ROOTED, and phone's internal memory got mounted as RW, then you can extract these to your computer utilizing ADB commands:
Code:
adb devices
adb exec-out "dd if=/dev/block/<BOOT> of=C:\COPY-of-BOOT.img bs=4096"

jwoegerbauer said:
Never have occupied with payload ...
FYI:
A phone's NAND-flash chip is parted into physical blocks what are called block devices: hence you have to find out the name of the block device where recovery and/or boot is located. Take note these names ( e.g. /dev/block/XXX ) are different on phones.
Once you got the names, and IF PHONE IS ROOTED, and phone's internal memory got mounted as RW, then you can extract these to your computer utilizing ADB commands:
Code:
adb devices
adb exec-out "dd if=/dev/block/<BOOT> of=C:\COPY-of-BOOT.img bs=4096"
[/cod
[/QUOTE]
Click to expand...
Click to collapse
jwoegerbauer said:
Never have occupied with payload ...
FYI:
A phone's NAND-flash chip is parted into physical blocks what are called block devices: hence you have to find out the name of the block device where recovery and/or boot is located. Take note these names ( e.g. /dev/block/XXX ) are different on phones.
Once you got the names, and IF PHONE IS ROOTED, and phone's internal memory got mounted as RW, then you can extract these to your computer utilizing ADB commands:
Code:
adb devices
adb exec-out "dd if=/dev/block/<BOOT> of=C:\COPY-of-BOOT.img bs=4096"
Click to expand...
Click to collapse
Awesome thank you. When I installed a roasted gsi I seen them. I just did not know which one was recovery and which was the boot img. If I reinstall the rooted gsi and take a screenshot of the directory can you help me with the proper commands to copy them? This is just above my knowledge. Once I get them I can figure out how to use them.

Look also inside here:
[Guide] Dumping boot.img & recovery.img using dd (for complicated partitions)
Hi there! i am new to forums as well as in developing. i have recently taken interest in making cyanogenmod for my device. So, i have been searching web for hours to dump boot.img and recovery.img for my device. As my device is a mediatek device...
forum.xda-developers.com

jwoegerbauer said:
Look also inside here:
[Guide] Dumping boot.img & recovery.img using dd (for complicated partitions)
Hi there! i am new to forums as well as in developing. i have recently taken interest in making cyanogenmod for my device. So, i have been searching web for hours to dump boot.img and recovery.img for my device. As my device is a mediatek device...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for all your help. I will give this a try and see if I can figure it out. I appreciate you taking the time to show me and help me.