[Q] Device encryption not starting - Verizon Samsung Galaxy S III

[Q] Device encryption not starting - Verizon Samsung Galaxy S III

Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
I/MountService( 872): encrypting storage...
I/power ( 872): *** release_dvfs_lock : lockType : 1
D/SSRMv2:CustomFrequencyManagerService( 872): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1188000 uid : 1000 pid : 872 tag : [email protected]
D/lights ( 872): button : 0 +
D/lights ( 872): button : 0 -
D/qdutils ( 321): getuiClearRegion:70 wormRect( l = 0 t = 0 r = 720 b = 50)
D/qdutils ( 321): getuiClearRegion:76 FinalwormRect( l = 0 t = 0 r = 720 b = 50)
E/SMD ( 346): DCD ON
I/SecureStorage(12345): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(12345): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
E/SecureStorage(12345): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(12345): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(12345): [ERROR]:Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Any ideas?

ccoager said:
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
Any ideas?
Click to expand...
Click to collapse
My recommendation? DON'T DO ENCRYPTION!! you may get your phone in a lockmode and unable to recover data..

Is there anything else that could be causing this?
I have not chosen device encryption and I am also seeing these messages in logcat..
I/SecureStorage(15360): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(15360): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_stor.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
E/SecureStorage(15360): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(15360): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(15360): [ERROR]:Error cannot connect to TA/driver!
E/SMD ( 213): DCD ON

Same Problem
I am getting the same thing and when I rooted my SCH-r530u I disabled the Knox thing
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon is preparing to run
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon successfully binded a socket
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_stor.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_storage.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Loading app sec_stor and sec_storage failed
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Fail to open session with qualcomm
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Error cannot connect to TA/driver!
02-20 22:57:12.161: V/AlarmManager(411): waitForAlarm result :8
Click to expand...
Click to collapse
What does it mean? I keep getting it every few seconds while the screen is on
* I was going to edit out the sad faces but its too funny cause it fits the situation perfectly*

Related

[BETA][Kernel][Port][GT-P6200]

First I must thank @ aorth, and @ garyd9. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device. In fact until I make any relevant edits this thread will remain tagged [PORT].
Beta 4 up. Stock Clocks and voltages built a version with voltage tables intact, but lowering even one of them by the min(25mV) and applying in SetCpu causes panic.
Beta testers needed. You know the drill. Backup and feedback is always appreciated.
Im almost positive all 6200 kernel partitions are on mmcblk0p5, you can double check with 'get pit' & heimdall. Mobile Odin says it supports P6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!Flashing a kernel to the incorrect partition is asking to be bricked.--please put both custom and stock on sdcard in case you cannot boot.--
The 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded for heimdall, or stock .zip wit CWM Recovery.
The other 2 that start with GT-P6200 can be flashed in recovery. <WARNING>: SOME People have had to wipe /data ; factory reset to get past stuck boot logo.</WARNING> I have updated the install script, so cache and dalvik should be totally cleared.
Either way my custom binary count hasnt changed any.
Features
custom bootanimation support: place appropriate botoanimation.zip in: /system/media/ with permission rw-r--r--. The ICS one garyd made us works lovely. Im using the xda TV one. link coming soon:
Busybox in /sbin.
Support for init.d scripts. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Be Warned. Also his 3G tweaks made my 3G speeds worse.)
Removed a lot of debug stuff.
unsecure kernel (adb shell gives root)
reboot bootloader and reboot download support
(quick boot in market is a great app)
Enjoy!!

reserved
Beta 4 up: 3/20
Removed OC/UV, stock clocks and voltages. tried a build with Gary's table sysfs in there, UV even one frequency by 25mV and pressing apply in SetCpu caused seizure. At least were stable now. Im not too concerned about battery life. There are other tweaks we can apply.
github: still updating..
https://github.com/crotoloandroid

Established on LA2 (SER). Far so good, thanks.

