Looking for working USB borescope recommendation.. - Nexus 7 (2013) General

I'm wanting to add a borescope to my Nexus and realize that not all of them are compatible. I've purchased a USB model that is not compatible even after a jailbreak so I was hoping someone has had the opportunity to test any that are compatible?
I purchased the following:
ebay item: 141214106067
and was looking at the following since it appears to have a USB2.0 UVC interface
ebay item: 111107144638
Any help or guidance would be appreciated..
VB,

I managed to pry out the following information from the command line
#dmesg | grep video
Linux Video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
uvcvideo: Found UVC 1.00 device USB camera (0bda:5801)
I believe this means the my USB camera is already using the UVC driver in attempt to work properly..
Anyone have any suggestions on how to possibly get this to work?

Actually looks like its supported at Linux UVC
0bda:5801 Realtek 2SF022 (HP Pavillon DV7 4151SG notebooks) Realtek

Continuing to dig and finding this in dmesg- firewalled???
130|[email protected]:/ # dmesg | grep video
<6>[ 7539.970855] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<6>[ 8885.732574] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<5>[ 8917.306060] type=1400 audit(1398128520.701:44): avc: denied { getattr } for pid=5504 comm="ra.simplewebcam" path="/dev/video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<6>[ 9269.163787] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<6>[ 9537.000366] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<5>[ 9575.854766] type=1400 audit(1398129235.463:47): avc: denied { getattr } for pid=6112 comm="ra.simplewebcam" path="/dev/video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<6>[ 9686.335266] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<6>[ 9902.219024] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)
<5>[ 9994.940917] type=1400 audit(1398129654.551:48): avc: denied { read write } for pid=6406 comm="ra.simplewebcam" name="video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<5>[ 9994.941192] type=1400 audit(1398129654.551:49): avc: denied { open } for pid=6406 comm="ra.simplewebcam" name="video0" dev="tmpfs" ino=7536 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:video_device:s0 tclass=chr_file
<6>[10049.950195] uvcvideo: Found UVC 1.00 device USB Camera (0bda:5801)

I've temporarily disabled SELinux.. still no luck but the avc: denied errors are gone.
It looks like there is a device conflict as it seems to not be able to open the /dev/video0?
Anyone have any thoughts?
D/dalvikvm( 2962): Trying to load lib /data/app-lib/com.camera.simplewebcam-1/libImageProc.so 0x41ea2f78
D/dalvikvm( 2962): Added shared lib /data/app-lib/com.camera.simplewebcam-1/libImageProc.so 0x41ea2f78
D/dalvikvm( 2962): No JNI_OnLoad found in /data/app-lib/com.camera.simplewebcam-1/libImageProc.so 0x41ea2f78, skipping init
D/dalvikvm( 2962): GC_FOR_ALLOC freed 71K, 2% free 9181K/9284K, paused 17ms, total 17ms
I/dalvikvm-heap( 2962): Grow heap (frag case) to 10.166MB for 1228816-byte allocation
D/dalvikvm( 2962): GC_FOR_ALLOC freed 1K, 2% free 10380K/10488K, paused 14ms, total 14ms
E/TEST ( 2962): Cannot open '/dev/video0': 16, Device or resource busy
D/dalvikvm( 2962): GC_CONCURRENT freed <1K, 2% free 10381K/10488K, paused 3ms+2ms, total 18ms
I/ActivityManager( 590): Displayed com.camera.simplewebcam/.Main: +211ms
I'm guessing this has something to do with the 2 built in camera's... not sure if they can be temporarily disabled or somehow mount the USB camera on another /dev maybe like /dev/video3?

making very little progress but I think I know what's going on.. the USB device is being loaded as /dev/video3 and not as /dev/video0 which I assume is what most applications are looking for.
This was me plugging and unplugging the camera. I believe this also tells me that the kernel already is set for the camera.
[email protected]:/ # ls -l /dev/v*
crw-rw---- system camera 81, 1 2014-04-22 21:54 v4l-subdev0
crw-rw---- system camera 81, 2 2014-04-22 21:54 v4l-subdev1
crw-rw---- system camera 81, 3 2014-04-22 21:54 v4l-subdev2
crw-rw---- system camera 81, 4 2014-04-22 21:54 v4l-subdev3
crw-rw---- system camera 81, 5 2014-04-22 21:54 v4l-subdev4
crw-rw---- system camera 81, 7 2014-04-22 21:54 v4l-subdev5
crw-rw---- system camera 81, 9 2014-04-22 21:54 v4l-subdev6
crw-rw---- system camera 81, 10 2014-04-22 21:54 v4l-subdev7
crw-rw---- system camera 81, 11 2014-04-22 21:54 v4l-subdev8
crw-rw---- system camera 81, 12 2014-04-22 21:54 v4l-subdev9
crw------- root root 7, 0 2014-04-22 21:54 vcs
crw------- root root 7, 1 2014-04-22 21:54 vcs1
crw------- root root 7, 128 2014-04-22 21:54 vcsa
crw------- root root 7, 129 2014-04-22 21:54 vcsa1
crw------- root root 10, 127 2014-04-22 21:54 vga_arbiter
crw-rw---- system camera 81, 0 2014-04-22 21:54 video0
crw-rw---- system camera 81, 6 2014-04-22 21:54 video1
crw-rw---- system camera 81, 8 2014-04-22 21:54 video2
[email protected]:/ # ls -l /dev/v*
crw-rw---- system camera 81, 1 2014-04-22 21:54 v4l-subdev0
crw-rw---- system camera 81, 2 2014-04-22 21:54 v4l-subdev1
crw-rw---- system camera 81, 3 2014-04-22 21:54 v4l-subdev2
crw-rw---- system camera 81, 4 2014-04-22 21:54 v4l-subdev3
crw-rw---- system camera 81, 5 2014-04-22 21:54 v4l-subdev4
crw-rw---- system camera 81, 7 2014-04-22 21:54 v4l-subdev5
crw-rw---- system camera 81, 9 2014-04-22 21:54 v4l-subdev6
crw-rw---- system camera 81, 10 2014-04-22 21:54 v4l-subdev7
crw-rw---- system camera 81, 11 2014-04-22 21:54 v4l-subdev8
crw-rw---- system camera 81, 12 2014-04-22 21:54 v4l-subdev9
crw------- root root 7, 0 2014-04-22 21:54 vcs
crw------- root root 7, 1 2014-04-22 21:54 vcs1
crw------- root root 7, 128 2014-04-22 21:54 vcsa
crw------- root root 7, 129 2014-04-22 21:54 vcsa1
crw------- root root 10, 127 2014-04-22 21:54 vga_arbiter
crw-rw---- system camera 81, 0 2014-04-22 21:54 video0
crw-rw---- system camera 81, 6 2014-04-22 21:54 video1
crw-rw---- system camera 81, 8 2014-04-22 21:54 video2
crw-rw---- system camera 81, 14 2014-04-22 21:56 video3
[email protected]:/ # ls -l /dev/v*
crw-rw---- system camera 81, 1 2014-04-22 21:54 v4l-subdev0
crw-rw---- system camera 81, 2 2014-04-22 21:54 v4l-subdev1
crw-rw---- system camera 81, 3 2014-04-22 21:54 v4l-subdev2
crw-rw---- system camera 81, 4 2014-04-22 21:54 v4l-subdev3
crw-rw---- system camera 81, 5 2014-04-22 21:54 v4l-subdev4
crw-rw---- system camera 81, 7 2014-04-22 21:54 v4l-subdev5
crw-rw---- system camera 81, 9 2014-04-22 21:54 v4l-subdev6
crw-rw---- system camera 81, 10 2014-04-22 21:54 v4l-subdev7
crw-rw---- system camera 81, 11 2014-04-22 21:54 v4l-subdev8
crw-rw---- system camera 81, 12 2014-04-22 21:54 v4l-subdev9
crw------- root root 7, 0 2014-04-22 21:54 vcs
crw------- root root 7, 1 2014-04-22 21:54 vcs1
crw------- root root 7, 128 2014-04-22 21:54 vcsa
crw------- root root 7, 129 2014-04-22 21:54 vcsa1
crw------- root root 10, 127 2014-04-22 21:54 vga_arbiter
crw-rw---- system camera 81, 0 2014-04-22 21:54 video0
crw-rw---- system camera 81, 6 2014-04-22 21:54 video1
crw-rw---- system camera 81, 8 2014-04-22 21:54 video2
[email protected]:/ #

