Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
dan15 said:
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
Click to expand...
Click to collapse
Yes my Android version is 4.4.2 build version is 18.2.A.1.14
ok, as my D5103 is ugrade to .17, i have to wait for a solution, if i don't want to downgrade, but i'm not sure that the rot will stay if i upgrade after root on .14...
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Abhinav2 said:
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Click to expand...
Click to collapse
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
CreasingMass Dev said:
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
Click to expand...
Click to collapse
None of them has AFAIK. Can u give some example of device which might have? Because recovery is basically flashed in FOTA partition
AJ
Al parecer no existe recovery
Xenon1978 said:
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Click to expand...
Click to collapse
No se si alguno de ustedes o tengo instalar un gestor de recuperación (Recovery) anteriormente a este modelo
Ahora he intentado hacerlo y puff.. el paquete ABD me dice que no EXISTE
Code:
FAILED <remote: Recovery partición doesn't founded>
Related
as the title said, here i will post partition table of our ancora
Code:
Number Start (sector) End (sector) Size Code Name
1 1 212991 104.0 MiB 0700 Microsoft basic data
2 212992 213991 500.0 KiB 8300 Linux filesystem
3 213992 221183 3.5 MiB 8300 Linux filesystem
5 229376 239615 5.0 MiB 8300 Linux filesystem
6 245760 285759 19.5 MiB 8300 Linux filesystem
7 286720 292863 3.0 MiB 8300 Linux filesystem
8 294912 306175 5.5 MiB 8300 Linux filesystem
9 311296 324271 6.3 MiB 8300 Linux filesystem
10 327680 333823 3.0 MiB 8300 Linux filesystem
11 335872 342015 3.0 MiB 8300 Linux filesystem
12 344064 360447 8.0 MiB 8300 Linux filesystem
13 360448 375807 7.5 MiB 8300 Linux filesystem
14 376832 387071 5.0 MiB 8300 Linux filesystem
15 393216 1488895 535.0 MiB 8300 Linux filesystem
16 1490944 1613823 60.0 MiB 8300 Linux filesystem
17 1613824 3887103 1.1 GiB 8300 Linux filesystem
18 3891200 3993599 50.0 MiB 8300 Linux filesystem
19 3997696 3998695 500.0 KiB 8300 Linux filesystem
20 4005888 4013079 3.5 MiB 8300 Linux filesystem
21 4014080 4024319 5.0 MiB 8300 Linux filesystem
22 4030464 4070463 19.5 MiB 8300 Linux filesystem
23 4071424 4081663 5.0 MiB 8300 Linux filesystem
24 4087808 4101807 6.8 MiB 8300 Linux filesystem
25 4104192 4114431 5.0 MiB 8300 Linux filesystem
26 4120576 4130815 5.0 MiB 8300 Linux filesystem
27 4136960 4147199 5.0 MiB 8300 Linux filesystem
28 4153344 7733247 1.7 GiB 8300 Linux filesystem
well, my question regarding this data are
1. why i don't get the name of each partition ?
2. as we know, kernel block memory is mmcblk0p13, the block size is 7.5MB, is this available size only for the kernel or this size included kernel+ramdisk?
3. we got so many partition, any idea of having a hidden partition that is vacant or useable to mount other things?
thanks
i hope pep would see this post and help me
Sent from my GT-I8150
hadidjapri said:
i hope pep would see this post and help me
Sent from my GT-I8150
Click to expand...
Click to collapse
You're making me ashamed
I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified:
* bootloader partition
* 2 (two) baseband partitions
* ROM partition
* recovery partition
As to the others... they *are* still mysterious...
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
pepoluan said:
You're making me ashamed
I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified:
* bootloader partition
* 2 (two) baseband partitions
* ROM partition
* recovery partition
As to the others... they *are* still mysterious...
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
Click to expand...
Click to collapse
i got efs from arco
another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk?
Sent from my GT-I8150
hadidjapri said:
another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk?
Click to expand...
Click to collapse
kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb.
This is the information I've gathered about the partitions.
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
arco68 said:
kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb.
This is the information I've gathered about the partitions.
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
Click to expand...
Click to collapse
hmm what does mmcblk10-26 store sir?
Sent from my GT-I8150
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
arco68 said:
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
Click to expand...
Click to collapse
I once dd-ed p22, it has similar strings to p6.
A kind of backup baseband?
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
sigprof said:
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
Click to expand...
Click to collapse
is it possible partition number 19-26 are intended to be backup partition?
Sent from my GT-I8150
Could phone operator lock code be stored in one of the (normally unmounted) partitions?
Sent from my GT-I8150 using xda app-developers app
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
IlyaKol said:
Mine is coming tomorrow. I'll gladly do it if you tell me how to dump it.
Click to expand...
Click to collapse
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
macdaddie87 said:
Sure here's a guide.. http://forum.xda-developers.com/showthread.php?t=2450045
If you need help pm me
Click to expand...
Click to collapse
I'm a system engineer (server support, etc.) so I should be able to handle it. Just needed to be pointed in the right direction. I shall post up tomorrow.
macdaddie87 said:
After flashing xposed 64bit the H815 will not boot. We need someone to dump the system partion so we have a way to restore system until kdz is available.
After someone dumps and uploads the system.img we should just be able to flash via fastboot.
Click to expand...
Click to collapse
Scratch that, evidently root is only available for the EU H815 and mine is the Taiwan one, from what I know. I'll see if I get lucky somehow, but by the looks of it I won't be able to provide the dump since I can't achieve root.
Some help
http://forum.xda-developers.com/g4/development/rom-docs-testrom-t3126728
Code:
major minor #blocks name
253 0 721772 zram0
179 0 30535680 mmcblk0
179 1 88064 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 1536 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 1536 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 2048 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 4096 mmcblk0p36
259 5 49152 mmcblk0p37
259 6 40960 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 8192 mmcblk0p40
259 9 8192 mmcblk0p41
259 10 32768 mmcblk0p42
259 11 47104 mmcblk0p43
259 12 10240 mmcblk0p44
259 13 4096 mmcblk0p45
259 14 4096 mmcblk0p46
259 15 4239360 mmcblk0p47
259 16 262144 mmcblk0p48
259 17 1261568 mmcblk0p49
259 18 24313856 mmcblk0p50
259 19 12271 mmcblk0p51
179 32 4096 mmcblk0rpmb
DDR -> /dev/block/mmcblk0p30
aboot -> /dev/block/mmcblk0p8
abootbak -> /dev/block/mmcblk0p14
apdp -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p38
cache -> /dev/block/mmcblk0p49
cust -> /dev/block/mmcblk0p48
devinfo -> /dev/block/mmcblk0p17
po -> /dev/block/mmcblk0p20
drm -> /dev/block/mmcblk0p40
eksst -> /dev/block/mmcblk0p33
encrypt -> /dev/block/mmcblk0p32
factory -> /dev/block/mmcblk0p43
fota -> /dev/block/mmcblk0p44
fsc -> /dev/block/mmcblk0p27
fsg -> /dev/block/mmcblk0p26
grow -> /dev/block/mmcblk0p51
hyp -> /dev/block/mmcblk0p6
hypbak -> /dev/block/mmcblk0p12
keystore -> /dev/block/mmcblk0p29
laf -> /dev/block/mmcblk0p37
limits -> /dev/block/mmcblk0p16
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p24
modemst2 -> /dev/block/mmcblk0p25
mpt -> /dev/block/mmcblk0p42
msadp -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p23
pmic -> /dev/block/mmcblk0p2
pmicbak -> /dev/block/mmcblk0p10
raw_resources -> /dev/block/mmcblk0p45
raw_resourcesbak -> /dev/block/mmcblk0p46
rct -> /dev/block/mmcblk0p34
recovery -> /dev/block/mmcblk0p39
rpm -> /dev/block/mmcblk0p7
rpmbak -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p3
sbl1bak -> /dev/block/mmcblk0p9
sdi -> /dev/block/mmcblk0p5
sdibak -> /dev/block/mmcblk0p15
sec -> /dev/block/mmcblk0p31
sns -> /dev/block/mmcblk0p41
spare1 -> /dev/block/mmcblk0p21
spare2 -> /dev/block/mmcblk0p36
ssd -> /dev/block/mmcblk0p28
system -> /dev/block/mmcblk0p47
tz -> /dev/block/mmcblk0p4
tzbak -> /dev/block/mmcblk0p11
userdata -> /dev/block/mmcblk0p50
I can't unlock the BL as I'm a TW phone not an EU phone. Sorry OP.
Hi guys
I have a best method for Nokia x liquid smooth lollipop developers for flashing this ROM without DAT.
________________________
System folder of this rom is compressed into DAT file.....developers easily extract system folder but sometimes they face some errors for Compressing To DAT.
For fix these errors.I build a updater-script for flahing this ROM like a kitkat roms flashing method.
so let's start for the hack
for accept this method you have to download the script from the given link....
you only want
Meta-Inf folder (go to the given link)
Boot.IMG
System folder (not DAT)
file_contexts
compress these files into zip and flash the ROM
that's it you flashed liquid lollipop without having DAT
remember
this script is only use for liquid smooth lollipop ROM by Ahmed hady
please press the thanks button
thank you
Link
http://www74.zippyshare.com/v/EhmIGNdK/file.html
Has the ril bug fixed?
we are truing to fix......by this updater-script I don't waste my time to compress system folder to DAT
Thanks Man ,,,
you welcome
hope you fix the ril soon , goodluck
okay
l.k said:
okay
Click to expand...
Click to collapse
Hey bro do you have knowledge of partitions of nokia x if yes then please explain
Share information about partitions I.e, which is boot partition,system partition etc
Here is my nokia x partitions list
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 250 mmcblk0p2
179 3 51200 mmcblk0p3
179 4 1 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 768 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 13576 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 10240 mmcblk0p16
179 17 13576 mmcblk0p17
179 18 471040 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 20 mmcblk0p20
179 21 1228800 mmcblk0p21
179 22 1370112 mmcblk0p22
179 23 40960 mmcblk0p23
179 24 10240 mmcblk0p24
179 25 399360 mmcblk0p25
179 26 59099 mmcblk0p26
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
253 0 102400 zram0
[email protected]:/ $
I don't know about that
Nokia X/XL Partitions
matrixex said:
Hey bro do you have knowledge of partitions of nokia x if yes then please explain
Share information about partitions I.e, which is boot partition,system partition etc
Click to expand...
Click to collapse
Bootloader 179 3 51200 mmcblk0p3
Persist 179 16 10240 mmcblk0p16
Boot 179 17 13576 mmcblk0p17
System 179 18 573440 mmcblk0p18
Cache 179 19 102400 mmcblk0p19
Storage 179 21 1172480 mmcblk0p21
Data 179 22 1267712 mmcblk0p22
YSH ALSAGER said:
Bootloader 179 3 51200 mmcblk0p3
Persist 179 16 10240 mmcblk0p16
Boot 179 17 13576 mmcblk0p17
System 179 18 573440 mmcblk0p18
Cache 179 19 102400 mmcblk0p19
Storage 179 21 1172480 mmcblk0p21
Data 179 22 1267712 mmcblk0p22
Click to expand...
Click to collapse
Thanks
I was searching for it
Well please also explain how did you find it
I'm working on cm13 compiled by thinhx2
ROM have a script error.....some symlink failed status 7....trying to fix it...
matrixex said:
Thanks
I was searching for it
Well please also explain how did you find it
Click to expand...
Click to collapse
Using Parition app
I've tried many times to fix the ril problem, but I can not. is there any other way to fix this problem ?
the rom using huawei device tree and the rom only for single rom bro,,,
we want twrp 3.0.0 for flashing cm13.....inches twrp 2.8.7.0 gave me error
some symlinks failed......
l.k said:
we want twrp 3.0.0 for flashing cm13.....inches twrp 2.8.7.0 gave me error
some symlinks failed......
Click to expand...
Click to collapse
That happens with me too I have created Nokia x stock rom after symlinking I have flashed it ,TWRP error displays "some symlink failed"
yeah as well as twrp 3.0.0 also isn't working
your rom file is not match with your sript,,
no twrp recovery isn't have complete symlinks which r used in cm13's script
hi so im using adb shell and i'd like to take a closer peek at the init files. i was pointed in the direction of downloading my bootloader first. i have since used adb shell command cat /proc/partitions and this was displayed:
major minor #blocks name
7 0 98304 loop0
179 0 30535680 mmcblk0
179 1 19456 mmcblk0p1
179 2 66464 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 64 mmcblk0p5
179 6 32 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 6144 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 4 mmcblk0p16
179 17 17408 mmcblk0p17
179 18 19456 mmcblk0p18
179 19 4084 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 9216 mmcblk0p23
179 24 3891200 mmcblk0p24
179 25 512000 mmcblk0p25
179 26 40960 mmcblk0p26
179 27 25894892 mmcblk0p27
253 0 1572864 vnswap0
179 32 4096 mmcblk0rpmb
179 64 124868096 mmcblk1
179 65 124851712 mmcblk1p1
[email protected]:/ #
which one of these contains the bootloader or how do i download the correct partition?
Code:
HWANE:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
254 0 2293760 zram0
179 0 61071360 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 2048 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 61440 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 2048 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 12288 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 24576 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 32768 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 28672 mmcblk0p34
179 35 4096 mmcblk0p35
179 36 98304 mmcblk0p36
179 37 1024 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 2048 mmcblk0p39
179 40 16384 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 131072 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 2048 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 4096 mmcblk0p46
179 47 32768 mmcblk0p47
259 0 2048 mmcblk0p48
259 1 16384 mmcblk0p49
259 2 14336 mmcblk0p50
259 3 5767168 mmcblk0p51
259 4 196608 mmcblk0p52
259 5 32768 mmcblk0p53
259 6 802816 mmcblk0p54
259 7 196608 mmcblk0p55
259 8 53043200 mmcblk0p56
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
179 192 62367744 mmcblk1
179 193 62366720 mmcblk1p1
253 0 4724684 dm-0
253 1 790064 dm-1
253 2 128924 dm-2
253 3 32172 dm-3
253 4 193424 dm-4
253 5 193424 dm-5
Code:
HWANE:/ $ ls -l /dev/block/platform/hi_mci.0/by-name/
[I][B]User friendly display[/B][/I]
/dev/block/mmcblk0p48 -> bootfail_info
/dev/block/mmcblk0p42 -> cache
/dev/block/mmcblk0p52 -> cust
/dev/block/mmcblk0p40 -> dfx
/dev/block/mmcblk0p35 -> dto
/dev/block/mmcblk0p34 -> dts
/dev/block/mmcblk0p27 -> erecovery_kernel
/dev/block/mmcblk0p28 -> erecovery_ramdisk
/dev/block/mmcblk0p38 -> erecovery_vbmeta
/dev/block/mmcblk0p29 -> erecovery_vendor
/dev/block/mmcblk0p5 -> fastboot
/dev/block/mmcblk0p4 -> frp
/dev/block/mmcblk0p26 -> fw_hifi
/dev/block/mmcblk0p3 -> fw_lpm3
/dev/block/mmcblk0p44 -> hisitest0
/dev/block/mmcblk0p45 -> hisitest1
/dev/block/mmcblk0p46 -> hisitest2
/dev/block/mmcblk0p30 -> kernel
/dev/block/mmcblk0p20 -> misc
/dev/block/mmcblk0p36 -> modem_fw
/dev/block/mmcblk0p18 -> modem_om
/dev/block/mmcblk0p17 -> modem_secure
/dev/block/mmcblk0p10 -> modemnvm_backup
/dev/block/mmcblk0p6 -> modemnvm_factory
/dev/block/mmcblk0p11 -> modemnvm_img
/dev/block/mmcblk0p12 -> modemnvm_system
/dev/block/mmcblk0p21 -> modemnvm_update
/dev/block/mmcblk0p7 -> nvme
/dev/block/mmcblk0p43 -> odm
/dev/block/mmcblk0p8 -> oeminfo
/dev/block/mmcblk0p47 -> patch
/dev/block/mmcblk0p16 -> persist
/dev/block/mmcblk0p55 -> product
/dev/block/mmcblk0p31 -> ramdisk
/dev/block/mmcblk0p32 -> recovery_ramdisk
/dev/block/mmcblk0p37 -> recovery_vbmeta
/dev/block/mmcblk0p33 -> recovery_vendor
/dev/block/mmcblk0p22 -> reserved2
/dev/block/mmcblk0p9 -> reserved3
/dev/block/mmcblk0p14 -> reserved4
/dev/block/mmcblk0p15 -> reserved5
/dev/block/mmcblk0p39 -> reserved8
/dev/block/mmcblk0p50 -> reserved9
/dev/block/mmcblk0p49 -> rrecord
/dev/block/mmcblk0p13 -> secure_storage
/dev/block/mmcblk0p25 -> sensorhub
/dev/block/mmcblk0p19 -> splash2
/dev/block/mmcblk0p51 -> system
/dev/block/mmcblk0p23 -> teeos
/dev/block/mmcblk0p24 -> trustfirmware
/dev/block/mmcblk0p56 -> userdata
/dev/block/mmcblk0p41 -> vbmeta
/dev/block/mmcblk0p54 -> vendor
/dev/block/mmcblk0p53 -> version
/dev/block/mmcblk0p1 -> vrl
/dev/block/mmcblk0p2 -> vrl_backup
Hello,
I want to flash a firmware for downgrade.
How i can make it without a dload method?
I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Yes me to dload not downgrade
Gesendet von meinem ANE-LX1 mit Tapatalk
Manflack said:
Hello,
I want to flash a firmware for downgrade.
How i can make it without a dload method?
I can't downgrade my phone with this method, always a warning appear "error checking files" or anything like that...
Click to expand...
Click to collapse
SirusX said:
Yes me to dload not downgrade
Gesendet von meinem ANE-LX1 mit Tapatalk
Click to expand...
Click to collapse
This is a partition layout it can't help you with downgrade.
To downgrade without brick the phone you have to find a roll back firmware. In the picture is an example for p20 pro.