Putting it through its paces right now
Thanks
SetCPU set to 200 min, 1400 max
OnDemand governor. No other changes.
Nenamark1: 55.6 fps (no previous record)
Nenamark2: 41.1 fps (47.7 fps pre-oc)... very erratic performance
Stability Test, HQ CPU&GPU, 6 minute test: CPU passes, 7. GPU passes, 55. No failures
GL Benchmark v2.1 (All Tests): Passed, however can't upload to GLBenchmark.com as their captcha service is ****ed
Only one issue I've come across so far, and this is the same issue RichardTrip was having when he compiled some custom kernels for me earlier this year. Random wakelocks bring the tab out of sleep and turn the screen on.
These are caused by the usb scanner looking for external USB devices...
Code:
D/UsbService( 3447): setUsbObserverNotification :: titleId = 0, messageId = 0, icon = 17302785, visible = false, dismissable = false
D/usbhost ( 3447): new device /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_open /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_new /dev/bus/usb/001/004 fd: 298
D/usbhost ( 3447): usb_device_new read returned 259 errno 4
D/UsbService( 3447): usbDeviceAdded : device :: /dev/bus/usb/001/004 [1519h:0020h] [02h,00h,00h] (CDC Control)
D/UsbService( 3447): isBlackListed :: deviceName = /dev/bus/usb/001/004
D/UsbService( 3447): isBlackListed :: mHostBlacklist[i] = /dev/bus/usb/001/002
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz2 subClass=0
E/UsbService( 3447): continue...
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/NotificationService( 3447): cancelNotification - pkg:android, id:17302785
D/TabletStatusBar( 3529): setVisibility(View.VISIBLE
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
D/dalvikvm( 6436): GC_CONCURRENT freed 358K, 11% free 6800K/7559K, paused 2ms+1ms
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/KeyguardViewMediator( 3447): setHidden false
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): turnOnLcd ::
D/PowerManagerService( 3447): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=true
I/PowerManagerService( 3447): Ulight 0->3|0
I/PowerManagerService( 3447): setTargetLocked mask=2 curValue=0.0 target=95 targetValue=95 delta=6.3333335 nominalCurrentValue=0
I/PowerManagerService( 3447): scheduling light animator
I/power ( 3447): *** set_screen_state 1
D/KeyguardViewMediator( 3447): onScreenTurnedOn, seq = 3
D/KeyguardViewMediator( 3447): notifyScreenOnLocked
D/KeyguardViewMediator( 3447): handleNotifyScreenOn
D/LockScreen( 3447): updateLayout: status=Normal
D/PowerManagerService( 3447): enableLightSensorLocked enable=true mAutoBrightessEnabled=false
D/PowerManagerService( 3447): jumpToTargetLocked targetValue=95: 2
I/PowerManagerService( 3447): Light Animator Finished curIntValue=95
I/OrientationDebug( 3447): [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
D/SensorManager( 3447): registerListener :: handle = 4 name= MPL accel delay= 60000 Listener= [email protected]0c5dc38
D/MPLSensor( 3447): handle : 4 en: 1
D/MPLSensor( 3447): enabled_sensors: 16 dmp_started: 0
D/MPLSensor( 3447): MLSetMPUSensors: 70
I/MPL-ml ( 3447): Actual ODR: 25 Hz
D/MPLSensor( 3447): set_power_states > MLDmpStart()
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=200000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=60000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
V/WindowManager( 3447): Setting event dispatching to true
D/KeyguardViewMediator( 3447): setHidden false
D/WifiStateMachine( 3447): ConnectedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65659 when=-1ms }
E/wpa_supplicant( 3807): initalize the scan timer ( 7 )
D/WifiService( 3447): ACTION_SCREEN_ON
I/ScreenReceiver : ( 4156): android.intent.action.SCREEN_ON
D/ProximityScreenOff( 4156): ScreenReceiver : action = android.intent.action.SCREEN_ON State: IDLEPhoneOn = false
D/WifiStateMachine( 3447): ConnectedState{ what=65618 when=-5ms arg1=1 }
D/SensorManager( 4156): registerListener :: handle = 8 name= GP2A Proximity sensor delay= 10000 Listener= [email protected]
I/ProximityScreenOff( 4156): SensorMonitor onStart::Registered
D/WifiStateMachine( 3447): ConnectedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65591 when=-13ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65608 when=-13ms arg1=1 }
D/WifiStateMachine( 3447): ConnectedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DefaultState{ what=65549 when=-14ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65613 when=-14ms }
D/JuicePlotter.CollectService( 4252): battery:48, plugged:0, screen:95, wifi:true(0kb/s), apn:false(0kb/s), bluetooth:false,cpu:2
W/googleanalytics( 4331): Store full. Not storing last event.
D/SurfaceFlinger( 3267): Screen about to return, flinger = 0xa920

