yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] bobl61:
/dev/block:
dm-0
dm-1
dm-10
dm-11
dm-12
dm-2
dm-3
dm-4
dm-5
dm-6
dm-7
dm-8
dm-9
loop0
loop1
loop10
loop11
loop12
loop13
loop2
loop3
loop4
loop5
loop6
loop7
loop8
loop9
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0rpmb
mmcblk1
mmcblk1p1
mmcblk1p2
platform
vold
zram0

/dev/block/platform:
mtk-msdc.0
mtk-msdc.1

/dev/block/platform/mtk-msdc.0:
by-num
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0rpmb

/dev/block/platform/mtk-msdc.0/by-num:
p1
p2
p3
p4
p5
p6
p7

/dev/block/platform/mtk-msdc.1:
by-num
mmcblk1
mmcblk1p1
mmcblk1p2

/dev/block/platform/mtk-msdc.1/by-num:
p1
p2

/dev/block/vold:
179:0
179:1
179:128
179:129
179:130
179:2
179:3
179:4
179:5
179:6
179:7
[Android Software/Hacking General [Developers Only]] bobl61:
adb shell su -c 'cat /proc/partinfo'
tmp-mksh: cat: /proc/partinfo: No such file or directory

:eek:

I found an MT6582 scatter file, not sure if they are device specific...
[Android Software/Hacking General [Developers Only]] AlexZap:
Scatter is going to be specific to the ROM, It will tell me what all the individual partitions are... otherwise it is trial and error. It is in the partinfo file you are missing too. There is anyone other way, but we start getting in to some major work. If you are up for it, we can try a couple of things... or you can try this tool https://mega.nz/#!5NxX0BaS!W8YeeKhU1BX18lcWWQ2i6QX1eYRj3-z8G39CuW7CsLw that might work.

If it doesn't, ill get the files together that you will need to put on your phone and we can figure it out.
[Android Software/Hacking General [Developers Only]] bobl61:
I tried the SpaceMTKTool. It's pretty much doing the same thing. Looking for mtk-msdc.0/by-name, which does not exist :(
[Android Software/Hacking General [Developers Only]] bigrammy:
It would be interesting to know if this app https://play.google.com/store/apps/details?id=ma.wanam.partitions can find and correctly identify all your partitions it works on my mt6732 phone android 5.1
[MENTION=5726442]AlexZap[/MENTION]

Not sure what script it uses to find them but it seems to work on multiple devices it might be worth an indepth look. ;)
[Android Software/Hacking General [Developers Only]] bobl61:
Thanks for the info. I'll have a look...
[Android Software/Hacking General [Developers Only]] bobl61:
Here's what Partitions Backup & Restore shows...
[Android Software/Hacking General [Developers Only]] AlexZap:
...

it would be worth a try... but i don't know the method that it uses. below are the steps to do it manually (hopefully) on any phone with a GUID partition table... though you do need root for it ant it isnt for the faint of heart! if Blu hadn't obfuscated things so much, this wouldn't be such a pain in the ass.

ok, lets see... first thing you want to do is download the attached file... it is the parted binary compiled for the ARM architecture. we need parted because fdisk usually bombs out on GPT type partitions. it is compressed so we have to uncompress it.

gzip -d parted.gz

now we have to push it on to the phone and run it... we might as well make it a system bin, as it is pretty powerful. so here are the steps:

adb root
adb remount
adb push parted /system/xbin
adb shell -c "chmod 777 /system/xbin/parted"

(i had mixed luck with this... if anything copy the file directly to your phone and use a root explorer to push it to the /system/xbin folder and set the permissions)

now we want to print out the partition table... simple enough...

adb shell su -c "parted /dev/block/mmcblk0 print ignore"

if it prompts you with errors, just press "i" to ignore

copy the output and send it to me

