Database Users

How to root LG D802 with 220H firmware ?

Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !

Cst79 said:
Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !
Click to expand...
Click to collapse
Towelroot

azher98 said:
Towelroot
Click to expand...
Click to collapse
Doesn't work, it sais "phone is not supported". I understand that towelroot exploits a Linux kernel loophole that was patched around June 3.

Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906

6ril1 said:
Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).

Cst79 said:
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).
Click to expand...
Click to collapse
It's very simple:
1) download ioroot:
http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip
2) extract datroot.zip from the archive just downloaded (from bts folder)
3) on the G2 enable dev option (Settings - About Phone. Then go to the bottom and you should see Build Number. This needs to be pressed a total of seven times. You should get a message at the fourth press. On the seventh, you'll get another message saying that Developer Options are unlocked.)
4) enable usb debug on the phone (Development Settings Enable USB Debugging)
5) plug the phone in usb with the pc and accept yhe RSA Fingerprint message.
6) reboot your phone in recovery with adb cmd (tape cmd: adb reboot recovery)
7) choose 'apply update from adb' in the phone recovery menu (navigate with vol down and valid with power)
8) in the pc tape cmd: adb sideload c:\datroot.zip
9) reboot et enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

6ril1 said:
It's very simple:
Click to expand...
Click to collapse
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !

Cst79 said:
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !
Click to expand...
Click to collapse
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.

6ril1 said:
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.
Click to expand...
Click to collapse
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !

Cst79 said:
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !
Click to expand...
Click to collapse
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.

6ril1 said:
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.
Click to expand...
Click to collapse
Hello,
No, my questions are not generic, I want to find out:
- How do I install CyanogenMod 12 after I root the phone.
- What are the steps to revert to 100% stock after I root the phone and install CM12; Can I just use the LG flash tool and flash the kdz with no complains from the LG software if I have CM12 installed ?
Thanks.

Do you loss data with this metod?
Thanks

D800 - I just can't get CloudyG2 working no matter what I do...

I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
Some of you sent me a PM asking for the install instructions on D800 and this is how you install CloudyG2 3.0:
Downloads:
1. Download CloudyG2 3.0 - https://www.androidfilehost.com/?fid=95897840722646001
2. Download Patch - https://mega.co.nz/#!sVY0mRTb!qn7S9B...3m_QpMQkgzunn0
3. Download Signal Patch - https://dl.dropboxusercontent.com/u/...l_Variants.zip
4. Download LP Baseband - http://blastagator.ddns.net/modem.php - d800-30f-modem-blastagator-signed.zip
5. Download KK Bootstack - http://blastagator.ddns.net/bootloader.php - bootstack-d800-KK_20c-blastagator-signed.zip
6. Optional: Download JB Bootstack in case if you want to revert the installation process and go back to your current ROM - http://blastagator.ddns.net/bootloader.php - bootstack-d800-JB_10d-blastagator-signed.zip
Flashing Process:
1. Backup the existing ROM (including EFS, Modem, etc.) in TWRP - very important and copy it over to the computer, just in case!
2. Wipe System + Data + Cache + Dalvik Cache - Do NOT select internal storage as it contains all your downloaded files + backups!
3. Flash KK Bootstack (downloaded from Step 5)
4. Flash LP Baseband (downloaded from Step 4)
5. Flash CloudyG2 3.0 (downloaded from Step 1) - Leave the default in Aroma when you have to pick the variant. Do NOT reboot the device as the patch installation (next Step) is very important.
6. Flash Patch (dowloaded from Step 2) - Select your variant.
7. Flash Signal Patch (downloaded from Step 3)
8. Reboot
Enjoy!
Click to expand...
Click to collapse
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions didn't seem to work so I Googled for them, maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!

level5music said:
I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions were dead mega.co.nz links so maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!
Click to expand...
Click to collapse
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..

raptorddd said:
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..
Click to expand...
Click to collapse
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?

level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
no not really, but i do know that we had to use 2871 cause newer version were wiping f2fs, so now latest build its working but i dont think it has something to do .... am sorry i just got mine like a week ago and mine was in lollipop.. so i know nothing about coming from other version of android. dont even know whatsa tot flash.. i still need to learn alot..
check here and see if you can find a way to fix this good luck
http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178

