LGX240F Help Porter TWRP + ROOT
LGX240F Help Porter TWRP + ROOT
(08-12-2018, 11:28 AM)hovatek(08-12-2018, 03:37 AM)tormenta1026 The answer is whether for the two questions I leave the boot and recovery stock without sing of my LGX240F.
https://www.mediafire.com/file/idev1cfbp...f.rar/file
Excuse the delay.
Flash this boot @ https://mega.nz/#!8HhTQKLT!ob6Gw_qOnKpd1...qGXhRvYwDI
let me know if the phone boots up normally after flashing it.
(08-12-2018, 10:56 PM)tormenta1026 ...
Sorry, my mistake.
boot without signature
https://www.mediafire.com/file/50ugxa7oq...t.rar/file
recovery without signature
https://www.mediafire.com/file/v640340ui...y.rar/file
(09-12-2018, 09:38 PM)X3non(08-12-2018, 10:56 PM)tormenta1026 ...
Sorry, my mistake.
boot without signature
https://www.mediafire.com/file/50ugxa7oq...t.rar/file
recovery without signature
https://www.mediafire.com/file/v640340ui...y.rar/file
since you verified an error at your end, try patching boot and rooting using magisk + this current boot.img you have just uploaded
lets know the outcome
- Copying image to cache
- Device platform: arm64-v8a
- Downloading zip
... 0%
- Extracting files
- Boot image is signed with AVB 1.0
- Unpacking boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [7522061]
RAMDISK_SZ [1584132]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
PAGESIZE [2048]
NAME [1494484820]
CMDLINE [bootopt=64S3,32N2,64N2 androidboot.selinux=permissive]
CHECKSUM [b4f94a2be5b5ad3c7cde695019cdd432f7f2490c]
DTB [67694]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
- Checking ramdisk status
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_8b47c07d4c3ad28be4b4b6eccd753ef2318bef70.img.gz]
- Patching ramdisk
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Remove pattern [,verify]
Remove [verity_key]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [fstab.mt6735] -> [.backup/fstab.mt6735]
Backup mismatch entry: [init] -> [.backup/init]
Backup missing entry: [verity_key] -> [.backup/verity_key]
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Loading dtbs from [dtb]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Patch @ 00EFC4D3 [736B69705F696E697472616D667300]->[77616E745F696E697472616D667300]
- Repacking boot image
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER [0]
KERNEL_SZ [7522061]
RAMDISK_SZ [1584132]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
PAGESIZE [2048]
NAME [1494484820]
CMDLINE [bootopt=64S3,32N2,64N2 androidboot.selinux=permissive]
CHECKSUM [b4f94a2be5b5ad3c7cde695019cdd432f7f2490c]
DTB [67694]
KERNEL_FMT [gzip]
RAMDISK_FMT [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER [0]
KERNEL_SZ [7526365]
RAMDISK_SZ [1829839]
SECOND_SZ [0]
EXTRA_SZ [0]
RECOV_DTBO_SZ [0]
PAGESIZE [2048]
NAME [1494484820]
CMDLINE [bootopt=64S3,32N2,64N2 androidboot.selinux=permissive]
CHECKSUM [10b741e13f5e4dbf0a806bd01ff95f936447038b]
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Cleaning up...
- Signing boot image with test keys
****************************
Patched image is placed in
/storage/emulated/0/Download/patched_boot.img
****************************
- All done!
(10-12-2018, 03:52 AM)tormenta1026 As I mentioned the error was when uploading the boot stock sign but even so I went back to try patching the boot.img that went up and I always have bootloop.
I leave the Magisk Manager log.
Magisk Manager was updated to version 6.1.0 (165) and Magisk v18.0.
...
(10-12-2018, 01:24 PM)hovatek(10-12-2018, 03:52 AM)tormenta1026 As I mentioned the error was when uploading the boot stock sign but even so I went back to try patching the boot.img that went up and I always have bootloop.
I leave the Magisk Manager log.
Magisk Manager was updated to version 6.1.0 (165) and Magisk v18.0.
...
Try this then
https://mega.nz/#!IaBCCAIY!M_x9rQfJAG1-J...oFCxMWveO0
(10-12-2018, 04:52 PM)tormenta1026 Always the same bootloop with fastboot and flashtool and always the same thank you very much for your help hovatek.
These LG cell phones are a slow and special embarrassment.
(11-12-2018, 11:14 AM)hovatek(10-12-2018, 04:52 PM)tormenta1026 Always the same bootloop with fastboot and flashtool and always the same thank you very much for your help hovatek.
These LG cell phones are a slow and special embarrassment.
I need you to run this quick test
1. Flash stock boot (-sign)
2. Remove sign using FB Win tools then flash the unsigned boot
3. Unpack then repack the unsigned boot using carliv image kitchen @ https://www.hovatek.com/forum/thread-15817.html (no modification) then flash
I want to know if the phone boots up normally in each test. Ensure to flash back the boot-sign before each test
(12-12-2018, 12:18 AM)tormenta1026 1. Flash stock boot (-sign) (I can only flashtool because fastboot fails.)
2. Works
3. Bootloop and when loading the boot stock on entering the system this message appears (Unfortunately the LDB application stopped).
(17-01-2019, 12:32 AM)tormenta1026I need some recent method to extract the boot.img I have used (QURepack, Carliv, img extractor) and when I rebuild it I always get bootloop.
Thank you very much for your reply.