I wanted to use my atrix to call out over wifi when i travel overseas. I did some research and found that this was possible on an android phone. I found this h**p://jasonmlee.net/archives/422/comment-page-1#comment-1762 and was able to setup the phone. Now whenever i make or receive calls, the call quality is very distorted. Any solution to fix this problem?
thanks
Instead of sipdroid, find the csipsimple nightly labeled atrix something. It isn't perfect, but it's the best solution I've found so far.
Will try that. Thanks!
Hello,
I've been trying for a bit now to get my atrix to do sip through my asterisk (trixbox) but all it does is screw up the audio. i'm mainly trying pcmu 8bit but tried other combos. any help is much appreciated... i basically want to flush this thing because of this problem. I've identified these links that discuss this issue but with no fix:
http code.google.com/p/sipdroid/issues/detail?id=885&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Stars
https supportforums.motorola.com/message/338790
http forum.androidcentral.com/motorola-atrix/63606-voip-sip-calling-issues.html
This is stock out of box from bell. sorry for the obfuscated link. new user rules.
I can't see anything suspicious in the log either:
[Jan 19 00:13:34] VERBOSE[2815] logger.c: == Using SIP RTP TOS bits 184
[Jan 19 00:13:34] VERBOSE[2815] logger.c: == Using SIP RTP CoS mark 5
[Jan 19 00:13:34] VERBOSE[2815] logger.c: == Using SIP VRTP TOS bits 136
[Jan 19 00:13:34] VERBOSE[2815] logger.c: == Using SIP VRTP CoS mark 6
[Jan 19 00:13:34] DEBUG[2783] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]om-internal:1] Macro("SIP/203-0000001a", "user-callerid,") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:1] Set("SIP/203-0000001a", "AMPUSER=203") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:2] GotoIf("SIP/203-0000001a", "0?report") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:3] ExecIf("SIP/203-0000001a", "1?Set(REALCALLERIDNUM=203)") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:4] Set("SIP/203-0000001a", "AMPUSER=203") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:5] Set("SIP/203-0000001a", "AMPUSERCIDNAME=molerolla") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:6] GotoIf("SIP/203-0000001a", "0?report") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:7] Set("SIP/203-0000001a", "AMPUSERCID=203") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:8] Set("SIP/203-0000001a", "CALLERID(all)="molerolla" <203>") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:9] ExecIf("SIP/203-0000001a", "0?Set(CHANNEL(language)=)") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:10] GotoIf("SIP/203-0000001a", "0?continue") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:11] Set("SIP/203-0000001a", "__TTL=64") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:12] GotoIf("SIP/203-0000001a", "1?continue") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Goto (macro-user-callerid,s,19)
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:19] NoOp("SIP/203-0000001a", "Using CallerID "molerolla" <203>") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:2] Set("SIP/203-0000001a", "MEETME_ROOMNUM=420") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:3] GotoIf("SIP/203-0000001a", "0?USER") in new stack
[Jan 19 00:13:34] VERBOSE[14060] logger.c: -- Executing [[email protected]:4] Answer("SIP/203-0000001a", "") in new stack
[Jan 19 00:13:35] VERBOSE[14060] logger.c: -- Executing [[email protected]:5] Wait("SIP/203-0000001a", "1") in new stack
[Jan 19 00:13:36] VERBOSE[14060] logger.c: -- Executing [[email protected]:6] Set("SIP/203-0000001a", "MEETME_OPTS=Ms") in new stack
[Jan 19 00:13:36] VERBOSE[14060] logger.c: -- Executing [[email protected]:7] Goto("SIP/203-0000001a", "STARTMEETME,1") in new stack
[Jan 19 00:13:36] VERBOSE[14060] logger.c: -- Goto (from-internal,STARTMEETME,1)
[Jan 19 00:13:36] VERBOSE[14060] logger.c: -- Executing [[email protected]:1] MeetMe("SIP/203-0000001a", "420,Ms,") in new stack
[Jan 19 00:13:36] VERBOSE[20057] logger.c: -- Stopped music on hold on SIP/200-00000008
[Jan 19 00:13:42] VERBOSE[14060] logger.c: == Spawn extension (from-internal, STARTMEETME, 1) exited non-zero on 'SIP/203-0000001a'
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Executing [[email protected]:1] Macro("SIP/203-0000001a", "hangupcall") in new stack
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Executing [[email protected]:1] GotoIf("SIP/203-0000001a", "1?skiprg") in new stack
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Goto (macro-hangupcall,s,4)
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Executing [[email protected]:4] GotoIf("SIP/203-0000001a", "1?skipblkvm") in new stack
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Goto (macro-hangupcall,s,7)
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Executing [[email protected]:7] GotoIf("SIP/203-0000001a", "1?theend") in new stack
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Goto (macro-hangupcall,s,9)
[Jan 19 00:13:42] VERBOSE[14060] logger.c: -- Executing [[email protected]:9] Hangup("SIP/203-0000001a", "") in new stack
[Jan 19 00:13:42] VERBOSE[14060] logger.c: == Spawn extension (macro-hangupcall, s, 9) exited non-zero on 'SIP/203-0000001a' in macro 'hangupcall'
Found this thread:
http code.google.com/p/csipsimple/issues/detail?id=795
I tried installing this:
http nightlies.csipsimple.com/trunk/CSipSimple-latest-trunk.apk
same problem as before. any help is appreciated. thx
I haven't tried that specific apk yet, but with the earlier 'atrix' one it will work so long as the clock rate is set to 32 khz and 'use routing api' is checked. It still sucks because it uses the microphone on the back of the phone, but it does clear up the static of death.
where is this option "use routing api" sorry i might be blind
i installed 3cx and it works! solved!
okay... just an update 3cx mostly works... won't use ear piece for audio out... only speaker... but at least calls are audible although other end reports choppyness a bit.
Looks like you already found another solution, but the "use routing api" only appears when you go into csipsimple's expert mode settings.
Related
Hi!
Has anyone luck with the TyTN and Linux? Have tried the synce package with synce-kde (raki) but there was no success.
There is a new eth dev unsing the rndis driver, and there is an ip connection between 169.254.2.1 <> 169.254.2.2 but nothing more
Any success on mounting as a mass storage dev?
There used to be a problem syncing with WM6. But recently I've been able to do it using the old usbserial method and the ipaq module. I haven't tried the GUI stuff, but the basic synce tools work fine. Mass storage mounting also works.
I'm in the same problem with synce and raki... my tytn don't understand my ubuntu?
I've searched a lot about this and doesn't works.
The only solution that works for me at the moment (may be the worst) is install a winXP in a VirtualBox but I know that it's not the better solution, and the "seamless" option of virtualbox last edition doesn't works for me...
Anybody has more info about linux, activesync and Hermes (wm5 o 6) ...
Please help!!
Well, as I've said, it works fine here with Gentoo and WM6.
- on the Hermes under Connections -> USB to PC, disable the advanced functionality.
- get synce and odccm
- in the kernel, enable usbserial and ipaq
Then your Hermes should be recognized as something like /dev/tts/USB0
I just use a little script like this:
Code:
synce-serial-config /dev/tts/USB0 192.168.0.101:192.168.0.102
sleep 1
odccm
sleep 1
synce-serial-start
If it works, you should see something like this:
Code:
0:192.168.0.101:192.168.0.102
You can now run synce-serial-start to start a serial connection.
Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/tts/USB0
local IP address 192.168.0.101
remote IP address 192.168.0.102
And then the basic synce tools like pls, pcp, etc., should work.
To get this working on Ubuntu you have to compile the whole synCE set of software (synce, rapi, odccm etc.) from SVN. This is done in this Guide:
http://ubuntuforums.org/showthread.php?t=345176
Just use that guide for instructions on how to compile from SVN, ignore the kernel patching and usb drivers and so on unless you're feeling masochistic.
For feisty, you can still use ipaq as demonstrated here, just stop after you have compiled and installed the synce packages. After that the aforementioned guide tries to compile the new drivers which requires kernel patching, pain, and suffering.
So, after compiling the newer synce, switch over to xor's instructions.
I've made a little Sync-with-Linux page for the Hermes Wiki. Feel free to contribute.
gentoo packages
Hi _xor,
I'm trying to get my Prophet WM6-upgraded PDA connected to my 2.6.23-tuxonice-r6 powered Gentoo Linux but couldn't make it work. I'm trying to use it as a GPRS modem and to sync it too (priority 2 actually).
How did you get odccm installed? app-pda/synce-dccm doesn't have it and there is no odccm at all.
Or yet better, what packages did you install? (I'm using KDE as my window manager as you do).
BTW, the links on the wiki are no longer valid and couldn't get to them through google too.
EDIT: I could make it work!!!!!
The problem was somehow related to the PPP connection not establishing the IP address correctly:
Jan 27 14:29:45 RJZ-LNX usb 2-2: new full speed USB device using uhci_hcd and address 23
Jan 27 14:29:45 RJZ-LNX usb 2-2: configuration #1 chosen from 1 choice
Jan 27 14:29:45 RJZ-LNX ipaq 2-2:1.0: PocketPC PDA converter detected
Jan 27 14:29:45 RJZ-LNX usb 2-2: PocketPC PDA converter now attached to ttyUSB0
Jan 27 14:29:51 RJZ-LNX synce-serial-start: Executing '/usr/sbin/pppd call synce-device'
Jan 27 14:29:51 RJZ-LNX pppd[28592]: pppd 2.4.4 started by root, uid 0
Jan 27 14:29:53 RJZ-LNX pppd[28592]: Serial connection established.
Jan 27 14:29:53 RJZ-LNX pppd[28592]: using channel 13
Jan 27 14:29:53 RJZ-LNX pppd[28592]: Using interface ppp0
Jan 27 14:29:53 RJZ-LNX pppd[28592]: Connect: ppp0 <--> /dev/ttyUSB0
Jan 27 14:29:53 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: waiting for IP address on ppp0
Jan 27 14:29:54 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: waiting for IP address on ppp0
Jan 27 14:29:54 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:29:55 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: waiting for IP address on ppp0
Jan 27 14:29:56 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: waiting for IP address on ppp0
Jan 27 14:29:57 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: waiting for IP address on ppp0
Jan 27 14:29:57 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:00 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:03 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:06 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:09 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:12 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:15 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:18 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:21 RJZ-LNX pppd[28592]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1ce61ea3> <pcomp> <accomp>]
Jan 27 14:30:24 RJZ-LNX pppd[28592]: LCP: timeout sending Config-Requests
Jan 27 14:30:24 RJZ-LNX pppd[28592]: Connection terminated.
Jan 27 14:30:24 RJZ-LNX pppd[28592]: Modem hangup
Jan 27 14:30:24 RJZ-LNX pppd[28592]: Exit.
I just re-enabled and disabled again the "enable advanced network functionality" on the PDA while it was connected to my PC and it started to work:
Jan 27 14:42:09 RJZ-LNX usb 2-2: new full speed USB device using uhci_hcd and address 27
Jan 27 14:42:09 RJZ-LNX usb 2-2: configuration #1 chosen from 1 choice
Jan 27 14:42:09 RJZ-LNX ipaq 2-2:1.0: PocketPC PDA converter detected
Jan 27 14:42:09 RJZ-LNX usb 2-2: PocketPC PDA converter now attached to ttyUSB0
Jan 27 14:42:32 RJZ-LNX synce-serial-start: Executing '/usr/sbin/pppd call synce-device'
Jan 27 14:42:32 RJZ-LNX pppd[30637]: pppd 2.4.4 started by root, uid 0
Jan 27 14:42:35 RJZ-LNX pppd[30637]: Serial connection established.
Jan 27 14:42:35 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: waiting for IP address on ppp0
Jan 27 14:42:35 RJZ-LNX pppd[30637]: Using interface ppp0
Jan 27 14:42:35 RJZ-LNX pppd[30637]: Connect: ppp0 <--> /dev/ttyUSB0
Jan 27 14:42:35 RJZ-LNX pppd[30637]: local IP address 192.168.131.102
Jan 27 14:42:35 RJZ-LNX pppd[30637]: remote IP address 192.168.131.201
Jan 27 14:42:36 RJZ-LNX odccm[28560]: DEBUG: _odccm_interface_address: found matching interface
Jan 27 14:42:36 RJZ-LNX odccm[28560]: DEBUG: PDA network interface discovered! udi='/devices/virtual/net/ppp0'
Jan 27 14:42:40 RJZ-LNX odccm[28560]: DEBUG: device_info_received
Jan 27 14:42:40 RJZ-LNX odccm[28560]: DEBUG: f1 ea 81 50 c4 44 98 68 41 c3 2e e3 1d ef d0 5f 05 00 00 00 02 00 00 00 0b 00 00 00 57 00 4d 00 5f 00 7a 00 61 00 70 00 70 00 61 00 63 00 6f 00 72 00 00 00 05 02 74 07 11 0a 00 00 05 00 00 00 2d 6e cb 62 00 00 00 00 0f 00 00 00 50 6f 63 6b 65 74 50 43 00 53 53 44 4b 00 00 07 00 00 00 57 49 5a 41 32 30 30 00 02 00 00 00 05 00 00 00 02 00 00 00 05 00 00 00 02 00 00 00 00 00 00 00 10 00 00 00 0c 00 00 00 5d 00 00 00 01 00 00 00
Jan 27 14:42:40 RJZ-LNX odccm[28560]: DEBUG: extradata:
Jan 27 14:42:40 RJZ-LNX odccm[28560]: DEBUG: 10 00 00 00 0c 00 00 00 5d 00 00 00 01 00 00 00
Jan 27 14:42:40 RJZ-LNX odccm[28560]: Message: device_info_received: registering object path '/org/synce/odccm/Device/_5081EAF1_44C4_6898_41C3_2EE31DEFD05F_'
I'll try later some cool apps, if any...
EDIT: After poking around in the driver code and comparing results of different camera apps, the following seems to be fact:
1. The driver only supports picture format JPEG (at least on its external interface). So ALL camera apps will get a jpeg from the driver.
2. The driver is always using 2x2 chroma subsampling (which is the main reason for the "poor"(?) image quality).
3. The quality of the compression can be adjusted by using the standard API call CameraParamter.setJpegQuality(0-100). The driver default seems to be 85.
4. However, after several testshots i can't make out any visual difference between the shots made with standard or 100% compression. Technically the 100% version uses better huffmann and quantation tables but this doesn't seem to effect the visual quality.
5. libmmjpeg.so is used for compression (an undocumented qcom jpeg lib). I had no success so far getting better results from the lib. There are some functions like "jpege_get_default_config" which seem the perfect place for patching, but i was unable to figure out the meaning of the various parameters.
6. libcald*.so is used for picture processing (image stablizing, postprocessing etc), so this would be the place for manipulations of the postprocessing pipeline.
6. Third party camera apps like "camera360", "camera fx", etc are unable to produce better compression results (though they seem to). In fact, f.e. camera360 is using the standard driver jpeg compression when set to 100% and is reencoding(!!) the jpeg when set to anything less then 100% (which means the jpeg is probably bigger after reencoding but will be never be better as the source was already crippled. Reencoding also can add several new compression artifacts.) They still might be able to produce better pictures by chosing better parameters for wb,ev... though.
7. The reason for "camera not found" with the modded apk was the some missing permissions. I already did a new apk which could be installed side-by-side with the standard app (i renamed the package structure), but until i find some way to get more quality from the driver releasing/maintaining it would be pointless. For the same reason i removed the old apk from the post.
Here is the blueprint to do the mod yourself (f.e. for other roms/devices):
Code:
You need apktool, SignApk, zipalign (search via forum).
- Copy system/app/SemcCameraUI.apk to your pc
- Copy system/framework/SemcGenericUxpRes.apk to your pc
- Copy system/framework/framework-res.apk to your pc
- apktool if framework-res.apk
- apktool if SemcGenericUxpRes.apk
- apktool d SemcCameraUI.apk
- find file "CameraController.smali" in extraced folder "SemcCameraUI\smali\com\sonyericsson\android\camera"
- insert these two lines at line 994[2.3.4 stock] (next line after "setRotation")
const/16 v1, 0x64
invoke-virtual {v0, v1}, Landroid/hardware/Camera$Parameters;->setJpegQuality(I)V
- rename the folder camera to cameraX and change all occurences of "com/sonyericsson/android/camera" to "com/sonyericsson/android/cameraX" in all files. Do the same for "com.sonyericcson.android.camera".
- choose a new name for the app (like "Camera 100") and change all references in res/values*/string.xml.
- rename the folder SemcCameraUI to SemcCameraX
- apktool b SemcCameraX
- java -jar SignApk.jar certificate.pem key.pk8 <your new SemcCameraX.apk> signed-SemcCameraX.apk
- zipalign -v 4 signed-SemcCameraX.apk SemcCameraX.apk
- install apk
- transform apk to system app (f.e. using Titanium Backup), otherwise you can't open camera device
APK attached (EDIT: removed)
Example pics:
Stock
JpegSnoopResult:
Code:
JPEGsnoop 1.5.2 by Calvin Hass
http://www.impulseadventure.com/photo/
-------------------------------------
Filename: [C:\Dokumente und Einstellungen\games\Eigene Dateien\Dropbox\privat\telefon\stock.JPG]
Filesize: [832205] Bytes
Start Offset: 0x00000000
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP1 (xFFE1) ***
OFFSET: 0x00000002
length = 7612
Identifier = [Exif]
Identifier TIFF = 0x[4D4D002A 00000008]
Endian = Motorola (big)
TAG Mark x002A = 0x002A
EXIF IFD0 @ Absolute 0x00000014
Dir Length = 0x000A
[Make ] = "Sony Ericsson"
[Model ] = "MT15i"
[Orientation ] = Row 0: top, Col 0: left
[XResolution ] = 72/1
[YResolution ] = 72/1
[ResolutionUnit ] = Inch
[Software ] = "4.0.1.A.0.283_2d_f200"
[DateTime ] = "2011:10:18 13:07:41"
[YCbCrPositioning ] = Centered
[ExifOffset ] = @ 0x00D4
Offset to Next IFD = 0x00000270
EXIF IFD1 @ Absolute 0x0000027C
Dir Length = 0x0007
[Compression ] = JPEG
[XResolution ] = 72/1
[YResolution ] = 72/1
[ResolutionUnit ] = Inch
[JpegIFOffset ] = @ +0x02DA = @ 0x02E6
[JpegIFByteCount ] = 6874
Offset to Next IFD = 0x00000000
EXIF SubIFD @ Absolute 0x000000E0
Dir Length = 0x0018
[ExposureTime ] = 10/500 s
[FNumber ] = F2.4
[ISOSpeedRatings ] = 160
[ExifVersion ] = 02.20
[DateTimeOriginal ] = "2011:10:18 13:07:41"
[DateTimeDigitized ] = "2011:10:18 13:07:41"
[ComponentsConfiguration ] = [Y Cb Cr .]
[ShutterSpeedValue ] = 564/100
[ExposureBiasValue ] = 0.00 eV
[MeteringMode ] = CenterWeightedAverage
[LightSource ] = unknown
[Flash ] = Flash did not fire
[FocalLength ] = 4 mm
[FlashPixVersion ] = 01.00
[ColorSpace ] = sRGB
[ExifImageWidth ] = 3264
[ExifImageHeight ] = 2448
[ExifInteroperabilityOffset ] = @ 0x0252
[CustomRendered ] = Normal process
[ExposureMode ] = Auto exposure
[WhiteBalance ] = Auto white balance
[DigitalZoomRatio ] = 100/100
[SceneCaptureType ] = Standard
[SubjectDistanceRange ] = 0
EXIF InteropIFD @ Absolute 0x0000025E
Dir Length = 0x0002
[InteroperabilityIndex ] = "R98"
[InteroperabilityVersion ] = 01.00
*** Marker: DQT (xFFDB) ***
Define a Quantization Table.
OFFSET: 0x00001DC0
Table length = 132
----
Precision=8 bits
Destination ID=0 (Luminance)
DQT, Row #0: 4 3 3 4 6 10 13 16
DQT, Row #1: 3 3 4 5 7 15 16 14
DQT, Row #2: 4 3 4 6 10 15 18 15
DQT, Row #3: 4 4 6 8 13 23 21 16
DQT, Row #4: 5 6 10 15 18 28 27 20
DQT, Row #5: 6 9 14 17 21 27 29 24
DQT, Row #6: 13 17 20 23 27 31 31 26
DQT, Row #7: 19 24 25 25 29 26 27 26
Approx quality factor = 86.93 (scaling=26.13 variance=1.22)
----
Precision=8 bits
Destination ID=1 (Chrominance)
DQT, Row #0: 4 5 6 12 26 26 26 26
DQT, Row #1: 5 5 7 17 26 26 26 26
DQT, Row #2: 6 7 15 26 26 26 26 26
DQT, Row #3: 12 17 26 26 26 26 26 26
DQT, Row #4: 26 26 26 26 26 26 26 26
DQT, Row #5: 26 26 26 26 26 26 26 26
DQT, Row #6: 26 26 26 26 26 26 26 26
DQT, Row #7: 26 26 26 26 26 26 26 26
Approx quality factor = 86.91 (scaling=26.18 variance=0.37)
*** Marker: SOF0 (Baseline DCT) (xFFC0) ***
OFFSET: 0x00001E46
Frame header length = 17
Precision = 8
Number of Lines = 2448
Samples per Line = 3264
Image Size = 3264 x 2448
Raw Image Orientation = Landscape
Number of Img components = 3
Component[1]: ID=0x01, Samp Fac=0x22 (Subsamp 1 x 1), Quant Tbl Sel=0x00 (Lum: Y)
Component[2]: ID=0x02, Samp Fac=0x11 (Subsamp 2 x 2), Quant Tbl Sel=0x01 (Chrom: Cb)
Component[3]: ID=0x03, Samp Fac=0x11 (Subsamp 2 x 2), Quant Tbl Sel=0x01 (Chrom: Cr)
*** Marker: SOS (Start of Scan) (xFFDA) ***
OFFSET: 0x00001FFD
Scan header length = 12
Number of img components = 3
Component[1]: selector=0x01, table=0x00
Component[2]: selector=0x02, table=0x11
Component[3]: selector=0x03, table=0x11
Spectral selection = 0 .. 63
Successive approximation = 0x00
*** Decoding SCAN Data ***
OFFSET: 0x0000200B
Scan Decode Mode: Full IDCT (AC + DC)
Scan Data encountered marker 0xFFD9 @ 0x000CB2CB.0
Compression stats:
Compression Ratio: 29.09:1
Bits per pixel: 0.83:1
Huffman code histogram stats:
Huffman Table: (Dest ID: 0, Class: DC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 18575 ( 15%)
# codes of length 03 bits: 91405 ( 73%)
# codes of length 04 bits: 6690 ( 5%)
# codes of length 05 bits: 5345 ( 4%)
# codes of length 06 bits: 2710 ( 2%)
# codes of length 07 bits: 123 ( 0%)
# codes of length 08 bits: 0 ( 0%)
# codes of length 09 bits: 0 ( 0%)
# codes of length 10 bits: 0 ( 0%)
# codes of length 11 bits: 0 ( 0%)
# codes of length 12 bits: 0 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 0 ( 0%)
# codes of length 15 bits: 0 ( 0%)
# codes of length 16 bits: 0 ( 0%)
Huffman Table: (Dest ID: 1, Class: DC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 41476 ( 66%)
# codes of length 03 bits: 9744 ( 16%)
# codes of length 04 bits: 5105 ( 8%)
# codes of length 05 bits: 3621 ( 6%)
# codes of length 06 bits: 1970 ( 3%)
# codes of length 07 bits: 474 ( 1%)
# codes of length 08 bits: 34 ( 0%)
# codes of length 09 bits: 0 ( 0%)
# codes of length 10 bits: 0 ( 0%)
# codes of length 11 bits: 0 ( 0%)
# codes of length 12 bits: 0 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 0 ( 0%)
# codes of length 15 bits: 0 ( 0%)
# codes of length 16 bits: 0 ( 0%)
Huffman Table: (Dest ID: 0, Class: AC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 365681 ( 44%)
# codes of length 03 bits: 60853 ( 7%)
# codes of length 04 bits: 247142 ( 30%)
# codes of length 05 bits: 77263 ( 9%)
# codes of length 06 bits: 34012 ( 4%)
# codes of length 07 bits: 28448 ( 3%)
# codes of length 08 bits: 9985 ( 1%)
# codes of length 09 bits: 5945 ( 1%)
# codes of length 10 bits: 2962 ( 0%)
# codes of length 11 bits: 1333 ( 0%)
# codes of length 12 bits: 885 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 0 ( 0%)
# codes of length 15 bits: 97 ( 0%)
# codes of length 16 bits: 1252 ( 0%)
Huffman Table: (Dest ID: 1, Class: AC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 161579 ( 51%)
# codes of length 03 bits: 41566 ( 13%)
# codes of length 04 bits: 50669 ( 16%)
# codes of length 05 bits: 34863 ( 11%)
# codes of length 06 bits: 16596 ( 5%)
# codes of length 07 bits: 3241 ( 1%)
# codes of length 08 bits: 5403 ( 2%)
# codes of length 09 bits: 3115 ( 1%)
# codes of length 10 bits: 1497 ( 0%)
# codes of length 11 bits: 603 ( 0%)
# codes of length 12 bits: 120 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 239 ( 0%)
# codes of length 15 bits: 117 ( 0%)
# codes of length 16 bits: 245 ( 0%)
YCC clipping in DC:
Y component: [<0= 0] [>255= 0]
Cb component: [<0= 0] [>255= 0]
Cr component: [<0= 0] [>255= 0]
RGB clipping in DC:
R component: [<0= 0] [>255= 0]
G component: [<0= 0] [>255= 0]
B component: [<0= 0] [>255= 0]
Average Pixel Luminance (Y):
Y=[119] (range: 0..255)
Brightest Pixel Search:
YCC=[ 1017, -16, -277] RGB=[205,255,251] @ MCU[ 90, 38]
Finished Decoding SCAN Data
Number of RESTART markers decoded: 0
Next position in scan buffer: Offset 0x000CB2CA.2
*** Marker: EOI (End of Image) (xFFD9) ***
OFFSET: 0x000CB2CB
*** Searching Compression Signatures ***
Signature: 01387A14AF75DC6963F040C1239B7DED
Signature (Rotated): 0196457BE1E9E30F00715A3DDE8B160C
File Offset: 0 bytes
Chroma subsampling: 2x2
EXIF Make/Model: OK [Sony Ericsson] [MT15i]
EXIF Makernotes: NONE
EXIF Software: OK [4.0.1.A.0.283_2d_f200]
Modded
JpegSnoopResult:
Code:
JPEGsnoop 1.5.2 by Calvin Hass
http://www.impulseadventure.com/photo/
-------------------------------------
Filename: [C:\Dokumente und Einstellungen\games\Eigene Dateien\Dropbox\privat\telefon\modded.JPG]
Filesize: [2360386] Bytes
Start Offset: 0x00000000
*** Marker: SOI (xFFD8) ***
OFFSET: 0x00000000
*** Marker: APP1 (xFFE1) ***
OFFSET: 0x00000002
length = 7550
Identifier = [Exif]
Identifier TIFF = 0x[4D4D002A 00000008]
Endian = Motorola (big)
TAG Mark x002A = 0x002A
EXIF IFD0 @ Absolute 0x00000014
Dir Length = 0x000A
[Make ] = "Sony Ericsson"
[Model ] = "MT15i"
[Orientation ] = Row 0: top, Col 0: left
[XResolution ] = 72/1
[YResolution ] = 72/1
[ResolutionUnit ] = Inch
[Software ] = "4.0.1.A.0.283_2d_f200"
[DateTime ] = "2011:10:18 13:03:54"
[YCbCrPositioning ] = Centered
[ExifOffset ] = @ 0x00D4
Offset to Next IFD = 0x00000270
EXIF IFD1 @ Absolute 0x0000027C
Dir Length = 0x0007
[Compression ] = JPEG
[XResolution ] = 72/1
[YResolution ] = 72/1
[ResolutionUnit ] = Inch
[JpegIFOffset ] = @ +0x02DA = @ 0x02E6
[JpegIFByteCount ] = 6812
Offset to Next IFD = 0x00000000
EXIF SubIFD @ Absolute 0x000000E0
Dir Length = 0x0018
[ExposureTime ] = 10/640 s
[FNumber ] = F2.4
[ISOSpeedRatings ] = 200
[ExifVersion ] = 02.20
[DateTimeOriginal ] = "2011:10:18 13:03:54"
[DateTimeDigitized ] = "2011:10:18 13:03:54"
[ComponentsConfiguration ] = [Y Cb Cr .]
[ShutterSpeedValue ] = 600/100
[ExposureBiasValue ] = 0.00 eV
[MeteringMode ] = CenterWeightedAverage
[LightSource ] = unknown
[Flash ] = Flash did not fire
[FocalLength ] = 4 mm
[FlashPixVersion ] = 01.00
[ColorSpace ] = sRGB
[ExifImageWidth ] = 3264
[ExifImageHeight ] = 2448
[ExifInteroperabilityOffset ] = @ 0x0252
[CustomRendered ] = Normal process
[ExposureMode ] = Auto exposure
[WhiteBalance ] = Auto white balance
[DigitalZoomRatio ] = 100/100
[SceneCaptureType ] = Standard
[SubjectDistanceRange ] = 0
EXIF InteropIFD @ Absolute 0x0000025E
Dir Length = 0x0002
[InteroperabilityIndex ] = "R98"
[InteroperabilityVersion ] = 01.00
*** Marker: DQT (xFFDB) ***
Define a Quantization Table.
OFFSET: 0x00001D82
Table length = 132
----
Precision=8 bits
Destination ID=0 (Luminance)
DQT, Row #0: 1 1 1 1 1 2 3 4
DQT, Row #1: 1 1 1 1 2 3 4 3
DQT, Row #2: 1 1 1 1 2 3 4 3
DQT, Row #3: 1 1 1 2 3 5 5 4
DQT, Row #4: 1 1 2 3 4 7 6 5
DQT, Row #5: 1 2 3 4 5 6 7 6
DQT, Row #6: 3 4 5 5 6 7 7 6
DQT, Row #7: 4 6 6 6 7 6 6 6
Approx quality factor = 96.95 (scaling=6.11 variance=1.09)
----
Precision=8 bits
Destination ID=1 (Chrominance)
DQT, Row #0: 1 1 1 3 6 6 6 6
DQT, Row #1: 1 1 2 4 6 6 6 6
DQT, Row #2: 1 2 3 6 6 6 6 6
DQT, Row #3: 3 4 6 6 6 6 6 6
DQT, Row #4: 6 6 6 6 6 6 6 6
DQT, Row #5: 6 6 6 6 6 6 6 6
DQT, Row #6: 6 6 6 6 6 6 6 6
DQT, Row #7: 6 6 6 6 6 6 6 6
Approx quality factor = 96.99 (scaling=6.01 variance=0.24)
*** Marker: SOF0 (Baseline DCT) (xFFC0) ***
OFFSET: 0x00001E08
Frame header length = 17
Precision = 8
Number of Lines = 2448
Samples per Line = 3264
Image Size = 3264 x 2448
Raw Image Orientation = Landscape
Number of Img components = 3
Component[1]: ID=0x01, Samp Fac=0x22 (Subsamp 1 x 1), Quant Tbl Sel=0x00 (Lum: Y)
Component[2]: ID=0x02, Samp Fac=0x11 (Subsamp 2 x 2), Quant Tbl Sel=0x01 (Chrom: Cb)
Component[3]: ID=0x03, Samp Fac=0x11 (Subsamp 2 x 2), Quant Tbl Sel=0x01 (Chrom: Cr)
*** Marker: SOS (Start of Scan) (xFFDA) ***
OFFSET: 0x00001FBF
Scan header length = 12
Number of img components = 3
Component[1]: selector=0x01, table=0x00
Component[2]: selector=0x02, table=0x11
Component[3]: selector=0x03, table=0x11
Spectral selection = 0 .. 63
Successive approximation = 0x00
*** Decoding SCAN Data ***
OFFSET: 0x00001FCD
Scan Decode Mode: Full IDCT (AC + DC)
Scan Data encountered marker 0xFFD9 @ 0x00240440.0
Compression stats:
Compression Ratio: 10.19:1
Bits per pixel: 2.36:1
Huffman code histogram stats:
Huffman Table: (Dest ID: 0, Class: DC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 4567 ( 4%)
# codes of length 03 bits: 87561 ( 70%)
# codes of length 04 bits: 9569 ( 8%)
# codes of length 05 bits: 8150 ( 7%)
# codes of length 06 bits: 6817 ( 5%)
# codes of length 07 bits: 5323 ( 4%)
# codes of length 08 bits: 2671 ( 2%)
# codes of length 09 bits: 190 ( 0%)
# codes of length 10 bits: 0 ( 0%)
# codes of length 11 bits: 0 ( 0%)
# codes of length 12 bits: 0 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 0 ( 0%)
# codes of length 15 bits: 0 ( 0%)
# codes of length 16 bits: 0 ( 0%)
Huffman Table: (Dest ID: 1, Class: DC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 16291 ( 26%)
# codes of length 03 bits: 13190 ( 21%)
# codes of length 04 bits: 13075 ( 21%)
# codes of length 05 bits: 8920 ( 14%)
# codes of length 06 bits: 5109 ( 8%)
# codes of length 07 bits: 3357 ( 5%)
# codes of length 08 bits: 1935 ( 3%)
# codes of length 09 bits: 493 ( 1%)
# codes of length 10 bits: 54 ( 0%)
# codes of length 11 bits: 0 ( 0%)
# codes of length 12 bits: 0 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 0 ( 0%)
# codes of length 15 bits: 0 ( 0%)
# codes of length 16 bits: 0 ( 0%)
Huffman Table: (Dest ID: 0, Class: AC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 1073745 ( 47%)
# codes of length 03 bits: 202328 ( 9%)
# codes of length 04 bits: 473414 ( 21%)
# codes of length 05 bits: 235823 ( 10%)
# codes of length 06 bits: 102316 ( 4%)
# codes of length 07 bits: 91894 ( 4%)
# codes of length 08 bits: 43153 ( 2%)
# codes of length 09 bits: 29245 ( 1%)
# codes of length 10 bits: 16204 ( 1%)
# codes of length 11 bits: 6722 ( 0%)
# codes of length 12 bits: 879 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 0 ( 0%)
# codes of length 15 bits: 82 ( 0%)
# codes of length 16 bits: 5813 ( 0%)
Huffman Table: (Dest ID: 1, Class: AC)
# codes of length 01 bits: 0 ( 0%)
# codes of length 02 bits: 335655 ( 34%)
# codes of length 03 bits: 167892 ( 17%)
# codes of length 04 bits: 200170 ( 20%)
# codes of length 05 bits: 149402 ( 15%)
# codes of length 06 bits: 63901 ( 7%)
# codes of length 07 bits: 16446 ( 2%)
# codes of length 08 bits: 21831 ( 2%)
# codes of length 09 bits: 14265 ( 1%)
# codes of length 10 bits: 4147 ( 0%)
# codes of length 11 bits: 2228 ( 0%)
# codes of length 12 bits: 271 ( 0%)
# codes of length 13 bits: 0 ( 0%)
# codes of length 14 bits: 881 ( 0%)
# codes of length 15 bits: 689 ( 0%)
# codes of length 16 bits: 744 ( 0%)
YCC clipping in DC:
Y component: [<0= 0] [>255= 0]
Cb component: [<0= 0] [>255= 0]
Cr component: [<0= 0] [>255= 0]
RGB clipping in DC:
R component: [<0= 0] [>255= 0]
G component: [<0= 0] [>255= 0]
B component: [<0= 0] [>255= 0]
Average Pixel Luminance (Y):
Y=[120] (range: 0..255)
Brightest Pixel Search:
YCC=[ 1010, 44, -290] RGB=[202,255,255] @ MCU[ 92, 37]
Finished Decoding SCAN Data
Number of RESTART markers decoded: 0
Next position in scan buffer: Offset 0x00240440.0
*** Marker: EOI (End of Image) (xFFD9) ***
OFFSET: 0x00240440
*** Searching Compression Signatures ***
Signature: 010564D93F295ADB889B91604DC82EE1
Signature (Rotated): 014302FE54745F4DBB58A0D51CDC66BD
File Offset: 0 bytes
Chroma subsampling: 2x2
EXIF Make/Model: OK [Sony Ericsson] [MT15i]
EXIF Makernotes: NONE
EXIF Software: OK [4.0.1.A.0.283_2d_f200]
For me it seems that image quality is slightly improved (less compression artifacts). But there is still some big limitation as the driver seems to use 2x2 chroma subsampling (see http://wwwimpulseadventurecom/photo/chroma-subsampling.html for technical details). I will have to write a little tool to see if the driver is capable of other formats...
Frank
Reserved...
If you like the mod i can do a 2.3.3 version and/or try a 2.3.4 to 2.3.3 backport (but i will need someone for testing as i don't want to change my rom).
Nice. I hope to be able to test it tomorrow.
Sent from my Mt15i using Opera Mobile.
not working on my Neo 2.3.4. say camera not available. I set permissions writhe.
not work on my neo 2.3.4 , i have set permissions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also not working
(the same as MaxMedia)
I suppose that you need to give a framework's apk and a semccameraUI apk too
Sent from my Xperiã ÑeØ using XDA app
Donate to my paypal acc. if I helped you & if u can't, atleast hit the thanx button
Hmm, thats strange.
Lets verify a few things:
- you have a Neo (not Neo V) on stock 2.3.4 GENERIC (fs WORLD-1-8_4.0.1.A.0.283), rooted
- Camera was not running (task stopped)
- you did replace /system/app/SemcCameraUI.apk
- permissions are rw-r--r--, filesize 1.881.049, owner system, group sdcard_rw
Now, regarding the error:
- Were you able to start the camera app? Is the app not found(old shortcuts will not work) or is the error coming from the app ?
You can try to run(install) the apk after it is installed. I did this accidently a few times so i am not sure if this is neccesarry to get it to work. If the app is not finding the camera(driver) is think something is not correctly initialized.
If it's still not working you might try doing the mod yourself (see blueprint).
here it does not work, too...
btw. isnt 90% or 95% enough ? what is the default ?
i dont need 4mb pics . 1,5mb instead of 0.7mb would be fine ;o)
inteks said:
here it does not work, too...
btw. isnt 90% or 95% enough ? what is the default ?
i dont need 4mb pics . 1,5mb instead of 0.7mb would be fine ;o)
Click to expand...
Click to collapse
You've got an 8 GB card free for that i suppose
Sent from my Xperiã ÑeØ using XDA app
Donate to my paypal acc. if I helped you & if u can't, atleast hit the thanx button
frank_harmann said:
Hmm, thats strange.
Lets verify a few things:
- you have a Neo (not Neo V) on stock 2.3.4 GENERIC (fs WORLD-1-8_4.0.1.A.0.283), rooted
- Camera was not running (task stopped)
- you did replace /system/app/SemcCameraUI.apk
- permissions are rw-r--r--, filesize 1.881.049, owner system, group sdcard_rw
Now, regarding the error:
- Were you able to start the camera app? Is the app not found(old shortcuts will not work) or is the error coming from the app ?
You can try to run(install) the apk after it is installed. I did this accidently a few times so i am not sure if this is neccesarry to get it to work. If the app is not finding the camera(driver) is think something is not correctly initialized.
If it's still not working you might try doing the mod yourself (see blueprint).
Click to expand...
Click to collapse
For the verification step, i did evrything-Verified
Error is- camera not available and 3rd step about reinstalling, I'll do that when I'll be free and then give feedback
Sent from my Xperiã ÑeØ using XDA app
Donate to my paypal acc. if I helped you & if u can't, atleast hit the thanx button
inteks said:
here it does not work, too...
btw. isnt 90% or 95% enough ? what is the default ?
i dont need 4mb pics . 1,5mb instead of 0.7mb would be fine ;o)
Click to expand...
Click to collapse
I totally agree, I'd say go with 90 or even 85, it reduces size a lot and it almost doesn't affect the quality, at least it is what most picture software does in the pc.
We could compare.
I don't know what settings had done Sony, I see to much noise and poor detail in my pictures, but I suspect they could be better.
frank_harmann said:
Stock
Modded
Click to expand...
Click to collapse
It's hard to notice actual visual improvements in your sample pic since even the stock settings took a really good picture. Perhaps try taking a pic of something where the stock app doesn't do as well (something further away than a mostly macro shot) and then take a modded shot and see if it's any better.
nexus2515 said:
You've got an 8 GB card free for that i suppose
Sent from my Xperiã ÑeØ using XDA app
Donate to my paypal acc. if I helped you & if u can't, atleast hit the thanx button
Click to expand...
Click to collapse
if have 32gb card in my phone but i've till now more than 1000 photos
my picturebackup at home with all pics is allready more then 20gb (only pics!!)
pls dont waste space if it doesnt improve quality ;o)
SCHUMI_4EVER said:
It's hard to notice actual visual improvements in your sample pic since even the stock settings took a really good picture. Perhaps try taking a pic of something where the stock app doesn't do as well (something further away than a mostly macro shot) and then take a modded shot and see if it's any better.
Click to expand...
Click to collapse
You mean, leave the house
Well, as i am interested to see if this really improves anything i will try to do some shots outside using stock, modded and Camera360.
Btw, if anyone has a max quality photo from Camera360, Camera Zoom FX or Vignette taken with the Neo/Arc i would like to run it through JpegSnoop in order to see if these have different chroma subsampling.
Regarding the compression i could easily make versions with different settings(or try to make it configurable, which is a bit tricky only having smali code).
Regarding the installation problem i am not sure where the error is. If anyone would be willing to do the easy blueprint steps on there own(not using the provided apk) this might enlighten me
EDIT: Please try to wipe the camera settings. This might solve the problem. (Settings->Applications->Manage Applications->All->Camera->Delete Data)
Ok, i just wrote a small test program to see what formats are supported by the driver.
Bad luck: only JPEG is supported (default compression is 85%)
This means in order to get rid of the 2x2 chroma subsampling the driver itself has to be modded (its even possible that the code is in firmware or limited by hardware jpeg compression).
So at the moment the best i can archieve at apk-level is setting the compression level up to 100%.
Btw, does anybody know which are the driver files for the cam?
wiping data does not help.
i tryed to do the mod for myself and got the same error ?!?
btw the codeline was on mine at 999 and not at 994 .....
im on 2.3.4 stock
Chaotic behaviour is difficult to reproduce
However, just hold on a bit, i am currently deeper in the rabbit hole and trying to mod the camdrive itself (atleast i already figured out places of the quantation and diffie huffman tables and that the driver can either use the dsp chip for hw-jpeg compression or fall back to sw-jpeg compression.) I will have to poke around a bit after i reanimated my phone (got a bootloop by a wrong change to the system files Well, at least i now can switch to doomkernel while in the process of fixing...)
Well, if you are playing with the driver, can't you edit night mode? Current exposure time is 1sec, which is short... It should be longer, at least 10sec...
vignette sample
frank_harmann said:
You mean, leave the house
Well, as i am interested to see if this really improves anything i will try to do some shots outside using stock, modded and Camera360.
Btw, if anyone has a max quality photo from Camera360, Camera Zoom FX or Vignette taken with the Neo/Arc i would like to run it through JpegSnoop in order to see if these have different chroma subsampling.
Regarding the compression i could easily make versions with different settings(or try to make it configurable, which is a bit tricky only having smali code).
Regarding the installation problem i am not sure where the error is. If anyone would be willing to do the easy blueprint steps on there own(not using the provided apk) this might enlighten me
EDIT: Please try to wipe the camera settings. This might solve the problem. (Settings->Applications->Manage Applications->All->Camera->Delete Data)
Click to expand...
Click to collapse
here comes the vignette sample from my neoView attachment 2011-10-22-17-34-22-154.zip
Hello, I've been reading the thread about BinExtractor and it seems to work with original TOT firmwares that now we can download using some nice methods (like going to a url and putting the IMEI or there's even an APP that does the same).
In my case I'm trying with 10B_00.tot for my E431g
Now, the latest binextractor seems to properly read the magic numbers from my tot file header but it's not able to extract the img files from it.
So I have already asked the developer to add my model to the supported devices but I would like to have more understanding of the TOT file headers so we could develop our own apps or even do things manually.
Does anyone have any information on how to better understand those headers it'd be really nice. So far I got to the part of "reading the first datablock" from the file but I don't really know what the app does with those (as follows):
Code:
/*SET FIRST DATABLOCK*/
dataBlock.blockOff = 0x2010;
dataBlock.blockSize = 12;
dataBlock.numItems = 4;
dataBlock.items = calloc(sizeof(Item), 4);
dataBlock.items[0].type = DISK_OFF;
dataBlock.items[0].size = 4;
dataBlock.items[1].type = FILE_OFF;
dataBlock.items[1].size = 4;
dataBlock.items[2].type = FILE_SIZE;
dataBlock.items[2].size = 4;
dataBlock.items[3].type = SKIP;
dataBlock.items[3].size = 4;
I have attached the mentioned datablock, the red-square is that 0x2010 offset start.
@xonar_ maybe you could give us some explanation of what those header parts mean and how can we know what to do depending on the differences. Here I'm trying to concentrate on L3 II header files.
Thanks to all in advance!
binExtractor github: https://github.com/Xonar/LGBinExtractor
method for manually getting the images from the firmware using dd: http://forum.xda-developers.com/showthread.php?t=2071465
get the original firmware using IMEI: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
root-check
Here's a little find I did searching for "ro.secure" inside the TOT
for me it looks like something related to the persist partition with a residing anti-root consistency check.. this is why it would be great to extract all the partitions from the firmware, we need a full check to make sure all this **** is gone before flashing anything to a phone.
cher
Code:
/rct<bh:00>/persist/rct.partition<bh:00>w<bh:00>/system/bin/su<bh:00>/system/xbin/su<bh:00>/system/sbin/su<bh:00>/sbin/su<bh:00>/data/local/tmp/su<bh:00>/system/app/Superuser.apk<bh:00>/system/app/SuperUser.apk<bh:00>/system/app/superuser.apk<bh:00>/data/data/com.noshufou.android.su<bh:00>/data/local/tmp/Superuser.apk<bh:00>/data/local/tmp/SuperUser.apk<bh:00>/data/local/tmp/superuser.apk<bh:00>/system/bin/busybox<bh:00>/system/xbin/busybox<bh:00>/data/local/tmp/busybox<bh:00>/system/<bh:00>/<bh:00>su<bh:00>getprop ro.secure<bh:00>r<bh:00>getprop ro.debuggable<bh:00>sys.rctd.uid<bh:00>1<bh:00>sys.uctd.on<bh:00>0<bh:00>rb<bh:00>wb<bh:00>Not Rooted
[LG RCT v%s]<bh:00>1.0.1224<bh:00>Rooted
<bh:00> LG RCT had been hacked by user.
<bh:00> > LG RCT Flag(backup)
<bh:00> > LG RCT Flag
<bh:00> Not allowed command had been executed.
<bh:00> > su
<bh:00> Permission related property had been changed.
<bh:00> > ro.secure
<bh:00> > ro.debuggable
<bh:00> Mount option had been changed.
<bh:00> > /system
<bh:00> > /
<bh:00> Rooting related file had been installed.
<bh:00> > superuser
<bh:00> > busybox
<bh:00>
[LG RCT v%s]<bh:00>/dev/block/platform/msm_sdcc.3/by-num/p26<bh:00>/persist<bh:00>/dev<bh:00>%s<bh:00>getprop ro.hardware<bh:00>/persist/rct<bh:00>/data/system/lgmdm_root_flag.txt<bh:00>/persist/rct.cfg<bh:00>/sdcard/RCT_security
gattytto said:
Hello, I've been reading the thread about BinExtractor and it seems to work with original TOT firmwares that now we can download using some nice methods (like going to a url and putting the IMEI or there's even an APP that does the same).
In my case I'm trying with 10B_00.tot for my E431g
Now, the latest binextractor seems to properly read the magic numbers from my tot file header but it's not able to extract the img files from it.
So I have already asked the developer to add my model to the supported devices but I would like to have more understanding of the TOT file headers so we could develop our own apps or even do things manually.
Does anyone have any information on how to better understand those headers it'd be really nice. So far I got to the part of "reading the first datablock" from the file but I don't really know what the app does with those (as follows):
Code:
/*SET FIRST DATABLOCK*/
dataBlock.blockOff = 0x2010;
dataBlock.blockSize = 12;
dataBlock.numItems = 4;
dataBlock.items = calloc(sizeof(Item), 4);
dataBlock.items[0].type = DISK_OFF;
dataBlock.items[0].size = 4;
dataBlock.items[1].type = FILE_OFF;
dataBlock.items[1].size = 4;
dataBlock.items[2].type = FILE_SIZE;
dataBlock.items[2].size = 4;
dataBlock.items[3].type = SKIP;
dataBlock.items[3].size = 4;
I have attached the mentioned datablock, the red-square is that 0x2010 offset start.
@xonar_ maybe you could give us some explanation of what those header parts mean and how can we know what to do depending on the differences. Here I'm trying to concentrate on L3 II header files.
Thanks to all in advance!
binExtractor github: https://github.com/Xonar/LGBinExtractor
method for manually getting the images from the firmware using dd: http://forum.xda-developers.com/showthread.php?t=2071465
get the original firmware using IMEI: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
Click to expand...
Click to collapse
9-APPS.img for my E431g:
init.vee3.rc: right at the end of the file, declared as a service
Code:
#Porting Rooting Check Tool
service rctd /system/bin/rctd
class late_start
user root
group root
full tree of 9-APPS.img
Code:
[email protected]:/media/sf_fw/img/tools/apps# tree ./
./
├── charger
├── cupssd.rc
├── data
├── default.prop
├── dev
├── fstab.vee3
├── init
├── init.goldfish.rc
├── init.lge.early.rc
├── init.lge.rc
├── init.lge.usb.sh
├── init.miniOS.rc
├── init.qcom.class_core.sh
├── init.qcom.class_main.sh
├── init.qcom.rc
├── init.qcom.ril.path.sh
├── init.qcom.sh
├── init.qcom.usb.rc
├── init.qcom.usb.sh
├── init.rc
├── init.target.rc
├── init.vee3.rc
├── init.vee3.usb.rc
├── lgdms.fota.rc
├── lgdms.fota_update.rc
├── proc
├── res
│** └── images
│** ├── charger
│** │** ├── battery_0.png
│** │** ├── battery_1.png
│** │** ├── battery_2.png
│** │** ├── battery_3.png
│** │** ├── battery_4.png
│** │** ├── battery_5.png
│** │** ├── battery_charge.png
│** │** └── battery_fail.png
│** ├── chargerimages
│** │** ├── battery_charging_01.png
│** │** ├── battery_charging_02.png
│** │** ├── battery_charging_03.png
│** │** ├── battery_charging_04.png
│** │** ├── battery_charging_05.png
│** │** ├── battery_charging_06.png
│** │** ├── battery_charging_07.png
│** │** ├── battery_charging_08.png
│** │** ├── battery_charging_bg.png
│** │** ├── battery_charging_complete.png
│** │** ├── battery_charging_warning_eng_1.png
│** │** ├── battery_charging_warning_eng_2.png
│** │** ├── battery_charging_warning_jp_1.png
│** │** ├── battery_charging_warning_jp_2.png
│** │** ├── battery_charging_warning_kor_1.png
│** │** ├── battery_charging_warning_kor_2.png
│** │** ├── battery_charging_warning.png
│** │** ├── battery_trickle_ani_01.png
│** │** ├── battery_trickle_ani_02.png
│** │** ├── battery_wait_ani_01.png
│** │** └── battery_wait_ani_02.png
│** └── errorlogo.png
├── sbin
│** ├── adbd
│** ├── brd
│** ├── chargerlogo
│** ├── clearlock
│** ├── cupssd
│** ├── lge_fota
│** ├── make_ext4fs
│** ├── setup_fs
│** ├── skd
│** └── wallpaper
├── skd.rc
├── sys
├── system
├── ueventd.goldfish.rc
├── ueventd.qcom.rc
├── ueventd.rc
└── ueventd.vee3.rc
gattytto said:
Here's a little find I did searching for "ro.secure" inside the TOT
for me it looks like something related to the persist partition with a residing anti-root consistency check.. this is why it would be great to extract all the partitions from the firmware, we need a full check to make sure all this **** is gone before flashing anything to a phone.
cher
Code:
/rct<bh:00>/persist/rct.partition<bh:00>w<bh:00>/system/bin/su<bh:00>/system/xbin/su<bh:00>/system/sbin/su<bh:00>/sbin/su<bh:00>/data/local/tmp/su<bh:00>/system/app/Superuser.apk<bh:00>/system/app/SuperUser.apk<bh:00>/system/app/superuser.apk<bh:00>/data/data/com.noshufou.android.su<bh:00>/data/local/tmp/Superuser.apk<bh:00>/data/local/tmp/SuperUser.apk<bh:00>/data/local/tmp/superuser.apk<bh:00>/system/bin/busybox<bh:00>/system/xbin/busybox<bh:00>/data/local/tmp/busybox<bh:00>/system/<bh:00>/<bh:00>su<bh:00>getprop ro.secure<bh:00>r<bh:00>getprop ro.debuggable<bh:00>sys.rctd.uid<bh:00>1<bh:00>sys.uctd.on<bh:00>0<bh:00>rb<bh:00>wb<bh:00>Not Rooted
[LG RCT v%s]<bh:00>1.0.1224<bh:00>Rooted
<bh:00> LG RCT had been hacked by user.
<bh:00> > LG RCT Flag(backup)
<bh:00> > LG RCT Flag
<bh:00> Not allowed command had been executed.
<bh:00> > su
<bh:00> Permission related property had been changed.
<bh:00> > ro.secure
<bh:00> > ro.debuggable
<bh:00> Mount option had been changed.
<bh:00> > /system
<bh:00> > /
<bh:00> Rooting related file had been installed.
<bh:00> > superuser
<bh:00> > busybox
<bh:00>
[LG RCT v%s]<bh:00>/dev/block/platform/msm_sdcc.3/by-num/p26<bh:00>/persist<bh:00>/dev<bh:00>%s<bh:00>getprop ro.hardware<bh:00>/persist/rct<bh:00>/data/system/lgmdm_root_flag.txt<bh:00>/persist/rct.cfg<bh:00>/sdcard/RCT_security
Click to expand...
Click to collapse
Hi there
gattytto said:
get the original firmware using IMEI: http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=your_imei
Click to expand...
Click to collapse
Thats a nice find
what are you trying to achieve by this doing this (extracting and making kdz files) ? we have cwm and unlocked bootloader we can do all using easy .zip's
anyway i think i have something that you might find useful (also check my thread for more (see sig))
Code:
*---------------------------- PartitionTable Info E430 V10C_00--------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
the attached file is output of sysinternals dbgview.exe while flashing stock v10c to phone e430
Hi, thanks a lot for your repply and the info, I'd like to answer to your question at the bottom of you post:
what I'm trying to do now is to examine all the .img files included inside the latest original .tot available for download from LG, mainly because since the last update it's impossible to root the e431g using vroot or any other 1-click rooting tool.
so far I've been able to unpack recovery and apps img (9-APPS.img and 17-RECOVERY.img) with their kernel and ramdisk.gz.
there are some things that I still don't understand, for example the existense of secundary recovery.img and oemsbl.img, so I have 17-RECOVERY.img, recovery.img, 3-OEMSBL.img and oemsbl.img
also I'm still trying to unpack some of the IMG files since they seem to be some special filesystem like yaffs2 but I haven't found any tool to browse them (didn't try converters 'cause that's not the approach I'm looking for). right now I'm compiling a 3.16-r2 kernel with the yaffs2 module that I tried modding to compile for that kernel (was hard job indeed).
my approach is to try modify the files present in my original downloaded TOT to root and unlock the bootloader to flash them back into my phone, thus trying to avoid bricking the phone.
you use skype or something?
here's a list of what I get:
Code:
10-MODEM_ST1.img: empty
11-MODEM_ST2.img: empty
12-MODEM.img: data
13-MODEM_BACKUP.img: data
14-SYSTEM.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
15-PERSIST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
16-CACHE.img: empty
17-RECOVERY.img: data
18-DRM.img: empty
19-FOTA.img: empty
20-USERDATA.img: empty
21-DLOAD.img: empty
22-BOOT_LOGO_IMAGE.img: data
23-MPT.img: empty
24-ENCRYPT.img: empty
25-CUST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
26-rct.img: empty
2-QCSBL.img: x86 boot sector; partition 1: ID=0x4d, active, starthead 0, startsector 1, 40 sectors; partition 2: ID=0x45, starthead 0, startsector 41, 2048 sectors; partition 3: ID=0x46, starthead 0, startsector 2089, 8192 sectors; partition 4: ID=0x5, starthead 0, startsector 10281, 7501784 sectors, code offset 0x0
3-OEMSBL.img: data
4-EXT.img: x86 boot sector; partition 1: ID=0x47, starthead 0, startsector 120791, 8192 sectors; partition 2: ID=0x5, starthead 0, startsector 1, 1 sectors, extended partition table, code offset 0x0
5-APPSSBL.img: Hitachi SH big-endian COFF object, not stripped
6-WALLPAPER.img: empty
7-MODEM_BACKUP.img: empty
8-misc.img: empty
9-APPS.img: data
oemsbl.img: data
recovery.img: data
also I've seen some info on mounting boot sector files like 4-EXT.img and 2-QCSBL.img but the file systems from those sectors don't seem to get recognized by the mount command.. so I'm guessing there's a filesystem module missing in my linux distro (that's why I'm compiling this other one).
IGGYVIP said:
Thats a nice find
what are you trying to achieve by this doing this (extracting and making kdz files) ? we have cwm and unlocked bootloader we can do all using easy .zip's
anyway i think i have something that you might find useful (also check my thread for more (see sig))
Code:
*---------------------------- PartitionTable Info E430 V10C_00--------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
the attached file is output of sysinternals dbgview.exe while flashing stock v10c to phone e430
Click to expand...
Click to collapse
I see
gattytto said:
Hi, thanks a lot for your repply and the info, I'd like to answer to your question at the bottom of you post:
what I'm trying to do now is to examine all the .img files included inside the latest original .tot available for download from LG, mainly because since the last update it's impossible to root the e431g using vroot or any other 1-click rooting tool.
so far I've been able to unpack recovery and apps img (9-APPS.img and 17-RECOVERY.img) with their kernel and ramdisk.gz.
there are some things that I still don't understand, for example the existense of secundary recovery.img and oemsbl.img, so I have 17-RECOVERY.img, recovery.img, 3-OEMSBL.img and oemsbl.img
also I'm still trying to unpack some of the IMG files since they seem to be some special filesystem like yaffs2 but I haven't found any tool to browse them (didn't try converters 'cause that's not the approach I'm looking for). right now I'm compiling a 3.16-r2 kernel with the yaffs2 module that I tried modding to compile for that kernel (was hard job indeed).
my approach is to try modify the files present in my original downloaded TOT to root and unlock the bootloader to flash them back into my phone, thus trying to avoid bricking the phone.
you use skype or something?
here's a list of what I get:
Code:
10-MODEM_ST1.img: empty
11-MODEM_ST2.img: empty
12-MODEM.img: data
13-MODEM_BACKUP.img: data
14-SYSTEM.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
15-PERSIST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
16-CACHE.img: empty
17-RECOVERY.img: data
18-DRM.img: empty
19-FOTA.img: empty
20-USERDATA.img: empty
21-DLOAD.img: empty
22-BOOT_LOGO_IMAGE.img: data
23-MPT.img: empty
24-ENCRYPT.img: empty
25-CUST.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
26-rct.img: empty
2-QCSBL.img: x86 boot sector; partition 1: ID=0x4d, active, starthead 0, startsector 1, 40 sectors; partition 2: ID=0x45, starthead 0, startsector 41, 2048 sectors; partition 3: ID=0x46, starthead 0, startsector 2089, 8192 sectors; partition 4: ID=0x5, starthead 0, startsector 10281, 7501784 sectors, code offset 0x0
3-OEMSBL.img: data
4-EXT.img: x86 boot sector; partition 1: ID=0x47, starthead 0, startsector 120791, 8192 sectors; partition 2: ID=0x5, starthead 0, startsector 1, 1 sectors, extended partition table, code offset 0x0
5-APPSSBL.img: Hitachi SH big-endian COFF object, not stripped
6-WALLPAPER.img: empty
7-MODEM_BACKUP.img: empty
8-misc.img: empty
9-APPS.img: data
oemsbl.img: data
recovery.img: data
also I've seen some info on mounting boot sector files like 4-EXT.img and 2-QCSBL.img but the file systems from those sectors don't seem to get recognized by the mount command.. so I'm guessing there's a filesystem module missing in my linux distro (that's why I'm compiling this other one).
Click to expand...
Click to collapse
i have tried unpacking .dz before but i was never successful as all of tools are outdated
only way i found to extract the .kdz is flashing it to phone and adb dd and pull from device but for that you need root (did you check the latest vroot ?
anyway i have made tool to dump and name all(skipping the sdcard) partitions from phone(L3 II) found HERE
also i made a tool to list ALL of files in phone in easy to read directory format found HERE*this also includes my filelist.txt for compare in case you want and does not require root
also here is my boot.img unpacked BOOT BROKENDOWN
i think you did not get a chance to read the attached file yet but inside you find that lg flashing software does :
Code:
Skip writing [MODEM_ST1;MODEM_ST2;DRM;MPT;CACHE;USERDATA;MODEM_BACKUP;PERSIST;BOOT_LOGO_IMAGE;] partition
Code:
Size of the [WALLPAPER] partition is zero \tab\par
00000463\tab 717.36279297\tab [4244] [13:16:39] Size of the [MODEM_BACKUP] partition is zero \tab\par
00000464\tab 717.36285400\tab [4244] [13:16:39] Size of the [misc] partition is zero \tab\par
00000465\tab 717.36291504\tab [4244] [13:16:39] Size of the [MODEM_ST1] partition is zero \tab\par
00000466\tab 717.36297607\tab [4244] [13:16:39] Size of the [MODEM_ST2] partition is zero \tab\par
00000467\tab 717.36303711\tab [4244] [13:16:39] Skip writing [MODEM_BACKUP] partition \tab\par
00000468\tab 717.36309814\tab [4244] [13:16:39] Skip writing [PERSIST] partition \tab\par
00000469\tab 717.36315918\tab [4244] [13:16:39] Size of the [CACHE] partition is zero \tab\par
00000470\tab 717.36322021\tab [4244] [13:16:39] Size of the [DRM] partition is zero \tab\par
00000471\tab 717.36328125\tab [4244] [13:16:39] Size of the [FOTA] partition is zero \tab\par
00000472\tab 717.36328125\tab [4244] [13:16:39] Size of the [USERDATA] partition is zero \tab\par
00000473\tab 717.36334229\tab [4244] [13:16:39] Size of the [DLOAD] partition is zero \tab\par
00000474\tab 717.36340332\tab [4244] [13:16:39] Skip writing [BOOT_LOGO_IMAGE] partition \tab\par
00000475\tab 717.36346436\tab [4244] [13:16:39] Size of the [MPT] partition is zero \tab\par
00000476\tab 717.36352539\tab [4244] [13:16:39] Size of the [ENCRYPT] partition is zero \tab\par
00000477\tab 717.36370850\tab [4244] [13:16:39] Size of the [rct] partition is zero \tab\par
it means none of these are inside the .kdz
about kdz could you send me direct link to firmware you are trying to root ?
e430 europe latest is v10c and its easly rootable using vroot so i will try to flash yours and see if i can get success
Hello, before you read my repply, I know you can get some tots (or kdz) from other places, but I will really appreciate you get me a link for the offical KDZ link generation url http://csmg.lgmobile.com:9002/...(and so on). Since I can extract the kdz to .cab, I want to know if yours is actually packed with different headers and if so that will give more info 'bout what tools need to get updated.
I will first answer to your request for the .kdz file I'm working on: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW238195432109876543213/V10B_00.kdz
as for the .kdz file extractor, I have been testing several ones until I got to this one (attached).
run it from a command prompt, can you give me the url produced for yor IMEI from the link I have provided in first post? It would let me accelerate testing for your particular case.
After you use that extractor with -kdz argument, you will get a .cab, open with winrar, you should get a .tot and a .dll file
if you get to extract your own kdz and obtain the .tot proceed as follows:
use LGBinExtractor to unpack the .tot from https://github.com/Xonar/LGBinExtractor, I provide a .exe with code updates to support e431g tot magic and headers..
use the -daph argument with your .tot and you should get output about partitions inside the firmware with this format:
Code:
AP HEADER
----------
Magic Number 0x0 : 44 DD 55 AA
0x8 : 97 4A EB 9F
0xC : 4C 47 45 34
0x10 : 33 31 67 00
0x14 : 00 00 00 00
0x18 : 00 00 00 00
0x1C : 00 00 00 00
0x600 : AA BB 00 CC
0x2000 : 33 EC 55 AA
Number of Partitions 25
PARTITION ENTRIES
-----------------
PARTITION ENTRY
------------
Data Block Name QCSBL
Data Block ID 2
Size on File 1024
File Offset 0
Size on Disk 2089
Disk Offset 0
PARTITION ENTRY
------------
Data Block Name OEMSBL
Data Block ID 3
Size on File 2048
File Offset 1024
Size on Disk 8192
Disk Offset 2089
If you get any error from the command "LGBinExtractor -daph file.tot" instead of the partitions list then you need to use the "LGBinExtractor -ebh file.tot" command to extract a copy of its header and attach it to the LGBinExtractor thread so the author will get the magic headers added to the app in https://github.com/Xonar/LGBinExtractor . If this is the case and you get a .tot from the KDZ but not IMG files from the TOT with LGBinExtractor, besides posting the headers to the author's thread, also upload here your header.bin with the link to your official .kdz so I can make some testing.
Note: in case you get the .tot but it's not supported by lgbinextractor, you can also setup a linux box (win 2012 hyper-v / virtualbox / etc..) and try to make the needed changes, then use that windows makefile I have attached and it will produce a .exe with your changes (or author's added changes in case he didn't share the .exe with the most recent changes you or someone else requested for their devices). You can use the default makefile and test inside the linux box with header.bin file until you get the partitions list, then you can produce the .exe and try unpack the whole .tot in your windows box.
If you can't get the .tot from your official kdz then we need to get the source for the LGExtract (kdz extractor) and make the needed changes in order to support your version.
cheers
http://ul.to/myyrb8ie <- the extractors and the makefile
IGGYVIP said:
i have tried unpacking .dz before but i was never successful as all of tools are outdated
only way i found to extract the .kdz is flashing it to phone and adb dd and pull from device but for that you need root (did you check the latest vroot ?
anyway i have made tool to dump and name all(skipping the sdcard) partitions from phone(L3 II) found HERE
also i made a tool to list ALL of files in phone in easy to read directory format found HERE*this also includes my filelist.txt for compare in case you want and does not require root
also here is my boot.img unpacked BOOT BROKENDOWN
i think you did not get a chance to read the attached file yet but inside you find that lg flashing software does :
Code:
Skip writing [MODEM_ST1;MODEM_ST2;DRM;MPT;CACHE;USERDATA;MODEM_BACKUP;PERSIST;BOOT_LOGO_IMAGE;] partition
Code:
Size of the [WALLPAPER] partition is zero \tab\par
00000463\tab 717.36279297\tab [4244] [13:16:39] Size of the [MODEM_BACKUP] partition is zero \tab\par
00000464\tab 717.36285400\tab [4244] [13:16:39] Size of the [misc] partition is zero \tab\par
00000465\tab 717.36291504\tab [4244] [13:16:39] Size of the [MODEM_ST1] partition is zero \tab\par
00000466\tab 717.36297607\tab [4244] [13:16:39] Size of the [MODEM_ST2] partition is zero \tab\par
00000467\tab 717.36303711\tab [4244] [13:16:39] Skip writing [MODEM_BACKUP] partition \tab\par
00000468\tab 717.36309814\tab [4244] [13:16:39] Skip writing [PERSIST] partition \tab\par
00000469\tab 717.36315918\tab [4244] [13:16:39] Size of the [CACHE] partition is zero \tab\par
00000470\tab 717.36322021\tab [4244] [13:16:39] Size of the [DRM] partition is zero \tab\par
00000471\tab 717.36328125\tab [4244] [13:16:39] Size of the [FOTA] partition is zero \tab\par
00000472\tab 717.36328125\tab [4244] [13:16:39] Size of the [USERDATA] partition is zero \tab\par
00000473\tab 717.36334229\tab [4244] [13:16:39] Size of the [DLOAD] partition is zero \tab\par
00000474\tab 717.36340332\tab [4244] [13:16:39] Skip writing [BOOT_LOGO_IMAGE] partition \tab\par
00000475\tab 717.36346436\tab [4244] [13:16:39] Size of the [MPT] partition is zero \tab\par
00000476\tab 717.36352539\tab [4244] [13:16:39] Size of the [ENCRYPT] partition is zero \tab\par
00000477\tab 717.36370850\tab [4244] [13:16:39] Size of the [rct] partition is zero \tab\par
it means none of these are inside the .kdz
about kdz could you send me direct link to firmware you are trying to root ?
e430 europe latest is v10c and its easly rootable using vroot so i will try to flash yours and see if i can get success
Click to expand...
Click to collapse
gattytto said:
Hello, before you read my repply, I know you can get some tots (or kdz) from other places, but I will really appreciate you get me a link for the offical KDZ link generation url http://csmg.lgmobile.com:9002/...(and so on). Since I can extract the kdz to .cab, I want to know if yours is actually packed with different headers and if so that will give more info 'bout what tools need to get updated.
I will first answer to your request for the .kdz file I'm working on: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW238195432109876543213/V10B_00.kdz
as for the .kdz file extractor, I have been testing several ones until I got to this one (attached).
run it from a command prompt, can you give me the url produced for yor IMEI from the link I have provided in first post? It would let me accelerate testing for your particular case.
After you use that extractor with -kdz argument, you will get a .cab, open with winrar, you should get a .tot and a .dll file
if you get to extract your own kdz and obtain the .tot proceed as follows:
use LGBinExtractor to unpack the .tot from https://github.com/Xonar/LGBinExtractor, I provide a .exe with code updates to support e431g tot magic and headers..
use the -daph argument with your .tot and you should get output about partitions inside the firmware with this format:
Code:
AP HEADER
----------
Magic Number 0x0 : 44 DD 55 AA
0x8 : 97 4A EB 9F
0xC : 4C 47 45 34
0x10 : 33 31 67 00
0x14 : 00 00 00 00
0x18 : 00 00 00 00
0x1C : 00 00 00 00
0x600 : AA BB 00 CC
0x2000 : 33 EC 55 AA
Number of Partitions 25
PARTITION ENTRIES
-----------------
PARTITION ENTRY
------------
Data Block Name QCSBL
Data Block ID 2
Size on File 1024
File Offset 0
Size on Disk 2089
Disk Offset 0
PARTITION ENTRY
------------
Data Block Name OEMSBL
Data Block ID 3
Size on File 2048
File Offset 1024
Size on Disk 8192
Disk Offset 2089
If you get any error from the command "LGBinExtractor -daph file.tot" instead of the partitions list then you need to use the "LGBinExtractor -ebh file.tot" command to extract a copy of its header and attach it to the LGBinExtractor thread so the author will get the magic headers added to the app in https://github.com/Xonar/LGBinExtractor . If this is the case and you get a .tot from the KDZ but not IMG files from the TOT with LGBinExtractor, besides posting the headers to the author's thread, also upload here your header.bin with the link to your official .kdz so I can make some testing.
Note: in case you get the .tot but it's not supported by lgbinextractor, you can also setup a linux box (win 2012 hyper-v / virtualbox / etc..) and try to make the needed changes, then use that windows makefile I have attached and it will produce a .exe with your changes (or author's added changes in case he didn't share the .exe with the most recent changes you or someone else requested for their devices). You can use the default makefile and test inside the linux box with header.bin file until you get the partitions list, then you can produce the .exe and try unpack the whole .tot in your windows box.
If you can't get the .tot from your official kdz then we need to get the source for the LGExtract (kdz extractor) and make the needed changes in order to support your version.
cheers
http://ul.to/myyrb8ie <- the extractors and the makefile
Click to expand...
Click to collapse
quick post
MY CURRENT FIRMWARE
*updating
Code:
F:\>mas -extract E430_TSC_UK.tot
Reading AP Header...
Reading GPT Header...
Does not contain GPT at first data block
Writing Files...
Writing File : 2-QCSBL.img -- DONE --
Writing File : 3-OEMSBL.img -- DONE --
Writing File : 4-EXT.img -- DONE --
Writing File : 5-APPSSBL.img -- DONE --
Writing File : 6-WALLPAPER.img -- DONE --
Writing File : 7-MODEM_BACKUP.img -- DONE --
Writing File : 8-misc.img -- DONE --
Writing File : 9-APPS.img -- DONE --
Writing File : 10-MODEM_ST1.img -- DONE --
Writing File : 11-MODEM_ST2.img -- DONE --
Writing File : 12-MODEM.img -- DONE --
Writing File : 13-MODEM_BACKUP.img -- DONE --
Writing File : 14-SYSTEM.img -- DONE --
Writing File : 15-PERSIST.img -- DONE --
Writing File : 16-CACHE.img -- DONE --
Writing File : 17-RECOVERY.img -- DONE --
Writing File : 18-DRM.img -- DONE --
Writing File : 19-FOTA.img -- DONE --
Writing File : 20-USERDATA.img -- DONE --
Writing File : 21-DLOAD.img -- DONE --
Writing File : 22-BOOT_LOGO_IMAGE.img -- DONE --
Writing File : 23-MPT.img -- DONE --
Writing File : 24-ENCRYPT.img -- DONE --
Writing File : 25-CUST.img -- DONE --
Writing File : 26-rct.img -- DONE --
Finished
IGGYVIP said:
quick post
MY CURRENT FIRMWARE
*updating
Click to expand...
Click to collapse
Almost done, but don't want to use KDZ, but LG FlashTool instead, but it's complaining about the CRC check.. anyone with some debugging skills to help us ollydbg patch the dll/exe to bypass the crc check? or maybe someone knows how this check is being performed?
thanks in advance
also this is killing me inside:
Code:
5-APPSSBL.img: Hitachi SH big-endian COFF object, not stripped
what does this mean? Hitachi SH is SH2 or SH3 or SH4 which is a chip, and this phone has ARM MSM7225A, why does this file get recognized as a SH3/4 instruction set? pleeeeeeeeeeeeeease! someone clarify this for me!!
/cache/log/ua_log.txt
Code:
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: executable_name -> "/tmp/rb_ua"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: config_file -> "/tmp/rb_ua.conf"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: work_dir -> "/cache/workdir"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: log_path -> "/cache/logs/ua_log"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: delta_path -> "(null)"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: exec_path -> "/tmp/exec"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: partitions_list -> "/system/etc/rb_recovery.fstab"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: result_file -> "/cache/result"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: in_ota_zip -> 1
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: fs_installer_types -> ""
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: fs_installer_ordinal -> -1
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: delta_location -> "/cache/delta"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: max_num_process -> 8
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: max_proc_ram -> -1
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: set_boot_to_recovery -> 0
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: raw_delta -> 0
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: in_recovery_kernel -> 1
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: no_reboot -> 1
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: no_ui -> 0
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: part_list_fstab_format -> 0
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: recovery_command -> "rb_ignore"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: wipe_ignore_path -> ""
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: log_history -> 8
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: update_flavor -> "std"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: update_dir -> "/system"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: mount_point -> "/system"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: pul_path -> ""
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: virtual_fs -> "fuse"
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: use_aufs -> 0
< 00 > [ 3121095 ] [pid 364 tid 714684]
Update Agent
Copyright (C) 1999-2015, Red Bend Software. All Rights Reserved.
Version: 10.0.1.12
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend PL: Got parent process' arguments:
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: argv[0] => /tmp/update_binary
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: argv[1] => 3
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: argv[2] => 25
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend UA: argv[3] => /sideload/package.zip
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend PL: In recovery mode, continuing images update
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend PL: Update started
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend PL: Looking for Delta offset in OTA ZIP
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend PL: OTA ZIP is 177085700 bytes long
< 00 > [ 3121095 ] [pid 364 tid 714684] Redbend PL: Found DP in OTA ZIP at offset 0x33
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: Percents ranges:
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 0: 0-1 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 1: 1-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 2: 1-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 3: 1-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 4: 1-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 5: 1-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 6: 1-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 7: 1-18 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 8: 20-0 custom op 1
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 9: 20-74 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 10: 94-5 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 11: 99-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 12: 99-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 13: 99-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 14: 99-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 15: 99-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 16: 99-0 custom op 0
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: 17: 100-0 custom op 1
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: UI Init
< 00 > [ 3121107 ] [pid 364 tid 714684] Redbend PL: Performing modem partition update (op 1)
< 00 > [ 3121110 ] [pid 364 tid 714684] Redbend PL: modem partition update done, ret 0
< 00 > [ 3121110 ] [pid 364 tid 714684] Redbend PL: Performing rpm partition update (op 1)
< 00 > [ 3121113 ] [pid 364 tid 714684] Redbend PL: rpm partition update done, ret 0
< 00 > [ 3121113 ] [pid 364 tid 714684] Redbend PL: Performing sbl1 partition update (op 1)
< 00 > [ 3121115 ] [pid 364 tid 714684] Redbend PL: sbl1 partition update done, ret 0
< 00 > [ 3121115 ] [pid 364 tid 714684] Redbend PL: Performing tz partition update (op 1)
< 00 > [ 3121118 ] [pid 364 tid 714684] Redbend PL: tz partition update done, ret 0
< 00 > [ 3121118 ] [pid 364 tid 714684] Redbend PL: Performing aboot partition update (op 1)
< 00 > [ 3121120 ] [pid 364 tid 714684] Redbend PL: aboot partition update done, ret 0
< 00 > [ 3121120 ] [pid 364 tid 714684] Redbend PL: Performing boot partition update (op 1)
< 00 > [ 3121123 ] [pid 364 tid 714684] Redbend PL: boot partition update done, ret 0
< 00 > [ 3121123 ] [pid 364 tid 714684] Redbend PL: Performing splash partition update (op 1)
< 00 > [ 3121126 ] [pid 364 tid 714684] Redbend PL: splash partition update done, ret 0
< 00 > [ 3121126 ] [pid 364 tid 714684] Redbend PL: Starting system partition scout
< 00 > [ 3121131 ] [pid 364 tid 714684] FS partition delta dump
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: delta_sig - 0x1510e889
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: delta_size - 166746542
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: ver - 82000
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: scout_ver - 80000
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: flags - 0x90000000
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: runtype_flags - 0x284
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: ram_size - 0x514a2
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: sector_size - 0x40000
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: dic_sz - 0x1a0e6
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: compress_sz - 0x5f87
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: min_alloc_ram_use - 0x137
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: ext_info_sz - 2
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_copy - 1954
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_diff - 486
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_insert - 11
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_delete - 3
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_del_dirs - 0
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_dirs - 687
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_del_link - 0
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_link - 0
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_critical_update - 486
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Delta Info: num_critical_insert - 11
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Size mismatch in file /system/bin/app_process32 - expected 0x00003518, received 0x00012664
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Error in verifying source of partition
< 00 > [ 3121131 ] [pid 364 tid 714684] Waiting for all processes to exit...
< 00 > [ 3121131 ] [pid 364 tid 714684] RedBend: Run info - maximum number of simultaneous processes used - 0
< 00 > [ 3121131 ] [pid 364 tid 714684] Redbend PL: system partition scout done, ret 8000013e
< 00 > [ 3121131 ] [pid 364 tid 714684] Redbend PL: Error -2147483330 [No such file or directory] at /disk2/workspace/vRM_Product_UA_Android_Delivery_8.0_git/vcc-10.0.1.12/MloaderPhone/UAL/Linux/User/rb_ua/rb_ua.c:3431
< 00 > [ 3121131 ] [pid 364 tid 714684] Redbend PL: Error -2147483330 [No such file or directory] at /disk2/workspace/vRM_Product_UA_Android_Delivery_8.0_git/vcc-10.0.1.12/MloaderPhone/UAL/Linux/User/rb_ua/rb_ua.c:3758
< 00 > [ 3121131 ] [pid 364 tid 714684] Redbend PL: Error during scout: 318
< 00 > [ 3121131 ] [pid 364 tid 714684] Redbend PL: Update agent terminated
/cache/recovery/log.txt
Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery (pid 208) on Wed Mar 11 20:03:31 1970
recovery filesystem table
=========================
0 /system ext4 /dev/block/bootdevice/by-name/system 0
1 /cache ext4 /dev/block/bootdevice/by-name/cache 0
2 /data ext4 /dev/block/bootdevice/by-name/userdata -16384
3 /sdcard vfat /dev/block/mmcblk1p1 0
4 /boot emmc /dev/block/bootdevice/by-name/boot 0
5 /recovery emmc /dev/block/bootdevice/by-name/recovery 0
6 /misc emmc /dev/block/bootdevice/by-name/misc 0
7 /splash emmc /dev/block/bootdevice/by-name/splash 0
8 /tmp ramdisk ramdisk 0
I:Got arguments from /cache/recovery/command
locale is [pl_PL]
stage is []
reason is [(null)]
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
framebuffer: 0 (540 x 960)
found frames = 7
installing_text: pl (337 x 33 @ 1258)
erasing_text: pl (109 x 33 @ 1258)
no_command_text: pl (162 x 33 @ 1258)
error_text: pl (45 x 33 @ 1258)
Command: "/sbin/recovery" "--update_package=/cache/__FUMO" "--locale=pl_PL"
av.offload.enable=false
mm.enable.qcom_parser=3407871
ro.fm.transmitter=false
ro.qc.sdk.audio.ssr=false
ro.qc.sdk.audio.fluencetype=fluence
ro.sf.lcd_density=240
ro.adb.secure=1
ro.cid=E02
ro.com.google.gmsversion=5.1_r3
ro.com.google.clientidbase=android-bullitt
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.widevine.cachesize=16777216
ro.frp.pst=/dev/block/bootdevice/by-name/config
ro.gps.agps_provider=1
ro.pip.gated=0
ro.sys.fw.bservice_age=5000
ro.sys.fw.bg_apps_limit=16
ro.sys.fw.bservice_limit=5
ro.sys.fw.bservice_enable=true
ro.sys.fw.empty_app_percent=50
ro.sys.fw.use_trim_settings=true
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_enable_memory=1073741824
ro.sys.usb.default.config=diag,serial_smd,rmnet_qti_bam,adb
ro.sys.umsdirtyratio=20
ro.boot.emmc=true
ro.boot.console=ttyHSL0
ro.boot.baseband=msm
ro.boot.hardware=qcom
ro.boot.serialno=ff78d667
ro.boot.cei_hw_id=MP1
ro.boot.cei_rf_id=EU
ro.boot.bootdevice=7824900.sdhci
ro.boot.cei_proj_id=LT32
ro.boot.ceibootmode=0
ro.boot.countrycode=E02
ro.boot.authorized_kernel=true
ro.hwui.text_large_cache_height=2048
ro.phys.mem=1G
ro.qcom.screencolor=1
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=msm8909
ro.build.id=LMY47O
ro.build.date=Sat Feb 6 15:40:45 CST 2016
ro.build.date.utc=1454744445
ro.build.host=vBuild1BT52
ro.build.tags=release-keys
ro.build.type=user
ro.build.user=rdadmin
ro.build.flavor=CatS40-user
ro.build.display.id=LTE_D0201121.0_S40_0.025.00
ro.build.product=CatS40
ro.build.version.sdk=22
ro.build.version.base_os=
ro.build.version.release=5.1
ro.build.version.codename=REL
ro.build.version.software=LTE_D0201121.0_S40_0.025.00
ro.build.version.incremental=1833
ro.build.version.all_codenames=REL
ro.build.version.security_patch=2016-03-01
ro.build.description=msm8909-user 5.1 LMY47O 1833 release-keys
ro.build.fingerprint=Cat/CatS40/CatS40:5.1/LMY47O/LTE_D0201121.0_S40_0.025.00:user/release-keys
ro.build.characteristics=default
ro.config.low_ram=false
ro.config.ringtone=Noises1.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.max_starting_bg=8
ro.config.notification_sound=pixiedust.ogg
ro.dalvik.vm.native.bridge=0
ro.secure=1
ro.vendor.extension_library=libqti-perfd-client.so
ro.zygote=zygote32
ro.carrier=unknown
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.name=CatS40
ro.product.board=msm8909
ro.product.brand=Cat
ro.product.model=S40
ro.product.device=CatS40
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=BullittGroupLimited
ro.baseband=msm
ro.bootmode=unknown
ro.hardware=qcom
ro.opengles.version=196608
ro.qualcomm.cabl=2
ro.revision=0
ro.serialno=ff78d667
ro.telephony.default_network=9
ro.alarm_boot=false
ro.bootloader=unknown
ro.debuggable=0
ro.factorytest=0
ro.setupwizard.mode=OPTIONAL
ro.core_ctl_max_cpu=4
ro.core_ctl_min_cpu=2
ro.use_data_netmgrd=true
ro.cutoff_voltage_mv=3200
dev.pm.dyn_samplingrate=1
drm.service.enabled=true
mmp.enable.3g2=true
net.bt.name=Android
net.change=net.bt.name
rec.playback.conc.disabled=true
ril.subscription.types=NV,RUIM
sys.hwc.gpu_perf_mode=1
sys.audio.init=false
use.voice.path.for.pcm.voip=true
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
rild.libargs=-d /dev/smd0
rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so
audio.dolby.ds2.enabled=false
audio.offload.min.duration.secs=30
audio.offload.buffer.size.kb=64
audio.offload.gapless.enabled=true
debug.sf.hw=1
debug.sf.hwc.canUseABC=0
debug.sf.swaprect=0
debug.egl.hw=1
debug.hwc.dynThreshold=2.5
debug.cpurend.vsync=false
debug.mdpcomp.logs=0
debug.composition.type=dyn
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-http=true
media.stagefright.enable-scan=true
media.stagefright.use-awesome=false
media.stagefright.enable-fma2dp=true
media.stagefright.enable-player=true
media.aac_51_output_enabled=true
voice.voip.conc.disabled=true
voice.record.conc.disabled=true
voice.playback.conc.disabled=true
config.disable_atlas=true
dalvik.vm.isa.arm.features=div
dalvik.vm.heapsize=256m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=6m
dalvik.vm.heapstartsize=14m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.heaptargetutilization=0.75
tunnel.audio.encode=false
persist.mm.sta.enable=1
persist.cne.feature=1
persist.dpm.feature=3
persist.gps.qc_nlp_in_use=1
persist.hwc.enable_vds=1
persist.loc.nlp_name=com.qualcomm.location
persist.sys.usb.config=diag,serial_smd,rmnet_qti_bam,adb
persist.sys.dalvik.vm.lib.2=libart.so
persist.sys.synaptics_dsx.qhd=false
persist.sys.isUsbOtgEnabled=true
persist.data.mode=concurrent
persist.data.netmgrd.qos.enable=true
persist.demo.hdmirotationlock=false
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.audio.fluence.speaker=false
persist.audio.fluence.voicerec=false
persist.audio.fluence.voicecall=true
persist.debug.wfd.enable=1
persist.radio.csvt.enabled=false
persist.radio.calls.on.ims=0
persist.radio.jbims=0
persist.radio.rat_on=combine
persist.radio.multisim.config=dsds
persist.radio.custom_ecc=1
persist.radio.mt_sms_ack=20
persist.radio.sib16_support=1
persist.radio.apm_sim_not_pwdn=1
persist.timed.enable=true
persist.camera.longshot.stages=1
persist.tuning.qdcm=1
persist.denoise.process.plates=0
persist.service.eapd.enable=1
persist.fuse_sdcard=true
keyguard.no_require_sim=true
telephony.lteOnCdmaDevice=1
DEVICE_PROVISIONED=1
Finding update package...
I:Update location: /cache/__FUMO
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1604 bytes; signature 1586 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
Extracting Redbend's Update Agent...
minzip: Extracted 2 file(s)
Running Red Bend Update Agent...
about to run program [/tmp/rb_ua] with 9 args
E:unknown command [RB]
Verifying images...
Error: Source images are different than expectedInfo: Using /cache/logs/ua_log as log file
Update Agent
Copyright (C) 1999-2015, Red Bend Software. All Rights Reserved.
Version: 10.0.1.12
recovery filesystem table
=========================
0 ramdisk ramdisk (null) ""
1 /system ext4 /dev/block/bootdevice/by-name/system (null) "system"
2 /cache ext4 /dev/block/bootdevice/by-name/cache (null) "cache"
3 /data ext4 /dev/block/bootdevice/by-name/userdata (null) "data"
4 /persist ext4 /dev/block/bootdevice/by-name/persist (null) "persist"
5 /boot emmc /dev/block/bootdevice/by-name/boot (null) "boot"
6 /recovery emmc /dev/block/bootdevice/by-name/recovery (null) "recovery"
7 /misc emmc /dev/block/bootdevice/by-name/misc (null) "misc"
8 /modem emmc /dev/block/bootdevice/by-name/modem (null) "modem"
9 /aboot emmc /dev/block/bootdevice/by-name/aboot (null) "aboot"
10 /rpm emmc /dev/block/bootdevice/by-name/rpm (null) "rpm"
11 /sbl1 emmc /dev/block/bootdevice/by-name/sbl1 (null) "sbl1"
12 /splash emmc /dev/block/bootdevice/by-name/splash (null) "splash"
13 /tz emmc /dev/block/bootdevice/by-name/tz (null) "tz"
Info: log file /cache/logs/ua_log is already open
Update agent terminated
run_program: child exited with status 62
script succeeded: result was [15872]
I:Saving locale "pl_PL"
I:Saving locale "pl_PL"
I:Saving locale "pl_PL
I think that's because I've recently rooted phone with KingoRoot which overwritten some executables. Is there any way to bypass that redbend update software and perform an update?
I've also intercepted an update package:
https://drive.google.com/open?id=0B2Myu0CQTYbLWGpjQVlrRFUwaUE
Any ideas?
Anything?
Hi.
According to the specs this box should be able to play x265 ("H.265 HEVC MP-10 at L5.1, up to 4K x 2K at 60fps") but I have found a series of files it won't handle: it stutters or does not start at all. The same file plays just fine on my Linux box using mpv or on my Moto G5Splus using vlc. I've tried vlc also on the mibox, any other decent players that will read from a NAS via SMB?
Running mkvinfo on the first one, this is what I get.
Code:
+ EBML head
|+ EBML version: 1
|+ EBML read version: 1
|+ Maximum EBML ID length: 4
|+ Maximum EBML size length: 8
|+ Document type: matroska
|+ Document type version: 4
|+ Document type read version: 2
+ Segment: size 294353417
|+ Seek head (subentries will be skipped)
|+ EBML void: size 4012
|+ Segment information
| + Timestamp scale: 1000000
| + Multiplexing application: libebml v1.3.1 + libmatroska v1.4.2
| + Writing application: mkvmerge v8.4.0 ('A better way to fly') 64bit
| + Duration: 00:22:50.138000000
| + Date: Wed Feb 17 22:39:11 2016 UTC
| + Segment UID: 0x95 0x69 0x3d 0x29 0x95 0x6a 0x5f 0x93 0xa4 0x3d 0xc0 0xd0 0x35 0xad 0xe7 0xf0
|+ Tracks
| + Track
| + Track number: 1 (track ID for mkvmerge & mkvextract: 0)
| + Track UID: 10006408651203267758
| + Track type: video
| + Lacing flag: 0
| + Minimum cache: 1
| + Codec ID: V_MPEGH/ISO/HEVC
| + Default duration: 00:00:00.041708333 (23.976 frames/fields per second for a video track)
| + Language: und
| + Video track
| + Pixel width: 1920
| + Pixel height: 1080
| + Display width: 1920
| + Display height: 1080
| + Codec's private data: size 118 (HEVC profile: Main @L5.0)
| + Track
| + Track number: 2 (track ID for mkvmerge & mkvextract: 1)
| + Track UID: 6483357143493454263
| + Track type: audio
| + Codec ID: A_AAC
| + Codec's private data: size 2
| + Default duration: 00:00:00.023219954 (43.066 frames/fields per second for a video track)
| + Language: jpn
| + Audio track
| + Sampling frequency: 44100
| + Channels: 2
| + Track
| + Track number: 3 (track ID for mkvmerge & mkvextract: 2)
| + Track UID: 7538420753266538136
| + Track type: subtitles
| + Default track flag: 0
| + Lacing flag: 0
| + Codec ID: S_TEXT/ASS
| + Codec's private data: size 1572
|+ EBML void: size 1007
|+ Attachments
| + Attached
| + File name: OpenSans-Semibold.ttf
| + MIME type: application/x-truetype-font
| + File data: size 221328
| + File UID: 16831001607229270432
|+ Cluster
thanks