level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
I had the exact problem happen to me ....... I got the black screen of death .... phone wouldnt boot ....... and when i used the kk bootloader i would lose recovery ..... I was coming from kk to CloudyG2 ....
This is how i solved.
1. Flashed back to stock, stumproot to root Autorec v1 for bootloader
2. used Flashify to upgrade to 2.8.7.1 ( its now 2.8.7.3)
3. Downloaded n used bumpted LP bootstack and flashed blastagator stripped rom (its in flashable zip and installs everythin including modem .... patches etc EVERYTHING) http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195
4. Downloaded kk bootstack , CloudyG2 3.3 and clean flashed in recovery
I have been enjoying Cloudy ever since ...... D800

Thanks all, got it running! Cloudyfa has done some absolutely brilliant work here with this ROM, as well as xdabbeb with the advanced camera driver and xCam. I'm usually a vanilla-or-nothing guy with my Android ROMs but this one is quick and power efficient. The KitKat ROM that shipped with the phone was super bloated and gross, but I'll admit LG UX 4.0 isn't really that offensive, plus I like the goodies like Multi-Window and QuickRemote. Once I disabled/hid some of the remaining LG bloat, it's surprisingly pleasant and not really that far from AOSP aesthetically. Again, cheers to those who provided the assist on this one for me!
... now my only question is, should I try CloudyG3?

twrp-2.8.7.2-angler.img overwritten by stock recovery

So I have flashed TWRP 2.8.7.2 on my 6P, and was able to go into it. However, if I shut the phone down then boot into the bootloader, arrow down to Recovery Mode and press the power button, I get the android lying on his back with a red triangle with an exclamation mark above his open front, with "No command." written below it. I can hold down the power button and press the volume up button to get to stock android recovery, then reboot to bootloader just fine.
If I connect the phone to my pc and flash TWRP again, I can get into TWRP, however, next time I reboot, it is gone. I read on TWRP's Nexus 6P page the following:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Click to expand...
Click to collapse
So, I flashed TWRP, then entered fastboot reboot in the cmd window, it rebooted to the bootloader. Then I pressed the volume down button to Recovery mode, pressed power and it went into TWRP. In TWRP I went to Reboot and selected Power Off. I booted it back into the bootloader, selected Recovery mode and it went back to the android with the red triangle and "No command."
I'm at a complete loss. I've read through hundreds of posts here on xda, with one person having the same issue, but fixed it by re-downloading the TWRP .img file and flashing it, Which I've tried... I even flashed the 2.8.7.1 version and had the same problem, then again with the 2.8.7.2 version and still same problem. I've searched for a more detailed explanation of "the proper key combo to enter recovery" and couldn't find anything.
I would really appreciate any help you guys can give me. The biggest thing I have come to understand after reading hundreds (literally) of posts, this community of people are really helpful.
My Android version is 6.0 and my Build number: is MDB08L.
Thanks for any help you guys can give.

this happened to me as well. i fixed it but i don't remember how. I think you need to flash twrp again and there is a tick box or setting that you need to check that will prevent the stock recovery from overwriting twrp. sorry i couldn't be more help.

jrc27 said:
this happened to me as well. i fixed it but i don't remember how. I think you need to flash twrp again and there is a tick box or setting that you need to check that will prevent the stock recovery from overwriting twrp. sorry i couldn't be more help.
Click to expand...
Click to collapse
Thanks for the quick reply. I just flashed TWRP again, entered it through recovery mode, but do not see a tick box or setting... I've looked through the options so many times that I may just be overlooking it by now. Any idea what the tick box or setting might have been labeled as?

I'm having the same issue and cannot seem to find a solution as well. I feel like I'm missing something very obvious...

You will need root explorer and go to the system folder. Then from there you need to rename this file to recovery-from-boot.bak or just delete.
Sent from my Nexus 6P using Tapatalk

