Database Users

[SOLVED]Just flashed latest 0.3 ROM - no root?

EDIT: SOLVED
I just flashed the latest ROM but when I enable debugging and type "adb shell" im getting "$" instead of "#"...? I'm trying to remount the filesystem "mount -o rw,remount /dev/block/mtdblock3 /system" but am getting access denied because of this.
Do I need to try reflashing?

you need to adb shell then type "su" to get to a root shell i believe

EDIT: SOLVED! I was too blind to notice i had to allow the root request on my phone. thanks!
after i type 'adb shell' and get "$" everything i type next just gets echoed
ex:
Code:
$ su
su
test
test
etc

gohamstergo said:
EDIT: SOLVED! I was too blind to notice i had to allow the root request on my phone. thanks!
after i type 'adb shell' and get "$" everything i type next just gets echoed
ex:
Code:
$ su
su
test
test
etc
Click to expand...
Click to collapse
Usually if you have root, adb shell will automatically grant root access...the notification on the phone is a new one to me...

xsnipuhx said:
Usually if you have root, adb shell will automatically grant root access...the notification on the phone is a new one to me...
Click to expand...
Click to collapse
It seems to be caused by the "Superuser Permissions" app, included with the ROM

Possible new way to ROOT

New possible root method on Thinkpad tablet forums, by OPDECIRKEL. He needs help testing it out.
look here and lets cross our fingers =D
http://www.thinkpadtabletforums.com...nt/yareftpt-yet-another-root-exploit-for-tpt/

opdecirkel released the exploit -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/

unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
***EDIT***
updated script worked!

-=HOLLYW00D=- said:
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
Click to expand...
Click to collapse
Not sure if it can help you, but try checking the TPT forum thread again, there has been some advances and troubleshooting going on

Moved To General​
As the first post is just a link and contains no development, this has no place in this section​

updated -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
Someone thinkpadtabletforum reported that it worked for him.

updated script worked for me! cwm installed fine as well!

I achieved root with the new method on OTA 2.5. Also installed CWM with no issues. Works great.
Sent from my PC36100 using Tapatalk

I can confirm it worked!
I had to update first because the "Disable Battery Discharge" option was not there. (I guess my Tablet stopped getting OTA updates since I was on ThinkPadTablet_A310_02_0024_0065_US... Also, you have to update one at a time, you can't go from 24_65 straight to 37_75. Also, I stopped at 39_86 since I was impatient.)
I like this once since we can see how it worked rather than blindly running some guys program (I never tried the first root.)

I can also confirm the new method to be working. Just rooted my 0089_WE TPT. Works like a charm

I am quoting the following post (i don't have privilege to post there): forum.xda-developers.com/showpost.php?p=23902281&postcount=64
daswahnsinn said:
I unrooted and then updated, now I can't root. I updated the SDK and made sure I have the proper drivers needed. So I take back my easy comment. I'll keep trying I might just manually push the files back.
Click to expand...
Click to collapse
How did it fail? At which stage and what error did you get?

Okay, I'll try and flash the oldest update zip, and it fails as it should, then I wipe the cache part, reboot, and I hit enter when I gets to the unlock screen then the CMD window closes.
EDIT: I spent a good hour or so combing through my PC and these forums and tried both methods a lot, and this one finally worked. It wouldn't let me get to the /cache/recovery/pwn/su part of the script. Thank you all for your support.

I have problems...
Hi all,
Apologizes for my english, too bad to discuss this kind of issues. Sorry in advance.
I had the "fantastic" idea to update the firmware some weeks ago, when I was SU. After this, I've lost most of capabilities!
I tried to follow the procedure, but I cannot reach 'root' in any case. I have version WE089. Downloaded US060, but there's only 065 for Western Europe. I got both, just in case..
Unfortunately, in the first step it failed I'm not able to update anything. The process crashes when is loading old firmware, either US060 or WE065.
I've realised that during the process I loose the USB link connection (when I reboot), and the system tries to install again and again the driver. If the TPT is running in recovery mode, it seems that is not connected via USB... If I have the tablet in "normal use", I see it through the Windows Desktop.
Other question: should I disconnect the Internet connection?
I guess other requirements are right (ADBD, debugging mode,...). It's really annoying, it took me a lot of hours and I haven't found any solution.
Can anybody help me? What I'm doing wrong?
Cheers!
jm
W7 64bits - TPT WE089

@jm
goto device manager. right click on Android device. reinstall device driver.
This worked for me in recovery when the device was not recognized.
Edit: look here: http://forum.xda-developers.com/showthread.php?t=1471106&page=2

What do you mean with loosing the connection? Is the adb driver installed correctly? Where did you get it from? Is it an genuine lenovo driver? If so, than you shouldn't worry!
Perhabs it's the MTP driver, that is missing when you boot into recovery? If it's the adb driver, than you should try jlove's method.
In addition I wanted to inform you, that the new method worked for me, too! Even with some complications... by this way, thanks again to opdecirkel!
Because the run.bat script did't worked correctly, I had to do it manually. So I put the "yareftpt" on C:\\, started cmd.exe, booted the TPT into recovery and changed the directory in cmd.exe with "cd.." to "cd yareftpt" ...followed the instructions with the update...
echo 4. Reboot in RECOVERY: (shutdown the tablet, then start it and press volume + few times until it starts in recovery)
echo 5. Go to apply update, select the update from the sdcard and try to apply it. It will fail, but that is OK.
echo 5. Then, go to 'WIPE CACHE PARTITION' and select it (navigate with volume buttons and select it with power button),
echo 6. When wipe cache complete, press (here) ^<ENTER^>.
and after that I copied the first line of the script into cmd and executed. I did it line after line, just to the next step. (dark green= copy line after line, paste and execute)
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
echo 7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete press (here) ^<ENTER^>
pause
some of commands might cause failures, but don't worry and just go on
adb shell "/system/bin/rm /cache/recovery/log"
echo 8. On the device, select REBOOT. When startup COMPLETE press (here) ^<ENTER^>
pause
adb push Superuser.apk /data/local/pwn/Superuser.apk
adb push busybox /data/local/pwn/busybox
adb push su /data/local/pwn/su
adb push pwn-in.sh /data/local/pwn/pwn-in.sh
adb shell "/system/bin/chmod 777 /data/local/pwn/pwn-in.sh"
echo Your PC command prompt appears next. Do the following things:
echo 1. adb shell
echo when '$' (adb shell) appear, do:
echo 2. /cache/recovery/pwn/su
echo when '#' appears. You are root. run the following:
echo 3. /data/local/pwn/pwn-in.sh
now you should try if you have su, even if you don't see in your app list..
download root checker, install, open and try it!
You should have root right now.
In my case, i had root, but no CWM!
So I had to install in manually, but with root it should't be a problem. you only have to download the correct cwm version:
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
then I installed it with the Android Terminal Emulator app, because the cmd.exe method did't worked for me. You should just follow the instructions:
or you can copy img file on /data/local/ folder of your tablet (with a file manager with root permissions)
launch "Android Terminal Emulator" application
and tape the instructions
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
http://www.thinkpadtabletforums.com...nd-development/clockworkmod-recovery-for-tpt/
After a shutdown and reboot into recovery I had cwm! So I am able to do nandroid backups...
In this way, I would particularly like to thank to all devs that made the TPT root possible! Now i like my TPT 1000% more than before...e.g. no status-bar in lecture notes -> sooo great!!

I do get the following error maybe someone can help me out
[*]
[*]
[*]
/system/bin/mkdir: not found
/system/bin/mkdir: not found
cannot create /data/local/pwn-bak/install-recovery.sh.orig: directory nonexisten
t
/system/bin/mkdir: not found
699 KB/s (22364 bytes in 0.031s)
/system/bin/rm: not found
/system/bin/ln: not found
7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete
press (here) <ENTER>
Drücken Sie eine beliebige Taste . . .
it cant find the mkdir command very strange

I'm a little rusty, but are the / and \ facing the correct way? And are you in the correct directory? Not found usually means path is incorrect.

@rangercaptain
thats the commands from the root script. I didnt change them.
the commands are send over from adb shell and the tablet is in root directory i think.
When i go into shell and type in ls i get access denied error.

and you load the update zip and wiped cache before typing the commands, right? You have to do this every time you try to root...
Try to do it with another method. Don't do it directly trough adb shell...just type the shell commands in the cmd.exe
You just have to chance the directory in cmd, before executing the commands.
Then try not to input 'adb shell' before the shortened command, but the whole command as one line like:
adb shell "/system/bin/mkdir /data/local/pwn"
Perhabs it will work..?!?

@neos
yes i do the same procedure.
I also tried over cmd with adb shell "command" and also in shell.
Always the same error.
I looked into the system/bin directory and mkdir does have filesize of 0kb...

[Q] Need help pushing a system file with adb

I have bricked my device when I tried to copy framework-res.apk to the system folder. I renamed the old framework-res.apk to framework-res.apk.bak but before I could paste the new one the phone freaked out and rebooted and now I'm stuck at the ATT white screen. I have adb access though so I'm hoping I can just push the framework-res file using adb. Every time I try this though I get an error saying file system is read only. I know all I probably need to do is get the computer to mount system as read/write. I just don't know how to do this. Is there anyone out there who can help me out?

Modified from:
http://forum.xda-developers.com/showthread.php?p=41339365
You may need to do:
mount -o remount,rw /system
chmod 777 /system/framework

Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.

jack_slapped said:
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Click to expand...
Click to collapse
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.

jack_slapped said:
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
Click to expand...
Click to collapse
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot

alacrify said:
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
Click to expand...
Click to collapse
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.

jack_slapped said:
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
Click to expand...
Click to collapse
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).

gwbard said:
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
Click to expand...
Click to collapse
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.

Aou said:
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
Click to expand...
Click to collapse
Yea I posted that last one before I saw his instructions. They were right on point. Thanks guys!

jack_slapped said:
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Click to expand...
Click to collapse
When you click "start" and type "cmd", you're starting a shell. They're command interpreters that extend functionality in specific ways. like "dir" for the Windows/DOS command shell, and "su" or "mount" for adb. Lots of good writeups on that around too

[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

[HOWTO] Alternate Unbricking Method

This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk

r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.

GSLEON3 said:
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.
Click to expand...
Click to collapse
Thanks. I thought about adding a wipe system command, but if the download was corrupted, they'd be screwed. So I left it out.
Sent from my Nexus 7 using Tapatalk

I went ahead and added another command to the OP that may/may not help. It couldn't possibly cause any harm, though. Has anyone actually tried and confirmed this to be working?
Sent from my iPod touch using Tapatalk

When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied

dcoig1 said:
When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied
Click to expand...
Click to collapse
Are you sure you have root?

r3pwn said:
Are you sure you have root?
Click to expand...
Click to collapse
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"

dcoig1 said:
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"
Click to expand...
Click to collapse
Hmmmm. Try pushing it to /sdcard and change the path in your echo command to reflect that.

I am guessing that somehow the /cache/kindleupdate.bin is in a secure area that we cannot push to. Is there any area that we can push to? It seems we may have to push somewhere else and then move into the secured area using adb shell with su permission like here:
http://forum.xda-developers.com/showthread.php?t=1687590&page=5
but we don't have an sdcard with our devices.
---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------
we actually do have an sdcard directory though... i will try to push there
---------- Post added at 10:54 PM ---------- Previous post was at 10:35 PM ----------
so i pushed the update file to the /sdcard/ directory then moved the file to the /cache/ directory, then renamed to kindleupdate.bin . Still does not help the system recovery issue. When I enter 'adb reboot recovery' it brings up a screen which says:
"Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------
---------- Post added at 11:48 PM ---------- Previous post was at 10:54 PM ----------
If it makes any difference I am not bricked at the grey kindle logo but the white and orange. It just keeps refreshing the animation over and over... nothing seems to ever happen. What should I normally see when I boot to recovery? An extra option to update or something?

No. What I meant was try pushing it to /sdcard then changing the echo command to reflect that.

so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery

dcoig1 said:
so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery
Click to expand...
Click to collapse
Yes. Try that.
EDIT: Wait. It'll probably say permission denied or some other lame error, so add
mount -o rw,remount /data
After the cache remount then change everything that references "/sdcard/" to "/data/media/0/".

That didn't work either. I keep getting the same result. I don't get errors using the sdcard directory though either, but I also tried with data/media/0. No errors, just doesn't work for me.

so do i.
adb push "bin" to sdcard can work,but after reboot recovery,
only show on screen like this：
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------

Do not reset to factory defaults

I wanted to mention fastboot works. Read more...

I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin

Faznx92 said:
I wanted to mention fastboot works. Read more...
Click to expand...
Click to collapse
Not really. Not nearly as useful as the KFHD's. No useful commands work.
ChittyChittyGangBang said:
I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin
Click to expand...
Click to collapse
And did this help you unbrick your device?

Unbrick my Kindle
Sorry to interrupt, but my kindle fire HDX 7" is also bricked, I can not get past the gray "Kindle Fire" screen, I can get into fastboot. My device is not detected in ADB. Is there any hope for my kindle or is it dead?

r3pwn said:
Not really. Not nearly as useful as the KFHD's. No useful commands work.
And did this help you unbrick your device?
Click to expand...
Click to collapse
Nope. Ended up wasting half a weekend on it.
I just sent it back and bought a Samsung Galaxy Tab. Now I have GPS and IR in addition to a device that works like a Droid device should.