Hello guys,
Can you please post a ls -al /dev/block/
and if you can provide a .tar.gz of the entire thing.
Thanks!
how do I do this on droid explorer, I tried opening the folder with usb debug on, but it won't open.
Hello,
You need root.
Code:
adb shell
su
cd /dev/block/
ls -al
I already did this somewhere around the forum, likely in one of the lagfix threads...
max_warheads said:
I already did this somewhere around the forum, likely in one of the lagfix threads...
Click to expand...
Click to collapse
I did a quick search. Please post here.
Thanks!
Code:
bash-4.1# ls -al /dev/block
total 0
drwxr-xr-x 3 0 0 1360 Aug 21 06:48 .
drwxr-xr-x 10 0 0 13580 Aug 21 06:48 ..
brw------- 1 0 0 137, 0 Aug 21 06:48 bml0!c
brw------- 1 0 0 137, 1 Aug 21 06:48 bml1
brw------- 1 0 0 137, 10 Aug 21 06:48 bml10
brw------- 1 0 0 137, 11 Aug 21 06:48 bml11
brw-r--r-- 1 0 0 137, 12 Aug 21 06:48 bml12
brw------- 1 0 0 137, 2 Aug 21 06:48 bml2
brw------- 1 0 0 137, 3 Aug 21 06:48 bml3
brw------- 1 0 0 137, 4 Aug 21 06:48 bml4
brw------- 1 0 0 137, 5 Aug 21 06:48 bml5
brw------- 1 0 0 137, 6 Aug 21 06:48 bml6
brw------- 1 0 0 137, 7 Aug 21 06:48 bml7
brw------- 1 0 0 137, 8 Aug 21 06:48 bml8
brw------- 1 0 0 137, 9 Aug 21 06:48 bml9
brw------- 1 0 0 7, 0 Aug 21 06:48 loop0
brw------- 1 0 0 7, 1 Aug 21 06:48 loop1
brw------- 1 0 0 7, 2 Aug 21 06:48 loop2
brw------- 1 0 0 7, 3 Aug 21 06:48 loop3
brw------- 1 0 0 7, 4 Aug 21 06:48 loop4
brw------- 1 0 0 7, 5 Aug 21 06:48 loop5
brw------- 1 0 0 7, 6 Aug 21 06:48 loop6
brw------- 1 0 0 7, 7 Aug 21 06:48 loop7
brw------- 1 0 0 179, 0 Aug 21 06:48 mmcblk0
brw------- 1 0 0 179, 1 Aug 21 06:48 mmcblk0p1
brw------- 1 0 0 179, 2 Aug 21 06:48 mmcblk0p2
brw------- 1 0 0 1, 0 Aug 21 06:48 ram0
brw------- 1 0 0 1, 1 Aug 21 06:48 ram1
brw------- 1 0 0 1, 10 Aug 21 06:48 ram10
brw------- 1 0 0 1, 11 Aug 21 06:48 ram11
brw------- 1 0 0 1, 12 Aug 21 06:48 ram12
brw------- 1 0 0 1, 13 Aug 21 06:48 ram13
brw------- 1 0 0 1, 14 Aug 21 06:48 ram14
brw------- 1 0 0 1, 15 Aug 21 06:48 ram15
brw------- 1 0 0 1, 2 Aug 21 06:48 ram2
brw------- 1 0 0 1, 3 Aug 21 06:48 ram3
brw------- 1 0 0 1, 4 Aug 21 06:48 ram4
brw------- 1 0 0 1, 5 Aug 21 06:48 ram5
brw------- 1 0 0 1, 6 Aug 21 06:48 ram6
brw------- 1 0 0 1, 7 Aug 21 06:48 ram7
brw------- 1 0 0 1, 8 Aug 21 06:48 ram8
brw------- 1 0 0 1, 9 Aug 21 06:48 ram9
brw------- 1 0 0 138, 1 Aug 21 06:48 stl1
brw------- 1 0 0 138, 10 Aug 21 06:48 stl10
brw------- 1 0 0 138, 11 Aug 21 06:48 stl11
brw------- 1 0 0 138, 12 Aug 21 06:48 stl12
brw------- 1 0 0 138, 2 Aug 21 06:48 stl2
brw------- 1 0 0 138, 3 Aug 21 06:48 stl3
brw------- 1 0 0 138, 4 Aug 21 06:48 stl4
brw------- 1 0 0 138, 5 Aug 21 06:48 stl5
brw------- 1 0 0 138, 6 Aug 21 06:48 stl6
brw------- 1 0 0 138, 7 Aug 21 06:48 stl7
brw------- 1 0 0 138, 8 Aug 21 06:48 stl8
brw------- 1 0 0 138, 9 Aug 21 06:48 stl9
brw------- 1 0 0 139, 0 Aug 21 06:48 tfsr0!c
brw------- 1 0 0 139, 1 Aug 21 06:48 tfsr1
brw------- 1 0 0 139, 10 Aug 21 06:48 tfsr10
brw------- 1 0 0 139, 11 Aug 21 06:48 tfsr11
brw------- 1 0 0 139, 12 Aug 21 06:48 tfsr12
brw------- 1 0 0 139, 2 Aug 21 06:48 tfsr2
brw------- 1 0 0 139, 3 Aug 21 06:48 tfsr3
brw------- 1 0 0 139, 4 Aug 21 06:48 tfsr4
brw------- 1 0 0 139, 5 Aug 21 06:48 tfsr5
brw------- 1 0 0 139, 6 Aug 21 06:48 tfsr6
brw------- 1 0 0 139, 7 Aug 21 06:48 tfsr7
brw------- 1 0 0 139, 8 Aug 21 06:48 tfsr8
brw------- 1 0 0 139, 9 Aug 21 06:48 tfsr9
drwxr-xr-x 2 0 0 100 Aug 21 06:48 vold
bash-4.1#
Actually, sorry, that was for the JH2 ROM.
So far this fix has worked on several Note 3 models: SM-N900V, sprint SM-N900P SM-N900R4, N9005, N900T, and Claro Puerto Rico SM-N900W8
I lost my IMEI after sending command "reboot nvbackup" Phone rebooted into bootloops, was stuck for over 6 weeks. I was able to get everything working again after restoring "FSG", and "backup" mounts from a good SM-N900V DE phone. FSG is not an EFS copy in our Note 3's. Samsung left in a command that will brick these phones. Samsung is negligent by leaving this kill command in Note 3's.
The command "reboot nvbackup" will brick Note 3's, (and S5's). Mine is a verizon model SM-N900V Developer Device. I studied block partitions, and searched for weeks. I started looking at "FSG" and "backup" partitions since "reboot nvbackup" writes partitions modemst1 and modemst2 to Backup and FSG. In other phones this makes a backup copy. "reboot nvrestore" would restore bad modemst's mounts. In Note 3's FSG partition is a system partition. Reboot nvbackup overwrote FSG. My blocks were obviously corrupted.
A friend of mine with a DE and sent me his "FSG" and "backup" partitions, so I could compare backup-mmblk0p17 and FSG-mmblk0p18. FSG is not a "golden copy of efs in Note3', and "Backup" partition should be completely empty.
My FSG was corrupted with efs backup "IMGEFS1". The "backup" partition was filled with IMGEFS2. "reboot nvbackup" caused the toxic condition.
I simply copied and pasted both clean mounts into my /dev/block/ replacing the corrupt ones. I didn't even have to reboot, the MEID, PRL, and MIN all instantly showed up in the status screen after pasting FSG. The note 3 is Back 100%.
This is a specific problem to note 3's caused by performing "reboot nvbackup" on newer Samsung phones that use FSG in the operating system. this partition is very interesting. For those of us that entered this command, or ran efs backup software that called up this command, and then there phone immediately rebooted into endless boot loops. This procedure might work to get your IMEI / MEID back too. I am guessing that the Verizon note 3 FSG is identical in all US Qualcomm note3's. I hope someone will help me confirm this by checking their MD5 on their FSG mount. The command "reboot nvrestore" will probably corrupt modemst1 and modemst2 too. I'm not gonna try it
Clean copy of FSG (mmcblk0p18) MD5 221daabe2e089699626e4b22606ad621 (folks with working note 3's please verify this check sum and post your model and MD5, You should have a backup anyway, the latest EFS Professional is now compatible with our snapdragon note 3's.
Backup mmcblk0p18 and the MD5 can be copied (Ctrl + C) directly from EFS Professional.
These "TOXIC" commands should not be in our note 3's, or S5's, shame on you Samsung!
EFS Professional has been updated so These important partitions can be backed up very easily, link below
Important partition that could save us note 3 owners:
aboot -> /dev/block/mmcblk0p6
efs -> /dev/block/mmcblk0p11
modemst1 -> /dev/block/mmcblk0p12
modemst2 -> /dev/block/mmcblk0p13
fsg -> /dev/block/mmcblk0p18
Prior to my fix, I was able to get my phone to run for several minutes at a time after flashing AOKP T-mobile ROM. (They now have a unified build). This ROM let me get logcats, access to play store through wifi, and in the end was able to drop the clean FSG into /dev/block with root explorer. Without even rebooting I looked at the status screen to my amazement and read my MEID, PRL, ESN were all there!
Another tip, by entering safe mode (hold power down until note3 screen shows up, then hold volume down until fully booted). The Safemode watermark will be on bottom left corner of screen. Airplane mode and wireless off helped too.
Six weeks of hell and way over 300 hours learning about Android's FS, and severe hacking on my phone finally paid off.
Thanks to all that helped me, and this forum!
I will add more info later, so others hopefully will be able to recover from this. Time to play with my note 3
Please use a hex editor to confirm FSG and backup are corrupt (HxD Hex Editor is good). See attached thumbnails at the bottom of this post comparing good partitions on top and corrupt on bottom. FSG should have "IMGEFSG" in hex, not IMGEFS1x. Backup should be completely empty, all 00000, if block17 has any hex data it's been "Samsunged".
If you want help from me please do the following steps:
Using your recovery program's File Manager, copy mmcklb0p18 and 17 to your External sd, save them, change names to mmcklb0p18bak and **17bak. Then it will be easy to view the mounts in hex editor on your computer, and have backups just in case. Once you confirm they're corrupt please post your note 3 model, describe what triggered bootloops, and paste the first 4 lines of FSG hex code. This fix will only help those that had their note-3 FSG corrupted by "reboot nvbackup", or possibly while using an EFS backup program that calls the command (EFS by Boris or early versions of EFS pro).
confirm FSG is corrupt with hex editor,
post your note 3 model, what triggered your problem, and the first 4 lines of hex from your **bak's to this thread. (first line using wordpad will work too)
Then PM me for faster response.
copy & paste the clean FSG to your /dev/block (You can use several methods to do this: TWRP or CWM's File Manger, or adb).
Sip Iced Tea and enjoy your note 3
Tips on how to backup and replace FSG
(Note: I have also looked at my S5 developer edition (ET-G900V) it looks like it is susceptible to being be bricked too. I also have a clean copy of S5 FSG)
Attached is my /dev system details:
adb shell
ls -lR /dev
Code:
/dev/block/platform/msm_sdcc.1/by-name:
lrwxrwxrwx 1 root root 20 Jan 2 18:08 aboot -> /dev/block/mmcblk0p6 <-------aboot
lrwxrwxrwx 1 root root 20 Jan 2 18:08 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 2 18:08 backup -> /dev/block/mmcblk0p17 <-----backup
lrwxrwxrwx 1 root root 21 Jan 2 18:08 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 2 18:08 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 2 18:08 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 2 18:08 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 2 18:08 efs -> /dev/block/mmcblk0p11 <------EFS
lrwxrwxrwx 1 root root 21 Jan 2 18:08 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 2 18:08 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 2 18:08 fsg -> /dev/block/mmcblk0p18 <-----FSG
lrwxrwxrwx 1 root root 20 Jan 2 18:08 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 2 18:08 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 2 18:08 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 2 18:08 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 2 18:08 param -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 2 18:08 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 2 18:08 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 2 18:08 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 Jan 2 18:08 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 2 18:08 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 2 18:08 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 2 18:08 system -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 2 18:08 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 2 18:08 userdata -> /dev/block/mmcblk0p25
#
Old stuff from my original post:
I am starting a thread here so I can document the bootloop problem with my Note 3 SM-N900V Developer Edition. I have screen captures, files and code that hopefully will reveal the problem, and maybe one of the Guru's can help fix.
The original problem was caused several months ago after a restore from TWRP openrecovery-twrp-2.6.3.0-hltetmo This version of TWRP had a problem with the efs restore. Endless bootloops, about 28 hours later I had my DE back working after searching XDA. The fix that I found was not correct for this model .it stopped the bootloops, but the efs folder that I created was from the wrong block. The fix I found had a script to rebuild efs folder from /dev/block/mmcblk0p12.This block is modemst1 in the Qualcomm model. The script created an EFS folder in root, but it was empty. Here is the thread, but it's not right for SM-N900V DE, and many others. If I knew then what I know, "confirm the EFS block before applying any script".
Last week I tried to do a efs backup so I could eventually fix the "Factory Mode" problem from blank efs folder. That's when efs folder went away again, "reboot nvbackup" and bootloops, I can't get it to stick since. Boot loops for a week.
Tried to rebuild missing efs folder using what I think is the correct adb script for SM-N900V DE using philz_touch_6.12.8-hltevzw The usb driver
Other Note 3's have efs in mmcblk0p12
Code:
mke2fs /dev/block/mmcblk0p11
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs
adb shell
mke2fs /dev/block/mmcblk0p11
Code:
mke2fs /dev/block/mmcblk0p11
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
3584 inodes, 14336 blocks
716 blocks (4.99%) reserved for the super user
First data block=1
Maximum filesystem blocks=14680064
2 block groups
8192 blocks per group, 8192 fragments per group
1792 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ #
I tried several other similar scripts and it would rebuild the proper /efs folder
contents of my efs folder built from mmcblk0p11 (EFS is lost on reboot)
Code:
adb shell
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs
ls /efs
FactoryApp lost+found
U0BwJo4kmkmm-BgyzUZgoEY7pn8_ prov
drm prov_data
hw_offset wifi
~ #
Copy of my efs after running script, before reboot. I think some folders and files are missing.
DRM is is intact
Some of the FactoryMode files are missing too. My EFS folder is only 1.02MB
Code:
adb shell
~ # ls -lR /efs
ls -lR /efs
/efs:
drwxrwxr-x 2 system system 1024 Jan 1 2013 FactoryApp
drwxrwxr-- 4 drm system 1024 Jan 1 2013 drm
-rw------- 1 system system 3 Jan 1 2013 hw_offset
drwx------ 2 root root 12288 Jan 2 21:10 lost+found
drwxrwx--- 2 radio system 1024 Jan 2 21:11 prov
drwx------ 4 system system 1024 Jan 1 2013 prov_data
drwxrwxr-x 2 radio system 1024 Jan 2 21:11 wifi
/efs/FactoryApp:
-rwxrwxr-x 1 media system 1 Jan 1 2013 earjack_count
-rwxr--r-- 1 system system 2 Jan 1 2013 factorymode
-rwxrwxr-x 1 system radio 4 Jan 2 21:11 fdata
-rwxrwxr-x 1 system radio 0 Jan 2 21:11 hist_nv
-rwxr--r-- 1 system system 3 Jan 1 2013 keystr
-rwxrwxr-x 1 system radio 1020 Jan 2 21:11 test_nv
/efs/drm:
drwx------ 3 system system 1024 Jan 1 2013 app_ms
drwxrwxr-- 3 drm system 1024 Jan 2 21:11 sdrm
/efs/drm/app_ms:
drwx------ 2 system system 1024 Jan 1 2013 MxNw57WpMwUrwl29zlzqzCi
rAwg_
/efs/drm/app_ms/MxNw57WpMwUrwl29zlzqzCirAwg_:
-rwx------ 1 system system 1072 Jan 1 2013 -lndchIc3h7lLcBHqLCVTRw
sBQU_
-rwx------ 1 system system 1072 Jan 1 2013 2a8EC7fiuOLWZ6xkJz2qV9B
UyqY_
-rwx------ 1 system system 1072 Jan 1 2013 39j-Wt07C-dAogUK9xbr3vf
7xFY_
-rwx------ 1 system system 1072 Jan 1 2013 8oPVwf9NrhTSk5DXKuiMfak
4SQI_
-rwx------ 1 system system 1072 Jan 1 2013 AqEmxtFosQPPH-ASRTWrTN0
zFwI_
-rwx------ 1 system system 1072 Jan 1 2013 aZ532jwWSI64IZ5usuKIzxv
4BOQ_
-rwx------ 1 system system 1072 Jan 1 2013 fil8fYE2kpyD+gNF9IULyWp
JiMs_
-rwx------ 1 system system 1072 Jan 1 2013 mxrN+7RFB9miwfZrRU1xlWi
eu4M_
-rwx------ 1 system system 1072 Jan 1 2013 oUtpSCeDR40uafRBmUR7mFY
w+ik_
-rwx------ 1 system system 1072 Jan 1 2013 wHPCuFBMd5Z7-P4jMU--oBv
QDz4_
-rwx------ 1 system system 1072 Jan 1 2013 xmCXhhIu8UwnU13OCzfWzRX
OFiI_
/efs/drm/sdrm:
drwxrwxr-- 2 drm system 1024 Jan 2 21:11 data_agent
/efs/drm/sdrm/data_agent:
/efs/lost+found:
/efs/prov:
-rw-rw---- 1 radio system 0 Jan 2 21:11 libdevkm.lock
/efs/prov_data:
drwx------ 2 system system 1024 Jan 1 2013 G+8IRqTrHDIvQWyDjPjJkVB
5u6o_
drwx------ 2 system system 1024 Jan 1 2013 bG5QQZ77nDjI2757PvvQ3rP
PrVg_
/efs/prov_data/G+8IRqTrHDIvQWyDjPjJkVB5u6o_:
/efs/prov_data/bG5QQZ77nDjI2757PvvQ3rPPrVg_:
/efs/wifi:
~ #
After reboot, efs folder is gone.
Code:
>adb shell ls -a -l /efs
ls: efs: No such file or directory
~ #
efs mmcblk0p11 14336KB
MD5 c91e8d8d61148fbc73074dc460b93894
Logcat
Captured some logcats
Code:
I/ARMAssembler( 183): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at [0xb49e12d0:0xb49e13a0] in 46146 ns
I/ARMAssembler( 183): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at [0xb49e13b0:0xb49e1484] in 39062 ns
I/ARMAssembler( 183): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at [0xb49e1490:0xb49e1540] in 35834 ns
I/Vold ( 185): /dev/block/vold/179:65 being considered for volume sdcard1
D/Vold ( 185): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 185): Trying to get filesystem type for /dev/block/vold/179:65
D/Vold ( 185): Found vfat filesystem on /dev/block/vold/179:65
I/fsck_msdos( 185): ** /dev/block/vold/179:65
I/fsck_msdos( 185): ** Phase 1 - Read and Compare FATs
I/fsck_msdos( 185): Attempting to allocate 3769 KB for FAT
I/fsck_msdos( 185): Attempting to allocate 3769 KB for FAT
I/fsck_msdos( 185): ** Phase 2 - Check Cluster Chains
I/fsck_msdos( 185): ** Phase 3 - Checking Directories
I/fsck_msdos( 185): ** Phase 4 - Checking for Lost Files
I/fsck_msdos( 185): 258 files, 2845024 free (482123 clusters)
W/Vold ( 185): blkid failed to identify /dev/block/vold/179:65
I/Vold ( 185): Filesystem check completed OK
D/Vold ( 185): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
<snip>
<snip>
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
I/ServiceManager( 1021): Waiting for service SurfaceFlinger...
D/Vold ( 185): Volume sdcard1 state changing 4 (Mounted) -> 5 (Unmounting)
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
I/ServiceManager( 1021): Waiting for service SurfaceFlinger...
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
I/ServiceManager( 1021): Waiting for service SurfaceFlinger...
I/Vold ( 185): /storage/sdcard1 sucessfully unmounted
I/Vold ( 185): /storage/sdcard1 sucessfully unmounted
I/Vold ( 185): /storage/sdcard1 unmounted successfully
D/Vold ( 185): Volume sdcard1 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)
I/ServiceManager( 1017): Waiting for service SurfaceFlinger...
Code:
01-01 15:40:52.669: D/(3450): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.669: D/(3450): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 15:40:52.679: D/QSEECOMAPI:(3450): QSEECom_get_handle sb_length = 0x104e80
01-01 15:40:52.679: E/QSEECOMAPI:(3450): Error::Failed to open /dev/qseecom device
01-01 15:40:52.679: E/(3450): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 15:40:52.679: D/(3450): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 15:40:52.679: D/QSEECOMAPI:(3450): QSEECom_get_handle sb_length = 0x104e80
01-01 15:40:52.679: E/QSEECOMAPI:(3450): Error::Failed to open /dev/qseecom device
01-01 15:40:52.679: E/(3450): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 15:40:52.679: D/(3450): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 15:40:52.679: D/QSEECOMAPI:(3450): QSEECom_get_handle sb_length = 0x104e80
01-01 15:40:52.679: E/QSEECOMAPI:(3450): Error::Failed to open /dev/qseecom device
01-01 15:40:52.679: E/(3450): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 15:40:52.679: D/(3450): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 15:40:52.679: D/QSEECOMAPI:(3450): QSEECom_get_handle sb_length = 0x104e80
01-01 15:40:52.679: E/QSEECOMAPI:(3450): Error::Failed to open /dev/qseecom device
01-01 15:40:52.679: E/(3450): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 15:40:52.679: D/(3450): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:40:52.679: D/(3450): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 15:40:52.679: D/QSEECOMAPI:(3450): QSEECom_get_handle sb_length = 0x104e80
01-01 15:40:52.679: E/QSEECOMAPI:(3450): Error::Failed to open /dev/qseecom device
01-01 15:40:52.679: E/(3450): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 15:40:52.769: E/su(3455): Getting exe path failed with 13: Permission denied
01-01 15:40:52.769: W/su(3455): request rejected (2000->0 /system/bin/sh)
01-01 15:40:53.799: E/su(3475): Getting exe path failed with 13: Permission denied
01-01 15:40:53.809: W/su(3475): request rejected (2000->0 /system/bin/sh)
01-01 15:40:53.909: E/su(3480): Getting exe path failed with 13: Permission denied
01-01 15:40:53.909: W/su(3480): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.009: E/su(3510): Getting exe path failed with 13: Permission denied
01-01 15:40:55.009: W/su(3510): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.119: E/su(3515): Getting exe path failed with 13: Permission denied
01-01 15:40:55.119: W/su(3515): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.219: E/su(3524): Getting exe path failed with 13: Permission denied
01-01 15:40:55.219: W/su(3524): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.319: E/su(3530): Getting exe path failed with 13: Permission denied
01-01 15:40:55.319: W/su(3530): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.409: E/su(3534): Getting exe path failed with 13: Permission denied
01-01 15:40:55.409: W/su(3534): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.509: E/su(3535): Getting exe path failed with 13: Permission denied
01-01 15:40:55.519: W/su(3535): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.609: E/su(3536): Getting exe path failed with 13: Permission denied
01-01 15:40:55.619: W/su(3536): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.709: E/su(3538): Getting exe path failed with 13: Permission denied
01-01 15:40:55.719: W/su(3538): request rejected (2000->0 /system/bin/sh)
01-01 15:40:55.809: E/su(3539): Getting exe path failed with 13: Permission denied
01-01 15:40:55.819: W/su(3539): request rejected (2000->0 /system/bin/sh)
01-01 15:40:56.219: E/su(3545): Getting exe path failed with 13: Permission denied
01-01 15:40:56.219: W/su(3545): request rejected (2000->0 /system/bin/sh)
01-01 15:40:56.519: I/dumpstate(3414): done
01-01 15:41:26.659: D/(4156): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:41:26.659: D/(4156): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 15:41:26.659: D/(4156): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 15:41:26.659: D/QSEECOMAPI:(4156): QSEECom_get_handle sb_length = 0x104e80
01-01 15:41:26.659: E/QSEECOMAPI:(4156): Error::Failed to open /dev/qseecom device
01-01 15:41:26.659: E/(4156): TIMA: tima-pkm--Unable to start TZ app; errno = 9
radionerd said:
Other Note 3's have efs in mmcblk0p12
Click to expand...
Click to collapse
<threadjack>
So this isn't accidentally misinterpreted, here "other" means non-Verizon versions of the Note 3.
The partitioning between a retail Verizon SM-N900V(ZKE) and Developer Edition Verizon are identical afaik.
</threadjack>
bftb0 said:
<threadjack>
So this isn't accidentally misinterpreted, here "other" means non-Verizon versions of the Note 3.
The partitioning between a retail Verizon SM-N900V(ZKE) and Developer Edition Verizon are identical afaik.
</threadjack>
Click to expand...
Click to collapse
I agree, and probably T-mobile too. There are others that had the same problem. After my bad TWRP restore 2 months ago it was in FactoryMode, no lock screen, and a few other annoyances. The bad (mount -t ext4 /dev/block/mmcblk0p12 /efs) is modem1(blk12) into efs.
7 days ago I tried to just get a backup of dev blocks and efs from efs pro. That's when it borked hard. I hope others with Qualcomm note 3's won't just blindly apply the script that writes modem1 to efs. Ouch!
Thanks,
radionerd said:
I agree, and probably T-mobile too. There are others that had the same problem. After my bad TWRP restore 2 months ago it was in FactoryMode, no lock screen, and a few other annoyances. The bad (mount -t ext4 /dev/block/mmcblk0p12 /efs) is modem1(blk12) into efs.
7 days ago I tried to just get a backup of dev blocks and efs from efs pro. That's when it borked hard. I hope others with Qualcomm note 3's won't just blindly apply the script that writes modem1 to efs. Ouch!
Thanks,
Click to expand...
Click to collapse
Did you try to create or edit the mounts via fstab, or vold.fstab or just editing mounts to include the following?
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic 0 0
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Did you try to create or edit the mounts via fstab, or vold.fstab or just editing mounts to include the following?
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic 0 0
Click to expand...
Click to collapse
I applied the script, attached logcat before reboot, and after. It cleaned up a few errors.
Thank You for the help!
logcat before reboot:
Code:
~ # mkdir /efs
mkdir /efs
~ # mount -t ext4 /dev/block/mmcblk0p11 /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs
~ # /dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,node
v,noatime,discard,journal_c hecksum,journal_async_commit,noauto_da_alloc,error s
=panic 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,node
v,noatime,discard,journal_c hecksum,journal_async_commit,noauto_da_alloc,error s
=panic 0 0
/sbin/sh: /dev/block/platform/msm_sdcc.1/by-name/efs: Permission denied
~ #
--------- beginning of /dev/log/system
I/Vold ( 184): Vold 2.1 (the revenge) firing up
D/Vold ( 184): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 184): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 184): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 184): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 65, PARTN 1
D/Vold ( 184): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
--------- beginning of /dev/log/main
I/ARMAssembler( 182): generated scanline__00000077:03545402_00000A02_00000000 [ 31 ipp] (53 ins) at [0xb49b71f0:0xb49b72c4] in 65417 ns
I/ARMAssembler( 182): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at [0xb49b72d0:0xb49b73a0] in 46406 ns
I/ARMAssembler( 182): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at [0xb49b73b0:0xb49b7484] in 39062 ns
I/ARMAssembler( 182): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at [0xb49b7490:0xb49b7540] in 37187 ns
I/Vold ( 184): /dev/block/vold/179:65 being considered for volume sdcard1
D/Vold ( 184): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 184): Trying to get filesystem type for /dev/block/vold/179:65
I/fsck_msdos( 184): ** /dev/block/vold/179:65
D/Vold ( 184): Found vfat filesystem on /dev/block/vold/179:65
I/fsck_msdos( 184): ** Phase 1 - Read and Compare FATs
I/fsck_msdos( 184): Attempting to allocate 3769 KB for FAT
I/fsck_msdos( 184): Attempting to allocate 3769 KB for FAT
I/fsck_msdos( 184): ** Phase 2 - Check Cluster Chains
I/fsck_msdos( 184): ** Phase 3 - Checking Directories
I/fsck_msdos( 184): ** Phase 4 - Checking for Lost Files
I/fsck_msdos( 184): 267 files, 2843776 free (482084 clusters)
W/Vold ( 184): blkid failed to identify /dev/block/vold/179:65
I/Vold ( 184): Filesystem check completed OK
D/Vold ( 184): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)
D/Vold ( 184): Volume sdcard1 state changing 4 (Mounted) -> 5 (Unmounting)
I/Vold ( 184): /storage/sdcard1 sucessfully unmounted
I/Vold ( 184): /storage/sdcard1 sucessfully unmounted
I/Vold ( 184): /storage/sdcard1 unmounted successfully
D/Vold ( 184): Volume sdcard1 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)
I/Vold ( 184): /dev/block/vold/179:65 being considered for volume sdcard1
D/Vold ( 184): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 184): Trying to get filesystem type for /dev/block/vold/179:65
D/Vold ( 184): Found vfat filesystem on /dev/block/vold/179:65
I/fsck_msdos( 184): ** /dev/block/vold/179:65
I/fsck_msdos( 184): ** Phase 1 - Read and Compare FATs
I/fsck_msdos( 184): Attempting to allocate 3769 KB for FAT
I/fsck_msdos( 184): Attempting to allocate 3769 KB for FAT
I/fsck_msdos( 184): ** Phase 2 - Check Cluster Chains
I/fsck_msdos( 184): ** Phase 3 - Checking Directories
I/fsck_msdos( 184): ** Phase 4 - Checking for Lost Files
I/fsck_msdos( 184): 267 files, 2843776 free (482084 clusters)
I/Vold ( 184): Filesystem check completed OK
W/Vold ( 184): blkid failed to identify /dev/block/vold/179:65
D/Vold ( 184): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)
D/Vold ( 184): Volume sdcard1 state changing 4 (Mounted) -> 5 (Unmounting)
I/Vold ( 184): /storage/sdcard1 sucessfully unmounted
I/Vold ( 184): /storage/sdcard1 sucessfully unmounted
I/Vold ( 184): /storage/sdcard1 unmounted successfully
D/Vold ( 184): Volume sdcard1 state changing 5 (Unmounting) -> 1 (Idle-Unmounted)
After reboot
Code:
beginning of /dev/log/main
D/ ( 3502): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: tima-pkm--Attempting to load TZAPPS
D/QSEECOMAPI: ( 3502): QSEECom_get_handle sb_length = 0x104e80
E/QSEECOMAPI: ( 3502): Error::Failed to open /dev/qseecom device
E/ ( 3502): TIMA: tima-pkm--Unable to start TZ app; errno = 9
D/ ( 3502): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: tima-pkm--Attempting to load TZAPPS
D/QSEECOMAPI: ( 3502): QSEECom_get_handle sb_length = 0x104e80
E/QSEECOMAPI: ( 3502): Error::Failed to open /dev/qseecom device
E/ ( 3502): TIMA: tima-pkm--Unable to start TZ app; errno = 9
D/ ( 3502): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: tima-pkm--Attempting to load TZAPPS
D/QSEECOMAPI: ( 3502): QSEECom_get_handle sb_length = 0x104e80
E/QSEECOMAPI: ( 3502): Error::Failed to open /dev/qseecom device
E/ ( 3502): TIMA: tima-pkm--Unable to start TZ app; errno = 9
D/ ( 3502): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: tima-pkm--Attempting to load TZAPPS
D/QSEECOMAPI: ( 3502): QSEECom_get_handle sb_length = 0x104e80
E/QSEECOMAPI: ( 3502): Error::Failed to open /dev/qseecom device
E/ ( 3502): TIMA: tima-pkm--Unable to start TZ app; errno = 9
D/ ( 3502): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
D/ ( 3502): TIMA: tima-pkm--Attempting to load TZAPPS
D/QSEECOMAPI: ( 3502): QSEECom_get_handle sb_length = 0x104e80
E/QSEECOMAPI: ( 3502): Error::Failed to open /dev/qseecom device
E/ ( 3502): TIMA: tima-pkm--Unable to start TZ app; errno = 9
E/su ( 3507): Getting exe path failed with 13: Permission denied
W/su ( 3507): request rejected (2000->0 /system/bin/sh)
E/su ( 3550): Getting exe path failed with 13: Permission denied
W/su ( 3550): request rejected (2000->0 /system/bin/sh)
E/su ( 3551): Getting exe path failed with 13: Permission denied
radionerd said:
I applied the script, attached logcat before reboot, and after. It cleaned up a few errors.
Thank You for the help!
Click to expand...
Click to collapse
Okay, first update busybox, I suggest installing "Busybox on Rails" from the playstore. Then make sure SuperSu is up to date and open the SuperSu app and place a check in the box that says something like "enable su at boot"
then download and unzip the create_firmware_symlinks file ive attached and connect your phone to your pc and try to replicate what I did below (I used my touchpad but the commands are still the same) make sure the id of sh is the same the output below.
dd if=/system/xbin/su of=/system/bin/.su
[email protected] ~ $ adb shell
[email protected]:/ # su
[email protected]:/ # dd if=/system/xbin/su of=/system/bin/.su
729+1 records in
729+1 records out
373584 bytes transferred in 0.099 secs (3773575 bytes/sec)
[email protected]:/ # mv /system/bin/.su /system/bin/su
[email protected]:/ # whoami
root
[email protected]:/ # id
uid=0(root) gid=0(root)
127|[email protected]:/ # id sh
uid=0(root) gid=0(root)
[email protected]:/ # exit
[email protected]:/ # exit
[email protected] ~ $ adb push create_firmware_symlinks /data/local/tmp
64 KB/s (3101 bytes in 0.047s)
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 create_firmware_symlinks
[email protected]:/data/local/tmp # sh create_firmware_symlinks
.......trimmed--------
[email protected]:/data/local/tmp # reboot
Click to expand...
Click to collapse
Surge1223 said:
Okay, first update busybox, I suggest installing "Busybox on Rails" from the playstore. Then make sure SuperSu is up to date and open the SuperSu app and place a check in the box that says something like "enable su at boot"
then download and unzip the create_firmware_symlinks file ive attached and connect your phone to your pc and try to replicate what I did below (I used my touchpad but the commands are still the same) make sure the id of sh is the same the output below.
Click to expand...
Click to collapse
I am studying this. I have busybox v1.21.1-kk static. Since I can't boot (bootloops), I looked into sideloading latest binaries. Busybox doesn't have v1.22.1.bin posted yet, just source.
I normally have Super SU pro. Philz CWM gives and option to install his version.
Thank You, I'm learning
Code:
C:\Users\Alan>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # busybox
busybox
BusyBox v1.21.1-kk static (2013-11-24 11:52 +0100) multi-call binary.
~ # whoami
whoami
root
~ # id
id
uid=0(root) gid=0(root)
~ # $ su
$ su
/sbin/sh: $: not found
My latest logcat snip after spending the day with my note 3. I think I'm going to wear out 3 buttons, or get carpal tunnel
Code:
?:??: W/?(?): --------- beginning of /dev/log/main
01-01 01:10:48.599: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.599: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 01:10:48.609: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 01:10:48.609: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
radionerd said:
My latest logcat snip after spending the day with my note 3. I think I'm going to wear out 3 buttons, or get carpal tunnel
Code:
?:??: W/?(?): --------- beginning of /dev/log/main
01-01 01:10:48.599: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.599: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 01:10:48.609: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
01-01 01:10:48.609: D/(3477): TAL: TIMA_backend_open--int8_t TIMA_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: QCOM_backend_open--int8_t QCOM_backend_open(void**, appID, uint32_t, uint32_t)
01-01 01:10:48.609: D/(3477): TIMA: tima-pkm--Attempting to load TZAPPS
01-01 01:10:48.609: D/QSEECOMAPI:(3477): QSEECom_get_handle sb_length = 0x104e80
01-01 01:10:48.609: E/QSEECOMAPI:(3477): Error::Failed to open /dev/qseecom device
01-01 01:10:48.609: E/(3477): TIMA: tima-pkm--Unable to start TZ app; errno = 9
Click to expand...
Click to collapse
You don't need to upadate Busybox linux style. Just download the app I mentioned in my last post, and it will update and repair your busybox binaries without rebooting. Also SuperSu pro is a donation version, I think your problem would be solved if you just updated supersu and busybox and then mounted /dev thats why I suggested it. You can download the latest SuperSu binary from Chainfire's thread but im assuming you have wifi you can use to connect to your note 3 to update those apps right? I think your making this too hard on yourself lol. Did you run all the commands I posted above? If so what if anything is currently in the /efs folder?
Edit: there seems to be an issue with su binary are you still rooted? Check the id on su, if its anything other than 0 then under adb shell
Code:
[email protected]:/ # mount -o remount, rw /system
[email protected]:/ # chown 0.0 /system/bin/su
[email protected]:/ # chmod 06755 /system/bin/su
[email protected]:/ # ln -s /system/bin/su /system/xbin/su
After this you would still need to update/reinstall busybox and supersu in order for the "sh" issue to be fixed
Surge1223 said:
Okay, first update busybox, I suggest installing "Busybox on Rails" from the playstore. Then make sure SuperSu is up to date and open the SuperSu app and place a check in the box that says something like "enable su at boot"
then download and unzip the create_firmware_symlinks file ive attached and connect your phone to your pc and try to replicate what I did below (I used my touchpad but the commands are still the same) make sure the id of sh is the same the output below.
Click to expand...
Click to collapse
Edit: Stand-by I jumped the gun. I will update after I do the steps right
Thanks Man!
Firmware folder with many Symlink errors
Code:
~ # ls -lR /system/etc/firmware
ls -lR /system/etc/firmware
/system/etc/firmware:
-rw-r--r-- 1 root root 1156 Aug 1 2008 a225_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a225_pm4.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a225p5_pm4.fw
-rw-r--r-- 1 root root 1156 Aug 1 2008 a300_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a300_pm4.fw
-rw-r--r-- 1 root root 2212 Aug 1 2008 a330_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a330_pm4.fw
-rw-r--r-- 1 root root 16128 Aug 1 2008 cpp_firmware_v1_1_1.fw
-rw-r--r-- 1 root root 16384 Aug 1 2008 cpp_firmware_v1_1_6.fw
-rw-r--r-- 1 root root 16384 Aug 1 2008 cpp_firmware_v1_2_0.fw
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b00 -> /firmware/image/dtcpip.b00
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b01 -> /firmware/image/dtcpip.b01
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b02 -> /firmware/image/dtcpip.b02
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b03 -> /firmware/image/dtcpip.b03
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.mdt -> /firmware/image/dtcpip.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b00 -> /firmware/image/keymaste.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b01 -> /firmware/image/keymaste.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b02 -> /firmware/image/keymaste.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b03 -> /firmware/image/keymaste.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.mdt -> /firmware/image/keymaste.mdt
-rw-r--r-- 1 root root 1156 Aug 1 2008 leia_pfp_470.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 leia_pm4_470.fw
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b00 -> /firmware/image/mc_v2.b00
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b01 -> /firmware/image/mc_v2.b01
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b02 -> /firmware/image/mc_v2.b02
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b03 -> /firmware/image/mc_v2.b03
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.mdt -> /firmware/image/mc_v2.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b00 -> /firmware/image/playread.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b01 -> /firmware/image/playread.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b02 -> /firmware/image/playread.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b03 -> /firmware/image/playread.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.mdt -> /firmware/image/playread.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b00 -> /firmware/image/sec_stor.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b01 -> /firmware/image/sec_stor.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b02 -> /firmware/image/sec_stor.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b03 -> /firmware/image/sec_stor.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.mdt -> /firmware/image/sec_stor.mdt
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b00 -> /firmware/image/skm.b00
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b01 -> /firmware/image/skm.b01
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b02 -> /firmware/image/skm.b02
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b03 -> /firmware/image/skm.b03
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.mdt -> /firmware/image/skm.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b00 -> /firmware/image/sshdcpap.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b01 -> /firmware/image/sshdcpap.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b02 -> /firmware/image/sshdcpap.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b03 -> /firmware/image/sshdcpap.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.mdt -> /firmware/image/sshdcpap.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b00 -> /firmware/image/tima_atn.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b01 -> /firmware/image/tima_atn.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b02 -> /firmware/image/tima_atn.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b03 -> /firmware/image/tima_atn.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.mdt -> /firmware/image/tima_atn.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b00 -> /firmware/image/tima_key.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b01 -> /firmware/image/tima_key.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b02 -> /firmware/image/tima_key.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b03 -> /firmware/image/tima_key.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.mdt -> /firmware/image/tima_key.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b00 -> /firmware/image/tima_lkm.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b01 -> /firmware/image/tima_lkm.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b02 -> /firmware/image/tima_lkm.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b03 -> /firmware/image/tima_lkm.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.mdt -> /firmware/image/tima_lkm.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b00 -> /firmware/image/tima_pkm.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b01 -> /firmware/image/tima_pkm.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b02 -> /firmware/image/tima_pkm.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b03 -> /firmware/image/tima_pkm.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.mdt -> /firmware/image/tima_pkm.mdt
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b00 -> /firmware/image/venus.b00
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b01 -> /firmware/image/venus.b01
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b02 -> /firmware/image/venus.b02
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b03 -> /firmware/image/venus.b03
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b04 -> /firmware/image/venus.b04
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.mdt -> /firmware/image/venus.mdt
drwxr-xr-x 2 root root 4096 Jan 4 13:55 wcd9320
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b00 -> /firmware/image/widevine.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b01 -> /firmware/image/widevine.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b02 -> /firmware/image/widevine.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b03 -> /firmware/image/widevine.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.mdt -> /firmware/image/widevine.mdt
/system/etc/firmware/wcd9320:
lrwxrwxrwx 1 root root 25 Jan 4 13:55 wcd9320_mbhc.bin -> /data/misc/audio/mbhc.bin
~ #
radionerd said:
Edit: Stand-by I jumped the gun. I will update after I do the steps right
Thanks Man!
Firmware folder with many Symlink errors
Code:
~ # ls -lR /system/etc/firmware
ls -lR /system/etc/firmware
/system/etc/firmware:
-rw-r--r-- 1 root root 1156 Aug 1 2008 a225_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a225_pm4.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a225p5_pm4.fw
-rw-r--r-- 1 root root 1156 Aug 1 2008 a300_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a300_pm4.fw
-rw-r--r-- 1 root root 2212 Aug 1 2008 a330_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a330_pm4.fw
-rw-r--r-- 1 root root 16128 Aug 1 2008 cpp_firmware_v1_1_1.fw
-rw-r--r-- 1 root root 16384 Aug 1 2008 cpp_firmware_v1_1_6.fw
-rw-r--r-- 1 root root 16384 Aug 1 2008 cpp_firmware_v1_2_0.fw
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b00 -> /firmware/image/dtcpip.b00
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b01 -> /firmware/image/dtcpip.b01
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b02 -> /firmware/image/dtcpip.b02
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b03 -> /firmware/image/dtcpip.b03
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.mdt -> /firmware/image/dtcpip.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b00 -> /firmware/image/keymaste.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b01 -> /firmware/image/keymaste.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b02 -> /firmware/image/keymaste.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b03 -> /firmware/image/keymaste.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.mdt -> /firmware/image/keymaste.mdt
-rw-r--r-- 1 root root 1156 Aug 1 2008 leia_pfp_470.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 leia_pm4_470.fw
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b00 -> /firmware/image/mc_v2.b00
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b01 -> /firmware/image/mc_v2.b01
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b02 -> /firmware/image/mc_v2.b02
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b03 -> /firmware/image/mc_v2.b03
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.mdt -> /firmware/image/mc_v2.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b00 -> /firmware/image/playread.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b01 -> /firmware/image/playread.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b02 -> /firmware/image/playread.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b03 -> /firmware/image/playread.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.mdt -> /firmware/image/playread.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b00 -> /firmware/image/sec_stor.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b01 -> /firmware/image/sec_stor.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b02 -> /firmware/image/sec_stor.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b03 -> /firmware/image/sec_stor.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.mdt -> /firmware/image/sec_stor.mdt
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b00 -> /firmware/image/skm.b00
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b01 -> /firmware/image/skm.b01
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b02 -> /firmware/image/skm.b02
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b03 -> /firmware/image/skm.b03
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.mdt -> /firmware/image/skm.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b00 -> /firmware/image/sshdcpap.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b01 -> /firmware/image/sshdcpap.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b02 -> /firmware/image/sshdcpap.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b03 -> /firmware/image/sshdcpap.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.mdt -> /firmware/image/sshdcpap.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b00 -> /firmware/image/tima_atn.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b01 -> /firmware/image/tima_atn.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b02 -> /firmware/image/tima_atn.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b03 -> /firmware/image/tima_atn.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.mdt -> /firmware/image/tima_atn.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b00 -> /firmware/image/tima_key.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b01 -> /firmware/image/tima_key.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b02 -> /firmware/image/tima_key.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b03 -> /firmware/image/tima_key.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.mdt -> /firmware/image/tima_key.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b00 -> /firmware/image/tima_lkm.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b01 -> /firmware/image/tima_lkm.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b02 -> /firmware/image/tima_lkm.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b03 -> /firmware/image/tima_lkm.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.mdt -> /firmware/image/tima_lkm.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b00 -> /firmware/image/tima_pkm.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b01 -> /firmware/image/tima_pkm.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b02 -> /firmware/image/tima_pkm.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b03 -> /firmware/image/tima_pkm.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.mdt -> /firmware/image/tima_pkm.mdt
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b00 -> /firmware/image/venus.b00
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b01 -> /firmware/image/venus.b01
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b02 -> /firmware/image/venus.b02
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b03 -> /firmware/image/venus.b03
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b04 -> /firmware/image/venus.b04
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.mdt -> /firmware/image/venus.mdt
drwxr-xr-x 2 root root 4096 Jan 4 13:55 wcd9320
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b00 -> /firmware/image/widevine.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b01 -> /firmware/image/widevine.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b02 -> /firmware/image/widevine.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b03 -> /firmware/image/widevine.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.mdt -> /firmware/image/widevine.mdt
/system/etc/firmware/wcd9320:
lrwxrwxrwx 1 root root 25 Jan 4 13:55 wcd9320_mbhc.bin -> /data/misc/audio/mbhc.bin
~ #
Click to expand...
Click to collapse
Also if they arent mounting right try doing it like this and type su even if you have the #
su
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
You don't need to upadate Busybox linux style. Just download the app I mentioned in my last post, and it will update and repair your busybox binaries without rebooting. Also SuperSu pro is a donation version, I think your problem would be solved if you just updated supersu and busybox and then mounted /dev thats why I suggested it. You can download the latest SuperSu binary from Chainfire's thread but im assuming you have wifi you can use to connect to your note 3 to update those apps right? I think your making this too hard on yourself lol. Did you run all the commands I posted above? If so what if anything is currently in the /efs folder?
Edit: there seems to be an issue with su binary are you still rooted? Check the id on su, if its anything other than 0 then under adb shell
Code:
[email protected]:/ # mount -o remount, rw /system
[email protected]:/ # chown 0.0 /system/bin/su
[email protected]:/ # chmod 06755 /system/bin/su
[email protected]:/ # ln -s /system/bin/su /system/xbin/su
After this you would still need to update/reinstall busybox and supersu in order for the "sh" issue to be fixed
Click to expand...
Click to collapse
I don't have xbin folder. I have tried to reinstall Supersu from zip, and from within Philz recovery "Reroot system (SuperSU)". It's not nagging about SU on close "verify root on exit" Take a look at my sbin, superuser and busybox are in there.
Code:
ls -lR /sbin
/sbin:
lrwxrwxrwx 1 root root 7 Jan 1 00:00 [ -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 [[ -> busybox
-rwxr-x--- 1 root root 198980 Jan 1 00:00 adbd
lrwxrwxrwx 1 root root 7 Jan 1 00:00 ash -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 awk -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 basename -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 bbconfig -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 blkid -> busybox
-rwxr-x--- 1 root root 1420 Jan 1 00:00 bootscripts_mnt.sh
lrwxrwxrwx 1 root root 8 Jan 1 00:00 bu -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 bunzip2 -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 busybox -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 bzcat -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 bzip2 -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cal -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cat -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 catv -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 chattr -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 chgrp -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 chmod -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 chown -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 chroot -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cksum -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 clear -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cmp -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cp -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cpio -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 cut -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 date -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 dc -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 dd -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 dedupe -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 depmod -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 devmem -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 df -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 diff -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 dirname -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 dmesg -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 dos2unix -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 du -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 dump_image -> recovery
-rwxr-x--- 1 root root 289480 Jan 1 00:00 e2fsck
lrwxrwxrwx 1 root root 7 Jan 1 00:00 echo -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 edify -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 egrep -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 env -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 erase_image -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 expand -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 expr -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 false -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 fdisk -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 fgrep -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 find -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 flash_image -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 fold -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 free -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 freeramdisk -> busybox
lrwxrwxrwx 1 root root 11 Jan 1 00:00 fsck.exfat -> mount.exfat
lrwxrwxrwx 1 root root 8 Jan 1 00:00 fsck_msdos -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 fstrim -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 fuser -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 getopt -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 getprop -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 grep -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 groups -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 gunzip -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 gzip -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 head -> busybox
-rwxr-x--- 1 root root 124884 Jan 1 00:00 healthd
lrwxrwxrwx 1 root root 7 Jan 1 00:00 hexdump -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 id -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 insmod -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 install -> busybox
-rwxr-x--- 1 root root 4255 Jan 1 00:00 install-su.sh
lrwxrwxrwx 1 root root 7 Jan 1 00:00 kill -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 killall -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 killall5 -> busybox
-rwxr-x--- 1 root root 409 Jan 1 00:00 killrecovery.sh
lrwxrwxrwx 1 root root 7 Jan 1 00:00 length -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 less -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 ln -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 losetup -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 ls -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lsattr -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lsmod -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lspci -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lsusb -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lzcat -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lzop -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 lzopcat -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 make_ext4fs -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 makedevs -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 md5sum -> busybox
-rwxr-x--- 1 root root 324744 Jan 1 00:00 minivold
lrwxrwxrwx 1 root root 8 Jan 1 00:00 minizip -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mkdir -> busybox
-rwxr-x--- 1 root root 201328 Jan 1 00:00 mke2fs
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mkfifo -> busybox
lrwxrwxrwx 1 root root 11 Jan 1 00:00 mkfs.exfat -> mount.exfat
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mkfs.ext2 -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mknod -> busybox
-rwxr-x--- 1 root root 182084 Jan 1 00:00 mkntfs
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mkswap -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mktemp -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 mkyaffs2image -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 modinfo -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 modprobe -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 more -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mount -> busybox
-rwxr-x--- 1 root root 212628 Jan 1 00:00 mount.exfat
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mountpoint -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 mv -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 nanddump -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 nandroid -> recovery
-rwxr-x--- 1 root root 216 Jan 1 00:00 nandroid-md5.sh
lrwxrwxrwx 1 root root 7 Jan 1 00:00 nandwrite -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 newfs_msdos -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 nice -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 nohup -> busybox
-rwxr-x--- 1 root root 329984 Jan 1 00:00 ntfs-3g
lrwxrwxrwx 1 root root 7 Jan 1 00:00 od -> busybox
-rwxr-x--- 1 root root 346680 Jan 1 00:00 parted
lrwxrwxrwx 1 root root 7 Jan 1 00:00 patch -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 pgrep -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 pidof -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 pigz -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 pkill -> busybox
-rwxr-x--- 1 root root 248 Jan 1 00:00 postrecoveryboot.sh
lrwxrwxrwx 1 root root 7 Jan 1 00:00 printenv -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 printf -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 ps -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 pstree -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 pwd -> busybox
-rwxr-x--- 1 root root 1344 Jan 1 00:00 raw-backup.sh
lrwxrwxrwx 1 root root 7 Jan 1 00:00 rdev -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 readlink -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 realpath -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 reboot -> recovery
-rwxr-x--- 1 root root 1082380 Jan 1 00:00 recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 renice -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 reset -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 resize -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 rev -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 rm -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 rmdir -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 rmmod -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 run-parts -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 sdcard -> recovery
-rwxr-x--- 1 root root 16529 Jan 1 00:00 sdparted
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sed -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 seq -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 setconsole -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 setprop -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 setserial -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 setsid -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 setup_adbd -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sh -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sha1sum -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sha256sum -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sha512sum -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sleep -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sort -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 split -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 start -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 stat -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 stop -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 strings -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 stty -> busybox
drwxr-x--- 4 root root 0 Jan 1 00:00 supersu
lrwxrwxrwx 1 root root 7 Jan 1 00:00 swapoff -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 swapon -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sync -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 sysctl -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 tac -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 tail -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 tar -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 tee -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 test -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 time -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 top -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 touch -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 tr -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 true -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 ttysize -> busybox
-rwxr-x--- 1 root root 197364 Jan 1 00:00 tune2fs
lrwxrwxrwx 1 root root 7 Jan 1 00:00 ueventd -> ../init
lrwxrwxrwx 1 root root 7 Jan 1 00:00 umount -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 uname -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 unexpand -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 uniq -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 unix2dos -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 unlzma -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 unlzop -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 unxz -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 unyaffs -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 unzip -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 uptime -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 usleep -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 uudecode -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 uuencode -> busybox
lrwxrwxrwx 1 root root 8 Jan 1 00:00 vdc -> recovery
lrwxrwxrwx 1 root root 8 Jan 1 00:00 volume -> recovery
lrwxrwxrwx 1 root root 7 Jan 1 00:00 watch -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 watchdogd -> ../init
lrwxrwxrwx 1 root root 7 Jan 1 00:00 wc -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 which -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 whoami -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 xargs -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 xzcat -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 yes -> busybox
lrwxrwxrwx 1 root root 7 Jan 1 00:00 zcat -> busybox
-rwxr-x--- 1 root root 132839 Jan 1 00:00 zip
/sbin/supersu:
drwxr-x--- 2 root root 0 Jan 1 00:00 arm
drwxr-x--- 2 root root 0 Jan 1 00:00 common
/sbin/supersu/arm:
-rwxr-x--- 1 root root 113032 Jan 1 00:00 su
/sbin/supersu/common:
-rwxr-x--- 1 root root 55 Jan 1 00:00 99SuperSUDaemon
-rwxr-x--- 1 root root 629 Jan 1 00:00 install-recovery.sh
~ #
radionerd said:
Edit: Stand-by I jumped the gun. I will update after I do the steps right
Thanks Man!
Firmware folder with many Symlink errors
Code:
~ # ls -lR /system/etc/firmware
ls -lR /system/etc/firmware
/system/etc/firmware:
-rw-r--r-- 1 root root 1156 Aug 1 2008 a225_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a225_pm4.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a225p5_pm4.fw
-rw-r--r-- 1 root root 1156 Aug 1 2008 a300_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a300_pm4.fw
-rw-r--r-- 1 root root 2212 Aug 1 2008 a330_pfp.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 a330_pm4.fw
-rw-r--r-- 1 root root 16128 Aug 1 2008 cpp_firmware_v1_1_1.fw
-rw-r--r-- 1 root root 16384 Aug 1 2008 cpp_firmware_v1_1_6.fw
-rw-r--r-- 1 root root 16384 Aug 1 2008 cpp_firmware_v1_2_0.fw
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b00 -> /firmware/image/dtcpip.b00
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b01 -> /firmware/image/dtcpip.b01
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b02 -> /firmware/image/dtcpip.b02
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.b03 -> /firmware/image/dtcpip.b03
lrwxrwxrwx 1 root root 26 Jan 4 13:55 dtcpip.mdt -> /firmware/image/dtcpip.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b00 -> /firmware/image/keymaste.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b01 -> /firmware/image/keymaste.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b02 -> /firmware/image/keymaste.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.b03 -> /firmware/image/keymaste.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 keymaste.mdt -> /firmware/image/keymaste.mdt
-rw-r--r-- 1 root root 1156 Aug 1 2008 leia_pfp_470.fw
-rw-r--r-- 1 root root 9220 Aug 1 2008 leia_pm4_470.fw
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b00 -> /firmware/image/mc_v2.b00
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b01 -> /firmware/image/mc_v2.b01
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b02 -> /firmware/image/mc_v2.b02
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.b03 -> /firmware/image/mc_v2.b03
lrwxrwxrwx 1 root root 25 Jan 4 13:55 mc_v2.mdt -> /firmware/image/mc_v2.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b00 -> /firmware/image/playread.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b01 -> /firmware/image/playread.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b02 -> /firmware/image/playread.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.b03 -> /firmware/image/playread.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 playread.mdt -> /firmware/image/playread.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b00 -> /firmware/image/sec_stor.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b01 -> /firmware/image/sec_stor.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b02 -> /firmware/image/sec_stor.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.b03 -> /firmware/image/sec_stor.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sec_stor.mdt -> /firmware/image/sec_stor.mdt
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b00 -> /firmware/image/skm.b00
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b01 -> /firmware/image/skm.b01
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b02 -> /firmware/image/skm.b02
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.b03 -> /firmware/image/skm.b03
lrwxrwxrwx 1 root root 23 Jan 4 13:55 skm.mdt -> /firmware/image/skm.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b00 -> /firmware/image/sshdcpap.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b01 -> /firmware/image/sshdcpap.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b02 -> /firmware/image/sshdcpap.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.b03 -> /firmware/image/sshdcpap.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 sshdcpap.mdt -> /firmware/image/sshdcpap.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b00 -> /firmware/image/tima_atn.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b01 -> /firmware/image/tima_atn.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b02 -> /firmware/image/tima_atn.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.b03 -> /firmware/image/tima_atn.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_atn.mdt -> /firmware/image/tima_atn.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b00 -> /firmware/image/tima_key.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b01 -> /firmware/image/tima_key.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b02 -> /firmware/image/tima_key.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.b03 -> /firmware/image/tima_key.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_key.mdt -> /firmware/image/tima_key.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b00 -> /firmware/image/tima_lkm.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b01 -> /firmware/image/tima_lkm.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b02 -> /firmware/image/tima_lkm.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.b03 -> /firmware/image/tima_lkm.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_lkm.mdt -> /firmware/image/tima_lkm.mdt
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b00 -> /firmware/image/tima_pkm.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b01 -> /firmware/image/tima_pkm.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b02 -> /firmware/image/tima_pkm.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.b03 -> /firmware/image/tima_pkm.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 tima_pkm.mdt -> /firmware/image/tima_pkm.mdt
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b00 -> /firmware/image/venus.b00
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b01 -> /firmware/image/venus.b01
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b02 -> /firmware/image/venus.b02
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b03 -> /firmware/image/venus.b03
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.b04 -> /firmware/image/venus.b04
lrwxrwxrwx 1 root root 25 Jan 4 13:55 venus.mdt -> /firmware/image/venus.mdt
drwxr-xr-x 2 root root 4096 Jan 4 13:55 wcd9320
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b00 -> /firmware/image/widevine.b00
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b01 -> /firmware/image/widevine.b01
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b02 -> /firmware/image/widevine.b02
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.b03 -> /firmware/image/widevine.b03
lrwxrwxrwx 1 root root 28 Jan 4 13:55 widevine.mdt -> /firmware/image/widevine.mdt
/system/etc/firmware/wcd9320:
lrwxrwxrwx 1 root root 25 Jan 4 13:55 wcd9320_mbhc.bin -> /data/misc/audio/mbhc.bin
~ #
Click to expand...
Click to collapse
These are HLOS applications from your NON-HLOS image. What's really interesting is the dates on these files. Can you do a dd backup of your NON-HLOS partition? I haven't seen a release from JAN 28 yet...
I know su and busybox are present in sbin. However whether or not busybox is properly linked to /system upon boot remains to be seen. Is there a particular reason your adverse to following my recommendations on usinf the playstore etc? Just wondering...regardless of what sbin shows the fact is that sh and su dont have the proper permissions.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
I know su and busybox are present in sbin. However whether or not busybox is properly linked to /system upon boot remains to be seen. Is there a particular reason your adverse to following my recommendations on usinf the playstore etc? Just wondering...regardless of what sbin shows the fact is that sh and su dont have the proper permissions.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Surge,
Not at all, I totally appreciate your help, I'm stuck without it. I just don't know how I can install it, or run it for that matter all I have is recovery mode. I have SDK. Can it run in recovery mode?
Thanks Man!
radionerd said:
Surge,
Not at all, I totally appreciate your help, I'm stuck without it. I just don't know how I can install it, or run it for that matter all I have is recovery mode. I have SDK. Can it run in recovery mode?
Thanks Man!
Click to expand...
Click to collapse
What happens if you open the google playstore then search for Supersu, select it and select update? Then search for busybox and try install a busybox app?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
What happens if you open the google playstore then search for Supersu, select it and select update? Then search for busybox and try install a busybox app?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know how to get the apk into my bricked phone.???
I have installed supersu ver193.zip from Philz CWM recovery (It's in my external SD). Also tried the cwm superSU that is imbedded in Philz recovery. Neither allow me to run su. I get" /sbin/sh: $: not found". I must be missing something on googleplay. Can I download the apk to my computer, then sideload it?
~ # $ su
$ su
/sbin/sh: $: not found
Click to expand...
Click to collapse
When I get home from work I will try again.
Thanks for you patience.
It boots
Surge1223,
I decided to throw the latest AOKP T-mobile Rom at my Note 3. It has the latest busybox, and fresh superSU. So I wiped and dropped it in. My phone is now booting up completely. I have lost my MEID, but it's up and running! I think I'm out of the woods
I get FC reboot after a a few minutes when not in airplane mode.
Full backup done, gonna try to put my partial /efs folder in and see what happens.
Thank You for helping me!
AOKP cleaned up, partial logcat attached.
Code:
I/start ( 329): A wise man never plays leapfrog with a unicorn
I/irsc_util( 354): irsc tool created:0x2a003020
I/irsc_util( 354): Starting irsc tool
I/irsc_util( 354): Trying to open sec config file
I/installd( 348): installd firing up
I/DEBUG ( 341): debuggerd: Feb 16 2014 01:28:06
I/irsc_util( 354): file_parser Number of element :0
I/irsc_util( 354): file_parser Invalid Format or Comment - '/* IPC Security Config */
I/irsc_util( 354): '
I/irsc_util( 354): file_parser Number of element :0
I/irsc_util( 354): file_parser Invalid Format or Comment - '/* <GPS QMI Service ID - 16>:<GPS QMI Instance ID - all instances>:<Client Group ID> */
I/irsc_util( 354): '
I/irsc_util( 354): file_parser Number of element :4
I/irsc_util( 354): file_parser Number of element :0
I/irsc_util( 354): file_parser Invalid Format or Comment - '/* IPC Security Config */
I/irsc_util( 354): '
I/irsc_util( 354): file_parser Number of element :0
I/irsc_util( 354): file_parser Invalid Format or Comment - '/* <GPS QMI Service ID - 16>:<GPS QMI Instance ID - all instances>:<Client Group ID> */
I/irsc_util( 354): '
I/irsc_util( 354): file_parser Number of element :4
I/irsc_util( 354): Feed the sec config info to the router
I/irsc_util( 354): Num of entries:1
I/run-parts( 325): vm.dirty_ratio = 90
I/run-parts( 325): vm.oom_kill_allocating_task = 0
I/run-parts( 325): vm.swappiness = 0
I/run-parts( 325): vm.vfs_cache_pressure = 20
I/macloader( 356): Writing murata to /data/.cid.info
D/macloader( 356): Setting permissions on /data/.cid.info
--------- beginning of /dev/log/system
I/Vold ( 334): Vold 2.1 (the revenge) firing up
D/Vold ( 334): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 334): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/rmt_storage( 367): SoC HW id is 126
I/rmt_storage( 367): No EBR found
I/rmt_storage( 367): Error (-1) parsing MBR partitions
I/rmt_storage( 367): Registering modemst1: 0x4a /boot/modem_fs1
I/rmt_storage( 367): Registering modemst2: 0x4b /boot/modem_fs2
I/rmt_storage( 367): Registering fsg: 0x58 /boot/modem_fsg
I/rmt_storage( 367): Registering ssd: 0x5d ssd
D/Vold ( 334): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 334): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 65, PARTN 1
D/Vold ( 334): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/rmt_storage( 367): Registering fsc: 0xff /boot/modem_fsc
I/rmt_storage( 367): 5 GPT partitions found
I/run-parts( 325): /data/misc/wifi/wpa_supplicant.conf: No such file or directory
D/QSEECOMD: ( 337): qseecom listener services process entry PPID = 1
E/QSEECOMD: ( 337): Listener: index = 0, hierarchy = 0
E/QSEECOMD: ( 337): Listener: index = 1, hierarchy = 0
D/QSEECOMD: ( 337): Parent qseecom daemon process paused!!
D/QSEECOMD: ( 416): qseecom listener service threads starting!!!
D/QSEECOMD: ( 416): Total listener services to start = 4
E/QSEECOMD: ( 416): Listener: index = 0, hierarchy = 1
E/QSEECOMD: ( 416): Listener: index = 1, hierarchy = 1
E/QSEECOMD: ( 416): Listener: index = 2, hierarchy = 1
I/SELinuxLabel( 415): data is mis-labeled, fixing...
D/QSEECOMD: ( 416): Init dlopen(libdrmtime.so, RTLD_NOW) succeeds
D/QSEECOMD: ( 416): Init::Init dlsym(g_FSHandle atime_start) succeeds
D/QSEECOMAPI: ( 416): QSEECom_register_listener 11 sb_length = 0x5000
D/QSEECOMD: ( 416): Init atime_start ret = 0
D/QSEECOMD: ( 416): time services: Started (Listener ID = 11)
E/QSEECOMD: ( 416): Listener: index = 3, hierarchy = 1
D/QSEECOMD: ( 416): Init dlopen(libdrmfs.so, RTLD_NOW) succeeds
D/QSEECOMD: ( 416): Init::Init dlsym(g_FSHandle fs_start) succeeds
D/QSEECOMAPI: ( 416): QSEECom_register_listener 10 sb_length = 0x5000
D/QSEECOMD: ( 416): Init fs_start ret = 0
D/QSEECOMD: ( 416): file system services: Started (Listener ID = 10)
D/QSEECOMD: ( 416): QSEECOM DAEMON RUNNING
I/Netd ( 340): Netd 1.0 starting
I/SELinuxLabel( 428): /data relabel starting...
E/ThermalEngine( 338): Thermal daemon started
E/ThermalEngine( 338): devices_manager_init: Init
D/QC-time-services( 364): Daemon:genoff_pre_init::Base = 0
D/QC-time-services( 364): Daemon:ats_rtc_init: Time read from RTC -- year = 70, month = 0,day = 5
E/ThermalEngine( 338): Number of gpus :1
E/ThermalEngine( 338): Number of cpus :4
I/ThermalEngine( 338): vdd_rstr_init: Init KTM VDD RSTR enabled: 0
E/ThermalEngine( 338): sensors_manager_init: Init
E/ThermalEngine( 338): BCL sensors setup done.
E/ThermalEngine( 338): Loading config file for virtual sensor
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): parse_section: algo_type field not first field in section
E/ThermalEngine( 338): parse_section: algo_type field not first field in section
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): virtual_sensors_init: Error getting virtual sensors set
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Algo Type 'monitor'
E/ThermalEngine( 338): Threshold 0 Action[0] : shutdown
E/ThermalEngine( 338): Threshold 0 Action Info[0] : 70
E/ThermalEngine( 338): Disable section PID-CPU0
E/ThermalEngine( 338): Ignoring unknown field '1'
E/ThermalEngine( 338): Disable section PID-CPU1
E/ThermalEngine( 338): Ignoring unknown field '1'
E/ThermalEngine( 338): Disable section PID-CPU2
E/ThermalEngine( 338): Ignoring unknown field '1'
E/ThermalEngine( 338): Disable section PID-CPU3
E/ThermalEngine( 338): Ignoring unknown field '1'
E/ThermalEngine( 338): Disable section PID-POPMEM
E/ThermalEngine( 338): Ignoring unknown field '1'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): Algo Type 'ss'
E/ThermalEngine( 338): pid_algo_init: Entry Disabled PID-POPMEM.
E/ThermalEngine( 338): pid_algo_init: Entry Disabled PID-CPU3.
E/ThermalEngine( 338): pid_algo_init: Entry Disabled PID-CPU2.
E/ThermalEngine( 338): pid_algo_init: Entry Disabled PID-CPU1.
E/ThermalEngine( 338): pid_algo_init: Entry Disabled PID-CPU0.
E/ThermalEngine( 338): pid_algo_init: No PID's to configured.
E/ThermalEngine( 338): sensors_setup: tm_cnt 29
E/ThermalEngine( 338): sensors_setup: TM Id VDD_DIG_SWMODE_MONITOR-TSENS10 Sensor tsens_tz_sensor10 num_thresholds 1
E/ThermalEngine( 338): sensors_setup: TM Id VDD_DIG_SWMODE_MONITOR-TSENS9 Sensor tsens_tz_sensor9 num_thresholds 1
E/ThermalEngine( 338): sensors_setup: TM Id CPU1_MONITOR Sensor cpu1 num_thresholds 1
E/ThermalEngine( 338): sensors_setup: TM Id CPU0_MONITOR Sensor cpu0 num_thresholds 1
E/ThermalEngine( 338): enable_threshold: tsens_tz_sensor10 (/sys/devices/virtual/thermal/thermal_zone10/trip_point_0_type)
E/ThermalEngine( 338): enable_threshold: tsens_tz_sensor8 (/sys/devices/virtual/thermal/thermal_zone8/trip_point_0_type)
I/ThermalEngine( 338): vdd_restrict_qmi_request: MODEM req level(0) is recorded and waiting for completing QMI registration
I/ThermalEngine( 338): vdd_restrict_qmi_request: ADSP req level(0) is recorded and waiting for completing QMI registration
I/ThermalEngine( 338): vdd_dig_sw_mode_ktm_disable_cb: write out 0
I/ThermalEngine( 338): hotplug_ktm_disable_cb: write out 0
E/ThermalEngine( 338): hotplug_ktm_disable_cb: CPU 1 Failed attempt to sync up with MP Desc.
E/ThermalEngine( 338): hotplug_ktm_disable_cb: CPU 2 Failed attempt to sync up with MP Desc.
E/ThermalEngine( 338): hotplug_ktm_disable_cb: CPU 3 Failed attempt to sync up with MP Desc.
D/QC-time-services( 364): Daemon:Value read from RTC seconds = 412594000
D/QC-time-services( 364): Daemon:genoff_modem_qmi_init: Initiallizing QMI
I/SurfaceFlinger( 343): SurfaceFlinger is starting
I/SurfaceFlinger( 343): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 343): loaded /vendor/lib/egl/libEGL_adreno.so
D/AudioDaemon( 366): Opening sound card state : /proc/asound/card0/state
D/AudioDaemon( 366): read for sound card state change before while
D/AudioDaemon( 366): sound card state file content: ONLINE
D/AudioDaemon( 366): * before while
E/AudioDaemon( 366): put cur_state to online
D/AudioDaemon( 366): cur_state=0, bootup_complete=0
E/AudioDaemon( 366): sound card up is deteced before while
E/AudioDaemon( 366): bootup_complete set to 1
D/AudioDaemon( 366): poll() for sound card state change
D/libEGL ( 343): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
I/mediaserver( 347): ServiceManager: 0x2a00b460
I/AudioFlinger( 347): Using default 3000 mSec as standby time.
E/MediaPlayerFactory( 347): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory( 347): Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found
I/CameraService( 347): CameraService started (pid=347)
D/libEGL ( 343): loaded /vendor/lib/egl/libGLESv2_adreno.so
I/SELinuxLabel( 530): /data relabel complete
I/SELinuxLabel( 533): /cache relabel starting...
I/Adreno-EGL( 343): <qeglDrvAPI_eglInitialize:385>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_KK_3.5_RB1.04.04.00.006.055_msm8974_KK_3.5_RB1__release_AU ()
I/Adreno-EGL( 343): OpenGL ES Shader Compiler Version: E031.24.00.02
I/Adreno-EGL( 343): Build Date: 12/11/13 Wed
I/Adreno-EGL( 343): Local Branch: mybranch2105762
I/Adreno-EGL( 343): Remote Branch: quic/kk_3.5_rb1.15
I/Adreno-EGL( 343): Local Patches: NONE
I/Adreno-EGL( 343): Reconstruct Branch: AU_LINUX_ANDROID_KK_3.5_RB1.04.04.00.006.055 + NOTHING
I/SELinuxLabel( 549): /cache relabel complete
I/qdutils ( 343): Right Split=0
W/qdcopybit( 343): open_copybit i = 0 surface_id=704702740
W/qdcopybit( 343): open_copybit i = 1 surface_id=704703032
W/qdcopybit( 343): open_copybit i = 2 surface_id=704703324
W/qdcopybit( 343): open_copybit i = 31 surface_id=704712048
W/qdcopybit( 343): open_copybit: 2 Plane YUV i=0 surface_id=704712640
W/qdcopybit( 343): open_copybit: 2 Plane YUV i=1 surface_id=704712936
W/qdcopybit( 343): open_copybit: 2 Plane YUV i=2 surface_id=704713232
W/qdcopybit( 343): open_copybit: 2 Plane YUV i=3 surface_id=704713528
W/qdcopybit( 343): open_copybit: 3 Plane YUV i=0 surface_id=704714120
D/qdhwcomposer( 343): int qhwc::adRead(): /sys/class/graphics/fb2/ad could not be opened : No such file or directory
I/qdhwcomposer( 343): Initializing Qualcomm Hardware Composer
I/qdhwcomposer( 343): MDP version: 500
I/SurfaceFlinger( 343): Using composer version 1.3
I/qdhwcomposer( 343): hwc_registerProcs
I/qdhwcomposer( 343): Initializing UEVENT Thread
I/qdhwcomposer( 343): Initializing VSYNC Thread
D/qdhwcomposer( 343): hwc_getDisplayAttributes disp = 0, width = 1080
D/qdhwcomposer( 343): hwc_getDisplayAttributes disp = 0, height = 1920
I/SurfaceFlinger( 343): EGL informations:
I/SurfaceFlinger( 343): vendor : Android
I/SurfaceFlinger( 343): version : 1.4 Android META-EGL
I/SurfaceFlinger( 343): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_create_context EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable
I/SurfaceFlinger( 343): Client API: OpenGL_ES
I/SurfaceFlinger( 343): EGLSurface: 8-8-8-8, config=0x5
I/qdhwcomposer( 343): vsync_loop: Reading vsync for dpy=0 from /sys/class/graphics/fb0/vsync_event
I/qdhwcomposer( 343): vsync_loop: Reading vsync for dpy=1 from /sys/class/graphics/fb1/vsync_event
E/mm-camera( 357): server_process_module_init:59, int mods
E/mm-camera-sensor( 357): module_sensor_init:4420 Enter
E/mm-camera-sensor( 357): sensor_init_probe:299 Done enumerating media entities
E/mm-camera-sensor( 357): sensor_init_probe:276 Done enumerating media devices
E/mm-camera-sensor( 357): [mm]read_EEPROM_header_version:385 EEPROM HEADER: core_version(0x44) resolution(0x31 0x33) isp(0x51) sensor_maker(0x53)
E/mm-camera-sensor( 357): [mm]read_EEPROM_header_version:387 EEPROM HEADER: year(0x47) month(0x46) iter(0x30 0x31)
E/mm-camera-sensor( 357): [mm]read_EEPROM_header_version:393 [FW_DBG] EEPROM HEADER: D 13 Q S G F 01 O A
E/mm-camera( 357): isp_util_gen_hws_caps: integrating kernel vfe is pending
I/SurfaceFlinger( 343): OpenGL ES informations:
I/SurfaceFlinger( 343): vendor : Qualcomm
I/SurfaceFlinger( 343): renderer : Adreno (TM) 330
I/SurfaceFlinger( 343): version : OpenGL ES 3.0 [email protected] [email protected] ([email protected])
I/SurfaceFlinger( 343): extensions: GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_robustness GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_depth_texture_cube_map GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_EXT_sRGB GL_EXT_sRGB_write_control GL_EXT_text
I/SurfaceFlinger( 343): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 343): GL_MAX_VIEWPORT_DIMS = 4096
E/mm-camera( 357): isp_resource_mgr_init: IN num_isps = 2
E/mm-camera( 357): isp_set_info: num_isps = 2
E/mm-camera( 357): cpp_module_init:49 name=cpp
D/SurfaceFlinger( 343): Screen acquired, type=0 flinger=0x2a007450
D/qdhwcomposer( 343): hwc_blank: Unblanking display: 0
D/qdhwcomposer( 343): hwc_blank: Done unblanking display: 0
E/qdhwcomposer( 343): hwc_vsync_control: vsync control failed. Dpy=0, enable=1 : Operation not supported on transport endpoint
E/SurfaceFlinger( 343): eventControl(0, 1) failed Operation not supported on transport endpoint
E/mm-camera( 357): cpp_hardware_load_firmware:359, cpphw->hwinfo.version = 0x10010000
D/qdutils ( 343): DEBUG_CALC_FPS: 0
D/qdutils ( 343): period: 10
D/qdutils ( 343): ignorethresh_us: 500000
D/libEGL ( 605): loaded /vendor/lib/egl/libEGL_adreno.so
D/libEGL ( 605): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D/AndroidRuntime( 344):
D/AndroidRuntime( 344): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/libEGL ( 605): loaded /vendor/lib/egl/libGLESv2_adreno.so
D/AndroidRuntime( 344): CheckJNI is OFF
I/Adreno-EGL( 605): <qeglDrvAPI_eglInitialize:385>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_KK_3.5_RB1.04.04.00.006.055_msm8974_KK_3.5_RB1__release_AU ()
I/Adreno-EGL( 605): OpenGL ES Shader Compiler Version: E031.24.00.02
I/Adreno-EGL( 605): Build Date: 12/11/13 Wed
I/Adreno-EGL( 605): Local Branch: mybranch2105762
I/Adreno-EGL( 605): Remote Branch: quic/kk_3.5_rb1.15
I/Adreno-EGL( 605): Local Patches: NONE
I/Adreno-EGL( 605): Reconstruct Branch: AU_LINUX_ANDROID_KK_3.5_RB1.04.04.00.006.055 + NOTHING
E/mm-camera( 357): cpp_module_init:90: info: CPP module_init successful
E/mm-camera( 357): c2d_module_init:28 name=c2d
I/CameraService( 347): Loaded "QCamera Module" camera module
I/AudioPolicyManagerBase( 347): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
D/audio_hw_primary( 347): adev_open: enter
D/dalvikvm( 344): Unable to stat classpath element '/system/framework/qcom.fmradio.jar'
D/dalvikvm( 344): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 344): Added shared lib libjavacore.so 0x0
D/dalvikvm( 344): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 344): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 344): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
D/dalvikvm( 344): Note: class Landroid/app/ActivityManagerNative; has 179 unimplemented (abstract) methods
E/audio_route( 347): value id out of range for mixer ctl 'Voice Tx Mute'
E/audio_route( 347): Control 'SLIMBUS_0_RX Port Mixer INT_BT_SCO_TX' doesn't exist - skipping
E
E/audio_route( 347): Control 'QCHAT_Tx Mixer SLIM_0_TX_QCHAT' doesn't exist - skipping
E/QMI_FW ( 364): QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-1
E/QMI_FW ( 364): QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-1
E/QMI_FW ( 364): QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-1
E/QMI_FW ( 364): QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-1
E/QMI_FW ( 364): QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-1
E/QMI_FW ( 364): QMUXD: WARNING qmi_qmux_if_pwr_up_init failed! rc=-1
E/QC-time-services( 364): Daemon:genoff_modem_qmi_init: qmi_client_get_service_list returned -2num_services 0
E/audio_route( 347): Control 'RX4 DSM MUX' doesn't exist - skipping
E/audio_route( 347): Control 'RX6 DSM MUX' doesn't exist - skipping
E/audio_route( 347): Control 'MAD Input' doesn't exist - skipping
D/msm8974_platform( 347): platform_init: Opened sound card:0
E/msm8974_platform( 347): platform_init: Could not find the symbol acdb_loader_reload_vocvoltable from libacdbloader.so
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_INITIALIZE_V2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/Bluetooth_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/General_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/Global_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/Handset_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/Hdmi_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/Headset_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ ( 347): [ACDB Command]->SW Minor/Major version mismatch warning /etc/Speaker_cal.acdb
D/ ( 347): [ACDB Command]->ACDB Sw Major = 2, ACDB Sw Minor = 1
D/ ( 347): [ACDB Command]->ACDB File Major = 1, ACDB File Minor = 2
D/ACDB-LOADER( 347): ACDB -> ACPH INIT
D/ ( 347): [ACPH]->Online service registered with ACPH
D/ ( 347): [ACPH]->ACPH init success
D/ACDB-LOADER( 347): ACDB -> RTAC INIT
D/ ( 347): [ACPH]->DSP RTC service registered with ACPH
D/ACDB-LOADER( 347): ACDB -> ADIE RTAC INIT
D/ ( 347): [ACPH]->ADIE RTC service registered with ACPH
D/ACDB-LOADER( 347): No existing ION info in ACDB driver
D/ACDB-LOADER( 347): ACDB -> ION_IOC_ALLOC
D/ACDB-LOADER( 347): ACDB -> ION_IOC_SHARE
D/ACDB-LOADER( 347): ACDB -> MMAP ADDR
D/ACDB-LOADER( 347): ACDB -> register MEM to ACDB driver: 0xb4f93000
I/rmt_storage( 367): rmt_storage_connect_cb: clnt_h=0x1 conn_h=0x2a006fd8
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fs1: clnt_h=0x1: req_h=0x1 msg_id=1: Client found
D/ACDB-LOADER( 347): ACDB -> send_asm_topology
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fs1: clnt_h=0x1: req_h=0x1 msg_id=1: Send response: res=0 err=0
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fs1: clnt_h=0x1 Worker thread started
I/rmt_storage( 367): wake lock name: rmt_storage_704672024, name creation success: 21
D/ACDB-LOADER( 347): ACDB -> send_adm_custom_topology
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_AUDIO_COPP_TOPOLOGIES
D/ACDB-LOADER( 347): ACDB -> AUDIO_SET_ADM_CUSTOM_TOPOLOGY
D/ACDB-LOADER( 347): ACDB -> send_asm_custom_topology
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_AUDIO_POPP_TOPOLOGIES
D/ ( 347): ACDBFILE_MGR: Property for the pid 00012E48 not found
D/ ( 347): ACDB_COMMAND: Failed to fetch the property info for pid 00012E48
E/ACDB-LOADER( 347): Error: ACDB get asm topologies returned = -18
D/ACDB-LOADER( 347): ACDB -> AUDIO_SET_ASM_CUSTOM_TOPOLOGY
D/ACDB-LOADER( 347): send mbhc data
I/rmt_storage( 367): rmt_storage_connect_cb: clnt_h=0x2 conn_h=0x2a007030
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fs2: clnt_h=0x2: req_h=0x2 msg_id=1: Client found
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fs2: clnt_h=0x2: req_h=0x2 msg_id=1: Send response: res=0 err=0
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fs2: clnt_h=0x2 Worker thread started
I/rmt_storage( 367): wake lock name: rmt_storage_704672872, name creation success: 21
I/rmt_storage( 367): rmt_storage_connect_cb: clnt_h=0x3 conn_h=0x2a007088
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fsg: clnt_h=0x3: req_h=0x3 msg_id=1: Client found
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fsg: clnt_h=0x3: req_h=0x3 msg_id=1: Send response: res=0 err=0
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fsg: clnt_h=0x3 Worker thread started
I/rmt_storage( 367): wake lock name: rmt_storage_704673456, name creation success: 21
I/rmt_storage( 367): rmt_storage_connect_cb: clnt_h=0x4 conn_h=0x2a0070e0
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fsc: clnt_h=0x4: req_h=0x4 msg_id=1: Client found
I/rmt_storage( 367): rmt_storage_open_cb: /boot/modem_fsc: clnt_h=0x4: req_h=0x4 msg_id=1: Send response: res=0 err=0
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fsc: clnt_h=0x4 Worker thread started
I/rmt_storage( 367): wake lock name: rmt_storage_704674040, name creation success: 21
I/rmt_storage( 367): rmt_storage_alloc_buff_cb: /boot/modem_fs1: clnt_h=0x1: req_h=0x5 msg_id=4: Alloc request received: Size: 1572864
I/rmt_storage( 367): rmt_storage_alloc_buff_cb: /boot/modem_fs1: clnt_h=0x1: req_h=0x5 msg_id=4: Send response: res=0 err=0
I/rmt_storage( 367): rmt_storage_rw_iovec_cb: /boot/modem_fsg: clnt_h=0x3: req_h=0x6 msg_id=3: R/W request received
I/rmt_storage( 367): Shared mem address set to 0xb688d000
I/rmt_storage( 367): wakelock acquired: 1, error no: 2
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fsg: clnt_h=0x3 Unblock worker thread (th_id: 704673456)
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fsg: clnt_h=0x3: req_h=0x6 msg_id=3: Bytes read = 512
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fsg: clnt_h=0x3: req_h=0x6 msg_id=3: Send response: res=0 err=0
I/rmt_storage( 367): rmt_storage_client_thread: /boot/modem_fsg: clnt_h=0x3 About to block rmt_storage client thread (th_id: 704673456) wakelock released: 1, error no: 0
I/rmt_storage( 367):
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 0000001A
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 0000001B
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 0000001C
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 0000001D
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 0000001E
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 0000001F
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ ( 347): Failed to fetch the lookup information of the device 00000067
E/ACDB-LOADER( 347): Error: ACDB ANC returned = -1
D/ACDB-LOADER( 347): ACDB -> init done!
D/platform_info( 347): platform_info_init: Failed to open /system/etc/audio_platform_info.xml, using defaults.
D/audio_hw_spkr_prot( 347): audio_extn_spkr_prot_init: Initialize speaker protection module
D/audio_hw_spkr_prot( 347): audio_extn_spkr_prot_init: Speaker protection disabled
I/AudioFlinger( 347): loadHwModule() Loaded primary audio interface from QCOM Audio HAL (audio) handle 1
I/AudioFlinger( 347): HAL output buffer size 960 frames, normal mix buffer size 960 frames
I/AudioMixer( 347): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger( 347): Using module 1 has the primary audio interface
I/AudioFlinger( 347): AudioFlinger's thread 0xb4f52008 ready to run
W/AudioFlinger( 347): Thread AudioOut_2 cannot connect to the power manager service
D/audio_hw_primary( 347): out_set_parameters: enter: usecase(0: deep-buffer-playback) kvpairs: routing=2
D/audio_hw_extn( 347): audio_extn_set_anc_parameters: anc_enabled:0
W/AudioFlinger( 347): Thread AudioOut_2 cannot connect to the power manager service
W/AudioFlinger( 347): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger( 347): no wake lock to update!
I/AudioFlinger( 347): HAL output buffer size 240 frames, normal mix buffer size 960 frames
I/AudioMixer( 347): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
E/MonoPipe( 347): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
I/SamplingProfilerIntegration( 344): Profiling disabled.
I/Zygote ( 344): Preloading classes...
I/rmt_storage( 367): rmt_storage_disconnect_cb: clnt_h=0x0x1 conn_h=0x0x2a006fd8
I/rmt_storage( 367): rmt_storage_disconnect_cb: clnt_h=0x0x2 conn_h=0x0x2a007030
I/rmt_storage( 367): rmt_storage_disconnect_cb: clnt_h=0x0x3 conn_h=0x0x2a007088
I/rmt_storage( 367): rmt_storage_disconnect_cb: clnt_h=0x0x4 conn_h=0x0x2a0070e0
D/TextLayoutCache( 344): Using debug level = 0 - Debug Enabled = 0
I/dalvikvm( 344): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
D/MtpDeviceJNI( 344): register_android_mtp_MtpDevice
I/dalvikvm( 344): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 344): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 344): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
D/MDnsDS ( 340): MDnsSdListener::Hander starting up
D/MDnsDS ( 340): MDnsSdListener starting to monitor
D/MDnsDS ( 340): Going to poll with pollCount 1
I/LibraryLoader( 344): loading: webviewchromium
I/LibraryLoader( 344): loaded: webviewchromium