Ok here's the question.
I have an edited framework-res.apk and it works fine if I flash it as whatever.zip after a clean boot.
However, if I replace that same framework-res.apk for the original one before building a ROM and then flash it, it gives me force closes after it boots.
I've read somewhere that the first boot needs the original in order to build the dexs, only after that can a new framework-res.apk be flashed. Now if this is true, how come there are several ROMs with an edited framework without the need to flash later?
Thanks
Related
Hi,
When I flash the battery circle mod (http://forum.xda-developers.com/showthread.php?t=730673) through recovery as an update on my phone, everything goes well.
I even made one myself with Apk manager (http://forum.xda-developers.com/showthread.php?t=695701) using the stock framework-res.apk file and it works just fine.
I have cooked my own rom based on 2.03.405.3 with the kitchen (http://forum.xda-developers.com/showthread.php?t=633246) (rooted, disabled the bootsound and deodexed the whole rom).
Now I putted the battery circle mod (tried with both of them) into my rom using winrar and replaced the framework-res.apk and signed the rom.
But when I flash this rom on my phone, my phone gets stuck in a bootloop. I already searched with google to find similar problems but didn't find any. No mather what I try, it always ends with a boot loop
Anyone who can help me out???
Did you tried flashing other rom?
jup, i already flashed some roms from other members + some that i made myself and no problems at all
Open your original framework-res.apk with 7zip (not extract, just open) replace the file (use drag and drop), except for meta file and sign file, and afrer finish just close the 7zip, now you have modified framework-res.apk and cook it. It's very easy yeah.......
Sent from my HTC Legend using Tapatalk
BesFen said:
Open your original framework-res.apk with 7zip (not extract, just open) replace the file (use drag and drop), except for meta file and sign file, and afrer finish just close the 7zip, now you have modified framework-res.apk and cook it. It's very easy yeah.......
Click to expand...
Click to collapse
Guess it ain't that easy. Tried it exactly the way you said and again bootloop
I have made my rom.zip with dsixda's HTC Android Kitchen.
I open this rom with 7-zip and extract the framework-res.apk file and I leave my rom open.
Then I open the framework-res.apk with 7-zip, I drag and drop the files that need to be replaced and I close the file.
I then sign framework-res.apk with stericson's autosigner and drag and drop the signend file into my still open rom.zip which I then close.
I sign the rom.zip an put it on my sd-card.
I go into recovery, wipe data/factory reset and wipe the dalvik cache and then flash the zip and reboot.
And again I have a bootloop
But when I make an update.zip of the edited framework-res.apk and I flash then I have no problems at all.
Attached: logcat file with my bootloop error. (Other error than the one I my first post)
nobody who can help me ???
Did you deodex or get already deodexed framework?
Do you wipe data partition every time you flash this ROM of yours?
BlaY0 said:
Did you deodex or get already deodexed framework?
Do you wipe data partition every time you flash this ROM of yours?
Click to expand...
Click to collapse
My whole rom is deodexed with the kitchen. There are no .odex file in my rom.
And yes i always wipe before I flash
OK, let's get this straight... you wipe data, then flash your rom (without updated framework-res.apk), then boot and just after that (in second recovery session) you push new framework-res.apk, reboot again and it works? Or... you wipe your data, flash rom, push new framework-res.apk (via update), reboot and it works?
Did you make some logcat of failed attempt?
matn013 said:
Guess it ain't that easy. Tried it exactly the way you said and again bootloop
I have made my rom.zip with dsixda's HTC Android Kitchen.
I open this rom with 7-zip and extract the framework-res.apk file and I leave my rom open.
Then I open the framework-res.apk with 7-zip, I drag and drop the files that need to be replaced and I close the file.
I then sign framework-res.apk with stericson's autosigner and drag and drop the signend file into my still open rom.zip which I then close.
I sign the rom.zip an put it on my sd-card.
I go into recovery, wipe data/factory reset and wipe the dalvik cache and then flash the zip and reboot.
And again I have a bootloop
But when I make an update.zip of the edited framework-res.apk and I flash then I have no problems at all.
Attached: logcat file with my bootloop error. (Other error than the one I my first post)
Click to expand...
Click to collapse
I said open framework-res.apk with 7zip before you cook it, replace the file and close it, no need to sign it, and cook your rom. It's working well on mine.
Sent from my HTC Legend using Tapatalk
matn013 said:
But when I make an update.zip of the edited framework-res.apk and I flash then I have no problems at all.
Click to expand...
Click to collapse
...so I guess problem is somewhere else?
BesFen said:
I said open framework-res.apk with 7zip before you cook it, replace the file and close it, no need to sign it, and cook your rom. It's working well on mine.
Sent from my HTC Legend using Tapatalk
Click to expand...
Click to collapse
So what do you mean by "and cook your rom"? Replace the changed framework-res.apk file in my rom.zip and run my rom through the kitchen again?
Because I just did that and it doesn't work either
matn013 said:
So what do you mean by "and cook your rom"? Replace the changed framework-res.apk file in my rom.zip and run my rom through the kitchen again?
Because I just did that and it doesn't work either
Click to expand...
Click to collapse
Don't replace the framework-res.apk, extract your modified framework-res.apk, you can use winrar/winzip/7zip to extract it, take your custom .png file from it.
If it finish, then open OEM framework-res.apk with 7zip (not extract, just open), then drag and drop your custom .png file that you already take from custom framewoekees into it in same folder in 7zip, then build your rom.
Sent from my HTC Legend using Tapatalk
Did you mess with other files?
wrong permisions?
maby need to update you updater-script with file owner etc
Hello, i've a problem with my ROM:
when i put the framework into the ROM Cooked, on the first boot I get some errors and vibrations. Installing only recovery framework it works fine. The ROM is Signed with Android Signer
What's wrong?
Help
Help Me MASTERS
DocRambone, Darkyy, Jim_panse ecc..
Please ...
To start, this is in the wrong section.
Now for a few guesses on my part based on the vague diagnosis u provided.
1. U decompiled the framework-res and recompiled, in essence changing the digest of the manifest and hence only a push through recovery is valid.
2. You signed the framework-res in which case, well you shouldnt (copy meta-inf from original apk)
3. "Adb logcat" is your best friend (not literally i hope). Use it to find out where you went wrong, yes it's in english not "code" so it shud help you find out what it's complaining about.
velenoso84 said:
Hello, i've a problem with my ROM:
when i put the framework into the ROM Cooked, on the first boot I get some errors and vibrations. Installing only recovery framework it works fine. The ROM is Signed with Android Signer
What's wrong?
Help
Click to expand...
Click to collapse
what i9000 version do you have?
Thanks.
I have GT-I9000. The ROM and Framework is this http://forum.xda-developers.com/showthread.php?p=9807217#post9807217 I Want work JPU
Sent from my GT-I9000 using Tapatalk
Daneshm90 said:
To start, this is in the wrong section.
Now for a few guesses on my part based on the vague diagnosis u provided.
1. U decompiled the framework-res and recompiled, in essence changing the digest of the manifest and hence only a push through recovery is valid.
2. You signed the framework-res in which case, well you shouldnt (copy meta-inf from original apk)
3. "Adb logcat" is your best friend (not literally i hope). Use it to find out where you went wrong, yes it's in english not "code" so it shud help you find out what it's complaining about.
Click to expand...
Click to collapse
I just tried apkmanager 4.9 + apktools 1.3.1 and undergoing rebuilding me no errors.
I decompiled and recompiled twframework framework and without touching anything, I put in the ROM, I did the flash recovery but still have the same problems.
excuse for English
check the logcat, i bet you find your answer there
The comand is adb logcat > logAndroid.txt?
Hi guys I'm a friend who is helping velenoso84 in this work. When we flash rom with new framework the phone after bootanimation logo start to vibrate. We tried to use the logcat but him return only:
* daemon not running. starting it now *
* daemon started successfully *
Whyyy?????
Help me please guys
Hi,
My first deodexing, wasn't as simple as expected, I was surprised no one did it before me...
Deodexed: entire framework dir, and most of the app directory (all but 2 apks which refused to deodex...), as long as the framework is deodexed thats ok.
Needed it to patch the framework.jar for bidi language and it works, seems a bit of a lag after each boot before showing the widgets and apps but after that it runs smooth,
can someone explaing that maybe? something to do with unzipping delay maybe?
here is the file, enjoy.
http://www.multiupload.com/FRE906144I
EDIT1: this zip is not flashable nor is it full rom, just deodexed framework and app directories, use adb to push to device, it is working for me with no problems (except the delay at boot), no fc (forced.closed) at all.
flashable zip?
FaithCry said:
flashable zip?
Click to expand...
Click to collapse
its in a .zip so i would assume so. thats the only way to put new ROMs within Nexus S... unless you want to go to Odin which would be .tar
@OP
Was it bluetooth.apk & networklocation.apk? If so, I finally got those deodexed, but I couldn't get the framework.jar to deodex correctly xD
If you need/want them, I can send them to you.
#EDIT
Testing my build with your framework.jar to see if it works right..
#EDIT 2
I am still getting that da** framework fc lol. Let me logcat it..
#Edit 3
I think I might know what my issue is.. Trying a few things now
#Edit 4
I went back to my framework.jar and fixed some files & now it works.. Go figure! lol. I will upload in a bit
#Edit 5
The issues on my build were the messed up NetworkLocation.apk & Bluetooth.apk.. I fixed those, and we now have a fully deodexed 2.3.3
http://forum.xda-developers.com/showthread.php?t=971690
@OP You should change the thread title to [ROM] Stock 2.3.3 DEODEXED. I'll give it a flash in the morning and add it to my Roms, themes, and kernels thread You could even give it a flashy name hehe
The zip I supplied is not flashable as far as I know, I used adb in recovery mode to push the files to the phone,
my deodexed framework.jar works, I use it for a day now and also used a patching script on it to make it bidi enabled, and it still works, I get no fc's at all with it, just a delay on boot before I see all my widgets/icons, after that all ok.
I have a clean working nandroid deodexed backup which also has the bidi patch at:
http://www.multiupload.com/UQ364AHDWT
I created my rom and took the easy way out with the theming, I went to UOT kitchen and had it made and then manually tweaked it to my liking. Now I need to get it into my rom and I dont know how. It comes in a flashable zip that includes the updater-script, update-script, and update-binary and a folder with the settings along with my usual framework-res.apk.
How do I go about doing this? Is there a script I can use to have it first flash my rom then afterwards flash the theme?
flapflip22 said:
I created my rom and took the easy way out with the theming, I went to UOT kitchen and had it made and then manually tweaked it to my liking. Now I need to get it into my rom and I dont know how. It comes in a flashable zip that includes the updater-script, update-script, and update-binary and a folder with the settings along with my usual framework-res.apk.
How do I go about doing this? Is there a script I can use to have it first flash my rom then afterwards flash the theme?
Click to expand...
Click to collapse
Remove the apk from the UOT Zip and replace it with the one in your ROM.
Nevermind, just wrote up a simple script for it, then extracted and dropped it in my update folder. Nothing too hard
Hi all,
I'm running the latest stable cyanogenmod rom.
What I'm trying to do is to replace the default cyanogenmod wallpaper by editing the framework-res.apk but each time I'm trying to replace the original using root explorer or flashing it through recovery my device is stuck in a bootloop.
The steps I'm following to edit the apk are the following:
Decompiling using apktool
Replacing the original wallpaper located in res/drawable-nodpi
Recompiling the apk using apktool
Either replacing the original using root explorer or creating a flashable zip and flashing it using recovery
Any thoughts on what might be the problem?
kalpetros said:
Hi all,
I'm running the latest stable cyanogenmod rom.
What I'm trying to do is to replace the default cyanogenmod wallpaper by editing the framework-res.apk but each time I'm trying to replace the original using root explorer or flashing it through recovery my device is stuck in a bootloop.
The steps I'm following to edit the apk are the following:
Decompiling using apktool
Replacing the original wallpaper located in res/drawable-nodpi
Recompiling the apk using apktool
Either replacing the original using root explorer or creating a flashable zip and flashing it using recovery
Any thoughts on what might be the problem?
Click to expand...
Click to collapse
I don't know but, could it be that the image file that you put in framework-res.apk is not in the proper format or doesn't have the appropiate size (it needs to be exactly the same size as your screen size)?
TenKoX said:
I don't know but, could it be that the image file that you put in framework-res.apk is not in the proper format or doesn't have the appropiate size (it needs to be exactly the same size as your screen size)?
Click to expand...
Click to collapse
It's the same format (jpg) and the same size (960x800) as the original.