Database Develop

[reference] Moto G3 partition table

This post is just for our records. I keep having to pull it up every time I need to dump or copy a partition, so I thought I'd post it here.
drwxr-xr-x 2 root root 880 Jan 21 1970 .
drwxr-xr-x 4 root root 1000 Jan 21 1970 ..
lrwxrwxrwx 1 root root 20 Jan 21 1970 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 21 1970 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 21 1970 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 21 1970 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jan 21 1970 cache -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Jan 21 1970 carrier -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Jan 21 1970 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 21 1970 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 21 1970 customize -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Jan 21 1970 dhob -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 21 1970 frp -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 21 1970 fsc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 21 1970 fsg -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 21 1970 hob -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jan 21 1970 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 21 1970 hypBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 21 1970 keystore -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Jan 21 1970 kpan -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Jan 21 1970 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 21 1970 logs -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 21 1970 metadata -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 Jan 21 1970 misc -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 21 1970 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 21 1970 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 21 1970 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 21 1970 oem -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Jan 21 1970 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 21 1970 padB -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 21 1970 padC -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jan 21 1970 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 21 1970 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 Jan 21 1970 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 21 1970 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Jan 21 1970 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 21 1970 sp -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Jan 21 1970 ssd -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Jan 21 1970 system -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 Jan 21 1970 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 21 1970 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 21 1970 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 Jan 21 1970 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 21 1970 utagsBackup -> /dev/block/mmcblk0p15
Click to expand...
Click to collapse

I wonder why 1970. Sorry couldn't help it.
Sent from my Virgin Mobile CDMA Moto G3

@hp420 is this something often requested? I can add it to the FAQ if so. Otherwise still very helpful, cheers.

Parted log
Code:
[email protected]:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit kb
unit kb
(parted) print
print
Model: MMC QN1SMB (sd/mmc)
Disk /dev/block/mmcblk0: 7818183kB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 41943kB 41812kB ext4 modem
2 41943kB 42467kB 524kB sbl1
3 42598kB 42729kB 131kB DDR
4 42729kB 43856kB 1126kB aboot
5 44265kB 44521kB 256kB rpm
6 44646kB 45220kB 573kB tz
7 45261kB 45392kB 131kB hyp
8 45683kB 46207kB 524kB utags
9 46207kB 46731kB 524kB misc
10 46731kB 50332kB 3600kB padA
11 50332kB 51458kB 1126kB abootBackup
12 51868kB 52124kB 256kB rpmBackup
13 52249kB 52822kB 573kB tzBackup
14 52863kB 52994kB 131kB hypBackup
15 53285kB 53809kB 524kB utagsBackup
16 53809kB 55906kB 2097kB logs
17 55906kB 56431kB 524kB frp
18 56431kB 58720kB 2290kB padB
19 58720kB 60293kB 1573kB modemst1
20 60293kB 61866kB 1573kB modemst2
21 61866kB 62366kB 500kB hob
22 62366kB 62398kB 32.8kB dhob
23 62521kB 65667kB 3146kB ext2 fsg
24 65667kB 65668kB 1.02kB fsc
25 65668kB 65799kB 131kB cid
26 65799kB 66323kB 524kB metadata
27 66323kB 70518kB 4194kB logo
28 70518kB 74712kB 4194kB clogo
29 74842kB 83231kB 8389kB ext4 persist
30 83231kB 91619kB 8389kB kpan
31 91619kB 108397kB 16777kB boot
32 108397kB 125276kB 16880kB recovery
33 125305kB 125313kB 8.19kB ssd
34 125313kB 134218kB 8905kB padC
35 134218kB 142606kB 8389kB sp
36 142606kB 150995kB 8389kB keystore
37 150995kB 167772kB 16777kB oem
38 167772kB 184549kB 16777kB carrier
39 184549kB 218104kB 33554kB customize
40 218104kB 486539kB 268435kB ext4 cache
41 486539kB 2919236kB 2432696kB ext4 system
42 2919236kB 7784497kB 4865262kB userdata
One could do here repartitioning ? userdata, system, cache They are one after the other

