Related
Hi XDA Community!
I know some Custom ROMS includes shell scripts that are executed at the boot.
Now, I'm cooking one, already made the script, just searching for a way to autostart it at boot.
I'm trying to add my script to some /etc/init.d folder but in my cooked ROM there is just a system/etc folder, extracted from an update.zip without any init.d
HowTo?
[edit] Checked Cyan's ROM and I see /system/etc folder with content, and init.d is there.
Jack_R1 said:
On Cyanogen, for example, /etc is mounted to /system/etc on start.
Click to expand...
Click to collapse
Yes. In my rom, it is also mounted.
But init.d does not exists.
And I don't even know if it works that way on Android...
HowTo?
Edited my post above.
Jack_R1 said:
Edited my post above.
Click to expand...
Click to collapse
Thx for your time.
Yes I also did.
In fact, I search for the answer quite some time before posting.
I see this folder in Cyan's ROM.
But it still do not tell me how to make my script run at boot:
- do I have to create init.d?
- will my script be under names conventions (like 01xx 02xx 03xx)
- will it loads automaticaly by Android 2.2 ?
some progress:
i found etc/init* in ramdisk!
trying a few things on that and report
-------------------------------------
Sent via the XDA Tapatalk App
On CM, try putting your script in /system/bin then adding it's name to /system/etc/init.d/20userinit.
There is also an app in the market called autostart which runs a script at /data/opt/autostart.sh which you have to create. I use it because it's the first way I found to execute scripts at startup and I just stuck with it, so I've never used the CM script, but I think that's the proper place to add it.
Unfortunately, I haven't seen a way to run things at startup on froyo yet. When someone figures that one out, please report.
fubaya said:
Unfortunately, I haven't seen a way to run things at startup on froyo yet. When someone figures that one out, please report.
Click to expand...
Click to collapse
I'm trying Autostart (root), the app you told me, but it seems you also say that you found no way to do such thing on FroYo...
Do you mean autostart (the app) do NOT work on FroYo?
leonnib4 said:
I'm trying Autostart (root), the app you told me, but it seems you also say that you found no way to do such thing on FroYo...
Do you mean autostart (the app) do NOT work on FroYo?
Click to expand...
Click to collapse
Yes, autostart doesn't seem to work on Froyo. You talked about both Cyan and Froyo, which one are you using?
fubaya said:
Yes, autostart doesn't seem to work on Froyo. You talked about both Cyan and Froyo, which one are you using?
Click to expand...
Click to collapse
I said I was aware Cyan was using bootscripts, but Im using stock rooted froyo.
In fact, Im cooking one.
Found it!
In Cyanogen sources:
in boot.img
in ramdisk
init.rc
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
dsixda should include in its rom kitchen
Emulating the effect of the Autostart app
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
ddvo said:
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
Click to expand...
Click to collapse
Did you create the 20autostart folder? Are you performing this with Autostart running? I'm trying to have insmod tun.ko perform at each boot so my VPN works without having to open TerminalE and doing it at command line on the phone.
connexion2005 said:
Did you create the 20autostart folder?
Click to expand...
Click to collapse
20autostart is a shell script file, not a folder. All scripts in the directory /etc/init.d are executed on boot in alphanumerical order.
connexion2005 said:
Are you performing this with Autostart running?
Click to expand...
Click to collapse
Autostart is non-functional at least on my HTC Desire with rooted 2.2 (Froyo); you can uninstall it, while the method I explained above is guaranteed to work.
ddvo said:
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
Click to expand...
Click to collapse
I've tried it but it doesn't work for me.
there is a rcS file which seems to run everything in the init.d folder
i made a file "20autostart" file containing the script you posted.
I didn't have an "opt" folder in "/data", created one.
Created "autostart.sh, containing "swapon /data/swap256"(script works with gscript).
But it isn't run and no autostart.out or .err file is created after reboot. Seems like it isn't run at all..
There is an "sh" file in the "/bin" folder so it should be able to call that function.
I have no experience what so ever with this but i've done all the steps necessary.
Never mind, created an other solution!
Hi NRG, I just checked again with my system, and there it still works.
Maybe because it's a specific custom ROM version of Android 2.2?
Mine is called "Eight Minutes to Eight O´Clock A.M." from android.modaco.com/content/htc-desire-desire-modaco-com/312051/oclock-custom-rom/
Maybe you used the wrong shell path: /bin/sh instead of /system/bin/sh.
Which other solution have you found meanwhile?
Tasker can run things at boot if anyone needs another way to do it. You can run shell commands with Tasker and the Locale Execute Plugin.
/data/local/tmp
Hi, you are looking for - /data/local
chmod 755
Hey Folks, mybe one of you can give me a hint.
I extracted the boot.img saved before with oneclick-recovery for zte v9 light using mytools from another post (unpack-bootimg.pl etc) and everything worked. i am using Ubuntu Linux on my pc. After i added the quoted lines i repacked it, using the repack script from that mytools and flashed it using
Code:
flash_image boot /sdcard/boot.img
reboot
Well- thats what bricked my phone. Dont worry, got the official zte flashing tool, a clean android 2.2 and unbricked it after a few days of worrying... But what am i making wrong to get the init.d contents get executed on boot?
leonnib4 said:
Found it!
In Cyanogen sources:
in boot.img
in ramdisk
init.rc
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
dsixda should include in its rom kitchen
Click to expand...
Click to collapse
!!!!UPDATE!!!
I have created a tool that makes this process 100% easier!
http://forum.xda-developers.com/showpost.php?p=21566003&postcount=1
Proceed to use the following manual guide as reference but I suggest using the tool I created for an easier experience.
=======================================================================
First if you havent already, Unlock the Vivid Bootloader on HTCdev.com!
>>>>>Follow These directions step by step dont rush or skip any steps. Take your time with this removal. It involves deleting certain files from the system folder!<<<<<
***You need root, Look for ZERGRUSH's root method on the forums***
Update the root SU binary! ( can be done in the superuser settings menu )
Go to the marketplace and look for NoBloat Free
***Look for two entries***
HtcIQAgent (com.htc.android.iqagent)
IQRD (com.htc.android.iqrd)
Click to expand...
Click to collapse
Remove them or Backup and Remove them
Go to your terminal
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd system/bin
rm iqd
rm iqfd
cd system/lib
rm libhtciqagent.so
rm libciq_client.so
rm libciq_htc.so
cd system/etc
rm iqprofile.pro
Click to expand...
Click to collapse
close your terminal session
reboot
Enjoy!
Update : This seems to be complete for now, all CIQ libraries and apps removed. Supercurios CIQ app detects that only the log remains, its useless but you can delete this too. thanks khhawkins for opening up my eyes to something i blinked over.
Update #2: You will detect two linux kernel drivers t__param_str_ciq_info & t__param_ciq_info, these two load up from the stock kernel and cant do anything after CIQ has been removed. This is normal and you will not see CIQ resurface on your device
Update #3: If youre score is 150 on Supercurios CIQ detector app you are clear!
Update #4: Dont skip any steps!
RIP CIQ on the Vivid....
What about /system/bin/iqfd? Is that related too?
Thanks for this
Sent from my HTC PH39100 using xda premium
kxhawkins said:
What about /system/bin/iqfd? Is that related too?
Thanks for this
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
According to supercurios app for detecting CIQ, the IQD file in /system/bin remains after deletion of the main CIQ files. Youll see in the logcat regarding CIQ "Unable to start service Intent", after you killed the two main running apps. There are two linux drivers that stop running after you ill iqd. But even if they are on, they are basically stranded, youre CIQ free either way.
Thanks for pointing this out KHhawkins, Im updating the post to instruct how to remove the iqd file and the iqfd file
Mission Accomplished
I have searched for Zergrushs root but haven't had any luck. Can some one post the link?
capman231 said:
I have searched for Zergrushs root but haven't had any luck. Can some one post the link?
Click to expand...
Click to collapse
Search for the HTC supertool
there also happens to be an entry in /system/build.prop
ro.ril.ciq=1
dont know if changing it to 0 would have any effect.
Pirateghost said:
there also happens to be an entry in /system/build.prop
ro.ril.ciq=1
dont know if changing it to 0 would have any effect.
Click to expand...
Click to collapse
No effect, I see no more ciq activity on logcat. I wanted to tinker with the build.prop file and initially remove it, but its an unnecessary step. Similar to the orphaned kernel drivers
Sent from my HTC PH39100 using xda premium
My device has no system\pro directory at all.
Otherwise the only discrepancy I found was the file htciqagent.so was also libhtciqagent.so.
---------- Post added at 03:07 PM ---------- Previous post was at 02:44 PM ----------
FYI - My Voodoo CarrierIQ score is 150 after following your directions. The applicaiton labeled my device as "Carrier IQ elements found - however it seems inactive".
ifiweresolucky said:
My device has no system\pro directory at all...
Click to expand...
Click to collapse
Before
Code:
cd system\pro
rm iqprofile.pro
Issue:
Code:
find / -name iqprofile.pro
to locate the iqprofile.pro file.
Then, "cd" to that location, and issue
Code:
rm iqprofile.pro
Thanks, was in system\etc\
Fixed all entries
Any performance increase after removing CIQ?
ifiweresolucky said:
My device has no system\pro directory at all.
Otherwise the only discrepancy I found was the file htciqagent.so was also libhtciqagent.so.
---------- Post added at 03:07 PM ---------- Previous post was at 02:44 PM ----------
FYI - My Voodoo CarrierIQ score is 150 after following your directions. The applicaiton labeled my device as "Carrier IQ elements found - however it seems inactive".
Click to expand...
Click to collapse
Youre in the clear, the last "150" come from the linux kernel drivers which are actually part of the kernel.
Okay. Noob question here. When you say go to terminal. What does that mean? Terminal emulator on the phone? Or a terminal on the PC? And if on the PC what do I use?
I have unlocked the bootloader
He means a DOS prompt (Windows) or terminal window (Linux). Then navigate to where you have ADB (assuming you dont have environmental variables set up) and execute the commands.
backtothemac said:
Okay. Noob question here. When you say go to terminal. What does that mean? Terminal emulator on the phone? Or a terminal on the PC? And if on the PC what do I use?
I have unlocked the bootloader
Click to expand...
Click to collapse
On your Mac use the terminal app with adb. On a PC use command prompt with adb.
Sent from my HTC PH39100 using xda premium
I am missing something. I can open the shell. Enter SU and then then next step in the process fails. I am close. lol
backtothemac said:
I am missing something. I can open the shell. Enter SU and then then next step in the process fails. I am close. lol
Click to expand...
Click to collapse
Root first!
I did. I am missing something small I am sure. But I am definitely missing it.
whenever i tried to use terminal and enter the command "sh" ...... i prints "sh - applet not found" ?????
anyone has answer for it ?????? Please ! answer soon !!!!!
Strange sh should work by default
did you give superuser rights to the terminal ?
you should install busybox and then try
---------- Post added at 05:58 PM ---------- Previous post was at 05:35 PM ----------
And may i know for what are you trying to use sh?
do you want to run a script ?
Busybox?
nail16 said:
Strange sh should work by default
did you give superuser rights to the terminal ?
you should install busybox and then try
---------- Post added at 05:58 PM ---------- Previous post was at 05:35 PM ----------
And may i know for what are you trying to use sh?
do you want to run a script ?
Click to expand...
Click to collapse
Dear i tried to install busybox but it gave me errors that i have others busybox already installed .....
And i had this error because i was developing in eclipse and mounting i9000 as emulator ..... Error was "sh - applet not found"
sh is unix/linux comandline shell. When you open terminal sh run automaticaly
Solved !!!!!
I just changed my firmware back to JVU from JW4 and problemo solved ...... Thanx Anyway Guyz
Hi!
I've restarded my X8 (latest GingerZaraki, nAa14) and it's stuck on bootscreen now (the screens turns off after time but it can be waken by home button). It launches normally when /data is formated but this means that I have no apps and their settings. I've got CWM backup (unfortunately after it bootstocked) and I want to restore my apps manually. My Titanium backup is a bit outdated. And heres comes the [Q] part - is ther any possibility of restoring my data manually from CWM backup file in which I can choose what I want to restore and what not?
Thanks in advance.
Hi there..
Yes it is possible with a little reading. If you have an existing Linux install it's easier but you can use any livecd you wish.
Visit this site to get a little more info..
Good luck..
---------- Post added at 07:44 PM ---------- Previous post was at 07:40 PM ----------
Here's the easy way on a debian linux install..
Code:
linBox:/home/kaibo# modprobe mtdblock
linBox:/home/kaibo# modprobe jffs2
linBox:/home/kaibo# modprobe mtdram total_size=200000
linBox:/home/kaibo# cat /proc/mtd
dev: size erasesize name
mtd0: 0c350000 00020000 "mtdram test device"
linBox:/home/kaibo# dd if=/usr/src/sheeva/Image/ubuntu.jffs2 of=/dev/mtdblock0
278272+0 records in
278272+0 records out
142475264 bytes (142 MB) copied, 2.59761 s, 54.8 MB/s
linBox:/home/kaibo# mount -t jffs2 /dev/mtdblock0 /mnt
linBox:/home/kaibo# ls /mnt
bin dev home media opt root selinux sys usr
boot etc lib mnt proc sbin srv tmp var
Reboot to cwm, "backup and restore", "advanced restore"
stamatis, this actually cause the main problem - phone stucks on bootscreen. Recently I've found that the datas I had been looking for were in sd-ext.ext4.tar file, so I've exctracted what They're like me.xxx.xxx folders containing two another folders. Where should I put them if the app is installed on internam memory?
CtrlAltDelIrl, I've Ubuntu already but not feel too good with it, just basics. If nothing else helped, I'd try your solution. Thanks.
trove said:
stamatis, this actually cause the main problem - phone stucks on bootscreen. Recently I've found that the datas I had been looking for were in sd-ext.ext4.tar file, so I've exctracted what They're like me.xxx.xxx folders containing two another folders. Where should I put them if the app is installed on internam memory?
CtrlAltDelIrl, I've Ubuntu already but not feel too good with it, just basics. If nothing else helped, I'd try your solution. Thanks.
Click to expand...
Click to collapse
OK, i'll add a little more to make it easier..
Code:
sudo mkdir /mnt/jffs2
sudo modprobe mtdblock
sudo modprobe jffs2
sudo modprobe mtdram total_size=200000
cat /proc/mtd
sudo dd if=/home/user/Image/ubuntu.jffs2 of=/dev/mtdblock0
sudo mount -t jffs2 /dev/mtdblock0 /mnt/jffs2
ls /mnt/jffs2
Change what you need and type commands in a terminal..
---------- Post added 4th March 2013 at 12:22 AM ---------- Previous post was 3rd March 2013 at 11:55 PM ----------
Didn't even notice the different filesystem format lol..
It's very similar proceedure though..
Look here..
CtrlAltDelIrl, I'll try to this when I have some time. Thanks.
EDIT: I've tried your method CtrlAltDelIr, but I didn't succeed. Then I've found that Nandroid files can be extracted by Titanium Backup Pro, so I've bought it. Thanks for replies. Cya.
Like in description
Navibar 3 -5 -7 buttons mod - android 5.0
air3g, air 2
If you have my rom Lolipop ( mirek190 ) just plug USB and choose proper option.
On other rom make sure you have root and USB debugging on.
3 buttons navigation bar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5 buttons navigation bar
7 buttons navigation bar
air 3g
https://drive.google.com/open?id=0B8BF9-TGlz-FY2tWZUVZa05FU00
air 2
https://drive.google.com/open?id=0B8BF9-TGlz-FTEhvUTl2clE3Z3M
Ps - NOT RUN IT AS ADMINISTRATOR !
Hi mirek.
Can you add systemui.apk with a clock in its original position with 3 buttons?
Nope - center clock stays in the center like buttons
delete
Great job Mirek!
Hi, can you do this for the Air III? Do you need the stock SystemUI.apk?
EDIT:
I found this post www[dot]tsochen[dot]com/blog/post/15 and nearly the same intructions works for Air III M5C5. But the status_bar_*xml fix as not needed. This is the diff of navigation_bar.xml for 3 buttons
gist[dot]github[dot]com/kazuoteramoto/c0730bb27d0fb8dc6332
The system cannot find the path specified
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Wow, thanks, teramoto--this is fantastic! I just modded the SystemUI.apk on my device based on the tsochen link you provided, and your diff. I didn't want the screenshot and volume +/- buttons, but I did want to keep the menu button. So I just modded as indicated, and left the @id/menu entries untouched. The result is a nicely centered, four button variant.
EDIT: Somebody requested that I post my modded SystemUI.apk for a 4-button nav bar for the Air 3/III 32GB (M5C5). At the link below, I have done this, but also included 3- and 5-button versions, as well as the original 7-button SystemUI.apk version from the M5C5 v1.04 stock rom. The various SystemUI.apk files are obviously named by an explicit filename extension as you'll see when you download the archive. Also, let me reiterate--these are specifically for an Air 3/III 32GB (M5C5) tablet. Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing. Finally, and most importantly, note that credit for this goes to teramoto and the tsochen blog posting he pointed out above, which I just followed to do this, and also to mirek190 for starting this thread, and for helping out so many X98 Air users. Here's the link:
https://mega.nz/#!Hw0jRKBJ!0omuxVQXFHjzdbMV1bg6yvBhtMT570-gBhnkKxw2A4o
irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Facing the same problem...
irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Have you installed drivers ?
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
I did the same as you for whole day....thanks anyway.
irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
Thanks for a clue - 1st post updated .
verbage said:
Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing.
Click to expand...
Click to collapse
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
verbage said:
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
Click to expand...
Click to collapse
Hi. first let me thank you for your effort.
I tried your solution but I'm still without the buttons and notification bar.
Code:
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb shell
[email protected]_m5c5:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_m5c5:/ # cd /system/priv-app/SystemUI
cd /system/priv-app/SystemUI
[email protected]_m5c5:/system/priv-app/SystemUI # ls
ls
SystemUI.apk
x86
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI # chown root.root SystemUI.apk && chmod 644 SystemUI.apk
chown root.root SystemUI.apk && chmod 644 SystemUI.apk
<
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI #
Am I doing something wrong? Any other idea? Or can I put the original file back?
Thanks for any help with this
EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
wepecko said:
I tried your solution but I'm still without the buttons and notification bar...Am I doing something wrong? Any other idea? Or can I put the original file back?...EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
Click to expand...
Click to collapse
Hmmm, from your ls -l command, it appears that the file ownership and permission were already set correctly, and so there was no need to give the chown/chmod commands again, but doing so didn't hurt, and only confirmed things.
My M5C5 is also on sikke1's rom--I started with mirek190's v6.1 slim version for the Air 2/II even though I have an Air 3/III, and it worked pretty good except for some hiccups. And so that is why I ended up on sikke1's debloated M5C5 rom, too.
Have you rebooted? You may be nervous to do so, understandably, but adb is enabled by default in the sikke1 rom so even if the graphical UI does not pop up, you can still do manual triage via adb.
---------- Post added at 07:19 PM ---------- Previous post was at 06:53 PM ----------
One thought for the future--if you are going to do this manually, you should stage it appropriately to hopefully avoid issues. For example, copy the original to a backup with the -p option to preserve file properties while still leaving the in-use original completely intact (i.e. "cp -p SystemUI.apk SystemUI.apk.ORIGINAL)". Then copy your modded apk file(s) into the same directory, and make sure file ownership/permissions are set as per above. Then do another cp -p to replace the in-use original with the modded apk.
Here's my listing for the directory to show you what I mean. I have the original apk plus the 3-, 4-, and 5-button modded apks all in the same directory with the correct ownership/permissions set. I can quickly change to any config, for example, the 3-button config, with a single cp -p command, i.e. "cp -p SystemUI.apk.MODDED-3-BUTTON SystemUI.apk". And there is no downtime/hiccup because one file is immediately replaced by the other, and the ownership/permissions are already correctly set.
Code:
[email protected]_m5c5:/system/priv-app/SystemUI # ls -la
ls -la
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-03 16:43 SystemUI.apk.MODDED-3-BUTTON
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk.MODDED-4-BUTTON
-rw-r--r-- root root 3572764 2016-01-03 16:43 SystemUI.apk.MODDED-5-BUTTON
-rw-r--r-- root root 3604448 2015-12-31 00:21 SystemUI.apk.ORIGINAL
drwxr-xr-x root root 2015-08-26 23:06 x86
[email protected]_m5c5:/system/priv-app/SystemUI #
Again, since you have confirmed everything, I would suggest rebooting if you have not done that. As I said, even if the graphical UI does not come up, you can still get into adb for repairs. At the very worst, you might have to reflash the rom.
I'm not sure why you have had hiccups, but these modded apks are directly from the stock SystemUI.apk of a v1.04 M5C5 rom. I have the modded navigation_bar.xml files, and I can send those or just diffs vs. the original so you can see the few lines that I changed. But you'll see they are just like described by teramoto and the tsochen blog he pointed out.
Thanks verbage. I understand your backup procedure and admit it was a mistake to rewrite the file directly.
However im still trying to find solution to this. I did restart ofcourse, several times, but it didnt help at all. It was late yesterday so i didn't have much time to try different scenarios. Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck.
One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?
Sent from my XT890 using Tapatalk
wepecko said:
Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck... One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Hmmm, sorry to hear you are still having a problem. The 3-, 4-, and 5-button versions all work perfectly on my Air 3/III using sikke1's debloated M5C5 rom, and since you have the same device, any of the versions should also work for you.
Certainly, the 7-button stock original should work, too, and that is also included in the archive I posted.
Whether there may be a conflict with the xposed framework you have installed, I don't know as I do not have xposed installed on my Air 3/III.
Anyway, good luck with fix, and we'll wait to hear more.
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
wepecko said:
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
Click to expand...
Click to collapse
Great, glad to hear you have it working!