Ok.
I am using Dsixda kitchen to create a new ROM.
After making all mods, and edits, and changing the update-script to updater script, I try to compile it and sign it which is done succesfully.
I try to flash it and CWM gives me error (status 7)
Then I try using ketuts script. by replacing updater script and update binary.
It gets stuck at Android Splash Screen.
Here is the logcat: http://pastebin.com/S94vZX3G
But the main problem is:
W/dalvikvm( 5625): ERROR: Unable to find decl for native android/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.detachThemePathLjava/lang/String;I)Z
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.attachThemePathLjava/lang/StringI
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageCount)I
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageNameI)Ljava/lang/String;
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageIdI)I
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.addRedirectionsNativeI)V
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.clearRedirectionsNative)V
W/dalvikvm( 5625): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.generateStyleRedirectionsIII)Z
Then I tried out a small test and added only one app to main rom, used ketut script and compiled it and voila it worked. So i don't really know what's the problem because its definetely not in compiling.
Can someone possibly tell me what's the problem, and what i have to change to make it okay so that the ROM works according to the above logcat.
UPDATE: I tried using the base rom on my phone and i modded copied apps to system\app. Suddenly launcher Pro, and all the other apps i copied get force closed. So I reboot. And now its stuck at splash screen. When I check LogCat the same error that is listed above occurs.
It even happened to me as soon as i finished installing adrenaline engine 4.2b by ImbaWind.
Its quite similiar to the above logcat just that the number in the brackets is now 1175.
Please Help Me Out. I'm really stuck at this for like 4 days. So yup, please help me..atleast for a thanks
What custom rom did you use before the one you made.
Do other custom roms work on your phone?
Sent from my GT-S5830 using xda premium
SMillerNL said:
What custom rom did you use before the one you made.
Do other custom roms work on your phone?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Thank you for your reply!
I'm using Miracle V4 as the base ROM.
Actually, I've tried so many ROMs and never had a problem with even one.
Plus, I get a new number everytime.
I tried doing some tests, like first i just changed boot animation and kernel, and it worked. Succesfully flashed, but with wifi errors.
Then I just tried manually changing boot animation and flashing kernel. No problem at all.
I then tried doing some tests, and in the dalvik vm error i always get a different number every time.
It's kind of unusual. Its not a problem in kitchen with compiling because i've tried compiling before.
Help Me Out.
Please....
DONT Modify the update script by using dsxida kitchen manual editing please
the script that dsxida creates isnt compatible for ace ****** made moddified version of the dsxida kitchen script
to work with ace
that might give the problem
try using other update scripts
(***** i dont know name anymore sorry )
CoolCatGetHome said:
DONT Modify the update script by using dsxida kitchen manual editing please
the script that dsxida creates isnt compatible for ace ****** made moddified version of the dsxida kitchen script
to work with ace
that might give the problem
try using other update scripts
(***** i dont know name anymore sorry )
Click to expand...
Click to collapse
Yup. When building the ROM, I convert the update script to updater script. After that i manually delete the updater script and update binary from meta-inf and replace them with ketut's script. And I get no error in cwm when flashing, but it gets stuck at the splash screen...and logcat shows that error.
You clearly miss some files which your rom refers to.
But you should follow coolcat's advice. He's a great themer so he knows what he's talking about.
Sent from my GT-S5830 using xda premium
SMillerNL said:
You clearly miss some files which your rom refers to.
But you should follow coolcat's advice. He's a great themer so he knows what he's talking about.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
i am multifunctional XD
SMillerNL said:
You clearly miss some files which your rom refers to.
But you should follow coolcat's advice. He's a great themer so he knows what he's talking about.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Okk. So what should i do?
First, i don't change anything at all in the meta-inf. Except at the end. After converting. I replace with ketut scripts the updater script and the update binary.
Then I get the error in the logcat.
I tried doing one thing. Just making the mods in my phone. Then extract from cwm restore, but after flashing adrenaline engine. Same problem.
I just don't understand what i'm doing wrong.
Possibly point me out?
Related
Hi!
I have problem with installing my own apk file.
If I create some project in Eclipse and export apk file (doesn't matter if signed or not), even from empty project, and try to install it on phone, I get message: "Could not open xxx.apk as APK file". I'm using Darky's v8.0. I tried no-wipe and then wipe version, but still the same.
What's weird: I've created some simple project few days earlier and apk from this project works fine. Even when I export new one now. But any other apk from new projects doesn't work.
P.S. Sorry for my English
Dahsheg said:
Hi!
I have problem with installing my own apk file.
If I create some project in Eclipse and export apk file (doesn't matter if signed or not), even from empty project, and try to install it on phone, I get message: "Could not open xxx.apk as APK file". I'm using Darky's v8.0. I tried no-wipe and then wipe version, but still the same.
What's weird: I've created some simple project few days earlier and apk from this project works fine. Even when I export new one now. But any other apk from new projects doesn't work.
P.S. Sorry for my English
Click to expand...
Click to collapse
Have you tried with a STOCK ROM installed?
XXJPY and newer ROMs have their /system r/o. And all 2.2.1 ROMs save the app settings to dbdata.
ragin said:
Have you tried with a STOCK ROM installed?
XXJPY and newer ROMs have their /system r/o. And all 2.2.1 ROMs save the app settings to dbdata.
Click to expand...
Click to collapse
I have system mounted as r/w.
And even if the r/o would be a reason, then why any apk works fine, but not my files?
Please help me
I must create this apk...
My Galaxy Tab 7 P1000 was originally running clockwork 3.X... and I just tried to install clockwork 5... and after installation, the device keeps staying at the boot screen. And when I go to recovery mode, the 'HOME' button doesn't work.... :crying::crying:
How can I fixed this brick back to a normal tab?
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
priyana said:
The usual.
Use overcome method.
Follow my signature.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hey Dude,
Thanks for your reply. I will try it out tomorrow and hope it works on my stupid tab.
By the way, 1 more question. Before reading your reply, I tried to install CWM-based recovery 5.0.2.8 again and tried to install CM9.x on the tab, but not matter which version I used, (P1000, 1000L, 1000N), all of them gave me 'assert failed getprop( ro.product.device ) galaxytab...'. It sounds that the ROM installation file couldn't recognize my P1000 tab.....do you have any idea on how come my device couldn't be recognized.
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Thx X 1000000000000000000000000
ableeker said:
I'm not sure what exactly has happened in these cases, but it's clear some information, some kind of ID perhaps, somehow has been removed or corrupted. I've seen it myself, but luckily there's fix. When you install a ROM, the first command of updater-script in folder META-INF is an assert statement. This statement tests what Tab you have, and aborts if it's not the right one. Now, if you get an assert error and you're positive you've got the right ROM for the Tab, you can disable the check and it will install the ROM. Even if it's the wrong one! You open the ZIP, edit updater-script and remove the assert statement. It's best to open the ZIP, and not unpack and repack it. And to modify some ZIPs you will have to use Linux, because Windows can't handle those ZIPs.
Click to expand...
Click to collapse
i am trying to get into port roms and stuff well i tried to port pac from the giothread but am stuck at bootloop since two days
could anyone good ant reading and understanding logcat help me regarding errors the link below is of errors
http://pastebin.com/1wV0cdU4:good:
no fatalities in the whole process... scanning for warnings now ......
warnings : http://pastebin.com/pSxvPG2L
checking for debugs now........
There are some Library errors, some classes errors, also some unknown permission.
Are you copied right library and classes to ROM ?
Also, you can fix permission related errors by placing right .xml in /system/etc/permission
F4uzan said:
There are some Library errors, some classes errors, also some unknown permission.
Are you copied right library and classes to ROM ?
Also, you can fix permission related errors by placing right .xml in /system/etc/permission
Click to expand...
Click to collapse
I tried to fix lib errors but the required libs are just not there either in base or port
Sent from my GT-S5570 using Tapatalk 2
I am using The Galaxy Note GT-N7000 with Cyanogenmod 10.1 along with CM kernel. I was trying to install WeChat from Google Play. It got downloaded successfully but during installation, it failed displaying the following error: Unknown error code during application installation -24
Now I did try to search the solution for it over the net. I found a forum on this website for a fix, but that didn't quite work out. I did reply there too. I just needed your help too for solving this problem.
I tried using Root Explorer to search that data folder in data/data but unfortunately, that is where I was finding problem. I wasn't able to find the particular data folder of WeChat and so I wasn't able to proceed further in the process. Please help me out with this!
Thanks a lot in advance
I did a new port, see OP
I have bootanimation
Hopefully this helps
When I first saw this the first thing that came to mind was finding all the needed hardware files and putting them in the port. Now I looked over the logcat and sure enough it has hardware errors. You re having gralloc issues and hwcomposor issues. I stopped looking after I saw surfaceflinger as right after that is when the crash starts. In my opinion these are the main two issues stopping boot.
Gralloc issue
Code:
E/HAL ( 176): load: module=/system/lib/hw/gralloc.msm8974.so
E/HAL ( 176): dlopen failed: cannot locate symbol "_ZN13AdrenoMemInfo9getStrideEii" referenced by "gralloc.msm8974.so"...
Hwcomposor issue
Code:
E/HAL ( 176): load: module=/system/lib/hw/hwcomposer.msm8974.so
E/HAL ( 176): dlopen failed: cannot locate symbol "_ZN7overlay6RotMem3Mem12setReleaseFdERKi" referenced by "hwcomposer.msm8974.so"...
Now you have way more issues than those but those should be your focus right now. You will have to get the correct hardware files for hamerhead and use them to replace the hardware files for that are for the Xpeira Z3. But even if you get it booting you will have camera issues along with a lot more stuff. You may even have to decompile the framworks.apk and edit smali files to look for the correct hardware files and to use different strings.
Now I have to say I am not even sure if what you are attempting can even be done. I do wish you luck and hopefully what I posted here will help you move forward some.
T-Macgnolia said:
When I first saw this the first thing that came to mind was finding all the needed hardware files and putting them in the port. Now I looked over the logcat and sure enough it has hardware errors. You re having gralloc issues and hwcomposor issues. I stopped looking after I saw surfaceflinger as right after that is when the crash starts. In my opinion these are the main two issues stopping boot.
Gralloc issue
Code:
E/HAL ( 176): load: module=/system/lib/hw/gralloc.msm8974.so
E/HAL ( 176): dlopen failed: cannot locate symbol "_ZN13AdrenoMemInfo9getStrideEii" referenced by "gralloc.msm8974.so"...
Hwcomposor issue
Code:
E/HAL ( 176): load: module=/system/lib/hw/hwcomposer.msm8974.so
E/HAL ( 176): dlopen failed: cannot locate symbol "_ZN7overlay6RotMem3Mem12setReleaseFdERKi" referenced by "hwcomposer.msm8974.so"...
Now you have way more issues than those but those should be your focus right now. You will have to get the correct hardware files for hamerhead and use them to replace the hardware files for that are for the Xpeira Z3. But even if you get it booting you will have camera issues along with a lot more stuff. You may even have to decompile the framworks.apk and edit smali files to look for the correct hardware files and to use different strings.
Now I have to say I am not even sure if what you are attempting can even be done. I do wish you luck and hopefully what I posted here will help you move forward some.
Click to expand...
Click to collapse
I replaced these files already, from a hammerhead Cm12 nightly :/
dekefake said:
I replaced these files already, from a hammerhead Cm12 nightly :/
Click to expand...
Click to collapse
You may need other files or maybe even need to edit framworkes.apk to allow the files to be used by the system. What I am saying is just because they are present doesn't mean the system will use them. Look closely at the errors I pointed out as it will give you some idea of what to do.it says cannot find symbol blah blah blah. You need to find where that symbol is in the CM ROM and make sure it is in your port.
T-Macgnolia said:
You may need other files or maybe even need to edit framworkes.apk to allow the files to be used by the system. What I am saying is just because they are present doesn't mean the system will use them. Look closely at the errors I pointed out as it will give you some idea of what to do.it says cannot find symbol blah blah blah. You need to find where that symbol is in the CM ROM and make sure it is in your port.
Click to expand...
Click to collapse
Framework-res.apk file from Sony doesnt want to decompile properly. Using latest Apktool for Lollioop
T-Macgnolia said:
You may need other files or maybe even need to edit framworkes.apk to allow the files to be used by the system. What I am saying is just because they are present doesn't mean the system will use them. Look closely at the errors I pointed out as it will give you some idea of what to do.it says cannot find symbol blah blah blah. You need to find where that symbol is in the CM ROM and make sure it is in your port.
Click to expand...
Click to collapse
Sucedded to decompile framework-res.apk..
Replaced storage list by Nexus 5 one, and power profiles, but can't find anything about _ZN* :/
Still sticks to the same on logcat
dekefake said:
Sucedded to decompile framework-res.apk..
Replaced storage list by Nexus 5 one, and power profiles, but can't find anything about _ZN* :/
Still sticks to the same on logcat
Click to expand...
Click to collapse
these are native methods(you wont find in smali files), you can use armobjectdump/hexedit to look which files have, my bet would be you either needing to replace some of our files with the z3(hw files) or replacing some system libs(the one where the code needs to exist).
another bet would be trying to use our caf libs,however AFAIk would need changes to the kernel
Just to say i restarted a new project (look OP)
New logcat to debug.
Thanks in advance for help