I recently experienced the same issue with my Nexus 5 (as I was upgrading it from Kitkat to Marshmallow). I finally solved it by flashing TWRP via Flashify (https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=fr)
So, here are the steps I used : flashed TWRP via bootloader (via PC with USB cable) and boot straight into recovery... flash my rom (with root included) then reboot normally. Then downloaded flashify from the playstore, then flashed TWRP again using flashify... Done, never had this issue since then... I can now reboot into TWRP without problem from the rom, the bootloader or TWRP itself
I don't have a Nexus 6P yet (should do next week ), but it could be worth testing Flashify

Thanks for the suggestions guys.
I'm sorry, I should have mentioned that I haven't gone any further than trying to flash TWRP. This is the first phone I've even unlocked the bootloader on, so I'm extremely new at this.
I'm guessing that Root Explorer and Flashify both require root, which I don't have. Is there a way to get root access with TWRP not staying installed? Is it possible to root the phone while TWRP is installed? The reason I ask is if rooting the phone requires the phone to be rebooted, then TWRP will no longer be installed.
Please excuse the rudimentary questions, I just don't want to mess anything up. I've read so many things over the past several years that warn people to be careful because the phone could be bricked.

j.r.pitcher said:
Thanks for the suggestions guys.
I'm sorry, I should have mentioned that I haven't gone any further than trying to flash TWRP. This is the first phone I've even unlocked the bootloader on, so I'm extremely new at this.
I'm guessing that Root Explorer and Flashify both require root, which I don't have. Is there a way to get root access with TWRP not staying installed? Is it possible to root the phone while TWRP is installed? The reason I ask is if rooting the phone requires the phone to be rebooted, then TWRP will no longer be installed.
Please excuse the rudimentary questions, I just don't want to mess anything up. I've read so many things over the past several years that warn people to be careful because the phone could be bricked.
Click to expand...
Click to collapse
Don't worry, we have all been junior at this at some point... (and I don't pretend to be an expert, but I've gone through this whole process a few days back with my nexus 5... so it's fresh for me)
I'm guessing that if you have unlocked the bootloader and are trying to install TWRP, you ultimately want to root your phone.
To root your phone you have 2 options,
- either root your stock rom, by following the instruction here [GUIDE] Unlock/Root/Flash for Nexus 6P (read the (section 6) instructions carefully and make sure the version (build) of your rom is the correct one to flash a modified boot.img)
- or you can directly replace the stock rom with a pre-rooted rom that you can find in the XDA Developer section (the Chroma rom for instance could be a good one)
In both cases, you'll need to flash some files via TWRP...
Since you have an issue with rebooting into TWRP, you will have to first boot into your stock rom, copy or download on your phone SD card the zip files that you'll need to flash with TWRP and then reboot into bootloader, and follow the instruction for rooting or install a modified pre-rooted rom. Whenever you'll need to boot into recovery during the process, you will need flash TWRP again via adb and boot directly into TWRP (the flash and direct boot adb instruction from cmd on your PC is: fastboot boot <twrp name>.img).
Once you have a rooted rom, you can test Flashify to make TWRP recovery permanent
Enjoy your new rooted phone
PS: don't worry too much about bricking your phone. I believe this occurs when people don't read instructions carefully enough and don't flash the correct zip files or img files... You may find some video tutorials on how to root, but XDA guides are usually great

Well said surfinette!

