Database Develop

[DISCUSS] General Questions/Problems with Theming

There seems to be a lot of things that are new when it comes to theming the Nexus S and Gingerbread in general.
A lot of us have run into various problems.
The purpose of this thread is to discuss the problems we're facing and to ask general questions regarding theming.

Issues:
1. [SOLVED] I can't flash anything unless it is the full ROM. I tried jabbawalkee's base zip but no luck.
Solution: Post 12. Thanks to ogdobber.
2. If I make a nand of a themed ROM and try to restore it, I get a bootloop. Unthemed ROM works fine.
Temporary Solution: Don't use ROM Manager to restore your themed Nandroids. Go to recovery and restore the Nand and don't reboot.
Flash the pertinent ROM again without wiping anything, then reboot. Flash the theme again.
3. How to get out of a bootloop? I've been doing the battery pull and volume up + power button does not work during a bootloop.
Solution: adb reboot recovery
4. [SOLVED] Nexus S loses signal after reboot.
After unlocking the bootloader, I used paul's Superboot to get root and used ROM manager to flash the latest CWM. All is well except every-time I reboot, I lose the signal (it shows emergency calls only) and I have to search for available networks in Mobile network settings.
Solution:
In the dialpad enter *#*#4636#*#*
Select phone information
Scroll down to preferred networks
Select "WCDMA only"
Click on Update
You need to re-enter the SMSC Carrier number. For WIND Mobile Canada, SMSC is 16135009000
Android requires you to enter this info in Hex.
Hex = 07916131059000F0
For Mobilicity Canada Hex = 07916174080001F6
In the dialpad enter *#*#4636#*#*
Select phone information
Scroll down to SMSC field, enter 07916131059000F0 and done. Then reboot.

Theming Guide:
Master™ started a guide where we could post useful stuff like the transparent notification bar & anything else in a simple Nexus S (or gingerbread guide...)
https://docs.google.com/document/d/1nZSTpSuFg_ox7cEzn5YZSx3P8nXMgly4Q-AvVRC8Lfw/edit?hl=en#
If you guys want to edit it, PM him so he can add you.
Click to expand...
Click to collapse

Stuck this useful thread

theimpaler747 said:
Stuck this useful thread
Click to expand...
Click to collapse
Thanks a lot!
Issue number 2 has been confirmed by another users. Maybe its a bug in CWM.

sonnysekhon said:
Thanks a lot!
Issue number 2 has been confirmed by another users. Maybe its a bug in CWM.
Click to expand...
Click to collapse
Could be that, I remember on my hero I tried to restore a recovery of my theme and it looped too

sonnysekhon said:
Issues:
1. I can't flash anything unless it is the full ROM. I tried jabbawalkee's base zip but no luck.
2. If I make a nand of a themed ROM and try to restore it, I get a bootloop. Unthemed ROM works fine.
3. How to get out of a bootloop? I've been doing the battery pull and volume up + power button does not work during a bootloop.
4. Nexus S loses signal after reboot.
After unlocking the bootloader, I used paul's Superboot to get root and used ROM manager to flash the latest CWM. All is well except every-time I reboot, I lose the signal (it shows emergency calls only) and I have to search for available networks in Mobile network settings.
Anyone else having this issue? Any fixes?
If you guys can provide some insight, I will be most thankful.
Click to expand...
Click to collapse
In regard to #1, you're right about that. The mount line is incorrect, I believe it needs to be changed to ext4 instead of mtd but I haven't gotten the line just right yet. I contacted PaulOBrien and Koush for assistance but didn't have much luck getting it right.
In terms of #4, I actually didn't have that same issue with his Superboot...but perhaps I overlooked it.
Hopefully we can get a theme zip base to work from. I'm hoping one of the ROM devs can jump in and maybe push us in the right direction. I'm not a code type of guy so I let the coders do the update script stuff . In the meantime, we'll just have to use the full ROM.
Thanks for this thread sonny!

On the Galaxy S I can find the data and wifi icons for the notification bar no problem, but I can't seem to find them anywhere for the Nexus S (along with a couple of others). Sorry if the answer is obvious, but I'm stuck. Could someone please point me in the right direction?