chrisrotolo said:
1st I must thank @ aorth, and @ garyd. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device.
Beta testers needed. 100% working and stable for me. UWAXME - Malyasia Tab
Im almost positive all 6200 kernel partition is on mmcblk0p5, you can double check with get pit & heimdall. Mobile Odin says it supports P-6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!--please put both custom and stock on sdcard in case you cannot boot.--
the 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded in heimdall, or stock .zip wit CWM Recovery.
the other 2 that start with GT-P6200 can be flashed in recovery.
Either way my custom binary count hasnt changed.
As Im short on time at the moment I will make this brief and update this thread shortly.
contains:
custom bootanimation support place usual in: /system/media/bootanimation.zip with permission rw-r--r--. the ICS one garyd made us works lovely.
OC to 1.4 (NO UV yet, but likely in final release.)
unsecure kernel (adb shell gives root)
and init.d scripts tested with Supercharger. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Also his 3G tweaks made my actually worse.)
to come: UV, reboot download support, (botologos maybe?), what else? let me know I'll see what I can do. This is my first kernel, Im learning as I go.
This should have been released a week ago, but I was stuck on a permissions issue, that was so easy to fix.
Enjoy!!
Click to expand...
Click to collapse
it great and mega fast i am so pleased we have you on out team bro you are mega awesome....donation on its way.
i installed the cwm version and it wad stuck in boot loop but i wiped data and it worked...thanks got for app extracter haha :-D but well worth it.
thanks man keep up the good work
regards jmar8124 G-tab plus kl3 Malaysia

You had to factory reset? Ill double check my scripts to wipe cache and dalvik

chrisrotolo said:
You had to factory reset? Ill double check my scripts to wipe cache and dalvik
Click to expand...
Click to collapse
ye but it could have been something to do with old tegers haha stupid lum of crap haha its got to be the worst app iv ever purchased. thanos man you kernel is great il try installing it agen with out kernel beeing loaded

Updated my original post above ^^^

double_ofour said:
Pare how can i convert CDL to o2? step-by-step please
Click to expand...
Click to collapse
Thanks chris, will test this. Excited to see some dev going on with international version of 7+. Some suggestions:
Please name your kernel! Make it sound cool as it really is
Add cifs.ko support in the future?
Also just a question, would oc'ng to 1.4 ghz be dangerous without any overvolting. Thanks!
Sent from my GT-P6200 using XDA

download and flash awayyyy.... doing stress test now...
edit...
installation no problem... setting up setcpu now... and doing stress test for max 1400

thanks for the help testing guys. This 1.4 is "hidden" in stock cpufreq commented out as "development only". Should be fine unless you run graphics intense apps with min & man set to 1.4 and performance governor for long periods of time.
I'll add warning about some having to wipe /data with CWM.
I'll look into cifs.ko, should be doable.
I've been getting a lot of dropped signal, may be totally unrelated, I just move to a new building, and also just got word we should be getting AT&T LTE in Hartford CT in a few weeks, so could be network thing.
be back as soon as I can guys. Feedback helps.

u guys getting any deep sleep on cpu spy? im not getting any deep sleep
Edit: a reboot helped got deep sleep back. Reasonable batt life at 1.4ghz

being using it for 2 hours with nova2... current batt from 100% to 60% but full 2 hours on nova... quite ok... runnning setcpu 1400 with ondemand governor... havent face any problem yet...

Flashed the custom kernel with recovery ...everything works just fine.
First boot was a bit long as expected.
I used nofrills cpu control, the default interactive governor was a bit laggy, changed to conservative. No deep sleep problem at all.
Thank you.
Sent from my GT-P6200 using XDA

