Database Users

[DEV Discussion]Moto X variants *partition dumps*

I don't know how many of us have access to multiple Moto X devices let alone have physical access to more then one vendor release. It seems that all moto x devices are physically identical apart from any custom decorations done by Motorola (the made in the US ones) and the model identifier on the back bottom "Model: XT1056" (as mine shows) they even lack carrier markings on the phone like most have.
But there are differences between the Models and that's what this thread is being made to investigate. I've noticed both from examining the open source releases on github and poking around the memory that there is a lot of sprint-specific modifications including what appears to be set aside partitioning for sprint's... well, er... ****. We don't really know exactly what kind of operation sprint has going on where they need their own partition but it's likely related their funky LTE implementation (remember they were late-adopters since they placed their chips on wimax initially and had cut some corners to deploy LTE on a wide enough scale to compete with carriers that had been building their LTE infrastructure for a year or two at least. There is even a system app completely devoted to this). I've pretty much figured out all the sprint specific system apps and their purposes but I'll post that later since the selfish ulterier motive of the thread is to get partition tables and partition dumps from other models so I can start comparing them and figuring out where the UICC lock implementation really is. People going for VZ/AT&T bootloader unlock solutions may benefit from using these dumps similarly.
Here is the partition table for the XT1056 (bootloader unlocked although that shouldn't make any difference in the partition table)
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 105MB 105MB ext4 modem
2 105MB 107MB 1536kB sbl1
3 107MB 108MB 1536kB sbl2
4 108MB 109MB 526kB sbl3
5 110MB 111MB 524kB aboot
6 112MB 112MB 145kB rpm
7 112MB 112MB 215kB tz
8 113MB 113MB 524kB utags
9 113MB 114MB 1049kB logs
10 114MB 117MB 3150kB padA
11 117MB 119MB 1536kB sbl2Backup
12 119MB 121MB 2097kB sbl3Backup
13 121MB 123MB 1536kB abootBackup
14 123MB 123MB 512kB rpmBackup
15 123MB 124MB 512kB tzBackup
16 124MB 124MB 524kB utagsBackup
17 124MB 126MB 1671kB padB
18 126MB 129MB 3146kB modemst1
19 129MB 132MB 3146kB modemst2
20 132MB 134MB 2097kB mbl
21 134MB 135MB 655kB hob
22 135MB 135MB 8192B dhob
23 135MB 143MB 8389kB ext4 persist
24 143MB 143MB 8192B ssd
25 143MB 147MB 3146kB ext2 fsg
26 147MB 148MB 1049kB sp
27 148MB 148MB 524kB misc
28 148MB 151MB 3146kB ext3 pds
29 151MB 151MB 131kB cid
30 151MB 156MB 4194kB logo
31 156MB 160MB 4194kB clogo
32 160MB 161MB 1049kB devtree
33 161MB 171MB 10.5MB boot
34 171MB 182MB 10.5MB recovery
35 182MB 190MB 8389kB kpan
36 190MB 1257MB 1067MB ext4 cache
37 1257MB 1258MB 1049kB padC
38 1258MB 2869MB 1611MB ext4 system
39 2869MB 2982MB 113MB customize
40 2982MB 15.7GB 12.8GB userdata
I'll provide dumps of any of these partitions on request, I am requesting partition tables from any other models and some speicific partition dumps from other models and any 1056 that hass been UICC unlocked by sprint. cid, tz, misc, utags, persist, kpan, mbl, any of the little odd partitions.
Notes- misc partition is all zeros on mine,
cid partition includes some binary data and some phone-speicific identifiers like the serial number. Most of these partitions I request don't appear to be written to during rsd flashes or most zip flashes so all theinformation contained in these should be preserved between flashes, that is why I am interested in them and why these partitions are the difference between the models.
I will reserve the next post because I'll include some more of the model specific info like the sprint specific system apps and descriptions as i promised, later.

Reserved for thread ****.

Which command I need to use to get partition table?

Al936 said:
Which command I need to use to get partition table?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450045

I have written a small utility to hopefully assist in the analysis of this information. It is based on the same idea as the cat command in POSIX, but with the added benefit of allowing you to effectively 'cast' the file as a collection of chars, 8-bit ints, unsigned 8-bit ints, 16-bit ints, unsigned 16-bit ints, 32-bit ints, unsigned 32-bit ints, 64-bit ints or unsigned 64-bit ints and print to the console. I wrote it because I want to modify the factory 4.4 update files to inject root.
I have attached the .cpp file to this post (simply rename it from "catAll.c" to "catAll.cpp"). It can be compiled with mingw using the following command: g++ catAll.cpp -o catall
I hope this is helpful!

Using the catAll utility I wrote, I have performed the following dumps of gpt.bin and motoboot.bin from the factory 4.4 firmware for the T-Mobile variant (XT1053):
>char
>8-bit signed integer
>8-bit unsigned integer
>16-bit signed integer
>16-bit unsigned integer
>32-bit signed integer
>32-bit unsigned integer
>64-bit signed integer
>64-bit unsigned integer
I will also post the dump of factory 4.2.2's gpt.bin for the XT1053 shortly. I would like to compare them to understand why the phone "detects" trying to downgrade the firmware when flashing from factory 4.4 to factory 4.2.2

The model numbers indicate unique hardware variants - XT1053, ZT1058, XT1060 etc all have different *radio* hardware internally.

I have an XT1049 from hybrid Wi-Fi/cell MVNO Republic Wireless. My phone is not rooted so I can't push parted onto the system and get a partition table readout like the one you have posted.
I do have the out put of 'ls -al /dev/block/platform/msm_sdcc.1/by-name' and 'cat /proc/partitions' which may provide useful information. Here are chunks of these two files (in the order I have listed them above):
lrwxrwxrwx root root 2014-03-14 15:32 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-03-14 15:32 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-03-14 15:32 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-03-14 15:32 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2014-03-14 15:32 cid -> /dev/block/mmcblk0p29
...
and
major minor #blocks name
7 0 3150 loop0
7 1 17703 loop1
179 0 15388672 mmcblk0
179 1 102400 mmcblk0p1
179 2 1500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 514 mmcblk0p4
...
Would full listings of these commands be useful to you?

OP, I have an XT1056 as well, currently running 4.4.2. It is the stock ROM with stock recovery. I am preparing to unlock the BL and flash TWRP, but would prefer a copy of the stock recovery image for the purposes of returning to stock for OTA updates in the future. A search lead me to this thread. Can you tell me the proper command to pull the stock recovery, or if it's easier for you, can you pull it and post it?
Thanks in advance!

I'm not the OP but in case he doesn't respond ...
You may find the stock Sprint 4.4.2 ROM here:
http://sbf.droid-developers.org/phone.php?device=0
Scroll down to the listing marked --
"Android 4.4.2
Blur_Version.161.44.32.ghost_sprint.Sprint.en.US"
The link to download it is on the far right side of that line on the page.
The recovery image is in the zip file. No special commands are needed to extract it from the archive. Just do 'unzip ghost_sprint-user-4.2.2-13.9.0Q2.X-116-MX-17-57-1-1-release-keys-cid9.xml.zip' and it will be extracted into a new directory wherever you are in the file hierarchy. So be sure you have write permission there.
If you need help flashing it there are many, many [better] places in these forums to find it.

Brilliant! Thank you very much!
glarepate said:
I'm not the OP but in case he doesn't respond ...
You may find the stock Sprint 4.4.2 ROM here:
http://sbf.droid-developers.org/phone.php?device=0
Scroll down to the listing marked --
"Android 4.4.2
Blur_Version.161.44.32.ghost_sprint.Sprint.en.US"
The link to download it is on the far right side of that line on the page.
The recovery image is in the zip file. No special commands are needed to extract it from the archive. Just do 'unzip ghost_sprint-user-4.2.2-13.9.0Q2.X-116-MX-17-57-1-1-release-keys-cid9.xml.zip' and it will be extracted into a new directory wherever you are in the file hierarchy. So be sure you have write permission there.
If you need help flashing it there are many, many [better] places in these forums to find it.
Click to expand...
Click to collapse

Verizon VK810 rooted and TWRP

Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app

Chance77 said:
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Click to expand...
Click to collapse
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.

LG already released source. https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=vk810

edgemaster191 said:
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
Click to expand...
Click to collapse
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.

prana22 said:
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
Click to expand...
Click to collapse
I would do something but I have never even compiled CM11 let alone tweaked it to work with a new device. I can work with a developer who doesn't have one, but I don't know enough to do it on my own.

That is where I am as well. I know just enough to get myself in trouble.
Sent from my VK810 4G using XDA Free mobile app

anyone care to share a system dump of the VK810?
boot.img and system partition would be useful
my local verizon store refuses to sell it to me without a contract............ sigh
probably going to get it from amazon

Sure, how do I do that? <-- I am a noob

popezaphod said:
Sure, how do I do that? <-- I am a noob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450045
info about the various partitions,good reading: http://www.all-things-android.com/content/review-android-partition-layout
if you have the custom recovery installed, you could do a backup of the device from recovery and share the files
don't share your EFS partition because it contains your unique IMEI/ESN number, and sometimes devices break if you flash someone else's EFS partition. don't share your userdata partition obviously
(if you can't figure out which is the EFS partition from the WAY #2 image, or how to do a system dump, I just need the following partitions and partition layout)
What I need:
1) Following partitions
BOOT - contains ramdisk info necessary to compile a working boot image
RECOVERY - not that necessary, but more info is useful
SYSTEM - probably contains modem libraries not present in the v500 system partition
2) Partition Layout
needed to compile a working ROM
more info is better... so a complete system dump (minus EFS and userdata) would be great
thanks for helping...