Dean-O said:
On the Galaxy S I can find the data and wifi icons for the notification bar no problem, but I can't seem to find them anywhere for the Nexus S (along with a couple of others). Sorry if the answer is obvious, but I'm stuck. Could someone please point me in the right direction?
Click to expand...
Click to collapse
system/app/SystemUI.apk

Great, thanks.

Found a solution to issue number 4, updated the post.

sonnysekhon said:
Issues:
1. I can't flash anything unless it is the full ROM. I tried jabbawalkee's base zip but no luck.
Click to expand...
Click to collapse
this is a solution to problem 1.
in the META-INF\com\google\android needs to have updater-script and update-binary
the updater-script needs the following line
Code:
run_program("/sbin/busybox", "mount", "/system");
attached is a meta-inf. use it in place of your current one for flashing themes

Thanks ogdobber.

Hi,
I'm a newb to theming. Can anyone point me to the right direction to change my stock news widget to transparent?
Thanks in advance

cyc1120 said:
Hi,
I'm a newb to theming. Can anyone point me to the right direction to change my stock news widget to transparent?
Thanks in advance
Click to expand...
Click to collapse
start with the 2 links below, you basically need to change the transparency level on the widget_background in the drawable(hdpi) folder. but it is not that easy because it is a .9 png (unless you go 100%)
[GUIDE] Want to learn how to theme?
The Ultimate Android Themeing Guide
Here is a thread by rori that he themes a bunch of stuff to transparent smoke http://forum.xda-developers.com/showthread.php?t=731625

I can't for the life of me try to figure out how to make an object in photoshop have a transparent background. I make the background transparent, add the object (eg: a number) and everything looks great. Then once I flatten the image the transparency disappears. What I don't get is up until I flatten it, the whole background is transparent. I'm completely baffled, can anyone offer an idiot some help?

kenvan19 said:
I can't for the life of me try to figure out how to make an object in photoshop have a transparent background. I make the background transparent, add the object (eg: a number) and everything looks great. Then once I flatten the image the transparency disappears. What I don't get is up until I flatten it, the whole background is transparent. I'm completely baffled, can anyone offer an idiot some help?
Click to expand...
Click to collapse
What image is it? And by flatten it, do you mean you are making it an indexed image?

theimpaler747 said:
What image is it? And by flatten it, do you mean you are making it an indexed image?
Click to expand...
Click to collapse
Its a number for a Beautiful widgets clock skin. By flatten it I mean in photoshop CS5 when you make an image with multiple layers (the layers get created automatically when I try to add anything, in this case text) in order to save it as anything but a .psd you have to flatten it (IE force all of the layers into one).

kenvan19 said:
Its a number for a Beautiful widgets clock skin. By flatten it I mean in photoshop CS5 when you make an image with multiple layers (the layers get created automatically when I try to add anything, in this case text) in order to save it as anything but a .psd you have to flatten it (IE force all of the layers into one).
Click to expand...
Click to collapse
Never save it as a psd for edits on android Save it as a .png

theimpaler747 said:
Never save it as a psd for edits on android Save it as a .png
Click to expand...
Click to collapse
Exactly, I'm trying to save it as a png but in order to do that I have to flatten the image which causes the transparency of the background to disappear.

Custom Notification Bar/Custom Theme

Ok so I modified the framework-res.apk file to have a custom notification bar. My question is how to make it so I can flash just the notification bar onto my phone? I know Metamorph is real easy but I want to be able to flash it in Clockworkmod Recovery. Any help would be greatly appreciated.

easiest way to do it is adb pushing it back to /system/framework/framework-res.apk

Well that's what I have been doing, but I want to make it be able to be flashed in recovery.

You need to make an update.zip

brfield said:
You need to make an update.zip
Click to expand...
Click to collapse
How do I go about doing that?

Go to circle.glx.nl and choose flashable theme. Upload your framework-res.apk and voila !

badeaioan said:
Go to circle.glx.nl and choose flashable theme. Upload your framework-res.apk and voila !
Click to expand...
Click to collapse
Tried it and it seems great, but for some reason its causing everything to crash and force close on my phone.