For anyone interested in cifs.ko or tun.ko, check out this thread...
http://forum.xda-developers.com/showthread.php?t=1400255
Anyone else having wakelocks? / random wake ups? I havent had any.
Welp, likely not going to be able to implement @garyd9's UV, keep getting this mesaage :
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_set_cpufreq_armvolt':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_cpufreq_init':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_freq'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_mV'
make: *** [.tmp_vmlinux1] Error 1
at end of kernel build. The one we have I think should be fine. I will add support for reboot bootloader (& download), and probably release final version tomorrow.
I dont want to make this a long in depth thing anyways (its already been a few weeks for me), becuase hopefully Ice Cream is near.
And my home cpu is in dire need of an upgrade (AMD dual core 4GB) building takes nearly an hour on VM, I will likely be getting a new one shortly.
UPDATE: so I think I am getting wake locks/ USB issue. I think Ive had it wake itself 3 times in a row, and Ive had it lose signal when I press power button to wake device, it signal bars are 0;all grey, and/or says no signal, and occasionally at the same time will says usb device removed.
ive compared my config to garyd9's, at least the one I think he used. didnt see anything I think might cause it, although we do have a bit more hardware in ours. I though I recall something in the kernel menuconfig about wakelocks.
I guess its to be expected, hacking my first kernel. Guess I will just have to run some DMESG's
VENT APPEND: I am finding github push/pull/commit/add/etc to be a steamy pile of crap. I will search for alternatives.

yup got random wake locks... but i haven't face any usb/no signal issue. at least not yet
btw info about governors is quite nice here...
http://forum.xda-developers.com/showthread.php?t=1369817

I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks

chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
chris,
using cpu spy and betterbatterystats app from xda, i was able to trace my wakelocks to mediascanner. so i just killed mediascanner and i got deep sleep back. im not sure though if i had this problem even before i flashed your custom kernel because i never used cpu spy and betterbatterystats on the stock kernel. maybe this helps? i don't get signal drops

chris... i'm currently testing some of the script for init.d on this thread...
http://forum.xda-developers.com/showthread.php?t=1353903

chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
im always on wifi, barely use my data plan. but i do have wakelocks draining the battery. i also noticed once that my screen didn't time out, screen was on all the time when i left my tablet, so battery drained quite quickly. i think someone has reported this also. i'll do more observation.

[Q] Bluetooth media doesnt work on ported rom. Please help?