you can either keep or delete parted at this point.
[Android Software/Hacking General [Developers Only]] bobl61:
adb shell su -c "parted /dev/block/mmcblk0 print ignore"
Error: Can't have a partition outside the disk!
[Android Software/Hacking General [Developers Only]] AlexZap:
Wow... you are just having no luck at all.

Did you try that app?
[Android Software/Hacking General [Developers Only]] bobl61:
Tell me about it :mad: I installed the app. What should I backup?

http://xdaforums.com/showpost.php?p=62591520&postcount=1698
[Android Software/Hacking General [Developers Only]] AlexZap:
Well... you don't have a gpt. This is some weird hybrid that blu probably created before there was official kit Kat from mediatek? Or who the hell really knows. But with those names, it is easy enough for me to customize my script for you... give me a bit and I'll post something that will work.
[Android Software/Hacking General [Developers Only]] bobl61:
Hehe... okay thanks :good:
[Android Software/Hacking General [Developers Only]] bigrammy:
According to bob161 screen shot it looks like he has KK 4.4.2 in which case MTKDroidtools should work out of the box :good:

Your bootimg (no dot) recovery mbr ebr2 etc etc will all be at /dev or /mmcblk0 same thing.
[Android Software/Hacking General [Developers Only]] AlexZap:
You would think, but no, it is lollipop... and it doesn't work... http://xdaforums.com/showpost.php?p=62591520&postcount=1662

That's why I think blu is using some unofficial lollipop build instead of mediatek official. There is no dumchar_info, do mtkdrt won't work, but it is also built just like the old 4.4.2 or lower ROMs. Strange for sure. The next trick will be making a scatter file.
[Android Software/Hacking General [Developers Only]] vampirefo:
Backup system, boot, recovery, from recovery you can then build twrp.

From boot you can make insecure boot, from system you can make flashable ROM.

That's really all you need, you can back up other partitions if you want but only need the 3 I posted.
[Android Software/Hacking General [Developers Only]] bigrammy:
I suspect the phone is really KK 4.4.2 faked to look like Lollipop and the dumchar_info renamed or removed to prevent Mtkdrt detecting it's true version :confused:

Edit: [MENTION=5384442]bobl61[/MENTION] and [MENTION=5726442]AlexZap[/MENTION]

Ok guys I have done some more digging around & I think I know what's happened :eek:

The phone was as we suspected on the KK 4.4.2 but probably got an OTA update to Lollipop which kept the old KK4.4.2 partition layout etc pretty clever really as most mtk ota's end in tears :D

I think you maybe able to use the scatter from the KK4.4.2 Here to pull the partitions with SPFlashtool as I dont think an OTA with stock recovery can reliabley perform a repartition :fingers-crossed:

There is another official one in the same section but not sure which best matches your specific phone so be sure to check the other Official version too.

I hope that sort of makes sense. :laugh:

Edit 2: I have attached the scatter which is from the ROM I linked above. ;)
[Android Software/Hacking General [Developers Only]] vampirefo:
I don't think that is the same phone, really the two phones look nothing a like. I also have a blu phone and it's nothing like either of the phones.
[Android Software/Hacking General [Developers Only]] bobl61:
The phone came (new) with Lollipop 5.0 installed. I didn't do any OTA updates.
[Android Software/Hacking General [Developers Only]] AlexZap:
this is true, but if you look at the list of partitions that are listed... none of these are there. dunno how they are not listed... it is very confusing. there is no boot or recovery partition.

i would agree that this is the most plausible explanation. seeing that dumchar_info is a function of the kernel, and the way that the /dev system lists the partitions is mediatek's new method... so i am certain that it is lollipop and not 4.4.2 that is just "skinned"... as far as how well this will work, however, is anyone's guess. i am using syserr's method to backup the system. you dump the whole whole mmcblk0 and then use the scatter file (which i hope is accurate) to dice up that image. you will need at least double the free space on your computer that your phone has... so if you have an 8gb phone, you will need 16gb or more free.