Ok, so I think I narrowed it down to the fact that I need the correct update-script. I made one, flashed it and it went fine, but then I rebooted and didnt see a difference. So I tried to reflash it and then it gave me a syntax error. I know what a syntax error is, but my question is if anybody could give me the info of what I should put in the update-script so that it'll work correctly. Thanks!

i have a question too...
my phone has touchwiz 3.0
which in the notification bar there is a toggle buttons like; wifi, silent, bluetooth... etc.
i know it's important and useful, but why have to put it in notification bar... wasting some space, especially when in landscape mode.
is there any way to remove that toggle button?

I have that toggle widget too on my P500.
My .apk is located in /system/framework/lge-res.apk .
Backup it and then delete the .apk and see if it goes. If it doesn't work you will need a custom ROM with the toggle widget stripped out.

I want touchwiz on my phone.
Sent from my M860 using Tapatalk

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!

This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.

What is write enabler?

Keeps aborting for me

THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.

@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.

To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.

What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516

So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2

jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?

ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.

lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.

O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2

ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.

I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.

I reinstalled the stock odex ROM and flashed this again and it worked.

Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.

Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.

ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app

fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

[Q] how do you flash "framework-res.apk" without bricking the g1?

I was wondering how I could edit the framework-res.apk (it can be found in the /system/framework directory) file and not brick my phone, I've tried putting a modified version
in a signed zip file that was supposed to be for that very purpose, a stock update.zip for getting rc29 to 1.5(and yes, I did flash my phone back to rc29) and I recently tried to just take a file manager in root mode and copy-paste-overwrite, but I just soft-bricked my phone halfway into the process, probably because it was still mounted
P.S. I did mount the /system directory as rw
my phone:htc dream,no 2g-3g contract(wifi only),rooted (universal androot),stock 1.6 drc83(but I can get it to rc29,1.5 and crc43; at least I think thats the name of the second update),stock recovery,superuser elite+superuser- latest, su binary- latest, busybox- latest binary, and about 5000 scratches.
--edit-- can also get cyanogen recovery,and root through cm 4.1.99, and cm4.2.15.1.

So is your goal to root your g1? Have you followed any guides to root? Can you give just a bit more detail of end goal and a bit confused about what os you are currently running. Also its nice to get all info from bootloader screen
Sent from my HTC Vision using xda premium

reply
demkantor said:
So is your goal to root your g1? Have you followed any guides to root? Can you give just a bit more detail of end goal and a bit confused about what os you are currently running. Also its nice to get all info from bootloader screen
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I've actually already got cyanogenmod 4.2.15 on it so rooting isn't really an issue right now.
What I really want to do is theme my phone, because I really like the ICS buttons and black statusbar - but I want to wait until I'm more experienced
before I try to port cm7 to the g1 (as far as I know, cm7 is the first cyanogenmod to support themes).
P.S. since this is being sent from my g1 - I can't currently post my bootloader info; but I will as soon as I can.
Also. I want to know how I can sign the framework-res.apk after changing it to my satisfaction.

Sorry, reading my last post (although 2months old) I must have been trying to reply to someone else
You don't need to sign the framework-res
Just decompile with apktool, make changes, recompile (make sure to add the metainf and manifest from original back in) then you can create a flashable.zip to flash it and chmod, or add it to a ROM and sign the ROM or use adb when in recovery to push it and change permissions
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
Sorry, reading my last post (although 2months old) I must have been trying to reply to someone else
You don't need to sign the framework-res
Just decompile with apktool, make changes, recompile (make sure to add the metainf and manifest from original back in) then you can create a flashable.zip to flash it and chmod, or add it to a ROM and sign the ROM or use adb when in recovery to push it and change permissions
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
How would I sign the rom if I put it in one?
Apktool gives me errors when I try to recompile.
Ninjamorph from the market makes the changes, but they don't take hold.
P.S. perfect timing with the reply, as I posted my reply only about 45 min. ago!

If there are errors recompiling write those down and I'll take a look, as for as signing the ROM there are many ways, I use signapk for windows and one that amonra made for Linux, just Google search sign ROM android and you'll find many ways
Sent from my Nexus 4 using Tapatalk 2