Any developer here??? Pls help me to fix bt media... My rom is HTC Sense 4 for htc explorer/pico which is ported by derefas from HTC Desire C. Bluetooth file transfer works very well but bt headset doesnt work. Here is the logcat.
E/BluetoothA2dpService.cpp( 349): onConnectSinkResult: D-Bus error: org.bluez.E
rror.Failed (Stream connection failed)
D/BluetoothA2dpService( 349): checkSinkSuspendState(): state=0,mTargetA2dpState
=-1
D/StateMachine( 349): handleMessage: new destination call exit
D/StateMachine( 349): invokeExitMethods: PendingCommandState
I/BluetoothProfileState( 349): Message:Entering Stable State
D/AudioService( 349): isSpecialCase=true , mEventAudioOnly=false , isStreamActi
ve=false
D/AudioService( 349): checkEqIdAndApplyEffect isHeadsetPlugged()=false , mBluet
oothHeadsetConnected=false , id=900 , mHtcSpecificAP=false , mGlobalSoundEffect=
900
V/AudioHardwareMSM72XX( 114): setParameters() global_effect=none
D/AudioService( 349): broadcastSoundEffectChanged beats state=false appName=BT
state changed
V/BluetoothEventManager( 2780): Received android.bluetooth.a2dp.profile.action.C
ONNECTION_STATE_CHANGED
I/LocalBluetoothProfileManager( 2780): Failed to connect A2DP device
D/StateMachine( 349): handleMessage: new destination call exit
D/StateMachine( 349): invokeExitMethods: OutgoingA2dp
I/BluetoothDeviceProfileState( 349): Entering ACL Connected state with: 102
D/BluetoothA2dpService( 349): A2DP state : device: C4:85:08:05:59:5A State:1->0
I/BluetoothA2dpService( 349): [embedded] A2DP state : address: C4:85:08:05:59:5
A name: SHEKHAR-PC State:1->0
D/BluetoothAdapterStateMachine( 349): BluetoothOn process message: 52
D/BluetoothService( 349): CONNECTION_STATE_CHANGE: C4:85:08:05:59:5A: 1 -> 0
V/BluetoothEventManager( 3562): Received android.bluetooth.a2dp.profile.action.C
ONNECTION_STATE_CHANGED
I/LocalBluetoothProfileManager( 3562): Failed to connect A2DP device
I/USERIAL_LINUX( 3593): ##### USERIAL_Ioctl: BT_Sleep, USERIAL_IO_BT_WAKE_DEASSE
RT ####
D/PhoneStatusBarPolicy( 634): isCdma():false hasService:true mSimState=UNKNOWN
gprsState=0 mDataState=0 dataActivity=1 mPhone.htcModemLinkOn:false hspa==true
E/ ( 3593): btm_sec_disconnected - Clearing Pending flag
W/ ( 3593): BTA_DM_LINK_DOWN_EVT::bdaddr c4:85:08:05:59:5a reason x13
I/ ( 3593): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTR
L) 11 pbytes (hdl 22)
D/DTUN_HCID4( 3608): dtun_dm_sig_link_down()
I/DTUN_HCID4( 3608): dtun_dm_sig_link_down device = 0x6f7900 reason = 19
I/DTUN_HCID4( 3608): [embedded]LINK_DOWN name = SHEKHAR-PC, address = C4:85:08:0
5:59:5A, reason = 0x13
D/BluetoothEventLoop( 349): Device property changed: C4:85:08:05:59:5A property
: Connected value: false
D/ ( 3593): >>> STOP GKI_timer_update(), wake_lock_count:0
D/ ( 3593): >>> SUSPENDED GKI_timer_update()
Can anyone guide me to fix this?

why wifi not working? here there is the answer...

hello,
i open this thread to collect informations about a common problem that happens after flashing new roms
this thread has generic purpose, and is not intended for a specific board...
- suggestions on how to discover the cause of the problem
- suggestions on how to fix the problem
anyone that think to have some useful informations on this issue can insert his post
i am not an expert ( and still my wifi is not working )
but i collected some informations, and i would like to share them

