Related
Does anyone know is there a one click root app out there for the GN yet? Will Unrevoked be doing a program for this? If not is there an word of one being done? It was made so easy for my DINC I would love to get my free tethering back.
here lets look at a pinned topic from the Gnex General board
http://forum.xda-developers.com/showthread.php?t=1338442
and one from the dev board
http://forum.xda-developers.com/showthread.php?t=1360413
Goat_For_Sale said:
here lets look at a pinned topic from the Gnex General board
http://forum.xda-developers.com/showthread.php?t=1338442
and one from the dev board
http://forum.xda-developers.com/showthread.php?t=1360413
Click to expand...
Click to collapse
Not really what Im talking about since its "it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash". I dont want to do this everytime I reboot plus it doesnt unlock the bootloader. Im wanting to know about a simple one step app that is permanent.
I think this is another case for a split forum. Unfortunatly the verizon nexus is different than the non-verizon.
I too am looking to root to get back my 3rd party wifi tether. as of now, I have found nothing that makes me think it is possible "today". Verizon has somehow locked the 3rd party apps. I am not a programer, or claim to be one; but I follow instructions well.
People need to say, I have verizon and I need this....XDA is world wide and people assume that when you are asking a question about a GN you are asking about the version they have and this forum is loaded with non-LTE information, with some LTE info hear and there.
If I find a LTE easy root I will gladly post it here
the insecure doesnt really matter. For what youre talking about it is a permanent flash you will not neet to re root everytime you turn on your phone. I superbooted yesterday. Im currently rooted and my phone has probably been restarted 15 times
It's pretty easy to manually root the LTE GN. The follow steps are for Windows.
Download this zipped package. It contains adb, fastboot, and Paul's unsecured boot.img that will install su and Superuser.apk for you.
Download ADB USB Drivers.
Step 1.) Unlock your bootloader. Put your phone into fastboot mode and install the ADB USB Drivers. Run fastboot-windows from the zipped package
Code:
fastboot-windows oem unlock
Step 2.) Put your phone back into fastboot mode if it reboots after unlocking. Then boot Paul's boot.img
Code:
fastboot-windows boot boot.img
Step 3.) Voila you're rooted... easy as pie.
ac7822 said:
the insecure doesnt really matter. For what youre talking about it is a permanent flash you will not neet to re root everytime you turn on your phone. I superbooted yesterday. Im currently rooted and my phone has probably been restarted 15 times
Click to expand...
Click to collapse
mayor bloom said:
I think this is another case for a split forum. Unfortunatly the verizon nexus is different than the non-verizon.
I too am looking to root to get back my 3rd party wifi tether. as of now, I have found nothing that makes me think it is possible "today". Verizon has somehow locked the 3rd party apps. I am not a programer, or claim to be one; but I follow instructions well.
People need to say, I have verizon and I need this....XDA is world wide and people assume that when you are asking a question about a GN you are asking about the version they have and this forum is loaded with non-LTE information, with some LTE info hear and there.
If I find a LTE easy root I will gladly post it here
Click to expand...
Click to collapse
That would be great if you find anything. As for saying that the superboot I guess ill give it a try. The post says that it will unroot (not sure how that works) on every reboot. Maybe im just not understanding it correctly
silow said:
It's pretty easy to manually root the LTE GN. The follow steps are for Windows.
Download this zipped package. It contains adb, fastboot, and Paul's unsecured boot.img that will install su and Superuser.apk for you.
Download ADB USB Drivers.
Step 1.) Unlock your bootloader. Put your phone into fastboot mode and install the ADB USB Drivers. Run fastboot-windows from the zipped package
Code:
fastboot-windows oem unlock
Step 2.) Put your phone back into fastboot mode if it reboots after unlocking. Then boot Paul's boot.img
Code:
fastboot-windows boot boot.img
Step 3.) Voila you're rooted... easy as pie.
Click to expand...
Click to collapse
Do you happen to have anything for us MAC users?? I'm really surprised I can't seem to find anything concrete for it.....
AlpineM3 said:
Do you happen to have anything for us MAC users?? I'm really surprised I can't seem to find anything concrete for it.....
Click to expand...
Click to collapse
I followed this tutorial to set up fastboot and adb on my mac:
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
Then you just need the boot.img linked above and use the same commands(except use the mac fastboot that you set up earlier)
There were no drivers needed to be installed.
jhuynh said:
I followed this tutorial to set up fastboot and adb on my mac:
http://blog.wapnet.nl/2011/05/setup-adb-and-fastboot-with-android-sdk-on-mac-osx/
Then you just need the boot.img linked above and use the same commands(except use the mac fastboot that you set up earlier)
There were no drivers needed to be installed.
Click to expand...
Click to collapse
What about to unlock the boot loader? Thanks btw
Sent from my Galaxy Nexus using xda premium
AlpineM3 said:
What about to unlock the boot loader? Thanks btw
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The commands are the exact same as the commands for windows except your fastboot probably isn't called fastboot-windows.
I found this guys and it seems to be the best and most straight forward guide to rooting the GN Ive found. Take a look http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/141563-guide-how-unlock-bootloader-root-verizon-galaxy-nexus.html
Also has a mac version along with video and other information.
AlpineM3 said:
What about to unlock the boot loader? Thanks btw
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Once you have fastboot loaded and the drivers, it's just a matter of booting to the bootloader and doing a fastboot OEM unlock. It should be no different.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
Kipphh said:
Does anyone know is there a one click root app out there for the GN yet? Will Unrevoked be doing a program for this? If not is there an word of one being done? It was made so easy for my DINC I would love to get my free tethering back.
Click to expand...
Click to collapse
OP:
No one will likely be doing a one-click system since this is a Nexus. Manual root is superior, and it is incredibly easy with some light knowledge of fastboot and adb. Honestly, I feel like if you cannot find your way around rooting a Nexus, perhaps you should not root it. An understanding of the system really comes in handy if you face issues.
Just unlock the bootloader using fastboot (there are instructions for this everywhere), then boot to an insecure boot.img of some sort (superboot is an option, I used koush's ClockworkMod image). Once you have this, you can use adb to push superuser to the system partition. If you overwrite the recovery, don't worry, because there is a script that will overwrite with the stock recovery after each boot.
If you want ClockworkMod permanently installed (as on your DINC, I presume) you will have to rename/remove the script. I have not done this, as I just re-flash ClockworkMod every time I alter something.
Hope that helps.
kekspernikai said:
Once you have fastboot loaded and the drivers, it's just a matter of booting to the bootloader and doing a fastboot OEM unlock. It should be no different.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
OP:
No one will likely be doing a one-click system since this is a Nexus. Manual root is superior, and it is incredibly easy with some light knowledge of fastboot and adb. Honestly, I feel like if you cannot find your way around rooting a Nexus, perhaps you should not root it. An understanding of the system really comes in handy if you face issues.
Just unlock the bootloader using fastboot (there are instructions for this everywhere), then boot to an insecure boot.img of some sort (superboot is an option, I used koush's ClockworkMod image). Once you have this, you can use adb to push superuser to the system partition. If you overwrite the recovery, don't worry, because there is a script that will overwrite with the stock recovery after each boot.
If you want ClockworkMod permanently installed (as on your DINC, I presume) you will have to rename/remove the script. I have not done this, as I just re-flash ClockworkMod every time I alter something.
Hope that helps.
Click to expand...
Click to collapse
Well Im happy to say your wrong. Here is a link to a one step root.
http://forums.androidcentral.com/ve...ks/147177-wugs-galaxy-nexus-root-toolkit.html
I can't seem to get this to work. I'm trying to unlock my phone using the nexus toolkit but when I put my phone into fastboot mode and click the unlock option on the toolkit I just get '< waiting for device >'. Every video I watch just shows them plugging the phone in and then having the program unlock it for them. It's not doing the same for me. Any suggestions?
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
063_XOBX said:
Stop using the toolkit. If something goes wrong you'll have no clue how to fix it. Read one of the "real" rooting guides that uses adb and fastboot and you'll save yourself a whole lot of headache down the road.
Click to expand...
Click to collapse
Every guide and video I find uses that method. Do you have a link to the other method?
http://forum.xda-developers.com/showthread.php?t=1529058
063_XOBX said:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
I still get the 'waiting for device' when I do it this way too. I have the most current samsung drivers. I also did everything to set up ADB.
uninstall the drivers and reinstall using the naked drivers.
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
figaro1418 said:
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
Click to expand...
Click to collapse
ok so what you'll need to do is make sure you have working ADB and Fastboot on you PC and make sure they can see the phone.
First you want to get:
http://forum.xda-developers.com/showthread.php?p=42407269
once you have this loaded on your pc we are going to want to make sure it works. for simplicity im going to this a certain way once you get the hang of paths and how this all works you can choose to do it a different way.
first make a folder on your c drive fastboot
once you have that folder place all the contents of ADB and Fastboot from the link above into the folder.
from windows open up a command prompt. (search CMD.exe)
once opened we want to get to that directory so we type this :
cd c:\
once that is done lets plug phone into the pc
run command
adb devices
(output should look something like this)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\>
this means no devices are seen by the pc. This is okay, for now.
with the phone you are going to need to enable develop mode. to do so go to
settings > about > software information > more > click the build number on the screen about 10 times in a row.
if done correctly it will call you a developer in a toast notification.
back all the way out to settings and go to the bottom. you should see developer options now. accept the warrning and get into the options. you will see the option for USB debugging, we want to have this enabled now.
once this is all done run this command from the CMD.exe you had to open above
adb kill-server
then run
adb devices
(output should look something like this)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
***device name here***
you are now talking to the phone via ADB congrats.
...next step
Perfect! I'm up and running in adb. Thanks for the great instructions Now what should I flash?
I'm running bonestock and it's amazing. Haven't found the need to change. It runs awesome, everything works, simply amazing.
Sent from my iPhone 5s using Tapatalk 4
figaro1418 said:
I've been scouring XDA, looking for a way to get S-Off on my Unlocked/S-ON VZW HTC ONE. I was one of the few who managed to unlock the phone early using HTC DEV. Now I'm stuck with the antiquated firmware, modems, kernels, etc. Can anyone help with this? I'm kind of a noob when it comes to Fastboot....so you may need to steer me toward a walk-through. Thanks in advance
Click to expand...
Click to collapse
Why do you say you're stuck with S-On? You can still S-Off, just so you know.
karn101 said:
Why do you say you're stuck with S-On? You can still S-Off, just so you know.
Click to expand...
Click to collapse
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Lock your bootloader?
Sent from my iPhone 5s using Tapatalk 4
Look at the HTC one toolkit by squabbi on the HTC one general forum ,it helped me get root back after taking the ota
Sent from my GT-P3110 using xda app-developers app
I was in the same situation as you in regard to HTC Dev unlocked on day one but still had S-On. What I did was flashed the Odexed Full ROM version: 1.10.605.10 from santod040 (http://forum.xda-developers.com/showthread.php?t=2485319) and then flashed the stock boot.img and signed-recovery.
However, after doing that I had one hell of a time with rumrunner, even though I was using the download for 1.10.605.10. It turns out, even though I was on the stock ROM I flashed above with the correct version my OS was showing 1.10.605.02 because I had one of the weird phones that shipped with that version instead of .08. Luckily for me since I had the stock boot.img and signed-recovery, I just did the OTA update to 1.10.605.15 and then used rumrunner for that version.
Also, no you don't need to lock your bootloader before doing that. I didn't.
bloodiedwraith said:
I was in the same situation as you in regard to HTC Dev unlocked on day one but still had S-On. What I did was flashed the Odexed Full ROM version: 1.10.605.10 from santod040 (http://forum.xda-developers.com/showthread.php?t=2485319) and then flashed the stock boot.img and signed-recovery.
However, after doing that I had one hell of a time with rumrunner, even though I was using the download for 1.10.605.10. It turns out, even though I was on the stock ROM I flashed above with the correct version my OS was showing 1.10.605.02 because I had one of the weird phones that shipped with that version instead of .08. Luckily for me since I had the stock boot.img and signed-recovery, I just did the OTA update to 1.10.605.15 and then used rumrunner for that version.
Also, no you don't need to lock your bootloader before doing that. I didn't.
Click to expand...
Click to collapse
synisterwolf said:
Lock your bootloader?
Sent from my iPhone 5s using Tapatalk 4
Click to expand...
Click to collapse
figaro1418 said:
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Click to expand...
Click to collapse
I had mine unlocked on day one as well. When RomRunner came out, I was able to run it just fine (unlocked).
Are you on a stock ROM? You can always make a backup, move those files to your computer, RUU to be completely stock, and then run RomRunner.
Once that's done, just bring over your backup and restore it in recovery.
figaro1418 said:
With Rumrunner? It won't work on my unlocked bootloader! I have ADB up and running on my computer, but my computer won't recognize the device in fastboot mode. I'm open to any ideas or advice. Again, I'm kind of a noob to HTC. I used to work with Samsung Phones. I've only recently learned how to work with HTC.
Click to expand...
Click to collapse
It won't recognize it because that's what fastboot is for in the folder your adb is in. Don't type adb devices. Type fastboot devices. Then you'll see your mistake
Sent from my One using Tapatalk
karn101 said:
I had mine unlocked on day one as well. When RomRunner came out, I was able to run it just fine (unlocked).
Are you on a stock ROM? You can always make a backup, move those files to your computer, RUU to be completely stock, and then run RomRunner.
Once that's done, just bring over your backup and restore it in recovery.
Click to expand...
Click to collapse
He can't run the RUU because you have to be S-OFF to do that, hence why I put what I needed to do since I was in the same situation.
bloodiedwraith said:
He can't run the RUU because you have to be S-OFF to do that, hence why I put what I needed to do since I was in the same situation.
Click to expand...
Click to collapse
You don't need to be S-Off to do it. The signed RUUs are up.
Here's a link.
http://flyhalf205.com/?dir=RUU
Regardless, flashing a stock ROM is most likely the easiest route to go. I was just throwing up an alternative.
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
cosmickiller said:
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
Click to expand...
Click to collapse
i can help you over teamviewer just pm me.
cosmickiller said:
Hi All
having a problem here, windows 7 detect my phone, but in Hansoon 2000 and launch the cmd Getvar All, cmd unable to detect my phone
FYI my phone was already rooted and s-off, i totally forget how i did it
Reason to use Hansoon 2000 is because i had downloaded the official Lollipop update (1.44GB Asia) but have no means and ways to flash it even with twrp build in.
There is not supersu and does not seems root after i have **** up the OS.
Hope anyone here can guide me step by step, i getting confuse after looking for information on google and on XDA forums
Regards
Andy
Click to expand...
Click to collapse
You shouldn't use toolkits. Are you s-off?
Yes S-off
xunholyx said:
You shouldn't use toolkits.
Click to expand...
Click to collapse
Agreed. Why use a toolkit for what is accomplished with a single adb command? Toolkit just adds unnecessary complexity, and another point of potential failure.
Is the phone in recovery or booted into OS? getvar is an adb command, and adb only works under those conditions. Also, adb needs to be activated in the phone's settings.
hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:
Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
About phone ????
mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD
Lol love rotation, here
mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you
@mikmikush You're welcome, my pleasure!
Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:
"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!