Good Amount of Info
ro.product
Code:
[ro.product.board]: [MSM8960]
[ro.product.brand]: [lge]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [altev]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [LGE]
[ro.product.model]: [VK810 4G]
[ro.product.name]: [altev_vzw]
[email protected]:/ # getprop | grep ro.build.
ro.build
Code:
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1392900914]
[ro.build.date]: [Thu Feb 20 21:55:14 KST 2014]
[ro.build.description]: [altev_vzw-user 4.2.2 JDQ39B VK81010C.1392900840 release
-keys]
[ro.build.display.id]: [JDQ39B]
[ro.build.fingerprint]: [lge/altev_vzw/altev:4.2.2/JDQ39B/VK81010C.1392900840:us
er/release-keys]
[ro.build.host]: [LGEARND9B11]
[ro.build.id]: [JDQ39B]
[ro.build.product]: [altev]
[ro.build.tags]: [release-keys]
[ro.build.target_country]: [US]
[ro.build.target_operator]: [VZW]
[ro.build.target_region]: [US]
[ro.build.type]: [user]
[ro.build.user]: [hyungjin.yoo]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [VK81010C.1392900840]
[ro.build.version.release]: [4.2.2]
[ro.build.version.sdk]: [17]
Stock aBoot img
https://www.dropbox.com/s/kf3fysyhvlyw8l0/aboot.img
Boot IMG w/ TWRP Installed(Not sure if that matters or not)
https://www.dropbox.com/s/egm0rp381cahbeo/boot.img
TWRP Recovory
https://www.dropbox.com/s/ypwreq1c07yj36v/VK810_twrp_2.7.0.1.zip
Recovory IMG w/ TWRP Installed
https://www.dropbox.com/s/23xy2o8qydqsunu/recovery.img
Stock build.prop
https://www.dropbox.com/s/4rqciye90mhp1cj/build.prop
Partitions
Code:
7 0 5229 loop0
7 1 22901 loop1
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 2195456 mmcblk0p23
179 24 1392640 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 11247616 mmcblk0p35
259 4 4079 mmcblk0p36
254 0 5229 dm-0
254 1 22900 dm-1
lrwxrwxrwx root root 1970-01-13 12:13 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-13 12:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-13 12:13 bnr -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-13 12:13 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-13 12:13 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-13 12:13 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-13 12:13 eksst -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-13 12:13 encrypt -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-13 12:13 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-13 12:13 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-13 12:13 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-13 12:13 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-13 12:13 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-13 12:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-13 12:13 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-13 12:13 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-13 12:13 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-13 12:13 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-13 12:13 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-13 12:13 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-13 12:13 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-13 12:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-13 12:13 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-13 12:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-13 12:13 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-13 12:13 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-13 12:13 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-13 12:13 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-13 12:13 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-13 12:13 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-13 12:13 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-13 12:13 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-13 12:13 userdata -> /dev/block/mmcblk0p35
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You

NICG said:
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
Click to expand...
Click to collapse
Thanks for posting....
Slightly strange values...
VK810 (LTE):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2248146944 # 2114M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 11517558784 #10984
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
V500 (wifi):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 880803840 # 840M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 6189744128 # 5.9G
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
can you post the output of the below command? Want to verify the BOARD_FLASH_BLOCK_SIZE settings
cat /proc/mtd
EDIT1:
Who wants to be a guinea pig for my first cm-11.0 build? (requires you to have TWRP recovery)
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img is already LOKI patched
<removed>
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....

I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed

traccdma said:
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
Click to expand...
Click to collapse
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)

paperWastage said:
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
Click to expand...
Click to collapse
i think we should stick with v500/v510/vk810 convention.....
http://forum.xda-developers.com/showpost.php?p=48103469&postcount=22
from this, it looks like the recovery image needs to be fixed...
http://forum.xda-developers.com/showpost.php?p=48331517&postcount=10
for now, I've manually edited the META-INF/com/google/android/updater-script to include "altev" as part of the check
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img will be LOKI-patched during the flash (which means don't use my previous upload where I pre-patched the boot.img)
http://d-h.st/tAq
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....

with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own

traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
hmm, not sure why TWRP is complaining. need to investigate tomorrow. if the update_script failed, then the boot.img wasn't patched, so the new boot image won't boot at all.
were you able to restore from nandroid backup?
you also try replacing the update-binary in the ROM with this
http://forum.xda-developers.com/showthread.php?t=2532300

that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.

traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
whenever that happens get a recovery log, They are very helpful

traccdma said:
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
Click to expand...
Click to collapse
good to hear...
need two things:
system dump of stock ROM.
The proprietary libs I'm using right now is from v500 which probably doesn't have the radio libs. maybe wifi/bt driver is different too
logs
As Drgravy said, logs are helpful. Recovery log, /proc/last_kmsg from kernel boot, ...

Sorry been a little busy but here you go.
Stock Rooted System IMG
https://www.dropbox.com/s/rpxmbp1lgb5a4k9/system.img

[Q] LG F70 D315 From tracfone No download mode

I achive for now:
!!!! Restore from any softbrick (any partition ful corrupted emmc) almost infalible!!! i have soft bricked bootloaders gpt, more than 10 times and resurrected again
A clowermod recovery
Semi flashed with f70 d315 stock?
I´m working when i can i post my results
Root
root is easy just use Towelroot
Clowermod Recovery
Tanks to OpenBump
put in sdcard and
Code:
adb shell
su
dd if=/sdcard/cwmrecovery_bumped.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery
Clower mod for L31L
Boot loader
The bootloader has some protection in aboot
if you disasemble with idapro is idem to the f70 d315, g2 mini and family the block that you have to patch
but this file is protected if you pach a single bit it bring you a raw disk when conect the phone (Q9006 mode)

-----OLD POST--------
I have a LG F70 D315 from tracfone whit this company the models change to LGL31L but I verify and many references says that is F70 an no other
I wan to flash whit a lesser restrictive firmware that not belong to this company to later flash a custom room, volume down while conet to get DOWNLOAD MODE are removed from this phone
I have KDZ, extracted to , i rooted sucefully the phone, got recovery mode
but the only way I find to flash is via download and this mode dosent apear
I think is rplace with a batery charging becouse that is what I see whit
Code:
adb reboot-bootloader
and others
and when try key conbinations to power up to download mode it bring me to the batery loader again
In the original extracted f70 d315 kdz the download mode is in the laf partition
I have it have a diferent size of the original fone laf
there is a way to push this to get download mode?
Sorry for my bad English and for post in this secction becouse I dont find LG 70 board
thanks
The partition info off the phone is this
Code:
shell># cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 22528 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 512 mmcblk0p30
179 31 2097152 mmcblk0p31
259 0 921600 mmcblk0p32
259 1 4220416 mmcblk0p33
259 2 40943 mmcblk0p34
179 32 512 mmcblk0rpmb
shell># ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 20:09 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 20:09 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 20:09 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 20:09 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 20:09 cache -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-02 20:09 drm -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 20:09 eksst -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-02 20:09 encrypt -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 20:09 factory -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 20:09 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 20:09 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 20:09 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 20:09 grow -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-02 20:09 laf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 20:09 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 20:09 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 20:09 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 20:09 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 20:09 mpt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-02 20:09 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 20:09 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 20:09 rct -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 20:09 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 20:09 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 20:09 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 20:09 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 20:09 sbl1b -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 20:09 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 20:09 sns -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 20:09 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 20:09 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-02 20:09 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 20:09 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 20:09 userdata -> /dev/block/mmcblk0p33
shell># 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) print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8389kB 75.5MB 67.1MB fat16 modem
2 75.5MB 76.5MB 1049kB sbl1
3 76.5MB 77.1MB 524kB rpm
4 77.1MB 77.6MB 524kB tz
5 77.6MB 78.1MB 524kB sdi
6 78.1MB 80.2MB 2097kB aboot
7 80.2MB 80.7MB 524kB rpmb
8 80.7MB 81.3MB 524kB tzb
9 81.3MB 83.4MB 2097kB abootb
10 83.4MB 85.5MB 2097kB pad
11 85.5MB 88.6MB 3146kB modemst1
12 88.6MB 91.8MB 3146kB modemst2
13 91.8MB 109MB 16.8MB misc
14 109MB 143MB 33.6MB ext4 persist
15 143MB 166MB 23.1MB laf
16 168MB 191MB 23.1MB boot
17 191MB 214MB 23.1MB recovery
18 214MB 217MB 3146kB fsg
19 218MB 219MB 524kB fsc
20 219MB 219MB 524kB ssd
21 226MB 227MB 524kB DDR
22 235MB 235MB 524kB encrypt
23 235MB 236MB 524kB rct
24 243MB 252MB 8389kB ext4 drm
25 252MB 260MB 8389kB ext4 sns
26 260MB 281MB 21.0MB factory
27 281MB 315MB 33.6MB fota
28 319MB 320MB 1049kB sbl1b
29 320MB 353MB 33.6MB ext4 mpt
30 353MB 354MB 524kB eksst
31 361MB 2508MB 2147MB ext4 system
32 2508MB 3452MB 944MB ext4 cache
33 3452MB 7774MB 4322MB ext4 userdata
34 7776MB 7818MB 41.9MB grow
(parted) q
I copy laf to recovery partition with dd and bring me to Download Mode when I enter to recovery but i dont find a way to flash yet

unlock boot loader
I maybe try to flash via custom recovery but i have to unlock bootloader
This method
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
says change bites in this string 20 00 EB 00 00 50 E3 E0 FF FF 0A
The stock firmware have this string in aboot.img 20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f e5
but the aboot of my phone the string change to
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a
and is the string only string that match to 20 00 eb 00 00 50 e3
20 00 eb 00 00 50 e3 e0 ff ff 0a 60 00 9f ->stock firm
20 00 eb 00 00 50 e3 08 00 84 e5 07 00 00 0a ->current room
If i change this with this conditions the phone may not boot anymore?

I am trying to get the download mode for the L31l and am wondering how you copied the files to the recovery partition.
I got the kdz file extracted it and extracted the dz files and have the binfiles.
I have also created an image file by combining the bin files but don't think this will do anything.
I am planning to use the method from:
htt p://ww w.lg-phone s.org/how-to-flas h-unbrick-lg-f70-bac k-to-stoc k.htm l
(Remove spaces)
To flash the kdz file of I can get download mode to work.
Thanks

Download mode
To get download mode:
1-To get download mode I rooted easy with towelroot
2-With dd made a backup of all partitions (nandroid backup)
3-Flash laf partition to recovery (change msm_sdcc I dont know exactly the name because I don´t have phone here and my tools):
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/dev/block/platform/msm_sdcc.1/by-name/recovery
4-Do
Code:
adb shell
reboot recovery
and you will enter to download instead of recovery
but for me was unseful because the firmware is for Lgf70 and is a lgl31l
and any flash sofware detected
I do the last I posted and dead:silly: to usb qualcom mode that see as raw disk
http://forum.xda-developers.com/showthread.php?t=2582142
this mode is easy to recover but intead I fail and dd other partition sbl
and have a mode that is very very triky and dont find how to solve
cause nothing worme form my phone
This a mode who I'am now QDLoader 9008
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830/page17#post58460319

I also got into download but couldn't get it to load the F70 rom.
Anybody have any ideas?

Thanks for your work. Have you been able to load the portion of the f70 rom that contains the hidden menu for unlock?
I know there is some information about adding it back to the verizon g2 available.
Thanks again

Any more info to share?
You mentioned a f70 rom. Any more luck getting it to work?
Thanks

f70 rom
1god 1Bad news I flash the f70 but the unlock menu says that not more atemps left (usseless)
Flash f70 room bricks me the phone many times with a backup I can bring back ever I want but may sometimes have to open the phone and make a tespoint
Frist backup all your phone whit dd
I backup all single partition
dd if=/dev/block/platform/msm_sdcc.1/by-name/xxx of=/sdcard/backup
and after backup the GPT partition table
you beter dd all then phone mmc instead
of course copy to a PC or any external
Extract boot.img and system.img of F70 room kdztools etc...
For f70 room you have to bumped boot.img of F70
frist have to repack whit bootimg.exe http://en.miui.com/thread-27657-1-1.html
descompress and compress
and after used open bump
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
Better put frist system.img to sdcard
1)whit dd flash the recovery to the boot img after that youre phone start always in recovery
because no recovery convination
2)flash boot.img to recovery
3) Now when you turn your phone start in the recovery mount /sdcard /system...
conect in and this recovery have adb
flash whit dd system partition
don't exit recovery
4)wipe cache factory reset
5) in avanced revot recovery will boot system (anytimes you power on have to do this)
The gide is not easy and safe i can made a better but flash f70 dosen't worst
yes you have more usb modes enabled, wifi theter and hotspot
but no unock , even any unlock boxes that have f70 direct unlock
all becuse the nvram is not accesible????