Surfinette said:
Don't worry, we have all been junior at this at some point... (and I don't pretend to be an expert, but I've gone through this whole process a few days back with my nexus 5... so it's fresh for me)
I'm guessing that if you have unlocked the bootloader and are trying to install TWRP, you ultimately want to root your phone.
To root your phone you have 2 options,
- either root your stock rom, by following the instruction here [GUIDE] Unlock/Root/Flash for Nexus 6P (read the (section 6) instructions carefully and make sure the version (build) of your rom is the correct one to flash a modified boot.img)
- or you can directly replace the stock rom with a pre-rooted rom that you can find in the XDA Developer section (the Chroma rom for instance could be a good one)
In both cases, you'll need to flash some files via TWRP...
Since you have an issue with rebooting into TWRP, you will have to first boot into your stock rom, copy or download on your phone SD card the zip files that you'll need to flash with TWRP and then reboot into bootloader, and follow the instruction for rooting or install a modified pre-rooted rom. Whenever you'll need to boot into recovery during the process, you will need flash TWRP again via adb and boot directly into TWRP (the flash and direct boot adb instruction from cmd on your PC is: fastboot boot <twrp name>.img).
Once you have a rooted rom, you can test Flashify to make TWRP recovery permanent
Enjoy your new rooted phone
PS: don't worry too much about bricking your phone. I believe this occurs when people don't read instructions carefully enough and don't flash the correct zip files or img files... You may find some video tutorials on how to root, but XDA guides are usually great
Click to expand...
Click to collapse
Thanks for the detailed instructions, I really appreciate it.
To be perfectly honest, I was really nervous trying all of that out. I know you said that I shouldn't worry too much about bricking the phone, but it was still a fear.
I have TWRP installed now and it is sticking. Below is a description of how I got it to stay installed.
I didn't have access to my pc this weekend, so was planning on doing it yesterday (Monday). However, Sunday I was re-reading through the posts in this thread and jrc27 mentioned a tick box or setting that you need to check, and I remembered that when I installed TWRP the first time there was a screen that gave you a choice of "Keep Read Only" or "Swipe to Allow Modifications", then remembered someone posting elsewhere about doing the "Swipe to Allow Modifications" is what let's TWRP overwrite the part of Android that resets the recovery mode to the stock recovery mode upon reboot. Well, everytime I would reboot the phone it would be back to the stock recovery mode, so I must have hit "Keep Read Only" that first time, and checked the "Never show this screen during boot again" checkbox. In another post someone was having a different problem with TWRP and someone else told them to delete the .twrps file in the TWRP folder.
So, I flashed TWRP again, and in Advanced, I went into the File Manager, found the .twrps file and deleted it. Rebooted the phone, flashed TWRP again and had the screen that gave me a choice of "Keep Read Only" or "Swipe to Allow Modifications". I did the "Swipe to Allow Modifications", and it booted into TWRP just fine. I rebooted the phone, went to recovery mode and it again booted into TWRP. So, finally it is sticking.
Again, thanks for all of the suggestions, I do appreciate it greatly, as well as welcoming comments and tone of voice (or text as it may be).
Here is what that screen looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

warpanda said:
I'm having the same issue and cannot seem to find a solution as well. I feel like I'm missing something very obvious...
Click to expand...
Click to collapse
I'm new to xda, so not sure how the forums work. I just posted a reply to Surfinette with how I fixed the issue on my phone. I don't know if you get a message saying a new post was added or not, so I am replying to your post to let you know about it.

u must have the zip in SD card for rooting..
simply....
after flashing twrp do not reboot, or stock recovery will be flashed again... (thats how it works stock)
instead:
after flashing twrp, scroll down and click recovery to boot it... once in twrp, flash the root zip.... the zip used for rooting the device already includes the script that fixes the code that reflashes the factory recovery
(this is assuming you already download the root zip. when i say root zip i mean the proper SuperSU at the time... either system or systemless versions)

chaco81 said:
u must have the zip in SD card for rooting..
simply....
after flashing twrp do not reboot, or stock recovery will be flashed again... (thats how it works stock)
instead:
after flashing twrp, scroll down and click recovery to boot it... once in twrp, flash the root zip.... the zip used for rooting the device already includes the script that fixes the code that reflashes the factory recovery
(this is assuming you already download the root zip. when i say root zip i mean the proper SuperSU at the time... either system or systemless versions)
Click to expand...
Click to collapse
Thanks for the info, chaco81!

TWRP for Z3 compact ; Unlocked Bootloader - GUIDE

Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!

Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??

dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality

Clarification
Should I have to flash DRM Fix every time I flash TWRP?

andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to

i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.

epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?

panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks

epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!

To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
 @epiii_nephrine

panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:

epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.

After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.

smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again

I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.

panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.

ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!

panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.

ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions

[STOCK][N][ARB01] H830 20N ZIPs + KDZ (2017-12-01 Security Patch)

First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE

Thank you very much bedwa!

Kdz link updated!

Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.

Keeping me honest, I swear I'll remember them next time.

Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.

shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:

help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i had this issues when i try to flash it i already use uppercut

solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?

abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.

Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)

fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.

@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.

Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?

nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.

I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?

Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.

Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?

No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.

New security patch update alert