Database Users

[EXPERIMENTAL]-PROJECT JIT-(Just in time)EXPERTS ONLY |Aug 13th|

New as of Saturday August 8th
I will update the files every time I find a problem​
WARNING PLEASE READ:
Project JIT is highly highly experimental! If you are to do this, MAKE A NANDROID BACKUP IN ROM MANAGER OR RECOVERY! There are always chances of something going wrong. I nor anyone else is responsible of what happens.
Experienced users please know the possible risks:
Boot Looping, requiring a restore
Constant FC's
Wiping everything
These are just the risks, please note it is not 100%​
JIT stands for Just in time compiler. It does not like Touchwiz, so download ADW.Launcher or LauncherPro before starting and set it as default.
This whole process is in ADB. If you dont know how, or what it is, DONT DO IT!
Things to do before you start:
-Download a different launcher than TouchWiz
-Make a backup in recovery or Rom Manager
-Did I mention DO A BACKUP!
-If you have an external SD card, pull it out
-Download the vmlibs file
What I expect you to know before you start:
-ADB
-What JIT is
-How this will effect the performance
-The risks
-How its not my fault if you screw your phone over
-How experimental this is
-How to make a nandroid backup
-How to make a nandroid restore
Remember, this is experimental and I cannot guarantee for it to completely work.
Download This- vmlibs.zip
Then follow these steps:
-Make a backup!!!
-Create 2 folders on your internal sdcard: “jit” & “dalbk”
-Extract the vmlibs.zip to the “jit” folder on your sdcard
-Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad, text edit or similiar program.
-Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Edit the following line:dalvik.vm.startheapsize=8m
to: dalvik.vm.startheapsize=12m
-Save the changes
-Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit, but if your phone boot loops, thats why you have A BACKUP!
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
While in recovery, wipe the dalvik cache, this will prevent it from boot looping.
To Disable
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
If that fails, that is why you have a backup. To restore, go to recovery, click on nandroid, and restore from your backup.

Reserved for future posting

Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App

LGSilva said:
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It didn't here. Not sure if that is due to other fsckup or the fact that I was running I9k rom with my kernel and sdcard hack...

Restoring to stock to give this a whirl

tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are

hansmrtn said:
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
Click to expand...
Click to collapse
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).

NukaCola said:
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
Click to expand...
Click to collapse
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me

hansmrtn said:
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
Click to expand...
Click to collapse
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.

NukaCola said:
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
Click to expand...
Click to collapse
Yeah, thats why I had to fix some stuff lol. I noticed that it wouldnt go past the att screen. Now it should work correctly. The worst that could happen now is it boot loops on the Galaxy S screen

Haha I was just about to post the same problem, downloading new file and trying it again!

Zilch25 said:
Haha I was just about to post the same problem, downloading new file and trying it again!
Click to expand...
Click to collapse
Hey, when you edit the build.prop to add the dalvik vm line, can you look for the vm heap size and change it from 48 to 32? I am about to test doing that, and I would like more feedback

Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!

Zilch25 said:
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Click to expand...
Click to collapse
Dont worry, I will try it

ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.

Zilch25 said:
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Click to expand...
Click to collapse
Do you know how to run a logcat?
Its gonna take a while because its re writing the dalvik cache

That I do not, but I'm willing to try it if you can give me a quick crash course

Zilch25 said:
That I do not, but I'm willing to try it if you can give me a quick crash course
Click to expand...
Click to collapse
Well I am looking at my logcat now, and it is just repeating boot animation.
A logcat is useful, so how you do it is adb logcat.
I changed a couple things to test around with here is what I did-
I added all of this to the build.prop-
#JIT
dalvik.vm.execution-mode=int:jit
and changed:
dalvik.vm.heapsize=48m
to
dalvik.vm.heapsize=32m
Right now I am resorting to try the older vmlibs with the new settings

Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?

Zilch25 said:
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Click to expand...
Click to collapse
No thanks for the feedback. Its only worked for me once, and then when I rebooted it got stuck in a boot loop.
Whats a device thats running android 2.1, and has a jit hack that is extremely similar to the Galaxy S series?

Lag Fix for Galaxy S "Showcase"