HTCDreamOn said:
@hp420 is this something often requested? I can add it to the FAQ if so. Otherwise still very helpful, cheers.
Click to expand...
Click to collapse
Not generally. It's a simple adb shell command to get this, I just thought it may help someone. I keep a copy on my computer for reference when I'm working so I don't have to keep pulling it up in terminal.

maxprzemo said:
One could do here repartitioning ? userdata, system, cache They are one after the other
Click to expand...
Click to collapse
Yes, I suppose you could, but you may have to rebuild images with proper sizes to be compatible

Hedied4me said:
I wonder why 1970. Sorry couldn't help it.
Sent from my Virgin Mobile CDMA Moto G3
Click to expand...
Click to collapse
Unix time started on January 1, 1970, Linux/Android follows the same standard... if no time or date reference is available, it assumes It is January 1, 1970 at 00:00:00 UTC, and counts seconds from that point. To be honest, the Jan 20 part confuses me more than the 1970.

acejavelin said:
Unix time started on January 1, 1970, Linux/Android follows the same standard... if no time or date reference is available, it assumes It is January 1, 1970 at 00:00:00 UTC, and counts seconds from that point. To be honest, the Jan 20 part confuses me more than the 1970.
Click to expand...
Click to collapse
Yeah, that was my thought, as well. You would usually see dec 31 1969 but every file without a date on this device is jan 20

Could someone please tell me which of these is the bootloader? They are not clearly marked. I'd like to dump it, but I don't want to play around with it, being it's the bootloader, and all. I dump the wrong one and flash it and buh bye phone, you know?

hp420 said:
Yeah, that was my thought, as well. You would usually see dec 31 1969 but every file without a date on this device is jan 20
Click to expand...
Click to collapse
Woodstock?

Can someone provide the results to the following commands:
adb shell
su
(grant su permission on phone)
ls -l /dev/block/platform​

@lost101
Code:
[email protected]_umts:/ # ls -l /dev/block/platform
lrwxrwxrwx root root 1970-04-22 06:56 msm_sdcc.1 -> /dev/block/bootdevice
drwxr-xr-x root root 1970-04-22 06:56 soc.0

Bricked P10 lite (tried to flash C432 on C109)

Hello,
I tried to flash C432 ROM on my current C109 ROM, but the Update.app process always fails at 5%...
I extracted update.app,
I tried to flash with fastboot but I probably made something wrong when I tried to wipe data/factory reset with factory recovery...
I can only flash boot / recovery / cust / system
My issue is now the ROM tries to boot, then bootloop to eRecovery...
I can't find a way to revive it...
I tried to flash C109B110 and C432B120 but it does not change my bootloop issue
The original ROM is WAS-LX1AB109C100, I can't find it anywhere ...
Can someone help me ?
Thank you
Edit : My bootloader is unlocked btw

Hey, look here
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=WAS-LX1&firmware_page=0
Try to flash a newer version

aburezk said:
Hey, look here
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=WAS-LX1&firmware_page=0
Try to flash a newer version
Click to expand...
Click to collapse
Already tried, didn't find a solution...
The Update mode always fails at 5%... I can flash with fastboot, but still no luck currently...

Orphee said:
Already tried, didn't find a solution...
The Update mode always fails at 5%... I can flash with fastboot, but still no luck currently...
Click to expand...
Click to collapse
Are you using the original recovery?or TWRP?

Tried both, i think my biggest mistake was to format /data with TWRP...

Orphee said:
Tried both, i think my biggest mistake was to format /data with TWRP...
Click to expand...
Click to collapse
I remember I did something similar when I had lg g2 the solution was to run some commands in adb and it worked bypassed the loop
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
These are the commands
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc

aburezk said:
I remember I did something similar when I had lg g2 the solution was to run some commands in adb and it worked bypassed the loop
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
These are the commands
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
You do this while in TWRP ? Cause I don't think I have access to ADB when booting.

Orphee said:
You do this while in TWRP ? Cause I don't think I have access to ADB when booting.
Click to expand...
Click to collapse
Yes from twrp

