yashsingh1/xdaforums huggingface dataset:
[G2 General] lorddm:
Hi Richard.

It work.

Thank you.

--------------------------------------

LG G2 D802 (International vers.) rooted
[G2 General] benjmiester:
Would this work on the tmobile ver too? I just rooted, what files do I look for? Are there paramaters for the phone speaker volume?
[G2 General] amorek13:
yes it does, just follow the instractions, line numbers are different, start looking around 5404 if i remember correctly
[G2 General] spinedoc:
Anyone know which entry would increase the speaker volume for Google Voice? I increased the speaker volume and it seems to have helped, but when I play Google Voice over speakerphone it is still very quiet, quieter than the stock speaker settings even.
[G2 General] benjmiester:
It sure does! Thanks man. It was actually around 5335ish for me. That and i'm using viper audio mod as well. Between the two, my speaker is loud as hell now. I eqd out a little of the low end to help make sure it doesn't distort.
[G2 General] joemagistro:
edited mine to 64 to be safe.... works great! thanks!
[G2 General] ericdabbs:
Which setting name is it in the file to edit the Bluetooth headset Rx volume?
[G2 General] pbedard:
Confirmed works on sorints g2
[G2 General] diehardbattery:
Excuse my ignorance but I'm having a bit of trouble figuring out how to set the permissions correctly. I'm using root explorer... Where should the check marks be?
[G2 General] pbedard:
Think it works in all devices

---------- Post added at 03:33 PM ---------- Previous post was at 03:33 PM ----------

Exactly where they are
[G2 General] diehardbattery:
Okay, I'm stuck. I try to save the file with 920 Text Editor and it keeps failing saying it's read only...Nevermind, I got it...
[G2 General] aj522:
My Verizon g2 was already set at 65
[G2 General] xip2:
How do you compare the loudness with this mod in comparison to S4 and even htc One?
[G2 General] mrbickers:
boosting bt headset volume

What would a typical bluetooth headset (not stereo bt headphones) be called in the device list in the snd_soc_msm_Taiko file? Or does the volume level for bluetooth have anything to do with this file since the speaker is actually being driven by the headset and not the phone? I think that it would because the volume buttons on the headset control the volume on the phone. So if we edit the volume settings for the appropriate device in the snd_soc_msm_Taiko file, shouldn't we be able to increase (or decrease) the max bt volume in the same way we increase speaker volume via this thread?

In other words, is there a comprehensive list of what the devices in snd_soc_msm_Taiko actually refer too?
[G2 General] zounduser:
Bri. U have a g2 as well? Lol. Nice. Thinking of buying a Verizon model. A user confirmed this morning it will work on ATT
[G2 General] bri315317:
Yes i do, i actually prefer the G2 [ Dont tell the others] hahahaha :)
[G2 General] dj-P:
I have the same problem, could you tell me how you fixed it?
[G2 General] dj-P:
ok, i did it with 920 editor by adding a space after the number. This allowed me to save it. But I've noticed that this changed the permission into rw rw r. Is this problem?
[G2 General] sqlpro:
i've same question? my permission changed too! would that cause any issue? thanks for the advise.
[G2 General] al2fast:
anyone get the volume mod to work after kitkat upgrade? I'm on the Verizon variant, worked great before KitKat and now I've tried it again and no luck. Had to be the most useful root mod I did. To be clear I was trying to increase the headset volume again.
[G2 General] chaki-:
I was browsing and saw this thread. D802 here. That is my factory setting. Never had any complains about the volume on my phone and thanks to this thread i find out it is not necessary to change anything
[G2 General] al2fast:
I just installed twrp and zipped the file from this thread and got increased volume back:

http://xdaforums.com/showthread.php?t=2701745
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Hi everyone. I have a GT-I9300 Int'l version. The phone had worked previously with a custom rom, however' the previous owner tried to update through kies and now the phone is showing an error and asking to recover with kies. I tried that, and it fails. Also, i downloaded the stock rom for it from sammobile and the flash fails after about 2/3 of the way through.

How do i fix this? :confused:

I appreciate any and all help !
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Internal NAND failure. Needs repair.

Maybe try to flash the recovery OS+ PIT first as nothing else will work as a software fix.

http://xdaforums.com/showthread.php?t=2187081&highlight=recovery+pit
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Ok i tried. The repartition fails. Any other suggestions?
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Yes. Send for repair

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
So basically what you are saying is that i need to replace the Nand chip?
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Yes = new motherboard

Warranty say it was updating via Kies and failed
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
So if I understand, the NAND failure is actually the motherboard and that needs to be replaced correct?
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Its the eMMC NAND Flash memory that is broken and needs replacing, however as this is soldered onto the motherboard, it is easier to replace the motherboard - which is what Samsung usually do.
[Galaxy S III Q&A, Help & Troubleshooting] tigerporc:
You should be able to get a brand new motherboard with warranty claim (hope your binary download count is NO or 0 count)
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Well, I checked with Samsung Repair Center and I do have warranty on the phone. BUT, the Binary Counter shows 1 as the you can see in the pic. Any suggestions?
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
There's nothing you can do.

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Sorry if this is an inappropriate question, but what about if I try to get the phone to hard brick?
[Galaxy S III Q&A, Help & Troubleshooting] sriram231092:
this is developers site buddy not destroyers site. that's not a fine question to ask. :fingers-crossed:
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
I know, that's why i apologized from the start about the question :o

But I've learned that sometimes we have to demo in order to rebuild. Looks like that's my case.

Thank you to everyone who answered and tried to help.

Ill try to continue on my own. :)
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
That is fraud and such posts are against XDA rules and just disguised theft anyway .
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Again, my apologies. Guess i will have to take in to local repair shop for repairs.

Thank You
[Galaxy S III Q&A, Help & Troubleshooting] Hobbygamer27:
I would try to let it warranty repair, cuz the flash counter increases at fail Kies Updates sameways.
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Well, after more searching and reading, i found some real good news. As it turns out, my GT-I9300 is from Lithuania in the EU. Apparently, Rooting and/or flashing does not void the 2 year warranty in the EU. So, I will be sending it n ASAP.

Here is the post that I got that info from if it might help anyone else.

http://xdaforums.com/showthread.php?t=1998801#

Thanks Again to everyone
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Depends as that rule applies only to the seller not to any extra warranty such as Samsung offer . Samsungs extra warranty is a limited warranty simply they will reject rooted phones .

So you return the phone to the seller see what they say if they say no its rooted then take them to court over failure to comply with EU law .At least we will then have a form of case law .

Yet to see any user get away with claiming EU covers this is why and seen multiple rejects .

Nand is damaged why one its faulty to start with or two the user has damaged it .
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
I am not talking about Samsung limited warranty. I am talking about the EU Compulsory Warranty that is in place by EU law. Let's see how this goes. :fingers-crossed:
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
It will be rejected. The EU law means nothing. Thousands of people in the EU have suffered as the "2 year compulsory warranty" IS the Samsung extended warranty, which is limited.
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Ok, so for whoever is interested, I sent the phone as is to a shop in the UK. They did refuse warranty repair as the phone has been rooted. However, not ready to give up and shell out an arm and a leg, I wrote an email to the CEO of Samsung UK explaining the situation. I got a response apologizing for the service and that they (Samsung) will repair the phone under warranty. I then spoke to the repair center and I was told that they were mistaken and thought I was talking about a Galaxy Note 2 which isn't covered if rooted, and when he realized we were talking about the Galaxy GT-I9300, it is in fact covered under warranty regardless of root state. So the phone will be fixed in 7-10 days then shipped back. :D:beer:

Update:

After hassles from Samsung UK, I finally got the phone back and its fixed!!!!!!!!!!

Chalk up a point on the board for the little guy!
[Galaxy S III Q&A, Help & Troubleshooting] scorpionhd2:
Mods, please close the thread due to no use anymore.

Thanks!
[Android Q&A, Help & Troubleshooting] ssm14293:
Hi All!!

I have a Qmoible A5Classic and I want to develop its CWM Recovery. I want to fetch its recovery by

dd if=etc of=abc

but the problem is i cannot find which partition is my recovery partition.

cat proc/partitions

shows:

major minor #blocks name
7 0 1254 loop0
179 0 3815552 mmcblk0
179 1 1 mmcblk0p1
179 2 163840 mmcblk0p2
179 3 1064960 mmcblk0p3
179 4 2028784 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 524288 mmcblk0p6
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 1949696 mmcblk1
179 25 1948672 mmcblk1p1

and

cat proc/mounts

show these:

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

emmc@android /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0

/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0

emmc@usrdata /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0

emmc@cache /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0

/dev/block/vold/179:4 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:25 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:25 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

Can anyone please point out the right partition?

PS: It is rooted.

Regards
[Android Q&A, Help & Troubleshooting] shimp208:
I would recommend running the following command as root from terminal emulator:

cat /cache/recovery/last_log

This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
[Android Q&A, Help & Troubleshooting] ssm14293:
cmd says /recovery emmc recovery (null) 0

This is what I get upon running your command:

Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0

recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
[Android Q&A, Help & Troubleshooting] shimp208:
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:

cd /dev/block/platform

Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:

msm_sdcc.1
msm_sdcc.3

Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:

ls -l /dev/block/platform/{platform directory name here}/by-name

If that command returns an output take note of the the block number that contains the recovery partition.

Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:

dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536

Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:

cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img

Let me know how the above commands work out for you :).
[Android Q&A, Help & Troubleshooting] ssm14293:
Translation: Dude!!!! Ur great!! please accept my humble gift :D :victory:

