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.
Related
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
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
I would like to deodex my stock rom fot theming it but i am not able to do it..I have tried every possible software and every possible tutorial but when I try to deodex an odex file it gives me error like this :
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: regCount does not match the number of a
rguments of the method
at org.jf.dexlib.Util.ExceptionWithContext.withContext(ExceptionWithCont
ext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(Instructio
nIterator.java:91)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:154)
at org.jf.dexlib.Item.readFrom(Item.java:77)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.java:48)
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:280)
Caused by: java.lang.RuntimeException: regCount does not match the number of arg
uments of the method
at org.jf.dexlib.Code.Format.Instruction3rc.checkItem(Instruction3rc.jav
a:129)
at org.jf.dexlib.Code.Format.Instruction3rc.<init>(Instruction3rc.java:7
9)
at org.jf.dexlib.Code.Format.Instruction3rc.<init>(Instruction3rc.java:4
4)
at org.jf.dexlib.Code.Format.Instruction3rc$Factory.makeInstruction(Inst
ruction3rc.java:145)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(Instructio
nIterator.java:82)
... 6 more
Error occured at code address 0
Please anyone ca help
i have uploaded my odex file in attachment is there any one who can convert it into dex...if you are successful please tell me I would like to deodex my whole rom...
Hello All,
So here's the situation: I am trying to use my cheap virtually unbrickable tablet to learn more about kernel development and eventually ROM building.
I have extracted the manufacturers (WoPad) LiveSuit image and used split_bootimg.pl to break up the boot image.
I extracted the config file from the kernel image using extract-ikconfig and it created a config file. I didn't see the config in /proc.
So, I have the factory ramdisk and the factory kernel config.
I have downloaded several kernel sources (lichee-3.0.8, ChritianTroy's 3.0.36, and another one from linux-sunxi 3.0.72). I can successfully compile all of them without errors and they all generate zImages, uImages, etc using the factory config as well as the sun4i_crane configs they come with.
When I repack the boot.img with the newly created kernel and install it on nandc it wont' boot past the android icon (u-boot). I was hoping someone could shed light where I'm messing up. When I compare my boot.img to the factory one, they both have the same offset where the kernel starts (0x00000800). I have also ensured I'm replacing the kernel modules when I'm changing kernel versions.
Here is the line I'm using to repack the boot.img
Code:
mkbootimg --base 0x40000000 --pagesize 2048 --kernel zImage --ramdisk ramdisk-repack.cpio.gz --board sun4i --cmdline \"console=ttyS0,115200 rw init=/init loglevel=8\" -o boot.img
OR
mkbootimg --base 0x40000000 --pagesize 2048 --kernel bImage --ramdisk ramdisk-repack.cpio.gz --board sun4i --cmdline \"console=ttyS0,115200 rw init=/init loglevel=8\" -o boot.img
OR
mkbootimg --base 0x40000000 --pagesize 2048 --kernel uImage --ramdisk ramdisk-repack.cpio.gz --board sun4i --cmdline \"console=ttyS0,115200 rw init=/init loglevel=8\" -o boot.img
Any help will be appreciated. Also, I'm building on Ubuntu 13.04 with Google GCC 4.6 from the ndk. I have built kernels for other devices without issues. This one has me stumped.
Thanks
Here is an output from UART
Code:
CPU: SUNXI Family
Board: A10-EVB
DRAM: 512 MiB
NAND: 3800 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:9-
-name- -start- -size-
bootloader : 100000 1000000
env : 1100000 200000
boot : 1300000 2000000
system : 3300000 10000000
data : 13300000 40000000
misc : 53300000 100000
recovery : 53400000 2000000
cache : 55400000 8000000
UDISK : 5d400000 90400000
-----------------------------------
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x1300000, size 0x2000000
33554432 bytes read: OK
Starting kernel ...
Since I posted my question, I have managed to work my way through some errors but I'm stuck again. Now I'm having issues getting past init. It is stuck in a loop because of this:
Code:
<4>ft5x_ts: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
[ 8.740000] ft5x_ts: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
<6>init: command 'insmod' r=-1
[ 8.780000] init: command 'insmod' r=-1
<4>hv2605: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
[ 8.840000] hv2605: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
<6>init: command 'insmod' r=-1
[ 8.850000] init: command 'insmod' r=-1
<4>ump: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
[ 9.000000] ump: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)
<6>init: command 'insmod' r=-1
Again, if any kernel devs out there are reading this your assistance is appreciated.
I was able to solve this on my own too. Ended up being the tool chain I was using. I used 4.4.3 and all is well. Only bug I'm having is a WiFi driver issue now.
Sent from my YP-G70 using xda premium
rjwil1086 said:
I was able to solve this on my own too. Ended up being the tool chain I was using. I used 4.4.3 and all is well. Only bug I'm having is a WiFi driver issue now.
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
dude i know its a bit late but can you walk me through your entire kernel compilation procedure starting by sharing the source and the tricks of booting the newly created kernel ?
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