Found an interesting thread where I believe the developer is trying to make the USB camera /dev/video0... I'd post the URL but I've only posted 7 times to the forum.
sorry... gonna post a few more time to meet the 10 post limit to post URL's... and I have to wait 5 minutes between posts.. a bit on the paranoid side around here..

Gonna try flashing a zip file.. of a potential fix?

Backing up my device.. post #9

Device done backing up..

Here is the URL:
http://forum.xda-developers.com/showthread.php?t=2100452&page=4
Anyone know if this is still a working solution?

Wow.. no suggestions or reply's to this thread. Huge bummer..
Still digging around and seeing some noise about using the /system/etc/nvcamera.conf file however that file is not on my Nexus 7? I trieed creating one but not sure its being read.. maybe it is. Anyway, it didn't work..
Need to make /system directory read/write:
# mount -o rw,remount /system
# vi /etc/nvcamera.conf# format, cameraName=device,direction,orientation,type
This is the file before mods
# type can be 'stereo' for stereo capable, 'mono' for not stereo capable,
# 'usb' to enable searching for a usb device and where to put it in the list
# if found. Lines must be shorter then 256 characters
version=1
camera0=/dev/ov5640,back,0,mono
#camera1=/dev/ov5650,back,0,mono // 2nd camera for stereo once supported
camera1=/dev/mi1040,front,0,mono
#camera4=/dev/ov5650,back,0,stereo // virtual stereo device once supported
Change this line:
camera0=/dev/ov5640,back,0,mono
to:
camera0=/dev/ov5640,front,0,mono
And this line:
camera1=/dev/mi1040,front,0,mono
to:
camera1=/dev/mi1040,back,0,mono
Click to expand...
Click to collapse
I could really use some help with this.. anyone?

