Hello all. I recently flashed my phone to stock to fix some problems I was having in a CM nightly and I have been having a hard time getting back onto CM10.
Here is a list of things I have done in an attempt to get back onto CM10.
I have flashed to 2.3.6 stock, rooted, flashed CWM (newest version, touch and non-touch) and tried to flash cm10
Flashed UCLD3 and installed CWM, and team win recovery (newest versions) and still get a status 7. I am unsure what version of android I need to be on in order to get back to CM10. I have been going at this for a few hours on 2 separate days and it is getting quite frustrating. I consistently get a status 7 error.
I have, in both CWM and TWRP wiped cache, dalvik cache, and system prior to attempting to install cm10, as well as having tried to instal cm9 and 9.1. Nothing seems to work and I am unsure why. I will attach a log of what I attempted to do below this.
Starting recovery on Tue Jan 22 22:37:05 2013
Loading volume table...
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p8 (null)
2 /recovery emmc /dev/block/mmcblk0p22 (null)
3 /efs ext4 /dev/block/mmcblk0p21 (null)
4 /data ext4 /dev/block/mmcblk0p25 (null)
5 /system ext4 /dev/block/mmcblk0p24 (null)
6 /cache ext4 /dev/block/mmcblk0p26 (null)
7 /emmc vfat /dev/block/mmcblk0p28 (null)
8 /sdcard vfat /dev/block/mmcblk1p1 (null)
I:Internal path defined: '/emmc'
I:External path defined: '/sdcard'
Pixel format: 800x1280 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (800 x 1280)
I:=> Installing busybox into /sbin
ln: /sbin/mke2fs: File exists
ln: /sbin/sh: File exists
ln: /sbin/tune2fs: File exists
I:=> Linking mtab
I:=> Getting locations
Wevice does not support /proc/emmc
Wevice does not support /proc/mtd
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
I:=> Created /efs folder.
* Verifying partition sizes...
du: /emmc/.android_secure: No such file or directory
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p24 | ext4 | 1048576 | 800252 | 1 | f |
| data | /dev/block/mmcblk0p25 | ext4 | 2099200 | 112916 | 1 | f |
| boot | /dev/block/mmcblk0p8 | emmc | 10240 | 10240 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 10240 | 10240 | 0 | i |
| cache | /dev/block/mmcblk0p26 | ext4 | 309248 | 16600 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 15554048 | 493344 | 1 | n |
| emmc | /dev/block/mmcblk0p28 | vfat | 11369472 | 6240 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| efs | /dev/block/mmcblk0p21 | ext4 | 10240 | 4356 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:boot information:
mnt: 'boot'
blk: '/dev/block/mmcblk0p8'
dev: '/dev/block/mmcblk0p8'
fst: 'emmc'
fnm: ''
format location: '/dev/block/mmcblk0p8'
mountable: 0
backup method: 2
memory type: 2
I:system information:
mnt: 'system'
blk: '/dev/block/mmcblk0p24'
dev: '/dev/block/mmcblk0p24'
fst: 'ext4'
fnm: ''
format location: '/dev/block/mmcblk0p24'
mountable: 1
backup method: 3
memory type: 2
I:data information:
mnt: 'data'
blk: '/dev/block/mmcblk0p25'
dev: '/dev/block/mmcblk0p25'
fst: 'ext4'
fnm: ''
format location: '/dev/block/mmcblk0p25'
mountable: 1
backup method: 3
memory type: 2
I:cache information:
mnt: 'cache'
blk: '/dev/block/mmcblk0p26'
dev: '/dev/block/mmcblk0p26'
fst: 'ext4'
fnm: ''
format location: '/dev/block/mmcblk0p26'
mountable: 1
backup method: 3
memory type: 2
I:recovery information:
mnt: 'recovery'
blk: '/dev/block/mmcblk0p22'
dev: '/dev/block/mmcblk0p22'
fst: 'emmc'
fnm: ''
format location: '/dev/block/mmcblk0p22'
mountable: 0
backup method: 2
memory type: 2
I:sdcext information:
mnt: 'sdcard'
blk: '/dev/block/mmcblk1p1'
dev: '/dev/block/mmcblk1p1'
fst: 'vfat'
fnm: ''
format location: '/dev/block/mmcblk1p1'
mountable: 1
backup method: 1
memory type: 2
I:sdcint information:
mnt: 'emmc'
blk: '/dev/block/mmcblk0p28'
dev: '/dev/block/mmcblk0p28'
fst: 'vfat'
fnm: ''
format location: '/dev/block/mmcblk0p28'
mountable: 1
backup method: 1
memory type: 2
I:sd-ext information:
mnt: 'sd-ext'
blk: '/dev/block/mmcblk1p2'
dev: ''
fst: ''
fnm: ''
format location: ''
mountable: 1
backup method: 3
memory type: 0
I:android_secure information:
mnt: '.android_secure'
blk: '/emmc'
dev: '/emmc/.android_secure'
fst: 'vfat'
fnm: ''
format location: ''
mountable: 0
backup method: 3
memory type: 0
I:special 1 information:
mnt: 'efs'
blk: '/dev/block/mmcblk0p21'
dev: '/dev/block/mmcblk0p21'
fst: 'ext4'
fnm: ''
format location: '/dev/block/mmcblk0p21'
mountable: 1
backup method: 3
memory type: 2
I:special 2 information:
mnt: ''
blk: ''
dev: ''
fst: ''
fnm: ''
format location: ''
mountable: 0
backup method: 1
memory type: 0
I:special 3 information:
mnt: ''
blk: ''
dev: ''
fst: ''
fnm: ''
format location: ''
mountable: 0
backup method: 1
memory type: 0
I:Loading package: TWRP (/script/ui.xml)
I:Loading package: TWRP (/emmc/TWRP/theme/ui.zip)
I:Loading package: TWRP (/res/ui.xml)
I:Loading resources...
I:Loading variables...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page clear_vars
I:Loading page confirm_action
I:Loading page action_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page wipe
I:Loading page backup
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backup_run
I:Loading page restore
I:Unable to open '/emmc/TWRP/BACKUPS/4db46581'
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page reboot
I:Loading page settings
I:Loading page timezone
I:Loading page advanced
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageracction
I:Loading page decrypt
I:Loading page trydecrypt
I:Loading page terminalfolder
I:Loading page terminalcommand
I:Switching packages (TWRP)
Processing arguments (1)...
I:Set page: 'clear_vars'
I:Set page: 'main2'
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76I
ro.build.display.id=full_i717-eng 4.0.4 IMM76I eng.bigbiff.20120711.094109 test-keys
ro.build.version.incremental=eng.bigbiff.20120711.094109
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed Jul 11 09:41:47 EDT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=bigbiff
ro.build.host=nas
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_i717
ro.product.device=i717
ro.product.board=i717
ro.product.cpu.abi=armeabi
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=i717
ro.build.description=full_i717-eng 4.0.4 IMM76I eng.bigbiff.20120711.094109 test-keys
ro.build.fingerprint=Android/full_i717/i717:4.0.4/IMM76I/eng.bigbiff.20120711.094109:eng/test-keys
ro.build.characteristics=default
ro.cm.device=i717
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=4db46581
ro.bootmode=unknown
ro.baseband=csfb
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
service.adb.root=1
Running boot script...
sh: invalid number '1000000000000'
Finished running boot script.
I:Attempt to load settings from settings file...
I:Switching packages (TWRP)
I:Set page: 'restore'
I:Unable to open '/sdcard/TWRP/BACKUPS/4db46581'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'wipe'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Formatting /cache...
I:tw_format: Formatting "/dev/block/mmcblk0p26" as "ext4"
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p26
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
19344 inodes, 77312 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=79691776
3 block groups
32768 blocks per group, 32768 fragments per group
6448 inodes per group
Superblock backups stored on blocks:
32768
Writing inode tables: 0/31/32/3done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
du: /emmc/.android_secure: No such file or directory
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p24 | ext4 | 1048576 | 800252 | 1 | f |
| data | /dev/block/mmcblk0p25 | ext4 | 2099200 | 112916 | 1 | f |
| boot | /dev/block/mmcblk0p8 | emmc | 10240 | 10240 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 10240 | 10240 | 0 | i |
| cache | /dev/block/mmcblk0p26 | ext4 | 309248 | 16552 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 15554048 | 493344 | 1 | n |
| emmc | /dev/block/mmcblk0p28 | vfat | 11369472 | 6240 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| efs | /dev/block/mmcblk0p21 | ext4 | 10240 | 4356 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
-- Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
Cleaned: /cache/dalvik-cache...
Cleaned: /cache/dc
/sd-ext not present, skipping
-- Dalvik Cache Directories Wipe Complete!
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
du: /emmc/.android_secure: No such file or directory
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p24 | ext4 | 1048576 | 800252 | 1 | f |
| data | /dev/block/mmcblk0p25 | ext4 | 2099200 | 58952 | 1 | f |
| boot | /dev/block/mmcblk0p8 | emmc | 10240 | 10240 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 10240 | 10240 | 0 | i |
| cache | /dev/block/mmcblk0p26 | ext4 | 309248 | 16552 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 15554048 | 493344 | 1 | n |
| emmc | /dev/block/mmcblk0p28 | vfat | 11369472 | 6240 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| efs | /dev/block/mmcblk0p21 | ext4 | 10240 | 4356 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
-- Factory reset started.
Formatting /data...
I:tw_format: Formatting "/dev/block/mmcblk0p25" as "ext4"
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p25
mke2fs 1.41.12 (17-May-2010)
warning: 512 blocks unused.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
131328 inodes, 524288 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=536870912
16 block groups
32768 blocks per group, 32768 fragments per group
8208 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: 0/16 1/16 2/16 3/16 4/16 5/16 6/16 7/16 8/16 9/1610/1611/1612/1613/1614/1615/16done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Formatting /cache...
I:tw_format: Formatting "/dev/block/mmcblk0p26" as "ext4"
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p26
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
19344 inodes, 77312 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=79691776
3 block groups
32768 blocks per group, 32768 fragments per group
6448 inodes per group
Superblock backups stored on blocks:
32768
Writing inode tables: 0/31/32/3done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
E:unknown volume for path [/sd-ext]
-- Factory reset complete.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
du: /emmc/.android_secure: No such file or directory
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p24 | ext4 | 1048576 | 800252 | 1 | f |
| data | /dev/block/mmcblk0p25 | ext4 | 2099200 | 68608 | 1 | f |
| boot | /dev/block/mmcblk0p8 | emmc | 10240 | 10240 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 10240 | 10240 | 0 | i |
| cache | /dev/block/mmcblk0p26 | ext4 | 309248 | 16552 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 15554048 | 493344 | 1 | n |
| emmc | /dev/block/mmcblk0p28 | vfat | 11369472 | 6240 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| efs | /dev/block/mmcblk0p21 | ext4 | 10240 | 4356 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Formatting /system...
I:tw_format: Formatting "/dev/block/mmcblk0p24" as "ext4"
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p24
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262144 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Writing inode tables: 0/81/82/83/84/85/86/87/8done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
du: /emmc/.android_secure: No such file or directory
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p24 | ext4 | 1048576 | 34052 | 1 | f |
| data | /dev/block/mmcblk0p25 | ext4 | 2099200 | 68608 | 1 | f |
| boot | /dev/block/mmcblk0p8 | emmc | 10240 | 10240 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 10240 | 10240 | 0 | i |
| cache | /dev/block/mmcblk0p26 | ext4 | 309248 | 16552 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 15554048 | 493344 | 1 | n |
| emmc | /dev/block/mmcblk0p28 | vfat | 11369472 | 6240 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| efs | /dev/block/mmcblk0p21 | ext4 | 10240 | 4356 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
-- Install /sdcard/cm-10-20130120-NIGHTLY-quincyatt.zip ...
Finding update package...
I:Update location: /sdcard/cm-10-20130120-NIGHTLY-quincyatt.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "SGH-I717" || getprop("ro.build.product") == "SGH-I717" ||
getprop("ro.product.device") == "quincyatt" || getprop("ro.build.product") == "quincyatt"
assert failed: getprop("ro.product.device") == "SGH-I717" || getprop("ro.build.product") == "SGH-I717" || getprop("ro.product.device") == "quincyatt" || getprop("ro.build.product") == "quincyatt"
E:Error in /sdcard/cm-10-20130120-NIGHTLY-quincyatt.zip
(Status 7)
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
du: /emmc/.android_secure: No such file or directory
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p24 | ext4 | 1048576 | 34052 | 1 | f |
| data | /dev/block/mmcblk0p25 | ext4 | 2099200 | 68608 | 1 | f |
| boot | /dev/block/mmcblk0p8 | emmc | 10240 | 10240 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 10240 | 10240 | 0 | i |
| cache | /dev/block/mmcblk0p26 | ext4 | 309248 | 16552 | 1 | f |
| sdcard | /dev/block/mmcblk1p1 | vfat | 15554048 | 493344 | 1 | n |
| emmc | /dev/block/mmcblk0p28 | vfat | 11369472 | 6240 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| efs | /dev/block/mmcblk0p21 | ext4 | 10240 | 4356 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
Error flashing zip '/sdcard/cm-10-20130120-NIGHTLY-quincyatt.zip'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'backup'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Click to expand...
Click to collapse
What version of cwm and twrp did you use? Saying " newest " is not sufficient.
FYI. Status 7 means the recovery is outdated.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I was using TWRP 2.2 and CWM from 9/12, I'm unsure what version it was, its no longer installed. I am currently back on UCLD3.
Get TWRP 2.3.3.0. Issue will be solved.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Will attempt and report back, thanks.
Big thank you, worked perfectly. Appreciate it!
All you had to do was ask what status 7 error means. . . I'm just saying.
That was the longest post ever.
Good to hear. Would you mind putting " solved " in your thread title please? It helps other users find the solution for this type of issue. Happy flashing!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Hello, i want extract the stockfw i have successful extract the kdz to cab and to dz (with linux).
i have download some tool for dz file but exist a problem with HEADER (probably is different... no iam sure 100 it is different...)
i post the python script error for understand better my problem...
Code:
[!] Error: Unsupported DZ file format.
[ ] Expected: 0x32 0x96 0x18 0x74 ,
but received 0x44 0xdd 0x55 0xaa .
the python script is dzfiletools.py (downloaded from xda), that python tool have that line
Code:
dz_header = "\x32\x96\x18\x74"
dz_sub_header = "\x30\x12\x95\x78"
dz_sub_len = 512
how to insert the right value from lg l3 II dz header value?
Code:
0000000: 44dd 55aa ffff ffff 2b17 d205 4c47 4534 D.U.....+...LGE4
0000010: 3330 0000 0000 0000 0000 0000 0000 0000 30..............
0000020: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000030: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000040: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000050: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000060: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000070: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000080: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000090: ffff ffff ffff ffff ffff ffff ffff ffff ................
The whole python tool http://paste.ubuntu.com/7473191/
Hmmm
Naxil said:
Hello, i want extract the stockfw i have successful extract the kdz to cab and to dz (with linux).
i have download some tool for dz file but exist a problem with HEADER (probably is different... no iam sure 100 it is different...)
i post the python script error for understand better my problem...
Code:
[!] Error: Unsupported DZ file format.
[ ] Expected: 0x32 0x96 0x18 0x74 ,
but received 0x44 0xdd 0x55 0xaa .
the python script is dzfiletools.py (downloaded from xda), that python tool have that line
Code:
dz_header = "\x32\x96\x18\x74"
dz_sub_header = "\x30\x12\x95\x78"
dz_sub_len = 512
how to insert the right value from lg l3 II dz header value?
Click to expand...
Click to collapse
I have Never managed and believe me i have tried ..
easiest way to obtain all partitions i found is to:
Flash Stock (the one you want to extract)
Root (busybox might be needed but not sure)
enable usb debugging
Run the attached tool (it will automatically dump all partitions from phone {just like extracting .dz})
Why do you want it anyway ?
ROM building ?
no, iam not able to make a rom.. but i try to understand HOW the roms works (i have only understand that, the roms (Stock) is divided in
1 boot (need to be modded or exploited for change and load different recovery right??)
2 recovery
3 system
4 data/cache
If i not mess with boot and recovery (now i have the cwm on recovery) i can't brick my phone right? or i can always replace it with new kdz (windows + kdzupd)
I want the systemUI from 430 or other kind of file for have back the menu retroillumination...
Easy
Naxil said:
no, iam not able to make a rom.. but i try to understand HOW the roms works (i have only understand that, the roms (Stock) is divided in
1 boot (need to be modded or exploited for change and load different recovery right??)
2 recovery
3 system
4 data/cache
If i not mess with boot and recovery (now i have the cwm on recovery) i can't brick my phone right? or i can always replace it with new kdz (windows + kdzupd)
I want the systemUI from 430 or other kind of file for have back the menu retroillumination...
Click to expand...
Click to collapse
open lg mobile support tool
select emergency upgrade
enter imei or serial
wait for it to download
wait for it to flash it
now you have e430 again
now if firmware is not v10c and you want to easily root download it and normal flash .kdz
now root and unlock bootloader and install cwm again
EDIT: also in my E430 thread there is links to all stock partitions like after extracting .dz
so... no way to mod the python script for dz e430 file?
Lets do it ?
Naxil said:
so... no way to mod the python script for dz e430 file?
Click to expand...
Click to collapse
i'm not capable of doing it
but i'm sure i can help you
read http://forum.xda-developers.com/showpost.php?p=52569369&postcount=48 that
use that program while flashing and inside the log that you will get there is a lot of info that you might find useful for extracting the .dz
also i can provide you with all info from e430 if any needed
Naxil said:
so... no way to mod the python script for dz e430 file?
Click to expand...
Click to collapse
bump ?
IGGYVIP said:
i'm not capable of doing it
but i'm sure i can help you
read http://forum.xda-developers.com/showpost.php?p=52569369&postcount=48 that
use that program while flashing and inside the log that you will get there is a lot of info that you might find useful for extracting the .dz
also i can provide you with all info from e430 if any needed
Click to expand...
Click to collapse
so the APPS file is the bootloader?
following your post
Code:
*---------------------------- PartitionTable Info [COLOR="red"]LG Optimus L3 II E430[/COLOR] --------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
APPS points to /dev/block/mmcblk0p9 and in the freeedom pack the boot.img points to the same file
ensarman said:
so the APPS file is the bootloader?
following your post
Code:
*---------------------------- PartitionTable Info [COLOR="red"]LG Optimus L3 II E430[/COLOR] --------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
APPS points to /dev/block/mmcblk0p9 and in the freeedom pack the boot.img points to the same file
Click to expand...
Click to collapse
/dev/block/mmcblk0p5 is bootloader in freedom pack its lock.bin
Hello, I've been reading the thread about BinExtractor and it seems to work with original TOT firmwares that now we can download using some nice methods (like going to a url and putting the IMEI or there's even an APP that does the same).
In my case I'm trying with 10B_00.tot for my E431g
Now, the latest binextractor seems to properly read the magic numbers from my tot file header but it's not able to extract the img files from it.
So I have already asked the developer to add my model to the supported devices but I would like to have more understanding of the TOT file headers so we could develop our own apps or even do things manually.
Does anyone have any information on how to better understand those headers it'd be really nice. So far I got to the part of "reading the first datablock" from the file but I don't really know what the app does with those (as follows):
Code:
/*SET FIRST DATABLOCK*/
dataBlock.blockOff = 0x2010;
dataBlock.blockSize = 12;
dataBlock.numItems = 4;
dataBlock.items = calloc(sizeof(Item), 4);
dataBlock.items[0].type = DISK_OFF;
dataBlock.items[0].size = 4;
dataBlock.items[1].type = FILE_OFF;
dataBlock.items[1].size = 4;
dataBlock.items[2].type = FILE_SIZE;
dataBlock.items[2].size = 4;
dataBlock.items[3].type = SKIP;
dataBlock.items[3].size = 4;
I have attached the mentioned datablock, the red-square is that 0x2010 offset start.
@xonar_ maybe you could give us some explanation of what those header parts mean and how can we know what to do depending on the differences. Here I'm trying to concentrate on L3 II header files.
Thanks to all in advance!
binExtractor github: https://github.com/Xonar/LGBinExtractor
method for manually getting the images from the firmware using dd: http://forum.xda-developers.com/showthread.php?t=2071465
get the original firmware using IMEI: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
root-check
Here's a little find I did searching for "ro.secure" inside the TOT
for me it looks like something related to the persist partition with a residing anti-root consistency check.. this is why it would be great to extract all the partitions from the firmware, we need a full check to make sure all this **** is gone before flashing anything to a phone.
cher
Code:
/rct<bh:00>/persist/rct.partition<bh:00>w<bh:00>/system/bin/su<bh:00>/system/xbin/su<bh:00>/system/sbin/su<bh:00>/sbin/su<bh:00>/data/local/tmp/su<bh:00>/system/app/Superuser.apk<bh:00>/system/app/SuperUser.apk<bh:00>/system/app/superuser.apk<bh:00>/data/data/com.noshufou.android.su<bh:00>/data/local/tmp/Superuser.apk<bh:00>/data/local/tmp/SuperUser.apk<bh:00>/data/local/tmp/superuser.apk<bh:00>/system/bin/busybox<bh:00>/system/xbin/busybox<bh:00>/data/local/tmp/busybox<bh:00>/system/<bh:00>/<bh:00>su<bh:00>getprop ro.secure<bh:00>r<bh:00>getprop ro.debuggable<bh:00>sys.rctd.uid<bh:00>1<bh:00>sys.uctd.on<bh:00>0<bh:00>rb<bh:00>wb<bh:00>Not Rooted
[LG RCT v%s]<bh:00>1.0.1224<bh:00>Rooted
<bh:00> LG RCT had been hacked by user.
<bh:00> > LG RCT Flag(backup)
<bh:00> > LG RCT Flag
<bh:00> Not allowed command had been executed.
<bh:00> > su
<bh:00> Permission related property had been changed.
<bh:00> > ro.secure
<bh:00> > ro.debuggable
<bh:00> Mount option had been changed.
<bh:00> > /system
<bh:00> > /
<bh:00> Rooting related file had been installed.
<bh:00> > superuser
<bh:00> > busybox
<bh:00>
[LG RCT v%s]<bh:00>/dev/block/platform/msm_sdcc.3/by-num/p26<bh:00>/persist<bh:00>/dev<bh:00>%s<bh:00>getprop ro.hardware<bh:00>/persist/rct<bh:00>/data/system/lgmdm_root_flag.txt<bh:00>/persist/rct.cfg<bh:00>/sdcard/RCT_security
gattytto said:
Hello, I've been reading the thread about BinExtractor and it seems to work with original TOT firmwares that now we can download using some nice methods (like going to a url and putting the IMEI or there's even an APP that does the same).
In my case I'm trying with 10B_00.tot for my E431g
Now, the latest binextractor seems to properly read the magic numbers from my tot file header but it's not able to extract the img files from it.
So I have already asked the developer to add my model to the supported devices but I would like to have more understanding of the TOT file headers so we could develop our own apps or even do things manually.
Does anyone have any information on how to better understand those headers it'd be really nice. So far I got to the part of "reading the first datablock" from the file but I don't really know what the app does with those (as follows):
Code:
/*SET FIRST DATABLOCK*/
dataBlock.blockOff = 0x2010;
dataBlock.blockSize = 12;
dataBlock.numItems = 4;
dataBlock.items = calloc(sizeof(Item), 4);
dataBlock.items[0].type = DISK_OFF;
dataBlock.items[0].size = 4;
dataBlock.items[1].type = FILE_OFF;
dataBlock.items[1].size = 4;
dataBlock.items[2].type = FILE_SIZE;
dataBlock.items[2].size = 4;
dataBlock.items[3].type = SKIP;
dataBlock.items[3].size = 4;
I have attached the mentioned datablock, the red-square is that 0x2010 offset start.
@xonar_ maybe you could give us some explanation of what those header parts mean and how can we know what to do depending on the differences. Here I'm trying to concentrate on L3 II header files.
Thanks to all in advance!
binExtractor github: https://github.com/Xonar/LGBinExtractor
method for manually getting the images from the firmware using dd: http://forum.xda-developers.com/showthread.php?t=2071465
get the original firmware using IMEI: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
Click to expand...
Click to collapse
9-APPS.img for my E431g:
init.vee3.rc: right at the end of the file, declared as a service
Code:
#Porting Rooting Check Tool
service rctd /system/bin/rctd
class late_start
user root
group root
full tree of 9-APPS.img
Code:
[email protected]:/media/sf_fw/img/tools/apps# tree ./
./
├── charger
├── cupssd.rc
├── data
├── default.prop
├── dev
├── fstab.vee3
├── init
├── init.goldfish.rc
├── init.lge.early.rc
├── init.lge.rc
├── init.lge.usb.sh
├── init.miniOS.rc
├── init.qcom.class_core.sh
├── init.qcom.class_main.sh
├── init.qcom.rc
├── init.qcom.ril.path.sh
├── init.qcom.sh
├── init.qcom.usb.rc
├── init.qcom.usb.sh
├── init.rc
├── init.target.rc
├── init.vee3.rc
├── init.vee3.usb.rc
├── lgdms.fota.rc
├── lgdms.fota_update.rc
├── proc
├── res
│** └── images
│** ├── charger
│** │** ├── battery_0.png
│** │** ├── battery_1.png
│** │** ├── battery_2.png
│** │** ├── battery_3.png
│** │** ├── battery_4.png
│** │** ├── battery_5.png
│** │** ├── battery_charge.png
│** │** └── battery_fail.png
│** ├── chargerimages
│** │** ├── battery_charging_01.png
│** │** ├── battery_charging_02.png
│** │** ├── battery_charging_03.png
│** │** ├── battery_charging_04.png
│** │** ├── battery_charging_05.png
│** │** ├── battery_charging_06.png
│** │** ├── battery_charging_07.png
│** │** ├── battery_charging_08.png
│** │** ├── battery_charging_bg.png
│** │** ├── battery_charging_complete.png
│** │** ├── battery_charging_warning_eng_1.png
│** │** ├── battery_charging_warning_eng_2.png
│** │** ├── battery_charging_warning_jp_1.png
│** │** ├── battery_charging_warning_jp_2.png
│** │** ├── battery_charging_warning_kor_1.png
│** │** ├── battery_charging_warning_kor_2.png
│** │** ├── battery_charging_warning.png
│** │** ├── battery_trickle_ani_01.png
│** │** ├── battery_trickle_ani_02.png
│** │** ├── battery_wait_ani_01.png
│** │** └── battery_wait_ani_02.png
│** └── errorlogo.png
├── sbin
│** ├── adbd
│** ├── brd
│** ├── chargerlogo
│** ├── clearlock
│** ├── cupssd
│** ├── lge_fota
│** ├── make_ext4fs
│** ├── setup_fs
│** ├── skd
│** └── wallpaper
├── skd.rc
├── sys
├── system
├── ueventd.goldfish.rc
├── ueventd.qcom.rc
├── ueventd.rc
└── ueventd.vee3.rc
gattytto said:
Here's a little find I did searching for "ro.secure" inside the TOT
for me it looks like something related to the persist partition with a residing anti-root consistency check.. this is why it would be great to extract all the partitions from the firmware, we need a full check to make sure all this **** is gone before flashing anything to a phone.
cher
Code:
/rct<bh:00>/persist/rct.partition<bh:00>w<bh:00>/system/bin/su<bh:00>/system/xbin/su<bh:00>/system/sbin/su<bh:00>/sbin/su<bh:00>/data/local/tmp/su<bh:00>/system/app/Superuser.apk<bh:00>/system/app/SuperUser.apk<bh:00>/system/app/superuser.apk<bh:00>/data/data/com.noshufou.android.su<bh:00>/data/local/tmp/Superuser.apk<bh:00>/data/local/tmp/SuperUser.apk<bh:00>/data/local/tmp/superuser.apk<bh:00>/system/bin/busybox<bh:00>/system/xbin/busybox<bh:00>/data/local/tmp/busybox<bh:00>/system/<bh:00>/<bh:00>su<bh:00>getprop ro.secure<bh:00>r<bh:00>getprop ro.debuggable<bh:00>sys.rctd.uid<bh:00>1<bh:00>sys.uctd.on<bh:00>0<bh:00>rb<bh:00>wb<bh:00>Not Rooted
[LG RCT v%s]<bh:00>1.0.1224<bh:00>Rooted
<bh:00> LG RCT had been hacked by user.
<bh:00> > LG RCT Flag(backup)
<bh:00> > LG RCT Flag
<bh:00> Not allowed command had been executed.
<bh:00> > su
<bh:00> Permission related property had been changed.
<bh:00> > ro.secure
<bh:00> > ro.debuggable
<bh:00> Mount option had been changed.
<bh:00> > /system
<bh:00> > /
<bh:00> Rooting related file had been installed.
<bh:00> > superuser
<bh:00> > busybox
<bh:00>
[LG RCT v%s]<bh:00>/dev/block/platform/msm_sdcc.3/by-num/p26<bh:00>/persist<bh:00>/dev<bh:00>%s<bh:00>getprop ro.hardware<bh:00>/persist/rct<bh:00>/data/system/lgmdm_root_flag.txt<bh:00>/persist/rct.cfg<bh:00>/sdcard/RCT_security
Click to expand...
Click to collapse
Hi there
gattytto said:
get the original firmware using IMEI: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
Click to expand...
Click to collapse
Thats a nice find
what are you trying to achieve by this doing this (extracting and making kdz files) ? we have cwm and unlocked bootloader we can do all using easy .zip's
anyway i think i have something that you might find useful (also check my thread for more (see sig))
Code:
*---------------------------- PartitionTable Info E430 V10C_00--------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
the attached file is output of sysinternals dbgview.exe while flashing stock v10c to phone e430
Hi, thanks a lot for your repply and the info, I'd like to answer to your question at the bottom of you post:
what I'm trying to do now is to examine all the .img files included inside the latest original .tot available for download from LG, mainly because since the last update it's impossible to root the e431g using vroot or any other 1-click rooting tool.
so far I've been able to unpack recovery and apps img (9-APPS.img and 17-RECOVERY.img) with their kernel and ramdisk.gz.
there are some things that I still don't understand, for example the existense of secundary recovery.img and oemsbl.img, so I have 17-RECOVERY.img, recovery.img, 3-OEMSBL.img and oemsbl.img
also I'm still trying to unpack some of the IMG files since they seem to be some special filesystem like yaffs2 but I haven't found any tool to browse them (didn't try converters 'cause that's not the approach I'm looking for). right now I'm compiling a 3.16-r2 kernel with the yaffs2 module that I tried modding to compile for that kernel (was hard job indeed).
my approach is to try modify the files present in my original downloaded TOT to root and unlock the bootloader to flash them back into my phone, thus trying to avoid bricking the phone.
you use skype or something?
here's a list of what I get:
Code:
10-MODEM_ST1.img: empty
11-MODEM_ST2.img: empty
12-MODEM.img: data
13-MODEM_BACKUP.img: data
14-SYSTEM.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
15-PERSIST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
16-CACHE.img: empty
17-RECOVERY.img: data
18-DRM.img: empty
19-FOTA.img: empty
20-USERDATA.img: empty
21-DLOAD.img: empty
22-BOOT_LOGO_IMAGE.img: data
23-MPT.img: empty
24-ENCRYPT.img: empty
25-CUST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
26-rct.img: empty
2-QCSBL.img: x86 boot sector; partition 1: ID=0x4d, active, starthead 0, startsector 1, 40 sectors; partition 2: ID=0x45, starthead 0, startsector 41, 2048 sectors; partition 3: ID=0x46, starthead 0, startsector 2089, 8192 sectors; partition 4: ID=0x5, starthead 0, startsector 10281, 7501784 sectors, code offset 0x0
3-OEMSBL.img: data
4-EXT.img: x86 boot sector; partition 1: ID=0x47, starthead 0, startsector 120791, 8192 sectors; partition 2: ID=0x5, starthead 0, startsector 1, 1 sectors, extended partition table, code offset 0x0
5-APPSSBL.img: Hitachi SH big-endian COFF object, not stripped
6-WALLPAPER.img: empty
7-MODEM_BACKUP.img: empty
8-misc.img: empty
9-APPS.img: data
oemsbl.img: data
recovery.img: data
also I've seen some info on mounting boot sector files like 4-EXT.img and 2-QCSBL.img but the file systems from those sectors don't seem to get recognized by the mount command.. so I'm guessing there's a filesystem module missing in my linux distro (that's why I'm compiling this other one).
IGGYVIP said:
Thats a nice find
what are you trying to achieve by this doing this (extracting and making kdz files) ? we have cwm and unlocked bootloader we can do all using easy .zip's
anyway i think i have something that you might find useful (also check my thread for more (see sig))
Code:
*---------------------------- PartitionTable Info E430 V10C_00--------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
the attached file is output of sysinternals dbgview.exe while flashing stock v10c to phone e430
Click to expand...
Click to collapse
I see
gattytto said:
Hi, thanks a lot for your repply and the info, I'd like to answer to your question at the bottom of you post:
what I'm trying to do now is to examine all the .img files included inside the latest original .tot available for download from LG, mainly because since the last update it's impossible to root the e431g using vroot or any other 1-click rooting tool.
so far I've been able to unpack recovery and apps img (9-APPS.img and 17-RECOVERY.img) with their kernel and ramdisk.gz.
there are some things that I still don't understand, for example the existense of secundary recovery.img and oemsbl.img, so I have 17-RECOVERY.img, recovery.img, 3-OEMSBL.img and oemsbl.img
also I'm still trying to unpack some of the IMG files since they seem to be some special filesystem like yaffs2 but I haven't found any tool to browse them (didn't try converters 'cause that's not the approach I'm looking for). right now I'm compiling a 3.16-r2 kernel with the yaffs2 module that I tried modding to compile for that kernel (was hard job indeed).
my approach is to try modify the files present in my original downloaded TOT to root and unlock the bootloader to flash them back into my phone, thus trying to avoid bricking the phone.
you use skype or something?
here's a list of what I get:
Code:
10-MODEM_ST1.img: empty
11-MODEM_ST2.img: empty
12-MODEM.img: data
13-MODEM_BACKUP.img: data
14-SYSTEM.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
15-PERSIST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
16-CACHE.img: empty
17-RECOVERY.img: data
18-DRM.img: empty
19-FOTA.img: empty
20-USERDATA.img: empty
21-DLOAD.img: empty
22-BOOT_LOGO_IMAGE.img: data
23-MPT.img: empty
24-ENCRYPT.img: empty
25-CUST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
26-rct.img: empty
2-QCSBL.img: x86 boot sector; partition 1: ID=0x4d, active, starthead 0, startsector 1, 40 sectors; partition 2: ID=0x45, starthead 0, startsector 41, 2048 sectors; partition 3: ID=0x46, starthead 0, startsector 2089, 8192 sectors; partition 4: ID=0x5, starthead 0, startsector 10281, 7501784 sectors, code offset 0x0
3-OEMSBL.img: data
4-EXT.img: x86 boot sector; partition 1: ID=0x47, starthead 0, startsector 120791, 8192 sectors; partition 2: ID=0x5, starthead 0, startsector 1, 1 sectors, extended partition table, code offset 0x0
5-APPSSBL.img: Hitachi SH big-endian COFF object, not stripped
6-WALLPAPER.img: empty
7-MODEM_BACKUP.img: empty
8-misc.img: empty
9-APPS.img: data
oemsbl.img: data
recovery.img: data
also I've seen some info on mounting boot sector files like 4-EXT.img and 2-QCSBL.img but the file systems from those sectors don't seem to get recognized by the mount command.. so I'm guessing there's a filesystem module missing in my linux distro (that's why I'm compiling this other one).
Click to expand...
Click to collapse
i have tried unpacking .dz before but i was never successful as all of tools are outdated
only way i found to extract the .kdz is flashing it to phone and adb dd and pull from device but for that you need root (did you check the latest vroot ?
anyway i have made tool to dump and name all(skipping the sdcard) partitions from phone(L3 II) found HERE
also i made a tool to list ALL of files in phone in easy to read directory format found HERE*this also includes my filelist.txt for compare in case you want and does not require root
also here is my boot.img unpacked BOOT BROKENDOWN
i think you did not get a chance to read the attached file yet but inside you find that lg flashing software does :
Code:
Skip writing [MODEM_ST1;MODEM_ST2;DRM;MPT;CACHE;USERDATA;MODEM_BACKUP;PERSIST;BOOT_LOGO_IMAGE;] partition
Code:
Size of the [WALLPAPER] partition is zero \tab\par
00000463\tab 717.36279297\tab [4244] [13:16:39] Size of the [MODEM_BACKUP] partition is zero \tab\par
00000464\tab 717.36285400\tab [4244] [13:16:39] Size of the [misc] partition is zero \tab\par
00000465\tab 717.36291504\tab [4244] [13:16:39] Size of the [MODEM_ST1] partition is zero \tab\par
00000466\tab 717.36297607\tab [4244] [13:16:39] Size of the [MODEM_ST2] partition is zero \tab\par
00000467\tab 717.36303711\tab [4244] [13:16:39] Skip writing [MODEM_BACKUP] partition \tab\par
00000468\tab 717.36309814\tab [4244] [13:16:39] Skip writing [PERSIST] partition \tab\par
00000469\tab 717.36315918\tab [4244] [13:16:39] Size of the [CACHE] partition is zero \tab\par
00000470\tab 717.36322021\tab [4244] [13:16:39] Size of the [DRM] partition is zero \tab\par
00000471\tab 717.36328125\tab [4244] [13:16:39] Size of the [FOTA] partition is zero \tab\par
00000472\tab 717.36328125\tab [4244] [13:16:39] Size of the [USERDATA] partition is zero \tab\par
00000473\tab 717.36334229\tab [4244] [13:16:39] Size of the [DLOAD] partition is zero \tab\par
00000474\tab 717.36340332\tab [4244] [13:16:39] Skip writing [BOOT_LOGO_IMAGE] partition \tab\par
00000475\tab 717.36346436\tab [4244] [13:16:39] Size of the [MPT] partition is zero \tab\par
00000476\tab 717.36352539\tab [4244] [13:16:39] Size of the [ENCRYPT] partition is zero \tab\par
00000477\tab 717.36370850\tab [4244] [13:16:39] Size of the [rct] partition is zero \tab\par
it means none of these are inside the .kdz
about kdz could you send me direct link to firmware you are trying to root ?
e430 europe latest is v10c and its easly rootable using vroot so i will try to flash yours and see if i can get success
Hello, before you read my repply, I know you can get some tots (or kdz) from other places, but I will really appreciate you get me a link for the offical KDZ link generation url http://csmg.lgmobile.com:9002/...(and so on). Since I can extract the kdz to .cab, I want to know if yours is actually packed with different headers and if so that will give more info 'bout what tools need to get updated.
I will first answer to your request for the .kdz file I'm working on: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW238195432109876543213/V10B_00.kdz
as for the .kdz file extractor, I have been testing several ones until I got to this one (attached).
run it from a command prompt, can you give me the url produced for yor IMEI from the link I have provided in first post? It would let me accelerate testing for your particular case.
After you use that extractor with -kdz argument, you will get a .cab, open with winrar, you should get a .tot and a .dll file
if you get to extract your own kdz and obtain the .tot proceed as follows:
use LGBinExtractor to unpack the .tot from https://github.com/Xonar/LGBinExtractor, I provide a .exe with code updates to support e431g tot magic and headers..
use the -daph argument with your .tot and you should get output about partitions inside the firmware with this format:
Code:
AP HEADER
----------
Magic Number 0x0 : 44 DD 55 AA
0x8 : 97 4A EB 9F
0xC : 4C 47 45 34
0x10 : 33 31 67 00
0x14 : 00 00 00 00
0x18 : 00 00 00 00
0x1C : 00 00 00 00
0x600 : AA BB 00 CC
0x2000 : 33 EC 55 AA
Number of Partitions 25
PARTITION ENTRIES
-----------------
PARTITION ENTRY
------------
Data Block Name QCSBL
Data Block ID 2
Size on File 1024
File Offset 0
Size on Disk 2089
Disk Offset 0
PARTITION ENTRY
------------
Data Block Name OEMSBL
Data Block ID 3
Size on File 2048
File Offset 1024
Size on Disk 8192
Disk Offset 2089
If you get any error from the command "LGBinExtractor -daph file.tot" instead of the partitions list then you need to use the "LGBinExtractor -ebh file.tot" command to extract a copy of its header and attach it to the LGBinExtractor thread so the author will get the magic headers added to the app in https://github.com/Xonar/LGBinExtractor . If this is the case and you get a .tot from the KDZ but not IMG files from the TOT with LGBinExtractor, besides posting the headers to the author's thread, also upload here your header.bin with the link to your official .kdz so I can make some testing.
Note: in case you get the .tot but it's not supported by lgbinextractor, you can also setup a linux box (win 2012 hyper-v / virtualbox / etc..) and try to make the needed changes, then use that windows makefile I have attached and it will produce a .exe with your changes (or author's added changes in case he didn't share the .exe with the most recent changes you or someone else requested for their devices). You can use the default makefile and test inside the linux box with header.bin file until you get the partitions list, then you can produce the .exe and try unpack the whole .tot in your windows box.
If you can't get the .tot from your official kdz then we need to get the source for the LGExtract (kdz extractor) and make the needed changes in order to support your version.
cheers
http://ul.to/myyrb8ie <- the extractors and the makefile
IGGYVIP said:
i have tried unpacking .dz before but i was never successful as all of tools are outdated
only way i found to extract the .kdz is flashing it to phone and adb dd and pull from device but for that you need root (did you check the latest vroot ?
anyway i have made tool to dump and name all(skipping the sdcard) partitions from phone(L3 II) found HERE
also i made a tool to list ALL of files in phone in easy to read directory format found HERE*this also includes my filelist.txt for compare in case you want and does not require root
also here is my boot.img unpacked BOOT BROKENDOWN
i think you did not get a chance to read the attached file yet but inside you find that lg flashing software does :
Code:
Skip writing [MODEM_ST1;MODEM_ST2;DRM;MPT;CACHE;USERDATA;MODEM_BACKUP;PERSIST;BOOT_LOGO_IMAGE;] partition
Code:
Size of the [WALLPAPER] partition is zero \tab\par
00000463\tab 717.36279297\tab [4244] [13:16:39] Size of the [MODEM_BACKUP] partition is zero \tab\par
00000464\tab 717.36285400\tab [4244] [13:16:39] Size of the [misc] partition is zero \tab\par
00000465\tab 717.36291504\tab [4244] [13:16:39] Size of the [MODEM_ST1] partition is zero \tab\par
00000466\tab 717.36297607\tab [4244] [13:16:39] Size of the [MODEM_ST2] partition is zero \tab\par
00000467\tab 717.36303711\tab [4244] [13:16:39] Skip writing [MODEM_BACKUP] partition \tab\par
00000468\tab 717.36309814\tab [4244] [13:16:39] Skip writing [PERSIST] partition \tab\par
00000469\tab 717.36315918\tab [4244] [13:16:39] Size of the [CACHE] partition is zero \tab\par
00000470\tab 717.36322021\tab [4244] [13:16:39] Size of the [DRM] partition is zero \tab\par
00000471\tab 717.36328125\tab [4244] [13:16:39] Size of the [FOTA] partition is zero \tab\par
00000472\tab 717.36328125\tab [4244] [13:16:39] Size of the [USERDATA] partition is zero \tab\par
00000473\tab 717.36334229\tab [4244] [13:16:39] Size of the [DLOAD] partition is zero \tab\par
00000474\tab 717.36340332\tab [4244] [13:16:39] Skip writing [BOOT_LOGO_IMAGE] partition \tab\par
00000475\tab 717.36346436\tab [4244] [13:16:39] Size of the [MPT] partition is zero \tab\par
00000476\tab 717.36352539\tab [4244] [13:16:39] Size of the [ENCRYPT] partition is zero \tab\par
00000477\tab 717.36370850\tab [4244] [13:16:39] Size of the [rct] partition is zero \tab\par
it means none of these are inside the .kdz
about kdz could you send me direct link to firmware you are trying to root ?
e430 europe latest is v10c and its easly rootable using vroot so i will try to flash yours and see if i can get success
Click to expand...
Click to collapse
gattytto said:
Hello, before you read my repply, I know you can get some tots (or kdz) from other places, but I will really appreciate you get me a link for the offical KDZ link generation url http://csmg.lgmobile.com:9002/...(and so on). Since I can extract the kdz to .cab, I want to know if yours is actually packed with different headers and if so that will give more info 'bout what tools need to get updated.
I will first answer to your request for the .kdz file I'm working on: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW238195432109876543213/V10B_00.kdz
as for the .kdz file extractor, I have been testing several ones until I got to this one (attached).
run it from a command prompt, can you give me the url produced for yor IMEI from the link I have provided in first post? It would let me accelerate testing for your particular case.
After you use that extractor with -kdz argument, you will get a .cab, open with winrar, you should get a .tot and a .dll file
if you get to extract your own kdz and obtain the .tot proceed as follows:
use LGBinExtractor to unpack the .tot from https://github.com/Xonar/LGBinExtractor, I provide a .exe with code updates to support e431g tot magic and headers..
use the -daph argument with your .tot and you should get output about partitions inside the firmware with this format:
Code:
AP HEADER
----------
Magic Number 0x0 : 44 DD 55 AA
0x8 : 97 4A EB 9F
0xC : 4C 47 45 34
0x10 : 33 31 67 00
0x14 : 00 00 00 00
0x18 : 00 00 00 00
0x1C : 00 00 00 00
0x600 : AA BB 00 CC
0x2000 : 33 EC 55 AA
Number of Partitions 25
PARTITION ENTRIES
-----------------
PARTITION ENTRY
------------
Data Block Name QCSBL
Data Block ID 2
Size on File 1024
File Offset 0
Size on Disk 2089
Disk Offset 0
PARTITION ENTRY
------------
Data Block Name OEMSBL
Data Block ID 3
Size on File 2048
File Offset 1024
Size on Disk 8192
Disk Offset 2089
If you get any error from the command "LGBinExtractor -daph file.tot" instead of the partitions list then you need to use the "LGBinExtractor -ebh file.tot" command to extract a copy of its header and attach it to the LGBinExtractor thread so the author will get the magic headers added to the app in https://github.com/Xonar/LGBinExtractor . If this is the case and you get a .tot from the KDZ but not IMG files from the TOT with LGBinExtractor, besides posting the headers to the author's thread, also upload here your header.bin with the link to your official .kdz so I can make some testing.
Note: in case you get the .tot but it's not supported by lgbinextractor, you can also setup a linux box (win 2012 hyper-v / virtualbox / etc..) and try to make the needed changes, then use that windows makefile I have attached and it will produce a .exe with your changes (or author's added changes in case he didn't share the .exe with the most recent changes you or someone else requested for their devices). You can use the default makefile and test inside the linux box with header.bin file until you get the partitions list, then you can produce the .exe and try unpack the whole .tot in your windows box.
If you can't get the .tot from your official kdz then we need to get the source for the LGExtract (kdz extractor) and make the needed changes in order to support your version.
cheers
http://ul.to/myyrb8ie <- the extractors and the makefile
Click to expand...
Click to collapse
quick post
MY CURRENT FIRMWARE
*updating
Code:
F:\>mas -extract E430_TSC_UK.tot
Reading AP Header...
Reading GPT Header...
Does not contain GPT at first data block
Writing Files...
Writing File : 2-QCSBL.img -- DONE --
Writing File : 3-OEMSBL.img -- DONE --
Writing File : 4-EXT.img -- DONE --
Writing File : 5-APPSSBL.img -- DONE --
Writing File : 6-WALLPAPER.img -- DONE --
Writing File : 7-MODEM_BACKUP.img -- DONE --
Writing File : 8-misc.img -- DONE --
Writing File : 9-APPS.img -- DONE --
Writing File : 10-MODEM_ST1.img -- DONE --
Writing File : 11-MODEM_ST2.img -- DONE --
Writing File : 12-MODEM.img -- DONE --
Writing File : 13-MODEM_BACKUP.img -- DONE --
Writing File : 14-SYSTEM.img -- DONE --
Writing File : 15-PERSIST.img -- DONE --
Writing File : 16-CACHE.img -- DONE --
Writing File : 17-RECOVERY.img -- DONE --
Writing File : 18-DRM.img -- DONE --
Writing File : 19-FOTA.img -- DONE --
Writing File : 20-USERDATA.img -- DONE --
Writing File : 21-DLOAD.img -- DONE --
Writing File : 22-BOOT_LOGO_IMAGE.img -- DONE --
Writing File : 23-MPT.img -- DONE --
Writing File : 24-ENCRYPT.img -- DONE --
Writing File : 25-CUST.img -- DONE --
Writing File : 26-rct.img -- DONE --
Finished
IGGYVIP said:
quick post
MY CURRENT FIRMWARE
*updating
Click to expand...
Click to collapse
Almost done, but don't want to use KDZ, but LG FlashTool instead, but it's complaining about the CRC check.. anyone with some debugging skills to help us ollydbg patch the dll/exe to bypass the crc check? or maybe someone knows how this check is being performed?
thanks in advance
also this is killing me inside:
Code:
5-APPSSBL.img: Hitachi SH big-endian COFF object, not stripped
what does this mean? Hitachi SH is SH2 or SH3 or SH4 which is a chip, and this phone has ARM MSM7225A, why does this file get recognized as a SH3/4 instruction set? pleeeeeeeeeeeeeease! someone clarify this for me!!
Hello
I am looking for a solution to reach the serial interface of a 3D printer in a debian chroot linux deploy.
My devices is Samsung A3 2015, rom: resurrection remix 7.1
During my tests, I can communicate with the printer (I sent gcode commands correctly) with a simple serial port application on the playstore.
I deployed the octoprint server in Debian Arm of Linux Deploy. In the octoprint configuration an automatic search of the periphery (usually /dev/ttyUSB) does not work; no port found.
In addition, when I navigate with a terminal in the android system, there is no /dev/ttyUSB file.
But where does Android map the periphery?
Here is the result of the dmesg when connecting the printer:
Code:
[85207.609290] usb 1-1: full-speed USB device number 10 using msm_hsusb_host
[85207.737337] usb 1-1: New USB device found, idVendor = 1a86, idProduct = 7523
[85207.737475] usb 1-1: New USB device strings: Mfr = 0, Product = 2, SerialNumber = 0
[85207.737514] usb 1-1: Product: USB2.0-Serial
An lsusb, gives me my printer:
Code:
Bus 001 Device 014: ID 1a86: 7523 QinHeng Electronics HL-340 USB-Serial Adapter
Code:
root @ localhost: ~ # usb-devices
T: Bus = 01 Lev = 01 Prnt = 01 Port = 00 Cnt = 01 Dev # = 9 Spd = 12 MxCh = 0
D: Ver = 1.10 Cls = ff (sell) Sub = 00 Prot = 00 MxPS = 8 # Cfgs = 1
P: Vendor = 1a86 ProdID = 7523 Rev = 02.63
S: Product = USB2.0-Serial
C: # Ifs = 1 Cfg # = 1 Atr = 80 MxPwr = 98mA
I: If # = 0 Alt = 0 # EPs = 3 Cls = ff (sells) Sub = 01 Prot = 02 Driver = (none)
With debian/arch etc, /dev is well mounted.
By the way there is no /dev/ttyUSB in the android system (simple terminal) when I plug the printer.
But where does it map the serial port finally!
I aim on getting problem ..
Hi, I know that this is an old thread, but I ran in the exact same issue.
Did you ever solve this please?
This is what I get:
Code:
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=1a86 ProdID=7523 Rev=02.64
S: Product=USB Serial
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=98mA
I: If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=02 Driver=(none)
It seems that no driver gets loaded
New phone bought from uae
After May update keeps restarting random times.teied reinstalling firm with odin,rlfactory reset,changing csc also reboots in safemode too.
I will post my last reset reason from log
Could any one find the reason thank you pls..
23/06/21 18:48:06
reason : userrequested,mainline_update
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.reboot(ShutdownThread.java:444)
at com.android.server.power.PowerManagerService$2.run(PowerManagerService.java:6070)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
at com.android.server.UiThread.run(UiThread.java:52)
18:48:12 2023-06-21 18:48:12+0530 | REBOOT | | REASON: userrequested,mainline_update
18:48:12 terminating init service start
18:48:15 terminating init service end
18:48:15 volume shutdown start
18:48:16 volume shutdown end
2023-06-21 18:49:16+0530 | ON | RP | S918BXXU2AWF1 / apex_updated
23/06/21 18:51:47
reason : userrequested,mainline_update
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.reboot(ShutdownThread.java:444)
at com.android.server.power.PowerManagerService$2.run(PowerManagerService.java:6070)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
at com.android.server.UiThread.run(UiThread.java:52)
18:51:49 2023-06-21 18:51:49+0530 | REBOOT | | REASON: userrequested,mainline_update
18:51:49 terminating init service start
18:51:52 terminating init service end
18:51:52 volume shutdown start
18:51:52 volume shutdown end
2023-06-21 18:52:48+0530 | ON | RP | S918BXXU2AWF1 / apex_updated
23/06/21 18:58:50
reason : userrequested,mainline_update
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.reboot(ShutdownThread.java:444)
at com.android.server.power.PowerManagerService$2.run(PowerManagerService.java:6070)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.os.HandlerThread.run(HandlerThread.java:67)
at com.android.server.ServiceThread.run(ServiceThread.java:44)
at com.android.server.UiThread.run(UiThread.java:52)
18:58:52 2023-06-21 18:58:52+0530 | REBOOT | | REASON: userrequested,mainline_update
18:58:52 terminating init service start
18:58:55 terminating init service end
18:58:55 volume shutdown start
18:58:56 volume shutdown end
2023-06-21 19:00:01+0530 | ON | RP | S918BXXU2AWF1 / apex_updated
21:05:45 2023-06-21 21:05:45+0530 | REBOOT | | REASON: system
21:05:45 terminating init service start
21:05:48 terminating init service end
21:05:48 volume shutdown start
21:05:48 volume shutdown end
2023-06-21 21:06:22+0530 | ON | RP | S918BXXU2AWF1
2023-06-21 23:30:39+0530 | ON | MP | S918BXXU2AWF1 /
2023-06-22 07:55:25+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"294", TZ_RR:check rpm or kernel(magic_val : 0xfefef
2023-06-22 10:36:57+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"295", TZ_RR:check rpm or kernel(magic_val : 0xfedec
2023-06-22 11:09:27+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"296", TZ_RR:TZBSP_ERR_FATAL_NON_SECURE_WDT
2023-06-22 11:41:56+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"297", TZ_RR:check rpm or kernel(magic_val : 0xfeffd
23/06/22 11:44:15
reason : userrequested
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.shutdown(ShutdownThread.java:240)
at com.android.server.statusbar.StatusBarManagerService.lambda$shutdown$4(StatusBarManagerService.java:2210)
at com.android.server.statusbar.StatusBarManagerService.$r8$lambda$2ndFA8HNezCsgX2sySFgr4QHJWQ(Unknown Source:0)
at com.android.server.statusbar.StatusBarManagerService$$ExternalSyntheticLambda8.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at com.android.server.SystemServer.run(SystemServer.java:1346)
at com.android.server.SystemServer.main(SystemServer.java:989)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
11:44:18 2023-06-22 11:44:18+0530 | SHUTDOWN | | REASON: userrequested
11:44:18 terminating init service start
11:44:22 terminating init service end
11:44:22 volume shutdown start
11:44:22 volume shutdown end
2023-06-22 11:44:36+0530 | | NP | / / 3924000(58%)
2023-06-22 11:44:36+0530 | LPM |
2023-06-22 12:15:24+0530 | ON | RP | S918BXXU2AWF1
2023-06-22 15:10:19+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"298", TZ_RR:check rpm or kernel(magic_val : 0xf6fea
2023-06-22 17:31:21+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"299", TZ_RR:check rpm or kernel(magic_val : 0xfeffc
2023-06-22 18:24:35+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"300", TZ_RR:check rpm or kernel(magic_val : 0xf6def
2023-06-22 18:33:33+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"301", TZ_RR:check rpm or kernel(magic_val : 0xf7dee
2023-06-22 20:33:00+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"302", TZ_RR:check rpm or kernel(magic_val : 0xfffec
2023-06-22 20:36:30+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"303", TZ_RR:check rpm or kernel(magic_val : 0xf6def
2023-06-22 22:07:29+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"304", TZ_RR:TZBSP_ERR_FATAL_NON_SECURE_WDT
2023-06-23 06:51:13+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"308", TZ_RR:TZBSP_ERR_FATAL_NON_SECURE_WDT
2023-06-23 07:20:33+0530 | ON | KP | S918BXXU2AWF1 / "RWC":"309", PANIC:Oops - BUG PC:rpmh_rsc_debug+0x334/0x338 [qcom_rpmh] LR:rpmh_rsc_debug+0x228/0x338 [qcom_rpmh] / apex_updated
2023-06-23 12:40:32+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"310", TZ_RR:TZBSP_ERR_FATAL_NON_SECURE_WDT
23/06/23 13:00:09
reason : userrequested
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.shutdown(ShutdownThread.java:240)
at com.android.server.statusbar.StatusBarManagerService.lambda$shutdown$4(StatusBarManagerService.java:2210)
at com.android.server.statusbar.StatusBarManagerService.$r8$lambda$2ndFA8HNezCsgX2sySFgr4QHJWQ(Unknown Source:0)
at com.android.server.statusbar.StatusBarManagerService$$ExternalSyntheticLambda8.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at com.android.server.SystemServer.run(SystemServer.java:1346)
at com.android.server.SystemServer.main(SystemServer.java:989)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
13:00:11 2023-06-23 13:00:11+0530 | SHUTDOWN | | REASON: userrequested
13:00:11 terminating init service start
13:00:15 terminating init service end
13:00:15 volume shutdown start
13:00:15 volume shutdown end
2023-06-23 13:31:43+0530 | ON | NP | S918BXXU2AWF1
23/06/23 15:34:35
reason : userrequested
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.shutdown(ShutdownThread.java:240)
at com.android.server.statusbar.StatusBarManagerService.lambda$shutdown$4(StatusBarManagerService.java:2210)
at com.android.server.statusbar.StatusBarManagerService.$r8$lambda$2ndFA8HNezCsgX2sySFgr4QHJWQ(Unknown Source:0)
at com.android.server.statusbar.StatusBarManagerService$$ExternalSyntheticLambda8.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at com.android.server.SystemServer.run(SystemServer.java:1346)
at com.android.server.SystemServer.main(SystemServer.java:989)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
15:34:38 2023-06-23 15:34:38+0530 | SHUTDOWN | | REASON: userrequested
15:34:38 terminating init service start
15:34:41 terminating init service end
15:34:41 volume shutdown start
15:34:41 volume shutdown end
23/06/23 15:35:14
reason : userrequested
java.lang.Exception: It is not an exception!! just save the trace for process which called shutdown thread!! ShutdownThread.shutdown
at com.android.server.power.ShutdownThread.shutdownInner(ShutdownThread.java:344)
at com.android.server.power.ShutdownThread.shutdown(ShutdownThread.java:240)
at com.android.server.statusbar.StatusBarManagerService.lambda$shutdown$4(StatusBarManagerService.java:2210)
at com.android.server.statusbar.StatusBarManagerService.$r8$lambda$2ndFA8HNezCsgX2sySFgr4QHJWQ(Unknown Source:0)
at com.android.server.statusbar.StatusBarManagerService$$ExternalSyntheticLambda8.run(Unknown Source:2)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at com.android.server.SystemServer.run(SystemServer.java:1346)
at com.android.server.SystemServer.main(SystemServer.java:989)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
2023-06-23 15:35:14+0530 | ON | NP | S918BXXU2AWF1
15:35:17 2023-06-23 15:35:17+0530 | SHUTDOWN | | REASON: userrequested
15:35:17 terminating init service start
15:35:20 terminating init service end
15:35:20 volume shutdown start
15:35:20 volume shutdown end
2023-06-23 15:38:11+0530 | ON | NP | S918BXXU2AWF1
2023-06-23 19:16:09+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"311", TZ_RR:check rpm or kernel(magic_val : 0xfffec
2023-06-23 19:54:18+0530 | ON | MP | S918BXXU2AWF1 /
2023-06-23 21:55:11+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"313", TZ_RR:check rpm or kernel(magic_val : 0xfffec
22:18:24 2023-06-23 22:18:24+0530 | REBOOT | | REASON: download
22:18:24 terminating init service start
22:18:27 terminating init service end
22:18:27 volume shutdown start
22:18:28 volume shutdown end
2023-06-23 22:31:28+0530 | ON | RP | S918BXXU2AWF1
22:32:17 2023-06-23 22:32:17+0530 | REBOOT | | REASON: recovery
22:32:17 terminating init service start
22:32:20 terminating init service end
22:32:20 volume shutdown start
22:32:20 volume shutdown end
2023-06-23 22:34:45+0530 | ON | RP | S918BXXU2AWF1
2023-06-24 00:06:58+0530 | ON | WP | S918BXXU2AWF1 / "RWC":"314", TZ_RR:TZBSP_ERR_FATAL_NON_SECURE_WDT