yashsingh1/xdaforums huggingface dataset:
[G4 General] Bill Gamble:
An F version of which model?
[G4 General] BryWr:
Ahh, don't I feel silly. Thanks very much!

All working now on Tmo!
[G4 General] bendsley:
They've had root for a while as I understand it. Granted the method right now isn't the prettiest, at least it isn't bricking phones as they have been worried about it.
[G4 General] TDSJR:
Are you trashing the developers reps?
[G4 General] leond:
my Sprint system image dump is up and live on a dropbox folder, link has been send to OP.

Build number: LMY47D

Software version: LS991ZV5
[G4 General] flamadiddle:
Can you blame them for wanting something in return for all their hard work? They met the requirements of the bounty, and they did it first. Be happy.
[G4 General] thecubed:
Let me just put this to bed: we're not claiming the bounty for root. This isn't a root that I'd feel deserves a bounty claim, it's such a cheap way to get root.

We'd also rather not waste exploits. We were sitting on this for a while so we could come up with an alternate root that didn't blow this one, however since someone else had the exact same root, we figured we might as well release it.

Codefire and jcase have had this exploit since a few days before jcase's video confirming root was released.
[G4 General] kyle1867:
I'm not pointing fingers at anyone, I'm just commenting that this is very humorous. Competition does good things.
[G4 General] leond:
This is the beauty of capitalism, competition and free market. Whoever gets with their product to the market first gets to cash out.

What exactly is the complain?
[G4 General] ramsesht:
I am on LS991ZV4

do we need this image as well?
[G4 General] fatboypup:
dunno if anyone else pulled a Sprint .img but im uploading mine now
[G4 General] ramsesht:
Software version info please? Thank you in advance.
[G4 General] bendsley:
OEM Unlock is in android on all devices. T-Mobile was the only one it seems that didn't lock theirs. Flashing TWRP on AT&T variant will not work right now.
[G4 General] hkfriends:
awaiting for H815T v10b :)
[G4 General] thecubed:
We're working on the Sprint one right now, looks like our read command was a bit wrong. Thanks to [MENTION=1083982]leond[/MENTION] for working with us on this.
[G4 General] SpinningHook:
I am having problems with step number 8 of the linked "[GUIDE] New Root Method for LG Devices" tutorial. Every time I run the ports.bat file, I get what's detailed in the attached pic, i.e. nothing that is disclosing which ports to use. I am positive that I have followed the instructions precisely up until that point. Has anyone else encountered this or have any ideas (my model is VS986)? Thanks in advance
[G4 General] TheShadow1:
Thank you so much for your service. It is very appreciated. Eagerly awaiting sprint root.
[G4 General] Ser Gilgoroth:
Removed
[G4 General] the_scotsman:
Is your phone connected with USB? USB debugging enabled? Drivers installed? Check device manager to ensure there are no yellow exclamation marks next to the device.
[G4 General] davelee1054:
I don't have much context but just looking at the command it just means the script failed to find any entries in that registry folder.

OP/anyone: I know you might not have this information yet but do you know if this root will work for either version of the Sprint software? ZV4 (original) and ZV5 (after OTA)
[G4 General] iakovl:
H815L israel
[G4 General] Broth3rz:
Where does one see '10c' on the H815 model?
[G4 General] antus:
For the record, I have tried this inject root script method on the Aus/Optus H815T and the results were not successful. The phone failed to boot.

I still had the original system.img on the internal storage, and was able to use download mode to access the phone again and flash the original file back. This recovered the phone.

First attempt was with 10b and I took the OTA to 10c and tried again with the same results.

I then broke down the process doing small parts of autoroot.sh and testing to see what breaks it. I can install the su binaries, and I can make the modifications to install_recovery.sh. The boot breaks specifically when I replace app_process64 with a symlink to daemonsu.

I have also noticed the phone has a root checker and it is logging and reporting my attempts. From reading threads about the G2/G3 it looks like this checker is for warranty purposes and wont actually be stopping me. Can someone confirm this?

Modified

Rooting related file had been installed
> .sh
> .ext
> su
> superuser
> busybox

Detection time
> 2015-08-14 18:36

[p1:LGH815xxxxxxxxxx:6.03]

I am currently thinking that the current version of supersu is not compatible with this phone. Is there a better root development thread area to discuss this issue with those who are developing the root images?