aburezk said:
Yes from twrp
Click to expand...
Click to collapse
in /dev/block/platform/hi_mci.0/by-name/
Code:
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl_backup -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 May 31 14:24 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 May 31 14:24 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 May 31 14:24 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 May 31 14:24 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 May 31 14:24 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 May 31 14:24 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 May 31 14:24 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 May 31 14:24 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 May 31 14:24 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 May 31 14:24 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved6 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 May 31 14:24 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 May 31 14:24 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 May 31 14:24 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 May 31 14:24 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 May 31 14:24 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 31 14:24 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 May 31 14:24 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 May 31 14:24 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 May 31 14:24 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 31 14:24 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 May 31 14:24 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 31 14:24 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 May 31 14:24 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 May 31 14:24 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 May 31 14:24 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 May 31 14:24 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 May 31 14:24 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 May 31 14:24 boot -> /dev/block/mmcblk0p28
I don't have fota.

Orphee said:
in /dev/block/platform/hi_mci.0/by-name/
Code:
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl_backup -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 31 14:24 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 May 31 14:24 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 May 31 14:24 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 May 31 14:24 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 May 31 14:24 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 May 31 14:24 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 May 31 14:24 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 May 31 14:24 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 May 31 14:24 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 May 31 14:24 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 May 31 14:24 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved6 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 May 31 14:24 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 May 31 14:24 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 May 31 14:24 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 May 31 14:24 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 May 31 14:24 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 May 31 14:24 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 May 31 14:24 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 31 14:24 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 May 31 14:24 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 May 31 14:24 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 May 31 14:24 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 May 31 14:24 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 May 31 14:24 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 May 31 14:24 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 31 14:24 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 May 31 14:24 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 31 14:24 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 May 31 14:24 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 May 31 14:24 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 May 31 14:24 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 May 31 14:24 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 May 31 14:24 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 May 31 14:24 boot -> /dev/block/mmcblk0p28
I don't have fota.
Click to expand...
Click to collapse
Thats was for LG G2, it's different here

Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !

Orphee said:
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Click to expand...
Click to collapse
:good:

can you please give me the link for dc phoenix?
Orphee said:
Hello,
I fixed it with DC Phoenix and the right FW.
Thanks !
Click to expand...
Click to collapse
i have the same problem with my p10 lite. please give me the link of dc phoenix.

geanish95 said:
i have the same problem with my p10 lite. please give me the link of dc phoenix.
Click to expand...
Click to collapse
https://www.dc-unlocker.com/file-list/DC-unlocker_softwares/DC_Phoenix

Good evening I have a huawei p10 lite and I installed another firmware of another phone.
Now the p10 lite phone does not turn on, it is off, can anyone help me restore it?
Thanks so much
Angel
---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------
I wanted to tell you that the phone Huawei p10 lite does not go into fastboot mode and do not know how to restore it.
I installed the firmware of another telephone DC Phoenix.
And now she does not turn on
Thank you and sorry for my English not perfect

Angelo_Thanks said:
Good evening I have a huawei p10 lite and I installed another firmware of another phone.
Now the p10 lite phone does not turn on, it is off, can anyone help me restore it?
Thanks so much
Angel
---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------
I wanted to tell you that the phone Huawei p10 lite does not go into fastboot mode and do not know how to restore it.
I installed the firmware of another telephone DC Phoenix.
And now she does not turn on
Thank you and sorry for my English not perfect
Click to expand...
Click to collapse
Try plugging USB hold power+vol down
What's your model?

Hi my model is Huawei p10 Lite WAS-LX1A a few days ago I received the upgrade to C432B131 I wanted to install it as a please but did not allow me with unlocked and root recovery TWRP.
Then I installed it I do not know how to do it after several attempts but the phone did not work well. When I clicked on developer options she returned to the home page. So that I then installed a firmware of another phone and so no longer signs of life. I tried various keystrokes but nothing turned on.
Can you help me please?
Thanks the phone is new.
Angel

I DC Phoenix active on the PC does not know yet how long the activation with credits. How can I restore the Huawei P10 Lite phone that does not turn on?
The phone does not go in fastboot mode !!!
Thank you very much for helping
Angel

I tried to charge the Huawei p10 lite phone
but will not charge does not light any LED while it is charging anything.
can you help me?
Is there a way to restart the phone with a Toolkit or something else?
I thank you for the answer.