i brick my d315 with update v10e
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english

willowlefou said:
hello,
I have got a LG D315 with root and TWRP 2.8.0.0.
today i see there is a update v10e for my phone.
so i accept the install. the update download , pass de verify ( no problem cause root) and reboot.
but the phone boot on TWRP only and the update no run . i can't reboot normaly , I'm blocked on TWRP ( reboot on system, bootloader or recovery >> return to TWRP) , the phone refuse to upgrade or reboot normaly ?
any ideas ???
please help !!
ps : sorry I'm french and i write bad english
Click to expand...
Click to collapse
I resolved my problem ,
I have backup the LAF files so in TWRP I 've restore the laf
Code:
dd if=/sdcard/backup/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
after i reboot in download mode ( power off / button up + plug usb cable )
the LGFlashTool2014 detect my phone i Ican retore the D31510e_00.kdz file with this tools.
my data aren't destroy.
thanks!

Hi guys! My lg f70 phone broken after use flash tool, (Qdloader 9008), i search fixing on internet, and finding them QFIl and qpst.. My phone cpu msm8926, need emmc firehose 8926 file for flashing emmc and fastboot restore file, somebody help? Sorry my bad english!

How to install a new rom with bootloader loocked?

Hello I have a machine Redmi2 that does not boot, only boots with fastboot when I pressed the power off button ans Vol - button
I can execute fastboot commands.
For example:
fastboot devices
Click to expand...
Click to collapse
967354587d12 fastboot
Click to expand...
Click to collapse
fastboot oem device-info
Click to expand...
Click to collapse
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
I could dowloaded various rom (official from xiaomi and not official like aosp-caf_wt88047_64-21-05-2017-eng.pirej.zip or xiaomi-miui-hellas-5.1_wt88047_V8_XTRVbeta2_7.2.24.zip) but I can install a new system in this machine.
First I try to unlock the bootloader with official method from Xiaomi but the result is error.
Now I try to boot with twrp and this is works.
To boot with twrp I cam execute this with fastboot
fastboot flash recovery twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'recovery' (11426 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.544s
Click to expand...
Click to collapse
fastboot flash boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'boot' (11426 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.493s
Click to expand...
Click to collapse
And with this comand boots the machine with twrp
fastboot boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
When machine boots I have access to external card from my PC and I can put the rom to try to install.
When try to clean the partitions I can not do it:
This is the errors
Error al desmontar '/system' (invalid argument)
Error al desmontar '/data' (invalid argument)
Error al desmontar '/cache' (invalid argument)
Incapaz de montar almacenamiento
Click to expand...
Click to collapse
When I try to install RR-N-v5.8.3-20170516-wt88047-OFFICIAL.zip for example I can not install this rom.
Do you know if it is possible install a rom with bootloader locked?
Doy you know if it is possible unlocked the bootloader if xiaomi unlocker does not works?
Any ideas to install a rom in this machine?
Best regards.

i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?

AKHILR4J said:
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
Click to expand...
Click to collapse
Thanks for your help,
I have downloaded the lastest twrp img from redmi 2, and I have the same problems.
Machine boots with twrp but I can not write in the internal partitions and I can not install a rom.
I think that I need unlock the bootloader to can to modify the android partitions but I do not know to do it.

try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS

Liquid2 said:
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Click to expand...
Click to collapse
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.

Hello again, I have tried to mount /system with a terminal in TWRP with this command
Code:
# Montamos la carpeta /system como lectura(r) y escritura(w)
mount -o remount,rw /system
but the problem is my /proc/mounts file
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=967420k,nr_inodes=153983,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=967420k,nr_inodes=153983 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p25 /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /firmware vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Do you know how can I can change this file to include the /system partition to mount read/write and I can install a rom os.
Regards,

jriosa said:
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Click to expand...
Click to collapse
have u tried another twrp?? make sure it for your device

Liquid2 said:
have u tried another twrp?? make sure it for your device
Click to expand...
Click to collapse
Thanks for your help, I have tried different versions from twrp with the same result.
Regards, Julio.

sori, cant help much, maybe
i myself in very newbie
how about if you flash fresh with flashboot rom using miflash, see if it can boot into official miui first
then you can try install twrp again and flash custom rom
have you tried twrp

Hello Now I access to android with adb.
When I boot the android with TWRP, I can access with my PC using adb.
I execute this.
adb root
Click to expand...
Click to collapse
adb shell
Click to expand...
Click to collapse
This is the partitions on my machine
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 13557743 mmcblk0p30
179 32 4096 mmcblk0rpmb
179 64 30375936 mmcblk1
179 65 30371840 mmcblk1p1
Click to expand...
Click to collapse
~ # cd /dev
/dev # find -inme mmcblk0
find: unrecognized: -inme
Segmentation fault
/dev # find -iname mmcblk0
./block/mmcblk0
./block/platform/soc.0/7824900.sdhci/mmcblk0
Click to expand...
Click to collapse
I have added parted to managed partitions in my machine
To see parttions in my disk
~ # /sbin/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) p
Click to expand...
Click to collapse
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
Click to expand...
Click to collapse
To see my partitions
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 32.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 13.4G 15.6G 46% /external_sd
Click to expand...
Click to collapse
I think that I can not install a new rom (offcial or unofficial) because the system I can not access to partitions /system for example and I think that system partitions is mmcblk0p23.
Do you know how I can modify my partitions to see in df -h and launch a new rom with twrp?
Thanks a lot,

Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.

Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.

jriosa said:
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Click to expand...
Click to collapse
Have you unmounted the data partition in twrp before executing the rm command?

SidOfficial said:
Have you unmounted the data partition in twrp before executing the rm command?
Click to expand...
Click to collapse
This is my commands and my point mounts are
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
Click to expand...
Click to collapse
I see a new error
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
Click to expand...
Click to collapse
maybe the first partition I think is OK
~ # parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 67.1MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 67.1MB 67.1MB fat16
Click to expand...
Click to collapse
adb shell
~ # cp /external_sd/parted /sbin/parted
~ # chmod +x /sbin/parted
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
~ # 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 MiB
unit MiB
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) rm 30
rm 30
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) q
q
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
~ # 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) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
(parted)
Click to expand...
Click to collapse
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?