Just wanted to close the loop and let the forum know that I got my generic borescope working on my Nexus via the USB port, I did have to root it but might not have had to assuming I could give permissions of /ueventd.xxxx.rc set to 0666. SInce its rooted its a moot point..
I also modified the source code for simplewebcam (https://bitbucket.org/droidperception/simplewebcam/overview)
VB,

Related

[Q] Android Wallpaper Service on Nook Simple Touch (the removal of)

Hi all,
On a Nook Simple Touch (E-ink reader), there is a service I am unable to locate and delete.
The details:
Code:
Label: Android System
Name: system
Flags: PERSISTENT, SYSTEM
Clients: I
Package: android
Pack. label: Wallpaper
Pack. details: android/com.android.internal.service.wallpaper.ImageWallpaper
While I accept that the system requires resources, this service degrades the performance of the e-reader every now and then to irritatingly slow levels. When it is persistently using CPU time, the screen is very noticeably unresponsive, perhaps once a day or so.
grep reports that this service is a "Default built-in wallpaper that simply shows a static image. "
Added to the rather odd fact that I do not recall having a wallpaper beyond a sheet of white, which I would gladly sacrifice in return for a reliably responsive system.
I additionally don't know how a wallpaper service takes almost more memory than my web browser.
I have been unable to locate documentation on this service, what it does, where it resides and how to disable it.
If anyone could provide any insight on this service, it would be greatly appreciated.
Thanks
(tl;dr: Android's imagewallpaper service uses more RAM/CPU than a web browser, and I would like to kill it or understand why)
The service you mention is the default and very simple implementation of a WallpaperService.
Basically, it gets an intent to use a drawable as a background and draws it when needed.
It really should not be using any CPU or memory.
But it is, and using 10-20% of CPU and about a quarter of my RAM.
How would one go about diagnosing the root cause, and subsequently disabling it?
I tried 'pm disable servicename' but it only shifted the exact same CPU and RAM usage to the Google checkin service, and after I disabled that, to the Android system itself.
What might be causing this?
Where are you getting these statistics from?
Are you getting these statistics over ADB without an app running?
What are you using for a launcher?
Do you have any widgets on the desktop?
What does logcat say?
What does ps say?
Renate NST said:
Where are you getting these statistics from?
Click to expand...
Click to collapse
From the task manager built into Relaunch (nookdevs . com/ReLaunch), a barebones file manager/launcher without animations nor wallpaper.
Renate NST said:
Are you getting these statistics over ADB without an app running?
Click to expand...
Click to collapse
This is persistent over a week-long period of regular usage, as in, the resource consumption is constant regardless of what I am doing with the device (ie. fresh boot, web browser, reading).
I am unaware of the command to pull these statistics over ADB, though I suspect they will be similar.
Renate NST said:
What are you using for a launcher?
Click to expand...
Click to collapse
Relaunch (nookdevs . com/ReLaunch)
Written for the Nook, spartan feature set includes only file manager, basic app selection, wifi and battery information.
UI is simplistic, about what you'd expect from a file manager.
No animations.
Renate NST said:
Do you have any widgets on the desktop?
Click to expand...
Click to collapse
I have a listing of files in the current directory, beyond that nothing.
Renate NST said:
What does logcat say?
Click to expand...
Click to collapse
pastebin . com/j4EWAH0R
(Does not seem to have anything relevant, but the lagging problems only manifest themselves once a day or so.)
Renate NST said:
What does ps say?
Click to expand...
Click to collapse
Code:
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 552 248 c00d4988 0000d6cc S /init
root 2 0 0 0 c0078ee4 00000000 S kthreadd
root 3 2 0 0 c006925c 00000000 S ksoftirqd/0
root 4 2 0 0 c0090d48 00000000 S watchdog/0
root 5 2 0 0 c0075624 00000000 S events/0
root 6 2 0 0 c0075624 00000000 S khelper
root 12 2 0 0 c0075624 00000000 S suspend
root 127 2 0 0 c0075624 00000000 S kblockd/0
root 133 2 0 0 c0075624 00000000 S cqueue
root 143 2 0 0 c0075624 00000000 S twl4030-irqchip
root 144 2 0 0 c01a4b54 00000000 S twl4030-irq
root 170 2 0 0 c0075624 00000000 S omap2_mcspi
root 177 2 0 0 c0075624 00000000 S ksuspend_usbd
root 182 2 0 0 c01df4e4 00000000 S khubd
root 187 2 0 0 c0075624 00000000 S kmmcd
root 218 2 0 0 c00a573c 00000000 S pdflush
root 219 2 0 0 c00a573c 00000000 S pdflush
root 220 2 0 0 c00aa36c 00000000 S kswapd0
root 222 2 0 0 c0075624 00000000 S aio/0
root 230 2 0 0 c0075624 00000000 S epd-su/0
root 231 2 0 0 c0075624 00000000 S epd-dspck/0
root 371 2 0 0 c01f7818 00000000 S usb_mass_storag
root 385 2 0 0 c0075624 00000000 S zforce_wq
root 404 2 0 0 c0075624 00000000 S kondemand/0
root 416 2 0 0 c0075624 00000000 S hid_compat
root 485 2 0 0 c0215cb8 00000000 S mmcqd
root 716 2 0 0 c0215cb8 00000000 S mmcqd
root 720 2 0 0 c012dcdc 00000000 S kjournald
root 724 2 0 0 c012dcdc 00000000 S kjournald
root 725 1 700 276 c017e784 afe0c74c S /system/bin/sh
root 728 1 836 360 c00d4988 afe0cb14 S /system/bin/OMXPolicyManager
root 729 1 1900 360 ffffffff afe0c7ec S /system/bin/OMXResourceManager
root 734 1 216 64 c007dd0c 0001413c S /system/bin/bridged
system 735 1 764 264 c022646c afe0c9ec S /system/bin/servicemanager
root 737 1 816 400 c00d4988 afe0cb14 S /system/bin/vold
root 738 1 628 244 c0248ce4 afe0d37c S /system/bin/debuggerd
root 740 1 171004 8552 c00d4988 afe0cb14 S zygote
media 741 1 28516 1820 ffffffff afe0c9ec S /system/bin/mediaserver
bluetooth 742 1 1068 348 c00d4988 bef345b4 S /system/bin/dbusdaemon
root 743 1 756 328 c02ab6e8 afe0c74c S /system/bin/installd
keystore 746 1 1600 272 c0248ce4 afe0d37c S /system/bin/keystore
root 754 2 0 0 c0075624 00000000 S pvr_timer/0
root 782 2 0 0 c0075624 00000000 S pvr_workqueue
root 790 1 16832 12172 c016e7e8 afe0c74c S /system/bin/omap-edpd.elf
system 810 740 353844 54808 ffffffff afe0c9ec S system_server
root 820 2 0 0 c0075624 00000000 S pvr_display_syn
system 1003 740 258112 16916 ffffffff afe0d974 S com.android.settings
root 1008 2 0 0 c0075624 00000000 S sdio_wq
root 1015 2 0 0 c0075624 00000000 S tiwlan_wq
wifi 1032 1 1988 668 c00d4988 afe0cb14 S /system/bin/wpa_supplicant
app_2 1043 740 245724 12396 ffffffff afe0d974 S com.android.inputmethod.latin
app_3 1108 740 249840 11984 ffffffff afe0d974 S com.bn.cloud.svc:svc
system 1134 740 252272 18352 ffffffff afe0d974 S com.bn.devicemanager
system 1181 740 261060 10192 ffffffff afe0d974 S com.bn.waveformdownloader.svc
app_22 1201 740 249236 11240 ffffffff afe0d974 S com.android.vending
app_23 1558 740 308052 62676 ffffffff afe0d974 S com.UCMobile
app_29 1742 740 253832 15392 ffffffff afe0d974 S com.eink.norefresh
app_29 1756 1742 636 344 c0227544 afe0c74c S /system/bin/logcat
app_34 3105 740 259656 21560 ffffffff afe0d974 S com.harasoft.relaunch
dhcp 3173 1 304 164 c00d4988 0000ee6c S /system/bin/dhcpcd
app_30 3247 740 250176 15752 ffffffff afe0d974 S siir.es.adbWireless
root 3289 1 3372 184 ffffffff 0000f444 S /sbin/adbd
root 3369 3289 700 328 c017e784 afe0c74c S /system/bin/sh
root 3370 3289 636 344 c0227544 afe0c74c S logcat
app_17 3395 740 251488 11776 ffffffff afe0d974 S com.google.process.gapps
app_20 3413 740 244860 10292 ffffffff afe0d974 S com.android.setupwizard
root 3442 3289 700 328 c0066b58 afe0d61c S /system/bin/sh
root 3446 3442 844 340 00000000 afe0c74c R ps
Thanks
Edit: The PID/UID of the problematic process is 810/1000, which corresponds to "system 810 740 353844 54808 ffffffff afe0c9ec S system_server" from the ps result. I'm searching for insight on system_server.
Thanks, oops, sorry. I meant to say "top".
If you are running something that displays stats constantly it could be causing the wallpaper to constantly redraw.
Try a top from ADB, I'm sure that it will show zero usage.
You do have some wackiness going on in your logcat.
The UMSServer is going crazy. Is there a problem with your SD card?
Cross-referencing the PID with the processes reported in the task manager appears to point the issue at "system_server"
I'm not sure of the relevance of this, but it appears other Android devices have encountered issues with this particular process, with symptoms similar to mine.
However, their solutions (disabling GPS, replacing 'system_server' with its 2.3/4.0 counterpart) do not seem to apply, or cause more issues in this case.
The UMS messages only show up during physical USB connection, not during logcat when there is only a wireless connection, so it should be unrelated.
Could you clarify 'top'?
Your explanation makes sense, but it doesn't fully explain why the system slows to a crawl for about ten to twenty minutes out of the blue every now and then, seemingly caused by this process.
However, this may just be an unrelated factor.
I have, in my search for what 'system_server' does, discovered what happens if you replace said file with its 2.3/4.0 counterpart, should anyone wish to know.
Regular functions are unaffected, resource usage by the process is slightly diminished, however the tablet is unable to wake from sleep.
Additionally, removing most of the Google and B&N system services has somewhat circumvented the issue.
Thanks for your help, by the way, wouldn't have gotten past the whole figuring out what ImageWallpaper was without it.
I looked at the code for UMSServerActivity quickly and jumped to the conclusion that it was for mounting of the SD card.
It's actually the USB Mass Storage mounter.
I looked at logcat with a USB drive plugged in and I don't get any of those messages that you have.
From a shell in ADB:
Code:
# top
User 0%, System 0%, IOW 0%, IRQ 0%
User 3 + Nice 0 + Sys 1 + Idle 300 + IOW 0 + IRQ 0 + SIRQ 0 = 304
PID CPU% S #THR VSS RSS PCY UID Name
24453 0% R 1 876K 388K fg root top
2 0% S 1 0K 0K fg root kthreadd
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K unk root watchdog/0
and so on for another 50 lines...
There is a somewhat more pressing issue, is there a way to have Android save logcat data automatically regardless of system state and ADB connection?
Right now it only has ADB over wifi, which is terminated soon after the device sleeps.
The reason I ask is that right now if I leave it for too long it refuses to wake up, I assumed this was an issue with the replacement of "system_server" in "/system/bin/", as the reverting those changes initially did away with the problem, but it just manifested itself twice over the span of five minutes and I'd like to track
down the source.
Thanks
aliastral said:
I assumed this was an issue with the replacement of "system_server" in "/system/bin/"
Click to expand...
Click to collapse
Um, if you start indiscriminately swapping out system parts you are bound to cause wackiness.
For example: I've been having problems with "mediaserver".
It crashes all the time, but what is in /system/bin/mediaserver is just a stub that gets a bunch of processes running.
I wouldn't think of trying to swap out /system/bin/mediaserver.
The problem probably lies in a bug in one of the audio libraries in /system/lib

[Q] Sorry, your device does not have a back facing camera

I have just bought nexus 4 and I cannot switch to back camera.
Switch button is missing and when I try to switch to panorama mode there is a message:
"Sorry, your device does not have a back facing camera"
I have flashed google 4.2.2 and 4.3 factory images without luck.
Could anyone post the output of
adb shell ls /dev
please?
Mine is:
Code:
1|[email protected]:/ $ ls /dev
__properties__
alarm
android_adb
android_mbim
android_rndis_qc
apr_apps2
ashmem
bcm2079x-i2c
binder
block
bus
ccid_bulk
ccid_ctrl
console
cpu_dma_latency
cpuctl
device-mapper
diag
dsp_debug
efs_hsic_bridge
full
fuse
gemini0
genlock
graphics
gss
hsicctl0
hsicctl1
hsicctl2
hsicctl3
hw_random
i2c-0
i2c-3
i2c-4
input
ion
keychord
kgsl-3d0
kmem
kmsg
log
loop-control
mdm
media0
media1
mem
msm_aac
msm_aac_in
msm_acdb
msm_amrnb
msm_amrnb_in
msm_amrwb
msm_amrwb_in
msm_amrwbplus
msm_camera
msm_dsps
msm_evrc
msm_evrc_in
msm_mp3
msm_multi_aac
msm_qcelp
msm_qcelp_in
msm_rotator
msm_rtac
msm_sps
msm_vidc_dec
msm_vidc_dec_sec
msm_vidc_enc
msm_vidc_enc_sec
msm_vidc_reg
msm_wma
msm_wmapro
mtp_usb
network_latency
network_throughput
nmea
null
ppp
ptmx
pts
qmi0
qmi1
qmi2
qseecom
ramdump_dsps
ramdump_gss
ramdump_lpass
ramdump_riva
ramdump_smem-dsps
ramdump_smem-gss
random
rfkill
rmnet_mux_ctrl
rtc0
smd1
smd11
smd2
smd21
smd22
smd27
smd3
smd36
smd4
smd5
smd6
smd7
smd_cxm_qmi
smd_pkt_loopback
smd_sns_adsp
smd_sns_dsps
smdcnt_rev0
smdcnt_rev1
smdcnt_rev2
smdcnt_rev3
smdcnt_rev4
smdcnt_rev5
smdcnt_rev6
smdcnt_rev7
smdcnt_rev8
smdcntl0
smdcntl1
smdcntl2
smdcntl3
smdcntl4
smdcntl5
smdcntl6
smdcntl7
smdcntl8
smem_log
snd
socket
tgt
tty
tty0
tty1
tty10
tty11
tty12
tty13
tty14
tty15
tty16
tty17
tty18
tty19
tty2
tty20
tty21
tty22
tty23
tty24
tty25
tty26
tty27
tty28
tty29
tty3
tty30
tty31
tty32
tty33
tty34
tty35
tty36
tty37
tty38
tty39
tty4
tty40
tty41
tty42
tty43
tty44
tty45
tty46
tty47
tty48
tty49
tty5
tty50
tty51
tty52
tty53
tty54
tty55
tty56
tty57
tty58
tty59
tty6
tty60
tty61
tty62
tty63
tty7
tty8
tty9
ttyHSL0
tun
uhid
uinput
urandom
usb_accessory
usf1
v4l-subdev0
v4l-subdev1
v4l-subdev2
v4l-subdev3
v4l-subdev4
v4l-subdev5
v4l-subdev6
v4l-subdev7
v4l-subdev8
v4l-subdev9
vcs
vcs1
vcsa
vcsa1
video0
video1
video100
wcnss_wlan
xt_qtaguid
zero
[email protected]:/ $
Here is my dmesg output. I am running stock 4.3 rom.
I have the same issue with stock 4.2.2.
Could anyone help me, please?
Code:
pastebin.com/wcwms4qH
return it.
Yep. Just return it.
Thank you for your comments.
Actually I have bought it on an auction, however I have contacted seller and he has agreed to send me a new one.
theanacrusis said:
Thank you for your comments.
Actually I have bought it on an auction, however I have contacted seller and he has agreed to send me a new one.
Click to expand...
Click to collapse
Yeah, they must have opened it up.
Sent from my Nexus 4 using Tapatalk 4

[SOLVED] Note 3 SM-N900V DE "reboot nvbackup" Samsung's bomb

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

Can Someone please read this log and explain what is causing this drain

CPU Usage:29m 53s
CPU Usage (Background Only):29m 53s
Keep Awake:9m 39s
Bytes Sent:1.34 MB
Bytes Received:3.29 MB
App UID:0
Wakelock Detail
Included Packages
Included Processes
mdm_helper
file-storage
spi32765
boost_sync/0
boost_sync/1
boost_sync/2
boost_sync/3
msm_slim_qmi_cl
ipc_bridge
iptables
mmcqd/0rpmb
thermal-engine
app_process
ptt_socket_app
auditd
mdss_fb0
dumpstate
dhcpcd
fstrim
jbd2/loop0-8
jbd2/loop1-8
cfinteractive
wl_event_handle
mxhci_wq
kinteractivexup
external-modem_
bgcompact
kauditd
msm_thermal:fre
msm_thermal:the
smdexe
system
ngd_rx_thread1
at_distributor
zygote
daemonsu:0
ueventd
clatd-wlan0
daemonsu:10029
daemonsu:10176
daemonsu:10206
kswapd0
irq/440-fts_tou
debuggerd
loc_launcher
irq/416-msm_sdc
jbd2/mmcblk0p13
jbd2/mmcblk0p22
jbd2/mmcblk0p23
jbd2/mmcblk0p25
jbd2/mmcblk0p26
jbd2/mmcblk0p27
ks
sh
adbd
init
lmkd
netd
rild
spi0
sush
vold
irq/438-hrm_sen
/init
mpdecision
rcu_preempt
ddexe
hwrng
khubd
loop0
loop1
pkgld
qmuxd
rcu_sched
daemonsu:mount:master
busybox
time_daemon
irq/61-mxhci_hs
kthreadd
installd
kworker/0:0
kworker/0:1
kworker/0:2
kworker/0:3
kworker/0:4
kworker/0:5
kworker/1:0
kworker/1:1
kworker/1:2
kworker/1:3
kworker/1:4
kworker/1:5
kworker/2:0
kworker/2:1
kworker/2:2
kworker/2:3
kworker/2:4
kworker/3:0
kworker/3:1
kworker/3:2
kworker/3:3
kworker/3:4
healthd
ip6tables
daemonsu:10206:11753
daemonsu:10206:23328
daemonsu:10206:7551
daemonsu:10206:7748
hostapd
mmcqd/0
irq/602-SSP_Int
qseecomd
com.policydm
ksoftirqd/0
ksoftirqd/1
ksoftirqd/2
ksoftirqd/3
wpa_supplicant
migration/0
migration/1
migration/2
migration/3
irq/430-wcd9xxx
irq/645-wacom_i
ssp_sensorhub_t
edmaudit
daemonsu:master
irq/442-max7784
dnsmasq
irq/603-cypress
kworker/0:0H
kworker/0:1H
kworker/0:2H
kworker/0:3H
kworker/1:0H
kworker/1:1H
kworker/1:2H
kworker/2:0H
kworker/2:1H
kworker/2:2H
kworker/3:0H
kworker/3:1H
kworker/3:2H
kworker/u8:0
kworker/u8:1
kworker/u8:2
kworker/u8:3
kworker/u8:4
kworker/u8:5
kworker/u8:6
kworker/u8:7
kworker/u8:8
kworker/u8:9
kworker/u9:0
kworker/u8:10
kworker/u8:11
kworker/u8:12
kworker/u8:13
kworker/u8:14
kworker/u8:15
kworker/u8:16
kworker/u8:17
kworker/u8:18
kworker/u8:19
kworker/u8:20
kworker/u8:21
kworker/u8:22
kworker/u8:23
kworker/u8:24
kworker/u8:25
kworker/u8:26
kworker/u8:27
kworker/u8:28
kworker/u8:29
kworker/u8:30
kworker/u8:31
kworker/u8:32
kworker/u8:33
kworker/u8:34
kworker/u8:35
kworker/u8:36
kworker/u8:37
kworker/u8:38
kworker/u8:39
kworker/u8:40
kworker/u8:41
kworker/u8:42
kworker/u8:43
kworker/u8:44
kworker/u8:45
kworker/u8:46
kworker/u8:47
kworker/u8:48
kworker/u8:49
dumpsys
irq/170-msm_sdc

Samsung A205 FMP error

My samsung A205 fails to initialize FMP, the smatphone with the bootloader unlocked.
I tried various kernels like Rippler, Eureka and physwizz versions in TWRP.
And several Roms
I can always see the same error in dmesg:
Code:
[ 2560.206443] [2: mmc-cmdqd/0: 1799] exynos-fmp fmp: exynos_fmp_config: Fail to work fmp config due to fips in error.
[ 2560.206474] [2: mmc-cmdqd/0: 1799] mmc0: cmdq_prep_tran_desc: failed to configure crypto engine. ret(-1)
[ 2560.206485] [2: mmc-cmdqd/0: 1799] mmc0: cmdq_request: failed to setup tx desc: -1
[ 2560.206535] I[2: ksoftirqd/2: 22] mmc0: mmc_blk_cmdq_complete_rq: txfr error: -1
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206630] [2: kworker/2:2: 3612] =============== CQ RECOVERY START ======================
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206784] [2: kworker/2:2: 3612] [CQ] mmc0: SW RESET: 250
[ 2560.206794] [2: kworker/2:2: 3612] ----- cnt_recovery: 2743
[ 2560.206803] [2: kworker/2:2: 3612] ----- cnt_recovery_halt_pass: 2743
[ 2560.206812] [2: kworker/2:2: 3612] ----- cnt_recovery_halt_fail: 0
[ 2560.207055] [2: kworker/2:2: 3612] [CQ] mmc0:----- REQUEUE: tag 0 sector 32770, nr 2, retries 1
[ 2560.207181] [2: kworker/2:2: 3612] [CQ] mmc0: Enable after SW RESET
[ 2560.207198] [2: kworker/2:2: 3612]
While a well-functioning team shows:
Code:
[ 2.047718] [7: swapper/0: 1] exynos-fmp fmp: Exynos FMP Version: 1.3.2
[ 2.048316] [7: swapper/0: 1] exynos-fmp fmp: Found partno 32 for FMP test
[ 2.053900] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP aes-xts passed
[ 2.058193] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP aes-cbc passed
[ 2.058212] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP sha256 passed
[ 2.058246] [6: kworker/u16:3: 251] [SENSOR] stk3x3x_prox_cal: read_value = 10, (0xc0)
[ 2.058263] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for UFSFMP hmac(sha256) passed
[ 2.058269] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_fips_init: self-tests for FMP passed
[ 2.058751] [7: swapper/0: 1] FIPS(do_fmp_integrity_check): Integrity Check Passed
[ 2.058758] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_fips_init: integrity check for FMP passed
[ 2.058868] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_probe: Exynos FMP driver is proved
Documentation about FMP and FIPS:
Document 2016
Document 2020
What could i try?
because of that mistake cannot access the flash memory properly so it cannot start a full android system just start in TWRP.
tried compiling a kernel with FIPS options disabled, and it works I can see the capabilities of all partitions by starting TWRP in read-only mode. when I do it in read write mode it works unstable and restarts.
Exploring in the kernel source code I could see
arch/arm64/boot/dts/exynos/dtbo/exynos7885.dts
Code:
fmp_0: fmp {
compatible = "samsung,exynos-fmp";
exynos,host-type = "mmc";
exynos-host = <&dwmmc_0>;
exynos,block-type = "mmcblk0p";
exynos,fips-block_offset = <5>;
Mount the partition mmcblk0p5 (CPEFS) and I found it to be of type ext4 and empty.
Could someone give me a copy of that partition or show me what files it originally has inside?
Upgrade:
I discovered that the partition mmcblk0p4 (SEC EFS) is corrupt.
In mmcblk0p5 (CPEFS) I have these two hidden files:
Code:
.nv_core.bak
.nv_core.bak.md5
In mmcblk0p4 (SEC EFS) I have:
Code:
Battery
FactoryApp
TEE
adp_token
afc
cpk
imei
lost+found
lpm
lpm_boot.log
nfc
nxp
pfw_data
prov
prov_data
recovery
sec_efs
ssm
tee
umc
wv.keys
./Battery:
batt_capacity_max
./FactoryApp:
Sensorinfo
asoc
batt_after_manufactured
batt_cable_count
batt_discharge_level
batt_temp_charge
cisd_data
cisd_wc_data
factorymode
fdata
gyro_cal_data
hist_nv
keystr
max_current
max_temp
rtc_status
test_nv
./FactoryApp/Sensorinfo:
Accelerometer
Barometer
Gyroscope
Light
Magnetometer
Proximity
./TEE:
./adp_token:
./afc:
./cpk:
./imei:
factory.prop
mps_code.dat
omcnw_code.dat
./lost+found:
#27
#28
#29
#30
#31
#32
#33
#35
#36
#39
#40
#41
#42
#43
#44
#45
#46
#48
#49
#50
#51
#52
#53
#54
#55
#56
#57
#58
#59
#60
#61
#62
#63
#64
#65
#66
#67
#72
#74
#75
#76
#81
#82
#92
#93
#94
#95
#98
./lost+found/#40:
./lpm:
./nfc:
./nxp:
./pfw_data:
./prov:
issued.log
libdevkm.lock
./prov_data:
./recovery:
extra_history
history
prev_tmp_recovery.log
./sec_efs:
!SVC
SVC
SettingsBackup.json
nfc
skpm_FACTORY_OCF_ECC_P256
skpm_OTA_WB_TA_Downloader_RSA_2048
skpm_sk.dat
skpm_supported_list
ucm_ca_cert
./sec_efs/nfc:
./sec_efs/ucm_ca_cert:
./ssm:
./tee:
./umc:
BulkEnrollmentProfile
From what I see in lost+found I know I have lost files.
Unfortunately e2fsck does not repair my partition. I made a copy using dd and tried to repair that image from my Salckware on my desktop pc but without success.
It would be great if someone published a complete backup of the partitions obviously without MAC, IMEI, Serial Number, and Bluethoo address.
Who can help me:
I need a copy of the sec_efs partition
To do this, I had to run:
Code:
dd if=/dev/block/mmcblk0p4 of=/external_sd/secefs.img bs=4096
or at least the listing
Code:
ls -R -l > /external_sd/secefs.lst
I've been looking for a backup on the web for days but I haven't been successful so far. If you see any dumps of that paticion on the web, the download link will do me good.
Thanks
Cant you just install stock firmware using odin
physwizz said:
Cant you just install stock firmware using odin
Click to expand...
Click to collapse
Hello,
do not
This phone came with an error in which when turning on it showed a blue screen where it said update, then it failed and it was on screen:
Code:
E:[libfs_mgr]
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
and entered the recovery stock. where it said it couldn't mount / cache
if I put wipe cache it threw other errors and it was not corrected.
If I chose to start from the system it would be in a loop.
Initially it was with BIT 1 I updated it to BIT 8 using odin but the error persisted, I continued with the loop but (from what I search the web nobody solved it)
After a week of testing with different roms. On February 4, immediately took advantage of activating oem and unlocking the bootloader. When rebooting it did not turn on again but I was able to finish unlocking the bootloader and install TWRP 3.5 from physwizz.
When entering TWRP it does not allow multidisabler-samsung-3.1.zip
giving me an error. I could not mount the vendor partition nor any other. What's more, everything accused 0 MB
Using TWRP 3.3 in combination with the Eureka kernel I am able to mount some partitions.
After that I started to read the system logs to explore dmesg and there I realized that what is wrong is the FMP system
Reading the source code of the linux kernel I see that this works using the partition mmcblk0p5 (CPEFS).
Regarding CPEFS, note that in the PIT file it does not declare which file should be written to that partition.
Checking the other partitions I discover broken SEC_EFS.
I made a backup of what I could using tar and another with dd
and I tried to repair it using e2fsck but it was badly damaged
format it with the same original parameters and restore the files you rescue from backups.
Currently if I install an original rom with odin I get the same scenario.
loop and if I started I recovered the error:
Code:
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
NOTE: Now I am looking for a merge file. I understand what the factory uses. but I only found up to BIT 7 and my phone is in BIT 8.
Thank you
Excuse my english
sercari said:
Hello,
do not
This phone came with an error in which when turning on it showed a blue screen where it said update, then it failed and it showed on the screen:
Code:
E:[libfs_mgr]
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
and entered the recovery stock. where it said it couldn't mount / cache
if I put wipe cache it threw other errors and it was not corrected.
If I chose to start from the system it would be in a loop.
Initially it was with BIT 1 I updated it to BIT 8 using odin but the error persisted, I continued with the loop but (from what I search the web nobody solved it)
After a week of trying different roms. on february 4 it turned on immediately take advantage of activating oem and unlocking the bootloader. When rebooting it did not turn on again but I was able to finish unlocking the bootloader and install TWRP 3.5 from physwizz.
When entering TWRP it does not allow multidisabler-samsung-3.1.zip
giving me an error. I could not mount the vendor partition nor any other. What's more, everything accused 0 MB
Using TWRP 3.3 in combination with the Eureka kernel I managed to mount some partitions.
After that I started reading the system logs to explore dmesg and there I realized that what is wrong is the FMP system
Reading the source code of the linux kernel I see that this works using the partition mmcblk0p5 (CPEFS).
Regarding CPEFS, note that in the PIT file it does not declare which file should be written to that partition.
checking the other partitions I discover broken SEC_EFS.
I made a backup of what I pure using tar and another with dd
and I tried to repair it using e2fsck but it was badly damaged
Format it with the same original parameters and restore the files you rescue from the backups.
Currently if I install an original rom with odin I get the same scenario.
loop and if I started I recovered the error:
Code:
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
NOTE: Now I am looking for a merge file. I understand what the factory uses. but I only found up to BIT 7 and my phone is in BIT 8.
Thank you
Excuse my english
Click to expand...
Click to collapse
Go here
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
physwizz said:
Go here
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you, this guide is very good, unfortunately it does not solve my case. Disable_Dm-Verity_ForceEncrypt didn't work either.
The problem of my phone is with FMP = Flash Memory Protector
It fails to start FIPS because a file is probably missing or corrupt. I think that what would help me would be to see the list of files of those partitions to know their name and weight.
It would help me if you can create a text file on your external memory card and paste this content inside:
Code:
mkdir /secefs
mount /dev/block/mmcblk0p4 /secefs -o ro
cd /secefs
ls -a -R -l > /external_sd/secefs.lst
mkdir /efs
mount /dev/block/mmcblk0p3 /efs -o ro
cd /efs
ls -a -R -l > /external_sd/efs.lst
mkdir /cpefs
mount /dev/block/mmcblk0p5 /cpefs -o ro
cd /cpefs
ls -a -R -l > /external_sd/cpefs.lst
Or with this other you can make a backup:
Code:
dd if=/dev/block/mmcblk0p4 of=/external_sd/secefs.img
dd if=/dev/block/mmcblk0p3 of=/external_sd/efs.img
dd if=/dev/block/mmcblk0p5 of=/external_sd/cpefs.img
(suppose the file is called mkbl.txt)
finally run it from the TWRP terminal:
Code:
/external_sd/mkbl.txt
with that I would generate files in /external_sd/
NOTE: If you generate backup files, keep in mind that they contain IMEIs and addresses that are private to you. You could make a copy of the .img file, mount it from linux in a folder and edit the files that contain personal information. Or you can trust me and I can erase that personal information to make the files public.
On the other hand, in the case of the lists with ls, it does not include any personal information, only file names and weights
sercari said:
In mmcblk0p5 (CPEFS) I have these two hidden files:
Code:
.nv_core.bak
.nv_core.bak.md5
Click to expand...
Click to collapse
Confirmed cpefs that is mounted in / vendor / cpefs contains only these two files normally.
Code:
-rwx------ 1 radio radio 546304 feb 4 20:51 .nv_core.bak
-rwx------ 1 radio radio 32 feb 4 20:51 .nv_core.bak.md5
drwx------ 2 radio radio 4096 ene 1 2019 lost+found
I would only need to find out the content of the partition /dev/mccblk0p4 (sec_efs) which I think is not mounted anywhere when the system is running. for which it is necessary to mount it to be able to list its content. I wait if someone can help me.
Thanks to TBM13 from the telegram @Galaxy_A20_official group who shared with me the list of files and directories on their sec_efs partition.
Thanks to TOP who shared the list of files on his cpefs partition. Thanks to this I can continue investigating.
mmcblk0p4 (sec_efs):
Code:
.:
total 180
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 .
drwxr-xr-x 30 root root 0 2021-02-24 17:24 ..
drwxrwxr-x 2 radio system 4096 2019-01-01 12:00 Battery
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 FactoryApp
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 TEE
drwxr--r-- 2 system system 4096 2019-01-01 12:00 adp_token
drwx------ 2 system system 4096 2019-01-01 12:00 afc
drwxrwx--x 2 radio system 4096 2019-06-29 17:29 cpk
drwxrwxr-x 2 root radio 4096 2020-04-29 04:04 imei
drwx------ 2 root root 16384 2008-12-31 15:00 lost+found
drwxrwxr-x 2 system system 4096 2020-12-15 23:19 lpm
-rw-rw---- 1 root system 256 2020-12-15 23:19 lpm_boot.log
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 nfc
drwxrwx--- 2 system audio 4096 2019-01-01 12:00 nxp
drwxrw---- 2 oem_5279 oem_5279 4096 2019-01-01 12:00 pfw_data
drwxrwx--- 2 system system 4096 2019-06-29 17:22 prov
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 prov_data
drwxrwx--x 2 radio system 4096 2020-12-15 23:25 recovery
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 sec_efs
drwxrwx--- 2 system system 4096 2019-01-01 12:00 ssm
drwx------ 2 system system 4096 2019-01-01 12:00 tee
drwx------ 2 system system 4096 2019-08-31 01:46 umc
-rw-r--r-- 1 system system 168 2019-06-29 17:22 wv.keys
./Battery:
total 20
drwxrwxr-x 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-rw---- 1 system system 4 2021-02-21 02:58 batt_capacity_max
./FactoryApp:
total 132
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 system system 28 2019-06-29 08:37 HwParamBattQR
-rw------- 1 system system 4876 2019-06-29 17:22 HwParamData
-rw------- 1 system system 824 2019-06-29 17:22 HwPartInform
drwx------ 2 system system 4096 2019-01-01 12:00 Sensorinfo
-rw-r----- 1 system log 3 2019-01-01 12:00 asoc
-rwxr--r-- 1 system system 1 2019-01-01 12:00 baro_delta
-rw-r----- 1 system system 2 2020-12-15 22:43 batt_after_manufactured
-rw------- 1 system system 4 2021-02-23 14:39 batt_cable_count
-rw-r----- 1 system system 6 2020-12-15 22:57 batt_discharge_level
-rw------- 1 system system 62 2021-02-24 17:10 batt_temp_charge
-rw------- 1 system system 1 2019-01-01 12:00 cable_detect_count_octa
-rw-rw---- 1 system system 195 2021-02-23 15:31 cisd_data
-rw-rw---- 1 system system 20 2019-01-01 12:00 cisd_wc_data
-rwxr--r-- 1 system system 13 2019-01-01 12:00 control_no
-rw------- 1 system system 2 2020-11-28 14:37 earjack_count
-rwxr--r-- 1 system system 2 2019-06-29 17:22 factorymode
-rwxrwxr-x 1 system radio 4 2019-01-01 12:00 fdata
-rw------- 1 system system 30 2021-02-24 13:06 gyro_cal_data
-rwxrwxr-x 1 system radio 0 2018-12-31 17:00 hist_nv
-rwxr--r-- 1 system system 2 2019-06-29 17:22 keystr
-rw------- 1 system system 5 2019-10-12 21:38 max_current
-rw------- 1 system system 4 2020-01-19 20:53 max_temp
-rwxr--r-- 1 system system 5 2019-06-29 17:29 mdnie
-rw------- 1 system system 1 2019-06-29 17:29 mdnie_ver
-rwxr--r-- 1 system system 5 2019-01-01 12:00 prepay
-rw------- 1 system system 1 2019-06-29 17:22 rtc_status
-rwxr--r-- 1 system system 11 2019-06-29 17:22 serial_no
-rwxrwxr-x 1 system radio 2000 2018-12-31 17:00 test_nv
./FactoryApp/Sensorinfo:
total 40
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 ..
-rw------- 1 system system 21 2019-01-01 12:00 Accelerometer
-rw------- 1 system system 4 2019-01-01 12:00 Barometer
-rw------- 1 system system 17 2019-01-01 12:00 Gyroscope
-rw------- 1 system system 4 2019-01-01 12:00 Light
-rw------- 1 system system 19 2019-01-01 12:00 Magnetometer
-rw------- 1 system system 31 2019-01-01 12:00 Proximity
./TEE:
total 16
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./adp_token:
total 16
drwxr--r-- 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./afc:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./cpk:
total 20
drwxrwx--x 2 radio system 4096 2019-06-29 17:29 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-r--r-- 1 radio radio 920 2019-06-29 17:29 h2k.dat
./imei:
total 40
drwxrwxr-x 2 root radio 4096 2020-04-29 04:04 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 root root 96 2021-02-21 03:41 factory.prop
-rwxrwxr-x 1 radio system 3 2020-12-15 23:26 mps_code.dat
-rw-rw-r-- 1 radio root 3 2020-12-15 23:26 omcnw_code.dat
-rw-rw-r-- 1 radio root 3 2020-12-15 23:26 omcnw_code2.dat
-rwxrwxr-x 1 system radio 14 2019-06-29 17:22 prodcode.dat
-rw-rw-r-- 1 system system 4 2019-12-29 20:07 total_call_time
./lost+found:
total 28
drwx------ 2 root root 16384 2008-12-31 15:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./lpm:
total 20
drwxrwxr-x 2 system system 4096 2020-12-15 23:19 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-rw---- 1 root system 85 2020-12-15 23:19 lpm_info.log
./nfc:
total 16
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./nxp:
total 16
drwxrwx--- 2 system audio 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./pfw_data:
total 16
drwxrw---- 2 oem_5279 oem_5279 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./prov:
total 20
drwxrwx--- 2 system system 4096 2019-06-29 17:22 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw----r-- 1 system system 559 2019-09-01 00:28 issued.log
-rw-rw---- 1 system system 0 2019-01-01 12:00 libdevkm.lock
./prov_data:
total 16
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./recovery:
total 24
drwxrwx--x 2 radio system 4096 2020-12-15 23:25 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 root root 257 2020-12-15 23:25 extra_history
-rw------- 1 root root 2529 2020-12-15 23:25 history
./sec_efs:
total 76
-rw------- 1 system system 569 2020-12-15 23:12 !SVC
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rwx------ 1 root radio 0 2019-06-29 17:07 .ffw
-rw------- 1 system system 569 2020-12-15 23:12 SVC
-rw------- 1 system system 6655 2020-12-15 23:32 SettingsBackup.json
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 nfc
-rw------- 1 system system 1517 2019-06-29 17:22 skpm_FACTORY_OCF_ECC_P256
-rw------- 1 system system 983 2019-09-01 00:29 skpm_OTA_WB_FIDO_Bound_FP_ECC_P256
-rw------- 1 system system 4104 2019-08-31 02:43 skpm_OTA_WB_TA_Downloader_RSA_2048
-rw------- 1 system system 3941 2019-08-31 02:43 skpm_sk.dat
-rw------- 1 system system 4711 2019-09-01 00:29 skpm_supported_list
drwx------ 2 system system 4096 2019-01-01 12:00 ucm_ca_cert
./sec_efs/nfc:
total 16
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 .
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 ..
./sec_efs/ucm_ca_cert:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 ..
./ssm:
total 16
drwxrwx--- 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./tee:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./umc:
total 20
drwx------ 2 system system 4096 2019-08-31 01:46 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 system system 1 2019-08-31 01:46 BulkEnrollmentProfile
Observing the list compare weight, permissions, owner and group of each file in /lost+found and I was able to deduce which file was and give it the corresponding location and name.
The only file I am missing is: /sec_efs/skpm_OTA_WB_FIDO_Bound_FP_ECC_P256
Someone has any idea about this file, apparently it is a key but I don't know if the phone should generate it automatically or how to get it.
I add that you do not know that the skpm_sk.dat file is blank. if I have it with a hex editor it is full of zeros
Thanks
Finally and mysteriously I boot into twrp allowing me to see all the partitions. (Only TWRP with full memory access would not start the system) Take advantage and I made a copy from partition 1 to 25 to and 31. Unfortunately I discovered that I have the partitions boot0, boot1, boot3, m9kefs, m9kefs2, m9kefs3, nad_fw, nad_refer blank.
UPDATE:
1- Get a copy of m9kefs1, 2 and 3 and I have them ok.

Categories

Resources