run the program like so:

./mtk_backup_blu.sh scatterfile.txt

where scatterfile is the scatter file that you found

it should be error free, but i cannot test, as i dont have this type of phone to test against.
[Android Software/Hacking General [Developers Only]] AlexZap:
here is the issue... it is easy enough to dump all the partitions... but with out a scatter file, it is use next to useless... there is no way to flash it with spflash tool. if you look at the list of partitions, it is very very strange, because there is no "recovery", there is no "boot", there is no "nvram"... standard mediatek partitions. there are only 7... the EBR, Protect_S, protect_F, secro, system (android), cache, and userdata. unless there are hidden partitions (which isnt unheard of) there isn't much else i can do.

thats why i think this is some quasi rom made by blu that is made from mediatek source, but isn't truly a mediatek rom. i wish i had an answer of some kind, but it leaves me kinda lost :confused::eek:
[Android Software/Hacking General [Developers Only]] bobl61:
It appears to be working:

Checking for netcat ... netcat found!
Checking for adb ... adb found!
Checking for pipeviewer ... pv found!
backing up rom

It's at 1.5GB and still running...
[Android Software/Hacking General [Developers Only]] AlexZap:
I'm not worried about it working... I'm worried about it producing viable backups.

Once done , change to the folder that holds the ROM and Itry

file system.img

If it complains that it is not a file system image, then I am stuck here.
[Android Software/Hacking General [Developers Only]] bobl61:
Checking for netcat ... netcat found!
Checking for adb ... adb found!
Checking for pipeviewer ... pv found!
backing up rom
15219712+0 records inB/s] [ <=> ]
15219712+0 records out
7792492544 bytes transferred in 7816.511 secs (996927 bytes/sec)
7.26GB 2:10:16 [ 974kB/s] [ <=> ]
cat: scatterfile.txt: No such file or directory
dd: failed to open ‘0123456789ABCDEF-20150831-205315/PRELOADER’: No such file or directory
cat: 0123456789ABCDEF-20150831-205315/preloader.bin: No such file or directory
./mtk_backup_blu_c.sh: line 34: 4 + : syntax error: operand expected (error token is "+ ")

:confused:
[Android Software/Hacking General [Developers Only]] AlexZap:
Scatterfile.txt should be the scatter file for the phone... not just a name. Use the one attached in post 1708 if you can't find a specific one. It is worth a shot.
[Android Software/Hacking General [Developers Only]] bobl61:
Yeah... the file is named MT6582_Android_scatter.txt, not Scatterfile.txt. Trying it now :fingers-crossed:
[Android Software/Hacking General [Developers Only]] bigrammy:
For Info:

The one I posted appears to have the system (Andriod) and userdata listed as yaffs.img's. :confused:
[Android Software/Hacking General [Developers Only]] bobl61:
In the event the one you posted doesn't work, I have one from My Blu Studio C HD (D535U). Can you have a look at it?
[Android Software/Hacking General [Developers Only]] bigrammy:
Yes thats yaffs also.

Did you get this OTA "BLU_D830U_V19_Generic25-06-15 11:00" If you did is it still on your device?? if so check if there is a boot.img or recovery.img included. :fingers-crossed:

Found this source for BLU roms Here I can not find your specific device though.

Maybe you could ask on the forum thread Here for the D830U. ;)
[Android Software/Hacking General [Developers Only]] bobl61:
It's a backup I have on my computer. It's BLU_D535U_V04_GENERIC. Yes, there is boot.img and recovery.img.

http://forum.gsmhosting.com/vbb/11252537-post335.html
[Android Software/Hacking General [Developers Only]] AlexZap:
there is something very very strange about the way this phone is ROMed... i would suggest posting on BLU's google plus page asking them for the original rom. https://plus.google.com/communities/117846429749085694805/stream/fdff49af-5248-458c-ba4f-7bcd2475d137.
[Android Software/Hacking General [Developers Only]] bobl61:
https://plus.google.com/117382240590217983218/posts/964C2dqcFD5
[Android Software/Hacking General [Developers Only]] bigrammy:
As AlexZap says we need the Stock boot and recovery.img for your exact device at the very least.