I'm sorry to post this in the Fascinate forum, but as you all know Cellular South's version the "Showcase" is identical in hardware as is the Mesmerize, but there isn't a forum for either of them..
I see there's plenty of kernels and etc.. But is there just a simple lag fix that I can do to my Showcase that will make every day use better and less laggy?
A simple yes or no is fine with me.
if there is a way a link post or explanation would be VERY appreciated.
Thanks,
Elijahblake
(PS)Sort of on the same subject, but I read that gingerbread is going to support ext4 file system. I know the Galaxy S uses the RFS file system which I believe is where we get the lag in the first place.. Will it be possible to switch file system formats?
I'm not real familiar with all these Linux formats. Would it be similar to reformatting like from FAT32 to NTFS?

If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.

jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app

elijahblake said:
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
Click to expand...
Click to collapse
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum

jt1134 said:
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
Click to expand...
Click to collapse
will do.. May take me some while to get all this info gathered..
quick question? I've read of some people not being able to see certain apps in the market after rooting.. Is this still the case?
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?

elijahblake said:
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
Click to expand...
Click to collapse
To get the upgrade, you shouldn't have to un-root, but you should probably disable voodoo first as the update will almost certainly have a new kernel, and applying the update without disabling voodoo could cause quite a headache.
If you do apply the update right away, you could quite possibly loose root, so you may want to wait until the devs re-root the update. This could make things easier for you as the rooted update will also likely be cleaned up some.
To disable voodoo, you'd just need to create a file called "disable_lagfix" in /sdcard/voodoo and then reboot your phone. See the thread in the dev forum about removing voodoo for more details if you want.

ok well it looks like I'm rooted.. Now I tried to open the ADB that came in the fascinate root zip but it's not opening for more than a split second... you have a download link?
Also can uninstall all this bloatware now??
edit.. thought I had Android SDK on this laptop.. Downloading it now

jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake

elijahblake said:
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
Click to expand...
Click to collapse
I have c:\androidsdk
I put ADB inside tools and it sees my device when I run ADB devices
But on the commands you listed nothing happens, I'm not sure if that's the entire commands or if I'm supposed to add something to them..

Try to run the following
Code:
adb shell cat /dev/block/bml7 > /sdcard/zImage
adb shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
adb shell mount
or just typing "adb shell" and entering the commands at the new prompt, and typing "exit" to get back to the normal command prompt.

here's what happened..
the first two commands didn't work. DO i need to create a folder name zImages?
The second command said access denied..
You tell me if the mount worked haha..

jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit

well, it granted me SU rights.. but still a no go...

i figured since i was in shell i shouldn't type that.. still got no directory found...

imnuts said:
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
Click to expand...
Click to collapse
would root explorer make this any easier?

I just tested out all of the commands on my Fascinate and they all worked, so I'm guessing that the Showcase is putting stuff in a different place. jt will have to help you out further as I'm not sure of where else to look for the info he needs.

elijahblake said:
i figured since i was in shell i shouldn't type that.. still got no directory found...
Click to expand...
Click to collapse
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.

GeekMouse said:
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
Click to expand...
Click to collapse
I typed it exactly the way you said.. still got this..
Can you take a shot at it?

elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
It doesn't need shell at the beginning.

elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
This is how it should be typed
Code:
adb shell
su
cat /dev/block/bml7 > /sdcard/zImage
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit

How do I do system dump for Nexus S

I'll be picking up an NS first thing Thursday morning. If someone tells me how to do a system dump I will do it right after getting the phone. Spread the love.

irishrally said:
I'll be picking up an NS first thing Thursday morning. If someone tells me how to do a system dump I will do it right after getting the phone. Spread the love.
Click to expand...
Click to collapse
If I get the phone i will dump it and make rom thats prerooted with busybox. If I dont then here is the commands to dump system.
1 root your phone
2 install busybox to /system/xbin
3 enter these commands from terminal
4 su
5 cd /sdcard
6 chmod 777 /system/xbin/busybox
7 /system/xbin/busybox tar czvf dump.tar /system

Nice one irish, hope you can release it soon

Nice one, let us know. Your be helping alot of people out!

shep211 said:
If I get the phone i will dump it and make rom thats prerooted with busybox. If I dont then here is the commands to dump system.
1 root your phone
2 install busybox to /system/xbin
3 enter these commands from terminal
4 su
5 cd /sdcard
6 chmod 777 /system/xbin/busybox
7 /system/xbin/busybox tar czvf dump.tar /system
Click to expand...
Click to collapse
Why not adb pull /system/ ?