Sure I could flash the international version and probably be happy, but thats not what this forum is supposed to be about, right?

Ive learnt heaps about the G4 trying to figure this out, and am having a good time doing so :)
[G4 General] storm91:
Anyone tried with F500S 10x?
[G4 General] p33k:
I keep meaning to dump my system image and see if someone can inject root into it. Let me know if you find anything out ;) and I'll do the same!
[G4 General] antus:
You can try it with the details from the thread listed above. Just make sure you keep system.img on your phone as well as rootedsystem.img so that you can flash system.img back on if it fails to boot. Use the same DD command, just change the file your referencing. Eg if the details at the start of this thread are:

dd if=/data/media/0/rootedsystem.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0

Use this to recover it:

dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0

I found my phone "optimised" the apps again after the first recovery but booted up fine and back to normal. Ive now broken it more than 10 times, still trying to get it right for this variant. :D Main thing is the skip and offset variables for DD. Dont mess with them to keep your changes localised to the system partition and assuming your original system.img is still present recovery is straight forward.
[G4 General] storm91:
Hi mate. Thanks for the explanation and the rule of posting!

---------- Post added at 04:09 PM ---------- Previous post was at 03:37 PM ----------

Hi p33k, I tried this method it doesn't work

http://xdaforums.com/android/development/guide-root-method-lg-devices-t3049772

In the end, I tried the method under this thread and it works brilliantly !

But you need to inject autoroot.sh manually. What I mean manually here is "YOU" created and inject the system.img that you backed up originally.

And also following the comment from the previous guy, he told me to put both original system files and rootedsystem.img in my phone so for "worst case scenario" something goes wrong. I can always come back to my original.

Proves After Root. (My device is F500S 10x base software version)

HERE

HERE

Gosh I'm so happy right now, if you have any questions I will try my best to guide you
[G4 General] daClaus:
After flashing the pre-rooted systemimg I lost exFat support (was on 10b, the pre-rooted file is 10c). So I need to flash the matching boot.img - I assume the one for 10c. Can anyone tell me where to find this file and how do I flash it?
[G4 General] Shadicbypass:
You cant yet you have to flash a kdz and then ota to 10c and then reroot
[G4 General] antus:
After enough messing around I finally got my Aussie Optus H815T rooted manually. Now I understand everything about supersu I will get some sleep and come back to autoroot.sh and try again to see if I can figure out why it didnt work on this variant. I think its something to do with the selinux perms of these files, or the version included in the autoroot zip. (this list is not exhaustive of files installed). These files should come out like this, and the version included seems to be missing the sugote files. The zygote_exec selinux perms seem to play part in this, and does seem to be necessary for my device. In my case, if these files all exist in the right place but those with zygote_exec perms are setup with system_file perms then boot does not complete.

[root@gemini operatingtable]# ls -lZ bin/app_*
lrwxrwxrwx. root root u:object_r:system_file:s0 bin/app_process -> app_process64
-rwxr-xr-x. root 2000 u:object_r:zygote_exec:s0 bin/app_process32
lrwxrwxrwx. root root u:object_r:system_file:s0 bin/app_process64 -> ../xbin/daemonsu
-rwxr-xr-x. root root u:object_r:zygote_exec:s0 bin/app_process64_original
-rwxr-xr-x. root 2000 u:object_r:system_file:s0 bin/app_process_init
[root@gemini operatingtable]# ls -lZ xbin/*
-rwxr-xr-x. root root u:object_r:system_file:s0 xbin/daemonsu
-rwxr-xr-x. root 2000 u:object_r:system_file:s0 xbin/dexdump
-rwxr-xr-x. root root u:object_r:system_file:s0 xbin/su
-rwxr-xr-x. root root u:object_r:zygote_exec:s0 xbin/sugote
-rwxr-xr-x. root root u:object_r:system_file:s0 xbin/sugote-mksh
-rwxr-xr-x. root root u:object_r:system_file:s0 xbin/supolicy
-rwxr-xr-x. root 2000 u:object_r:system_file:s0 xbin/tcd

command> .\adb shell
shell@p1:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:toolbox:s0
shell@p1:/ $ su -
su -
root@p1:/ # id
id
uid=0(root) gid=0(root) context=u:r:init:s0
[G4 General] jxordan:
I misread this and accidentally did step 5 (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). Should I continue or did I just mess the process up
[G4 General] Shadicbypass:
It wont affect just continue
[G4 General] jlv3:
The guessing the whole reason to use the pre-rooted image is because the lg_root.sh script from the other thread doesn't work correctly with the G4, correct?