If you have a working adb try these cmd's

adb shell

dd if=/dev/bootimg of=/sdcard/boot.img

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

If it works you find them on the root of your sdcard check both internal and external cards.
[Android Software/Hacking General [Developers Only]] lopestom:
Please guys... What happen?

Can you stop spam on this thread?

Can you writing in your PM?

What you want?

1. Make the stock ROM?

Try SpaceTool: https://mega.nz/#!p0ZTkbQJ!W8YeeKhU1BX18lcWWQ2i6QX1eYRj3-z8G39CuW7CsLw

Tks for Simone Guarrera

Look more here: http://goo.gl/pmIBU7

Or here: http://goo.gl/kULNYV

1.1. Try NANDROID backup application:

You can test:

http://xdaforums.com/showthread.php?t=1620255

[v9.52] Online Nandroid / Nandroid Backup without re-booting [CWM + TWRP + 4EXT]﻿

2. Create Custom recoveries?

Try with files backup in 1 or 1.1 (recovery and boot)...

For many users only boot.img can help...

Of course is need ROOT, adbd insecure and patience....
[Android Software/Hacking General [Developers Only]] bigrammy:
I guess this development for this specific device should continue in a separate thread. :)

Dude we are not Noob's :laugh:

Spam! not a very good choice of words :mad:

SpaceTool does not work for the MTK BLU Studio C (D830us) hence why he posted here. :rolleyes:

Everything else needs root.
[Android Software/Hacking General [Developers Only]] bobl61:
adb shell
shell@STUDIO_C:/ $ dd if=/dev/bootimg of=/sdcard/boot.img
dd: /dev/bootimg: Permission denied

:confused:

Okay, ran it with adb insecure enabled...

adb shell
root@STUDIO_C:/ # dd if=/dev/bootimg of=/sdcard/boot.img
dd: /sdcard/boot.img: File too large
8388608+0 records in
8388607+1 records out
4294967295 bytes transferred in 1011.388 secs (4246606 bytes/sec)

It's a 32GB card (23GB available) :confused:
[Android Software/Hacking General [Developers Only]] AlexZap:
You know how to pick a winner of a device :))

Any luck with the recovery?
[Android Software/Hacking General [Developers Only]] bobl61:
This phone is a FREAK :cyclops: Same thing with recovery (file too large). What if I formatted the card to exFat?
[Android Software/Hacking General [Developers Only]] AlexZap:
Won't matter... the file sizes should be 16 megabytes each at most. You could try:

dd if=/dev/recovery of=/sdcard/recovery.img bs=1k count=16384

That should force dd to only grab the first 16 mb...
[Android Software/Hacking General [Developers Only]] bobl61:
From what I've been reading, there is a 4GB limit on Fat32 formatted sd cards...
[Android Software/Hacking General [Developers Only]] AlexZap:
There is, but we are talking mb, not gb. A size smaller. Your phone only has 8 gb of storage, iirc.
[Android Software/Hacking General [Developers Only]] bobl61:
Ummm :fingers-crossed: I now have a boot.img and recovery.img on my sdcard.

https://mega.nz/#F!Gl1STRSJ!ulX1mvUc96DMtPMx4rh-iw
[Android Software/Hacking General [Developers Only]] vampirefo:
[MENTION=5384442]bobl61[/MENTION]

what you uploaded is garbage, try below commands, and upload the files created.

dd if=/dev/bootimg of=/sdcard/boot.img bs=4096 count=4000

dd if=/dev/recovery of=/sdcard/recovery.img bs=4096 count=4000
[Android Software/Hacking General [Developers Only]] bobl61:
Uploaded new files.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5384442]bobl61[/MENTION]