Anderdroid said:
Why not adb pull /system/ ?
Click to expand...
Click to collapse
To save u the step of packaging the dump for distribution later

Daneshm90 said:
To save u the step of packaging the dump for distribution later
Click to expand...
Click to collapse
Yeah but you can adb pull without rooting ?

We need a new way to boot into recovery

Currently there is no way to boot directly into cwm from powered off this is of great nuisance to rom developers as if a bsod is encountered you must either use adb to restore a custom rom and then bit into recovery to restore your nandroid or if adb is not working then you must restore the stock image via nvflash not available for mac then reflash cwm and restore nandroid what we need is a key sequence like many android devices
Sent from my HTC Desire using XDA App

bob1369 said:
Currently there is no way to boot directly into cwm from powered off this is of great nuisance to rom developers as if a bsod is encountered you must either use adb to restore a custom rom and then bit into recovery to restore your nandroid or if adb is not working then you must restore the stock image via nvflash not available for mac then reflash cwm and restore nandroid what we need is a key sequence like many android devices
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Incorrect
We have two better methods to restore to a working rom than what you said above
1)adb into CWM and restore
2) a tool for turning nandroid backups into nvflashable update.
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
Edit: oops didn't read your post properly, here is info for others anyway.
We cannot currently boot like you suggest due to the fact CWM is not installed in a regular recovery partition, we might be able to make a key combo similar to the "host/slave" switch however this is only in boot.img so will rely on at least getting to that part of boot (which is the same as adb).

Thank you for the second the first is useful but adb rarely works with bsod
Sent from my HTC Desire using XDA App

I should have added these were the only ways I knew
Sent from my HTC Desire using XDA App

Would it be possile to have some kind of boot menu like the motorola defy 2ndInit mod?

Pyr0x64 said:
Would it be possile to have some kind of boot menu like the motorola defy 2ndInit mod?
Click to expand...
Click to collapse
Exactly - or even something like this:
http://forum.xda-developers.com/showthread.php?t=859571
It's being used on my Xperia X10 phone (the needed files are now bundled in roms), to get around the fact that we can't flash a recovery image to a partition. It uses a key press (or three) at boot, to trigger the recovery loading sequence.
This may help too:
http://forum.xda-developers.com/showthread.php?t=999393
I've attached the specific file that gets edited (in a zip file).
Also, here's the code:
Code:
[B]#!/system/bin/busybox sh
cat /dev/input/event2 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck ]
then
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /data
umount -l /cache[/B]
[I]# Extract recovery
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar[/I]
[B]# Umount system
umount -l /system
chroot / /init
fi[/B]
# zdzihu: boot custom kernel
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot.img > /proc/splboot/boot_img
sleep 3
echo > /proc/splboot/boot
/system/bin/charger
# remount rw
mount -o remount,rw rootfs /
cd /
rm -r /sdcard
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
# zdzihu: hack-fix
if [ -e /data/data/com.android.providers.telephony/databases/telephony.db ]; then
/system/bin/chroot / /init
exit
fi
chroot / /init
The bold part is the section that we could use. The section in italics would have to be removed, and replaced with some commands specifically related to loading the recovery image on the Vega - maybe Paul could help?
The only problem with this is that if the 'system' partition were to be formatted, this would stop working.

2int like on defy would be the best option i think because we still need to be abel to acess stock recovery so that you cab easily restore stock rom if you realy mess up unless their is another way to enter nvflash from within a recovery
But yeah i agree we need a way on boot its a pain in the ass having to reflash stock then reccovery every time i test my rom

add.thebad said:
But yeah i agree we need a way on boot its a pain in the ass having to reflash stock then reccovery every time i test my rom
Click to expand...
Click to collapse
You don't have to have a look at lennyuks post at the top flash a cwm (nandroid) backup through nv flash
typed by using my vega as a tennis racquet

bob1369 said:
You don't have to have a look at lennyuks post at the top flash a cwm (nandroid) backup through nv flash
typed by using my vega as a tennis racquet
Click to expand...
Click to collapse
Thats a nice solution, I agree.
But still I miss the possibility to go to recovery directly from the tablet. Same as I do from my HTC Desire.
Being on the train, downloading and flashing a new ROM, Kernel, or whatever, I do not have a laptop or PC with me to use your method. Just need to get somehow into recovery to restore my last working ROM.
"typed being on the other side of the tennis court using my viewpad as a tennis racquet "

