Urgent: TWRP Install on Schok Volt SV55 (UMX

Urgent: TWRP Install on Schok Volt SV55 (UMX_U693CL) Display Issue

stevenetphone
Enthusiastic Member

7

20-10-2023, 01:51 PM

#1

Subject: Urgent Help Needed for SEO-Optimized TWRP Installation on Schok Volt SV55 (UMX_U693CL, Display Issue with Stock Recovery)

Dear [Recipient's Name],

I trust this message finds you well. I am currently facing a critical technical issue and am reaching out for your expert guidance and assistance. After investing significant time and effort over the past 24 hours, I regret to report that I have been unable to successfully port the necessary files to the Team Win Recovery Project (TWRP) on my Schok Volt SV55 smartphone. These files are based on the UMX_U693CL model but require modification due to a severe display issue encountered with the twrp recovery, which manifests as a persistent blue display with lines and color malfunction.

The challenge I am facing arises from a potential incompatibility between the stock file system and the recovery environment. It appears that specific essential files, vital for a seamless transition to recovery mode, may either differ in nomenclature or be absent according to various online tutorials. This lack of critical transition data has left me bewildered, making it difficult to pinpoint the root cause of the issue.

To provide more context, I have attempted to utilize Orange Fox Recovery 11 on my Schok Volt SV55, originally based on the UMX_U693CL model. However, my efforts have been hampered by an unusual display anomaly. Upon launching Orange Fox Recovery, the screen displays severe distortions, characterized by a persistent orange hue colors. So lets focus on the Twrp because the UMX U693CL kinda works. This issue may be linked to a display kernel driver malfunction, but given my limited expertise in this area, I lack the necessary knowledge to rectify it.

In light of the display challenge, I have attempted to locate an alternative TWRP for the Schok Volt SV55 model, originally based on the UMX_U693CL. Regrettably, the alternative recovery presents a blue display issue. Unfortunately, I am uncertain about the specific TWRP version that is compatible with my device, further complicating the resolution process.

For your convenience, here are the device specifications:

Model: Schok Volt SV55 (Originally based on UMX_U693CL)
Processor: Qualcomm Snapdragon 425, 1.31 GHz Quad-Core
GPU: Qualcomm Adreno ™ 308
Manufacturer: Schok Board
Hardware: Qcomm
Screen Resolution: 480 x 960, 196 DPI
Total RAM: 2 GB
Internal Storage: 16 GB
Android Version: 11
Security Patch: August 5, 2023
Bootloader: Unknown
Build ID: SV55216_01.02.05.230713
Kernel Architecture: arnv71
Kernel Version: 5.19.157-oerf(239713)
Root Access: Yes
Google Play Version: 23.40.14(170300-572056781)
Battery Voltage: 3872mV
Furthermore, I have included all relevant files, including the patched Magisk for this build. While root access has been successfully established, the TWRP file is available; however, display issues continue to pose a significant obstacle to progress. When the device is connected to a computer, it initiates a search for drivers, underscoring the necessity of resolving the blue display malfunction.

I humbly request your expertise in addressing this matter and would greatly appreciate any insights or guidance you can offer. Your proficiency in resolving the blue display issue and identifying the appropriate TWRP version for my Schok Volt SV55 (UMX_U693CL) would be of invaluable assistance. I am eager to conduct tests with any recovery solutions once the display issue is resolved.

Thank you for your time and consideration.

Sincerely,
Steven

Code:

#SchokVoltSV55, #UMX_U693CL, #TWRPInstallation, #TechnicalIssue, #DisplayProblem, #SmartphoneRecovery, #OrangeFoxRecovery, #AndroidRecovery, #Snapdragon425, #DisplayKernelDriver, #RootAccess, #Android11, #BlueDisplayIssue, #DisplayDistortions, #RecoveryEnvironment, #StockRecovery, #DeviceSpecifications, #AndroidRoot, #SmartphoneTroubleshooting, #UMX+U693CL, #TechnicalSupport, #RecoverySolutions, #TechnicalAssistance

Attached Files

ok.png
Size: 73.12 KB / Downloads: 25

AutoResponder
Verified Account

609

20-10-2023, 01:51 PM

#2

Thank you for reaching out for support. Due to high demand, our free support services may experience some delays in response time. We apologize for any inconvenience this may cause.
Alternatively, we offer private support where you can receive dedicated attention and prompt support. These sessions are designed to provide personalized solutions to your specific needs.
If you are interested in scheduling a private session, please visit https://www.hovatek.com/remote

stevenetphone
Enthusiastic Member

7

20-10-2023, 01:52 PM

#3

Subject: Urgent Help Needed for SEO-Optimized TWRP Installation on Schok Volt SV55 (UMX_U693CL, Display Issue with Stock Recovery)

Dear [Recipient's Name],

I trust this message finds you well. I am currently facing a critical technical issue and am reaching out for your expert guidance and assistance. After investing significant time and effort over the past 24 hours, I regret to report that I have been unable to successfully port the necessary files to the Team Win Recovery Project (TWRP) on my Schok Volt SV55 smartphone. These files are based on the UMX_U693CL model but require modification due to a severe display issue encountered with the twrp recovery, which manifests as a persistent blue display with lines and color malfunction.

The challenge I am facing arises from a potential incompatibility between the stock file system and the recovery environment. It appears that specific essential files, vital for a seamless transition to recovery mode, may either differ in nomenclature or be absent according to various online tutorials. This lack of critical transition data has left me bewildered, making it difficult to pinpoint the root cause of the issue.

To provide more context, I have attempted to utilize Orange Fox Recovery 11 on my Schok Volt SV55, originally based on the UMX_U693CL model. However, my efforts have been hampered by an unusual display anomaly. Upon launching Orange Fox Recovery, the screen displays severe distortions, characterized by a persistent orange hue colors. So lets focus on the Twrp because the UMX U693CL kinda works. This issue may be linked to a display kernel driver malfunction, but given my limited expertise in this area, I lack the necessary knowledge to rectify it.

In light of the display challenge, I have attempted to locate an alternative TWRP for the Schok Volt SV55 model, originally based on the UMX_U693CL. Regrettably, the alternative recovery presents a blue display issue. Unfortunately, I am uncertain about the specific TWRP version that is compatible with my device, further complicating the resolution process.

For your convenience, here are the device specifications:

Model: Schok Volt SV55 (Originally based on UMX_U693CL)
Processor: Qualcomm Snapdragon 425, 1.31 GHz Quad-Core
GPU: Qualcomm Adreno ™ 308
Manufacturer: Schok Board
Hardware: Qcomm
Screen Resolution: 480 x 960, 196 DPI
Total RAM: 2 GB
Internal Storage: 16 GB
Android Version: 11
Security Patch: August 5, 2023
Bootloader: Unknown
Build ID: SV55216_01.02.05.230713
Kernel Architecture: arnv71
Kernel Version: 5.19.157-oerf(239713)
Root Access: Yes
Google Play Version: 23.40.14(170300-572056781)
Battery Voltage: 3872mV
Furthermore, I have included all relevant files, including the patched Magisk for this build. While root access has been successfully established, the TWRP file is available; however, display issues continue to pose a significant obstacle to progress. When the device is connected to a computer, it initiates a search for drivers, underscoring the necessity of resolving the blue display malfunction.

I humbly request your expertise in addressing this matter and would greatly appreciate any insights or guidance you can offer. Your proficiency in resolving the blue display issue and identifying the appropriate TWRP version for my Schok Volt SV55 (UMX_U693CL) would be of invaluable assistance. I am eager to conduct tests with any recovery solutions once the display issue is resolved.

Thank you for your time and consideration.

Sincerely,
Steven

Code:

https://drive.google.com/drive/folders/1mewtrNZDj1mDEOteMpmRHYqprRJDgDv1?usp=share_link

Code:

#SchokVoltSV55, #UMX_U693CL, #TWRPInstallation, #TechnicalIssue, #DisplayProblem, #SmartphoneRecovery, #OrangeFoxRecovery, #AndroidRecovery, #Snapdragon425, #DisplayKernelDriver, #RootAccess, #Android11, #BlueDisplayIssue, #DisplayDistortions, #RecoveryEnvironment, #StockRecovery, #DeviceSpecifications, #AndroidRoot, #SmartphoneTroubleshooting, #UMX+U693CL, #TechnicalSupport, #RecoverySolutions, #TechnicalAssistance

AutoResponder
Verified Account

609

20-10-2023, 01:52 PM

#4

Thank you for reaching out for support. Due to high demand, our free support services may experience some delays in response time. We apologize for any inconvenience this may cause.
Alternatively, we offer private support where you can receive dedicated attention and prompt support. These sessions are designed to provide personalized solutions to your specific needs.
If you are interested in scheduling a private session, please visit https://www.hovatek.com/remote

stevenetphone
Enthusiastic Member

7

20-10-2023, 01:53 PM

#5

I trust this message finds you well. I am currently facing a critical technical issue and am reaching out for your expert guidance and assistance. After investing significant time and effort over the past 24 hours, I regret to report that I have been unable to successfully port the necessary files to the Team Win Recovery Project (TWRP) on my Schok Volt SV55 smartphone. These files are based on the UMX_U693CL model but require modification due to a severe display issue encountered with the twrp recovery, which manifests as a persistent blue display with lines and color malfunction.

The challenge I am facing arises from a potential incompatibility between the stock file system and the recovery environment. It appears that specific essential files, vital for a seamless transition to recovery mode, may either differ in nomenclature or be absent according to various online tutorials. This lack of critical transition data has left me bewildered, making it difficult to pinpoint the root cause of the issue.

To provide more context, I have attempted to utilize Orange Fox Recovery 11 on my Schok Volt SV55, originally based on the UMX_U693CL model. However, my efforts have been hampered by an unusual display anomaly. Upon launching Orange Fox Recovery, the screen displays severe distortions, characterized by a persistent orange hue colors. So lets focus on the Twrp because the UMX U693CL kinda works. This issue may be linked to a display kernel driver malfunction, but given my limited expertise in this area, I lack the necessary knowledge to rectify it.

In light of the display challenge, I have attempted to locate an alternative TWRP for the Schok Volt SV55 model, originally based on the UMX_U693CL. Regrettably, the alternative recovery presents a blue display issue. Unfortunately, I am uncertain about the specific TWRP version that is compatible with my device, further complicating the resolution process.

For your convenience, here are the device specifications:

Model: Schok Volt SV55 (Originally based on UMX_U693CL)
Processor: Qualcomm Snapdragon 425, 1.31 GHz Quad-Core
GPU: Qualcomm Adreno ™ 308
Manufacturer: Schok Board
Hardware: Qcomm
Screen Resolution: 480 x 960, 196 DPI
Total RAM: 2 GB
Internal Storage: 16 GB
Android Version: 11
Security Patch: August 5, 2023
Bootloader: Unknown
Build ID: SV55216_01.02.05.230713
Kernel Architecture: arnv71
Kernel Version: 5.19.157-oerf(239713)
Root Access: Yes
Google Play Version: 23.40.14(170300-572056781)
Battery Voltage: 3872mV
Furthermore, I have included all relevant files, including the patched Magisk for this build. While root access has been successfully established, the TWRP file is available; however, display issues continue to pose a significant obstacle to progress. When the device is connected to a computer, it initiates a search for drivers, underscoring the necessity of resolving the blue display malfunction.

I humbly request your expertise in addressing this matter and would greatly appreciate any insights or guidance you can offer. Your proficiency in resolving the blue display issue and identifying the appropriate TWRP version for my Schok Volt SV55 (UMX_U693CL) would be of invaluable assistance. I am eager to conduct tests with any recovery solutions once the display issue is resolved.

Thank you for your time and consideration.

Sincerely,
Steven

Code:

https://drive.google.com/drive/folders/1mewtrNZDj1mDEOteMpmRHYqprRJDgDv1?usp=share_link

Code:

#SchokVoltSV55, #UMX_U693CL, #TWRPInstallation, #TechnicalIssue, #DisplayProblem, #SmartphoneRecovery, #OrangeFoxRecovery, #AndroidRecovery, #Snapdragon425, #DisplayKernelDriver, #RootAccess, #Android11, #BlueDisplayIssue, #DisplayDistortions, #RecoveryEnvironment, #StockRecovery, #DeviceSpecifications, #AndroidRoot, #SmartphoneTroubleshooting, #UMX+U693CL, #TechnicalSupport, #RecoverySolutions, #TechnicalAssistance

AutoResponder
Verified Account

609

20-10-2023, 01:53 PM

#6

Thank you for reaching out for support. Due to high demand, our free support services may experience some delays in response time. We apologize for any inconvenience this may cause.
Alternatively, we offer private support where you can receive dedicated attention and prompt support. These sessions are designed to provide personalized solutions to your specific needs.
If you are interested in scheduling a private session, please visit https://www.hovatek.com/remote

kelvinchinedu
Contributor

1,647

23-10-2023, 09:05 PM

#7

If u have recovery partition or vendor_boot drop here

stevenetphone
Enthusiastic Member

7

24-10-2023, 06:20 PM

#8

(23-10-2023, 09:05 PM)kelvinchinedu If u have recovery partition or vendor_boot drop here

If this is the way to get the vender

Code:

Microsoft Windows [Version 10.0.19043.906]

(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator>adb shell su

df -h

Filesystem            Size  Used Avail Use% Mounted on

tmpfs                929M  1.1M  928M  1% /dev

tmpfs                929M    0  929M  0% /mnt

/dev/block/mmcblk0p39  11M  160K  11M  2% /metadata

/dev/block/dm-0      576M  574M  1.7M 100% /

/dev/block/dm-1      780M  777M  2.3M 100% /product

/dev/block/dm-2      279M  278M  912K 100% /vendor

/dev/block/dm-3      124M  124M  404K 100% /system_ext

magisk                929M  2.8M  926M  1% /debug_ramdisk

tmpfs                929M    0  929M  0% /apex

tmpfs                929M  352K  928M  1% /linkerconfig

/dev/block/mmcblk0p38 232M  1.0M  231M  1% /cache

/dev/block/mmcblk0p1  84M  76M  7.5M  91% /vendor/firmware_mnt

/dev/block/mmcblk0p34  12M  6.9M  4.8M  59% /vendor/dsp

/dev/block/mmcblk0p40  27M  536K  26M  2% /mnt/vendor/persist

/dev/block/dm-4        11G  7.7G  3.6G  69% /data

tmpfs                929M    0  929M  0% /data_mirror

worker                929M    0  929M  0% /debug_ramdisk/.magisk/worker

/data/media            11G  7.7G  3.6G  69% /mnt/runtime/default/emulated

/dev/fuse              11G  7.7G  3.6G  69% /mnt/user/0/emulated

dd if=/dev/block/dm-2 of=/sdcard/vender.img

582888+0 records in

582888+0 records out

298438656 bytes (285 M) copied, 16.609775 s, 17 M/s

dd if=/dev/block/dm-2 of=/sdcard/vender.img^Z

C:\Users\Administrator>dd if=/dev/block/mmcblk0p34 of=/sdcard/firmware_mnt.img

'dd' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\Administrator>adb shell su

dd if=/dev/block/mmcblk0p34 of=/sdcard/firmware_mnt.img

32768+0 records in

32768+0 records out

16777216 bytes (16 M) copied, 2.932504 s, 5.4 M/s

dd if=/dev/block/mmcblk0p40 of=/sdcard/persist.img

65536+0 records in

65536+0 records out

33554432 bytes (32 M) copied, 2.855434 s, 11 M/s

then i included the vender files alonge with the stock boot and patched magisk boot.img and original recovery.img

vender.img

Code:

https://drive.google.com/file/d/1c8PdLQuxXYby1jq_5WfsZeo5FXwDbZaG/view?usp=drive_link

Persist.img

Code:

https://drive.google.com/file/d/1yUQMcm24mjJwmjs3dz2pseUXnRtfbl_1/view?usp=drive_link

Stock Boot.img

Code:

https://drive.google.com/file/d/1Yoy0_7uBx-HacvOtA4R1SRhGPcXWkGLw/view?usp=sharing

Magisk Patched Boot.img

Code:

https://drive.google.com/file/d/1gSQgBFF02N0Y5D33rVdR_kSY4hprYQOZ/view?usp=drive_link

Stock Recovery.img

Code:

https://drive.google.com/file/d/1wnJJPFBs07hJQ_cqSkwWvFkpNcnkGDLP/view?usp=drive_link

Thank You

This post was last modified: 24-10-2023, 06:23 PM by stevenetphone.

stevenetphone
Enthusiastic Member

7

24-10-2023, 08:46 PM

#9

O my freaking #### i cant believe it i actually ported it myself Here you go people i used chat gpt to edit the default.prop file in hex lol hehehehehe

Code:

https://drive.google.com/file/d/1lSZQIH_xcyrAFzCfcNzylv5b5HBFAMoh/view?usp=drive_link

Ok there seems to be an issue in the fstab file because on twrp i goto backup and i have a 128gb memory card in it it says select storage sdcard (115412mb)
micro sd card (115412mb) I have to fix anyone stock

Code:

# Copyright (c) 2017,2021 The Linux Foundation. All rights reserved.

#

# Redistribution and use in source and binary forms, with or without

# modification, are permitted provided that the following conditions are

# met:

#    * Redistributions of source code must retain the above copyright

#      notice, this list of conditions and the following disclaimer.

#    * Redistributions in binary form must reproduce the above

#      copyright notice, this list of conditions and the following

#      disclaimer in the documentation and/or other materials provided

#      with the distribution.

#    * Neither the name of The Linux Foundation nor the names of its

#      contributors may be used to endorse or promote products derived

#      from this software without specific prior written permission.

#

# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED

# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT

# ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS

# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN

# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# Vendor variant of recovery.fstab. Same as recovery.fstab, with additional vendor entry.

#device        mount point      fstype        [device2] [length=]

system                                    /system        ext4    ro,barrier=1                                                    wait,avb=vbmeta_system,logical,first_stage_mount

/dev/block/bootdevice/by-name/cache        /cache          ext4    noatime,nosuid,nodev,barrier=1,data=ordered                    wait,check

vendor                                    /vendor        ext4    ro,barrier=1                                                    wait,avb,logical,first_stage_mount

product                                    /product        ext4    ro,barrier=1,discard                                            wait,avb=vbmeta_system,logical,first_stage_mount

system_ext                                /system_ext    ext4    ro,barrier=1,discard                                            wait,avb=vbmeta_system,logical,first_stage_mount

/dev/block/bootdevice/by-name/metadata    /metadata      ext4    noatime,nosuid,nodev,discard                                    wait,check,formattable,check,first_stage_mount

/dev/block/bootdevice/by-name/userdata    /data          f2fs    noatime,nosuid,nodev,discard                                    wait,check,encryptable=footer

/dev/block/mmcblk1p1                      /sdcard        vfat    nosuid,nodev                                                    wait

/dev/block/bootdevice/by-name/boot        /boot          emmc    defaults                                                        defaults

/dev/block/bootdevice/by-name/recovery    /recovery      emmc    defaults                                                        defaults

/dev/block/bootdevice/by-name/misc        /misc          emmc    defaults                                                        defaults

/dev/block/bootdevice/by-name/persist      /mnt/umx_persist        ext4    barrier=1                                                    wait

twrp stab

Code:

# twrp.fstab

#

/cache     ext4 /dev/block/bootdevice/by-name/cache        noatime,nosuid,nodev,barrier=1,data=ordered                    wait,check

#

system     ext4 /system    ro,barrier=1                                                    wait,avb=vbmeta_system,logical,first_stage_mount                                                  wait

/boot     emmc /dev/block/bootdevice/by-name/boot    defaults                                                        defaults

/recovery     emmc /dev/block/bootdevice/by-name/recovery    defaults                                                        defaults

/misc     emmc /dev/block/bootdevice/by-name/misc    defaults                                                        defaults

/mnt/umx_persist     ext4 /dev/block/bootdevice/by-name/persist    barrier=1                                                    wait

/system_ext     ext4 /system_ext        ro,barrier=1,discard 

/data     ftfs /dev/block/bootdevice/by-name/userdata          noatime,nosuid,nodev,discard                                    

/logo     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo     flags=display="Logo";backup=1;flashimg=1

vendor     ext4 /vendor     ro,barrier=1                                                    wait,avb,logical,first_stage_mount

/nvram     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram     flags=display="NvRam";backup=1;flashimg=1

/nvdata     ext4 /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata flags=display="NvData";backup=1;flashimg=1

/frp     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp     flags=display="FRP";backup=1

/proinfo     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo flags=display="ProInfo";backup=1

/product     ext4 /product ro,barrier=1,discard  

/expdb     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb

/seccfg     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg

/oemkeystore emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/oemkeystore

/secro     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/secro     flags=display="Secro";backup=1

/keystore     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/keystore

/tee1     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1     flags=display="tee1";backup=1

/tee2     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2     flags=backup=1;subpartitionof=/tee1

/metadata     ext4    /dev/block/bootdevice/by-name/metadata    noatime,nosuid,nodev,discard                                    wait,check,formattable,check,first_stage_mount

/protect_f     ext4 /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 flags=display="Protect_F";backup=1

/protect_s     ext4 /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 flags=display="Protect_S";backup=1

/lk         emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk     flags=display="UBoot";backup=1

/para     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para     flags=display="Para";backup=1

#

/sdcard vfat /dev/block/mmcblk1p1    nosuid,nodev                                                    wait

/storage        ext4    /data/media/0                                                      flags=display="Internal Storage";usermrf;backup=1;fsflags="bind";removable

#

#/flashinfo     emmc /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/flashinfo

#

/external_sd auto /dev/block/mmcblk1p1 flags=removable;storage;display="SDCARD"

/usbotg     auto    /dev/block/sda1     flags=removable;storage;display="USB-OTG"

i used twrp from same display size and ported it that way

This post was last modified: 24-10-2023, 08:53 PM by stevenetphone.

stevenetphone
Enthusiastic Member

7

24-10-2023, 10:45 PM

#10

ok this is what i got

Code:

# twrp.fstab

#

/cache            ext4    /dev/block/bootdevice/by-name/cache         noatime,nosuid,nodev,barrier=1,data=ordered                     wait,check

#

system        ext4    /system    ro,barrier=1                                                    wait,avb=vbmeta_system,logical,first_stage_mount                                                   wait

/boot            emmc    /dev/block/bootdevice/by-name/boot    defaults                                                        defaults

/recovery        emmc    /dev/block/bootdevice/by-name/recovery    defaults                                                        defaults

/misc        emmc    /dev/block/bootdevice/by-name/misc    defaults                                                        defaults

/mnt/umx_persist        ext4    /dev/block/bootdevice/by-name/persist    barrier=1                                                    wait

/system_ext            ext4    /system_ext        ro,barrier=1,discard 

/data            ext4    /dev/block/bootdevice/by-name/userdata           noatime,nosuid,nodev,discard                                    

/logo            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo            flags=display="Logo";backup=1;flashimg=1

vendor            ext4    /vendor            ro,barrier=1                                                    wait,avb,logical,first_stage_mount

/nvram            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram            flags=display="NvRam";backup=1;flashimg=1

/nvdata            ext4    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata        flags=display="NvData";backup=1;flashimg=1

/frp            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp            flags=display="FRP";backup=1

/proinfo        emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo        flags=display="ProInfo";backup=1

/product        ext4    /product        ro,barrier=1,discard  

/expdb            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb

/seccfg            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg

/oemkeystore    emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/oemkeystore

/secro            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/secro            flags=display="Secro";backup=1

/keystore        emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/keystore

/tee1            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1            flags=display="tee1";backup=1

/tee2            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2            flags=backup=1;subpartitionof=/tee1

/metadata        ext4    /dev/block/bootdevice/by-name/metadata    noatime,nosuid,nodev,discard                                    wait,check,formattable,check,first_stage_mount

/protect_f        ext4    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1        flags=display="Protect_F";backup=1

/protect_s        ext4    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2        flags=display="Protect_S";backup=1

/lk                emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk            flags=display="UBoot";backup=1

/para            emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para            flags=display="Para";backup=1

#

/sdcard    vfat    /dev/block/mmcblk1p1    nosuid,nodev                                                    wait

/storage        ext4    /data/media/0                                                       flags=display="Internal Storage";usermrf;backup=1;fsflags="bind";removable

#

#/flashinfo        emmc    /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/flashinfo

#

/external_sd    auto    /dev/block/mmcblk1p1     flags=removable;storage;display="SDCARD"

/usbotg            auto    /dev/block/sda1             flags=removable;storage;display="USB-OTG"

it loads into twrp but when it loads it has wronge name and it will not boot into system with it installed and heres the aik port and aik stock with the images in acordingly

Code:

https://drive.google.com/file/d/1eg10nbPYwbynpPupy8OnmVwwdJdmQAwc/view?usp=drive_link

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions