Android OS Forum banner
1 - 11 of 11 Posts

·
Android Beginner
Joined
·
9 Posts
Discussion Starter · #1 ·
I tried to center the clock by editing the XML code in SystemUI.apk (from a thread on XDA) which didn't work for me. So I used adb to push the original SystemUI.apk which I had copied to my PC back to the phone. Now my notification bar is gone. Please help!

Sent via Rooted 2.3.4 Moto Atrix using Tapatalk
 

·
Android Apprentice
Joined
·
29 Posts
Re flash the rom without wiping anything. I had the same problem trying to change the carrier logo.

Sent from my DROIDX using RootzWiki Forums
 

·
Android Beginner
Joined
·
9 Posts
Discussion Starter · #3 ·
Thanks nivek. Do you know where I could get the ROM? I'm still trying to learn all this stuff. This was my first attempt at any of this.

Sent via Rooted 2.3.4 Moto Atrix using Tapatalk
 

·
Android Nut
Joined
·
2,611 Posts
when you adb pushed it, it might have created a second systemui.apk. make sure there is only one there and it's the original one. then reboot and it should work
 

·
Android Apprentice
Joined
·
29 Posts
"loanerdave said:
Thanks nivek. Do you know where I could get the ROM? I'm still trying to learn all this stuff. This was my first attempt at any of this.

Sent via Rooted 2.3.4 Moto Atrix using Tapatalk
What rom were you on/were you stock? Look under the development section.

Sent from my DROIDX using RootzWiki Forums
 

·
Android Beginner
Joined
·
9 Posts
Discussion Starter · #6 ·
razorloves said:
when you adb pushed it, it might have created a second systemui.apk. make sure there is only one there and it's the original one. then reboot and it should work
There's only one apk but I do also have a SystemUI.odex and I don't recall if that was there before or not. Is that relevant?

Sent via Rooted 2.3.4 Moto Atrix using Tapatalk
 

·
Banned
Joined
·
1,227 Posts
loanerdave said:
There's only one apk but I do also have a SystemUI.odex and I don't recall if that was there before or not. Is that relevant?

Sent via Rooted 2.3.4 Moto Atrix using Tapatalk
Don't meant to talk out of my... you know what... but i don't think it is, though I've never really tried to modify an odexed rom... well, there's my two cents... :)
 

·
Android Nut
Joined
·
2,611 Posts
loanerdave said:
There's only one apk but I do also have a SystemUI.odex and I don't recall if that was there before or not. Is that relevant?
did you do a chmod 644 to set the right permissions on the apk?
 

·
Banned
Joined
·
1,227 Posts
Understanding Android file permissions

Overview Of Permissions via ADB SHELL
Example = drwxrwxrwx

To Check Permission at anytime in ADB just Type:
ls -l

The First character defines the Directory, Link, Binary.
Below are some examples
Example = d---------
d = Directory
l = Link
b = Binary

The next 9 characters define the file permissions. These permissions are
given in groups of 3 each.

The first 3 characters are the permissions for the owner of the file or directory.
Example = -rwx------

The next 3 are permissions for the group that the file is owned by.
Example = ----rwx---

The final 3 characters define the access permissions for everyone not part of the group.
Example = -------rwx

There are 3 possible attributes that make up file access permissions.

r - Read permission. Whether the file may be read. In the case of a
directory, this would mean the ability to list the contents of the
directory.

w - Write permission. Whether the file may be written to or modified. For
a directory, this defines whether you can make any changes to the contents
of the directory. If write permission is not set then you will not be able
to delete, rename or create a file.

x - Execute permission. Whether the file may be executed. In the case of a
directory, this attribute decides whether you have permission to enter,
run a search through that directory or execute some program from that
directory

In addition to the file permission, you can also modify the owner and
group of the file. The chown program is used here and its syntax is very
simple. You need to be the owner of a file or root to do this.

Understanding Owner Permissions:
The first command is for owner ID, the Second Command is for Group ID.
exp. root.root ( First Root is owner, Second Root is Group ).

Chmod 644 some file, Like Build.prop For testing & then Veiw the Resulted Changes!
Refer to the table below as a quick reference.

Command Line for Both would look like this

chmod 644 build.prop = -rw-r--r--
\/
Chmod Guide
0 - ---
1 - --x
2 - -w-
3 - -wx
4 - r--
5 - r-x
6 - rw-
7 - rwx

Behold 2 SH Chown Guide
\/
chown root.root build.prop
root.root = Root
root.shell = Shell

Busybox SH Chown Guide
\/
chown 0.0 build.prop
0.0 = Root
0.2000 = Shell

Side Note:Always set owner ( chown ) before Setting Permissions ( Chmod )!
--KANGED FROM here. -- Thanks to ~BH_MAN at the androidforums for the write-up.
 

·
Android Beginner
Joined
·
9 Posts
Discussion Starter · #10 ·
It was the file permissions. Thank you all for your insight. You can mark this thread [SOLVED].

Sent via Rooted 2.3.4 Moto Atrix using Tapatalk
 
1 - 11 of 11 Posts
Top