Lennyuk said:
Edit: oops didn't read your post properly, here is info for others anyway.
We cannot currently boot like you suggest due to the fact CWM is not installed in a regular recovery partition, we might be able to make a key combo similar to the "host/slave" switch however this is only in boot.img so will rely on at least getting to that part of boot (which is the same as adb).
Click to expand...
Click to collapse
we totally have recovery ins a own recovery partition called... well... recovery...
Code:
[[email protected] system.cm7]$ adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00020000 "misc"
[B]mtd1: 00500000 00020000 "recovery"
[/B]mtd2: 00800000 00020000 "boot"
mtd3: 09440000 00020000 "system"
mtd4: 02000000 00020000 "cache"
mtd5: 00400000 00020000 "staging"
mtd6: 12ea0000 00020000 "userdata"
edit: as a solution to this problem, getting "adb reboot recovery" working would work for most cases - since bootloops usually allow a short time for adb - enough to send one command. only exception are kernel screwups - but if you tweak your own kernel, you probably use fastboot to boot it without flashing anyways.
cm7 will have reboot to recovery running somewhere in the future.

it's possible to use adb shell:
HomerSp said:
So we all know rebooting into recovery can be a big pain on the Vega, especially as there's no key combination when booting.
I've found that you can use two bins to reboot while the device is booted (it needs to at the very least start the dexopt on the framework for this to work). Simply type this in a shell and the device will automatically reboot into recovery:
Code:
recovery_2 && reboot
Attached is a small bin (with source code) that allows you to use adb shell reboot recovery, although my goal is to make adb reboot recovery work as well. Simply push it to /system/bin and chmod 0755 it.
Click to expand...
Click to collapse
http://www.villainrom.co.uk/forum/s...ot-into-recovery-without-an-app-(devs-mainly)

[guide] lg l5-ii dual e-455

THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
Code:
Factory Firmware Link for LG-E455
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=_IMEI_NUMBER_
==>
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW376985432109876543213/V10D_00.kdz
G

hacking notes
[RESERVED]
Code:
$ ./adb shell /system/xbin/busybox | head -5
BusyBox v1.21.1 (2013-12-29 07:49:16 EST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices.
$ ./adb shell /system/xbin/busybox mount -v
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
[email protected] on /system type ext4 (rw,relatime,noauto_da_alloc,commit=1,data=ordered)
[email protected] on /data type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered)
[email protected] on /cache type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
[email protected]_lg on /persist-lg type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /persist type ext4 (rw,nosuid,nodev,relatime,data=ordered)
[email protected] on /mpt type ext4 (rw,nosuid,nodev,relatime,data=ordered)
/[email protected]_ro on /system/secro type ext4 (ro,relatime,data=ordered)
/dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
$ ./adb shell /system/xbin/busybox cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 0000f400 00002800 "sec_ro"
emmc_p3: 00014800 00004000 "persist_lg"
emmc_p4: 00018800 00003000 "persist"
emmc_p5: 0001b800 0000b000 "mpt"
emmc_p6: 0002b800 00005000 "swap"
emmc_p7: 00031000 0021d800 "android"
emmc_p8: 0024f000 0009a800 "cache"
emmc_p9: 002ea000 00443000 "usrdata"
emmc_p10: 0072d800 00005800 "fat"
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-12-23 21:47 mmcblk0p10 -> /dev/block/mmcblk0p10
PARTITION BACKUP
Code:
dd if=/dev/block/mmcblk0boot0 of=/sdcard/Download/mmcblk0boot0.img
dd if=/dev/block/mmcblk0boot1 of=/sdcard/Download/mmcblk0boot1.img
dd if=/dev/block/mmcblk0p1 of=/sdcard/Download/mmcblk0p1-ebr1.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/Download/mmcblk0p2-secro.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/Download/mmcblk0p3-persist_lg.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/Download/mmcblk0p4-persist.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/Download/mmcblk0p5-mpt.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/Download/mmcblk0p6-swap.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/Download/mmcblk0p10-fat.img
Tried
adb reboot oem-unlock
The phone booted back up, but I have no clue if it did unlock or not.
It did not prompt for anything on reboot. I guess its safe to assume
it is still locked...
Well I dont know any unbrick procedure for this devices, so I will
tread cautiously.

