Database Users

Trying to root again after 4.2.1 update

I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.

Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.

xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!

Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.

Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)

xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.

Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!

Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.

kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.

[Q] Need Help - GooManager Error and other question's

Hey Guys,
I recently bought a Nexus 7 from ebay. The guy I bought it from had put Paranoid Android 3 on it. I am cimplete noob and do not know how to root or flash.
I just did something which I dont know how to correct.
GooManager kept telling me there was an update which when tapped on, would bring me to the .zip file i was supposed to dl.
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh

Josh5321 said:
I recently went into GooManager and denied permissions and then quickly re enabled them in supersu but now when ever I get the update prompt it brings me to the GooManager home screen with a message that says "GooManager has been granted super user permissions for an inactive shell"
What did I do wrong and do you have any idea how I can:
1. Fix this error
2. Go about updating the Nexus 7 to the newest version of paranoid
3. Can Someone link me to the full instructions on how to get the newest paranoid 3 on my nexus 4?
Thanks a ton
Josh
Click to expand...
Click to collapse
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.

Pirateghost said:
1. there is no error
2. launch goomanager, hit check for updates, when it alerts you, let it down load and flash
3. go to the nexus 4 forum, there is a thread dedicated to Paranoid Android there.
Click to expand...
Click to collapse
but in the past when I would click on the update notification it brought me straight to the download file. now it just brings me to the goomanager main screen.

reboot the device and try again. or you can go in and clear out all data and cache for goomanager in your settings/apps/goomanager page

I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.

Josh5321 said:
I did a reboot and then cleared data and cashe and the notification just vanishes when tapped. Not sure how this happened. Can anyone link me to the latest PA 3 link to dl. ill just do it manually and maybe it will correct itself in the future.
Click to expand...
Click to collapse
open the NEXUS 7 ORIGINAL DEVELOPMENT FORUMS and download yourself, or open GOOMANAGER and BROWSE COMPATIBLE ROMS...

I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.

TyneBridges said:
I have an associated question: does GooManager require the separate SuperSU app to be installed?
My device (a Motorola Xoom) is supposedly rooted, but SuperSU fails to install and GooManager can't get root permission. It's frustratingly difficult to tell (on this device at least) if there's proper root access - one checker app tells me the tablet is rooted, others say it isn't.
Click to expand...
Click to collapse
Hi, TyneBridges...
Well, I've never used GooManager myself... but the apps description on PlayStore certainly suggests you do need to be rooted to be use it.
You're a long way from the Motorola Xoom forums (wherever they may be)... but try, from PlayStore, running some app that requires root... like Titanium backup, or perhaps better, Android Terminal emulator (by Jack Palevich)... run it, and type...
Code:
su
If you're NOT rooted, you should see something like this...
Code:
$su
su: not found
$
-------------------------------------------------------
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
If you have some root SU binary installed, then Chainfire's SuperSU app should detect it... and either replace it, or update it.
Anyway... just some thoughts.
I really have no idea what other technical issues/problems there might be rooting a Motorola Xoom. And so you should hunt out the XDA forum for your specific device for more information... I'd be very surprised if there wasn't one.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, TyneBridges...
...
One last thought that's just occurred to me.... you may actually already BE rooted (ie., have the SU binary installed in /system/bin or /system/xbin or wherever)... but you may be just missing the SuperSU app itself (and which 'manages' the apps you grant root to). This is has happened to me, several times, when re-rooting... for reasons which remain a mystery.
But you can download it from PlayStore, here...
...
Click to expand...
Click to collapse
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John

TyneBridges said:
Thanks for the reply. You imply that the SuperSU app *is* needed but that's the one that I've tried, and failed, to install. It just keeps telling me that the binary needs to be updated then, when I accept that, a pause and "Installing" followed by "Installation failed". I've tried the terminal program you suggest
su
Gives:
Permission denied
...so it appears that the tablet is not correctly rooted, but I don't know what the problem is.
--
John
Click to expand...
Click to collapse
Hi, again John...
I'm afraid I'm a bit out of my depth with the Motorola Xoom... I know absolutely nothing about it. Sorry.
Here's where you should really be asking...
http://forum.xda-developers.com/motorola-xoom
...if anybody can solve your problem, then that's where you're likely to find them.
----------------------------------------------
If you can install a Custom Recovery like TWRP or CWM on your device, then it **SHOULD** (theoretically) just be a case of flashing Chainfire's UPDATE-SuperSU-v1.94, via that Custom Recovery.
On Nexus devices, you use FASTBOOT to flash a Custom Recovery.... on Samsung Devices, you need something called Odin to do likewise.
Once you have a Custom Recovery installed, rooting should be a piece of cake.
Problem is, I have absolutely no idea how to get such a Custom Recovery installed on a Xoom.
Do a bit of research... XDA is a vast repository of considerably more knowledgeable people than myself... and somebody is likely to know something.
Good luck.
Rgrds,
Ged.

