Develop Bugs

[LOKI] Official Loki bootloader bypass support thread

I have successfully ported Loki to the LG Optimus G Pro, LG Lucid 2, LG Motion, and LG Spirit (with more devices likely on the way). Loki is a tool for developers that allows them to prepare custom recovery images and kernels suitable for flashing on these devices, which have locked bootloaders.
If you are an ordinary user with no development experience, I recommend you sit back and wait until your development community produces simplified instructions for you to flash custom ROMs.
Otherwise, the Loki source tree (with pre-compiled binaries) is available here:
https://github.com/djrbliss/loki
This thread is dedicated to giving the LG Optimus G Pro community a single place to consolidate all Loki-related questions and support requests. I do not have time to support this thread myself, so I hope your development community is willing to step up to the plate. In particular, I understand there has been some difficulty in accessing the recovery subsystem - I trust you guys will be able to sort that out in no time.
The only questions I will answer personally are requests to add support for additional device variants or builds. If you are going to make such a request, please provide the build number and a copy of the aboot partition, which is needed by me in order to port Loki.
Enjoy the custom ROMs!
Paypal:
goo.gl/zBGb0

Nicely done, you sir definitely have a knack for this!
I am also happy to see that I was right about the boot header location, too!
If you're interested, and have some time, hit me up in #lg-optimus-g on Freenode and we can talk about other exploits that can be leveraged against the rest of LK or even SBL3 for this phone.

You are a Hero!!!
My bounty pledge is 50. I'll send you 40 as soon as I get home tonight and will give 10+ to thecubed because he still did/does and will work hard for our precious "monster"
Which LGOPro versions are currently supported?
Sent from my LG-F240L using xda app-developers app

st1114g said:
You are a Hero!!!
My bounty pledge is 50. I'll send you 40 as soon as I get home tonight and will give 10+ to thecubed because he still did/does and will work hard for our precious "monster"
Which LGOPro versions are currently supported?
Sent from my LG-F240L using xda app-developers app
Click to expand...
Click to collapse
thanks for being a gentleman and fulfilling your pledge

Hi djrbliss
Please help to support E988 for HK version ... Thanks so much !
ro.product.model=LG-E988
ro.product.brand=lge
ro.product.name=geefhd_open_hk
ro.product.device=geefhd
ro.product.board=GKOPENHK
ro.build.description=geefhd_open_hk-user 4.1.2 JZO54K E98810b.1370153677 release-keys
.vendor = "LGE",
.device = "LG Optimus G Pro",
.build = "E98810b",
https://mega.co.nz/#!IU5TVSRT!E14pyiV0FXEHLFVL1f1y6GCwwnw83zXdDoSM-rbW9VA

shabbypenguin said:
thanks for being a gentleman and fulfilling your pledge
Click to expand...
Click to collapse
I am a girl, I am a girl .... lol :angel:
But either way, if I have a promise to keep I'll never brake it, or just can't go to sleep
Don't mean to throw this off topic but how do I go about donating to djrbliss? I can't seem to find a Donate button :/

st1114g said:
I am a girl, I am a girl .... lol :angel:
But either way, if I have a promise to keep I'll never brake it, or just can't go to sleep
Don't mean to throw this off topic but how do I go about donating to djrbliss? I can't seem to find a Donate button :/
Click to expand...
Click to collapse
my apologies
http://goo.gl/zBGb0 here is his paypal donation link

shabbypenguin said:
my apologies
http://goo.gl/zBGb0 here is his paypal donation link
Click to expand...
Click to collapse
Thanks, Done!!! May the guys enjoy and have more coming!
No need for an apology

Bounty paid. It's not fully unlocked, but we've got custom roms in sight now. I'll donate the same for the cubed when he gets the Loki implementation wrapped up and moboot. I'm also still hoping for an exploit that will let us unlock the bootloader. Gotta love the dev community.

At&t is pushing a software update, although I highly doubt it's for patching the bootloader it may affect something else. Has anyone updated to it or knows if it will affect this exploit.
Edit: I meant to post this in general in another topic sorry anyways found The answer when I went to the general forum. Sorry, next time I won't post from a moving vehicle.

hkfriends said:
Hi djrbliss
Please help to support E988 for HK version ... Thanks so much !
ro.product.model=LG-E988
ro.product.brand=lge
ro.product.name=geefhd_open_hk
ro.product.device=geefhd
ro.product.board=GKOPENHK
ro.build.description=geefhd_open_hk-user 4.1.2 JZO54K E98810b.1370153677 release-keys
.vendor = "LGE",
.device = "LG Optimus G Pro",
.build = "E98810b",
https://mega.co.nz/#!IU5TVSRT!E14pyiV0FXEHLFVL1f1y6GCwwnw83zXdDoSM-rbW9VA
Click to expand...
Click to collapse
Your device is running an identical aboot.img to the AT&T model, so it is now supported. I updated the tool to indicate support.

djrbliss said:
Your device is running an identical aboot.img to the AT&T model, so it is now supported. I updated the tool to indicate support.
Click to expand...
Click to collapse
amazing....thanks so much
is there anyone can give me a clean cwm recovery img, so i can patch it to support E988？

