Hey guys, I'm trying to extract system.img from a system.img on Windows 7 x64 but when I try using unyaffs, it just says
Code:
Exception: STATUS_ACCESS_VIOLATION at eip=004010A0
eax=E1A04000 ebx=00000003 ecx=00E1A000 edx=00F51DA2 esi=0028CD3C edi=00000000
ebp=0028CCD8 esp=0028CCA0 program=C:\Users\Konstantin\unyaffs\unyaffs.exe, pid 17288, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CCD8 004010A0 (0028CD3D, 00000000, 611F0108, 00401323)
0028CD08 0040139F (00000002, 00F383F0, 00F38278, 00000001)
0028CD68 61006E73 (00000000, 0028CDA4, 61006720, 7EFDE000)
End of stack trace
Anyone got an idea?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Related
Hi everyone,
I am new here on the forum, and the Streak is my very first Android phone. Just wanted to quickly say I really enjoy the community here and I like how everyone tries to help each other.
I noticed that a lot of people have been having problems with Camera forced close issues, which is what I've been experiencing as well. Please mind that this is my first Android phone, and my understanding of Linux is very limited.
I thought I'd post my findings so far in the forced close issues I've been experiencing. Here are some of what I think are the culprits behind the forced close:
Main Log:
1. First it tries to set unsupported parameters for the audio input, followed by more failed attempts to set other parameters
Code:
11-21 02:00:11.475 E/audio_input( 91): unsupported parameter:
x-pvmf/media-input-node/cap-config-interface;valtype=key_specific_value
11-21 02:00:11.475 E/audio_input( 91): VerifyAndSetParameter failed
2. Big Fail! It tries to load what looks to be a video encoder, and can't find it:
Code:
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.qcom.video.encoder.mpeg4 handle, try another component if available
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.PV.mpeg4enc handle, try another component if available
11-21 02:00:11.525 E/AuthorDriver( 91): Command 13 completed with error -17
11-21 02:00:11.535 E/MediaRecorder( 754): prepare failed: -17
11-21 02:00:11.535 E/videocamera( 754): prepare failed for /mnt/sdcard/DCIM/Camera/VID_20101121_020011.3gp
3. Dalvik Virtual Machine pops up an error, and throws it at Android for error handling:
Code:
11-21 02:00:11.545 F/dalvikvm( 754): Exception!!! threadid=1: thread exiting with uncaught exception (group=0x4001d7d8)
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:1297)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.access$300(VideoCamera.java:99)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera$MainHandler.handleMessage(VideoCamera.java:300)
Events Log:
1. Pretty straightforward -- video camera -- problem returns to android for handling during use of Media Recorder?
Code:
11-21 02:00:11.575 I/am_crash( 148): [754,com.android.camera,48709,java.io.IOException,prepare failed.,MediaRecorder.java,-2]
11-21 02:00:11.585 I/am_finish_activity( 148): [1193151496,8,com.android.camera/.VideoCamera,crashed]
11-21 02:00:11.585 I/am_pause_activity( 148): [1193151496,com.android.camera/.VideoCamera]
11-21 02:00:12.095 I/am_resume_activity( 148): [1190436808,2,com.dell.launcher/.Launcher]
System Log:
1. Same below -- start video camera, crash, Android handles the "oh no"s...
Code:
cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.android.camera/.Camera }
11-21 02:00:10.445 I/ActivityManager( 148): Starting activity: Intent { flg=0x4000000 cmp=com.android.camera/.VideoCamera (has extras) }
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
I've also attached the processes log, processesthread log, and system.prop files for reference (I removed all wifi and carrier information at the bottom of the system.prop, but I don't think it's relevant)
I think the main cause of the crash is the media recorder trying to set unsupported parameters and missing video encoder. Not sure though. Any assistance would be greatly appreciated -- I am still looking into the problems, and will get back to everyone on my findings.
Good job...Guess the codec might also be dealing with audio and the bad parm is caused by the unregistered/missing codec? [noob]
Yes - I think definitely there were some serious problems with updating it from a non-00 baseband version.
I think dependencies are missing/broken from either updating from a non 00 baseband version or the flashboot method itself. Those with 00 baseband have it easier, as they already have all the dependencies and can upgrade using the
"copy package to /sdcard/update.pkg" method.
I gave up trying to find the dependencies that were broken, instead went the "downgrading, converting to baseband 00 version and upgrading back to Froyo" method.
I've finally got everything working (including 720p recording) with a combination of Homeiss' "How To Install Official Dell 2.2 Upgrade.pkg" and Geek78's "How to go back from 21 to 00 builds" guide with a little alteration suggested by llecaroz (from modaco forum).
I think this downgrade first to Baseband 00 first than upgrade should fix all problems. The trick is to downgrade to downgrade to 1.6 that matches your baseband (21,31) first! In my case, I had a baseband 21 version.
Suggestions:
- I suggest to downgrade using Geek78's guide first (because, based on my experience, downgrading from 21 2.1 -> 00 1.6 ends up with DELL forever logo).
- If you end up with a "FOTA version error" thingy, you need to flash with a different recovery file (it changes the recovery version from 21 to 00)
- If getting "flash_image: not found" error, it means you are missing the binary. Get it from cyanogen.
Good luck with Homeiss' and Geek78's guide.
I can re-compile a more comprehensive guide, but I think I am unable to place links in here.
If you have upgraded the fastboot way (with the 3 files Stephen provided) You will have FCs on 720p recording! I have downgraded mine to 6267 and then upgraded with the pkg file! Now 720p works perfect!
While i'm extracting a new system.sin from Nordic ICS ftf for Xperia Neo i have this problem:
Code:
1 [main] unyaffs 1088 exception::handle: Exception: STATUS_ACCESS_VIOLATION
835 [main] unyaffs 1088 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
in stackdump is:
Code:
Exception: STATUS_ACCESS_VIOLATION at eip=004010B0
eax=9207DAAB ebx=00000084 ecx=00004800 edx=00C5147A esi=0028CD34 edi=61179FC3
ebp=0028CCD8 esp=0028CCA0 program=C:\Users\Lukasz\Desktop\Xperia Neo\ftf_extractor\unyaffs.exe, pid 7988, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CCD8 004010B0 (00C51420, 00000000, 612058E8, 00401333)
0028CD08 004013AF (00000002, 00C383C0, 00C38290, 00000001)
0028CD68 61006CD3 (00000000, 0028CDA4, 61006570, 7EFDE000)
End of stack trace
What's going on? system.sin from old Gingerbread is extracting fine
EmannsXperia said that experts from here are the best experts so i'm posting it here
Try posting in this thread
http://forum.xda-developers.com/showthread.php?p=17557317
Your friends are right the xda devs are awesome
From XDA on my XPERIA X10-S, powered by DooMKerneL
Hello,
so I extracted a .DZ ROM file. The system.img(.ext4) has 6 parts:
system.img.ext4_0
...
system.img.ext4_5
How can I merge them into a functional system.img(.ext4) file in Windows?
I've used this cmd command:
copy /b "system.img.ext4_*" "system.img"
Then I used unyaffs to extract it, but it returned this errors:
7 [main] unyaffs 1564 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1529 [main] unyaffs 1564 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
1114863 [main] unyaffs 1564 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1131084 [main] unyaffs 1564 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
The content of unyaffs.exe.stackdump is:
Exception: STATUS_ACCESS_VIOLATION at eip=610DEFA1
eax=00000000 ebx=00000009 ecx=FFFFFFFF edx=00000000 esi=611021A0 edi=00000000
ebp=0028CC08 esp=0028CC04 program=C:\***\unyaffs.exe, pid 1564, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CC08 610DEFA1 (00000000, 0040DC70, 00000200, 610E5635)
0028CC48 004010BF (0028CCA9, 00000000, 0040130E, 00401333)
0028CC78 004013AF (00000002, 00F401B0, 00F40090, 610BEE77)
0028CD58 610060D8 (00000000, 0028CD90, 61005450, 0028CD90)
61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48)
1114863 [main] unyaffs 1564 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1131084 [main] unyaffs 1564 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
What am I doing wrong?
_/=-)+(-=\_ said:
Hello,
so I extracted a .DZ ROM file. The system.img(.ext4) has 6 parts:
system.img.ext4_0
...
system.img.ext4_5
How can I merge them into a functional system.img(.ext4) file in Windows?
I've used this cmd command:
copy /b "system.img.ext4_*" "system.img"
Then I used unyaffs to extract it
Click to expand...
Click to collapse
Simple.
You're using an unyaffs extractor on a non-yaffs2 file.
Look for tools that let you open ext4 images instead, such as this one.
Hello all
I am having some trouble with SDK installing apps to my Android. I've tried to find many forums about my issue, but I've hit a brick wall every time. My rooted device is an LG Optimus C running Android 2.2 (ancient lol). My issue is that I'm getting the error: Failure [INSTALL_FAILED_DEXOPT] for every app I try to install. I've wiped the device twice and then found out that this error happens every time after I've installed a good amount of apps...which I read somewhere that this will happen because of not having enough space in Dalvik..or in the data area and won't allow the install to write anything else..correct me if I'm wrong on this I've also cleared all caches multiple times, including Dalvik.
I've also tried the work around where you try and skip that all together and put the app straight into /system /app. That came up with no resolution, even with the correct properties selected (read/write/execute etc). So now, I really have no other avenues left but to come here and ask.
Here is the Logcat results I get using adb install -r app.apk no matter what app it is. I will use tumblog.apk (compatible with device) for this example:
D/AndroidRuntime( 4201):
D/AndroidRuntime( 4201): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
I/AndroidRuntime( 4201): Heap size: -Xmx32m
D/AndroidRuntime( 4201): CheckJNI is OFF
D/AndroidRuntime( 4201): Calling main entry com.android.commands.pm.Pm
W/ActivityManager( 1356): No content provider found for:
W/ActivityManager( 1356): No content provider found for:
D/PackageParser( 1356): Scanning package: /data/app/vmdl-166230949.tmp
D/PackageManager( 1356): Scanning package com.luckydroid.tumblelog
E/PackageManager( 1356): Package com.luckydroid.tumblelog has mismatched uid: 10
060 on disk, 10061 in settings
I/PackageManager( 1356): Linking native library dir for /data/app/com.luckydroid
.tumblelog-1.apk
D/installd( 1256): DexInv: --- BEGIN '/data/app/com.luckydroid.tumblelog-1.apk'
---
D/dalvikvm( 4211): Zip inflate: partial write (will retry): (24536 of 32768)
E/dalvikvm( 4211): Zip inflate: write failed: No space left on device
W/dalvikvm( 4211): DexOptZ: extraction of classes.dex from /data/app/com.luckydr
oid.tumblelog-1.apk failed
W/installd( 1256): DexInv: --- END '/data/app/com.luckydroid.tumblelog-1.apk' --
- status=0xff00, process failed
E/installd( 1256): dexopt failed on '/data/dalvik-cache/[email protected]@com.luckydroid.
[email protected]' res = 65280
W/PackageManager( 1356): Package couldn't be installed in /data/app/com.luckydro
id.tumblelog-1.apk
D/AndroidRuntime( 4201): Shutting down VM
I/AndroidRuntime( 4201): NOTE: attach of thread 'Binder Thread #3' failed
D/jdwp ( 4201): adbd disconnected
I really have no clue what any of this means lol...pretty new to logcat. I am aware of the file name not matching the original name of the apk..shouldn't matter considering I've installed many apps with shortened names. Any help would be greatly appreciated! Thanks
EDIT: Looks like "E/dalvikvm( 4211): Zip inflate: write failed: No space left on device" is the problem. Not enough space in Dalvik. Still have no idea how to work around.
Bump
Is this not posted in the correct forum? I'm just guessing no one knows of a solution?
Çözüme Yakın
Sizin sorununuz apk~classes.dex~.smali dosyalarının içinde gereksiz kodları siliniz. "Ayrıca Facebook klasörünü bulup siliniz (her clasess.dex'te bulunmaz)" ayrıca kimi classes.dex boyutu 9MB iken yükleniyor bazı clasess.dex dosyaları ise 7,8*MB olunca yüklenmiyor. Tabikide kodlar içinde dexOpt= dex options ayarı vardır ama ben bulamadım sadece bunları biliyorum. Umarım çözüm bulan çıkar. TR
As the title says, whenever I open a folder on the desktop File Manager crashes. Remix OS version is 2.0.102, build 5.1.1-B2016030106. Has anyone else experienced this?
Error message:
Code:
exceptionClassName: java.lang.NullPointerException
exceptionMessage: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
throwFileName: DocumentsActivity.java
throwClassName: com.jide.filemanager.DocumentsActivity
throwMethodName: getParentDirectory
throwLineNumber: 1571
stackTrace: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
at com.jide.filemanager.DocumentsActivity.getParentDirectory(DocumentsActivity.java:1571)
at com.jide.filemanager.DirectoryFragment.onCreateView(DirectoryFragment.java:379)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5401)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
How do you get anything to open from the desktop? I have to use the toolbar to do anything.
putr4s said:
As the title says, whenever I open a folder on the desktop File Manager crashes. Remix OS version is 2.0.102, build 5.1.1-B2016030106. Has anyone else experienced this?
Error message:
Code:
exceptionClassName: java.lang.NullPointerException
exceptionMessage: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
throwFileName: DocumentsActivity.java
throwClassName: com.jide.filemanager.DocumentsActivity
throwMethodName: getParentDirectory
throwLineNumber: 1571
stackTrace: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
at com.jide.filemanager.DocumentsActivity.getParentDirectory(DocumentsActivity.java:1571)
at com.jide.filemanager.DirectoryFragment.onCreateView(DirectoryFragment.java:379)
at android.app.Fragment.performCreateView(Fragment.java:2053)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:894)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1067)
at android.app.BackStackRecord.run(BackStackRecord.java:834)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1452)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:447)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5401)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Click to expand...
Click to collapse
hi,
I created a folder and placed some apps in it on desktop, afterwards tried to open folder, but it did not respon.d I had to delete folder eventually.
So, yes, i agree the folders are buggy.,
(Not working.?)
good luck
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
fsuinnc said:
How do you get anything to open from the desktop? I have to use the toolbar to do anything.
Click to expand...
Click to collapse
hi,
i double click on the app icon (desktop) and it launches /open.
Good luck