Related
I tried to delete calander.apk because I don't need and it could boost my phone up. I did the following:
Su
Cd /system/app
Rm -f Calendar.apk
But it can't delete it because. It is a readonly system file. I also tried rebooting and doing it by pressing atl+x. That also didn't work what do I do now????
(I am still a newbie so I think I might have placed this thread in the wrong place...sorry)
Unfortunately it won't boost your phone up it'll most likely mess it up
$ su
# busybox mount -o rw,remount /system
...
This is the wrong forum. There is a dream Q&A section for questions like this. And there is a sticky at the top of the forum pointing you in the right direction. Well... 2 stickies actually, you can look up what alt+x does. Oh, and familiarize yourself with nandroid
you have to mount your system, on terminal go with
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm nameapplication.apk
reboot
Ok. I will try and tell u later. Thanks for the help. Do u guys know what qxdmlog.apk is
read the two posts about yours, they already told you how...
Yes it worked. thx man. There is force cloase or anything thanks again
Hi guys,
As I'm sure most of you already know, some super-smart devs have already gotten ubuntu running on evo and nexus 1. I haven't heard any news of anyone doing this on the incredible.
I would love this functionality, but I'm no dev and have no experience building kernels. Anyone with the appropriate know how interested in having a look at the evo forum, and see if they can compile a kernel that will allow us to run ubuntu on or incredibles?
Just fyi: feedback from evo users suggest that all ubuntu functionality is working, including full flash support and even hulu.com!
Are you as excited as I am? Lets get to work on this- let me know and I'll help anyway I can.
Sent from my ADR6300 using XDA App
Ok, hadn't done this before, but it turned out to be pretty easy. I have compiled the kernel, and packaged it into an update.zip file signed with test keys. You can flash this straight from CW recovery.
If anyone is interested, this "kupdate-signed.zip" will update the kernel to the one I have compiled.
This kernel is completely identical to the stock htc kernel, except that it has the
CONFIG_BLK_DEV_LOOP=y
set so that we can run Ubuntu.
FInd it here: www<dot>4shared<dot>com/file/-kxtUfIw/kupdate-signed<dot>html
--samwathegreat
Ok, so the kernel seems to work perfectly for me, however I am unable to get ubuntu running.
I'm not sure where the problem lies, but I think it has to do with our restricted access to /system and /data.
Hopefully someone here can figure out what it is that I'm missing......I've tried following the instructions while booted into recovery and mounting /system and /data > everything works fine when I run the ubuntu.sh file, but I can't run the bootubuntu file under recovery........so after rebooting phone and trying to run bootubuntu, I get all kinds of errors and ultimately it fails.
After viewing the contents of bootubuntu file, I noticed that once again, it's trying to mount the /system partition......
If this is indeed because of the nand lock, then why does the procedure work on the evo 4g? I was under the impression that it incorporated the same nand lock as the incredible?
Any ideas?
Thanks
Edit:
The nand lock is indeed the culprit...just found out that evo users have full nand unlock available. I wasn't aware of that -hopefully we have the same soon on the incredible.
Patiently waiting...
Sent from my ADR6300 using XDA App
I was looking through the
bootubuntu a few days ago and if I remember correctly it was just moving some if the scripts into the system partition. We could probably boot into recovery and move the files in manually then edit the scripts to remove the system access.
Think its possible? I haven't looked at the scripts in a few days...
Sent from my ADR6300 using XDA App
If you need someone to test let me know.
Sent from my HTC Incredible using Tapatalk
I posted a thread about chroot earlier with no reply. No true nand unlock means no chroot which means no dual booting into ubuntu/debian/meego etc. Also no response from unrevoked if they plan on releasing a true nand unlock.
Other big problem is input.
http://forum.xda-developers.com/showthread.php?t=631389
That's about putting debian on the nexus as well using adb which might be possible but ending the session might have to be a battery pull. The big problem are sound drivers, GSM radio/modem drivers and on screen input.
Dvdivx:
Thanks, we're on the right track, however fastboot won't work on our devices either...again because of nand (that's why I had to make my kernel into an update.zip and sign with test keys - the evo boys just use fastboot to update their kernels). MAYBE we could get one of the distros installed in recovery with update.zip, but I don't see how we could boot android too if we go this method.
Shame I went to all the trouble of building that kernel....oh well. Maybe we will have nand unlock soon and get to use it yet.
Keep me posted if you find something out that hasn't been mentioned here. Thanks.
Sent from my ADR6300 using XDA App
I've been trying this for the last few days and stumbled uppon this thread when trying to get around the problem of mount -o loop.
I'm using http[://]nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/ as my guide and running through the two scripts manually adjusting as needed.
Thanks to your kernel i was able to get the ubuntu.img mounted. Here is what I've done so far...
#running jager chocolate rom with
#reboot recovery
mkdir /tmp/system
mount -o rw -t yaffs2 /dev/block/mtdblock3 /tmp/system
cd /tmp/system
cp /sdcard/ubuntu/fsrw .
cp /sdcard/ubuntu/bootubuntu .
cp /sdcard/ubuntu/unionfs .
cp /sdcard/ubuntu/mountonly .
chmod 4777 fsrw
chmod 4777 bootubuntu
chmod 4777 unionfs
chmod 4777 mountonly
#reboot and connect with adb shell
export kit=/sdcard/ubuntu
export bin=/system/bin
export mnt=/data/local/ubuntu
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
mkdir /data/local/ubuntu
mount -o rw,loop -t ext2 $kit/ubuntu.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "127.0.0.1 localhost" > $mnt/etc/hosts
chroot $mnt /bin/bash
So.... now I've got "[email protected]:/#"
And...
# uname -a
Linux localhost 2.6.29 #1 PREEMPT Sun Jul 11 03:35:47 EDT 2010 armv7l GNU/Linux
# chroot $mnt /bin/bash
[email protected]:/# cat /etc/issue
Ubuntu 9.10 \n \l
I think I'd call that a success.... Someone care to confirm?
Done with the following:
apt-get update
apt-get install tightvncserver
apt-get install lxde
export USER=root
vncserver
Over to androidVNC... The connection is taking forever to go through
When i go back to the terminal and cat /root/.vnc/localhost:1.log I see the following:
xrdb: No such file or directory
xrdb: can't open file /root/.Xresources
Segmentation fault
Edit: Nevermind... it works. When I entered the address in androidvnc, localhost was autocorrected as locals and I didn't notice.
The following script I saved as ubuntu.sh to handle creating the environment variables and such that is required each time you launch ubuntu. i call it with sh ubuntu.sh since I cant make it executable on the sdcard and don't feel like booting into recovery to put it in /system/bin until I work out the little issues. The only problem with below is that it is not un mounting the ubuntu image... Any ideas?
#####BEGIN ubuntu.sh#####
export kit=/sdcard/ubuntu
export bin=/system/bin
export mnt=/data/local/ubuntu
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
export USER=root
mount -o rw,loop -t ext2 $kit/ubuntu.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
sysctl -w net.ipv4.ip_forward=1
echo Running ubuntu!
chroot $mnt /bin/bash
#After exit, cleanup
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
#####END ubuntu.sh#####
Also, I was able to launch a few applications inside my VNC session including firefox. It was really really slow (i guess as expected). i would be interested in a performance comparison from someone who has both an incredible and one of other devices people have made run ubuntu in this fashion.
Ok so I've wiped my phone and started from scratch to come up with an easy procedure...
All that you need is the kernel samwathegreat posted, ubuntu.img (in /sdcard/ubuntu) and the following script. You only need to boot into recovery to do a nandroid backup and to install the kernel.
###### BEGIN ubuntu.sh ######
export PATH=/system/bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
export USER=root
mkdir /data/local/ubuntu
mount -o rw,loop -t ext2 /sdcard/ubuntu/ubuntu.img /data/local/ubuntu
busybox mount --bind /dev/pts /data/local/ubuntu/dev/pts
busybox mount --bind /proc /data/local/ubuntu/proc
busybox mount --bind /sys /data/local/ubuntu/sys
sysctl -w net.ipv4.ip_forward=1
echo waiting for things to settle...
sleep 5
echo Running ubuntu!
chroot /data/local/ubuntu /bin/bash
#After exit, cleanup
umount /data/local/ubuntu/dev/pts
umount /data/local/ubuntu/proc
umount /data/local/ubuntu/sys
umount /data/local/ubuntu
###### END ubuntu.sh ######
Here is everything in one zip file: www megaupload com/?d=WO094E5Q
FANTASTIC!
pez:
Thanks so much!
I'm thrilled that my kernel did indeed go to some good use. You obviously have greater linux knowledge than I, as i would not have been able to do the scripting myself.
In the true spirit of teamwork, we've accomplished this WITHOUT having nand access. To me, this is quite an accomplishment.
Thanks to everyone that worked on this! Also - Although I did build the kernel myself, I feel that credit must also go to "Koush", who provided the means and instructions to package the kernel into an update.zip file, and sign with test keys.
Good Luck everybody, and have fun playing with ubuntu on your Incredible!!!
-samwathegreat
Here is a really crappy video I recorded. I open the browser at the start to show I disabled all network access and am indeed connecting to localhost.
http://www.youtube.com/watch?v=HMYvQ5r_OyA
If someone else could replicate my success and post a better video I'd appreciate it.
Edit: Just saw your reply samwathegreat. Did you get a chance to try it yourself? I wrote a little howto on androidforums.com (http://androidforums.com/all-things...-run-ubuntu-droid-incredible.html#post1127643) hoping that others would be able to confirm they were successful too.
Also, the key mapping is messed up when connecting with VNC, but I haven't had time to find out why.
This is pretty awesome. I'll have to try this later just for the hell of it.
Too cool. My ROM has a kernel capable of this. I'm gonna try!
ihtfp69 said:
Too cool. My ROM has a kernel capable of this. I'm gonna try!
Click to expand...
Click to collapse
Hell, you should package this in with your rom.
Gimpeh said:
Hell, you should package this in with your rom.
Click to expand...
Click to collapse
Seconded!
Vote called motion carried, the I's have it.
Gimpeh said:
Hell, you should package this in with your rom.
Click to expand...
Click to collapse
Wouldn't having something like this in your sky raider rom bloat it and cause more battery use having it run in the background?
kentoe said:
Wouldn't having something like this in your sky raider rom bloat it and cause more battery use having it run in the background?
Click to expand...
Click to collapse
If it's running all the time. As long as you have a kill command it should be fine.
Hey guys,
Ran into this today as I was browsing through the Vibrant dump and thought I would share it
What's needed:
A T-Mobile Vibrant
SU access(root)
busybox
It is possible that this might work for other Galaxy S phones, but as of yet I am unaware of whether or not they all have a shutdown animation.
Basically, this is a quick HOW-TO on removing or changing the quick little animation that plays when you turn off your phone. I'm pretty sure most people find it annoying and would like to turn it off, while others may want to do something interesting with it so I'll break it up into 2 tutorials(though they are fairly similar).
NOTE: This only works for the shutdown sequence. The boot sequence is stored in proprietary files called .qmg and doesn't apply to this simple hack.
Quick Structure Overview: (Just jibber jabber...read if you want)
Alright, so basically the animation is simply a bunch of PNG's that represent frames in the movie/animation. They are found in the folder '/system/media/video/shutdown' and are named under a framed convention "shutdown_x.png" where 'x' represents the frame number in the animation. There are 14 frames in the initial batch, and from what I've tested(which isn't a ton) that's the max frames, but you are more than welcome to try; it won't hurt anything if you do.
Also, based off my tests, the system will do any subset range as long as it starts at 1(so like 1-5 or 1-12 instead of 1-14). It also may be important to note that I have not tried any other files besides .png. It may be a good experiment to try other files. Post your results here; I'm sure someone will find them useful.
FOR BOTH:
If you want to back up the animation(terminal or adb shell):
Code:
//Name the directory whatever you want...this is just an example
$ mkdir /sdcard/animationbackup
$ busybox cp /system/media/video/shutdown /sdcard/animationbackup
REMOVE:
Simply remove the shutdown folder that holds all the frames.
Open terminal(or adb shell):
Code:
$ su
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
$ rm -R /system/media/video/shutdown
$ mount -o ro,remount -t rfs /dev/block/stl9 /system
You should now be able to shut off your phone and enjoy the nice shutdown progress spindle instead of the animation.
CHANGE:
Load up your list of PNG's that you want for your animation and throw them in a folder called "shutdown" (no quotes). Be sure they are named in this format:
Code:
shutdown_x.png
//where x is the frame of this image
Throw it onto your 15GB internal memory(Not the 2GB sdcard but the big one that the system references as /sdcard)
Then run this command(terminal or adb shell):
Code:
$ su
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
$ rm -R /system/media/video/shutdown
$ busybox cp /sdcard/shutdown /system/media/video/
$ mount -o ro,remount -t rfs /dev/block/stl9 /system
Lastly, there is some programs that will take a video file and convert it into frames(decompile them, in other words). I found Blaze Media Pro, yesterday and worked fine for this if you are interested.
UPDATE:
Batistian has figured out how to remove the 14 frame limit that seemed to be a requirement for the shutdown sequence. It requires a config file inside the shutdown folder. Attached I have the i9000's shutdown folder with the config file inside it. Also attached is the config file that you can just throw into your shutdown folder if you want it to progress more frames.
Also, bubonik has posted the directory locations of the audio sounds. You should be able to change these if you want, if you hate the T-Mobile branded sounds.
bubonik said:
Startup sound: /system/etc/PowerOn.wav
Shutdown sound: /system/media/audio/ui/Shutdown_128.ogg
Click to expand...
Click to collapse
Last attachment is the shutdown and power on sounds from the i9000. You can use these to replace those sounds using similar tactics that was mentioned in the tutorial.
UPDATE 2:
Replace your Bootup with the i9000 boot up
1) Download the attached Bootup.zip and unzip it. Contained is the bootsamsung.qmg.
2) Copy to your SD Card(the one that shows up as 15 gb)
3) Run this command in adb shell, terminal, or use Root Explorer:
Code:
$ su
$ mount -o rw,remount -t rfs /dev/block/stl9 /system
$ rm -R /system/media/bootsamsung.qmg
$ busybox cp /sdcard/bootsamsung.qmg /system/media/
$ mount -o ro,remount -t rfs /dev/block/stl9 /system
This should replace your boot up sequence
Thanks to Batistian, bubonik, jroid, and everyone else who worked on advancing the progress of this tutorial. I know a lot of you were digging through both the Vibrant dump and the i9000 dump, all for good reason
Lastly, I need to point out that I'm not responsible for any destructo-proceedings that may develop after following this tutorial. Know what you are getting into before doing anything that involves your system files.
nice stuff thanks for the post.
The startup/shutdown sounds are so annoying, this is a great start.
I was already looking into this yesterday, u beat me to it What I'm trying to do is get the galaxy S 19000 shutdown animation on the vibrant. I seen it in a vid someone posted about odin3, where I noticed by quick glance that the shutdown animation was similar to the galaxy S boot animation (with the cool blue chips rotating to form GalaxyS) I got a hold of a 19000 dump so i'll be looking into it
Tydiz said:
Code:
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
$ rm -R /system/media/video/shutdown
$ mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Code:
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
$ rm -R /system/media/video/shutdown
$ busybox cp /sdcard/shutdown /system/media/video/
$ mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Shouldn't that be:
mount -o rw,remount -t rfs /dev/block/stl9 /system
to mount rw
and
mount -o ro,remount -t rfs /dev/block/stl9 /system
to mount ro
??
Maybe I am missing something
thanks! worked like a charm, i can't wait to change my boot animation to android peeing on apple
What you guys don't like all that pink nonsense floating around?
Droid gets the cool eye and we get the love, hugs, kiss's, or whatever the heck it says.
t1n0m3n said:
Shouldn't that be:
mount -o rw,remount -t rfs /dev/block/stl9 /system
to mount rw
and
mount -o ro,remount -t rfs /dev/block/stl9 /system
to mount ro
??
Maybe I am missing something
Click to expand...
Click to collapse
They both work and seem to do the same thing. This is the command I've always used to grant the rw permissions in the system partition and its always worked fine. If I were to guess(and it probably is wrong), the yaffs(yet another flash file system) points the the rfs as a generalized pointer(in case something decides not to use rfs???). Anyway, both work on the vibrant from what I've tested
Zyxwvu44 said:
thanks! worked like a charm, i can't wait to change my boot animation to android peeing on apple
Click to expand...
Click to collapse
If you actually do this, let us know! I totally want that on my phone!
Sent from my SGH-T959 using XDA App
gravis86 said:
If you actually do this, let us know! I totally want that on my phone!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i had it on my droid. when i get home i can post the image files, but i don't know how we would load it on to the vibrant. all i had to do was update.zip for the droid, we may have to wait for a recovery to be working
is there a similar process for startup?
basataom said:
is there a similar process for startup?
Click to expand...
Click to collapse
boot process handles its animation a lil differently. There are 2 animations (tmo & galaxy S) that reside in /system/media/ that are called by 2 scripts in /system/bin precisely bootanimation and bootanimation2nd. shutdown is alot easier to replace and mod because it's handled by a dedicated shutdown app that processes the .png's as long as they're in order in sequence of shutdown_.png In order to mod bootanimation, we need a tool that can read .qmg files. I'm pretty sure inside the .qmg's files are png's also as aosp's bootanimation.zip for eclair contain .png's
Ok so a little on my progress:
I'm not able to delete the whole /shutdown dir and copy it over from the sdcard it gives me this error cp: 'omitting /sdcard/shutdown' so instead I did:
mkdir /system/media/video/shutdown
cp /sdcard/shutdown/* /system/media/video/shutdown
and it copies, however, it gets all mixed up and out of order. The result is the shutdown animation appearing but not running, it gets stuck obviously because the png's are out of order. Any idea as to how to transfer the contents into /shutdown without the system screwing up the order?? There's 60 png's for this animation btw
here is the droid peeing on apple boot animation for the droid. the desc file tells it the resolution, how many times to repeat, the lag in between switching sections. i dont remember the specifics of that file, but im sure its different for the vibrant anyway,
well, these pictures could be used at least
kizer said:
What you guys don't like all that pink nonsense floating around?
Droid gets the cool eye and we get the love, hugs, kiss's, or whatever the heck it says.
Click to expand...
Click to collapse
Its cause Tmo loves us! They have to give us the hugs and kisses somehow
Zyxwvu44 said:
here is the droid peeing on apple boot animation for the droid. the desc file tells it the resolution, how many times to repeat, the lag in between switching sections. i dont remember the specifics of that file, but im sure its different for the vibrant anyway,
well, these pictures could be used at least
Click to expand...
Click to collapse
I haven't tested it, but I formated your files so you should be able to transfer them and give it a go
jroid said:
Ok so a little on my progress:
I'm not able to delete the whole /shutdown dir and copy it over from the sdcard it gives me this error cp: 'omitting /sdcard/shutdown' so instead I did:
mkdir /system/media/video/shutdown
cp /sdcard/shutdown/* /system/media/video/shutdown
and it copies, however, it gets all mixed up and out of order. The result is the shutdown animation appearing but not running, it gets stuck obviously because the png's are out of order. Any idea as to how to transfer the contents into /shutdown without the system screwing up the order?? There's 60 png's for this animation btw
Click to expand...
Click to collapse
Looking into this as well. I have the files copied over...I'll play around with it when I get a chance and update when I find something new about it
Tydiz said:
Looking into this as well. I have the files copied over...I'll play around with it when I get a chance and update when I find something new about it
Click to expand...
Click to collapse
you have the galaxy S shutdown files? I can upload if you need them. I also have the files copied over, however, like I mentioned earlier the order is all screwed up. When I shutdown, it shows the galaxy S logo and about to start the animation but stops and the tmobile audio plays like usual then shuts down. The audio for the shutdown anim. is in /system/media/audio/ui
You can also delete the entire /video folder.
Startup sound: /system/etc/PowerOn.wav
Shutdown sound: /system/media/audio/ui/Shutdown_128.ogg
I remember there was a time that the remount command was shorter for some ROM's on the g1.
Is
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
the only option for remounting system as rw?
Thanks for this. I used root explorer to make my changes. Now to find a better shutdown audio file.
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?
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