I'm trying to change to splash-screen / boot logo of my Sony Xperia Z4 tablet (SGP771)
I have already rooted my device.
With the help of the bootimg.exe tool I unpacked the boot.img - exchanged the logo.rle and repacked the boot.img.
My custom logo.rle I created with boot_screen_logo_creation_package.
However, when flashing the new-boot.img to my device (with fastboot flash boot new-boot.img) the logo is not changed. Still showing the Sony logo before the bootanimation appears.
My tablet runs the Marshmallow firmware and I'm using the corresponding AndroPlusKernel v31 (Z4T_SGP771_AndroPlusKernel_v31.zip).
I tried already different tools like bootimg_tools from this xda forum, or split_bootimg.pl from the android-wiki.
The one mentioned in my question I found in several forums (wordpress, miui, dark-cyanide-devs ...)
Most of the tools I tried already did not repack the image correctly (fastboot reported "remote: dtb not found")
The tool I used, mentioned in the question, seemed to work for correcly unpacking and repacking. But as I said - the logo does not change -.-
Any suggestions what I am doing wrong?
Doesn't the initial splash logo reside in the bootloader or in another part of the system? I'm pretty sure it isn't in boot.img, at least this was not the case with my HTC phones.
jelbo said:
Doesn't the initial splash logo reside in the bootloader or in another part of the system? I'm pretty sure it isn't in boot.img, at least this was not the case with my HTC phones.
Click to expand...
Click to collapse
Thank you for your reply. Do you have any idea where I could find it? I already searched through the filesystem with the adb shell:
Code:
>find . -name "*.rle"
and also *.png, *.bmp, *.jpg or also > find . -name "*logo*"
I did not open the pictures I found, but by their name I could not tell if there is the logo beyond (besides the logo.rle)
I attached the search result if it helps somehow?
MM365 said:
Thank you for your reply. Do you have any idea where I could find it? I already searched through the filesystem with the adb shell:
Code:
>find . -name "*.rle"
and also *.png, *.bmp, *.jpg or also > find . -name "*logo*"
I did not open the pictures I found, but by their name I could not tell if there is the logo beyond (besides the logo.rle)
I attached the search result if it helps somehow?
Click to expand...
Click to collapse
I'm pretty sure it's not a file on a filesystem and, if it is, it would be on a partition you can not just search on easily. I remember having to flash a boot splash image on my HTC One m7 using fastboot flash splash1 splash.img. splash1 is the dedicated partition for the splash image, on mmcblk0p13.
I don't know how it is on Xperia's, but I guess it's similar. It'd be nice to be able to change this though, I also dislike the bright white Sony splash screen.
Here's the partition info I pulled from Disk Info Pro:
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* TA [mmcblk0p1] Not mounted
Total space: 2 MB
* LTALabel [mmcblk0p2] (/lta-label) [ext4]
Used: 5.7 MB, Free: 10.3 MB, Total space: 16 MB
* modem [mmcblk0p3] (/firmware) [vfat]
Used: 16.8 MB, Free: 63.2 MB, Total space: 80 MB
* pmic [mmcblk0p4] Not mounted
Total space: 128 KB
* alt_pmic [mmcblk0p5] Not mounted
Total space: 128 KB
* limits [mmcblk0p6] Not mounted
Total space: 1 KB
* DDR [mmcblk0p7] Not mounted
Total space: 1 MB
* apdp [mmcblk0p8] Not mounted
Total space: 256 KB
* msadp [mmcblk0p9] Not mounted
Total space: 256 KB
* dpo [mmcblk0p10] Not mounted
Total space: 1 KB
* hyp [mmcblk0p11] Not mounted
Total space: 512 KB
* alt_hyp [mmcblk0p12] Not mounted
Total space: 512 KB
* fsg [mmcblk0p13] Not mounted
Total space: 1.5 MB
* ssd [mmcblk0p14] Not mounted
Total space: 8 KB
* sbl1 [mmcblk0p15] Not mounted
Total space: 1 MB
* alt_sbl1 [mmcblk0p16] Not mounted
Total space: 1 MB
* modemst1 [mmcblk0p17] Not mounted
Total space: 1.5 MB
* modemst2 [mmcblk0p18] Not mounted
Total space: 1.5 MB
* s1sbl [mmcblk0p19] Not mounted
Total space: 256 KB
* alt_s1sbl [mmcblk0p20] Not mounted
Total space: 256 KB
* sdi [mmcblk0p21] Not mounted
Total space: 128 KB
* alt_sdi [mmcblk0p22] Not mounted
Total space: 128 KB
* tz [mmcblk0p23] Not mounted
Total space: 1 MB
* alt_tz [mmcblk0p24] Not mounted
Total space: 1 MB
* rpm [mmcblk0p25] Not mounted
Total space: 512 KB
* alt_rpm [mmcblk0p26] Not mounted
Total space: 512 KB
* aboot [mmcblk0p27] Not mounted
Total space: 1 MB
* alt_aboot [mmcblk0p28] Not mounted
Total space: 1 MB
* boot [mmcblk0p29] Not mounted
Total space: 64 MB
* rdimage [mmcblk0p30] Not mounted
Total space: 32 MB
* persist [mmcblk0p31] (/persist) [ext4]
Used: 5.3 MB, Free: 26.7 MB, Total space: 32 MB
* FOTAKernel [mmcblk0p32] Not mounted
Total space: 64 MB
* misc [mmcblk0p33] Not mounted
Total space: 1 MB
* keystore [mmcblk0p34] Not mounted
Total space: 512 KB
* devinfo [mmcblk0p35] Not mounted
Total space: 1 KB
* config [mmcblk0p36] Not mounted
Total space: 512 KB
* rddata [mmcblk0p37] Not mounted
Total space: 100 MB
* apps_log [mmcblk0p38] (/rca) [ext4]
Used: 5.2 MB, Free: 4.8 MB, Total space: 10 MB
* diag [mmcblk0p39] (/idd) [ext4]
Used: 2.5 MB, Free: 13.5 MB, Total space: 16 MB
* oem [mmcblk0p40] (/oem) [ext4]
Used: 79.2 MB, Free: 220 MB, Total space: 300 MB
* Cache [mmcblk0p41] (/cache) [ext4]
Used: 11.4 MB, Free: 188 MB, Total space: 200 MB
* B2B [mmcblk0p42] Not mounted
Total space: 384 MB
* Data (userdata) [mmcblk0p43] (/data) [ext4]
Used: 13.7 GB, Free: 9 GB, Total space: 22.7 GB
* System [mmcblk0p44] (/system) [ext4]
Used: 4.3 GB, Free: 820 MB, Total space: 5.1 GB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
--------------------------
tmpfs mount points
--------------------------
* /dev [tmpfs]
Used: 144 KB, Free: 1.4 GB, Total space: 1.4 GB
* /mnt [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
* /tmp [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
* /storage [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
* /storage/self [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
jelbo said:
I'm pretty sure it's not a file on a filesystem and, if it is, it would be on a partition you can not just search on easily. I remember having to flash a boot splash image on my HTC One m7 using fastboot flash splash1 splash.img. splash1 is the dedicated partition for the splash image, on mmcblk0p13.
I don't know how it is on Xperia's, but I guess it's similar. It'd be nice to be able to change this though, I also dislike the bright white Sony splash screen.
Click to expand...
Click to collapse
Thank you for your help - I really appreciate it !
I tried to >fastboot flash splash custom.img
and >fastboot flash splash1 custom.img
and fastboot reports "Command not allowed"
Code:
target reported max download size of 536870912 bytes
sending 'splash' <750 KB>...
OKAY [0.052s]
writing 'splash'...
FAILED <remote: Command not allowed>
finished. total time: 0x077s
UsbDebugging is enabled.
I used the tool from this xda forum to create the img from a 450x800 png file.
I did not use the tool to flash the img because the tools adb reported my device as "offline" (rebooting did not help)
- so I tried to flash it manually with fastboot...
Do you have any suggestions what went wrong?
MM365 said:
Thank you for your help - I really appreciate it !
I tried to >fastboot flash splash custom.img
and >fastboot flash splash1 custom.img
and fastboot reports "Command not allowed"
Code:
target reported max download size of 536870912 bytes
sending 'splash' <750 KB>...
OKAY [0.052s]
writing 'splash'...
FAILED <remote: Command not allowed>
finished. total time: 0x077s
UsbDebugging is enabled.
I used the tool from this xda forum to create the img from a 450x800 png file.
I did not use the tool to flash the img because the tools adb reported my device as "offline" (rebooting did not help)
- so I tried to flash it manually with fastboot...
Do you have any suggestions what went wrong?
Click to expand...
Click to collapse
First of all, you should not run commands like that if you don't know exactly what you are doing. I'm by no means an expert in this, but when you read my list of partitions you can see there's no partition named splash or splash1. You tried to flash a file into that partition. Also, the file should not be 450x800 but likely the native resolution, which is 2560x1440.
Let me try to ping @[NUT], I'm pretty sure he can tell us right away if it's possible or not. In the meantime, I'll do a little search again myself. So far I haven't found a lot. Looks like it is indeed an .rle file in the kernel.
jelbo said:
First of all, you should not run commands like that if you don't know exactly what you are doing. I'm by no means an expert in this, but when you read my list of partitions you can see there's no partition named splash or splash1. You tried to flash a file into that partition. Also, the file should not be 450x800 but likely the native resolution, which is 2560x1440.
Let me try to ping @[NUT], I'm pretty sure he can tell us right away if it's possible or not. In the meantime, I'll do a little search again myself. So far I haven't found a lot. Looks like it is indeed an .rle file in the kernel.
Click to expand...
Click to collapse
Ok. Thanks.
please let me know if you come to any conclusion.
Related
Please can someone help me to resize the system partition of an Android JB 4.2.2 on cubieboard?
Image: sun7i_android_sugar-cubieboard2-8192cu.img
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204
2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2)
3) To burn to flash: PhoenixSuit1.0.6
unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 1048576
user_type = 0x2
so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
but :
1) In installed android, the system has only 512MB and not 1GB as show.
2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )
Here is my devices list and size:
Code:
NAME SIZE MOUNTPOINT LABEL
nand 3.8G
|-nand1 16M Volumn
|-nand2 16M
|-nand3 16M
|-nand4 512M
|-nand5 512M
|-nand6 16M
|-nand7 32M
|-nand8 320M
|-nand9 16M PRIVATE
|-nand10 256M
`-nand11 2.1G
mmcblk0 14.4G
|-mmcblk0p1 900M /
`-mmcblk0p2 13.5G EXTRA
icemagno said:
Please can someone help me to resize the system partition of an Android JB 4.2.2 on cubieboard?
Image: sun7i_android_sugar-cubieboard2-8192cu.img
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204
2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2)
3) To burn to flash: PhoenixSuit1.0.6
unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 1048576
user_type = 0x2
so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
but :
1) In installed android, the system has only 512MB and not 1GB as show.
2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )
Here is my devices list and size:
Code:
NAME SIZE MOUNTPOINT LABEL
nand 3.8G
|-nand1 16M Volumn
|-nand2 16M
|-nand3 16M
|-nand4 512M
|-nand5 512M
|-nand6 16M
|-nand7 32M
|-nand8 320M
|-nand9 16M PRIVATE
|-nand10 256M
`-nand11 2.1G
mmcblk0 14.4G
|-mmcblk0p1 900M /
`-mmcblk0p2 13.5G EXTRA
Click to expand...
Click to collapse
Use this software, search it on google and install it on your PC, then partition you SD
MiniTool Partition Wizard Pro v7.1
azithro said:
Use this software, search it on google and install it on your PC, then partition you SD
MiniTool Partition Wizard Pro v7.1
Click to expand...
Click to collapse
"3) To burn to flash: PhoenixSuit1.0.6"
This implies using NAND .... SD is not in the context.
Thanks anyway!
I have a NOOK tablet 16GB that is somehow locked from modifying partitions
I have tried
the repart image , which has worked many times for me in the past
the AdamOutler Ubuntu Disk
formatting / wiping options in various versions of CWM and TWRP
fastboot erases
fastboot formats
dd'ing /zero to various partitions
parted
sgdisk
a zillion scripts
something at a low level is preventing modifications to the partitions
Im wasting far too much time on this , but I hate being beat (-:
I have a backup of rom and factory , and dd images of stock parttions so I am 100% comfortable with something that
will COMPLETELY ZAP the device
if I boot a known good CM10 image from SD card, it fails to boot , I was assuming if I could get a running android from the card, I'd have access to lots of tools... , but it just fails to tun CM10
any help appreciated.
Thanks
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
sagirfahmid3 said:
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
Click to expand...
Click to collapse
Thanks for responding, Yes, I have tried multiple ways to to zap the table and it doesnt stick.
sgdisk -Z, sgdisk -z parted,
no matter what I do the partitions remain untouched.
I reboot and it still boots into an old stock OS that has a FC shortly after startup, and the internal recovery (factory) , which I can not overwrite, gives the please restart and try again message.
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
mikeataol said:
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
Click to expand...
Click to collapse
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
sagirfahmid3 said:
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
Click to expand...
Click to collapse
Hi, no, I didnt forget to "write" after the "o"
/tmp # ./gdisk /dev/block/mmcblk0
./gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Command (? for help): o
o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
y
Command (? for help): w
w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
/tmp # q
/tmp #
after reboot
Command (? for help): p
p
Disk /dev/block/mmcblk0: 31105024 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): CE21388C-B927-4A5C-91CE-DBD1DE4AB3BC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535678
Partitions will be aligned on 256-sector boundaries
Total free space is 1285 sectors (642.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
7 262144 1019903 370.0 MiB 8300 factory
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
Humm...wow, that's pretty crazy. Try writing zeroes to your emmc and then retrying.
# dd if=/dev/zero of=/dev/block/mmcblk0
well, now it's getting interesting.
supersu didn't work for me (always failed to patch boot.img) but i found another way to get root. xda is just great.
it's definitely not my work...just used other people's achievements, so all credits go to them!!!
!!! Please, don't blame me if sth goes wrong. It worked for me and my model. Do it on your won risk!
!!! Before you do anything, back up your phone (in TWRP)
so what you need to gain root:
Yoga Book [YB1-X9OL]
working ADB --> e.g. see here
unlocked bootloader --> see here (unlocking the bootloader does a factory reset, so back up your data)
twrp_recovery --> see here (do not flash it, just boot temporarily)
files for root --> see end of post
1. download attached file
2. boot twrp
3. install 1-Magisk-v7.zip
4. install 2-phh-superuser-magisk-r259.zip
5. reboot
6. install 3-Phh Superuser_1.0.3.3.apk
7. install a root checker to verify
got this way from here: https://forum.xda-developers.com/honor-4x/help/honor-4x-che1-l04-mm-6-0-1-emui-4-root-t3475854/
more about magisk can be found here (maybe even a newer solution/version): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
screenshot:
{
"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"
}
files for root: View attachment MMroot.zip
EDIT:
You can also use the newest version of Magisk (v.10.2.) to get root, but then follow the following steps:
1. download and install the newest magisk.zip via twrp, phh's superuser is already included, so no need to install it seperately (as with v.7)
2. reboot system
3. install phh's superuser manager from playstore
!!!if you want to update from Magisk v.7., don't do it with magiskmanager cause it will break root.
donwload Magisk's uninstaller.zip (get it here) and install it via twrp before you install v.10.2.
Awesome ! I can't wait to try it , but it's so sad that I have to review my courses now :crying:
Awesome, thanks to the OP, thanks to the god, I installed it perfectly, now it looks stable when I use it
AndyVerne said:
Awesome, thanks to the OP, thanks to the god, I installed it perfectly, now it looks stable when I use it
Click to expand...
Click to collapse
hey u used the instructions above? im a newbie in this so any instructions from yr side on how to do it?
bisharat said:
hey u used the instructions above? im a newbie in this so any instructions from yr side on how to do it?
Click to expand...
Click to collapse
what help do you need?
Hey
What method do you recommend for backing up everything before unlocking for those who do not use google or lenovo services?
So why do you say to not actually flash TWRP, but to only boot to it temporarily? Does this fail if you properly flash TWRP?
Anyone tried this on the non-LTE version YB1-X90F?
west0ne said:
Anyone tried this on the non-LTE version YB1-X90F?
Click to expand...
Click to collapse
i think it would work. i think most important is to know whether partitions are the same and twrp is working.
to find out install disk info and copy the details about your partitions (via the share symbol).
also install AIDA64 then go to "system files" (?) and click on build.prop and copy the information there. do the same for /proc/partitions.
i will check the similarities.
nevertheless you could try to boot (!!!not flash!!!) the recovery, just to see if it boots at all (if yes and partitions are the same, it should be save) as you do not flash it, it doesn't hurt your device but do not use it in any way.
heldc said:
So why do you say to not actually flash TWRP, but to only boot to it temporarily? Does this fail if you properly flash TWRP?
Click to expand...
Click to collapse
because i'm not an experienced developer...and i don't know if it will break at one point or fails in any way (i didn't build it from source, just modified twrp from yoga tab 3 pro).
so if you only boot it, stock recovery will still be there and you could flash stockrom if nothing works at all. I must say I feel quite comfortable this way...use twrp whenever i must, but have stock untouched.
on the other hand, so far twrp worked quite well for me
if you dare flash it, i won't take responsibility in any way.
secondly, doing ota update should be a lot easier with stock recovery.
hope you see my points!?
hajkan said:
Hey
What method do you recommend for backing up everything before unlocking for those who do not use google or lenovo services?
Click to expand...
Click to collapse
funny question, because there's no satisfying way to back up everything without twrp or root! it' s the main reason why i started to find a way for root and 'porting' a custom recovery. now i can use titanium or whatever tool to back up and of course twrp to back up all partitions.
back up what's possible.
danjac said:
i think it would work. i think most important is to know whether partitions are the same and twrp is working............
i will check the similarities.
nevertheless you could try to boot (!!!not flash!!!) the recovery, just to see if it boots at all (if yes and partitions are the same, it should be save) as you do not flash it, it doesn't hurt your device but do not use it in any way.
Click to expand...
Click to collapse
I've not had a chance to try the twrp yet but will give it a go but in the mean time.
Thanks.
Here is the diskinfo.
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.2 GB, Free: 43.7 GB, Total space: 53 GB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 11.5 GB, Free: 17.4 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 992 MB, Free: 2.8 GB, Total space: 3.8 GB
Here's the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.incremental=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-10-01
ro.build.version.base_os=
ro.build.date=2016年 12月 09日 星期五 15:04:15 CST
ro.build.date.utc=1481267055
ro.build.type=user
ro.build.user=buildslave
ro.build.host=bjws76
ro.build.tags=release-keys
ro.build.flavor=yeti_10_row_wifi-user
ro.product.ota.model=Lenovo YB1-X90F
ro.product.model=Lenovo YB1-X90F
ro.product.brand=Lenovo
ro.product.name=yeti_10_row_wifi
ro.product.device=yeti
ro.product.board=r2_cht_ffd
ro.lenovo.mtpname=YOGA BOOK
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,x86,armeabi-v7a,armeabi,arm64-v8a
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.manufacturer=LENOVO
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=gmin
# ro.build.product is obsolete; use ro.product.device
ro.build.product=yeti
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=yeti_10_row_wifi-user 6.0.1 MMB29M YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW release-keys
ro.build.fingerprint=Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000239_161209:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.camera.rec.pixel_format=0x10F
sys.powerctl.no.shutdown=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
ro.dalvik.vm.isa.arm64=x86_64
ro.enable.native.bridge.exec64=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=6.0_r7
ro.opengles.version=196609
ro.ycbcr.pixel_format=0x10F
ro.spid.gps.FrqPlan=FRQ_PLAN_26MHZ_2PPM
ro.spid.gps.RfType=GL_RF_4752_BRCM_EXT_LNA
ro.spid.gps.pmm=disabled
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=Notice.ogg
ro.carrier=unknown
ro.config.alarm_alert=New_Morning.ogg
ro.lenovo.device=tablet
ro.com.google.clientidbase=android-lenovo
persist.backgrounddata.enable=false
ro.lenovo.wificert=no
ro.lenovo.childmode=true
ro.lenovo.mtpname=YOGA
BOOK
ro.product.ota.model=Lenovo
YB1-X90F
debug.show_anr_dialog=false
log.tag.VibeTonz=ERROR
ro.lenovo.operator=open
ro.yeti.telephony.call=false
ro.lenovo.region=row
ro.lenovo.sim=none
ro.lenovo.tablet=wifi
ro.lenovo.platform=intel
ro.lenovo.bqb=pass
ro.lenovo.cta=false
ro.lenovo.videocall=false
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.x86_64.variant=silvermont
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=silvermont
dalvik.vm.isa.x86.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0x543ffafdb4f6e02c750f8f5883ce5d8b763f13a3000000000000000000000000
west0ne said:
I've not had a chance to try the twrp yet but will give it a go but in the mean time.
Thanks.
Here is the diskinfo.
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.2 GB, Free: 43.7 GB, Total space: 53 GB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 11.5 GB, Free: 17.4 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 992 MB, Free: 2.8 GB, Total space: 3.8 GB
Here's the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.incremental=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-10-01
ro.build.version.base_os=
ro.build.date=2016年 12月 09日 星期五 15:04:15 CST
ro.build.date.utc=1481267055
ro.build.type=user
ro.build.user=buildslave
ro.build.host=bjws76
ro.build.tags=release-keys
ro.build.flavor=yeti_10_row_wifi-user
ro.product.ota.model=Lenovo YB1-X90F
ro.product.model=Lenovo YB1-X90F
ro.product.brand=Lenovo
ro.product.name=yeti_10_row_wifi
ro.product.device=yeti
ro.product.board=r2_cht_ffd
ro.lenovo.mtpname=YOGA BOOK
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,x86,armeabi-v7a,armeabi,arm64-v8a
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.manufacturer=LENOVO
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=gmin
# ro.build.product is obsolete; use ro.product.device
ro.build.product=yeti
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=yeti_10_row_wifi-user 6.0.1 MMB29M YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW release-keys
ro.build.fingerprint=Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000239_161209:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.camera.rec.pixel_format=0x10F
sys.powerctl.no.shutdown=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
ro.dalvik.vm.isa.arm64=x86_64
ro.enable.native.bridge.exec64=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=6.0_r7
ro.opengles.version=196609
ro.ycbcr.pixel_format=0x10F
ro.spid.gps.FrqPlan=FRQ_PLAN_26MHZ_2PPM
ro.spid.gps.RfType=GL_RF_4752_BRCM_EXT_LNA
ro.spid.gps.pmm=disabled
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=Notice.ogg
ro.carrier=unknown
ro.config.alarm_alert=New_Morning.ogg
ro.lenovo.device=tablet
ro.com.google.clientidbase=android-lenovo
persist.backgrounddata.enable=false
ro.lenovo.wificert=no
ro.lenovo.childmode=true
ro.lenovo.mtpname=YOGA
BOOK
ro.product.ota.model=Lenovo
YB1-X90F
debug.show_anr_dialog=false
log.tag.VibeTonz=ERROR
ro.lenovo.operator=open
ro.yeti.telephony.call=false
ro.lenovo.region=row
ro.lenovo.sim=none
ro.lenovo.tablet=wifi
ro.lenovo.platform=intel
ro.lenovo.bqb=pass
ro.lenovo.cta=false
ro.lenovo.videocall=false
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.x86_64.variant=silvermont
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=silvermont
dalvik.vm.isa.x86.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0x543ffafdb4f6e02c750f8f5883ce5d8b763f13a3000000000000000000000000
Click to expand...
Click to collapse
oh damn, could you please get the info about partitions from disk info again. the most important partitions are missing...like boot, bootloader, recovery, ...
just go to settings and make sure that you check all the following settings (see the attached screenshot):
show mount path
show partition name
show file name
expert mode
unmounted partitions
devicemapper partitions
temp. filesystems
danjac said:
i think it would work. i think most important is to know whether partitions are the same and twrp is working.
to find out install disk info and copy the details about your partitions (via the share symbol).
also install AIDA64 then go to "system files" (?) and click on build.prop and copy the information there. do the same for /proc/partitions.
i will check the similarities.
nevertheless you could try to boot (!!!not flash!!!) the recovery, just to see if it boots at all (if yes and partitions are the same, it should be save) as you do not flash it, it doesn't hurt your device but do not use it in any way.
Click to expand...
Click to collapse
danjac said:
oh damn, could you please get the info about partitions from disk info again. the most important partitions are missing...like boot, bootloader, recovery, ...
just go to settings and make sure that you check all the following settings (see the attached screenshot):
show mount path
show partition name
show file name
expert mode
unmounted partitions
devicemapper partitions
temp. filesystems
View attachment 4001102
Click to expand...
Click to collapse
More detailed disk-info
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* android_bootloader [mmcblk0p1] Not mounted
Total space: 100 MB
* android_bootloader2 [mmcblk0p2] Not mounted
Total space: 100 MB
* android_boot [mmcblk0p3] Not mounted
Total space: 30 MB
* android_recovery [mmcblk0p4] Not mounted
Total space: 30 MB
* android_misc [mmcblk0p5] Not mounted
Total space: 1 MB
* android_metadata [mmcblk0p6] Not mounted
Total space: 16 MB
* android_persistent [mmcblk0p7] Not mounted
Total space: 1 MB
* android_frp [mmcblk0p8] Not mounted
Total space: 1 MB
* android_config [mmcblk0p9] (/config) [ext4]
Used: 4.4 MB, Free: 3.6 MB, Total space: 8 MB
* android_factory [mmcblk0p10] (/factory) [ext4]
Used: 4.4 MB, Free: 5.6 MB, Total space: 10 MB
* android_country [mmcblk0p11] (/country) [ext4]
Used: 90 MB, Free: 934 MB, Total space: 1 GB
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.4 GB, Free: 43.6 GB, Total space: 53 GB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
* mmcblk0boot1 [mmcblk0boot1] Not mounted
Total space: 4 MB
* mmcblk0boot0 [mmcblk0boot0] Not mounted
Total space: 4 MB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 12.3 GB, Free: 16.6 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 1.5 GB, Free: 2.3 GB, Total space: 3.8 GB
Hey there,
I'm trying to root my Yoga Book too. I have a related post with a little question here : https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Thank you !
west0ne said:
More detailed disk-info
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* android_bootloader [mmcblk0p1] Not mounted
Total space: 100 MB
* android_bootloader2 [mmcblk0p2] Not mounted
Total space: 100 MB
* android_boot [mmcblk0p3] Not mounted
Total space: 30 MB
* android_recovery [mmcblk0p4] Not mounted
Total space: 30 MB
* android_misc [mmcblk0p5] Not mounted
Total space: 1 MB
* android_metadata [mmcblk0p6] Not mounted
Total space: 16 MB
* android_persistent [mmcblk0p7] Not mounted
Total space: 1 MB
* android_frp [mmcblk0p8] Not mounted
Total space: 1 MB
* android_config [mmcblk0p9] (/config) [ext4]
Used: 4.4 MB, Free: 3.6 MB, Total space: 8 MB
* android_factory [mmcblk0p10] (/factory) [ext4]
Used: 4.4 MB, Free: 5.6 MB, Total space: 10 MB
* android_country [mmcblk0p11] (/country) [ext4]
Used: 90 MB, Free: 934 MB, Total space: 1 GB
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.4 GB, Free: 43.6 GB, Total space: 53 GB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
* mmcblk0boot1 [mmcblk0boot1] Not mounted
Total space: 4 MB
* mmcblk0boot0 [mmcblk0boot0] Not mounted
Total space: 4 MB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 12.3 GB, Free: 16.6 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 1.5 GB, Free: 2.3 GB, Total space: 3.8 GB
Click to expand...
Click to collapse
partitions are vrtually the same...just try to boot it. i think there's a good chance it might work, if it starts try and test it...e.g. backup and restore data, see if terminal works and so on...
if yes i think you are good to go
but as always....no guarantee!!!
This worked perfectly for me. Thank you so much!
west0ne said:
More detailed disk-info
Click to expand...
Click to collapse
did you test it? would be nice to get some feedback / results.
cheers.
danjac said:
did you test it? would be nice to get some feedback / results.
cheers.
Click to expand...
Click to collapse
Fastboot seemed to just hang. Going to try downloading a different version and with desktop rather than laptop.
west0ne said:
Fastboot seemed to just hang. Going to try downloading a different version and with desktop rather than laptop.
Click to expand...
Click to collapse
would be nice!
by now, i have one confirmation that twrp and root worked for YB1-X90F (WIFI) from liguangming1981.
but two are better than one
This is my first post. I've added nothing constructive to the forum, and i'm here to get some help. Just wanted to come clean, i'm definitely that guy right now.
To cut to the chase i need to root a Kyocera Duraforce Pro (E6810)
Kingroot is a no go. To the best of my knowledge, there does not exist a forum where someone has successfully done it. I don't mind to get a little sketchy, i have a junk Duraforce pro that still works (half ****ed screen) and ill gladly try something that might brick that one.
Im looking for a direction to go, doesn't have to be a step by step. Anyone personally rooted a Duraforce Pro?
Why do i NEED to? I need to edit the apn settings for my mms to work on bluegrass. The settings are locked, neither verizon nor kyocera is any help. Ive searched far and wide for ways around the grayed out apn menu, my phone has to be rooted first. If you know how to edit apn settings on 6.0.1 without a root let me know. Gotta get my **** picks, cant live without it.
Thanks in advance,
-Senior Bumble****
Hey Senior Bumble,
I was just about to try this on a new phone that I purchased. If you have one that you don't mind bricking, would you mind giving it a shot? Here are the links to root the device. I have a Verizon phone.
https://www.androidinfotech.com/2016/12/unlock-bootloader-kyocera-duraforce-pro.html
https://www.androidinfotech.com/2016/12/root-kyocera-duraforce-pro-marshmallow-twrp.html
Good luck, let me know how it goes!
Any update on this. Was it successful?
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Sorry i took a while to get back to you, no luck.
Both of Sirachi's options ask me to "Put your Mobile in Boot Loader Mode" after this, my computer will no longer recognize the device. "adb devices" returns nothing and "reboot bootloader" fails.
If i use Augustoandro's guide i can get a little further until i reach a dead end. When i run "reboot bootloader" it does take my device to the Kyocera startup screen, it then appears to freeze and is unresponsive. I first tried to proceed after checking "fastboot devices" once, only to have "fastboot oem unlock" fail. I then pulled the battery and retried this time waiting a while on the restart screen. I checked fastboot devices a few times to see if it would change.
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
e1898b6 fastboot
PS C:\adb> fastboot devices
e1898b6 fastboot
PS C:\adb> fastboot devices
e1898b6 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Good news is i've been dicking around with the junk phone (pulling batteries, navigating bootloader menus without being able to see them) and haven't bricked it yet.
Any ideas on why its failing? I would guess its related to adb not being able to send the duraforce directly to bootloader menu? Drivers maybe?
Thanks for all the suggestions, i'm picking up more and more knowledge of the process as i go.
Hey there!
I have the same problem as Senior Bumble...
First attempts I made in rooting was with an E6820 (AT&T branded). With it i did not even got the devices into bootloader. So i bought an E6810 (Verizon branded), and could activate the bootloader. But any attempts to unlock the bootloader failed.
Is there anybody who has another idea how to unlock the bootloader?
Thanks!
Greetings Norb
ebno said:
Hey there!
I have the same problem as Senior Bumble...
First attempts I made in rooting was with an E6820 (AT&T branded). With it i did not even got the devices into bootloader. So i bought an E6810 (Verizon branded), and could activate the bootloader. But any attempts to unlock the bootloader failed.
Is there anybody who has another idea how to unlock the bootloader?
Thanks!
Greetings Norb
Click to expand...
Click to collapse
What version is the E6820 on?
Enabling "OEM unlocking" under developer options in MM doesn't do anything in terms of enabling unsigned bootloaders to go unchecked & unhaulted by what comes before & after if flashed, or even enabling fastboot flashing, etc. in the first place
Has anyone succeeded in flashing and/or rooting the DuraForce Pro? Mine is an E6820 AT&T variant, and I haven't been able to get in either bootloader or recovery mode with the various key combinations found online. The E6810 and E6830 versions all seem to be different devices although they are all "Kyocera Dura Force Pro" models. Any recommendations on accessing the bootloader on my E6820 (I've already enabled Developer Mode & "unlock OEM bootloader" in the settings with little/no effect)?
Kyocera Duraforce Pro E6820 (AT&T)
This smartphone's bootloader is encrypted directly from the factory.. I also have the unlocked AT&T version & even enabling OEM bootloader unlocking doesn't do anything particular that I can see.. The farthest I have gotten is to an Android error screen with the robot's stomach open saying "no command".. I contacted Kyocera directly and was told by a representative that if you were to forget the pin number the phone is essentially bricked and has to be sent into the carrier or Kyocera directly to reflashed because she said there is no way for the user to enter into recovery mode with any button combination!! I shared my concerns & irritations with her and she even said that it didn't make any sense.. I don't think this phone is rootable due to the excessively high levels of encryption and without any help from our carriers or Kyocera we're stuck with bloatware and a slow phone unfortunately.. I'm having major issues with my phone's speed booting up, along with intermittent "drops" with my mobile data connection, and my camera is constantly attempting to auto focus causing me to not be able to record videos or take decent pictures.. If we could root these phones and put a custom rom on them, I really believe that it'll fix many of these issues and other problems we're having but I'm afraid that I'll have to abandon this device for another manufacturer because I have exhausted all efforts to get this thing rooted..
I have had no luck for nearly 2 years in rooting or installing custom recovery on my E6820 AT&T DuraForce Pro (which is soon to be retired as a GPS/Altimeter). I have already ordered a Ulefone Armor 6E as a replacement phone. I have attached below some partition info from my active, working E6820 in case anyone is still attempting to root these (this comes from an app called DiskInfo)
Some of the modules I'm guessing might be involved in locking the bootloader are:
*keymaster
*keymasterbak
*aboot
*abootbak
*boot
*keystore
======Partition info ======
--------------------------
Internal Storage
--------------------------
* zram0 [zram0] Not mounted
Total space: 512 MB
--------------------------
Internal Storage (MMC)
--------------------------
* modem [mmcblk0p1] (/firmware) [vfat]
Used: 83.1 MB, Free: 8.9 MB, Total space: 92 MB
* sbl1 [mmcblk0p2] Not mounted
Total space: 1 MB
* sbl1bak [mmcblk0p3] Not mounted
Total space: 1 MB
* rpm [mmcblk0p4] Not mounted
Total space: 512 KB
* rpmbak [mmcblk0p5] Not mounted
Total space: 512 KB
* tz [mmcblk0p6] Not mounted
Total space: 2 MB
* tzbak [mmcblk0p7] Not mounted
Total space: 2 MB
* cmnlib64 [mmcblk0p8] Not mounted
Total space: 512 KB
* cmnlib64bak [mmcblk0p9] Not mounted
Total space: 512 KB
* cmnlib [mmcblk0p10] Not mounted
Total space: 512 KB
* cmnlibbak [mmcblk0p11] Not mounted
Total space: 512 KB
* keymaster [mmcblk0p12] Not mounted
Total space: 512 KB
* keymasterbak [mmcblk0p13] Not mounted
Total space: 512 KB
* devcfg [mmcblk0p14] Not mounted
Total space: 512 KB
* devcfgbak [mmcblk0p15] Not mounted
Total space: 512 KB
* aboot [mmcblk0p16] Not mounted
Total space: 2 MB
* abootbak [mmcblk0p17] Not mounted
Total space: 2 MB
* boot [mmcblk0p18] Not mounted
Total space: 64 MB
* recovery [mmcblk0p19] Not mounted
Total space: 64 MB
* fota [mmcblk0p20] Not mounted
Total space: 64 MB
* fotabk [mmcblk0p21] Not mounted
Total space: 64 MB
* devparam [mmcblk0p22] Not mounted
Total space: 10 MB
* splash [mmcblk0p23] Not mounted
Total space: 25 MB
* reserve1 [mmcblk0p24] Not mounted
Total space: 512 KB
* reserve2 [mmcblk0p25] Not mounted
Total space: 512 KB
* system [mmcblk0p26] Not mounted
Total space: 4.5 GB
* Cache [mmcblk0p27] (/cache) [ext4]
Used: 89.9 MB, Free: 2 GB, Total space: 2.1 GB
* Data (userdata) [mmcblk0p28] (/data) [ext4]
Used: 18.7 GB, Free: 2.7 GB, Total space: 21.5 GB
* dsp [mmcblk0p29] (/dsp) [ext4]
Used: 8.2 MB, Free: 7.8 MB, Total space: 16 MB
* mdtp [mmcblk0p30] Not mounted
Total space: 32 MB
* devinfo [mmcblk0p31] Not mounted
Total space: 8 MB
* carrier [mmcblk0p32] (/carrier) [ext4]
Used: 5.5 MB, Free: 34.5 MB, Total space: 40 MB
* fotamng [mmcblk0p33] Not mounted
Total space: 257 MB
* reserve3 [mmcblk0p34] Not mounted
Total space: 56 MB
* reserve4 [mmcblk0p35] Not mounted
Total space: 2 MB
* reserve5 [mmcblk0p36] Not mounted
Total space: 2 MB
* fsc [mmcblk0p37] Not mounted
Total space: 512 KB
* ssd [mmcblk0p38] Not mounted
Total space: 512 KB
* DDR [mmcblk0p39] Not mounted
Total space: 512 KB
* fsg [mmcblk0p40] Not mounted
Total space: 2 MB
* misc [mmcblk0p41] Not mounted
Total space: 1 MB
* keystore [mmcblk0p42] Not mounted
Total space: 512 KB
* config [mmcblk0p43] Not mounted
Total space: 512 KB
* oem [mmcblk0p44] Not mounted
Total space: 64 MB
* limits [mmcblk0p45] Not mounted
Total space: 512 KB
* mota [mmcblk0p46] Not mounted
Total space: 512 KB
* reserve6 [mmcblk0p47] Not mounted
Total space: 512 KB
* dip [mmcblk0p48] Not mounted
Total space: 1 MB
* syscfg [mmcblk0p49] Not mounted
Total space: 512 KB
* mcfg [mmcblk0p50] Not mounted
Total space: 4 MB
* apdp [mmcblk0p51] Not mounted
Total space: 512 KB
* msadp [mmcblk0p52] Not mounted
Total space: 512 KB
* dpo [mmcblk0p53] Not mounted
Total space: 512 KB
* log [mmcblk0p54] Not mounted
Total space: 60 MB
* logwork [mmcblk0p55] Not mounted
Total space: 32 MB
* kcs [mmcblk0p56] (/kcs) [ext4]
Used: 9.5 MB, Free: 480 KB, Total space: 10 MB
* cslog [mmcblk0p57] Not mounted
Total space: 16 MB
* bootwork [mmcblk0p58] Not mounted
Total space: 16 MB
* sum [mmcblk0p59] Not mounted
Total space: 1 MB
* sec [mmcblk0p60] Not mounted
Total space: 512 KB
* chkcode [mmcblk0p61] Not mounted
Total space: 512 KB
* dnand [mmcblk0p62] Not mounted
Total space: 8 MB
* sysprop [mmcblk0p63] (/pstore) [ext4]
Used: 6.1 MB, Free: 1.9 MB, Total space: 8 MB
* persist [mmcblk0p64] (/persist) [ext4]
Used: 5.2 MB, Free: 10.8 MB, Total space: 16 MB
* modemst1 [mmcblk0p65] Not mounted
Total space: 2 MB
* modemst2 [mmcblk0p66] Not mounted
Total space: 2 MB
* bfss1 [mmcblk0p67] Not mounted
Total space: 4 MB
* bfss2 [mmcblk0p68] Not mounted
Total space: 8 MB
* reserve7 [mmcblk0p69] Not mounted
Total space: 7 MB
* kcs_work [mmcblk0p70] Not mounted
Total space: 1 MB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
--------------------------
SD Card
--------------------------
* android_meta [mmcblk1p1] Not mounted
Total space: 16 MB
* android_expand [mmcblk1p2] Not mounted
Total space: 14.8 GB
--------------------------
device-mapper
--------------------------
* System [dm-0] (/system) [ext4]
Used: 3.4 GB, Free: 1 GB, Total space: 4.5 GB
* dm-1 [dm-1] (/devparam) [ext4]
Used: 4.4 MB, Free: 5.5 MB, Total space: 9.9 MB
* dm-2 [dm-2] Not mounted
Total space: 21.5 GB
* dm-3 [dm-3] (/mnt/expand/hexSerialNo) [ext4]
Used: 11.3 GB, Free: 3.6 GB, Total space: 14.8 GB
--------------------------
tmpfs mount points
--------------------------
* /dev [tmpfs]
Used: 124 KB, Free: 890 MB, Total space: 890 MB
* /mnt [tmpfs]
Used: 0 B, Free: 890 MB, Total space: 890 MB
* /storage [tmpfs]
Used: 0 B, Free: 890 MB, Total space: 890 MB
* /storage/self [tmpfs]
Used: 0 B, Free: 890 MB, Total space: 890 MB
--------------------------
Memory
--------------------------
* RAM
Used: 1.3 GB, Free: 465 MB, Total space: 1.8 GB
* Swap
Used: 476 MB, Free: 35.5 MB, Total space: 511 MB
Motochopper works
I read the super block from the UFS memory chip on a Huawei P30
Code:
Welcome to Medusa Pro Software version 2.1.0.
Started.
Reader #0: Generic EMV Smartcard Reader 0
Loading firmware. Please wait... Done.
Selected UFS interface.
Selected PIN - CONNECTOR socket.
Please use USB3.0 for better speed.
Connected. Reading information.
Manufacturer name: SAMSUNG
Product name: KLUDG4U1EA-B0C1
Serial Number: 365c76002705
OEM ID: SAMSUNG_OEM_ID
Page size : 4096 B
Block size : 4096 B
Block count : 31246336
Size : 119.20 GB (122056.00 MB)
AttrRefClkFreeq = 0
MaxDataInSize = 32768
MaxDataOutSize = 32768
Connect successful.
---------------------------------------------------------------
Physical partition number: 0
Block count : 1024 (0x400)
Size : 4.00 MB
Physical partition number: 1
Block count : 1024 (0x400)
Size : 4.00 MB
Physical partition number: 2
Block count : 2048 (0x800)
Size : 8.00 MB
P00: GPT (00000000, 00000080) 512 KB
P01: frp (00000080, 00000080) 512 KB
P02: persist (00000100, 00000600) 6 MB
P03: reserved1 (00000700, 00000100) 1024 KB
Physical partition number: 3
Block count : 31234048 (0x1DC9800)
Size : 119.15 GB (122008.00 MB)
P00: GPT (00000000, 00000080) 512 KB
P01: vrl (00000080, 00000080) 512 KB
P02: vrl_backup (00000100, 00000080) 512 KB
P03: modem_secure (00000180, 00000880) 8.5 MB
P04: nvme (00000A00, 00000500) 5 MB
P05: certification (00000F00, 00000100) 1024 KB
P06: oeminfo (00001000, 00006000) 96 MB
P07: secure_storage (00007000, 00002000) 32 MB
P08: modemnvm_factory (00009000, 00001000) 16 MB
P09: modemnvm_backup (0000A000, 00001000) 16 MB
P10: modemnvm_img (0000B000, 00002200) 34 MB
P11: hisee_encos (0000D200, 00000400) 4 MB
P12: veritykey (0000D600, 00000100) 1024 KB
P13: ddr_para (0000D700, 00000100) 1024 KB
P14: lowpower_para (0000D800, 00000100) 1024 KB
P15: batt_tp_para (0000D900, 00000100) 1024 KB
P16: reserved2 (0000DA00, 00001900) 25 MB
P17: splash2 (0000F300, 00005000) 80 MB
P18: bootfail_info (00014300, 00000200) 2048 KB
P19: misc (00014500, 00000200) 2048 KB
P20: dfx (00014700, 00001000) 16 MB
P21: rrecord (00015700, 00001000) 16 MB
P22: cache (00016700, 00006800) 104 MB
P23: fw_lpm3 (0001CF00, 00000100) 1024 KB
P24: reserved3 (0001D000, 00000600) 6 MB
P25: ivp (0001D600, 00000300) 3072 KB
P26: hdcp (0001D900, 00000100) 1024 KB
P27: hisee_img (0001DA00, 00000400) 4 MB
P28: hhee (0001DE00, 00000400) 4 MB
P29: hisee_fs (0001E200, 00000800) 8 MB
P30: fastboot (0001EA00, 00000C00) 12 MB
P31: vector (0001F600, 00000400) 4 MB
P32: isp_boot (0001FA00, 00000200) 2048 KB
P33: isp_firmware (0001FC00, 00000E00) 14 MB
P34: fw_hifi (00020A00, 00000C00) 12 MB
P35: teeos (00021600, 00000800) 8 MB
P36: sensorhub (00021E00, 00001000) 16 MB
P37: erecovery_kernel (00022E00, 00001800) 24 MB
P38: erecovery_ramdisk (00024600, 00002000) 32 MB
P39: erecovery_vendor (00026600, 00001000) 16 MB
P40: kernel (00027600, 00001800) 24 MB
P41: eng_system (00028E00, 00000C00) 12 MB
P42: recovery_ramdisk (00029A00, 00002000) 32 MB
P43: recovery_vendor (0002BA00, 00001000) 16 MB
P44: dts (0002CA00, 00000100) 1024 KB
P45: dto (0002CB00, 00001400) 20 MB
P46: trustfirmware (0002DF00, 00000200) 2048 KB
P47: modem_fw (0002E100, 00003800) 56 MB
P48: eng_vendor (00031900, 00000C00) 12 MB
P49: modem_patch_nv (00032500, 00000400) 4 MB
P50: modem_driver (00032900, 00001400) 20 MB
P51: reserved4 (00033D00, 00000C00) 12 MB
P52: ramdisk (00034900, 00000200) 2048 KB
P53: vbmeta_system (00034B00, 00000100) 1024 KB
P54: vbmeta_vendor (00034C00, 00000100) 1024 KB
P55: vbmeta_odm (00034D00, 00000100) 1024 KB
P56: vbmeta_cust (00034E00, 00000100) 1024 KB
P57: vbmeta_hw_product (00034F00, 00000100) 1024 KB
P58: recovery_vbmeta (00035000, 00000200) 2048 KB
P59: erecovery_vbmeta (00035200, 00000200) 2048 KB
P60: vbmeta (00035400, 00000400) 4 MB
P61: modemnvm_update (00035800, 00001000) 16 MB
P62: modemnvm_cust (00036800, 00001000) 16 MB
P63: patch (00037800, 00002000) 32 MB
P64: preas (00039800, 00012800) 296 MB
P65: preavs (0004C000, 00002000) 32 MB
[B][COLOR="Red"]P66: super (0004E000, 00160000) 5.5 GB[/COLOR][/B]
P67: version (001AE000, 00024000) 576 MB
P68: preload (001D2000, 00047800) 1144 MB
P69: userdata (00219800, 01BB0000) 110.8 GB
Backuping nvme partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SAMSUNG_KLUDG4U1EA-B0C1_nvme_0xa00_0x500_11_06_2020_17_48_51.bin file...
Reading. Please wait... Done.
Elapsed time 00:00:00
SW: 2.1.0; FW: 1.00.
Backuping oeminfo partition...
Opening C:/Program Files/Medusa Pro Software/Backups/SAMSUNG_KLUDG4U1EA-B0C1_oeminfo_0x1000_0x6000_11_06_2020_17_48_51.bin file...
Reading. Please wait... Done.
Elapsed time 00:00:05
SW: 2.1.0; FW: 1.00.
---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------RPMB: Counter of the successful data write requests = 196.
Partition table has been found on device.
RPMB: Counter of the successful data write requests = 196.
Save to E:/tmp file...
Reading partition super... Done.
Reading is finished.
SW: 2.1.0; FW: 1.00.
Then I used the tool "lpunpack" to unpack super. Img, and got this
Code:
cust.img
hw_product.img
odm.img
system.img
vendor.img
Oddly, though, none of these files are in ext4 or Android Sparse:
Code:
λ file *
cust.img: data
hw_product.img: data
odm.img: data
system.img: data
vendor.img: data
I tried using the command mount under ubuntu18, but unfortunately it failed
Code:
[email protected]:~/Desktop/tmp$ sudo mount -t erofs -o loop system.img /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/loop9, missing codepage or helper program, or other error.
I've extracted using: imjtool.
http://newandroidbook.com/tools/imjtool.html
VD171 said:
I've extracted using: imjtool.
http://newandroidbook.com/tools/imjtool.html
Click to expand...
Click to collapse
I tried, and the result is the same
They are erofs partitions.