[Q] Stuck at "X" Nexus 7 2013

First I have been to and searched every post and site I can find to turn this thing around, with no success. Sent several emails.
Took a rooted New Nexus 7 that had been restored back because it froze/did not respond. Got a new N7, unlocked bootloader and installed TWRP using Terminal (Mac) booted into recovery (TWRP) it said you are not rooted, install SU by swiping below. I swiped and tried to reboot and it stops at X. I have wiped, reinstalled TWRP and used a One Click Toolkit to Root. no success. Not really sure what I did wrong.....given I have always trusted TWRP.
Anyway... have unlocked bootloader, TWRP installed and cannot get Android File Transfer to recognize device. Welcome help or suggestions.
Thank you in advance.
David

Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.

natezire71 said:
Same thing happened to me. Don't listen to TWRP about SU. You'll need to do it manually for it to be successful. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2381582. This won't relock your bootloader. You just need to root it by flashing the SU zip found on one if the "How to root" threads.
Click to expand...
Click to collapse
Yeah, youre correct, you have to manually flash twrp. I would suggest running the utility to make youre device boot again, then make sure you have the LATEST twrp, then reboot and flash COMPATIBLE SU and you should be golden. Im not sure about macs though but you should deff be goin the right way.

Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David

dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2395003
I don't have a Mac, so I don't know if this will help. Only thing I could find.

dschaap said:
Thank you, I used that site the last time I got into trouble. Do you or anyone know of a Mac site that will get me out of this rut. I won't have access to a PC for a few days and am anxious to set this tablet up.
Thank you for response,
David
Click to expand...
Click to collapse
If you were able to install using a Mac, then you should have no troubles setting things up again. Avoid toolkits if you can, especially during the early days where things are buggy.
If you put your tablet into fastboot though, you can get started by going ahead and running fastboot -w and then flashing the stock recovery images back on. Sure, you won't have root, but I've found that 1) root doesn't take super nicely unless you're already signed into the tablet anyway, and 2) regardless of 1), once your bootloader is unlocked you might as well get set up and then root afterwards.

Mine did the same thing. What I did to fix was:
1. Go into recovery and format data in the wipe menu.
2. Then factory reset.
3. Restart os.
This was posted by decksy post #11 in tutorial for unlock, recovery, and root thread so if it works thank him.
Sent from my Nexus 7 using xda app-developers app

Can't boot to Download Mode

Yes, I've searched and worked for hours on this. I keep hitting a brick wall.
D800, rooted, TWRP, KK rom.
Even though I didn't ask for it somehow the OTA must have installed because my phone rebooted and then was stuck in recovery boot-loops. I can't boot into download mode which means I can't restore to stock or do anything. Do I have any options or is it time to head to the ATT store and try a warranty replacement?
Thanks in advance.

kimtyson said:
Yes, I've searched and worked for hours on this. I keep hitting a brick wall.
D800, rooted, TWRP, KK rom.
Even though I didn't ask for it somehow the OTA must have installed because my phone rebooted and then was stuck in recovery boot-loops. I can't boot into download mode which means I can't restore to stock or do anything. Do I have any options or is it time to head to the ATT store and try a warranty replacement?
Thanks in advance.
Click to expand...
Click to collapse
Well then if it's not booting into custom recovery/download mode then there is no way for att to see it was rooted so as long as you stick to the ota broke your phone it shouldn't be a problem
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
Well then if it's not booting into custom recovery/download mode then there is no way for att to see it was rooted so as long as you stick to the ota broke your phone it shouldn't be a problem
Click to expand...
Click to collapse
Thanks for your reply. Actually, it keeps booting into TWRP. That's part of my issue, and described in my post. So, yes, they will sort of see that it isn't stock.

