What does all this mean and how do I fix it? I'm porting a ROM to the S3 and I get all the way to the boot anim then it freezes. I know that could be any number of things but i'd like to start with this first as it happens first. I've swapped out the .jar files with those from cm9 as they are confirmed working. and the port ROM is ics as well. Cache is also cleared 3 times before install.
E/dalvikvm( 316): DexOpt: build rev does not match VM: 27 vs 28
W/dalvikvm( 206): DexOpt: --- END 'core.jar' --- status=0xff00, process failed
E/dalvikvm( 206): Unable to extract+optimize DEX from '/system/framework/core.jar'
D/dalvikvm( 206): Unable to process classpath element '/system/framework/core.jar'
D/dalvikvm( 206): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 206): ODEX file is stale or bad; removing and retrying (/cache/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 206): DexOpt: --- BEGIN 'core-junit.jar' (bootstrap=1) ---
E/dalvikvm( 322): DexOpt: build rev does not match VM: 27 vs 28
W/dalvikvm( 206): DexOpt: --- END 'core-junit.jar' --- status=0xff00, process failed
E/dalvikvm( 206): Unable to extract+optimize DEX from '/system/framework/core-junit.jar'
D/dalvikvm( 206): Unable to process classpath element '/system/framework/core-junit.jar'
Click to expand...
Click to collapse
Specifically this:
E/dalvikvm( 322): DexOpt: build rev does not match VM: 27 vs 28
Click to expand...
Click to collapse
and this:
D/dalvikvm( 206): DexOpt: incorrect opt magic number (0xff ff ff ff)
Click to expand...
Click to collapse
I feel like those 2 are the big ones. If i can fix those the others should get fixed as well. Feel free to correct me if im wrong and offer up and suggestions. any advice will be appreciated. Thanks.
here is the full log if interested:
http://pastebin.com/9hfTtaMN
Bump
Sent from my SPH-L710 using xda app-developers app
Well from looking at the source code for where that happens:
http://in-the-box.googlecode.com/svn-history/r6/trunk/InTheBoxSim/dexopt/OptMain.c
It seems that it doesn't want to accept the ICS version (revision 17) when it is running JB (revision 23)
I wouldn't know how to fix it, but this is a start.
As for the the "incorrect magic" error, try taking a look here:
https://groups.google.com/forum/m/?fromgroups#!topic/android-platform/oy4trrd0eKw
Thanks for the reply. They are both running ics. I'm porting sense from the evo 4g lte. I didn't mention that in my original post because the minute I mention sense people get all scared and think "oh I don't know anything about sense I can't help" but it's a problem that occurs on a lot of roms especially new ones. The reason I haven't figured this out yet is because no one ever mentions how to fix it and if they do then I can't quite figure out the search terms to use to find it lol. But any who. What we have done is used an already started sense port that uses a custom cm9 kernel that from all I can tell only had the bootclasspath changed to match the sense kernel. The first test got us to the beginning of the boot animation. Replacing libs in the lib folder got us a tad further in the boot animation but freezes half way. The rom is deodexed. We are gonna try reodexing and see what happens. But until then all of our test involved the error above. My buddy added the ODEX files back and the 27 vs 28 simply swapped places to 28 vs 27. We found that rather odd as well.
So as it stands we get this error. Plus a seg fault. We think the dalvik error may be tied to the fact that the rom is deodexed. Gonna try reodexing.
The two roms are both ics as I mentioned before. So how could the build rev be different? What could I change to get them the same? How do I find out what caused the initial DexOpt write failure that lead to the other magic number errors?
Sent from my SPH-L710 using xda app-developers app
We fixed the magic number issue by injecting the ODEX files back into the rom but still have a version mismatch. Gonna start from scratch with an the stock odexed jb update and see if we can eliminate the problem all together.
Sent from my SPH-L710 using xda app-developers app
Sorry for not replying, but other than the version mismatch, I am out of my area of expertise by a longshot but this stuff is interesting to me so I'll read up on it and see if I can help
Thanks. Ill keep you posted on any progress I make wit this if you'd like. Anybody else that is interested feel free to jump in.
GRock84 said:
We fixed the magic number issue by injecting the ODEX files back into the rom but still have a version mismatch. Gonna start from scratch with an the stock odexed jb update and see if we can eliminate the problem all together.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I know this is an old thread, but I'm having magic number issue on a port I'm doing. Can you explain how you injected the odex files back into the ROM?
Related
want anyone try port from wildfire without sense? exactly rom is OpenFire. i had ported it..
Michga said:
want anyone try port from wildfire without sense? exactly rom is OpenFire. i had ported it..
Click to expand...
Click to collapse
sure post it up i will give it a shot, i mean without sense its just reg Aosp like fresh froyo and a few of the other builds. i dont think there is much differnce
okey but later.. now im working on rom with sense
i have still 2 problems..
1. phone cycle in bootanimation and in console is link:: notfound
or
2. init: unable to open persistent property directory /data/property errno: 2
Michga said:
i have still 2 problems..
2. init: unable to open persistent property directory /data/property errno: 2
Click to expand...
Click to collapse
add this in sysinit.rc under # create basic filesystem structure
mkdir /data/property 0700 root root
See if that helps. Goodluck!
ive installed most of the ics ports on all of them they state working wifi
now on my phone it only works when it wants to but gingerbread and below its perfect
is this the same for everyone or just me and something that will improve over course of rom development
Only tried Sandvolt's ICS-Rom, but I did not have any problems with WiFi.
Do you run a full wipe before flashing roms?
Sent from dGB using Transparent XDA App
yes i did a full wipe as well as dalvik
it did work today though but after a reboot its back off
its also a gsm desire pvt4 with s-off if that helps but it leads me to belive its more of a software issue rather hardware as stock ruu and other roms work perfect apart from ics it is pretty volitile it either works or doesnt
I've tried two different variants of ICS Roms and I had the same experience. Under gb the wifi works, but under ics I'm getting a very weak signal.
WiFi appears to be a bit hit and miss
I'm running Sandvolt's ICS ROM, I find about half the time WiFi works properly, and the rest of the time I have to drop back to 3G (which can be pretty average at times).
Could you specify what exactly do you mean with "doesn't work"? Can you switch it on? Does it remains on and can you set up/edit a new/existing profile? Advanced WLAN and profile settings are correctly set up?
[email protected] said:
Could you specify what exactly do you mean with "doesn't work"? Can you switch it on? Does it remains on and can you set up/edit a new/existing profile? Advanced WLAN and profile settings are correctly set up?
Click to expand...
Click to collapse
yer it just will not enable heres the logcat from adb
as you can see below it cant load the drivers is this normally a kernel problem i have been flashing by wiping all data and then dalvik i even returned to stock re rooted and reflashed i think its more a software error as any other rom excluding ics roms works perfect for wifi
E/WifiStateMachine( 181): Failed to load driver!
E/WifiStateMachine( 181): DriverFailedState
D/CAT ( 332): CatService: ril message arrived
D/CAT ( 332): CatService: ril message arrived
D/CAT ( 332): CatService: SESSION END
D/SurfaceTexture( 115): [Toast] this:0xa776a0 SurfaceTexture::abandon
D/dalvikvm( 181): GC_CONCURRENT freed 717K, 9% free 14566K/15943K, paused 12ms+
5ms
E/WifiStateMachine( 181): Failed to load driver!
E/WifiStateMachine( 181): DriverFailedState
D/dalvikvm( 933): GC_CONCURRENT freed 127K, 3% free 9694K/9927K, paused 3ms+3ms
I/power ( 181): *** set_screen_state 0
D/SurfaceFlinger( 115): About to give-up screen, flinger = 0xa06918
E/libEGL ( 115): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
D/AK8973 ( 122): Compass CLOSE
^C
C:\Users\sean\Desktop\SuperOneClick 2.3.1.0\ADB>
Maybe you find a solution here (SPACE=/):
http: code google com p android issues detail?id=1124
*Sorry, cannot yet post any link.
I'm using BravoCM b0.3.5_1, WiFi worked perfectly right from the start - no errors, good signal, and Google backup-restore even remembered all the passwords I configured in my old rom.
solved faulty SD card mounting as read only
Sent from my Spaceship using XDA App
seanpr92 said:
solved faulty SD card mounting as read only
Sent from my Spaceship using XDA App
Click to expand...
Click to collapse
could you mind posting the solution here? because i have the same problem with the current release of sanvold ics. how did you find out the problem is wit hsd, and how did you corrected it?
thanx a lot
ahmad598 said:
could you mind posting the solution here? because i have the same problem with the current release of sanvold ics. how did you find out the problem is wit hsd, and how did you corrected it?
thanx a lot
Click to expand...
Click to collapse
if you are flashing Sandvold ICS rom, try typical installation. you can take the logcat by connecting your device to pc via usb cable and run following:
###assuming you have android sdk downloaded and installed
c:\%android_sdk\platform-tools\adb logcat >> logfile.txt
mt25i
seanpr92 said:
ive installed most of the ics ports on all of them they state working wifi
now on my phone it only works when it wants to but gingerbread and below its perfect
is this the same for everyone or just me and something that will improve over course of rom development
Click to expand...
Click to collapse
I have exactly the same problem.
---------- Post added at 07:28 AM ---------- Previous post was at 07:20 AM ----------
ahmad598 said:
could you mind posting the solution here? because i have the same problem with the current release of sanvold ics. how did you find out the problem is wit hsd, and how did you corrected it?
thanx a lot
Click to expand...
Click to collapse
kmaq said:
if you are flashing Sandvold ICS rom, try typical installation. you can take the logcat by connecting your device to pc via usb cable and run following:
###assuming you have android sdk downloaded and installed
c:\%android_sdk\platform-tools\adb logcat >> logfile.txt
Click to expand...
Click to collapse
Thank you my friend.
Where do I type this command:fingers-crossed:
Figured a thread might help...
Log - http://pastebin.com/fH4vA9k7
Added libmms.so & SecTelephonyProvider
Things I noticed that might be useful.
Code:
dalvikvm(14284): Could not find method com.android.internal.telephony.ITelephony.IsInternationalRoaming, referenced from method com.android.mms.ui.ComposeMessageFragment.isInternationalRoaming
Code:
ActivityThread( 8412): Pub sms: com.android.providers.telephony.SmsProvider
ActivityThread( 8412): Pub mms-sms: com.android.providers.telephony.MmsSmsProvider
*Had another thread but it disappeared due to server problems*
*Mod advised to repost the thread*
Smith7018 said:
Hey man, using grep, it seems these libs mention "telephony":
Binary file libaudiopolicy_sec.so matches
Binary file libsec-ril.so matches
Binary file libvtmanager.so matches
Binary file libvtstack.so matches
Though, so does framework-res....... So, let's hope it's not that.
Click to expand...
Click to collapse
jeboo said:
I recall seeing telephony stuff deep in the framework. Check services.jar or the like.
Click to expand...
Click to collapse
Hi all, I would appreciate if someone can help me troubleshoot my logs to determine the cause for random reboots.
kmsg: http://www.mediafire.com/view/?pqrmk14laug8dq9
logcat: http://www.mediafire.com/view/?sk9nd4tye0b30ib
logcat (long format): http://www.mediafire.com/view/?bsdhnpah6as7mzp
CrazyRussianXDA said:
Hi all, I would appreciate if someone can help me troubleshoot my logs to determine the cause for random reboots.
Click to expand...
Click to collapse
What ROM/Kernel are you using? Have you customzied any values?
Running Codename Android 3.8 no customization except AOKP weather icons and the most recent Faux's kernel 21 but reboots happened on stock kernel as well. I installed the newest kernel to troubleshoot but reboots still occurring
can you please pastebin the logs?? mediafire sucks
I dont have an account there. Is there any other way I could get the logs to you?
Huh i dont think there's a need to register on pastebin.
Sent from my i9250
Well, I tried posting but got "You have exceeded the maximum file size of 500 kilobytes per paste" error when tried posting.
So, I trimmed the log to fit into requirements:
kmsg: http://pastebin.com/psNDbRAj
logcat: http://pastebin.com/fRjv0EmP
logat (long format, just in case time and date of events is needed): http://pastebin.com/sJGxrdmA
bk201doesntexist said:
Huh i dont think there's a need to register on pastebin.
Sent from my i9250
Click to expand...
Click to collapse
Posted to patebin.
Its a kernel panic alright
[21400.926086] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP
[21400.926116] Modules linked in:
[21400.926116] CPU: 0 Tainted: G W (3.0.45-tuna-faux123-jb-022+ #170)
[21400.926147] PC is at omap_rev+0x4/0x1c (... bunch of memory adresses)
which i believe to be human readable, needs a trace in the source and recompiled. Push this kmsg to faux?
Sent from my i9250
bk201doesntexist said:
Its a kernel panic alright
[21400.926086] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP
[21400.926116] Modules linked in:
[21400.926116] CPU: 0 Tainted: G W (3.0.45-tuna-faux123-jb-022+ #170)
[21400.926147] PC is at omap_rev+0x4/0x1c (... bunch of memory adresses)
which i believe to be human readable, needs a trace in the source and recompiled. Push this kmsg to faux?
Sent from my i9250
Click to expand...
Click to collapse
How can I push this to Faux?
And THANK you for helping.
CrazyRussianXDA said:
How can I push this to Faux?
And THANK you for helping.
Click to expand...
Click to collapse
provide the pastebin you linked here to him (faux123), the dev of lean kernel. through one of his threads, pm wouldn't be the appropriate means to do it.
Ok. It appears a lot of threads are popping up and its all about kernel crashing. I dont know what's causing it, but I can tell you not to flash a Rom after the update. First restore the RUU, this way you won't have to worry about fail Rom bootings on custom rims and kernels.
Again, just a warning.
>OTA Update
>RUU to stock
>Reroot and unlock bootloader
>flash Rom and kernel
>Boot
Sent from my HTC One V using Tapatalk 2
If you ruu to stock, why run the ota update???
Go check the threads with problems. The OTA update is 20MB, do its not a Rom. It patches a couple files and extracts some firmware. So restoring the RUU would be before the patches and OTA firmware.
Sent from my HTC One V using Tapatalk 2
Right. Read your message ahole. It says ota then ruu. Newb.
Sent from my HTC One V using xda app-developers app
Because people do the OTA first, as you did. No need to start getting smart. If you had a problem no need in posting, as its just a warning. Ither go somewhere or deal with it.
Sent from my HTC One V using Tapatalk 2
Honestly I avoid OTAs until one of these awesome devs looks into things....just my opinion of course
Sent from my One V using Tapatalk 2
robaho said:
Right. Read your message ahole. It says ota then ruu. Newb.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Don't be an ass to curiousnoob, he knows more than his name let's on. A lot more.
Sent from my HTC One V using Tapatalk 2
and then we see seller's 86 coming to the rescue
Sent from my One V
For those kernel devs, this consistently is the last commands in the logcat before the phone reboots:
I//system/bin/fsck_msdos( 99): ** /dev/block/vold/179:33
I//system/bin/fsck_msdos( 99): ** Phase 1 - Read and Compare FATs
I//system/bin/fsck_msdos( 99): Attempting to allocate 381 KB for FAT
D/UPolicy ( 303): [checkLatestPolicy] policy changed
D/ContactsEventQueueProcessor( 737): ContactsEventQueueProcessor.sleepThread() - mWakeUpLock.wait()
I/ ( 839): Launch RAM successful
I//system/bin/fsck_msdos( 99): Attempting to allocate 381 KB for FAT
I/rmt_storage( 238): rmt_storage write: bytes written = 4193792
I/rmt_storage( 238): rmt_storage lseek...
I/rmt_storage( 238): rmt_storage lseek ret = 8191
I/rmt_storage( 238): rmt_storage write buf = 0x406cce00, num_sector = 1
I/rmt_storage( 238): rmt_storage write: bytes written = 512