Develop Bugs

[REF] Partition layout

Code:
adsp -> /dev/block/mmcblk0p16
board_info -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p42
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p37
cdma_record -> /dev/block/mmcblk0p33
cir_img -> /dev/block/mmcblk0p40
control -> /dev/block/mmcblk0p30
custdata -> /dev/block/mmcblk0p22
ddr -> /dev/block/mmcblk0p14
debug_config -> /dev/block/mmcblk0p28
devlog -> /dev/block/mmcblk0p39
dsps -> /dev/block/mmcblk0p15
extra -> /dev/block/mmcblk0p32
fataldevlog -> /dev/block/mmcblk0p27
fsc -> /dev/block/mmcblk0p34
fsg -> /dev/block/mmcblk0p19
hboot -> /dev/block/mmcblk0p11
local -> /dev/block/mmcblk0p31
mfg -> /dev/block/mmcblk0p5
misc -> /dev/block/mmcblk0p24
modem_st1 -> /dev/block/mmcblk0p25
modem_st2 -> /dev/block/mmcblk0p26
pdata -> /dev/block/mmcblk0p29
pg1fs -> /dev/block/mmcblk0p2
pg2fs -> /dev/block/mmcblk0p6
radio -> /dev/block/mmcblk0p20
radio_config -> /dev/block/mmcblk0p18
recovery -> /dev/block/mmcblk0p43
reserve -> /dev/block/mmcblk0p41
reserve_1 -> /dev/block/mmcblk0p4
reserve_2 -> /dev/block/mmcblk0p23
reserve_3 -> /dev/block/mmcblk0p44
rpm -> /dev/block/mmcblk0p8
sbl1 -> /dev/block/mmcblk0p1
sbl1_update -> /dev/block/mmcblk0p7
sdi -> /dev/block/mmcblk0p10
sensor_hub -> /dev/block/mmcblk0p38
skylink -> /dev/block/mmcblk0p36
sp1 -> /dev/block/mmcblk0p12
ssd -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p45
tool_diag -> /dev/block/mmcblk0p21
tz -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p47
wcnss -> /dev/block/mmcblk0p17
wifi -> /dev/block/mmcblk0p13
Sent from my HTC One_M8 using Tapatalk

What exactly is this?
Sent from my HTC One_M8 using XDA Premium 4 mobile app

[SGP512][SYS DUMP] 17.1.1.A.0.402 + kernel + partition list

partition list:
Code:
B2B -> /dev/block/mmcblk0p25
DDR -> /dev/block/mmcblk0p17
FOTAKernel -> /dev/block/mmcblk0p16
LTALabel -> /dev/block/mmcblk0p18
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p5
alt -> /dev/block/mmcblk0p8
apps -> /dev/block/mmcblk0p22
boot -> /dev/block/mmcblk0p14
cache -> /dev/block/mmcblk0p24
dbi -> /dev/block/mmcblk0p4
fsg -> /dev/block/mmcblk0p21
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
ramdump -> /dev/block/mmcblk0p15
rpm -> /dev/block/mmcblk0p6
s1sbl -> /dev/block/mmcblk0p3
sbl1 -> /dev/block/mmcblk0p2
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p26
Original kernel: https://drive.google.com/file/d/0B8rpJsF4EG0YLXV4bi1FRC04V0k
System dump: https://drive.google.com/file/d/0B8rpJsF4EG0YTFItSXRkTVZVM1E

[HELP] Create a nandroid backup (Xperia C6 Clone/China)