Is there any posibility that I could just send you the rom I want to mod & a zipped folder containing a modified framework-res, and have you recompile/sign it? I just don't want to brick my phone. Thanks in advance!

If its a ROM for the g1 I already have it, how about just sending me your modded apk along with a link to the ROM and I'll make you a flashable.zip to install
And FYI, this isn't something that could brick your phone, recovery wouldn't be effected so worst scenario is you would end up in a bootloop
Sent from my Nexus 4 using Tapatalk 2

The rom is cyanogenmod 4.2.15.1 and I can't quite remember the link, but I'll post a zip with the frmwrk-rs and my email. Thanks in advance for the help!!

Here is a zip folder with the extracted/modified framework-res, if you don't have the rom I mentioned then ask for it in a comment.View attachment framework-res.zip

Sure, I'll take a look when I get home
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
Sure, I'll take a look when I get home
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Once you've signed/recompiled it, send the rom to me as a google drive/google docs file at [email protected] (or, if you know another better method, tell me) and I'll test it.

ok so finally got to a pc,
here you go
havent tested it at all, it recompiled but there was an issues with
framework-res\build\apk\res\drawable-land\Thumbs.db'
and
framework-res\build\apk\res\drawable\Thumbs.db
they were skipped but the rom should flash and whatever mods you made should be present other that this, dont have time to peek around and see what you did

demkantor said:
ok so finally got to a pc,
here you go
havent tested it at all, it recompiled but there was an issues with
framework-res\build\apk\res\drawable-land\Thumbs.db'
and
framework-res\build\apk\res\drawable\Thumbs.db
they were skipped but the rom should flash and whatever mods you made should be present other that this, dont have time to peek around and see what you did
Click to expand...
Click to collapse
Thank you so much for your time!
downloading......................
.......................complete!
flashing......

DREAMWAVE_devteam said:
Thank you so much for your time!
downloading......................
.......................complete!
flashing......
Click to expand...
Click to collapse
--edit-- (the best I can recall it saying)
finding update
opening update
verifying update
failed no verification (352 files)
update failed
installation aborted

Does the ROM flash for you with you current setup before the edited framework-res? What I mean, if you were to flash the update-cm4.... (Whatever the name) right now it flashes correct? With your current SPL, radio, and recovery. The only thing I did was recompile your framework-res, swap it with the one from the ROM you mentioned, rezipped and signed the ROM
I can't think of any edits you could have made to framework-res that wouldn't allow you to at least flash the ROM, may get stuck in a boot loop or never boot, but the ROM should flash
Sent from my Nexus 4 using Tapatalk 2

I looked inside the rom you sent me, and I didn't recognize any of it.
this is a link to the rom I got the framework-res from:
http://code.google.com/p/cyanogen-u...pdate-cm-4.2.15.1-signed.zip&can=1&q=4.2.15.1
from what I saw, the one you sent me looks more like a flash image than an update.zip,
if you look inside the one that I was talking about, it looks more like an ota, and I can flash it in cyanogen+jf 1.4 recovery which I got
from the flashrec app (not on google play anymore, from internet only).
I don't know if an unmodified version of the rom you sent me would flash, but the one you sent me seems to have problems in general.
No errors that would point specifically to the framework-res are appearing.
Here are the files that I modified: View attachment 2212696, decompile your own framework and paste/overwrite the contents over the contents of the res\drawable directory in the framework-res.apk.

I'm pretty sure that's the same ROM I installed you apk into, I'll be home shortly and take a look again, could have made a mistake
Sent from my Nexus 4 using Tapatalk 2

This rom that you gave me is about 10mb larger than the one I use, and takes 30 seconds to load in recovery and freezes everything momentarily.

@DREAMWAVE_devteam
yeah same rom, even checked SHA1 to make sure (with the ROM before i added your framework-res)
which is 1604kb compared with 5589kb of the original. so whatever was changed is what wont allow it to work
can you just quick go over how you decompiled and what changes you made, i know you linked something and ill look at it but i dont have a ton of time to dig right now so a brief overview would be nice