Original source: http://www.androidpolice.com/2013/01/21/exclusive-how-to-root-ntt-docomos-lg-optimus-g/
Credits:
adb backdoor: giantpune
Duct tape guru: jcase
bootloader: Team Codefire http://forum.xda-developers.com/showthread.php?t=2001655
Testers: Shados and germes81m
Donations:
For giantpune : Paypal to [email protected]
For jcase : http://forum.xda-developers.com/donatetome.php?u=2376614
Download: http://d-h.st/d6p
Files: (Verify the MD5s before proceeding)
MD5 (boot.img) = 175c1bdaabbbbcbd7a4b69a315057e5b
MD5 (hotplug) = 9fbef20822281a2dd546b3e43d8c30dd
MD5 (lk.img) = bc54a6a730658550713a0779b30bf6b7
MD5 (unlock.sh) = 3871c2dde3d6b1d99d27ffa4021c81d3
Fastboot Drivers (needed for windows):
http://forum.xda-developers.com/showthread.php?t=1996051
Notice:
This is an at your own risk kind of thing, if your phone becomes damaged or data lost, your
fault not mine. This does install a unsecured (ro.secure=0) boot image in the process, this
does potentially open your device to security risks (as do most customized firmwares.)
Story:
The Docomo Optimus G ships with a mandatory access control system, that prevents
remounting system, reading boot, executing some things as root, etc general pain in the butt.
We are using a backdoor found by giantpune (and later by Juggie). The backdoor is partially
broken on this device due to the MAC, so it does not yield a root shell for us. However we
can still use it with a couple extra steps to unlock the bootloader\s. We are also going to
install a modified boot img, that removes some of the phone's security features, and allows
us to actually have root access.
Notes:
Graphic glitches will occur while in the bootloader, you will have to use the bootloader 'blind'
Follow directions exactly.
Directions:
Code:
adb push lk.img /data/local/tmp/lk.img
adb push unlock.sh /data/local/tmp/unlock.sh
adb shell chmod 755 /data/local/tmp/unlock.sh
adb shell touch /sdcard/g_security
Disable USB Debugging, then enable usb debugging
Code:
adb shell id
Should recieve an error about not executing /system/bin/sh, this is what we want. If you
don't have the error, start over.
Code:
adb push hotplug /proc/sys/kernel/hotplug
Now toggle bluetooth once, and wait for your phone to display a garbaled screen (the bootloader).
If it displays a blank screen instead of a garbled screen, pull battery, reboot and run 'adb reboot bootloader'
Code:
fastboot devices
If you see your device listed, continue. If not then find the proper drivers, and then
continue.
Code:
fastboot flash boot boot.img
fastboot reboot
adb shell /sbin/rootme.sh
If your phone does not reconnect to your mobile network, try rebooting it serveral times.
If it does not still, then reflash stock firmware.
We are using supersu, and the app https://play.google.com/store/apps/details?id=eu.chainfire.supersu
is needed.
could you please make a tool to root 4.1.2?thanks!until now i can't find a way to root it.
wangzhiqiang said:
could you please make a tool to root 4.1.2?thanks!until now i can't find a way to root it.
Click to expand...
Click to collapse
Wrong place to ask
jcase said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ran out of time, and without the device it is a PITA. I believe something in the kernel is protecting system, possible SEAndroid or something with similar protections.
Will be going back at this later this week, any ideas?
Click to expand...
Click to collapse
I don't have a Optimus G or a varient therof. I'm just helping a guy extracting the *.tot file and I came accross this.
and looking at the ls output
-rwsr-s-r-x root root su
Click to expand...
Click to collapse
Its wrong. Setuid bit is not set for other and it won't allow for increasing permissions when run.
xonar_ said:
I don't have a Optimus G or a varient therof. I'm just helping a guy extracting the *.tot file and I came accross this.
and looking at the ls output
Its wrong. Setuid bit is not set for other and it won't allow for increasing permissions when run.
Click to expand...
Click to collapse
There are too many seperate partitions in tot file, any idea to combine ?
khengvantha said:
There are too many seperate partitions in tot file, any idea to combine ?
Click to expand...
Click to collapse
Yes. I'll be able to work on it more on Sunday. I'm going to be busy till then. (Or maybe I can sneak in an hour somewhere before then)
And it's a bit OT here. Not much to do with rooting Docomo Optimus G .
Re: [Root] Docomo Optimus G
Good catch, will fix and try again when I get a chance. This still doesn't fix sh refusing to run as root.
The ccs-init is preventing it, and remounting.
xonar_ said:
I don't have a Optimus G or a varient therof. I'm just helping a guy extracting the *.tot file and I came accross this.
and looking at the ls output
Its wrong. Setuid bit is not set for other and it won't allow for increasing permissions when run.
Click to expand...
Click to collapse
Yes this wasn't the issue.
xonar_ said:
I don't have a Optimus G or a varient therof. I'm just helping a guy extracting the *.tot file and I came accross this.
and looking at the ls output
Its wrong. Setuid bit is not set for other and it won't allow for increasing permissions when run.
Click to expand...
Click to collapse
jcase said:
Yes this wasn't the issue.
Click to expand...
Click to collapse
What does logcat say?
Try creating a minimalistic binary
Code:
#include <sys/types.h>
#include <unistd.h>
#include <stdio.h>
#include <errno.h>
#include <string.h>
int main()
{
if(setuid(0)==-1)
{
printf("Failed Setting Root UID : %s",strerror(errno));
}
else
{
printf("Success!\nCurrent UID : %d",getuid());
}
return 0;
}
It failed, Docomo used a MAC (ccs-init/ccs-audit). We got the bootloader unlocked yesterday, so we can removed the access control. I'll post details in the morning.
xonar_ said:
What does logcat say?
Try creating a minimalistic binary
Code:
#include <sys/types.h>
#include <unistd.h>
#include <stdio.h>
#include <errno.h>
#include <string.h>
int main()
{
if(setuid(0)==-1)
{
printf("Failed Setting Root UID : %s",strerror(errno));
}
else
{
printf("Success!\nCurrent UID : %d",getuid());
}
return 0;
}
Click to expand...
Click to collapse
DOCOMO LG OPTIMUS G user here..how can I help sir Jcase?
EDITTEDT: you know how to flash stock firmware if there would be any issues?
chacho_2me said:
DOCOMO LG OPTIMUS G user here..how can I help sir Jcase?
EDITTEDT: you know how to flash stock firmware if there would be any issues?
Click to expand...
Click to collapse
use the lg flash tool and .tot file.uploading complete,you may download now and make a mirror if possible.I'll post a guide on our group later.
still cannot find the kdz file of this device...
---------- Post added at 09:01 AM ---------- Previous post was at 08:41 AM ----------
jcase said:
Original source: http://www.androidpolice.com/2013/01/21/exclusive-how-to-root-ntt-docomos-lg-optimus-g/
Credits:
adb backdoor: giantpune
Duct tape guru: jcase
bootloader: Team Codefire http://forum.xda-developers.com/showthread.php?t=2001655
Testers: Shados and germes81m
Files: (Verify the MD5s before proceeding)
MD5 (boot.img) = 175c1bdaabbbbcbd7a4b69a315057e5b
MD5 (hotplug) = 9fbef20822281a2dd546b3e43d8c30dd
MD5 (lk.img) = bc54a6a730658550713a0779b30bf6b7
MD5 (unlock.sh) = 3871c2dde3d6b1d99d27ffa4021c81d3
Click to expand...
Click to collapse
it's an amazing job indeed. we're really grateful for what you've done on rooting the L-01E.:good::good::good:
do i have the permission to reprint this thread on other bbs in my country? I'll indicate the source of course.
THX again for rooting L-01E:fingers-crossed:
best regards.
Misudoll said:
use the lg flash tool and .tot file.uploading complete,you may download now and make a mirror if possible.I'll post a guide on our group later.
still cannot find the kdz file of this device...
---------- Post added at 09:01 AM ---------- Previous post was at 08:41 AM ----------
it's an amazing job indeed. we're really grateful for what you've done on rooting the L-01E.:good::good::good:
do i have the permission to reprint this thread on other bbs in my country? I'll indicate the source of course.
THX again for rooting L-01E:fingers-crossed:
best regards.
Click to expand...
Click to collapse
Repost as you wish, would be nice to have the README stay intact, as well as linking to the source.
ammmm... i dont know why i cant install the the fastboot drivers... i only installed the lg united drivers...and some drivers via windows update.... need help.. already tried uninstall the driver and restarted the PC..but everytime i rebooted back.. drivers is again there.eventhough i disconnected my internet... yeah i know im dumb...sorry
chacho_2me said:
ammmm... i dont know why i cant install the the fastboot drivers... i only installed the lg united drivers...and some drivers via windows update.... need help.. already tried uninstall the driver and restarted the PC..but everytime i rebooted back.. drivers is again there.eventhough i disconnected my internet... yeah i know im dumb...sorry
Click to expand...
Click to collapse
Not sure, not familiar enough with windows to give advice.
so better this be done on linux? in linux no need for fastboot drivers hmmm...so just need to set up sdk / adb on a linux machine?
chacho_2me said:
so better this be done on linux? in linux no need for fastboot drivers hmmm...so just need to set up sdk / adb on a linux machine?
Click to expand...
Click to collapse
It is OS independent, as long as fastboot and adb work.
jcase said:
It is OS independent, as long as fastboot and adb work.
Click to expand...
Click to collapse
so i shall open usb debugging at first and connect with the computer.and then follow the instructions to root the device?
and this step==> Now toggle bluetooth once
means i shall turn on and turn off the bluetooth,or just open it one time?
thx
It would be nice if we can have a video instruction.
i will try to root tonight, and may be made a video if i can root.
Thank you Jcase for the wonderful job.
finally 10 post......:cyclops:
I have a dev LG F160S...It like F180...This is the first LG phone with 2G RAM
and This is the first LG phone with 4.1 jb ....This is a great phone。。。but LG lock the BL...Can you help me to unlock the bl?
I can provide the .tot
offical aboot,recovery,boot here
btw,You can experiment with my phone:fingers-crossed:
Related
For D802 Only
I have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 Support firmware 30a/30d.
It can be use in other firmware version of D802
Download Link:
LGG2-D802-OneClickRootRecoveryV1.1.zip
http://bit.ly/1Ij1soU
If you like my work, want to support development and have few coins spare .You can Press button DONATE TO ME
How to install
Backup Data on SDCARD Before doing everything
AFTER SCRIPT FINISHED IT WILL BE REBOOT TO RECOVERY AUTOMATICLY
1. Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
2. Plug G2 into computer
3. Run OneClick_ROOT_RECOVERY.bat
4. Enjoy ROOT+TWRP on Lollipop Firmware
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>ports.bat
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
Click to expand...
Click to collapse
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
ขอบคุณครับ
For. any question that want to ask me in private Please Leave a question in facebook group
https://www.facebook.com/groups/1420724551528661/
......... DON'T INBOX TO ME .........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original Script
[Guide] Root LG firmwares (KitKat / Lollipop) - One click script by @avicohh
Ok
Tested on 32g Spain Vodafone 30d Rom and works like a charm, thanks
Led Zeppelin said:
Tested on 32g Spain Vodafone 30d Rom and works like a charm, thanks
Click to expand...
Click to collapse
I will be update my script for One Click ROO+TWRP.
That would be awesome
would be awesome!!
somboons said:
I will be update my script for One Click ROO+TWRP.
Click to expand...
Click to collapse
waiting just for that.. thanks :fingers-crossed::highfive::victory:
OMERZEN said:
waiting just for that.. thanks :fingers-crossed::highfive::victory:
Click to expand...
Click to collapse
Link online.
Feedback to me.
What khappens now to ur flashable rooted v30a and v30d
legola said:
What khappens now to ur flashable rooted v30a and v30d
Click to expand...
Click to collapse
Bump stock kernel is different .I want to people use compatible kernel.
somboons said:
Feedback to me.
Click to expand...
Click to collapse
This downgrade laf and aboot to v20?
4Freedom said:
This downgrade laf and aboot to v20?
Click to expand...
Click to collapse
this is a concept.
Great job man! Root & Recovery on Lollipop with LG G2 D802 is easy to do now!
somboons said:
this is a concept.
Click to expand...
Click to collapse
Okay, so now we have kitkat bootloader and kitkat "downlaod mode" on lollipop.
Between, about recovery, MUST we use only bumped version?
And every rom is compatible now?
4Freedom said:
Okay, so now we have kitkat bootloader and kitkat "downlaod mode" on lollipop.
Between, about recovery, MUST we use only bumped version?
And every rom is compatible now?
Click to expand...
Click to collapse
I answered you on all this points: http://forum.xda-developers.com/showpost.php?p=59882657&postcount=2
again: kk bootloader=> only bumped recovery/kernel
only rom with bumped kernel work on KK bootloader
6ril1 said:
only rom with bumped kernel work on KK bootloader
Click to expand...
Click to collapse
How can i understand if a rom has a bumped kernel?
Like official cm12?
And thanks for everything
i have a problem it say Couldn't open the port \\:\ COM3 after the phone enter in download mode
remio33 said:
i have a problem it say Couldn't open the port \\:\ COM3 after the phone enter in download mode
Click to expand...
Click to collapse
Screen shot please
I'm stuck at :
special command : ENTER , LEAVE
#
I did the root script once ,but wanted recovery ... maybe the other root script from avicohh is interfering ?
How to uninstall the supersu completely ,because it worked with the avicohh script, but i wanted recovery too so trying to install your script now ?
Kuoi said:
I'm stuck at :
special command : ENTER , LEAVE
#
I did the root script once ,but wanted recovery ... maybe the other root script from avicohh is interfering ?
How to uninstall the supersu completely ,because it worked with the avicohh script, but i wanted recovery too so trying to install your script now ?
Click to expand...
Click to collapse
Can you copy of log that show on command dos to me?
This script working very well for me.
somboons said:
Can you copy of log that show on command dos to me?
This script working very well for me.
Click to expand...
Click to collapse
Trying the avihocc script now ,but as expected ... same , stuck on #
I think the first install of supersu with avihocc script interfered with yours , so now i think i have to do the installation of the rom again to test if it was
Hello,
A few days ago I wrote a new implementation inspired by the work of CyboLabs and Codefire that in harmony contributed for the creation of Open_Bump. Basically I rewrote Open_Bump using POSIX C to run directly on LG G2 or any compatible device with Open_Bump. So now you can bump any kernel or recovery using the target device, validate images to know if they have been bumped and other things.
The source code and binaries for Linux and Android found at: https://github.com/ferreirawax/cbump
FAQ
What is POSIX?
POSIX is an API for Unix-like systems (Linux, Android, etc).
But what are the benefits of this?
Considering the benefits already mentioned above. Other example, if you are a developer, you will probably will get rid of Python or even get rid of everything and create a script to bump the Kernel/Recovery on the flash time.
And why the original developers did not do it?
I do not know.
I do not know how to use it.
See the readme in the link above.
Click to expand...
Click to collapse
Cheers!
It will be useful for developers, thanks for the effort
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
wulsic said:
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
Click to expand...
Click to collapse
Hello,
I know that Python works well, but Cbump was thought to be portable. I did not even know about MultiROM, I checked now and discover that he used the unrepresentative signature in many standard unicodes which is not an elegant method. About -f, yes. I had not thought about Loki up because I have no reason to use Loki instead of Bump (Without disregarding the Dan's splendid work), Maybe I can add support for Loki verification later. About streams take look here, I'll add more information/instructions in thread soon.
Thanks.
@ferreirawax
Very cool work. Can't wait to expand on this and find more use cases!
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Sj12345 said:
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You're in the WROOOOOONG thread, buddy...
jeebspawnshop said:
You're in the WROOOOOONG thread, buddy...
Click to expand...
Click to collapse
haha,no I dont buddy, LG exploits can be used for all LG devices (we have root on g2,g3,g4,gflex,gflex2 with the SAME EXPLOIT) He understands how the exploit "bump" works... so I need help from HIM to try this in my devices
....... thanks
From Readme.txt
"The flash function uses MSM identifier to detect partition block, Tested only on LG G2, Probably works too with LG G3 and others LG devices powered by Qualcomm."
Sorry its me again
I have a lot of question???? can you help me? @ferreirawax
I have two partitions on my phone (aboot and boot), which should be used???
I will dump the correct partition with
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/boot.img
then use your tool like
Code:
cbump /data/media/0/boot.img /data/media/0/cboot.img
flash partition with
Code:
dd if=/data/media/0/cboot.img of=/dev/block/bootdevice/by-name/boot
and try to booting up....so if this boot up means it works?
and my next step will be make a TWRP recovery???? I will be carefull cause My phone doesnt have kdz or tot for go back to stock... I only have my own backup from dd
@Sj12345 this is a rewritten version of open_bump so if bump didnt worked on your device this won't work either. Lollipop isn't working with bump only jellybean and kitkat as far as I know. Also I suggest before doing these things to learn what the partitions etc are before you will hardbrick yourself. Aboot is the bootloader. Boot is the boot.img so that's the kernel.
It probably will result into an security error.
Sent from my LG-D802 using Tapatalk
One word: COOL
This is awesome, thank you so much. Now we can use .zip to bump and flash, just like loki method. Will make testing things SO much easier. Won't have to re-bump the image every time
You the man!
Now if u can get one for the G4 n get the $10,000 bounty!
Sent from my LG-H811 using Tapatalk
5 Star For You [Excellent]
Testing Cbump to our devices
Awesome Tools! :good:
It should help multirom?
Inviato dal mio LG-D802 utilizzando Tapatalk
Edited
Sorry for the bump (ehehe), but does anyone have a mirror of this? Nvm, solved!
https://github.com/dorimanx/cbump
Ok, I found how to update my H440AR to that polish MM. First of all, "AR" in H440AR stands for Lg spirits that were assembled in Argentina but it seems there's no difference in hardware terms to H440N and H440F just a ROM issue, I do remember from the time I had a motorola defy as main phone when the hardware model changed over some rom upgrades so I tried the same.
This MAY work for H440 variants but I'M NOT RESPONSIBLE IF YOU BREAK YOUR DEVICE, this worked for me and I'm sharing what I found, these are the steps to get MM working please read everything carefully.
Brazilian H442F "Lg Volt 4g" confirmed to work with this[/COLOR]
Software Necessary:
LG Drivers: Here
Visual C++ Runtime Library (just in case): Here
LG Flash Tool 2014: Here
LG UP: Here ( First install LGUP_8994_DLL_Ver_0_0_3_23, then LGUP_Install_Ver_1_14_3.)
Script that makes LG UP recognize our device as H440n: Here or Here (MEGA)(Download as zip)
Roms: (yeah, two of them)
H440N LP: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW42DZL232VIAMQ4B7EF261/H440n10i_00_1124.kdz
H440N MM: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW4CUT3552TLAY871EAEID2/H440n20a_00_0428.kdz
Procedure:
1° Get into download mode, with phone turned off keep pressed volume up and plug your usb, keep in mind you need all the drivers already installed.
2° Once there open Lg Flash Tool 2014, don't change anything and press to select the KDZ and click on "CSE Flash", in the next window press start again. Once in the language selection window first choose "Clear phone Software update registry", a window will pop up, close it and choose "different country" and language "english" and let it finish the work if a the message "Connection to server failed, try again in a moment" pops up, just ignore it, you can see the progress behind that window and let it finish, in my case it took almost 8 minutes after froze for a while at 99%.
3° Once that is done your phone will report that its hardware version is H440N and you can proceed as Fobos531 explained on his thread. http://forum.xda-developers.com/android/development/guide-how-to-install-marshmallow-kdz-lg-t3385476
LG Flash tool screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
don't forget to press "Clear phone Software update registry"
For Spanish and languages not included in the original MM rom from poland, ElDainosor posted a solution here: http://forum.xda-developers.com/and...t-h440ar-to-h440n-maybe-t3387044#post67074988
For Brazilian H442F "LG Volt 4G" users, @Ninloth confirmed you can install the radio apk @walterfuster provided here
All credits to:
@Fobos531 for his guide on how to upgrade H440N.
@bender_007 for his script for LGUP.
@quangnhut123 for his guide on how to use LG Flash Tool and the utility itself, you can donate him a beer via paypal: [email protected]
@BrainNotFound @osvaldorluna @ElDainosor @walterfuster
And h420?
Enviado do meu LG-H420 através de Tapatalk
jtsisidoro said:
And h420?
Enviado do meu LG-H420 através de Tapatalk
Click to expand...
Click to collapse
H420 has truly different hardware so this wont work as far as I know.
Oki
Enviado do meu LG-H420 através de Tapatalk
Yup, i did it this way two days ago, and works perfect! Thanks for tagging me btw
BrainNotFound said:
Yup, i did it this way two days ago, and works perfect! Thanks for tagging me btw
Click to expand...
Click to collapse
I tagged those who asked about h440ar, but I wasn't sure if you meant the mm kdz or the LP ones when you said it worked haha
[email protected]
فرستاده شده از SM-J500Hِ من با Tapatalk
Works perfectly on a H440AR!
Thanks for tagging me and for sharing this way.
PS: to all those who wants their phone in spanish/other languages unavailable they have to do this:
1. Install MoreLocale 2 from Play Store.
2. Enable Debugging USB
3. Insert those commands on ADB (PC)
adb shell
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
(if this is done right, the command prompt will show:
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION < )
4. Choose their desired language on MoreLocale2 app.
5. Enjoy your Marshmallow ROM in your language
ElDainosor said:
Works perfectly on a H440AR!
Thanks for tagging me and for sharing this way.
PS: to all those who wants their phone in spanish/other languages unavailable they have to do this:
1. Install MoreLocale 2.
2. Enable Debugging USB
3. Insert those commands on ADB (PC)
adb shell
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
(if this is done right, the command prompt will show: android.permission.CHANGE_CONFIGURATION < )
4. Choose their desired language on MoreLocale2 app.
5. Enjoy your Marshmallow ROM in your language
Click to expand...
Click to collapse
amazing, thank you!
Error KDZ file is invalid, any solution for this error?
VinicimJF said:
Error KDZ file is invalid, any solution for this error?
Click to expand...
Click to collapse
Phone model and which part of the procedure? Converting h440ar to h440n or h440n LP to MM?
Korelev said:
Phone model and which part of the procedure? Converting h440ar to h440n or h440n LP to MM?
Click to expand...
Click to collapse
Phone model is H422F but in the case is printed H440F, LG UP recognize with H44210d, i edited the .reg file and make it identificable with H44n in LGUP, but with error in KDZ file. i'm trying to port from LP to MM.
VinicimJF said:
Phone model is H422F but in the case is printed H440F, LG UP recognize with H44210d, i edited the .reg file and make it identificable with H44n in LGUP, but with error in KDZ file. i'm trying to port from LP to MM.
Click to expand...
Click to collapse
But you were able to upgrade your phone to h440n using lg flash tool? That will make your phone report as h440n thus any problem with LGUP will be solved.
VinicimJF said:
Phone model is H422F but in the case is printed H440F, LG UP recognize with H44210d, i edited the .reg file and make it identificable with H44n in LGUP, but with error in KDZ file. i'm trying to port from LP to MM.
Click to expand...
Click to collapse
VinicimJF, you say that your phone is a H422f. The 422f model uses a Mediatek CPU (at least in Brazil). 44x models uses a Qualcomm CPU.
The firmwares won't be compatible. Probably that is the reason that you got a invalid KDZ message.
Check your device's CPU, you are risking bricking your phone.
jorlando said:
VinicimJF, you say that your phone is a H422f. The 422f model uses a Mediatek CPU (at least in Brazil). 44x models uses a Qualcomm CPU.
The firmwares won't be compatible. Probably that is the reason that you got a invalid KDZ message.
Check your device's CPU, you are risking bricking your phone.
Click to expand...
Click to collapse
thanks by advice, but here in brazil exist 2 variants, my device use's qualcomm snapdragon 400. anyway, thank you.
---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------
Korelev said:
But you were able to upgrade your phone to h440n using lg flash tool? That will make your phone report as h440n thus any problem with LGUP will be solved.
Click to expand...
Click to collapse
No, using flash tool, upgrade fail just in the begin.
I tryed other way, downloaded a LP FW v10i (HUN/HUNGARY) and flash using Lg flash tool, the process was fully complete with no errors, so then, without any modifications on windows reg i connected my device on usb and voila its recognized as H440N on LGUP, then i'm just put the same KDZ file that i was having error and it worked perfectly.
Software and Hardware Info Screen
VinicimJF said:
thanks by advice, but here in brazil exist 2 variants, my device use's qualcomm snapdragon 400. anyway, thank you.
---------- Post added at 12:51 PM ---------- Previous post was at 12:29 PM ----------
No, using flash tool, upgrade fail just in the begin.
I tryed other way, downloaded a LP FW v10i (HUN/HUNGARY) and flash using Lg flash tool, the process was fully complete with no errors, so then, without any modifications on windows reg i connected my device on usb and voila its recognized as H440N on LGUP, then i'm just put the same KDZ file that i was having error and it worked perfectly.
Software and Hardware Info Screen
Click to expand...
Click to collapse
Nice
Now i'm waiting for the root process. xD
It's there a way to go back to lollipop H440AR after flashing?
cabalarsen87 said:
It's there a way to go back to lollipop H440AR after flashing?
Click to expand...
Click to collapse
To h440n sure, and from there probably you can use lg flashing tool to return your phone to an h440ar rom.
Asteroid OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction and Warning:
YouTube Video: https://www.youtube.com/watch?v=b_GJiQYTAIk
Rom Alpha 7/24/2017
Downloads:
Official prebuilt Asteroid OS image : https://release.asteroidos.org/nightlies/sturgeon/
Instructions:
1. Make sure you have an ADB installation (Minimal adb and fastboot should do) and your watches' bootloader is unlocked and debugging is enabled from the settings.
2. Download the two files in the download section and place them in the same folder and connect the watch to the computer
3. Open up the shell or command prompt (cmd) and navigate to that folder
4. Issue these commands:
Code:
adb push asteroid-image-sturgeon.ext4 /sdcard/linux/rootfs.ext4
adb reboot bootloader
fastboot boot zImage-dtb-sturgeon.fastboot
5. The watch will reboot into Asteroid OS. Every time you want to boot into asteroid you have to issue the last two commands or else you will boot into android wear normally.
6. The Bluetooth synchronization app for Android is named AsteroidOSSync.apk. Be careful that dory is the only port with Bluetooth capabilities and this app will be of no use with other watches yet.
Download : AsteroidOSSync.apk
Removal Instructions:
Just open up shell or command prompt (cmd), connect the watch to the computer and issue this command:
Code:
adb shell rm /sdcard/linux/rootfs.ext4
Credits:
kido - Creator of the OS
Bencord0 - sturgeon port
Everyone on the #asteroid IRC
Links:
Webpage: asteroidos.org
Twitter: @asteroidOS
IRC: #asteroid
Can this interact with android at all? Like texts/notifications, etc?
phishfi said:
Can this interact with android at all? Like texts/notifications, etc?
Click to expand...
Click to collapse
The Bluetooth synchronization app for Android is named AsteroidOSSync for Android only
AsteroidOSSync.apk
CadBuRy.VN said:
The Bluetooth synchronization app for Android is named AsteroidOSSync for Android only
AsteroidOSSync.apk
Click to expand...
Click to collapse
Nice. I checked the website, too, but it doesn't have an actual answer. What can asteroid do? I see the apps that are available, but does the calendar get events from my gCalendar? Does it sync messages and contacts? I'll probably try this out tomorrow if I have time anyways, I just want to know if it's worth jumping into or if it's a heavily hamstrung OS for folks who are used to AW.
what does it look like in a rounded face?
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
phishfi said:
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
Click to expand...
Click to collapse
i got the same problem here.
phishfi said:
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
Click to expand...
Click to collapse
same here
phishfi said:
Just tried twice, even shelled into the watch to confirm that the zImage was saved to /sdcard/linux/ as "rootfs.ext4" and it still won't boot to this OS. I send the fastboot command, the watch vibrates, waits, vibrates again, then boots to Android Wear 2.0.
Click to expand...
Click to collapse
flo071 said:
i got the same problem here.
Click to expand...
Click to collapse
CVLover said:
same here
Click to expand...
Click to collapse
Dont want to sound rude (I really just wanna help)
Are you sure you downloaded both files? 509MB ext4 and 9MB fastboot?
Are both files in the same directory where you run your adb/fastboot commands?
Maybe we also need some permissions. I'm gonna check it later...
Also I will create a script (either shell or tasker script [maybe even an apk]) to easily boot into astroid os.
Both would be possible: on phone or on watch...
BIade said:
Dont want to sound rude (I really just wanna help)
Are you sure you downloaded both files? 509MB ext4 and 9MB fastboot?
Are both files in the same directory where you run your adb/fastboot commands?
Maybe we also need some permissions. I'm gonna check it later...
Also I will create a script (either shell or tasker script [maybe even an apk]) to easily boot into astroid os.
Both would be possible: on phone or on watch...
Click to expand...
Click to collapse
thank you.
and yes i did all the things.
is it possible that asteroid os needs an older version of the bootloader? maybe one from the older android wears.
btw an app for booting into asteroid os would be really nice.
flo071 said:
thank you.
and yes i did all the things.
is it possible that asteroid os needs an older version of the bootloader? maybe one from the older android wears.
btw an app for booting into asteroid os would be really nice.
Click to expand...
Click to collapse
that is a really good point. I guess you were also on aw2.0-official-rooted (not dev-pre-custom-rom)
EDIT:
PREFERRED_PROVIDER_virtual/android-headers = "android"
PREFERRED_PROVIDER_virtual/android-system-image = "android"
PREFERRED_VERSION_android = "marshmallow"
PREFERRED_PROVIDER_virtual/kernel = "linux-sturgeon"
PREFERRED_VERSION_linux = "3.10+marshmallow"
Click to expand...
Click to collapse
hmmmm.....
BIade said:
that is a really good point. I guess you were also on aw2.0-official-rooted (not dev-pre-custom-rom)
Edit incoming.. (just testing)
Click to expand...
Click to collapse
i am on last dev preview unrooted
I'm on the 2.0 build, unrooted, stock everything.
I definitely followed the instructions to the letter.
Just tried with AW1.5 , same problem... (yes I flashed it, because im crazy)
Same problem. Still boot into AW2.0. Official AW2.0 + rooted. Bootloader version is 4.3
wzhy said:
Same problem. Still boot into AW2.0. Official AW2.0 + rooted. Bootloader version is 4.3
Click to expand...
Click to collapse
Anyone here with an older bootloader than 4.3? I think we already tried all combinations of ROMs, not its time or the bootloader i think...
BIade said:
Anyone here with an older bootloader than 4.3? I think we already tried all combinations of ROMs, not its time or the bootloader i think...
Click to expand...
Click to collapse
Go here can get older version factory image with older version bootloader
https://developer.android.com/wear/preview/downloads.html
BTW, which bootloader version does this os develop on?
---------- Post added at 22:32 ---------- Previous post was at 22:01 ----------
I found why still boot into android wear!!
The asteroid os system image's path has been change!
Move it to /sdcard/asteroidos.ext4 then go into bootloader and boot zImage.
BIade said:
Anyone here with an older bootloader than 4.3? I think we already tried all combinations of ROMs, not its time or the bootloader i think...
Click to expand...
Click to collapse
i tried with 4.2 same problem as before...
flo071 said:
i tried with 4.2 same problem as before...
Click to expand...
Click to collapse
Just rootfs path has been change! !
New path is "/sdcard/asteroidos.ext4"
wzhy said:
Just rootfs path has been change! !
New path is "/sdcard/asteroidos.ext4"
Click to expand...
Click to collapse
it gives me the logo but doesnt boot. just stays there for a long time. may try again
Dear XDA-Dev-Community,
i have here a china-import with a supposed Android 10.
I would like to install a linaege or other ROM, but which one should I use?
Can you help me?
Basic knowledge for installing and testing is available...
In the appendix you can find some pictures for evaluation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nobody can help?
Maybe I can build my own Custom Rom for this device?
What i hove to do? Save the Drivers?!?!
Anybody know a good guide for me?
Probably a faked one... what build.prop entry ro.board.platform says?
And/or ro.mediatek.platform?
next message
CXZa said:
Probably a faked one... what build.prop entry ro.board.platform says?
And/or ro.mediatek.platform?
Click to expand...
Click to collapse
adb devices -l gives this:
Code:
device usb:1-2 product:P40 Pro+ model:U2 device:Smartphone transport_id:1
Code:
[ro.board.platform]: [mt6580]
[ro.mediatek.platform]: [MT6580]
complete getprop:
https://pastebin.com/h66R0mNk
So, MT6580 and probably a Lollipop. Could be worse.
There is some jlinksz (maker of these) threads here.
Also at 4pda, where there is more info and stuff.
Jlinksz K960 - Обсуждение - 4PDA
Jlinksz K960 - Обсуждение, Планшет, 9.6"
4pda.ru
I would not do much to it if it works well enough as it is. But if you do take a backup first as finding correct one later can be really really hard...
CXZa said:
So, MT6580 and probably a Lollipop. Could be worse.
Click to expand...
Click to collapse
Why worse? What problems you see?
CXZa said:
I would not do much to it if it works well enough as it is.
Click to expand...
Click to collapse
This is not an option. Its so creepy and full of preinstalled apps i can´t trust, u know?
So can i build a custom rom by extract the drivers and AOSP? Is this possible with beginner skills on coding?
0
Seppppx said:
I might be able to help. The kernel source is missing, but there are some device trees for other mt6580 phones. I will try to craft a device tree for this phone.
Click to expand...
Click to collapse
Thanks a lot! I will deliver how fast i can. But this took a long time and i get some troubles:
Seppppx said:
For now i need these things:
1. The android version.
Click to expand...
Click to collapse
Labeld as Android 10, but it's a fake. It looks like Android 6 / Marshmallow
2. raw dd'ed boot image of the device
3. raw dd'ed system image of the device
Click to expand...
Click to collapse
here the trouble beginns...
3. raw dd'ed system image of the device
[/QUOTE]
So i tried to get root by some tools, from this site here:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
But nothing works! by adb sideload or apk-install...
Some advice?
I have the exact same phone, same issues as Ronny has. Have made a backup image of the phone but it's quite large in size ( over 5gb broken into 3 files). Would this be of use in in figuring out how to Root the phone?
B
BruizerBG said:
Have made a backup image of the phone but it's quite large in size ( over 5gb broken into 3 files).
Click to expand...
Click to collapse
Yeah, i´m not alone ;D
Would like to hear how you done this!
And my offer to host your files for downloading on my nextcloud instance.
Could give you an uploadlink (password save) and publish the link here...
Seppppx said:
I might be able to help. The kernel source is missing, but there are some device trees for other mt6580 phones. I will try to craft a device tree for this phone.
For now i need these things:
1. The android version.
2. raw dd'ed boot image of the device
3. raw dd'ed system image of the device
Click to expand...
Click to collapse
Hi Seppppx, I have this phone with Android 5.1 on it. I use Linux so I am assuming I can set the phone up and do the dd's via an adb command?
Any guidance you can give on the correct way to do this would be good and I can try and get the files available for you .
B
ronnyst said:
Yeah, i´m not alone ;D
Would like to hear how you done this!
And my offer to host your files for downloading on my nextcloud instance.
Could give you an uploadlink (password save) and publish the link here...
Click to expand...
Click to collapse
Hi Ronny, you can backup the files on the phone by entering Recovery mode. Switch off the phone. Then, at the same time, hold down the power and volume up buttons down until a small menu appears in the middle of the screen. Choose the recovery option, volume up scrolls through the list, volume down selects which option you want from recovery, fastboot or normal. You'll have a android image pop up, maybe with the message "no command " , just wait or press the same button combination again and the recovery menu should appear . In the list will be the system or user files backup. I see from your images though that you have already figured most of the out.
That only gives us no. 3 of the files that Seppppx needs so I have asked him how to get the bootloader dump.
B
BruizerBG said:
Hi Seppppx, I have this phone with Android 5.1 on it. I use Linux so I am assuming I can set the phone up and do the dd's via an adb command?
Click to expand...
Click to collapse
At first: You need to be root do dd boot and systemimages. After you got it you get try this:
[Guide] Dumping boot.img & recovery.img using dd (for complicated partitions)
Hi there! i am new to forums as well as in developing. i have recently taken interest in making cyanogenmod for my device. So, i have been searching web for hours to dump boot.img and recovery.img for my device. As my device is a mediatek device...
forum.xda-developers.com
But i tried this and i failed because a doesn´t have su (root). So i tried to use adb push but even then i cant access the Boot/system-image folders (cause no root). See my previous posts for...
BruizerBG said:
Hi Ronny, you can backup the files on the phone by entering Recovery mode. Switch off the phone. Then, at the same time, hold down the power and volume up buttons down until a small menu appears in the middle of the screen. Choose the recovery option, volume up scrolls through the list, volume down selects which option you want from recovery, fastboot or normal. You'll have a android image pop up, maybe with the message "no command " , just wait or press the same button combination again and the recovery menu should appear . In the list will be the system or user files backup.
That only gives us no. 3 of the files that Seppppx needs so I have asked him how to get the bootloader dump.
B
Click to expand...
Click to collapse
Just look at my pictures from previous posts... I´d already done this...
BruizerBG said:
That only gives us no. 3 of the files that Seppppx needs so I have asked him how to get the bootloader dump.
B
Click to expand...
Click to collapse
Sorry Bruizer, but this option gives us only a dump of the userdata. this will doesn´t help Seppppx.
Any update on this? I have received a phone to use as back up until I get my own and it's the same type of deal as far as chinese phone goes.
Also, I forgot to mention that I was looking through the adb pull screen shot and even though I do not currently have root I can still cd to /dev/block/platform/mtk-msdc.0/ without viewing contents but when i try to cd by-name there is no directory by that name.... I want to be able to achieve root and also possibly make a custom rom for this device and I'm willing to follow any suggestions anybody has. Clearly the boot.img and such are in a different directory but I'm going to have to do more digging.
whizpopthat said:
Any update on this? I have received a phone to use as back up until I get my own and it's the same type of deal as far as chinese phone goes.
Click to expand...
Click to collapse
sorry no updates. we (BruizerBG and me) aren´t able to dd the boot partition.
I would be happy for any advice or help!!!
ronnyst said:
sorry no updates. we (BruizerBG and me) aren´t able to dd the boot partition.
I would be happy for any advice or help!!!
Click to expand...
Click to collapse
I'm trying to find some time to do some digging about finding the boot partition because as I stated in my last post the by-name dir doesn't exist but obviously we are unable to find out which dirs do exist without root... If I come up with something I will be sure to let you know.