In my view this mobile is a perfect one.
regarding software when it rooted it supported framework, busybox etc.. and worked like a chrm never a hang.....
but as for my knowledge for some reason lg took preventive steps not to touch the boot loader or pre loader of this device.......
As coming to the recovery and stock rom facility, practically there is no need for that.....
All the functions of a stock rom was enabled by rooting this device using vroot software........
after rooting this, convert the super su to english by following the below thread
http://forum.xda-developers.com/showthread.php?t=2337802

I don't think LG took any special steps... its just that this phone is not so common/popular with developers
Sent from my Nexus 5 using Tapatalk

ghatothkach said:
THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
G
Click to expand...
Click to collapse
Hi and thanks for that
latest version of vroot is 1.7.5
how can I download 1.7.3 ?

use new version
x-jack said:
Hi and thanks for that
latest version of vroot is 1.7.5
how can I download 1.7.3 ?
Click to expand...
Click to collapse
download new one it works (tested)

E455 story
Let's put all solutions for E455 here.
So far I managed to root it, using the chinese tool. There are 2 variants of that tool, Chinese (mgyun.com/vroot) and with English UI (mgyun.com/en/getvroot).
If you don't like the chinese dialog box, everytime it asks for root permissions, you can install later SuperSU (by Chainfire) or Superuser (by ClockworkMod). By my opinion both are good and work.
Also in our phones we have a problem which is common for the new "age" of androids. When we install an application, the "big" chunk of data are installed in the internal memory (2GB) instead of the external (SD). In long terms that means that android will notify us that we don't have free space for applications, because the internal memory run out of space. In real, the SD card is used only for photos/videos/etc.
The only solution for that is a future hotfix patch from LG (which i believe it will take a LOT of time) or in the best case, the KitKat update (when it will be available and if..)
Other solutions can be by modifying some core files inside android. It can be done but with a slight chance of bricking your phone. There are also programs who manage to transfer the files from internal to external.
ALL THESE methods require that you have the files already placed at internal memory and then you transfer them to external. What happens if you can't because you don't have free space at the internal?
I believe E455 is a very good model, which worths the money we spend, for the job it has to do. Dual SIM, nice battery, nice screen but without the support of developers because it's not mainstream model.

IGGYVIP said:
download new one it works (tested)
Click to expand...
Click to collapse
thanks :good:

There is a button to thank me
x-jack said:
thanks :good:
Click to expand...
Click to collapse
Nice one for feedback

tharorris said:
Let's put all solutions for E455 here.
I believe E455 is a very good model, which worths the money we spend, for the job it has to do. Dual SIM, nice battery, nice screen but without the support of developers because it's not mainstream model.
Click to expand...
Click to collapse
Oh how I wish it was a main stream model. I would actually love "any" 2+sim model which could get AOSP/AOKP and kernel customizations
and is as small and handy as this one here... I would not even mind spending as much as a Galaxy-S5 to get a 2+sim model here in the US, but unfortunately in the US, not only we want one wife we also want one carrier, for the phone so its not going to happen any soon.
I still have the phone not got time to hack it.
G

Yep
ghatothkach said:
Oh how I wish it was a main stream model. I would actually love "any" 2+sim model which could get AOSP/AOKP and kernel customizations
G
Click to expand...
Click to collapse
I would love it too but as history show us, never was a dual sim mobile phone "mainstream" before.
This one is small, has nice battery life, does not lag.... yet we stuck on this.
I know for sure that L7 II took KitKat official, when ours will get it? And i have a strong reason that even the simple sim will get KitKat, and we will still wait...
I will keep it rooted and wait.

tharorris said:
I would love it too but as history show us, never was a dual sim mobile phone "mainstream" before.
This one is small, has nice battery life, does not lag.... yet we stuck on this.
I know for sure that L7 II took KitKat official, when ours will get it? And i have a strong reason that even the simple sim will get KitKat, and we will still wait...
I will keep it rooted and wait.
Click to expand...
Click to collapse
did u try to unroot it?

LG E455 IMEI Problem
Hi,
I dont know if this is the correct place for that cuestion, but i see its a dedicated thread to lg 455, so i try to get some help.
I got that phone a few moths ago and after some 3g issues discovered a problem with the frecuencies of the baseband; solved that problem flashing a stock rom following this tutorial http://forum.xda-developers.com/showthread.php?t=2702213. All gone ok but a few day ago both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!