kimtyson said:
Thanks for your reply. Actually, it keeps booting into TWRP. That's part of my issue, and described in my post. So, yes, they will sort of see that it isn't stock.
Click to expand...
Click to collapse
well if an ota did this then do you have adb access? if not then you can use the twrp terminal and the commands from this thread http://forum.xda-developers.com/showthread.php?t=2451696 should help you to boot, I should know I just did it not too long ago since att forced my phone to update(mine should be the last post their)

XxZombiePikachu said:
well if an ota did this then do you have adb access? if not then you can use the twrp terminal and the commands from this thread http://forum.xda-developers.com/showthread.php?t=2451696 should help you to boot, I should know I just did it not too long ago since att forced my phone to update(mine should be the last post their)
Click to expand...
Click to collapse
Wow. I really appreciate your assistance.
I tried to run ADB Shell and get error:closed.
I don't know how to run from the command prompt. There is no keyboard.

kimtyson said:
Wow. I really appreciate your assistance.
I tried to run ADB Shell and get error:closed.
I don't know how to run from the command prompt. There is no keyboard.
Click to expand...
Click to collapse
when you are in you open your cmd window where you have adb set up run the command adb devices
also where did you get your adb from because I have mines setup from the android sdk

XxZombiePikachu said:
when you are in you open your cmd window where you have adb set up run the command adb devices
also where did you get your adb from because I have mines setup from the android sdk
Click to expand...
Click to collapse
I have downloaded and tried several versions of ADB, including the SDK and after updating the SDK, Still no use.
Can you tell me more on how to use the TWRP Terminal option. I have TWRP 2.7.0.0. Thanks!

kimtyson said:
I have downloaded and tried several versions of ADB, including the SDK and after updating the SDK, Still no use.
Can you tell me more on how to use the TWRP Terminal option. I have TWRP 2.7.0.0. Thanks!
Click to expand...
Click to collapse
well when you click on the terminal inside twrp it should have the blank space to type on and the keyboard should pop up to type with, which is something I find odd that it doesn't on yours

[HowTo] Encrypt/Decrypt phone when rooted & Xposed