I would suggest updating post #1 with a step to save the original system image (as described in post #2: Backup System to Internal Storage).

and THANK YOU for this!!
[G4 General] antus:
Correct, selinux has been tightened up since the G3 and the script can not break out of it (I tried it, ran through the whole steps just to test). Further, nobody has found any other way to break out of it. So we need to copy the while filesystem off the phone, patch it on another linux system and then copy it back like it pc based firmware update would do. Grabbing the pre-rooted images saves you making the image, but the autoroot.sh discussed above is another option if your phone is not an exact match for the images in the first posts.
[G4 General] workdowg:
Success!!!

Thanks again guys (coming from LG-G3 BUMP'D Official!)!!

I ran this in a VirtualBox Win 8.1 VM on my Arch laptop. Only issues I had were getting com ports. The ports.bat batch file didn't work. But I manually searched the registry for the ports. Also there was a missing dll, but that was just a quick Google search away (Edit: Installed the C++ Redistributable Package 2010)

[MENTION=1157052]thecubed[/MENTION] - Confirmation number: 71F21969JS813812T

[MENTION=6053822]IllegalArgument[/MENTION] - Confirmation number: 31019320FD651663A

[MENTION=2684188]autoprime[/MENTION] - Confirmation number: 3JH03396BK962511U

[MENTION=2376614]jcase[/MENTION] - Confirmation number: 6EH86297Y65718823
[G4 General] RenaKunisaki:
Yeah, G3 and I think G2 had this as well. There's the rctd binary (probably what does the actual checking, but maybe there are other checks too), rct.cfg, another file with a less obvious name (can't remember now, it's in my notes on PC) which is 4 bytes telling what rct found, and even an eMMC partition named rct with those same 4 bytes in it, and who knows where else this bugger hides. The service menu can display the log, IIRC there's a "disable" option too but doesn't appear to do anything.

Personally I'm less concerned about that, and more about unlocking the bootloader and preventing that stupid security error when I dare to remove Google Books and other bloat, and having XPosed. Even with root, we still don't have control over our own devices...
[G4 General] Shadicbypass:
I never recommend just placing a dll file directly into the application library you need to install the c++ redistributable package 2010. You were lucky in that it worked with you doing that.
[G4 General] workdowg:
Yes, that is what I had to do. I edited my post. ;)
[G4 General] Broth3rz:
My H815 says it's 10B. It says I have no more updates, how do I get 10c??? I'd like to root my phone but it's not 10c...?
[G4 General] android404:
It was the same with me. I suspected that it somehow had to do with my carrier and their update policy (telenor, norway). After "going back to stock" following this there was an ota update available and I'm rooted now.
[G4 General] rob219:
i got it to work. i used the 2014 lg flash tool, the PRH810PR10a_02.kdz put it in emergency mode instead of diag then used cse flash instead of normal flash.

i have the at&t black leather version. i flashed the atT one an if was fine but wanted the H810PR10a-310-410_Rooted.system image instead. now im stuck on the lg logo and dont know what to do. my mtp and usb modem drivers fail to install so i have no adb to push the image to my internal memory to flash it. can i flash it from the computer without having adb and the image on the computer and not on the phone? or can someone provide a mtp drive so i can at least adb?
[G4 General] montusk:
where can i find the prerooted img for h815 (international) v10d? S3V3N's link oile posted is not available anymore
[G4 General] rob219:
everytime i try flashing the at&t image it bricks my phone. i have to keep using the puerto rican kdz to restore it. i just tried everything again and flashed the at&t on and again its bricked. just gonna take it back and get an s6, at least i can slap i rom on it.
[G4 General] Shadicbypass:
Did you make sure you are doing everything step for step
[G4 General] chadderbox:
Once you go to the PR KDZ you can't go back to AT&T's ROM. That's why you keep bricking your phone. Not sure why it happened initially other than missing a step possibly but once committed to the PR ROM, you're stuck till we get an AT&T TOT out in the wild.
[G4 General] Follow_and_Feel:
I don't know why, but I'm not able to download the tar.gz file?!

