Hi all,
I try to deodex v10f app and framework successly and put all into system .all app work well but LGEIME.apk it's show FC.
who can help me to solve problem.
https://hotfile.com/dl/170459796/0b17282/LGEIME.zip.html
code for put LGEIME.apk to system
1. copyLGEIME.apk to /sdcard/tmp
2. run command as below
#mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
#busybox cp /sdcard/tmp/LGEIME.apk /system/app/
#rm /system/app/LGEIME.odex
#chmod 644 /system/app/*
#chown root.root /system/app/*
#mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
#reboot
now i use temporary fix. dooesn't deodex LGEIME.apk .
anyone , who can help me to fix problem?
you got a lot of errors during startup of the app, seems you are missing some framework references to jars.
im sure you should see error during compile when you make the new apk? at least it seems missing functions and result is crashing.
@Dexter_nlb when i complie a new apk doesn't has error
Related
Does anyone know how to uninstall myfaves from CM 4.1.9999 I had the apk that you were able to install to 4.0.4 and me thinking and acting like a noob I tried to install it on the new rom now I just keep getting force closes from it...if anyone can help it would be nice
Here is the command I used to install it from terminal
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
#cp /sdcard/download/MyFaves.apk /system/app
Thanks in advanced
su
mount -o rw,remount /system
rm -r /system/app/MyFaves.apk
Thank you very much....no more force closes
Tell me what I'm doing wrong here. I'm trying to make a script that will remove some apps whenever I flash a new rom. Here's what I thought would work:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/app
rm com.amazon*.apk
rm Mail.apk
rm Development.apk
rm LatinIME.apk
To use it I type:
Code:
$ su
# sh /sdcard/apps.sh
and it just fails at every line. Any help would be appreciated.
On the first line try
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
or your could shortcut it by using
mount /system
Stupid question, but do you have the permissions set to allow root access?
I've done that a few times to realize what my "mistake" was.
well you could just make a script for your PC something along the lines of
Code:
@echo off
adb remount
adb shell rm /system/app/com.amazon*.apk
adb shell rm /system/app/Mail.apk
adb shell rm /system/app/Development.apk
adb shell rm /system/app/LatinIME.apk
adb shell reboot
and rename it to a .bat or .cmd file
jackslim said:
On the first line try
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
or your could shortcut it by using
mount /system
Click to expand...
Click to collapse
Ok so I did that and the script appears to be working. I'll test it when Cyanogen release another update with amazon... Adding the -t yaffs2, what exactly did that do?
The -t is a trigger saying that your going to specify what type of filesystem your mounting, yaffs2 is the type of filesystem
For reference, these are my thoughts on the matter.
We have 3 ways to do this:
1. Get hold of SBL, change it and flash it
Currently impossible afaik.
2. Get an init.d bash script to reboot into recovery if key is pressed
Most likely possible taking these 2 assumptions into account:
a) Bash allows to detect a pressed key, something like this:
Code:
_key()
{
local kp
ESC=$'\e'
_KEY=
read -d '' -sn1 _KEY
case $_KEY in
"$ESC")
while read -d '' -sn1 -t1 kp
do
_KEY=$_KEY$kp
case $kp in
[a-zA-NP-Z~]) break;;
esac
done
;;
esac
printf -v "${1:-_KEY}" "%s" "$_KEY"
}
_key x
case $x in
$'\e[15~') reboot recovery ;;
esac
Replacing this key code for one of OB's.
But for this, we need assumption number 2:
b) Key codes mapping is the same for recoveries.
Now, while this is the method of the greatest chance to work, it is also fairly useless. Developers will often break the boot before the init.d scripts are ran. So, this code should be ran before. Hence, the third method.
3. Start a custom service in init.rc (@ ramdisk) that will detect pressed key
This would be the perfect solution as it can't be broken from kernel (zImage) or system changes. However, init.rc has its own programming language (android init language) and there's no way to run this kind of listener.
However, it is possible to run an external script located for example in /system/bin/. These can be both an executable compiled from c (higher chances of working) or a bash scripting like the aforementioned one (lower chances of working since android probably doesn't start a console on boot).
Code for this would be something like:
Code:
service exampleservice /system/bin/exampleservice
user exampleservice
group exampleservice
oneshot
So uh, am I missing anything?
Anyone has other ideas?
a lot of times i heared about pressing "G" and "Power" would boot into some kind of save mode... if thats true i guess its easyer to reprogramm that keycombo to do something else... so does that keycombo anything? i couldnt figure out^^
Sent from my LG-P970 using XDA App
Are others devices has the key combination code in SBL?
I wish I have enough knowledge about android system so i can help...
i04055 said:
Are others devices has the key combination code in SBL?
I wish I have enough knowledge about android system so i can help...
Click to expand...
Click to collapse
Yes there are devices heaving the key-combo in SBL if that answers your question. The "Samsung Galaxy S GT-I9000" e.g. has them there afaik. With that device it was possible flashing the SBL to add a "booting directly into recovery" key-combo...
So I don´t know why there should not be a solution to do the same to the OB but Noejn surely has good reason for telling its impossible.
But hey what about booting into recovery on every system startup and only boot into the system through the recovery? It´s a "quick & dirty" solution even if its possible but better than developing the way we do isn´t it? I´m not sure if its easier to change the startup that way than to add or modify a key-combo but maybe someone here does?
I'm sure (or hope..) someone can, but perhaps we should move this Thread to another part of the Forum so someone with the knowledge how to do this will read it.
d0n22 said:
But hey what about booting into recovery on every system startup and only boot into the system through the recovery? It´s a "quick & dirty" solution even if its possible but better than developing the way we do isn´t it? I´m not sure if its easier to change the startup that way than to add or modify a key-combo but maybe someone here does?
Click to expand...
Click to collapse
Yeah, i prefer that way if poosibble rather than nothing.
But if put it that way, when the phone get bootloop is it still posibbe to boot into recovery?
Sent from my LG-P970 using XDA App
This is how it's done on Xperia X8 phone.
The /system/bin/chargemon is usb-charge daemon that is being hijacked on boot (it's binary is replaced with this script)
Original chargemon is copied into "charger" to keep it's functionality.
Than "sleep 3" waits for any keypress, and checks the dump, if keys were pressed, it launches the recovery binary.
quite simple.
Code:
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event1 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -f /data/local/tmp/xrecovery ]
then
rm -f /data/local/tmp/xrecovery
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount /system
umount -l /dev/block/mtdblock0
# chroot
chroot / /init
fi
# remount rootfs rw
mount -o remount,rw rootfs /
chmod 0777 /dev -R
chown 0.2000 /dev/oncrpc -R
cd /
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
mkdir -p /minicm
cd /minicm
tar -xf /system/bin/ramdisk.tar
# Umount /system, data and cache
umount -l /dev/block/mtdblock0
umount /dev/block/mtdblock3
umount /dev/block/mtdblock1
rmdir /system /data /cache /mnt
racht said:
This is how it's done on Xperia X8 phone.
The /system/bin/chargemon is usb-charge daemon that is being hijacked on boot (it's binary is replaced with this script)
Original chargemon is copied into "charger" to keep it's functionality.
Than "sleep 3" waits for any keypress, and checks the dump, if keys were pressed, it launches the recovery binary.
quite simple.
Code:
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event1 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -f /data/local/tmp/xrecovery ]
then
rm -f /data/local/tmp/xrecovery
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount /system
umount -l /dev/block/mtdblock0
# chroot
chroot / /init
fi
# remount rootfs rw
mount -o remount,rw rootfs /
chmod 0777 /dev -R
chown 0.2000 /dev/oncrpc -R
cd /
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
mkdir -p /minicm
cd /minicm
tar -xf /system/bin/ramdisk.tar
# Umount /system, data and cache
umount -l /dev/block/mtdblock0
umount /dev/block/mtdblock3
umount /dev/block/mtdblock1
rmdir /system /data /cache /mnt
Click to expand...
Click to collapse
yeah ，from this we can see what is running before logo screen and we can mod that file
so.. is that mean we can boot to recovery mode same as x8?
racht said:
This is how it's done on Xperia X8 phone.
The /system/bin/chargemon is usb-charge daemon that is being hijacked on boot (it's binary is replaced with this script)
Original chargemon is copied into "charger" to keep it's functionality.
Than "sleep 3" waits for any keypress, and checks the dump, if keys were pressed, it launches the recovery binary.
quite simple.
Code:
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event1 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -f /data/local/tmp/xrecovery ]
then
rm -f /data/local/tmp/xrecovery
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount /system
umount -l /dev/block/mtdblock0
# chroot
chroot / /init
fi
# remount rootfs rw
mount -o remount,rw rootfs /
chmod 0777 /dev -R
chown 0.2000 /dev/oncrpc -R
cd /
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
mkdir -p /minicm
cd /minicm
tar -xf /system/bin/ramdisk.tar
# Umount /system, data and cache
umount -l /dev/block/mtdblock0
umount /dev/block/mtdblock3
umount /dev/block/mtdblock1
rmdir /system /data /cache /mnt
Click to expand...
Click to collapse
soundes quite promising... have you tried it?
Can this be usefull?
http://forum.xda-developers.com/showthread.php?t=991276
Noejn have you abandoned us ? Or are u planning to take a look at this ? Would be nice if u get OB up and running
recovery
Hi,
has there been any success with booting into recovery mode?
BR,
J
logitec said:
Hi,
has there been any success with booting into recovery mode?
BR,
J
Click to expand...
Click to collapse
No,I try to boot directly into recovery through boot.img,but I get a big "error" form the LG Security Team!
Hijacking a daemon would work if Optimus Black had those binaries. I took a quick glance at a backup and I didn't see chargemon in /system/bin.
Besides, a xRecovery is limited as it's dependent on system files so a /format can't be done which isn't really that "comfy", especially when changing fs.
But yeah, better than nothing. Still, the method you described is only possible in Xperia phones, as far as I know.
I still say injecting a service on the init.rc is the way to go.
However, I can't test this now.
racht said:
This is how it's done on Xperia X8 phone.
The /system/bin/chargemon is usb-charge daemon that is being hijacked on boot (it's binary is replaced with this script)
Original chargemon is copied into "charger" to keep it's functionality.
Than "sleep 3" waits for any keypress, and checks the dump, if keys were pressed, it launches the recovery binary.
quite simple.
Code:
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event1 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -f /data/local/tmp/xrecovery ]
then
rm -f /data/local/tmp/xrecovery
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount /system
umount -l /dev/block/mtdblock0
# chroot
chroot / /init
fi
# remount rootfs rw
mount -o remount,rw rootfs /
chmod 0777 /dev -R
chown 0.2000 /dev/oncrpc -R
cd /
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
mkdir -p /minicm
cd /minicm
tar -xf /system/bin/ramdisk.tar
# Umount /system, data and cache
umount -l /dev/block/mtdblock0
umount /dev/block/mtdblock3
umount /dev/block/mtdblock1
rmdir /system /data /cache /mnt
Click to expand...
Click to collapse
Good news, I'm getting close.
ok, thank you for everithing
Noejn said:
Good news, I'm getting close.
Click to expand...
Click to collapse
good news indeed^^ im working on it as well but im not feeling like getting close :-\ pls let me know what you did and how you did it as soon as its done... again thank you very much for your efforts!
Sent from my LG-P970 using XDA App
d0n22 said:
good news indeed^^ im working on it as well but im not feeling like getting close :-\ pls let me know what you did and how you did it as soon as its done... again thank you very much for your efforts!
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Well, I've succeed injecting the script on boot.
However, I'm getting some problems on the event0 > keycheck; I don't think at this time of boot /dev entries are up.
But I've already thought of a workaround and I'll test it tomorrow.
I´m thinking, if i compile kernel of ubuntu and install it in recovery partition, not possible then run ubuntu in native mode from sdcard with dualboot?
Just got done chatting with Hashcode about the wifi not working when flashing a ROM using SS3.
Here's the fix:
Change the line in the updater script that reads:
"/system/lib/modules/wlan.ko"
To this:
" /system/lib/modules/prima/prima_wlan.ko"
Done!
What exactly does this mean? Is wifi now working on the razr hd rom?
Sent from my Motorola Atrix HD MB886
Aman27deep said:
What exactly does this mean? Is wifi now working on the razr hd rom?
Sent from my Motorola Atrix HD MB886
Click to expand...
Click to collapse
If you edit the updater script as mentioned above it should according to hashcode
Actually, the exact fix for wifi if you already have the ROM installed is (doing this from adb):
su
mount -o remount,rw /system
rm /system/lib/modules/wlan.ko
ln -s /system/lib/modules/prima/prima_wlan.ko /system/lib/modules/wlan.ko
mount -o remount,ro /system
exit
Or if you want to fix the updater-script in the flash.zip:
Change the following line:
symlink("/system/lib/modules/prima/prima", "/system/lib/modules/wlan.ko");
to:
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
If someone could confirm that wifi is working on the AHD after this fix, that would be great! Thanks.
Hashcode said:
Actually, the exact fix for wifi if you already have the ROM installed is (doing this from adb):
su
mount -o remount,rw /system
rm /system/lib/modules/wlan.ko
ln -s /system/lib/modules/prima/prima_wlan.ko /system/lib/modules/wlan.ko
mount -o remount,ro /system
exit
Or if you want to fix the updater-script in the flash.zip:
Change the following line:
symlink("/system/lib/modules/prima/prima", "/system/lib/modules/wlan.ko");
to:
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
If someone could confirm that wifi is working on the AHD after this fix, that would be great! Thanks.
Click to expand...
Click to collapse
I didn't feel the need to put the entire line in, as if they couldn't figure out which line it was from what I posted, they had no business editing an updater script lol
Thanks for the fix for installed ROMs as well Hash!
Here's your quote from the page:
"So there's a symlink wrong for /system/lib/modules/wlan.ko it needs to point to: /system/lib/modules/prima/prima_wlan.ko
(I typo'd this in the script to: /system/lib/modules/prima/prima)
I'll rebuild the ROM and upload a corrected version "
http://www.droidrzr.com/index.php/t...ock-for-safestrap/page__p__136918#entry136918
Hashcode said:
Actually, the exact fix for wifi if you already have the ROM installed is (doing this from adb):
su
mount -o remount,rw /system
rm /system/lib/modules/wlan.ko
ln -s /system/lib/modules/prima/prima_wlan.ko /system/lib/modules/wlan.ko
mount -o remount,ro /system
exit
Or if you want to fix the updater-script in the flash.zip:
Change the following line:
symlink("/system/lib/modules/prima/prima", "/system/lib/modules/wlan.ko");
to:
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
If someone could confirm that wifi is working on the AHD after this fix, that would be great! Thanks.
Click to expand...
Click to collapse
Confirmed working!
Hashcode said:
Actually, the exact fix for wifi if you already have the ROM installed is (doing this from adb):
su
mount -o remount,rw /system
rm /system/lib/modules/wlan.ko
ln -s /system/lib/modules/prima/prima_wlan.ko /system/lib/modules/wlan.ko
mount -o remount,ro /system
exit
Or if you want to fix the updater-script in the flash.zip:
Change the following line:
symlink("/system/lib/modules/prima/prima", "/system/lib/modules/wlan.ko");
to:
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
If someone could confirm that wifi is working on the AHD after this fix, that would be great! Thanks.
Click to expand...
Click to collapse
A more detailed explanation is ALWAYS the best, thanks hash.
It leads to less people borking things up and being ignored due to asking "inane" questions...
Sent from my MotoAHD
The fix does not work for me Atrix HD ATT
HELP
Hashcode said:
Actually, the exact fix for wifi if you already have the ROM installed is (doing this from adb):
su
mount -o remount,rw /system
rm /system/lib/modules/wlan.ko
ln -s /system/lib/modules/prima/prima_wlan.ko /system/lib/modules/wlan.ko
mount -o remount,ro /system
exit
Or if you want to fix the updater-script in the flash.zip:
Change the following line:
symlink("/system/lib/modules/prima/prima", "/system/lib/modules/wlan.ko");
to:
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
If someone could confirm that wifi is working on the AHD after this fix, that would be great! Thanks.
Click to expand...
Click to collapse
Hello and thanks for the info. But howw exactly do I put the code on adb? Im not a pro in this and I wanna test it, and yes I'm a little late
On what rom you want to try this?
This is the new fork of cyanogenmod 13/Snapdragon Camera.
I pulled it from the Nexus 7 2013 build an made a flashable zip for the Nexus 6.
It has to run as a system app and is still under heavy development but it is pretty fast while starting and focusing.
So give it a try.
No magic, just a simple script, all credits go to the original developers from CM!
Code:
#!/sbin/sh
ZIP=$3
ui_print "mounting system ..."
mount /system
mount -o rw,remount /system
mount -o rw,remount /system /system
cd /tmp
unzip -o "$ZIP"
rm -rf /system/app/Snap/
mkdir /system/app/Snap/
cp Snap.apk /system/app/Snap/Snap.apk
chown 0.0 /system/app/Snap/ /system/app/Snap/Snap.apk
chmod 755 /system/app/Snap/
chmod 644 /system/app/Snap/Snap.apk
chcon u:object_r:system_file:s0 /system/app/Snap/Snap.apk
ui_print "... done"
umount /system
sync
exit 0
Do I need CyanogenMod to run this?
@OP: Did you try this before posting? It doesnt work on my Aosp rom. I tried out Snap on Neobuddy's unofficial CM build a few days back. Many iterations of Snap(as a .zip or .apk) for AOSP roms have surfaced and so far none of them work as intended. Not surprised that this did not either. If you're gonna post a flashable .zip at least make sure it works, not worried that anything will happen to my phone. if nothing else, it's annoying trying a harmless removal of a system app without leaving residual clutter. Cheers!
has this worked for anybody on aosp?
thanks, i like this cam
5k
where can i write the script tersebeut ..
please explain, and more details to avoid errors and impact on the bootloop,
sorry i'm a beginner
thx mastah