Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
darkghost568 said:
Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
Click to expand...
Click to collapse
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
OneDon said:
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
Click to expand...
Click to collapse
Thanks!
deleted
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
DrPhant0m said:
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
Click to expand...
Click to collapse
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
McNutnut said:
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
Click to expand...
Click to collapse
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
DrPhant0m said:
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
Click to expand...
Click to collapse
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
McNutnut said:
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
Click to expand...
Click to collapse
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
DrPhant0m said:
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
Click to expand...
Click to collapse
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
McNutnut said:
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
Click to expand...
Click to collapse
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
DrPhant0m said:
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
Click to expand...
Click to collapse
You're welcome! Sorry it didn't work. I do know it takes a few minutes for it to boot up the first time, but I imagine you waited pretty long. I have heard of phones taking 10-15 minutes to boot up after flashing.
I did add US99610h stock firmware to my thread at https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573 if you want to return to the newest stock firmware of the US996.
I hope you are able to get Magisk installed as it's nice to get past SafetyNet. Good luck!
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Nope. Cant with custom recovery..
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Click to expand...
Click to collapse
Your phone will boot loop if you don't go back to stock recovery first. I tried just to see what would happen and that's what happened. People who tried to flash it with Flashify reported no success.
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery. Thanks
Click to expand...
Click to collapse
Stock ROM? Important information you omitted. From a guy who always runs the latest stock ROM rooted and custom recovery here's how you do it: You do not have to remove them first, and although they (SU & kernel) will be overwritten with the new boot.img, it is very easy and straightforward. You need the TWRP flashable (beta) OTA zip file, in the OP here. Put the latest SU and your custom kernel on the device root, or wherever. (should already be there) and then reboot to TWRP recovery. Select "Install" and then select the OTA you downloaded above, and tap "Add more zips". Next you want to add the latest SU zip (2.79 SR3) and last add your kernel. Mine is EX. Once you have queued all 3 zips, in less than a minute you will be back up and running 7.1.2 , rooted and with kernel. Even if you flash each file individually you will still be ok. (OTA, SU, Kernel). See the same thread further down... Credit for the TWRP flashable OTA goes to @Displax.
Hello! Today I woke up with the notification of the new nougat update, Exciting! But I guess I have several problems: first of all, my phone is rooted, will I lose root acces? Also, I have TWRP installed. Yesterday I tried installing a security update on a device with TWRP and there was no way, will this happen to me? Another problem is my kernel, ElementalX. I've installed it since I had screen burn, but I don't really care about performing a fix everyday, but I know this kernel will prevent Nougat to install correctly. I do have a System Backup from when the kernel was not installed, and I read you can install 'just the boot.img' from TWRP restoring options but there's no "boot.img" file on my backup folder. I would like to add that I'm running on Marshmallow 6.0.1, rooted with SuperSU, using Xposed. The ElementalX kernel ver. is 3.10.84-ElementalX-G4-0.07 and the TWRP ver. is twrp-3.0.2-0-athene. Thank you all in advance!
polykiwi316 said:
Hello! Today I woke up with the notification of the new nougat update, Exciting! But I guess I have several problems: first of all, my phone is rooted, will I lose root acces? Also, I have TWRP installed. Yesterday I tried installing a security update on a device with TWRP and there was no way, will this happen to me? Another problem is my kernel, ElementalX. I've installed it since I had screen burn, but I don't really care about performing a fix everyday, but I know this kernel will prevent Nougat to install correctly. I do have a System Backup from when the kernel was not installed, and I read you can install 'just the boot.img' from TWRP restoring options but there's no "boot.img" file on my backup folder. I would like to add that I'm running on Marshmallow 6.0.1, rooted with SuperSU, using Xposed. The ElementalX kernel ver. is 3.10.84-ElementalX-G4-0.07 and the TWRP ver. is twrp-3.0.2-0-athene. Thank you all in advance!
Click to expand...
Click to collapse
You must return to stock recovery and stock kernel in order to flash the OTA. Yes you will lose root and will have to redo it once you are updated. The procedure for rooting in Nougat is different than on Marshmallow. There are numerous posts in this forum on the exact steps you need to take to accomplish all of this this safely. Take the time to read and research before you try anything. Don't just expect somebody to spoon feed you the info.
pastorbob62 said:
You must return to stock recovery and stock kernel in order to flash the OTA. Yes you will lose root and will have to redo it once you are updated. The procedure for rooting in Nougat is different than on Marshmallow. There are numerous posts in this forum on the exact steps you need to take to accomplish all of this this safely. Take the time to read and research before you try anything. Don't just expect somebody to spoon feed you the info.
Click to expand...
Click to collapse
Thanks! I'm installing it tomorrow!
Hey. So this might sound super noobish, but I rooted my S7 Edge and downloaded Lucky Patcher etc etc. Turns out Lucky Patcher isn't exactly working on Nougat for the time being (not sure of reason) but there's a fix listed on here that involves flashing a kernel which supposedly fixes Lucky Patcher somehow. So I went ahead and flashed the kernel from TWRP and it seemed like everything was cool but when my phone rebooted it lost its root status (reliably confirmed by root checker app).
Is there some order that I am supposed to do this in? Was I supposed to flash the kernel via odin instead of TWRP or have I made an error somewhere. I used the method of flashing no-verity-opt-encrypt and then SuperSU via TWRP in order to root my device, if that makes any difference. I feel like I'm missing an easy step here and I'd appreciate it if someone could sort me out.
Cheers
Ozzymandais said:
Hey. So this might sound super noobish, but I rooted my S7 Edge and downloaded Lucky Patcher etc etc. Turns out Lucky Patcher isn't exactly working on Nougat for the time being (not sure of reason) but there's a fix listed on here that involves flashing a kernel which supposedly fixes Lucky Patcher somehow. So I went ahead and flashed the kernel from TWRP and it seemed like everything was cool but when my phone rebooted it lost its root status (reliably confirmed by root checker app).
Is there some order that I am supposed to do this in? Was I supposed to flash the kernel via odin instead of TWRP or have I made an error somewhere. I used the method of flashing no-verity-opt-encrypt and then SuperSU via TWRP in order to root my device, if that makes any difference. I feel like I'm missing an easy step here and I'd appreciate it if someone could sort me out.
Cheers
Click to expand...
Click to collapse
Flashing a custom or stock kernel removes root. You should flash in twrp your root method zip file right after flashing the kernel and then reboot the system.
Due to the use of encryption by the official MIUI ROM we cannot use a custom recovery. Only the MIUI stock recovery knows the encryption password so only it can install OTA updates. If you are also having issues related to the fingerprint scanner data disappearing after each reboot, they will be fix by this.
So the actual solution... This might not be obvious to everyone but due the encryption password being unknown we actually need to keep the stock recovery. That's it. Just install the stock recovery. Now you might ask how you flash things like Magisk since the stock recovery doesn't support that kind of thing. It's simple too, just you a ciustom recovery. You don't actually need to have a recovery flashed to use it, you can just boot a image via fastboot(1). This is a bit annoying but still way less annoying than not being able to install updated or the fingerprint data resetting every reboot.
(1) Boot to custom recovery without replacing the stock recovery
Code:
fastboot boot custom-recovery.img
hmmm, I am not really sure what you wanted to explain, however, not only the miui stock recovery knows to handle encryption, as the ATG's twrp with certain version does it fine, as well.
They do but only the stock one knows the password used to encrypt MIUI.
PBRP handles OTA updates without issue. Have had two updates since installing it and haven't had any problems.