GUYS!
There's a topic in geekdashboard listing phones getting kitkat. Our mobiles are listed there! Its called "list of phones getting android 4.4 kitkat firmware".

ghatothkach said:
THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
G
Click to expand...
Click to collapse
when i press for recovery mode it says this back up is for service only .. pls help i need to fix my lg because its boot loop.

Is there any after market ROM for our phone? I have not found anything yet.
Sent from my SM-T320 using Tapatalk.

been a while...
howdy guys...
Its great to see that Lolipop 5.1 has native support for Dual Sim..
http://officialandroid.blogspot.com/2015/03/android-51-unwrapping-new-lollipop.html
I wish we can see some native AOSP roms for this phone...
My status remains the same, I have the phone but no time to hack it !
G
PS: Did anyone try...
http://www.unlock-bootloader.info/mp3-0/lg-optimus-l5-ii-dual-e455-5373.html
The instructions are useless, I have the latest adt/5.1 updates and adb cannot boot this phone into fastboot mode... I want to unlock the bootloader but in vain..
those instructions are crap... anyone else got any success ?
Click to expand...
Click to collapse

big-time screwup..
OK I had a rooted device...
now in the process of creating busybox links I overwite the suid-su binary with a link to busybox which is not suid !
No matter what I try I cannot get to remove the su link... any hints... The problem is the device usually mounts /system/ in ro mode and you need su/root to remount in rw mode...
The Superuser app always now complains of needing to install su binary and does not do anything in Normalmode and there is no TWRM/CWM on my phone...
any one know any tricks...
Huh....
Update:
- Got the KDZ file...
- Cant flash with the KDZ flasher
- Cant extract the KDZ file using the KDZ python tools
- STILL STRUGGLING
Click to expand...
Click to collapse
:cyclops::cyclops:
SUCCESS!.. in a wierd way...
- Rooted again with the VROOT app, os of today it is the 1.8.2.13115 version
- re-installed CF SuperSU
- re-installed SF SuperSU in system
AND... I am back in business...
Click to expand...
Click to collapse
G

Try
niconiconico111 said:
Hi,
I dont know if this is the correct place for that cuestion, but i see its a dedicated thread to lg 455, so i try to get some help.
I got that phone a few moths ago and after some 3g issues discovered a problem with the frecuencies of the baseband; solved that problem flashing a stock rom following this tutorial http://forum.xda-developers.com/showthread.php?t=2702213. All gone ok but a few day ago both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
Click to expand...
Click to collapse
Try chamelephone app it helped me with idroid imei problem
But you need a. Brand new simcard which you will insert after the program asks u to reboot when generation of imei is done thanks

ghatothkach said:
THIS THREAD IS for LG L5-II DUAL E455 ONLY
Please dont post anything else...
DOWNLOAD MODE:
Press VOL+ AND VOL- and power up the device
RECOVERY MODE
Press VOL+ AND QUICK-ACCESS and power up the device
FACTORY RESET
Press VOL- AND QUICK-ACCESS and power up the device
ROOT
Install http://www.mgyun.com/vroot (v1.7.3 tested as of this post)
The VROOT software also installs "working" LG drivers for the device.
Just follow instructions on the software... Installs a chinese version of SU, which seems
to have a english translation. This is not Chainfire's SuperSU.
- Installing ChainFire's SuperSU
Main Thread
SuperSU on Google Play (free)
Install the App from the market, or sideload the .apk
- When it installs it will use SU perms from the chinese app to install, and also prompt for removal of old root apps
- as soon as it is installed, make sure you go to settings and install it as a system app.
- reboot the phone
BUSYBOX
attached :
f68e66cf7df687887311c11d8e37fd3d *busybox
0548969bd4969c42f36233e91ffd0257 *busybox.zip
Code:
$ adb shell "mount -o rw,remount /system"
$ adb shell "chmod 0777 /system/xbin"
$ adb push busybox /system/xbin/
$ adb shell "chmod 755 /system/xbin/busybox"
$ adb shell "chmod 0755 /system/xbin"
Code:
Factory Firmware Link for LG-E455
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=_IMEI_NUMBER_
==>
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW376985432109876543213/V10D_00.kdz
G
Click to expand...
Click to collapse
Why all of that doesn't worked for me? any solution for my problem? Thx