jriosa said:
This is my commands and my point mounts are
I see a new error
maybe the first partition I think is OK
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
Click to expand...
Click to collapse
Yes, you can recreate all the partitions and can even resize the system and data partitions. Head over to this link https://forum.xda-developers.com/redmi-2/how-to/wt88047-redmi-2-resize-partition-t3612933

[Huawei Y6][GUIDE] How to Change Boot Logo (logo.img)

Note:
This is not bootanimation, this is the splash screen (the 'Huwaei' boot logo which is displayed when device is switched ON)
This is for Huawei Y6 Only..
(For other devices, please send me your splash.img so that I can create a tool for you too.)
NOTE: I think this tool is no longer working for latest firmwares.
Please check this new tool: [GUIDE] Changing boot splash image on the Huawei Y6
Requirements:
1. Rooted Huawei Y6 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create logo.img:
Before proceeding, make sure fastboot is setup properly in your computer (just incase something goes wrong)..
1. Download & Extract this in computer: Huawei_Y6_Logo_Maker.zip
2. Make sure you have a 720x1280 resolution picture.
3. Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'Create_Logo.bat' to create logo.img , which you can find inside the "output" folder.
STEPS to flash logo.img:
Optional: To backup your original logo.img:
Code:
dd if=/dev/block/bootdevice/by-name/logo of=/sdcard/logo.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the logo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/logo.img of=/dev/block/bootdevice/by-name/logo
c. To flash from Fastboot mode:
Code:
fastboot flash logo logo.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock logo.img from custom recovery or fastboot.
Hit the Thanks :good: button if it worked for you
You're welcome to post the bootlogos that you created..
Thanks to @adam_s_459_ who provided the stock logo.img of his Huawei Y6 (SCL-L04)