Hello.
So, as I described here, I success got root on this device. Now, I want a full backup in case things going bad. And obvious, a way to restore this backup.
I was searching for days for a ROM, but it simply don't exist (yet). This model have an identification (alps l1 mp6 v2 gxq6580 weg l p69) wich is used in some other devices (includings Samsung clones), so, I checked all the ROMs I found looking into /system partition on my device and comparing with /system image of the ROMs (I used SuperR's Kitchen), and none of them are equal, I mean, a lot of files (includind build.prop) are different, so there is a great chance to brick my phone if I use it.
Even if it is found, I can't restore with SP Flash Tools, because it don't work with this phone. I tried to readback, but it recognizes but never start. As the phone is a MT6580 based SoC, maybe is compatability issue also. MTK Droid Tools don't work also. It recognizes, but can't do anything (don't generate scatter, don't root, don't nothing), again maybe a compatibility also.
The stock recovery have no option to backup, and I'm afraid to flash a CWM or TWRP, because I don't know much about porting these things, and I don't have much information about partitions and these things yet. ADB while in recovery give me an unauthorized device, by the way.
The phone accept fastboot commands, but don't accept the 'fastboot boot image.img", to try a temporary recovery, it only accept the 'fastboot flash image.img'. As sayed on the thread above, the bootloader is now unlocked, by the way.
So... this the situation... Can't have backup for now. If it help you to help me, there is the result of ls -all /dev/block/platform/mtk-msdc.0/by-name/ command in adb shell:
Code:
1|[email protected]_weg_l:/ # ls -all /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-03-30 00:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-30 00:16 cache -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-30 00:16 expdb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-30 00:16 flashinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-30 00:16 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-30 00:16 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-30 00:16 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-30 00:16 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-30 00:16 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-30 00:16 nvdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-30 00:16 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-30 00:16 oemkeystore -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-30 00:16 para -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-30 00:16 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-30 00:16 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-30 00:16 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-30 00:16 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-30 00:16 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-30 00:16 secro -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-30 00:16 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-30 00:16 userdata -> /dev/block/mmcblk0p20
[email protected]_weg_l:/ #
I sucessfully (I think) dump a boot image with dd command (dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img), but I'm not sure it is 100% perfect and if it can be safely used to restore (and how to restore... maybe 'fastboot flash'?). Maybe I can dump some other images, but I don't tried yet.
If you need any other information, I reply in almost same time.
Thanks in advice.

So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!

romulocarlos said:
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
Click to expand...
Click to collapse
Hello, i have recently posted a complete ROM on needrom. https://www.needrom.com/download/sony-xperia-c6-clone-mt6580/
i guess that is the one your are looking for. Good luck and sorry for my bad englich.

Help
Rom is corrupted, is not it? It's working? tell me how to download, I thank you

[Backup] How create zImage for my htc one m8 ?

Hi,
As it said in another topics, do backup of your phone.
A scan of my config :
Code:
m8:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
adsp -> /dev/block/mmcblk0p16
board_info -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p42
cache -> /dev/block/mmcblk0p46
carrier -> /dev/block/mmcblk0p37
cdma_record -> /dev/block/mmcblk0p33
cir_img -> /dev/block/mmcblk0p40
control -> /dev/block/mmcblk0p30
custdata -> /dev/block/mmcblk0p22
ddr -> /dev/block/mmcblk0p14
debug_config -> /dev/block/mmcblk0p28
devlog -> /dev/block/mmcblk0p39
dsps -> /dev/block/mmcblk0p15
extra -> /dev/block/mmcblk0p32
fataldevlog -> /dev/block/mmcblk0p27
fsc -> /dev/block/mmcblk0p34
fsg -> /dev/block/mmcblk0p19
hboot -> /dev/block/mmcblk0p11
local -> /dev/block/mmcblk0p31
mfg -> /dev/block/mmcblk0p5
misc -> /dev/block/mmcblk0p24
modem_st1 -> /dev/block/mmcblk0p25
modem_st2 -> /dev/block/mmcblk0p26
pdata -> /dev/block/mmcblk0p29
pg1fs -> /dev/block/mmcblk0p2
pg2fs -> /dev/block/mmcblk0p6
radio -> /dev/block/mmcblk0p20
radio_config -> /dev/block/mmcblk0p18
recovery -> /dev/block/mmcblk0p43
reserve -> /dev/block/mmcblk0p41
reserve_1 -> /dev/block/mmcblk0p4
reserve_2 -> /dev/block/mmcblk0p23
reserve_3 -> /dev/block/mmcblk0p44
rpm -> /dev/block/mmcblk0p8
sbl1 -> /dev/block/mmcblk0p1
sbl1_update -> /dev/block/mmcblk0p7
sdi -> /dev/block/mmcblk0p10
sensor_hub -> /dev/block/mmcblk0p38
skylink -> /dev/block/mmcblk0p36
sp1 -> /dev/block/mmcblk0p12
ssd -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p45
tool_diag -> /dev/block/mmcblk0p21
tz -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p47
wcnss -> /dev/block/mmcblk0p17
wifi -> /dev/block/mmcblk0p13
So i have already do a backup of all partition (to .bin files) but as it said in the folliwing topic,
https://forum.xda-developers.com/showthread.php?t=2450045
If the partition is formatted as ext3/4 then the dumped partition will have .img as an extension.
Other partition dumps have different extensions; examples:
radio.bin
param.lfs
Sbl.bin
zImage (without extension)
Click to expand...
Click to collapse
What's possible to launch for zImage (without extension)? The following command ?
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/mfg of=mfg.zImage
or just .img extension file is okey for reflashing ?
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/mfg of=mfg.zImage
A script already exist to backup all partition ? an example : https://forum.xda-developers.com/showthread.php?t=2073775
--------------------------------------------------------------------------------------------------------
Moroever, can we create .tar.md5 for flashing BL, AP, CSC, ?
The following old code, we can create .tar.md5 files with X part.
A template exist for htc one m8?
https://forum.xda-developers.com/showthread.php?t=2417603%3Cbr%20/%3E[Backup%20Script]Backup%20all%20paritions%20on%20i9505%20to%20odin%20rom
Code:
echo "Making compressed tar ball"
busybox tar -cz NON-HLOS.bin modem.bin sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn system.img.ext4 recovery.img boot.img cache.img.ext4 > odin-${GETDATE}.tar.gz
echo "Writing MD5 sums..."
busybox md5sum -t odin-${GETDATE}.tar.gz >> odin-${GETDATE}.tar.gz
echo "Renaming..."
busybox mv odin-${GETDATE}.tar.gz odin-${GETDATE}.tar.md5.gz

Help me, i need a backup of /dev/block/mmcblk0p7 , of lg k10 m250

please help me, I just bricked my lg k10 2017, and I urgently need a dump file from /dev/block/mmcblk0p7 , please back up this directory/patition ,and upload it to me

To make a backup you need to run this command on terminal if=/dev/block/mmcblk0p7 of=/sdcard/aboot.img , and pls send me the aboot.img via email [email protected]

aboot?
OP -> /dev/block/mmcblk0p48
boot -> /dev/block/mmcblk0p13
cache -> /dev/block/mmcblk0p47
cust -> /dev/block/mmcblk0p44
efuse -> /dev/block/mmcblk0p34
eksst -> /dev/block/mmcblk0p26
encrypt -> /dev/block/mmcblk0p27
expdb -> /dev/block/mmcblk0p18
factory -> /dev/block/mmcblk0p33
flashinfo -> /dev/block/mmcblk0p50
frp -> /dev/block/mmcblk0p45
ftm -> /dev/block/mmcblk0p4
keystore -> /dev/block/mmcblk0p23
laf -> /dev/block/mmcblk0p11
lgfota -> /dev/block/mmcblk0p31
lk -> /dev/block/mmcblk0p9
lk2 -> /dev/block/mmcblk0p10
lo_bak_go -> /dev/block/mmcblk0p17
logo -> /dev/block/mmcblk0p16
md1arm7 -> /dev/block/mmcblk0p42
md1dsp -> /dev/block/mmcblk0p41
md1img -> /dev/block/mmcblk0p40
md3img -> /dev/block/mmcblk0p43
metadata -> /dev/block/mmcblk0p39
misc2 -> /dev/block/mmcblk0p3
mpt -> /dev/block/mmcblk0p30
nvcfg -> /dev/block/mmcblk0p37
nvdata -> /dev/block/mmcblk0p38
nvram -> /dev/block/mmcblk0p5
oemkeystore -> /dev/block/mmcblk0p20
para -> /dev/block/mmcblk0p12
persist -> /dev/block/mmcblk0p36
persist_lg -> /dev/block/mmcblk0p29
proinfo -> /dev/block/mmcblk0p1
protect1 -> /dev/block/mmcblk0p7
protect2 -> /dev/block/mmcblk0p8
rct -> /dev/block/mmcblk0p32
recovery -> /dev/block/mmcblk0p14
recoverybak -> /dev/block/mmcblk0p15
seccfg -> /dev/block/mmcblk0p19
secro -> /dev/block/mmcblk0p21
spare1 -> /dev/block/mmcblk0p2
spare2 -> /dev/block/mmcblk0p6
spare3 -> /dev/block/mmcblk0p22
spare4 -> /dev/block/mmcblk0p28
spare5 -> /dev/block/mmcblk0p35
system -> /dev/block/mmcblk0p46
tee1 -> /dev/block/mmcblk0p24
tee2 -> /dev/block/mmcblk0p25
userdata -> /dev/block/mmcblk0p49
Click to expand...
Click to collapse
And if it's bricked, how you restore that partition?

CXZa said:
aboot?
And if it's bricked, how you restore that partition?
Click to expand...
Click to collapse
I 'll use lglaf in linux

CXZa said:
aboot?
And if it's bricked, how you restore that partition?
Click to expand...
Click to collapse
Protect1 and Protect2 is same? A backup?

JunioJsv said:
Protect1 and Protect2 is same? A backup?
Click to expand...
Click to collapse
Not quite the same. There are texts that say the partition name in them.
No idea if a copy from a different device works at all.
That is, what they are used for... these protects...
Have you tried LGUP using refurbish mode?
It should do some wiping before writing.
Or LGBridge?
>LGlaf
Haven't been able to write a partition with that, in windows.
It "writes", that is, it takes its time but it doesn't stick...
I could write into some partitions in terminal mode,
but not into boot and recovery etc.
Now, with root writing into those partitions is possible but useless.
Corrupted, not trusted, whatever errors if them are modified...
Bootloader...

CXZa said:
Not quite the same. There are texts that say the partition name in them.
No idea if a copy from a different device works at all.
That is, what they are used for... these protects...
Have you tried LGUP using refurbish mode?
It should do some wiping before writing.
Or LGBridge?
>LGlaf
Haven't been able to write a partition with that, in windows.
It "writes", that is, it takes its time but it doesn't stick...
I could write into some partitions in terminal mode,
but not into boot and recovery etc.
Now, with root writing into those partitions is possible but useless.
Corrupted, not trusted, whatever errors if them are modified...
Bootloader...
Click to expand...
Click to collapse
Lgup wont work in my case. Already "unblock" the phone or simply gave a dd if=/dev/block/mmcblk0p8 of=/ if=/dev/block/mmcblk0p7 with lglaf and the revible phone

JunioJsv said:
Lgup wont work in my case. Already "unblock" the phone or simply gave a dd if=/dev/block/mmcblk0p8 of=/ if=/dev/block/mmcblk0p7 with lglaf and the revible phone
Click to expand...
Click to collapse
:highfive:

I fixed the same problem with the help of this forum, Thank you so much!.