Angelo_Thanks said:
I tried to charge the Huawei p10 lite phone
but will not charge does not light any LED while it is charging anything.
can you help me?
Is there a way to restart the phone with a Toolkit or something else?
I thank you for the answer.
Click to expand...
Click to collapse
You may send a message on dc phoenix support website, I know he has another tool (HCU? ), if there is a way to revive it, he will probably know how...

Changing boot loader splash screen

Dear All,
I've recently rooted an Amazon fire 7 (7th gen), by soldering a cable to trigger points and shorting it to the metal shield. Then I've installed Nexus custom ROM. All is going well, however I'd like to modify the "$amazon$" bootloader splashscreen, customizing it. Do you know if is it possible or not? I've searched the forum, however there are no results are about the Fire 7. I know this is easily feasible on other devices...
Thanks in advance,
Lg

LgWagon said:
Dear All,
I've recently rooted an Amazon fire 7 (7th gen), by soldering a cable to trigger points and shorting it to the metal shield. Then I've installed Nexus custom ROM. All is going well, however I'd like to modify the "$amazon$" bootloader splashscreen, customizing it. Do you know if is it possible or not? I've searched the forum, however there are no results are about the Fire 7. I know this is easily feasible on other devices...
Thanks in advance,
Lg
Click to expand...
Click to collapse
Dude, you asked the exact same question in a different thread. Cross posting is inconsiderate and irritates the residents.

Davey126 said:
Dude, you asked the exact same question in a different thread. Cross posting is inconsiderate and irritates the residents.
Click to expand...
Click to collapse
Oh, I'm very sorry..I couldn't see this first-posted thread in the sub-forum, so I thought it was not published.
I'll pay more attention

If you opt to change the boot logo following guidance from a related device be certain you have a recovery path as boot hangs are common. Proper logo resolution and permissions are essential. Otherwise, procedure is largely the same. Good luck.

has anyone figure this out? I've been reading the forum for days but haven't seen any examples of changing the amazon boot logo. I have an fire 8 HD 7th gen, and I cant find a logo.bin or logo partition I only see these blocks:
~ # cd dev/block/platform/soc/by-name ls -all
lrwxrwxrwx 1 root root 21 Dec 19 23:57 MISC -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Dec 19 23:57 PMT -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Dec 19 23:57 boot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 9 Dec 19 23:57 boot0hdr0 -> /dev/null
lrwxrwxrwx 1 root root 25 Dec 19 23:57 boot0hdr0_real -> /dev/block/mmcblk0boot0p1
lrwxrwxrwx 1 root root 9 Dec 19 23:57 boot0hdr1 -> /dev/null
lrwxrwxrwx 1 root root 25 Dec 19 23:57 boot0hdr1_real -> /dev/block/mmcblk0boot0p2
lrwxrwxrwx 1 root root 9 Dec 19 23:57 boot0img0 -> /dev/null
lrwxrwxrwx 1 root root 25 Dec 19 23:57 boot0img0_real -> /dev/block/mmcblk0boot0p3
lrwxrwxrwx 1 root root 9 Dec 19 23:57 boot0img1 -> /dev/null
lrwxrwxrwx 1 root root 25 Dec 19 23:57 boot0img1_real -> /dev/block/mmcblk0boot0p4
lrwxrwxrwx 1 root root 21 Dec 19 23:57 boot_amonet -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 Dec 19 23:57 boot_x -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Dec 19 23:57 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 19 23:57 dkb -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Dec 19 23:57 kb -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 9 Dec 19 23:57 lk -> /dev/null
lrwxrwxrwx 1 root root 9 Dec 19 23:57 lk2 -> /dev/null
lrwxrwxrwx 1 root root 20 Dec 19 23:57 lk2_real -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 19 23:57 lk_real -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Dec 19 23:57 metadata -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Dec 19 23:57 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Dec 19 23:57 recovery -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Dec 19 23:57 recovery_amonet -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Dec 19 23:57 recovery_x -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Dec 19 23:57 reserved -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Dec 19 23:57 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 9 Dec 19 23:57 tee1 -> /dev/null
lrwxrwxrwx 1 root root 20 Dec 19 23:57 tee1_real -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 9 Dec 19 23:57 tee2 -> /dev/null
lrwxrwxrwx 1 root root 20 Dec 19 23:57 tee2_real -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Dec 19 23:57 userdata -> /dev/block/mmcblk0p16