Which brand/model of device is? Which is teh CPU?

Do you have a clean version of your boot.img/recovery.img file?

I can patch to make it rooted if necessary.

When you uploaded boot.img/recovery.img fir integrity file please upload it as compressed archive (zip/rar/etc)

[MENTION=2472806]vampirefo[/MENTION]

Why do you use count=4000?
[Android Software/Hacking General [Developers Only]] bigrammy:
Extracted from your good recovery pull.. :good:

Seem they changed bootimg to boot :laugh:

Recovery fastab

boot /boot emmc defaults defaults
/dev/block/mmcblk0p2 /cache ext4 defaults defaults
/dev/block/mmcblk0p3 /data ext4 defaults defaults
misc /misc emmc defaults defaults
recovery /recovery emmc defaults defaults
/dev/block/mmcblk0p4 /sdcard vfat defaults defaults
/dev/block/mmcblk0p6 /system ext4 defaults defaults
/dev/block/mmcblk0p2 /custom ext4 defaults defaults

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/emmc@android /system ext4 ro wait
/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/emmc@protect_f /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/emmc@protect_s /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard0:emmc@fat,noemulatedsd
/devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard1:auto
/devices/platform/mt_usb auto vfat defaults voldmanaged=usbotg:auto

Now [MENTION=5726442]AlexZap[/MENTION] knows the paths it should make things a little easier

I will port you a custom recovery tomorrow. ;)
[Android Software/Hacking General [Developers Only]] vampirefo:
To capture good recovery and boot files, can't work with garbage files.

---------- Post added at 05:39 AM ---------- Previous post was at 05:36 AM ----------

These are good files. They are usable.
[Android Software/Hacking General [Developers Only]] bovirus:
Qhat does it eman?

I just need boot.img to unlock it.
[Android Software/Hacking General [Developers Only]] vampirefo:
For a back up, one backs up recovery and boot, and system.

Once you pull recovery extract it, to find out what partition system is on, then pull system.

Once you have recovery and boot you can make custom recovery from stock recovery.
[Android Software/Hacking General [Developers Only]] yuweng:
Guys, nothing is going to work on mostly latest MT6582 or may be even MT6592 too though haven't read any on latest MTK armv8 devices, the problem is users just downloads & never feedback or feedbacks at other forums... :rolleyes:

[MENTION=5384442]bobl61[/MENTION] You came to my thread & i told you the solutions, you never bother replying & you even warn others not to use my tools, fyi, my tools, worse come to worse only bricks the recovery only, mentioned at my thread that i don't own all MTK devices on the market, i advice you to unlock the bootloader first but you never listen or do research on that, most probably, you will be sending it back to BLU for the 2nd time... :cowboy:

Updates

[MENTION=5384442]bobl61[/MENTION]

Your last reply at my thread here before you went giving warning to others here... :rolleyes:
[Android Software/Hacking General [Developers Only]] bobl61:
[MENTION=4478781]yuweng[/MENTION] What are you talking about? What thread?

---------- Post added at 11:40 AM ---------- Previous post was at 11:25 AM ----------

Now [MENTION=5726442]AlexZap[/MENTION] knows the paths it should make things a little easier

I will port you a custom recovery tomorrow. ;)

That's great :D :fingers-crossed:
[Android Software/Hacking General [Developers Only]] vampirefo:
Porting twrp shouldn't be a problem for your phone, I already built and unloaded twrp for my blu phone.
[Android Software/Hacking General [Developers Only]] bobl61:
Updates

[MENTION=5384442]bobl61[/MENTION]

Your last reply at my thread here before you went giving warning to others here... :rolleyes:
[MENTION=4478781]yuweng[/MENTION] Neither of those posts were directed at you. I simply didn't want anyone with the same device to make the same mistake I did. No hard feelings :fingers-crossed:
[Android Software/Hacking General [Developers Only]] yuweng:
Got a little annoyed when you mentioned you can't even recall what i was talking about, thats all, no hard feelings... ;)