I dont have a by-name folder but only by-num, which really doesnt help. So now I will try your second method, extracting a part of the main image!! I'll tell you the result!!!

Regards
[Android Q&A, Help & Troubleshooting] ssm14293:
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please. :)

Regards
[Android Q&A, Help & Troubleshooting] shimp208:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
[Android Q&A, Help & Troubleshooting] ssm14293:
Some Luck with it...

Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:

unmkbootimg version 1.2 - Mikael Q Kuisma <kuisma@ping.se>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------

Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.

Thanks for helping out!

I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.

Regards
[Android Q&A, Help & Troubleshooting] ssm14293:
Few Questions

There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:

0x0000000000600000

but they end at different blocks, would that be a problem?

I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
[Android Q&A, Help & Troubleshooting] shimp208:
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.

I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
[Android Q&A, Help & Troubleshooting] ssm14293:
Found a way!

Hi again!!

I just got myself an 8GB memory card. I also searched more about nandroid backups for non-CWM phones. I got across onandroid, it creates img files of all partitions. It was created by someone from XDA Forums, can't remember the name. So at the moment it is generating MD5 Checksum.

After this I will create my OWN Rom and CWM for this phone :D :D :victory: , well after my finals ;).

Thanks for your help! :highfive:

For all Qmobile Rooted users, use onandroid to create backups, but at your own risk. I can confirm for QMobiel A5 Classic
[Android Q&A, Help & Troubleshooting] moniruzzaman:
where to copy symphony CWM recovery.img using dd command

:)

I am Moniruzzaman from Dhaka, Bangladesh...

Please forgive me for my weak English.

I have created a CWM recovery img (Latest Touch Version) for my rooted Symphony W85. My device partitions is similar to the Qmoible A5Classic. Now I have failed to copy it to the recovery partition as i could not figure out which is my recovery partition.

Partition Information:

preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd

dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd

mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0

ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1

pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0

nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0

seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0

uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0

bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0

recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0

sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5

misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0

logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0

expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0

ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0

android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6

cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2

usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3

fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4

bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0

recovery filesystem table

=========================

0 /tmp ramdisk (null) (null) 0

1 /boot emmc boot (null) 0

2 /cache ext4 /dev/block/mmcblk0p2 (null) 0

3 /data ext4 /dev/block/mmcblk0p3 (null) 0

4 /misc emmc misc (null) 0

5 /recovery emmc recovery (null) 0

6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0

7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0

8 /system ext4 /dev/block/mmcblk0p6 (null) 0

I have flashed the recovery.img using

dd if=mnt/sdcard/recovery.img of=/dev/recovery

. Everything was fine except my gsm signal was gone.

Then I tried flashed stock recovery.img using

dd if=mnt/sdcard/recovery.img of=/dev/recovery

- everything works fine again.

I have come so far and now i can't fine the right partitions. I am very frustrated.

Can any one please help me how to flash my CWM recovery img (Latest Touch Version) to my device as it is combined partitions.
[Android Q&A, Help & Troubleshooting] jazzespresso:
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....

Starting recovery on Thu Dec 4 03:55:45 2014

recovery filesystem table

=========================

0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0

1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0

2 /boot hidden /dev/block/platform/intel/by-label/boot 0

3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0

4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0

5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0

6 /panic raw /dev/block/platform/intel/by-label/panic 0

7 /factory ext4 /dev/block/platform/intel/by-label/factory 0

8 /misc emmc /dev/block/platform/intel/by-label/misc 0

9 /config ext4 /dev/block/platform/intel/by-label/config 0

10 /cache ext4 /dev/block/platform/intel/by-label/cache 0

11 /system ext4 /dev/block/platform/intel/by-label/system 0

12 /data ext4 /dev/block/platform/intel/by-label/data -16384

13 /sdcard vfat /dev/block/mmcblk1p1 0

14 /tmp ramdisk ramdisk 0
[Android Q&A, Help & Troubleshooting] shimp208:
I would recommend running the following command to dump your recovery partition:

cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img

Let me know if you still have questions, happy to help you out.
[Android Q&A, Help & Troubleshooting] jazzespresso:
thank you very much...what about boot.img?
[Android Q&A, Help & Troubleshooting] shimp208:
For boot you would run the command:

cat /dev/block/platform/intel/by-label/boot > /mnt/sdcard/boot.img

Hope this helps you!
[Android Q&A, Help & Troubleshooting] dihhedessa:
[MENTION=3558630]shimp208[/MENTION] and [MENTION=4758472]jazzespresso[/MENTION] maybe you guys could please help me? I am desperate!
[Android Q&A, Help & Troubleshooting] AndroGeek974:
Hi there,

I've the same problem, recovery is in mmcblk0, someone can help me please ? I can't find any solutions.

AndroGeek