Thank you so much for making this tool. I have been wanting to change that screen for so long as it is very ugly ?.

So I followed all of the steps and it made the logo.img but when I Flash it it just doesn't do anything. Just the same old Huawei logo ?

adam_s_459_ said:
So I followed all of the steps and it made the logo.img but when I Flash it it just doesn't do anything. Just the same old Huawei logo
Click to expand...
Click to collapse
Try method b) or c) to install logo.img..
I guess flashing from recovery doesn't work because the path to logo (partition) in the updater-script is wrong..
Or please tell where the "logo" block file is present in the /dev/block/ directory so that I'll edit that in the tool

GokulNC said:
Try method b) or c) to install logo.img..
I guess flashing from recovery doesn't work because the path to logo (partition) in the updater-script is wrong..
Or please tell where the "logo" block file is present in the /dev/block/ directory so that I'll edit that in the tool
Click to expand...
Click to collapse
I cannot find the logo file in that directory. I tried flashing from terminal and it didn't work. And I get an"external command not allowed" error in fastboot

adam_s_459_ said:
I cannot find the logo file in that directory. I tried flashing from terminal and it didn't work.
Click to expand...
Click to collapse
How did you extract the logo.img from your device then?
If you extracted it from stock firmware, please find out how it's flashed into device..
(If it's a flashable zip, send the updater-script.
If it's a fastboot flashable firmware, send me .bat files if there's any)
adam_s_459_ said:
And I get an"external command not allowed" error in fastboot
Click to expand...
Click to collapse
It means you have not setup the fastboot tool properly..
Search and follow the instructions to properly set it up