Asus Zenfone Max M2 - PARTITIONS LOCATION

Code:
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 ADF -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 APD -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 aboot -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.239999999 +0100 abootbak -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 apdp -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.239999999 +0100 asdf -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.159999999 +0100 asusfw -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:23.669999999 +0100 boot -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 cache -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.189999999 +0100 cmnlib -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.229999999 +0100 cmnlib64 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.219999999 +0100 cmnlib64bak -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 cmnlibbak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.179999999 +0100 config -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.179999999 +0100 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.219999999 +0100 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.179999999 +0100 devinfo -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 dip -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 dpo -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:23.679999999 +0100 dtbo -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 dtbobak -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.229999999 +0100 factory -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.189999999 +0100 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.239999999 +0100 fsgall -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 keymaster -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.219999999 +0100 keymasterbak -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 keystore -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 limits -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.189999999 +0100 lksecapp -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.219999999 +0100 lksecappbak -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 logdump -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 mcfg -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.229999999 +0100 mdtp -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.189999999 +0100 misc -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.229999999 +0100 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.229999999 +0100 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 mota -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 msadp -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.229999999 +0100 persist -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.209999999 +0100 priv -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:23.669999999 +0100 recovery -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.229999999 +0100 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.199999999 +0100 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.179999999 +0100 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.189999999 +0100 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.219999999 +0100 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 splashkernel -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 splashlk -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.179999999 +0100 splashlowbattery -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.179999999 +0100 splashsocbattery -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.199999999 +0100 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.169999999 +0100 syscfg -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:23.679999999 +0100 system -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.209999999 +0100 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-06-27 22:28:24.189999999 +0100 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.189999999 +0100 userdata -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:23.669999999 +0100 vbmeta -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.199999999 +0100 vbmetabak -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:23.679999999 +0100 vendor -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-06-27 22:28:24.179999999 +0100 version -> /dev/block/mmcblk0p65
.

that will be useful thank you

Restore Xperia V with only access to Fastboot?

Let me start by saying this is not my main or even secondary phone, so it doesn't contain anything of value.
Anyway, I tried to upgrade it from Android 4.3 to 5.0. so unlocked the bootloader, installed TWRP and Installed Android successfully but when installing the Gapps it returned an error. Booted up Android but with constant error messages related to Gapps not being fully installed. So some of the install must have taken, other parts not. I messed up because I'm not even sure of what I did trying to install another version of Gapps, trying to reinstall TWRP since I couldn't boot it anymore etc. Anyway, the result is the phone is stuck in a boot loop with a purple led lit. I am able to access it using Fastboot, but nothing more than that. I have no idea if I have screwed up the partition tables, if I have deleted any vital system files etc.
My question then - is it possible to restore the system to stock using nothing but Fastboot?
==update==
Installing TWRP using Fastboot and running fastboot reboot I'm able to enter TWRP once more. Not really sure what to check next though.
This is the output when checking the partition table:
/dev/block/platform/msm_sdcc.1 # [6nls -al /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 340 Jan 1 00:00 .
drwxr-xr-x 4 root root 420 Jan 1 00:00 ..
lrwxrwxrwx 1 root root 20 Jan 1 00:00 Boot -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 00:00 Boot2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 00:00 Cache -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 00:00 FOTAKernel -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 1 00:00 Kernel -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 1 00:00 SDCard -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 00:00 System -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Jan 1 00:00 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 00:00 TZ -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 1 00:00 Userdata -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 00:00 apps_log -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Jan 1 00:00 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 00:00 modemst1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 00:00 modemst2 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 1 00:00 ramdump -> /dev/block/mmcblk0p9
==update 2==
Using TWRP I was able to restore /data following this guide: https://erdentec.com/fix-twrp-mount-data-internal-storage-0mb/ after which I was able to install CARBON-5.1.1-UNOFFICIAL-20151220-1051-tsubasa.zip as well as Gapps for 5.1. The phone is still a but funky in that I can't boot to recovery without flashing TWRP each time before rebooting with Fastboot reboot but at least it's working.