i've updated my OP b'cos of you & i believe you didn't even check it out... :cowboy:

Questions & Answers

Q : OP said DO NOT USE IT ON LOCKED BOOTLOADER but the link doesn't say much for MTK devices.

A : There isn't any guide to identify locked bootloader on MTKs, generally you'll have to flash the recovery.img to find out whether it bricks ! However, farenheith has confirmed by flashing back the original stock 3e recovery.img & his locked bootloader MTK Motorola boots back !

To check your bootloader

adb reboot-bootloader [COLOR="Blue"]or[/COLOR] adb reboot bootloader [COLOR="blue"]or[/COLOR] adb reboot fastboot
[COLOR="Blue"]fastboot getvar all[/COLOR]

(bootloader) unlocked: NO

To unlock it, use below command.

fastboot oem unlock

i've seen some mentioned on their MTK when rebooting to recovery, there will be a menu to select either fastboot or recovery or normal so select fastboot then above command to check whether it is locked...

Source
[Android Software/Hacking General [Developers Only]] vampirefo:
I haven't seen a blu Walmart phone with a locked bootloader.
[Android Software/Hacking General [Developers Only]] bobl61:
Didn't get it at Walmart :p
[Android Software/Hacking General [Developers Only]] vampirefo:
K, I can get same phone at Walmart, unlocked.
[Android Software/Hacking General [Developers Only]] AlexZap:
here is a block level backup script based on this mapping. dunno what the misc partition is. and there is no NVRam listed, so i am figuring it is /dev/nvram. same with the EBR1 (guessing on /dev/ebr1). if anything fails, let me know. i have no idea how accurate this backup will be, but i still say it is next to useless without a scatter file for the device, and i have no idea how to generate one. you could check http://xdaforums.com/showthread.php?t=2540400 as he had some other methods then just the dumchar_info and my way of reading partinfo and reversing it. i have no idea if it will work for you.

is it weird to anyone else that cache and custom come from the same directory? anyway. enjoy.
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi at work now so limited PC usage :(

From what I can recall ebr1 has a block partition number I think it shows in the image in this post http://xdaforums.com/showpost.php?p=62591520&postcount=1698 Images are blocked for me so I cant see to confirm it. :laugh:

Not sure if nvram was listed too.

---------- Post added at 12:43 AM ---------- Previous post was at 12:38 AM ----------

It's quite normal for fastboot to wipe everything during in unlock :)
[Android Software/Hacking General [Developers Only]] AlexZap:
you are correct... that app lists mmcblk0p1 as ebr1... BUT, it also lists all the other partitions as different. the app lists this:

ebr1 -> mmcblk0p1

protect_f -> mmcblk0p2

protect_s -> mmcblk0p3

sec_ro -> mmcblk0p4

system -> mmcblk0p5

cache -> mmcblk0p6

userdata -> mmcblk0p7

and the mtab lists this

boot partition -> /boot

recovery partition -> /recovery

misc partiton /misc

cache -> mmcblk0p2

userdata -> mmcblk0p3

sdcard -> mmcblk0p4

system -> mmcblk0p6

custom -> mmcblk0p2

i don't know which to believe... but i would think the partition mapping directly from the phone's recovery image would be more correct, so i chose to go with that.

(and i found a typo or 2 in my script, so if you downloaded it, redownload it from that post.)
[Android Software/Hacking General [Developers Only]] yuweng:
Thats what i was trying to tell you but you never reply at my thread, fyi, normally i don't offer help other than my own, very bad experience, got totally ignored like i was invisible but here i saw few familiar names, AlexZap, vampirefo, bigrammy, consider yourself very lucky, so many veterans are helping you... :cowboy:

This is what bobl61 attached months ago.... :cool: