Database Info

[Q] Recovery mode not working

ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
{
"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 also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.

zach18 said:
ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
View attachment 1637759
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.
Click to expand...
Click to collapse
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
fastboot devices
Click to expand...
Click to collapse
It should list your phone.
Then type in
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.

try another computer to install recovery back or just rom manager by wi-fi.

Talal916 said:
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
It should list your phone.
Then type in
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.
Click to expand...
Click to collapse
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.

zach18 said:
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.
Click to expand...
Click to collapse
So being curious and trying to further troubleshoot, I followed this wiki to make sure everything was setup correctly.
Howto: Install the Android SDK (Google that, i can't post links yet)
When I typed
adb devices
Click to expand...
Click to collapse
and my device showed up.
But I am still not seeing it when I boot into FASTBOOT MODE, and type
fastboot devices
Click to expand...
Click to collapse

mypat said:
try another computer to install recovery back or just rom manager by wi-fi.
Click to expand...
Click to collapse
How do i install recovery back? where would i find that img?

zach18 said:
How do i install recovery back? where would i find that img?
Click to expand...
Click to collapse
Instal twrp.apk on your rooted phone. Connect to internet and twrp will download the IMG recovery for your phone. Reboot to boatloader and select recovery.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2

Is your phone unlocked?

ej8989 said:
Is your phone unlocked?
Click to expand...
Click to collapse
So I finally figured it out. I do apologize for how vague and un informative the question was. It was a case of me needing to dig a little more.
Here is what i did.
I had installed a Rom Manager, CyonGenMod when i rooted the phone. They had a recovery img in the app which i used. I think googled around for cyogenmod 10 and ICS 4.0.4. Then i realized i had to find google apps, so i could add my contacts from gmail. Then it was just messing around with bootloader to get the right setup.
I do appreciate the help, y'all put me on the right path. Made me find answers to the right questions. Again I apologize for not doing more due diligence.
Thanks for the help

Boot Loop after attempting to make backup in safestrap

Seeing as how the soak tests were about to come out I was booting into recovery to make a safestrap backup of the slot I'm using. After a couple seconds it rebooted and is now in the perpetual bootloop.
What's worse is I can't attempt a HouseofMoto fix because my ADB drivers are no longer working, the device is listed under ADB Interface as - Mot Single ADB Interface but running the adb shell command just brings up "Error: device not found".
I have done the HouseofMoto shpeal around the last OTA soak test so I'm fairly well versed but this has stumped me for the last 2 hours as to why the drivers won't work.
Any ideas?
Thanks

Kickbut101 said:
Seeing as how the soak tests were about to come out I was booting into recovery to make a safestrap backup of the slot I'm using. After a couple seconds it rebooted and is now in the perpetual bootloop.
What's worse is I can't attempt a HouseofMoto fix because my ADB drivers are no longer working, the device is listed under ADB Interface as - Mot Single ADB Interface but running the adb shell command just brings up "Error: device not found".
I have done the HouseofMoto shpeal around the last OTA soak test so I'm fairly well versed but this has stumped me for the last 2 hours as to why the drivers won't work.
Any ideas?
Thanks
Click to expand...
Click to collapse
can you get to the bootloader? try wiping from stock recovery if you can

BladeRunner said:
can you get to the bootloader? try wiping from stock recovery if you can
Click to expand...
Click to collapse
That is accessed by power button + vol up at boot?

Vol down and power button momentarily should get you to the boot loader. Once you are at the menu vol down to navigate & vol up to select.
Sent from my XT1080 using Xparent BlueTapatalk 2

BladeRunner said:
Vol down and power button momentarily should get you to the boot loader. Once you are at the menu vol down to navigate & vol up to select.
Sent from my XT1080 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I believe that's fastboot?
And that is the environment I'm in, but every option I select on that menu just bootloops

Don't use the power button to select use the vol up.
Sent from my XT1080 using Xparent BlueTapatalk 2

BladeRunner said:
Don't use the power button to select use the vol up.
Sent from my XT1080 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yeah, I am
correct me if I'm wrong but I believe safestrap hijacks the built in recovery environment with its own?

Kickbut101 said:
Yeah, I am
correct me if I'm wrong but I believe safestrap hijacks the built in recovery environment with its own?
Click to expand...
Click to collapse
I think you can have stock recovery and ss installed. Only thing is, if you rooted the ultra stock recovery will be gone until you fastboot flash it back.
Sent from my XT1080

an21281 said:
I think you can have stock recovery and ss installed. Only thing is, if you rooted the ultra stock recovery will be gone until you fastboot flash it back.
Sent from my XT1080
Click to expand...
Click to collapse
I did flash a stock recovery with fastboot commands.
now boots into stock recovery menu if I want it to, however I may have made an ass of myself seeing as how I forgot HouseofMoto can be executed (in fact HAS to be) within fastboot. and right now I am tackling the newer 2.0 version and still hitting some snags.
I realize I can probably just reflash the entire system with fastboot commands but right now I am attempting to preserve data.
will update with results

Got the phone booting now into OS after HoM.
ADB refuses to work in the OS, debugging on, drivers correct, multiple computers. I keep getting an error when trying to use ADB commands
{
"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"
}
And of course the unit is not rooted.
Am I overlooking something?

Kickbut101 said:
Got the phone booting now into OS after HoM.
ADB refuses to work in the OS, debugging on, drivers correct, multiple computers. I keep getting an error when trying to use ADB commands
And of course the unit is not rooted.
Am I overlooking something?
Click to expand...
Click to collapse
so does the phone recognize it is being is being connected in debugging mode or just as a media device?
I'd try uninstalling and reinstalling the drivers and trying a different usb cable.

BladeRunner said:
so does the phone recognize it is being is being connected in debugging mode or just as a media device?
I'd try uninstalling and reinstalling the drivers and trying a different usb cable.
Click to expand...
Click to collapse
Both, and I have had minimal luck with ADB since then.
I believe most of my problems are related to using MotoWpNomo and PwnMyMoto/Rockmymoto, which are not so compatible with one another. Also didn't know that MotoWpNomo is permanent and survives a HoM restore.

Kickbut101 said:
Both, and I have had minimal luck with ADB since then.
I believe most of my problems are related to using MotoWpNomo and PwnMyMoto/Rockmymoto, which are not so compatible with one another. Also didn't know that MotoWpNomo is permanent and survives a HoM restore.
Click to expand...
Click to collapse
Try opening device manager and uninstalling the ADB device that looks like your phone then reinstall the drivers. I have a feeling some other similar driver is blocking your phone when it had adb debugging turned on.
also try this program USB deview downloaded mfrom here: http://www.nirsoft.net/

Softbrick?

Hi guys, I think my Nexus is in bootloop another time...
Now I have not time to see anything, but the recovery is unlocked. . can I try something?
What should I do?
Thanks..

Not sure what you mean by recovery is unlocked.. Do you mean the bootloader?
Download the factory image from google and flash system, boot and cache img files and reboot. If you're still stuck, flash all img files and you will be up and running.

Softbrick? No such thing lol.
See/read here for everything you need to do to reflash your phone : http://forum.xda-developers.com/showthread.php?t=2784527
Sent from my Nexus 5 using Tapatalk 2

I'm finally back, sorry, I mean that the Recovery works, like the bootloader...
I have not understand you Vin4yak, after flashing the factory image what I have to do?
I have to follow this guide? http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
And I have to flash the factory image from the recovery?
Thanks

Factory images are flashed via fastboot
Click link to sticky thread in signature. Then read "adb and fastboot. What is it?" thread. Then you'll know everything and can follow the guide you posted
Although before that, you tried a factory reset from recovery, yes?
Sent from my Nexus 5 using Tapatalk

No, like I said I'm back just now and I'haven't tried nothing, so I have to try the factory reset?

Giolte_ said:
No, like I said I'm back just now and I'haven't tried nothing, so I have to try the factory reset?
Click to expand...
Click to collapse
Always the first thing to try if you can't boot.. It wipes your personal stuff off the device which could cause issues.
Sent from my Nexus 5 using Tapatalk

I've the TWRP, I've done the wipe all/factory reset, reboot but nothing is changed.
So, I've to follow this guide? http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
And what I should do? I see only commands like fastboot oem lock that I already know... or it is just a guide to know something more?

thats an information thread. Its info so you understand how to fastboot flash. Read it all to understand
You'll want to flash system, cache, boot and userdata.. Fyi userdata will wipe sdcard. Adb pull any data you need to kwwp
Sent from my Nexus 5 using Tapatalk

Ok.. however, I've already done the installation of adb, I have to do it another time?

No. Please try to apply logic to the situation
Sent from my Nexus 5 using Tapatalk

But "adb devices" doesn't match the device...

What the hell are you talking about. Its either listed and connected or not listed which means it's disconnected. It doesn't match anything.
Sent from my Nexus 5 using Tapatalk

Sorry, "match" is not the correct verb, however this is the situation:
"adb devices" in the cmd doesn't find the device, and here says "android bootloader interface", but I can't understand if this says it's connected or not...
{
"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"
}

Giolte_ said:
Sorry, "match" is not the correct verb, however this is the situation:
"adb devices" in the cmd doesn't find the device, and here says "android bootloader interface", but I can't understand if this says it's connected or not...
Click to expand...
Click to collapse
And you're booted into recovery, right?

No, I'm booted into Bootloader, I don't have to flash boot, system, userdata and cache via fastboot?

Giolte_ said:
No, I'm booted into Bootloader, I don't have to flash boot, system, userdata and cache via fastboot?
Click to expand...
Click to collapse
You've clearly not understood my thread. Adb only works in recovery. Fastboot only works in bootloader. If you're booted into bootloader use "fastboot devices". Please read the thread again. This time in full.
Sent from my Nexus 5 using Tapatalk

Mmm, sorry, I maybe jump this part...
So, ok, both fastboot and recovery see the device, now I'm gonna flash boot, userdata, cache and system via fastboot, yes? And then I have to do another factory reset like said in the guide "How to flash a factory image"?

You shouldn't have to do the factory reset but it won't hurt.
Sent from my Nexus 5 using Tapatalk

Ok, thanks, now unfortunately I have to go, I'll back in 1-2 hours and I try to flash these things.
I have to flash them in the order of this guide or it's the same?
Thanks again, now I really must go.

Tried to unroot, now Pixel won't go past 'Device is corrupt' screen

Hi all,
I tried to unroot and relock the bootloader for my Pixel through SuperSU (settings, unroot, restore stock recovery etc). However, now when I turn the phone on it gets to the 'your device is corrupt' screen (https://lh3.googleusercontent.com/-Avr7yNnXOpY/VjGcdDK9iHI/AAAAAAAGCf0/LLwjhkLX1yk/w666-h2518/15+-+1) and then just switches off. Is there anything I can do? Bootloader is currently locked (EE Pixel)
{
"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"
}

Just want to make sure I understand you, you said you re-locked your bootloader?

kornesque said:
Just want to make sure I understand you, you said you re-locked your bootloader?
Click to expand...
Click to collapse
Yup.
So did the SuperSU thing. Then went into fastboot to relock. That seemed successful so I tried to restart and this happened..
And I can't get into recovery >.<

My ability to post is intermittent, don't know what's up but if this doesn't get through then...well, i guess you won't know.
Did you take any 7.1.1 updates or sideload anything? Do you have a VZW variant? And can you get to the bootloader to issue fastboot/adb commands? Hopefully you're not hosed, we'll see what we can do and hopefully a guru shows up here too.

Try to unlock the bootloader again. If you can. Download the full system image from Google and flash that. Then re-lock it.
Sent from my Pixel using Tapatalk

brpqzme said:
Yup.
So did the SuperSU thing. Then went into fastboot to relock. That seemed successful so I tried to restart and this happened..
And I can't get into recovery >.<
Click to expand...
Click to collapse
What happens when you boot to recovery?

bobby janow said:
What happens when you boot to recovery?
Click to expand...
Click to collapse
It boots into the bootloader. Then I choose the RECOVERY option and the 'YOUR DEVICE IS CORRUPT' screen shows up again. It stays on that for a few seconds then the device turns off, exactly like how it does when I try to boot into the phone normally. So I can't get into recovery either..
kornesque said:
My ability to post is intermittent, don't know what's up but if this doesn't get through then...well, i guess you won't know.
Did you take any 7.1.1 updates or sideload anything? Do you have a VZW variant? And can you get to the bootloader to issue fastboot/adb commands? Hopefully you're not hosed, we'll see what we can do and hopefully a guru shows up here too.
Click to expand...
Click to collapse
So this is an EE variant (similar to the VZW one, but UK-based). I can get into the bootloader (holding down power+ vol down) but ADB DEVICES doesn't list anything. I didn't update it to 7.1.1. I used SuperSU to UNROOT, clicked YES when it asked to restore stock recovery and image. Booted into fastboot and relocked bootloader.
Though if I use the SkipSoft toolkit it does detect it in Fastboot mode

Electroz said:
Try to unlock the bootloader again. If you can. Download the full system image from Google and flash that. Then re-lock it.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Can't unlock without dePixel8, and can't use that unless I boot into Android itself so that I can push the files..

brpqzme said:
Can't unlock without dePixel8, and can't use that unless I boot into Android itself so that I can push the files..
Click to expand...
Click to collapse
Have you tried a regular fastboot unlock?
Sent from my Pixel using Tapatalk

Electroz said:
Have you tried a regular fastboot unlock?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yup, tried that through SkipSoft (because normal ADB doesn't detect my phone so using SkipSoft). It says 'failed' when I tried

No idea what skipsoft is. I mean did you load up a command prompt and run the "fastboot OEM unlock" command. This has nothing to do with ADB. You need to be in fastboot mode to run it. To make sure your device shows, run fastboot devices. Again, adb will not help with the bootloader locked.
Sent from my Pixel using Tapatalk

Electroz said:
No idea what skipsoft is. I mean did you load up a command prompt and run the "fastboot OEM unlock" command. This has nothing to do with ADB. You need to be in fastboot mode to run it. To make sure your device shows, run fastboot devices. Again, adb will not help with the bootloader locked.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Ah I see. OK so yes, 'FASTBOOT DEVICES" shows my device. FASTBOOT OEM UNLOCK fails though. Which I guess I expected, because it's an EE/VZW locked phone..

brpqzme said:
Ah I see. OK so yes, 'FASTBOOT DEVICES" shows my device. FASTBOOT OEM UNLOCK fails though. Which I guess I expected, because it's an EE/VZW locked phone..
Click to expand...
Click to collapse
OK. So even in recovery mode you can't get adb devices to show the phone? It sounds like you're out of luck.
Sent from my Pixel using Tapatalk

Electroz said:
OK. So even in recovery mode you can't get adb devices to show the phone? It sounds like you're out of luck.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!

brpqzme said:
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!
Click to expand...
Click to collapse
If you want to go back to stock and relock the bootloader, flash the entire system image from google first. Don't only do half of it or you'll end up in the same spot. Nice find on the fastboot Continue though!
Sent from my Pixel using Tapatalk

Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Electroz said:
If you want to go back to stock and relock the bootloader, flash the entire system image from google first. Don't only do half of it or you'll end up in the same spot. Nice find on the fastboot Continue though!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

brpqzme said:
Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Click to expand...
Click to collapse
Yes sir
Sent from my Pixel using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
brpqzme said:
Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Click to expand...
Click to collapse
But go with the 7.1.0 image just in case. So you can depixel8 again if need be.
Sent from my Pixel using Tapatalk

brpqzme said:
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!
Click to expand...
Click to collapse
If you truly are still unlocked, I would use Google's flashall bat file so you reflash both partitions correctly.
And I really wouldn't relock it. You got lucky, it would seem that your attempt to relock failed. If it had worked you would have been out of luck.
Without any mods other than unlocked I am pretty sure Android pay works fine.
Did you change anything else, like root or maybe system mods?
Edit. I'm wrong, unlocked trips safteynet. So you flash a kernel that fixes that. Franco does, I think Elemental does and this one does:
http://forum.xda-developers.com/pix...l-stock-kernel-safetynet-patch-t3516596/page5

Yea I don't get people. What's the point of relocking..

aholeinthewor1d said:
Yea I don't get people. What's the point of relocking..
Click to expand...
Click to collapse
You're assuming everybody stays up all night and day following these forums like you and me. We're the pathetic ones. LOL.

[Recovery]TWRP 3.1.1-0 LG G5 H840

DO NOT FORMAT YOUR MICRO SDCARD INSIDE TWRP RECOWERY
WARNING: If you want tho use /data and internal sdcard first have to format data in stock recovery This will wipe your internal storage, and factory reset your phone!
encryption is not supported yet
To flash this img to your phone use fastboot
Code:
fastboot flash recovery twrp-x.x.x-x-h840.img
+new test build with encryption support
source code https://github.com/synescu/twrp_lg_h840
1.Unlocking the bootloader.
1.1Get the latest drivers: ( http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 )
1.2Get ADB fastboot. If you hate installing huge files for just a few commands, you have 3 options:
-MINIMAL ADB and fastboot: (https://forum.xda-developers.com/showthread.php?t=2317790 )
-15 seconds ADB Installer v1.4.3: (https://forum.xda-developers.com/showthread.php?t=2588979 )
-SDK Platform-Tools coming directly from google: (https://developer.android.com/studio/releases/platform-tools.html )
I personally went with the “15 seconds ADB Installer v1.4.3”, because it installs also a Google driver, which might, or might have not helped out in the process to follow.
1.3Follow the instructions at the official LG unlocking page ( https://developer.lge.com/resource/mobile/RetrieveBootloader.dev ), just keep in mind that after step 1.2 you have adb ready to go @ your main drive C:\adb. You go to that folder shift + right click and open a command prompt at that location, the rest is trivial.
2.Updating to the latest official stock android.
2.1Get the latest kdz from: (https://lg-firmwares.com/lg-h840-firmwares/ ). As far as I know you can go for any of those firmwares, but it is advisable to use one from your region (Europe, South America, Middle East). As mentioned above my LG G5 H840 is the newest European model, totally unbranded. So I took the 20c for Spain. This is as high as you can get at present moment.
2.2 Flash with LGUP 1.14 and UPPERCUT 1.0.0, both available at: (http://downloads.codefi.re/autoprime/LG/LG_G5 )
2.3 Reboot and do a quick setup. I recommend to have your sim card, SD card out at this moment, do not connect to wireless networks, all of this you will have plenty of time to do later, besides whatever you set at this point will be lost in the next step.
3.Get TWRP and root
3.1TWRP. As a courtesy of synescu, we have 2 versions: a regular one and such with encryption support. It took me long to realize that only the one with encryption would work on a latest H840 installed with v20c. So I guess if you have an old phone and possibly firmware 10a/b/c/d, than you can try “twrp3.1.1-0-h840.img”, otherwise go straight to “twrp_encryption-h840.img”. If you use the one without encryption support you will find no way to root the phone, because it can not see the SD card, or any USB flash attached and also if you connect the phone to a PC with MTP mode, or any other mode you won’t be able to browse both (internal and external) memories on that phone.
3.1.1Put on a SD card following files: 1) latest stable SuperSU 2.79 2) no-verity-opt-encrypt.zip from here (https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip ) and just in case although not mandatory “twrp_encryption-h840.img”.
3.1.2Put in the C:\adb folder the “twrp_encryption-h840.img” and the stock recovery from here (https://forum.xda-developers.com/attachment.php?attachmentid=4149809&d=1494791791 ). The stock recovery is necessary in case you make a mistake and have to do a factory reset.
3.1.3Turn off the phone.
3.1.4Boot into stock recovery (holding volume down + power, at LG logo releasing power shortly and than pushing power again).
As a side note here, after I unlocked the bootloader I’ve got that annoying message on start-up that the phone is untrusted. With G4 H815 it was a small message in the upper corner, this time around it is a huge message in the middle of the screen. LG, for the love of god! After all the playing, I have now also a message screen, which I call “Options Menu”, it shows right after the nagging untrusted message. Although esthetically ugly, I have an easy way to go to recovery and fastboot in each and every regular power on, or restart. As said the Options Menu is showing up for 5 sec after the untrusted nagger. If you click the volume up, or down you get to the options (Power off, Restart, Recovery, Fastboot ), otherwise after 5 sec the phone would boot normally. I don’t know if this is the expected behavior of the phone, or did I trigger it somehow, but now I don’t have to use the combo buttons for anything.
Back from the side note. The new stock recovery is a white screen with 2 options for No and Yes. Go for YES and than YES again, after both YES the phone will be factory reset and will reboot. Do not allow it to boot though, because the userdata will be encrypted at this point and you will have to repeat the reset again. Use the combo buttons for recovery, which will bring you to the “Options Menu”, or Volume up and plug in the phone into the PC. Yet again there is hardly any time so maybe plugin in won’t be fast enough, so just keep pressed the combo buttons, also change with volume up and power, or remove the battery and start again. In any event do not let it boot until it brings you to the “Options Menu”
3.1.5In the Options Menu pick fastboot and plug the phone to the PC
3.1.6Open command prompt in adb and flash TWRP ( fastboot flash recovery twrp_encryption-h840.img ) you might be ok also to do factory reset from adb with this command (fastboot –w ), but unfortunately I forgot already if I did it, when it finally worked for me
3.1.7Disconnect from the PC and pull the battery out, or just keep the buttons combo pressed. It is possible that you see the old stock recovery (white screen YES/NO), which might have stayed somehow in memory. Do not perform further resets, just keep pressing the button combo and it will reboot eventually to the Options Menu.
3.1.8There you go 3 times volume down and power to pick recovery. Follows a reboot of the bootloader, nagging screens, but eventually it loads TWRP.
3.2Root.
3.2.1For some reason even after the factory reset, the data partition keeps an encrypted flag. So you can not write to it. Stock recovery should have reset it to non-encrypted, but it does not do it correctly, I guess. Therefore you go to Wipe, pick only the Data check box and go to change format in the bottom. Change the format to FAT and than back to EXT4
3.2.2Go to the SD card and flash no-verity-opt-encrypt.zip and SuperSu. Yes I know, that SuperSu is supposed to install also no-verity, but I like to flash both just in case.
3.2.3Do NOT wipe anything in TWRP at this point. Reboot only!!!!! Once the phone has booted in v20c you can go back to TWRP, Wipe and make all the backups you like
Thanks to @svetloslav for this complex post

Thanks a lot.
Can't wait to flash!!

YESS finally we have root on the SE thank you very much man

Hi all. When I try to flash recovery, fastboot give me that message:
target reported max download size of 536870912 bytes
sending 'recovery' (15089 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
Any suggestion? Thanks
Solved: I had not extracted the .img from the .tar archive

synescu said:
For now external sd card is mounted as internal. De only way you can flash something for now When I would have more time I will try to fix this and upload the source to github. I rooted the phone and installed the supersu and no verity zip
source code https://github.com/synescu/twrp_lg_h840
Click to expand...
Click to collapse
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?

bob8x said:
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
Click to expand...
Click to collapse
I'm booting this vith android 7.0
6.0 must boot just fine. didn't tried encryption but I'm pretty sure that doesn't work
Build compiled from Omni 6.0 sources
Sent from my LG-H840 using Tapatalk

Thank you very much for your precious time my friend. Good work

Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?

Wire1122 said:
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Click to expand...
Click to collapse
Yes internal storage it's properly mounted now
Sent from my LG-H840 using Tapatalk

Anyone can confirm if encryption works?
Sent from my LG-H840 using Tapatalk

synescu said:
Anyone can confirm if encryption works?
Click to expand...
Click to collapse
I have flash it succesffully. But how can I yest if it works?

I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs

Wire1122 said:
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
{
"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"
}
Sent from my LG-H840 using Tapatalk

Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs

Wire1122 said:
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
In Order to use data first you have to factory reset your phone using the stock recovery
Sent from my LG-H840 using Tapatalk

How? Stock recovery? Where is it? I'm noob and rooted with supersu

My log

Wire1122 said:
My log
Click to expand...
Click to collapse
stock h840-recovery.img

I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs

Wire1122 said:
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
Why would you think that you would keep TWRP after flashing stock recovery? Also, why would you flash stock recovery after flashing TWRP and SuperSU? You either have TWRP or stock recovery, not both. Also, don't ever recommend flashing stock recovery after modifying system in any way unless you reflash whole stock system as stock. Anyways, all you need to do to get TWRP back is use the :
fastboot flash recovery TWRP.img