I would like to share with you how to encrypt/decrypt when you are rooted. Restart one time the phone after you have installed the firmware and rooted.
Done with H815E two times.
I - Install PKILL tool
Install from the playstore Busybox Installer and install busybox. It will install on your device a lot of command line tools. (you need to be rooted)
II - Install Terminall
From the playstore install Terminal .
III - prerequisites
- Plug-in the charger on your phone
- Add unlock pin to your phone before encrypting
IV - Encrypting
Open Terminal and write
Code:
su
The carret change from $ to #
Code:
pkill -KILL daemonsu
The carret change from # to $
Just after that go settings and security then encrypt / decrypt device (don't wait)
I hope it will help you !
Have fun !

Didn't work on Verizon G4.
Followed all of the above steps on a freshly rooted and wiped Verizon G4 without success. Just sits on red Verizon boot animation endlessly. Really would like to have root and encryption.

keeperoffrisco said:
Followed all of the above steps on a freshly rooted and wiped Verizon G4 without success. Just sits on red Verizon boot animation endlessly. Really would like to have root and encryption.
Click to expand...
Click to collapse
Sorry for that, do you have a rebot your phone after having install root ? You need to do it one time.

I just disabled the SuperSU app and it worked.

Thanks! This works for my rooted 818P V110f! Yeah!!!

Nice! This is quicker and less painful then my method! I will try and provide feedback! Thank you sir.
Send from outer space using telepathy
---------- Post added at 12:21 PM ---------- Previous post was at 12:16 PM ----------
One question remains: Why on earth does LG sends it device into eternal "do nothing loop" when trying to encrypt a rooted device. Why o why? Must be the same evil bastard that implemented the "battery full" sound. He/she wants the LG customers to suffer!
Send from outer space using telepathy

My experience has been the same as keeperoffrisco's. And I, too, have the Verizon variant of the LG G4.
The obvious problem with this method and the Verizon model is that the phone restarts immediately after initiating the encryption process. For this reason, I don't see how killing the daemonsu binary will have any effect.
As soon as the encryption process is initiated, the screen flashes briefly to the green "Android" guy on a white background, and then switches to the Verizon boot screen, and then hangs there forever (until I pull the battery).
I sympathize with @fpsq: why the **** does the phone sit in this state once it's rooted? How is the bootloader establishing that the phone is rooted?
I'm really eager to find a method for encrypting a rooted Verizon LG G4!

You can. My rooted + encrypted LG G4 is right beside me. Have a look at these links for instructions:
http://forum.xda-developers.com/showpost.php?p=62457999&postcount=1919
http://forum.xda-developers.com/showpost.php?p=62156629&postcount=1468
Basically it is:
"You should NOT root via the method here described. UNLOCK your bootloader, encypt, start TWRP. Get password enter screen. Ignore that screen TWRP does not work properly. Tell TWRP to reboot system. Swipe to "yes install SU" Back in GUI install rest for SU from Play Store. Not to hard once you done it. "
To be able to decrypt once you are already rooted you need to uninstall root, then supersu + busybox and the like and then decrypt.
If this does not work you need to convince your device you never have been rooted (RCT bypass). The instructions for the LG G2 work just fine and can be found here:
http://forum.xda-developers.com/g2-mini/general/lg-rct-bypass-t2818441
Sometimes it is usefull that LG is only updateing software if it really really has to. So a lot of old and unchanged code in the excuse that servers LG as an Android skin. :cyclops:

fpsq said:
You can. My rooted + encrypted LG G4 is right beside me. Watch here for some instructions:
http://forum.xda-developers.com/showpost.php?p=62457999&postcount=1919
http://forum.xda-developers.com/showpost.php?p=62156629&postcount=1468
Basically it is:
"You should NOT root via the method here described. UNLOCK your bootloader, encypt, start TWRP. Get password enter screen. Ignore that screen TWRP does not work properly. Tell TWRP to reboot system. Swipe to "yes install SU" Back in GUI install rest for SU from Play Store. Not to hard once you done it. "
To be able to decrypt once you are already rooted you need to uninstall root, then supersu + busybox and the like and then decrypt.
If this does not work you need to convince your device you never have been rooted (RCT bypass). The instructions for the LG G2 work just fine and can be found here:
http://forum.xda-developers.com/g2-mini/general/lg-rct-bypass-t2818441
Sometimes it is usefull that LG is only updateing software if it really really has to. So a lot of old and unchanged code in the excuse that servers LG as an Android skin. :cyclops:
Click to expand...
Click to collapse
Thanks a lot for the reply to my question! I really appreciate it.
My understanding is that LG provides a method for unlocking the bootloader only on the H815 model. I have the VS986.
Am I missing something? Thanks for any clarification you may be able to provide!

DrRichardQuack said:
Thanks a lot for the reply to my question! I really appreciate it.
My understanding is that LG provides a method for unlocking the bootloader only on the H815 model. I have the VS986.
Am I missing something? Thanks for any clarification you may be able to provide!
Click to expand...
Click to collapse
Yes, right now LG provides a bootloader unlock only for the European variants of the H815 - so no Singapore or US variants and no Verizon, Dual Sim variants or whatsoever etc.
If you didn't take an OTA you might have a chance to use the unofficial bootloader unlock that is due to come out with the official release of the LG V10 on the 20th of October.
Greetings
Medzinmann

Do NOT buy not unlockable Phones. Buy the LG G4 H815. How on earth should manufactures ever learn if you keep throwing money at them? By the way, almost all carriers where infiltrated by the NSA. No one received a praise from the NSA like Verizon did for "collaboration". Verizon is the cheap hooker that gives ****s away for free. While it is you being ****ed. If you still use their services, you don't seem to mind, do you?

Works this method on Marshmallow (with rooted Kernel) too? After Encryption root becomes active again? Thanks.

S6 G920V
Fresh recovery of stock 5.0.2, then PingPongRoot. Followed your instructions and it worked perfectly. Thanks.

micheled said:
Works this method on Marshmallow (with rooted Kernel) too? After Encryption root becomes active again? Thanks.
Click to expand...
Click to collapse
For me it does not, sadly.
Has anyone an idea?
I've Systemless root, kill the deamon but the encryption process stills hangs on reboot.
Thank you in advance!

Cliff_T said:
For me it does not, sadly.
Has anyone an idea?
I've Systemless root, kill the deamon but the encryption process stills hangs on reboot.
Thank you in advance!
Click to expand...
Click to collapse
Ok, after some hours of trying, testing and failing I've found a solution.
Basically you have to install twrp first, encrypt the phone and then root it with the systemless supersu.
In my case, twrp still fails to decrypt the /data partition, even i've installed it as the phone was unencrypted. So I've to install the Super-su zip from the external sd card and then it was no problem .
The long version of the how to: https://www.0xcaffee.de/de/item/11-...-the-lg-g4-and-encrypt-the-device-and-root-it