GokulNC said:
How did you extract the logo.img from your device then?
If you extracted it from stock firmware, please find out how it's flashed into device..
(If it's a flashable zip, send the updater-script.
If it's a fastboot flashable firmware, send me .bat files if there's any)
Click to expand...
Click to collapse
So for some reason I couldn't upload just the updater script but this is the flashable file with it in it. I extracted the logo.img from stock firmware. I don't really know how to find out how is flashed on the device sorry. I don't know where I would find any .Bat files because I am fairly new to this type of thing. I hope this helps. Thanks.

@adam_s_459_ I just examined the partition table of Huawei Y6..
Code:
Number Start (sector) End (sector) Size Code Name
1 34 1057 512.0 KiB FFFF sbl1
2 1058 2081 512.0 KiB FFFF hyp
3 8192 8255 32.0 KiB FFFF sec
4 8256 8319 32.0 KiB FFFF DDR
5 16384 17407 512.0 KiB FFFF rpm
6 17408 18431 512.0 KiB FFFF tz
7 18432 28543 4.9 MiB FFFF aboot
8 28544 30591 1024.0 KiB FFFF pad
9 30592 161663 64.0 MiB FFFF oeminfo
10 161664 169855 4.0 MiB FFFF misc
11 169856 178047 4.0 MiB FFFF modemst1
12 178048 186239 4.0 MiB FFFF modemst2
13 188416 196607 4.0 MiB FFFF fsg
14 196608 606207 200.0 MiB FFFF modem
15 606208 606209 1024 bytes FFFF fsc
16 606210 606225 8.0 KiB FFFF ssd
17 606226 737297 64.0 MiB FFFF log
18 745472 761855 8.0 MiB FFFF persist
19 761856 892927 64.0 MiB FFFF boot
20 892928 991231 48.0 MiB FFFF recovery
21 991232 1089535 48.0 MiB FFFF erecovery
22 1089536 1613823 256.0 MiB FFFF cache
23 1613824 2138111 256.0 MiB FFFF cust
24 2138112 5808127 1.8 GiB FFFF system
25 5808128 5808127 0 bytes 0700 userdata
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
Code:
fastboot flash misc logo.img
@adam_s_459_ If you think it's risky for you or if you don't seem to understand, please ask any other experienced ones in this forum to help me out here, to try on their device..
Because I don't own an Huawei Y6 device