F240K optimus g pro
Hi djrbliss,
i've attached aboot.img for the korean F240k model
will it be the same as the ATT 980 or HK 988 ?
ro.product.model=LG-F240K
ro.product.brand=lge
ro.product.name=geefhd_kt_kr
ro.product.device=geefhd
ro.product.board=GKKT
ro.build.description=geefhd_kt_kr-user 4.1.2 JZO54K F240K10o.1366783154 release-keys
hopefully you be able to check it out and further extend the support for the Korean model.
do let me know if any other files needed to make it possible.
thanks in advance.

Hi djrbliss.
Please help to support F240L model.
ro.product.model=LG-F240L
ro.product.brand=lge
ro.product.name=geefhd4g_lgu_kr
ro.product.device=geefhd4g
ro.product.board=GKU
ro.build.description=geefhd4g_lgu_kr-user 4.1.2 JZO54K F240L10v.1369244097 release-keys
thank you!!

djrbliss said:
Your device is running an identical aboot.img to the AT&T model, so it is now supported. I updated the tool to indicate support.
Click to expand...
Click to collapse
Hi Dan,
I manage to flash ATT recovery (LOKI'ed) by DD only... as the loki_flash has error below
./loki_flash recovery gkatt-cwm-e98010g.lok
[+] loki_flash v1.5
Segmentation fault
139|[email protected]:/data/local/tmp #
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
another issue:
I am using loki_patch v1.5 to patch my custom build kernel
then I flash this Loki'ed kernel to my E988 and it keep re-boot loop
(with the wording => Cause: Device Unlock, so boot success!!....)
[email protected]:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok
[+] loki_patch v1.5
[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b
[+] Output file written to myboot.lok
[email protected]:/usr/android#

hkfriends said:
Hi Dan,
I manage to flash ATT recovery (LOKI'ed) by DD only... as the loki_flash has error below
./loki_flash recovery gkatt-cwm-e98010g.lok
[+] loki_flash v1.5
Segmentation fault
139|[email protected]:/data/local/tmp #
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
another issue:
I am using loki_patch v1.5 to patch my custom build kernel
then I flash this Loki'ed kernel to my E988 and it keep re-boot loop
(with the wording => Cause: Device Unlock, so boot success!!....)
[email protected]:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok
[+] loki_patch v1.5
[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b
[+] Output file written to myboot.lok
[email protected]:/usr/android#
Click to expand...
Click to collapse
I'll fix loki_flash as soon as possible, thanks.
Are you sure it's not an issue with your custom kernel? Could you try taking the stock boot.img, Loki-patching that, flashing it, and seeing if it boots? If that works, then the issue is on your end. Otherwise, I'll try to figure out what's going on.

djrbliss said:
I'll fix loki_flash as soon as possible, thanks.
Are you sure it's not an issue with your custom kernel? Could you try taking the stock boot.img, Loki-patching that, flashing it, and seeing if it boots? If that works, then the issue is on your end. Otherwise, I'll try to figure out what's going on.
Click to expand...
Click to collapse
Yes, It sounds strange... anyway, I will extract the LG source code again and try just compile it and Loki-patching and flash it to see...
the test before is clone the source from thecubed and just compiled successfully without modification
anyway, it is midnight in here, I will do that tormorrow again, thanks for your help

hkfriends said:
Yes, It sounds strange... anyway, I will extract the LG source code again and try just compile it and Loki-patching and flash it to see...
the test before is clone the source from thecubed and just compiled successfully without modification
anyway, it is midnight in here, I will do that tormorrow again, thanks for your help
Click to expand...
Click to collapse
You are patching a full boot.img (with ramdisk), not just a compiled kernel, right?

I posted a little about the segfault in loki_flash here: http://forum.xda-developers.com/showpost.php?p=43481635&postcount=15
it's one of those memcmp operations that's doing it.

madmack said:
I posted a little about the segfault in loki_flash here: http://forum.xda-developers.com/showpost.php?p=43481635&postcount=15
it's one of those memcmp operations that's doing it.
Click to expand...
Click to collapse
Could you post the Loki image that's causing the crash and the aboot and recovery/boot that you used to generate it?

Request for Japanese SHARP DIAG driver!

Hi, I have a SHARP SH-06E and I successfully turned on its DIAG mode.
Now I have some devices not recognized, the HW IDs are below:
USB\VID_04DD&PID_96CD&REV_0228&MI_02
USB\VID_04DD&PID_96CD&MI_02
USB\VID_04DD&PID_96CD&REV_0228&MI_03
USB\VID_04DD&PID_96CD&MI_03
I cannot find its driver anywhere...
Can I mod the HTC/Moto one and force it installed? I want to use QPST to explore its internals.

tewilove said:
Hi, I have a SHARP SH-06E and I successfully turned on its DIAG mode.
Now I have some devices not recognized, the HW IDs are below:
USB\VID_04DD&PID_96CD&REV_0228&MI_02
USB\VID_04DD&PID_96CD&MI_02
USB\VID_04DD&PID_96CD&REV_0228&MI_03
USB\VID_04DD&PID_96CD&MI_03
I cannot find its driver anywhere...
Can I mod the HTC/Moto one and force it installed? I want to use QPST to explore its internals.
Click to expand...
Click to collapse
Hello. How do did you enable in this mode smartphone Diag mode? You can link to the manual?

Killsleep said:
Hello. How do did you enable in this mode smartphone Diag mode? You can link to the manual?
Click to expand...
Click to collapse
Temp root, and then run this it will allow DIAG.
Then setprop, see init.qcom.rc for details.

IIUC, diag mode drivers should be same for all Snapdragon (600 here) devices. Anyway it's pretty easy to edit driver ID and force installation.
Please keep us in touch, enabling QPST access will be great.
Also maybe you know is there any way to enter recovery without ADB?

temp root
tewilove said:
Temp root, and then run this it will allow DIAG.
Then setprop, see init.qcom.rc for details.
Click to expand...
Click to collapse
How can I temp root the sh-06e? Doe's an english description exist?

Hree said:
How can I temp root the sh-06e? Doe's an english description exist?
Click to expand...
Click to collapse
I am still working on the translation of the rootkit. Should be ready in the next couple of days and will upload it to my website.

cheeseus said:
I am still working on the translation of the rootkit. Should be ready in the next couple of days and will upload it to my website.
Click to expand...
Click to collapse
Thank you, than I will see it on your famous webside :laugh:

Hree said:
Thank you, than I will see it on your famous webside :laugh:
Click to expand...
Click to collapse
TWO DIFFERENT rootkits translated and uploaded
But please note that I've had to implement a script that only allows one download per 24 hours because there has been some abuse, and my hosting plan doesn't offer a lot of traffic.

cheeseus said:
TWO DIFFERENT rootkits translated and uploaded
But please note that I've had to implement a script that only allows one download per 24 hours because there has been some abuse, and my hosting plan doesn't offer a lot of traffic.
Click to expand...
Click to collapse
Thank you, I used the Sharp Android Rooting Tools version 6.1 / 6.01.2014 and it functioned well.
You did a good job

cheeseus said:
TWO DIFFERENT rootkits translated and uploaded
But please note that I've had to implement a script that only allows one download per 24 hours because there has been some abuse, and my hosting plan doesn't offer a lot of traffic.
Click to expand...
Click to collapse
My sharp is rooted thanks to you! Thank you! But what can I do now? Can I upgrade my sh-06e with Kitkat or update my present system 4.2?
Best regards for all of you!

joshua.maxell said:
My sharp is rooted thanks to you! Thank you! But what can I do now? Can I upgrade my sh-06e with Kitkat or update my present system 4.2?
Best regards for all of you!
Click to expand...
Click to collapse
Welcome!
No, I'm afraid not. Sharp's (and all of Japanese manufacturers') smartphones use highly customized versions of Android. Your only chance to upgrade to a higher version is when Sharp/Docomo release it. Still, you will need to have installed all minor (software) updates before that. What this means: Once a new version of Android is released, send your phone to someone in Japan (e.g. the seller you bought it from) to update to latest build version, then upgrade Android, then return to you. Everything else - you risk bricking the phone.
What you can do now that you have root... Install Titanium Backup Pro to make backups of /system apps, then uninstall them (but make sure you read on Japanese sites what can and what can't be disabled unless you want to brick your phone).
Another thing you can do is install Link2SD to integrate updates of built-in apps into /system (overwrite the built in apps with newer versions). This, however, is not really necessary now that the phones come with 8-16 GB of onboard storage -- used to be important for phones like my 005SH or SH-01D where available ROM space was 200 MB and 850 MB respectively.
Yet another thing you can do is install AutoStarts to disable certain apps from launching when the phone boots, e.g. OneSeg TV and many others -- this will make the phone work faster. But then again, the SH-06E is pretty powerful... how much faster do you want it to be?

cheeseus said:
Welcome!
No, I'm afraid not. Sharp's (and all of Japanese manufacturers') smartphones use highly customized versions of Android. Your only chance to upgrade to a higher version is when Sharp/Docomo release it. Still, you will need to have installed all minor (software) updates before that. What this means: Once a new version of Android is released, send your phone to someone in Japan (e.g. the seller you bought it from) to update to latest build version, then upgrade Android, then return to you. Everything else - you risk bricking the phone.
What you can do now that you have root... Install Titanium Backup Pro to make backups of /system apps, then uninstall them (but make sure you read on Japanese sites what can and what can't be disabled unless you want to brick your phone).
Another thing you can do is install Link2SD to integrate updates of built-in apps into /system (overwrite the built in apps with newer versions). This, however, is not really necessary now that the phones come with 8-16 GB of onboard storage -- used to be important for phones like my 005SH or SH-01D where available ROM space was 200 MB and 850 MB respectively.
Yet another thing you can do is install AutoStarts to disable certain apps from launching when the phone boots, e.g. OneSeg TV and many others -- this will make the phone work faster. But then again, the SH-06E is pretty powerful... how much faster do you want it to be?
Click to expand...
Click to collapse
Thank you very much for this reply! That's very kind of you. My phone has some little fault (software). When I'm using the lock screen (trying to unlock) the phone resets itself. That's the one problem I have at the moment. My sharp is new and really great but I have little kids and I'm afraid that one day they may use my phone.
I thought if my phone is rooted I can upgrade the system to kitkat or normal jellybean ( not branded) and fix that problem.
Looks like I have only two options. Sell it on ebay or try it to do some upgrade. There are some apps on google play, maybe mobile odin pro or something? Any ideas?
regards for all

joshua.maxell said:
Thank you very much for this reply! That's very kind of you. My phone has some little fault (software). When I'm using the lock screen (trying to unlock) the phone resets itself. That's the one problem I have at the moment. My sharp is new and really great but I have little kids and I'm afraid that one day they may use my phone.
I thought if my phone is rooted I can upgrade the system to kitkat or normal jellybean ( not branded) and fix that problem.
Looks like I have only two options. Sell it on ebay or try it to do some upgrade. There are some apps on google play, maybe mobile odin pro or something? Any ideas?
regards for all
Click to expand...
Click to collapse
Hm... resetting when unlocking the screen... sounds weird. A friend has this phone, and my brother is still waiting to receive his in the next couple of days. But I haven't heard of any such issue with it. What is your build version? The latest one is 1.00.07. I read in the updates list that various bugs have been fixed but no mention of yours.
Have you disabled any apps? Maybe you can try re-enabling everything, then resetting to factory settings --- NEVER reset to factory setting if you have disabled any apps. Not sure about a rooted SH-06E.
I am sure that Android 4.3 will roll out some time this year for the SH-06E. You can upgrade it then. I might be able to help you with that but we'll see once the update comes out.

I did uninstall actually some apps but after when I restored the system everything was ok until I started to install google apps and the others. There may be some conflict. But obviously I'm not sure.
This phone is really pretty so perhaps I will not take a risk but who knows...
It would be nice if you could help me with installation of android 4.3. I have tired to find some information on Japanese websites, a there is some "img files" but those files are to small so perhaps it's not the system.
My build version is 1.00.07.
Kind regards
A little correction. I think I know what the problem is. I did not make an update of google keyboard and the problem gone. At this moment of course, after all day of using my Sharp. I hope this can be helpful for somebody.

Have you finally managed to get QPST worked?
I really want to use EDGE on my SH-06E but it seems that I have to enable it myself with QXDM.
I saw some Japaneses use HTC Diag driver on Xperia Z Ultra and it worked. Perhaps it would work with SH-06E.

hi there,
I just wondering, is it possible to upgrade to the latest (software/firmware/OS) SH-06E outside Japan? can I directly update just like ordinary android phone by OT using wifi?
thanks before

romeokk said:
Have you finally managed to get QPST worked?
I really want to use EDGE on my SH-06E but it seems that I have to enable it myself with QXDM.
I saw some Japaneses use HTC Diag driver on Xperia Z Ultra and it worked. Perhaps it would work with SH-06E.
Click to expand...
Click to collapse
Sorry but i don't know what QPST or QXDM is?
---------- Post added at 11:17 PM ---------- Previous post was at 10:32 PM ----------
wilto said:
hi there,
I just wondering, is it possible to upgrade to the latest (software/firmware/OS) SH-06E outside Japan? can I directly update just like ordinary android phone by OT using wifi?
thanks before
Click to expand...
Click to collapse
I'm afraid you can't do this.

tewilove said:
Temp root, and then run this it will allow DIAG.
Then setprop, see init.qcom.rc for details.
Click to expand...
Click to collapse
hello. did you find driver? and what to do with setprop?
Thanks

can u help me to enable diag mode for SH-10D
can u help me to enable diag mode for SH-10D without root!

How can I enable the DIAG mode in a 302SH? Already rooted, but unable to activate the DIAG mode so I can do a research in QPST? any tips?
---------- Post added at 12:47 PM ---------- Previous post was at 12:30 PM ----------
tewilove said:
Temp root, and then run this it will allow DIAG.
Then setprop, see init.qcom.rc for details.
Click to expand...
Click to collapse
What to do with Setprop? trying this in 302SH

[ROOT] [ROM] [LP] [5.0.1] ROOTED Lollipop [Alternative for DevEd] [WIP for RetEd]

​
MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices. it's used here to hijack the boot process & boot from a virtual ROOTED LP IMG in a 2nd EXT4 partition on the microSD card, that's independent on the physical system partition.
IMPROTANT INFORMATION: THE METHOD USED IN THIS THREAD IS SUCCESSFUL ON UNROOTED DEVELOPER EDITION WITHOUT USING A RECOVERY OR AUTO-ROOT - AND DOES NOT TRIP KNOX FLAG. FOR RETAIL EDITION, THE LOCKED BOOTLOADER SENDS A FLAG TO THE KERNEL TO WRITE PROTECT PARTITIONS INCLUDING SYSTEM.
POTENTIAL SOLUTION: BUILDING A KERNEL MODULE TO DISABLE WRITE PROTECTION AFTER PATCHING MEMORY TO BYPASS KERNEL MODULE VERIFICATION AND LOAD OUR UNSIGNED KERNEL MODULE – UTILIZING THE TEMPORARY ROOT ACCESS. WE ARE INVESTIGATING THIS SOLUTION. HOWEVER, IT MAY TAKE A LONG TIME AND IS NOT 100% GUARANTEED !
★ Disclaimer:
This service is FREE of charge, use it at your own risk, take it or leave it !
Click to expand...
Click to collapse
THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USE AT YOUR OWN RISK!
Click to expand...
Click to collapse
MultiSystem is a powerful tool and can perform potentially dangerous and/or destructive operations on your device and data that may affect your life. While it is unlikely to do irreversable damage to your device, it is not impossible, and you should proceed with caution. Loss of data and/or the need to re-flash a full stock (manufacturer-supplied) firmware IMGs (usually requiring a computer) is always a possibility, and is increasingly likely if you do not know what you are doing. It is possible to lose root access when using MultiSystem on locked-bootloader devices running unexpoitable (bu rooted) Android firmware, without careful reading of documentation or following the instructions. Please consult with expert users before performing actions you do not comprehend.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Notes:
To devs: Please do not use/port MultiSystem to any other device. If you'd like to add support for your device, please contact me!
Click to expand...
Click to collapse
To users: This thread is only for DEVELOPMENT. If you need a place for general discussions, go to the Q&A thread.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Instructions:
FLASH N910VVRU1ANJ5 Full Firmware, if needed
PARTITION microSD into 2 PRIMARY partitions: FAT32 & EXT4
ROOT via KingRoot: don't complete the installation, disconnect WiFi & close it after injecting su or when you see kinguser icon in app drawer !
MOUNT rootfs & system read/write in Terminal Emulator
Code:
su
mount -o remount,rw rootfs
mount -o remount,rw /system
INSTALL BusyBox to /system/xbin
INSTALL MultiSystem v1.3.1
UPDATE BusyBox by runnig the folowing commands in Terminal Emulator
Code:
su
MultiSystem advanced update_busybox
UNINSTALL KingRoot & all apps
DOWNLOAD & extract N910VVRU1BOAF_ROOTED.7z on device
ADD N910VVRU1BOAF_ROOTED.img to MultiSystem/img/system
OPEN & MultiSystem app
CLICK Update Configurations button
ACTIVATE Virtual System using the switch
SELECT N910VVRU1BOAF_ROOTED.img in Primary Virtual IMG
REBOOT to Download Mode from MultiSystem app
FLASH this for RetEd or this for DevEd via Odin
ENTER stock recovery before it boots up
WIPE data (Factory Reset)
REBOOT to the active virtual ROM - You can stop here if you wish!
WRITE the IMG to stock system partition /dev/block/mmcblk0p24
DONE
Thanks To: @Tomsgt , aka RootJunky
Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:
Click to expand...
Click to collapse
FOR DEVELOPER EDITION:
DO NOT FLASH RETAIL FIRMWARE, IT WILL LOCK YOUR DEVICE !​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Downloads:
N910VVRU1BOAF ROOTED: N910VVRU1BOAF_ROOTED.7z
md5: 244f1bc0f050ab5f95f6dd5507beaf50
Click to expand...
Click to collapse
★ Credits:
@ChainFire - for SuperSU & FlashFire
kingroot.net - for KingRoot
@gatesjunior - for KingRoot heads up & testing
@Tomsgt - for KingRoot heads up & creating a video tutorial
All authors of binaries/libraries, source codes, or tutorials
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
.

MINE

owenbeals said:
MINE
Click to expand...
Click to collapse
lol
Sent from my SM-G925V using XDA Free mobile app

Now that instructions/details have been added, this post is obsolete.

Everything Pops...
I have to say, the spinning purple gifs, sparkling, scintillating, glitzy light effects, Facebook links, fonts of different sizes and colors...everything is just stunning.
It imbues a sense of solemnity, in subtle ways that bring ineffable joy.
This has got to be the best OP I've yet to see on these fine forums.
Thank you.
I cannot wait to see what ensues.

DrPhant0m said:
Anyone that's interested in root progress of the RETAIL edition of the Note 4 may stumble across more details of what exactly is "Under Testing..." elsewhere, but out of respect of your privacy/strategy, I won't quote it from there to here. I'm being intentionally vague because you obviously didn't want to show all your cards in this thread yet.
However, I am curious (since I can't post in dev threads... I have to ask here) what the prerequisites are for this. Must one start with a specific software release? Can one enjoy root on a KitKat ROM, or must one be on Lollipop to get root this way? Is kingroot required, or are you jacking the code to install supersu instead of their weird proprietary su? Will it work on the Note Edge as well? So many questions...
Really, my most important question is: Can I finally buy a Note 4/Edge?!?
Click to expand...
Click to collapse
I elieve he said it will use king root initially before autoatically installing su as well as youll have flashfire/multisytem with a prma rooted L rom.. im sure with flashfire/multisystem you guys will now be able to create custom roms probanly for kk as well
Sent from my SM-G925V using XDA Free mobile app

micmars said:
I have to say, the spinning purple gifs, sparkling, scintillating, glitzy light effects, Facebook links, fonts of different sizes and colors...everything is just stunning.
Click to expand...
Click to collapse
Don't listen to this guy... he trolled me like this back when I was on BajaROM. I almost forgot about the whole ordeal, since BajaROM has been completely off the map for updates. So long, in fact, that for a moment I thought it might have been back when I had an S3.
Anyway... we don't need any of his bad energy in this thread. Keep up the good work, @hsbadr. Stay professional.

DrPhant0m said:
Anyone that's interested in root progress of the RETAIL edition of the Note 4 may stumble across more details of what exactly is "Under Testing..." elsewhere, but out of respect of your privacy/strategy, I won't quote it from there to here. I'm being intentionally vague because you obviously didn't want to show all your cards in this thread yet.
However, I am curious (since I can't post in dev threads... I have to ask here) what the prerequisites are for this. Must one start with a specific software release? Can one enjoy root on a KitKat ROM, or must one be on Lollipop to get root this way? Is kingroot required, or are you jacking the code to install supersu instead of their weird proprietary su? Will it work on the Note Edge as well? So many questions...
Really, my most important question is: Can I finally buy a Note 4/Edge?!?
Click to expand...
Click to collapse
micmars said:
I have to say, the spinning purple gifs, sparkling, scintillating, glitzy light effects, Facebook links, fonts of different sizes and colors...everything is just stunning.
It imbues a sense of solemnity, in subtle ways that bring ineffable joy.
This has got to be the best OP I've yet to see on these fine forums.
Thank you.
I cannot wait to see what ensues.
Click to expand...
Click to collapse
elliwigy said:
I elieve he said it will use king root initially before autoatically installing su as well as youll have flashfire/multisytem with a prma rooted L rom.. im sure with flashfire/multisystem you guys will now be able to create custom roms probanly for kk as well
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
DrPhant0m said:
Don't listen to this guy... he trolled me like this back when I was on BajaROM. I almost forgot about the whole ordeal, since BajaROM has been completely off the map for updates. So long, in fact, that for a moment I thought it might have been back when I had an S3.
Anyway... we don't need any of his bad energy in this thread. Keep up the good work, @hsbadr. Stay professional.
Click to expand...
Click to collapse
Check OP for sketchy steps that will get revised while testing... just to give you an idea about what to expect!

hsbadr said:
Check OP for sketchy steps that will get revised while testing... just to give you an idea about what to expect!
Click to expand...
Click to collapse
First step is "flash NJ6 full firmware..."
So, does this mean that firmware updates don't burn the path and plow salt into the fields like they do on the Note 3? That step implies that you can downgrade, unlike my Note 3.

DrPhant0m said:
First step is "flash NJ6 full firmware..."
So, does this mean that firmware updates don't burn the path and plow salt into the fields like they do on the Note 3? That step implies that you can downgrade, unlike my Note 3.
Click to expand...
Click to collapse
lol yes.. ppl have been goin between L and kk since L has been out.. BL has yet to be incremented
Sent from my SM-G925V using XDA Free mobile app

DrPhant0m said:
First step is "flash NJ6 full firmware..."
So, does this mean that firmware updates don't burn the path and plow salt into the fields like they do on the Note 3? That step implies that you can downgrade, unlike my Note 3.
Click to expand...
Click to collapse
Note 4 bootloader wasn't incremented yet; you can go back & forth from NI1 to/from NJ6 to/from OAF. So, downgrade/upgrade is still safe.

elliwigy said:
lol yes.. ppl have been goin between L and kk since L has been out.. BL has yet to be incremented
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
Awesome news. I'm not quite ready to go to LP because I need KK for a few things. It really pains me to watch @hsbadr rip out all this awesome new stuff for my Note 3 while I watch from the sidelines. If I do upgrade to a Note 4, it's nice to know that I'll be able to dabble in LP a little to scratch the itch, and then go back go KK as a daily driver.

What Do You Mean?
DrPhant0m said:
Don't listen to this guy... he trolled me like this back when I was on BajaROM. I almost forgot about the whole ordeal, since BajaROM has been completely off the map for updates. So long, in fact, that for a moment I thought it might have been back when I had an S3.
Anyway... we don't need any of his bad energy in this thread. Keep up the good work, @hsbadr. Stay professional.
Click to expand...
Click to collapse
Wait, I conveyed a positive vibe...just like that which is found in the Baja thread...I complemented the OP, and am thoroughly enjoying your signature line as well as that of the OP.
Not only that, I harbor genuine joy for what lies ahead...and despite this, you besmirch my post? I see no good reason for this.
Oh well, my highest hope for what lies ahead...

Will this work with att versions

roughmouth said:
Will this work with att versions
Click to expand...
Click to collapse
Nope. Not currently. As it is a Verizon rom
Sent from my SM-N910V using XDA Free mobile app

This may be a better question. Is anyone going to try to get this to work with att?

roughmouth said:
This may be a better question. Is anyone going to try to get this to work with att?
Click to expand...
Click to collapse
Yes, after making it as simple as possible for VZW users.

hsbadr said:
Yes, after making it as simple as possible for VZW users.
Click to expand...
Click to collapse
Sweet. I'm sure you have plenty of request in your inbox but I'm willing to test and help in anyway. Good work!
Sent from my SM-N910V using XDA Free mobile app

hsbadr said:
Yes, after making it as simple as possible for VZW users.
Click to expand...
Click to collapse
The problem seems that kingroot will not work on note 4 lollipop, so how will step 2 work unless I missed something?

LegoFarmer said:
The problem seems that kingroot will not work on note 4 lollipop, so how will step 2 work unless I missed something?
Click to expand...
Click to collapse
Step one takes you back to KitKat.

LG-H812 Root

Hi All,
I'm new to the xda forums and hopefully not posting this incorrectly.
I was wondering if there's a root available for my G4 H812?
Thanks in advance!

Did you mean H812 because, I don't think there is any LG H912 available?

Mopar1015 said:
Hi All,
I'm new to the xda forums and hopefully not posting this incorrectly.
I was wondering if there's a root available for my G4 H812?
Thanks in advance!
Click to expand...
Click to collapse
Welcome! Good news, there is root for your device. I will direct you to our little thread which can be found in either my signature or here in this link:
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
It is a work in progress, so if you have any contributions or questions, feel free to ask!

Thank you, Spudnubs. @imarcel99 you're right, I meant the 812 ☺

I presume that you are from Canada and you're using H812. If that's so then please check out this: http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449

I sure am. I'll check out the three for sure. I miss having a nexus phone...so much easier

Mopar1015 said:
I sure am. I'll check out the three for sure. I miss having a nexus phone...so much easier
Click to expand...
Click to collapse
Agreed. This is pretty easy though, just a ton of steps.
I have a Bell H812, and I went with the Telus 10g kdz image, then the rooted.
Since I am a Rogers customer, I then went with the Rogers 10h kdz image, then the rooted 10h image.
xposed v45 sdk22 installed using flashfire (you have to sign up for the beta to be able to install it), and then gravitybox and my G4 is pretty happy. I miss custom roms since they incorporated some stuff that isn't in gravitybox but it's minor things.
Main thing to do is to read the threads carefully and not to get ahead of yourself.
Good luck!

Thanks goofball2k. I'll give it a shot this weekend and hopefully I don't mess it up ☺

Mopar1015 said:
Thanks goofball2k. I'll give it a shot this weekend and hopefully I don't mess it up
Click to expand...
Click to collapse
The thing with using the LG Flash tool is there is a popup that comes up soon after it starts flashing. Ignore that window and then pay attention to the progress window, it took about 4-5 min on mine to finish. It should reboot by itself after it has completed.
For me, I really had to pay attention to step 5.
On the page you opened in step 2, follow steps 1,2,3,6,7,8,and 9 on that page only, then come back here.
Ensure that on step 9, you use the right COM port.
Click to expand...
Click to collapse
The step to flash the rooted image is key as well, since you have the H812
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
Then the key is patience.
If you do the xposed install using flashfire, you really need to have patience and make sure the phone is charged.

Just wondering why this version is so much different to root when compared to the US variants.

Blur_Version.26.11.51.sperry_sprint.en.US

New OTA captured...merry christmas.
Blur_Version.26.11.51.sperry_sprint.en.US

CodyF86 said:
New OTA captured...merry christmas.
Blur_Version.26.11.51.sperry_sprint.en.US
Click to expand...
Click to collapse
Thanks, same to you. Did you install this with no problems with the bootloader unlocked?

I have'nt installed it was hoping someone would be able to extract the good stuff and make a zip.

CodyF86 said:
I have'nt installed it was hoping someone would be able to extract the good stuff and make a zip.
Click to expand...
Click to collapse
Just wondered. I'll see what I can do with it.

CodyF86 said:
I have'nt installed it was hoping someone would be able to extract the good stuff and make a zip.
Click to expand...
Click to collapse
You can probably just remove all the assert prop lines and install it.

madbat99 said:
You can probably just remove all the assert prop lines and install it.
Click to expand...
Click to collapse
That doesn't always work quite right. I just flashed stock firmware and updated. Finally got the September security patch. I'll upload flashables of the imgs and make a flashable ROM later on.

Does anybody else find it weird that the signal indicator has reverted back to the KitKat style... I don't get why they changed it, looks so dated.
But it is nice that you guys finally got the BlueBorne patch, next up should be the KRACK patch - fingers crossed.

ATTACK said:
Does anybody else find it weird that the signal indicator has reverted back to the KitKat style... I don't get why they changed it, looks so dated.
But it is nice that you guys finally got the BlueBorne patch, next up should be the KRACK patch - fingers crossed.
Click to expand...
Click to collapse
Yeah, we'll probably get that in March or April.

volatile1 said:
That doesn't always work quite right. I just flashed stock firmware and updated. Finally got the September security patch. I'll upload flashables of the imgs and make a flashable ROM later on.
Click to expand...
Click to collapse
Would you mind doing the same for the retail (XT1768) variant? Flashing back to stock didn't help in my case. I got the same "status 7" error as another person here. I looked at the update's updater-script, but not being conversant with the particular script language I didn't want to take the chance. Failing that, you can just tell me the correct way to edit the script file. "Blur_Version.26.11.46.perry.retail.en.US.zip" is linked below.
https://drive.google.com/file/d/1ju_Au1_M9yHqBNGW4-mXAIZS3iJd0B95/view?usp=sharing

e.mote said:
Would you mind doing the same for the retail (XT1768) variant? Flashing back to stock didn't help in my case. I got the same "status 7" error as another person here. I looked at the update's updater-script, but not being conversant with the particular script language I didn't want to take the chance. Failing that, you can just tell me the correct way to edit the script file. "Blur_Version.26.11.46.perry.retail.en.US.zip" is linked below.
https://drive.google.com/file/d/1ju_Au1_M9yHqBNGW4-mXAIZS3iJd0B95/view?usp=sharing
Click to expand...
Click to collapse
Sorry. Changed my mind, I'm not posting anything anymore. A user I see in another thread makes my want to go get a different phone now that he's around here. He's a giant douche. I think I'm going to keep to myself. Have fun guys.

Can any someone that has installed the ota do me a favor and pull the modem.xx files from /firmware and possible the fsg from /fsg, I''d like to build cm with them but i can't install the ota at this point I have working lte on lineage and im not screwing that up heh.
Maybe this will make it easier for others to get lte on lineage.

CodyF86 said:
Can any someone that has installed the ota do me a favor and pull the modem.xx files from /firmware and possible the fsg from /fsg, I''d like to build cm with them but i can't install the ota at this point I have working lte on lineage and im not screwing that up heh.
Maybe this will make it easier for others to get lte on lineage.
Click to expand...
Click to collapse
I haven't updated yet (no time). But I will probably flash back to stock and update this week or weekend. If (when) I do, I'll get it for ya.
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
volatile1 said:
Sorry. Changed my mind, I'm not posting anything anymore. A user I see in another thread makes my want to go get a different phone now that he's around here. He's a giant douche. I think I'm going to keep to myself. Have fun guys.
Click to expand...
Click to collapse
Guess your username is pretty accurate, lol. Just kidding bro. We only do this stuff if it's still fun. the minute it's not fun, well hey, keep it fun dude.

CodyF86 said:
Can any someone that has installed the ota do me a favor and pull the modem.xx files from /firmware and possible the fsg from /fsg, I''d like to build cm with them but i can't install the ota at this point I have working lte on lineage and im not screwing that up heh.
Maybe this will make it easier for others to get lte on lineage.
Click to expand...
Click to collapse
Here's the new modem.img and fsg.mbn
https://www.androidfilehost.com/?fid=745849072291693264
I suppose I'll make a flashable of the rest of it when I have time. I think it would be safer to just pull all the imgs of everything that was patched so it would be sort of like a twrp flashable stock firmware. I don't want to see anyone's phone get bricked. There were a lot of patches. I'll see..
If anyone else gets the idea to flash this, it might not work with the old rom. The old modem doesn't work with the new update.
madbat99 said:
Guess your username is pretty accurate, lol.
Click to expand...
Click to collapse
Yes it is.

volatile1 said:
Here's the new modem.img and fsg.mbn
https://www.androidfilehost.com/?fid=745849072291693264
I suppose I'll make a flashable of the rest of it when I have time. I think it would be safer to just pull all the imgs of everything that was patched so it would be sort of like a twrp flashable stock firmware. I don't want to see anyone's phone get bricked. There were a lot of patches. I'll see..
If anyone else gets the idea to flash this, it might not work with the old rom. The old modem doesn't work with the new update.
Yes it is.
Click to expand...
Click to collapse
Looks like you got the plus, nice. How is it?

madbat99 said:
Looks like you got the plus, nice. How is it?
Click to expand...
Click to collapse
Nice. A little bigger and heavier with a fp sensor.
Sent from my Moto E (4) Plus using XDA Labs

@CodyF86 I just found some missing libs that I don't know how I missed before. They very well may be the solution. I'll test it out, but will need someone with an activated device to know for sure if it works because I activated my E4 Plus. I should know if I see Boost Mobile for the carrier though. I'll have something to test before the day is over.
Edit: scratch that, turns out they were all there after all. Damnit!
Sent from my Moto E (4) Plus using XDA Labs

is the OP firmware OTA targeted solely for Sprint variant?

surroundedbydrones said:
is the OP firmware OTA targeted solely for Sprint variant?
Click to expand...
Click to collapse
Yep. Sprint, boost, virgin Mobile.

ATTACK said:
Does anybody else find it weird that the signal indicator has reverted back to the KitKat style... I don't get why they changed it, looks so dated.
But it is nice that you guys finally got the BlueBorne patch, next up should be the KRACK patch - fingers crossed.
Click to expand...
Click to collapse
Yeah I noticed. Changed it with xposed.

After the update to 26.69-56 I'm finally getting lte+