The first thing is:
what happens when from the settings i click on wifi to turn it on
to see this, i opened a terminal emulator session
and i have written this:
adb logcat > 'some file name on a writable directory' (for example , i redirected the output to the external sd card)
here is what was written on the file (extracting from the file only the last part, that is the output related to my action of wifi activation):
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
Searching on the web this string: "Read wifi chip type OK ! wifi_chip_type"
i found this:
https://github.com/aloksinha2001/pi****u-3.0.8-alok/blob/master/RK30_MT5931_MT6622/wifi/wifi.c
into procedure check_wifi_chip_type() i saw exactly this part:
else if (0 == strncmp(buf, "RK901", strlen("RK901")) )
{
wifi_chip_type = RK901;
ALOGD("Read wifi chip type OK ! wifi_chip_type = RK901");
}
here is compared the value of string buf with "RK901"
the string buf is read from this file: "/sys/class/rkwifi/chip"
(so i suppose that this file has been written before by some other procedure)
so, i searched the caller procedure of check_wifi_chip_type():
in the same source i find this caller:
int wifi_load_driver()
{
#ifdef WIFI_DRIVER_MODULE_PATH
char driver_status[PROPERTY_VALUE_MAX];
int count = 100; /* wait at most 20 seconds for completion */
int type;
char path[64];
if (is_wifi_driver_loaded()) {
return 0;
}
strcpy(path, DRIVER_MODULE_PATH);
type = check_wifi_chip_type();
if((type == RK901) || (type == RK903) || (type == BCM4330)) {
strcpy(path, "/system/lib/modules/rkwifi.ko");
} else if (type == RTL8188CU) {
....
this procedure as first step checks if the driver is already loaded,
if not:
the driver module path is set by default to "/system/lib/modules/wlan.ko"
Then basing on the chip type is got a more specific path:
for example, for RK901/RK903/BCM4330 the path is set to : "/system/lib/modules/rkwifi.ko"
Then, is checked if the file does exist, and if not the path is seth to the default DRIVER_MODULE_PATH,
that is "/system/lib/modules/wlan.ko"
// judge if the KO file exist, if not, insmod wlan.ko
if (access(path, F_OK) < 0) {
ALOGD("DRIVER_MODULE_PATH = %s (Not such file)...", path);
strcpy(path, DRIVER_MODULE_PATH);
}
Then,
is called insmod (insert module),
to load the driver file in 'memory' (a new module into the kernel, i suppose):
if (insmod(path, DRIVER_MODULE_ARG) < 0) {
ALOGD("%s: driver load failed", __FUNCTION__);
wifi_unload_driver();
if(retry_count-- > 0) goto retry_load_driver;
return -1;
}
Looking the logcat above,
the flow in my case stops here, with : wifi_load_driver: driver load failed
so something happened in insmod:it is not able to load the file /system/lib/modules/rkwifi.ko in memory or initialize it
(the file is found, else the process should stop before, when checking access to the file)
The insmod function does this:
allocates memory for the structure name (type utsname) :
memset(&name, 0, sizeof(name));
and load the file on this area:
module = load_file(filename_release, &size);
Then is checked if the file has been loaded
if (!module)
return -1;
and finally
the module is 'initialized':
ret = init_module(module, size, args);
One of this two events went wrong, because insmod returned -1
My investigation stops here... i am not able to proceed more...
but i am open to all suggestions and hints
Thank you!!

Vicolodo said:
The first thing is:
what happens when from the settings i click on wifi to turn it on
to see this, i opened a terminal emulator session
and i have written this:
adb logcat > 'some file name on a writable directory' (for example , i redirected the output to the external sd card)
here is what was written on the file (extracting from the file only the last part, that is the output related to my action of wifi activation):
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
Searching on the web this string: "Read wifi chip type OK ! wifi_chip_type"
i found this:
https://github.com/aloksinha2001/pi****u-3.0.8-alok/blob/master/RK30_MT5931_MT6622/wifi/wifi.c
into procedure check_wifi_chip_type() i saw exactly this part:
else if (0 == strncmp(buf, "RK901", strlen("RK901")) )
{
wifi_chip_type = RK901;
ALOGD("Read wifi chip type OK ! wifi_chip_type = RK901");
}
here is compared the value of string buf with "RK901"
the string buf is read from this file: "/sys/class/rkwifi/chip"
(so i suppose that this file has been written before by some other procedure)
so, i searched the caller procedure of check_wifi_chip_type():
in the same source i find this caller:
int wifi_load_driver()
{
#ifdef WIFI_DRIVER_MODULE_PATH
char driver_status[PROPERTY_VALUE_MAX];
int count = 100; /* wait at most 20 seconds for completion */
int type;
char path[64];
if (is_wifi_driver_loaded()) {
return 0;
}
strcpy(path, DRIVER_MODULE_PATH);
type = check_wifi_chip_type();
if((type == RK901) || (type == RK903) || (type == BCM4330)) {
strcpy(path, "/system/lib/modules/rkwifi.ko");
} else if (type == RTL8188CU) {
....
this procedure as first step checks if the driver is already loaded,
if not:
the driver module path is set by default to "/system/lib/modules/wlan.ko"
Then basing on the chip type is got a more specific path:
for example, for RK901/RK903/BCM4330 the path is set to : "/system/lib/modules/rkwifi.ko"
Then, is checked if the file does exist, and if not the path is seth to the default DRIVER_MODULE_PATH,
that is "/system/lib/modules/wlan.ko"
// judge if the KO file exist, if not, insmod wlan.ko
if (access(path, F_OK) < 0) {
ALOGD("DRIVER_MODULE_PATH = %s (Not such file)...", path);
strcpy(path, DRIVER_MODULE_PATH);
}
Then,
is called insmod (insert module),
to load the driver file in 'memory' (a new module into the kernel, i suppose):
if (insmod(path, DRIVER_MODULE_ARG) < 0) {
ALOGD("%s: driver load failed", __FUNCTION__);
wifi_unload_driver();
if(retry_count-- > 0) goto retry_load_driver;
return -1;
}
Looking the logcat above,
the flow in my case stops here, with : wifi_load_driver: driver load failed
so something happened in insmod:it is not able to load the file /system/lib/modules/rkwifi.ko in memory or initialize it
(the file is found, else the process should stop before, when checking access to the file)
The insmod function does this:
allocates memory for the structure name (type utsname) :
memset(&name, 0, sizeof(name));
and load the file on this area:
module = load_file(filename_release, &size);
Then is checked if the file has been loaded
if (!module)
return -1;
and finally
the module is 'initialized':
ret = init_module(module, size, args);
One of this two events went wrong, because insmod returned -1
My investigation stops here... i am not able to proceed more...
but i am open to all suggestions and hints
Thank you!!
Click to expand...
Click to collapse
Interesting... Yesterday i was trying to solve this problem caused by a cwm recovery flashing during about 8 hours with my mk809ii. I let my pc downloading about 10 different roms from other similar devices, and this morning i stay to try one by one. Finally i found "mk808B bob finless 2.1 room (jb4.2.2) with wifi APxxxx" (APxxxx is my wifi chip, i can't remember the xxxx just now) fix both wifi and bluetooth.
You did a good research, i will save your post on case i get the error again, but i think the best thing to do is to search for a compatible rom and try, with same both cpu and wifi chipset. Also now after read your post i am going to save a backup of system /lib and system /etc directories, maybe changing the wifi library files fix the error without needing of flash and reflash...
Thanks, i liked your post!
Enviado desde mi GT-P7510 usando Tapatalk 2

somthing intresting help unbrick

[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut

how to unbrick?

botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
how did you check this out?

theonecallednick said:
how did you check this out?
Click to expand...
Click to collapse
I found uart pin on mainboard for debuging .
with serial usb cable pl2303

This is the red light only and unknown hardware found (the unknown hardware is in fact mtk usb vcom driver buth sony version ) if you try sp flash tool for mtk then it comunicates with de phone buth it needs some authentication file.

Help..
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..

botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
.........................
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
Samuel Wankhede said:
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
Click to expand...
Click to collapse
Try the guide given in thread linked below
http://forum.xda-developers.com/showpost.php?p=57614511&postcount=13

Please share uart pinout
Baudrate should be 115200??
Thanks

uart
please share the uart pinout , thanks

[msm8939][meizu][camera]dlopen failed: could not load library "libcam.meiyan.so" need

[msm8939][meizu][camera]dlopen failed: could not load library "libcam.meiyan.so" need
Hello,
Could you please help me?
Platform:meizu m1note msm8939
I ported from flyme to miui.
The camera has problem.
I got the error:
dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so";
caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
About symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl",
I found it at:
m463c/rom/update/system $ g CBeautyShot
Binary file ./lib/libarcsoft_beauty_shot.so matches
Binary file ./lib/libcam.meiyan.so matches
And I push them to my phone.
But I still get the error.
Who can help me? Thank you very much.
I have been debugging for several days.
01-02 08:17:52.901 I/libmdmdetect( 351): Found internal modem: modem
01-02 08:17:52.901 E/QC-QMI ( 272): qmi_client [272]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 E/QC-QMI ( 351): qmi_client [351]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 I/ThermalEngine( 288): Sensor:tsens_tz_sensor3:80000 mC
01-02 08:17:52.941 E/HAL ( 276): load: module=/system/lib/hw/camera.msm8916.so
01-02 08:17:52.941 E/HAL ( 276): dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so"; caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
01-02 08:17:52.941 E/CameraService( 276): Could not load camera HAL module
01-02 08:17:52.941 I/mediaserver( 276): ListenService instantiated
01-02 08:17:52.941 V/ListenService( 276): instantiate entered
01-02 08:17:52.941 V/ListenService( 276): getInstance entered, mNumInstances currently 0
Eismog
my-mail:[email protected]

Is there anyone who can help me?

Database Info

welcome