GokulNC said:
@adam_s_459_ I just examined the partition table of Huawei Y6..
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
If you think it's risky for you or if you don't seem to understand, please ask any other experienced ones in this forum to help me out here, to try on their device..
Because I don't own an Huawei Y6 device
Click to expand...
Click to collapse
I'm going to see if I can Flash the current misc partition in fastboot before I do it. So I fastboot I just enter "fastboot flash misc logo.img"?

Stock Recovery Huawei Y6
I need Stock Recovery Huawei Y6
Please

Are u a huawei y6 developer

Stock Recovery Huawei Y6
Kompesjo said:
I need Stock Recovery Huawei Y6
Please
Click to expand...
Click to collapse
Hi,
I have all that you need but this is for Huawei Y6 (SCL-L02)
this device is a single sim, 8GB ROM & 1GB RAM
if ya need em email me [email protected]

GokulNC said:
@adam_s_459_ I just examined the partition table of Huawei Y6..
Code:
Number Start (sector) End (sector) Size Code Name
1 34 1057 512.0 KiB FFFF sbl1
2 1058 2081 512.0 KiB FFFF hyp
3 8192 8255 32.0 KiB FFFF sec
4 8256 8319 32.0 KiB FFFF DDR
5 16384 17407 512.0 KiB FFFF rpm
6 17408 18431 512.0 KiB FFFF tz
7 18432 28543 4.9 MiB FFFF aboot
8 28544 30591 1024.0 KiB FFFF pad
9 30592 161663 64.0 MiB FFFF oeminfo
10 161664 169855 4.0 MiB FFFF misc
11 169856 178047 4.0 MiB FFFF modemst1
12 178048 186239 4.0 MiB FFFF modemst2
13 188416 196607 4.0 MiB FFFF fsg
14 196608 606207 200.0 MiB FFFF modem
15 606208 606209 1024 bytes FFFF fsc
16 606210 606225 8.0 KiB FFFF ssd
17 606226 737297 64.0 MiB FFFF log
18 745472 761855 8.0 MiB FFFF persist
19 761856 892927 64.0 MiB FFFF boot
20 892928 991231 48.0 MiB FFFF recovery
21 991232 1089535 48.0 MiB FFFF erecovery
22 1089536 1613823 256.0 MiB FFFF cache
23 1613824 2138111 256.0 MiB FFFF cust
24 2138112 5808127 1.8 GiB FFFF system
25 5808128 5808127 0 bytes 0700 userdata
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
Code:
fastboot flash misc logo.img
@adam_s_459_ If you think it's risky for you or if you don't seem to understand, please ask any other experienced ones in this forum to help me out here, to try on their device..
Because I don't own an Huawei Y6 device
Click to expand...
Click to collapse
Respected Sir
I Need oeminfo Partition Backup Plz
Will Get Grateful For Help
Thanks Anticipation

shoaibrao said:
@adam_s_459_ I just examined the partition table of Huawei Y6..
As far as I can guess, maybe it resides in the misc partition..
Try flashing it to the misc partition.. (Back it up before you do)
Respected Sir
I Need oeminfo Partition Backup Plz
Will Get Grateful For Help
Thanks Anticipation
Click to expand...
Click to collapse
You should ask this on Huawei Y6 questions and answers