The download starts and then there's 0,00 kb/s speed. All my other connections are working. Is there a problem with the server? :rolleyes:

Kind regards

Follow
[G4 General] Shadicbypass:
Which file
[G4 General] Follow_and_Feel:
The international h815 tar.gz
[G4 General] PalmCentro:
by me it works...

View attachment 3441213
[G4 General] Follow_and_Feel:
Ok thank you. Then it has got to do something with my crappy internet provider. Thanks for letting me know :)

But...do you know any other hoster where I could download the file?

Because I'm getting the g4 tomorrow and I MUST root it. Otherwise it wouldn't be a good phone :D

Kind regards
[G4 General] PalmCentro:
The only place wherethese files are stored are in the OP and

So.... Sorry
[G4 General] ssmaster:
Can anyone elaborate as to why EXFAT support gets broken once rooted (I'm on VZW 11A)? I spent hours trying to diagnose my 64gb micro sd card, bought a new one, and now realized I had to reformat as FAT32.

Actually, reformatting to FAT 32 didn't work. The card is readable in my PC, my wifes G4 unrooted, but not my G4 rooted.
[G4 General] hdelvalle009:
work in windows 10?
[G4 General] Shadicbypass:
If you flash a system image that is different then your current version. It causes a boot.img and system mismatch which causes exfat to break for some reason
[G4 General] ssmaster:
My problem is a bit more than that. Now I reformatted my new card as FAT32. I tried it in my wife's G4 unrooted and it works fine, and it doesn't work on my phone. I am starting to think its a hardware issue. My original SD card worked fine for 2 or 3 days before I started getting errors. That is why I think its due to hardware at this moment.

I tried putting in an old trusty card from my DROID CHARGE and it wouldn't read that one either. I am going to have to flash back to stock unrooted and get it fixed under warranty.
[G4 General] Shadicbypass:
Yeah you are gonna need to do that
[G4 General] RenaKunisaki:
Don't just restore the original system.img. Flash a KDZ and see if that fixes it; if not, then have it repaired. This is because the G4 (like other LG devices) have a little process "rct" that checks for certain files (SuperUser.apk, su, busybox, etc) and actions (executing "su") and logs what it finds in various places such as rct.cfg and an "rct" partition on the internal flash. Simply restoring the original system.img won't erase these logs. Restoring a KDZ might erase them (I think it restores all partitions to factory state, but I'm not sure), and also might fix the problem (if it does turn out to be a software issue). If they see that log and find you rooted the device, they might not honour the warranty, so you don't want to take that chance.

Alternatively, you could do what I (accidentally) did and wipe out the entire eMMC (using the same method used to root the device), which will brick it so hard it won't even power on; then just tell them you don't know what happened (last night it worked, today it's dead). In my case they evidently couldn't figure out what went wrong either and just replaced the mainboard.
[G4 General] Shadicbypass:
Wow how did you achieve that. How did you mess up the command
[G4 General] RenaKunisaki:
When I flashed my system.img I mixed up the "skip" and "seek" parameters :| so instead of copying the entire file over the system partition, I copied part of the file over everything. Apparently with a missing bootloader, it won't do a thing.

Don't root phones at 2AM, kids.
[G4 General] Shadicbypass:
Lol haha well as a last resort for warranty purposes
[G4 General] r4Rok:
Something quite strange is happening on my H818N 10d rooted phone......two days back suddenly stock messaging app, Hangouts and WhatsApp started force closing. Now when, i open stock messaging app, it just force closes and doesn't open. Hangout and WhatsApp would open, but force close, when an message is tap to open. I tried to factory reset, but setup couldn't complete, becasue of force close on Google Play service. So, i KDZ 10d, and re-injected root in to 10d_system, and flashed it. The phone worked fine for a day, now again force close on all the three 'stock message app, Hnagouts, and WhatsApp" has started. Any idea, what's causing these force close?

PS: Before, re-flashing KDZ, and re-rooting, I deleted system cache, application cache and their data but to no avail.
[G4 General] jlv3:
Sorry to hear about that! A good reason to use cut-and-paste.
[G4 General] hackarchive:
I'm currently uploading the stock img for China H818. Can anyone walk me through how to inject root or provide a link or should I just post the uploaded file here for a good Samaritan to take over?
[G4 General] Fma15:
So will this also work with the h812 internatinal version?
[G4 General] storm91:
Hi dude, I did inject root on my own for my F500S (Korean Variant) 10x software based. It's basically simple as I combined few tutorials from xda and some from lgviet.com forum.

Basically, what you need is just a stock unrooted system.img, then boot up your Linux (ubuntu if you have). Actually any other debian should work. I tried using Kali Linux to inject the root to the system.img, it works flawlessly as well.

So right after you rooted your own system.img, pushed back to your internal storage and used the dd command to replace the original system image file that's currently running in your device.

I believe this method is safeproof as long as you didn't messed up the block bytes during the dd command. Other than that, you are 'safe' in terms of going back if something goes wrong during the process.

Good Luck and have a try. I'm not sure it will work for H818 version but I believe it will, since this method is ALL variants method :good::good:

Oh yea, you can refer to Page #179 for my post of my successful rooted file
[G4 General] TheBiles:
Can we use this to downgrade from 11A? I rooted when I was still on 10B and had to flash the stock 11A through the LG tool, and I think that may have interfered with my advanced calling.
[G4 General] Follow_and_Feel:
Yeah i read that. Thought he'd maybe mirrored it himself, but ok.

Can anybody confirm this method working on H815 10a?
[G4 General] hackarchive:
Found that thread later myself too and niw I'm rooted. Injected myself.Already posted a how to in the general section.
[G4 General] Lock-N-Load:
So if people are doing this, and then turning off OTA, how are people expecting to have the Stagefright issue resolved if their phone brand/provider is affected?
[G4 General] Follow_and_Feel:
Hey there. I have a similar problem. Just bought the G4 today and, of course, rooted it immediately. I came from a Galaxy Note 4 and did a titanium backup for the G4. Now the G4 won't read my MicroSD-card. I checked it in my former Note 4 - All the files are there. Is there any way to be rooted and still use the MicroSD? The only reason why I've rooted the G4 is because of the data from the Note 4 (well okay, several other reasons too). So does anybody have a workaround for this? I really need my 128GB card :crying::crying:
[G4 General] rfarrah:
Do a google search for SD card fix. Fixed mine. Good luck!
[G4 General] Follow_and_Feel:
Well I just formatted the card with the G4 after i did a complete backup to my PC with another mobile phone. Now the sd card is mounted and I have no issues, if that helps anybody. Cheerio
[G4 General] flamadiddle:
There's no downgrade from 11A. The 11A bootloader increments a counter that prevents a previous version from being installed, and if the bootloader and system image mismatch, you get a bootloop.
[G4 General] antus:
Imho you would be better off rooting your own system.img than installing a mismatching one which causes that. Pitty nobody has rolled this up in to a root package which roots your own img yet.

Also, if your watching LG - you'd get less warranty claims and less malfunctioning phones out in the wild if you let us unlock our bootloaders see?
[G4 General] Shadicbypass:
They have not done that because it says in the op that you are not allowing to roll any of this into a one click root
[G4 General] asaf400:
Hey guys, just wanting to let you know, I've managed to get exfat going on my rooted 10c without a complete kdz flash..

I've done what people have suggested:

Just flash the boot.img for the 10c version so there woudn't be a mismatch between 10c system.img and 10b boot.img..

I've done this by extracting the boot.bin (.img) from the LG 10c .KDZ (and .DZ) with the tool from here:

http://xdaforums.com/showthread.php?t=2600575

copied the boot.img to the device, and then used flashify (STOCK Recovery and LOCKED Bootloader) to flash the boot.img,

And it has worked :)

The reason for my late upgrade is I was waiting for Xposed to 'work' for my H815 EUR,

And now IT DOES!!

Head over here for info:

http://xdaforums.com/g4/general/wip-install-xposed-framework-t3140904

And now I have a rootedsystem.img of 10c With Xposed ;) !!

I'm uploading my .img now, will update if anyone is interested..

P.S I've 'installed' xposed the same way this root method works:

http://xdaforums.com/g4/general/lg-g4-dual-sim-models-h818p-h818n-t3115759/post62097182#post62097182

by offline mounting the system.img to ubuntu, and then running the xposed install script (givven i've mounted my system to the actual /system root folder in the ubuntu machine, and the xposed files are at the current directory which the script runs from...)

This way, I've used the 'accepted' install script, in an offline and safe manner, without the need for custom recovery or tinkering \ understanding the install script :)