Database Develop

Took OTA with custom recovery

Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!

boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.

KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.

switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update

I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev

Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!

slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079

switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...

This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.

switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop

Cannot install 5.1 update on Verizon

New member here. I just got the phone today, and it's activated, running 5.0. When I check for an update, it shows that there is one, and I download the update. However, after the phone restarts to begin the update, it stops on the system installation screen (it says "error" very quickly, and the android falls over). When the phone restarts, it says that the update couldn't be installed. I've wiped the cache and have done a factory reset, but neither work. Any help would be much appreciated.
Update: Tier 2 tech support from Verizon says the phone has been rooted (I bought the phone used). Is there any way to completely unroot the phone?

Usually a root program can unroot the phone, like if that phone have the root program "SuperSu" on it, there is an unroot function within the program. However, this is not recommended, when the rooting is done and you don't know what the original owners did, there are probably other system files that were changed and the OTA update will detect it and it won't work regardless.
What you should do is flash the factory stock firmware for the device. This will completely return the phone to stock 5.0 and also erase everything in the phone:
1. Download the adb/fastboot files, which is the program used to flash firmwares to android devices:
http://rootjunkysdl.com/?device=Adb Fastboot Files
2. Download the Verizon 5.0 stock firmware:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
3. Download and install the Motorola fastboot driver:
http://forum.xda-developers.com/showpost.php?p=59139823&postcount=2
4. Boot the phone into fastboot mode:
While the phone is turned off, press and hold Vol - and Power. Release Power while still holding Vol - and you will see the bootloader menu appears. Connect the phone to the computer and leave it on this menu, here you can use fastboot commands.
Your computer will begin to install the fastboot driver for your phone right now, go to Computer's Device Manager and make sure you see in top of the list "Android device" and then "Motorola ADB Interface" below it, or something very similar related to ADB.
5. Extract both the files from the ADB/Fastboot files (step 1) and files from the Verizon firmware (step 2) into the same folder. Run the batch file "XT1096_5.0_LXE22.46.11_cid2_CFC.xml.bat", it will run a series of commands that will wipe the phone and install the stock firmware. If all the commands ran successfully you have a fresh install like out of the box.
Note: In the bat file, there is a command called "fastboot erase userdata", this command delete all of the user's apps and files, if you want to keep them you can delete that line from the bat file, however, you might get an error later on if your apps data does match with the version of the firmware you just flashed on the phone (in which case you can have to boot into recovery and wipe data (which will wipe everything) or wipe cache to fix the errors.
6. After installation is done, press Vol+ to select "Normal Power up". For some goofy reason, Vol+ is the select key Motorola phones, not Power. Now you can try doing the OTA update again.
Warning: Do not install the older version firmware (4.4.4) to your phone. There are reports from people who downgrade the version on their Motorola and when they receive over the air update it hard brick their device.

Unlocked Bootloader Error Message - System Update Failing

I am from India and I exchanged my iPhone 4S for a Moto X 2014 just this evening wanting to try my hands on the Android experience.
I do not know what the seller did to this phone but I now have two issues. I tried to call the seller immediately after I noticed these problems when I came home but the number is switched off. Shame on him!
After Google'ing I found this forum for android support so I hope posting the problems here would give me some solution
Problem #1: Every time when I boot my phone, it has the warning screen which says "Warning unlocked bootloader".
Problem #2: The warning went off and landed me on the home screen. I connected to my WiFi and saw that there is a software update. I downloaded it and chose to install it. It kept rebooting for 4-5 times and then said "System Update - Failed".
Can anyone please be patient enough to give me step by step solution with download links to get my Moto X2 back in shape as how it was out of the box?
I googled a lot for the keywords "relock bootloader moto x 2014", "unroot moto x 2014" and plenty of links with different download links came up. I do not know which one to trust. I am not dumb and I can easily follow instructions. So, please anyone wanna help?

If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).

Nek0x90 said:
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Click to expand...
Click to collapse
Thank you for the reply. Attached the screenshot.
i64.tinypic.com/2nu3asn.png

I fiddled around to find out how to get into the Fastboot mode... and I observed something weird there..
AP Fastboot Flash Mode (S)
60.16 (sha-#some checksum number key with date 2015-04-02 and time#
CPU: MSM8974AC EA1.1
eMMC: 2048MB Samsung RV=07 PV=0B TY=57
Battery OK
Device i UNLOCKED. Status Code: 3
Software status: Official
I mean Seriously? I see the word Samsung in a Moto phone? I so regret buying from this seller... too much for a first Android phone :crying:
Well I also managed to Google more and installed the device drivers and the Fastboot software in my Windows PC.
Booted my device in fastboot mode and issues the below commands:
fastboot devices
#my device was shown#
fastboot oem lock
#told me to use the command with begin#
fastboot oem lock begin
#Said something like the image is ready#
Nothing happened then though. I powered on my device and I still see that warning. Still the software update is failing. :crying::crying::crying:

You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.

Nek0x90 said:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Click to expand...
Click to collapse
I am not trying to unlock my bootloader. I am trying to restore it back to the "out of the box" state. I mean I want to lock it and I want it to be in the state how it usually is when bought from the store.
Ok... I google'd how to go into the recovery mode and found this link (teamandroid.com/2015/01/08/enter-recovery-mode-moto-x/).
I followed those steps:
1. Turn OFF your phone.
2. Press and hold the Volume Down button for 2-5 seconds. While holding the Volume Down button, press the Power Button for 1-2 seconds and release.
3. I used the Volume down key to highlight "Recovery" and clicked on the power button to select it.
4. My screen went off. I mean the light gone.
Then I had to press and hold the power on button, it booted my phone with that warning unlocked bootloader message.
What am I doing wrong?
UPDATE:
I did a fastboot, connected phone to PC and issued the below command from PC and get below error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
UPDATE 2:
I enabled the developers option (by tapping on the Build number multiple times)
So, I installed an app called MobileUncle Tools.
I then opened the app from my mobile and clicked on "Reboot into recover".
It says "Please root your Android first".
OK.. so looks like the phone is not rooted - which is good.
Only the bootloader is unlocked. All I need to figure out is - re-lock my bootloader and make the system update go through successfully.
Any help please?

You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.

Nek0x90 said:
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Click to expand...
Click to collapse
I have one question for you:
What do you mean by "Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery".
My understanding is - you are saying my stock firmware is intact because it said Official in the fastboot screen. Right?
Ok... now back to the recovery check... I think I did it.
1. I went in the fastboot mode
2. Used volume down key to scroll down to Recovery option (2nd option)
3. Pressed Volume up key to select it
4. The phone rebooted (The white screen "warning unlocked bootloader" message was displayed this time too)
5. I saw a dead android symbol with the word "No command."
6. I pressed Power and Volume Up key. I saw the recovery screen I guess. There were many options - Wipe data, Wipe Cache, Install from SD, etc.
What do I need to check there?
EDIT:
Ok I noted this number from there:
Android system recovery <3e>
LPE23.32-25.1
followed by the options
reboot system now
apply update from sdcard
etc.
I think this is what has happened:
Google says "LPE23.32-25.1" is the Android 5.1 Lollipop update (v23.16.1, build LPE23.32-25.1)
However, the current Android version on my device "About" screen is 4.4.4
The OTA system update, my device telling me about is Android 5.0 Lollipop version: 22.21.19.en.EU (which is a lower version than my recovery's version)
My menu options look all white and after google'ing I realize that it has Android L's menu. Please see the screenshot i65.tinypic.com/14l4mmb.png
Could that be that reason? What can I do t rectify it?

1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.

joseph_1802 said:
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
Click to expand...
Click to collapse
THANK YOU SO MUCH for clearing that point 1 and 2. That is a relief!
Point #3 - "Your solution will be to manually flash the correct firmware or use RSD Lite."
What do I flash? OTA 5.1 (because my bootloader is from 5.1) or OTA 22.21.19.en.EU (because that is what I see in my phone's Software Update Available screen.
Where do I download those OTA files?
How do I flash using RSDLite? Any guide?
Thank you!
UPDATE:
Found the guide forum.xda-developers.com/showthread.php?t=2231249
I only need to know what I version I need to flash AND where can I download it from. Please?

Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg

Nek0x90 said:
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?

Flower07 said:
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Click to expand...
Click to collapse
No it's not a problem. This will give you the latest version with the stagefright patch.
Sent from my XT1095 using Tapatalk

It is .3 because it has the stagefright patch, the .1 version doesn't have that patch but both of them are basically the same, so there's no problem if you flash one or another.

How to Unlock Bootloader, Flash TWRP, and ROOT LG G4 H811 T-Mobile.

Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!

This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things

Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.

Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.

joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.

marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.

joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.

Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks

I have the G4 LGUS991 gotta can I tell if it's h811?

4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?

mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.

So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4

This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...

If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app

NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs

I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.

How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!

So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.

hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks

rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.

[GUIDE] Return to Stock and Upgrade

Hey guys, I am new to this gear live dev and I want to help out. I just got my gear a few days ago and I'm still playing with it I figured that my device is at 5.0.1 and has Dev-Key in the build number. I went ahead and did some research (more than 35 hours) and came to a conclusion. I figured I can help a lot of people by posting my method here. I am currently on 5.0.2 and I am trying to figure out why I still did not get the 5.1.1 update. Looks like Samsung is slow and I will ask around if anyone got the OTA or I'll sideload the OTA scripts. Making the long story short.
Entering the bootloader (hard way)
Press and hold down the power button until your device reboots. Don't let go yet. As soon as you see the Samsung logo you have to swipe from the top left corner to bottom right corner really fast 2 times. Now let go of the power button and you should be in bootloader. If not keep trying again. I would recommend this as the last resort.
Entering bootloader (easy way):
Enable USB debugging by going to settings -> about device -> tapping build number 7 times. A new option should now show up under settings called developer options. At this point make sure that you have proper adb fastboot drivers. If not you can use the minimal ADB FASTBOOT 15 second Installer I will provide a link to the thread. Make sure that the watch is paired with your phone and keep the phone near you. Connect the watch to your machine via USB and let it recognize the device. Open a terminal or cmd window and enter adb devices. You will most likely be returned with some number and unauthorized. At this step if you get an error such like ADB is not an executable program then you have not installed ADB correctly. Switching over to your phone you will now see a debugging request from your watch. Go ahead and it always allow. Now you have granted debug permissions on you watch. Run the command again and this time, the device should return authorized. Run " adb reboot bootloader ". You will be taken to the bootloader.
Unlocking Bootloader and Flashing and relocking the bootloader:
The first step is to unlock the bootloader (don't know if this voids the warranty but I think it will). After you unlock the bootloader (fastboot oem unlock) WARNING: THIS WILL WIPE YOUR DEVICE and then boot back to the OS set it up and redo the steps under Entering bootloader. Once you have entered the bootloader you will need the stock os which is KMV78Y_stock. It is 4.4w and we will upgrade it soon. Open a cmd and run fastboot devices and you should see your device in the list. If not something is wrong , check if you have the right fastboot drivers and your watch is connected properly. Try a different usb port and don't use a usb HUB. ON WINDOWS extract the zip and navigate to the folder till you see the image files. Here shift+right click and you should see an option for open command windows here. For rest of the other people without windows cd to where the image files exist. Run the command “fastboot flash system system.img ” and “ fastboot flash boot boot.img ” . Once you have done that you will have to relock the bootloader. Relocking the bootloader is an important step to receiving further updates so I recommend relocking it. IF YOU DON'T RELOCK THE BOOTLOADER THEN YOU ARE STUCK ON 4.4W WHICH SUCKS SOOOO MUCH!!!!. Relock the bootloader by running “ fastboot oem lock “. Just keep in mind that you can re-unlock your bootloader after you have upgraded but unlocking bootloader will wipe your device again. *SIGH* I ALSO HATE READING LONG INSTRUCTIONS BUT YOU ARE ALMOST AT THE END!!!. After you relock your bootloader go ahead and swipe down on the screen until you highlight the recovery option and swipe right to select. Once you have booted into recovery you will see a warning sign. Don't Panic. Just tap on the screen and you will be brought to the recovery screen once again select reset and select yes.After the reset go ahead and reboot the device. You will be brought into the android wear stock os. Go ahead and set up your device again and go to the setting ->about device -> software updates. You will see that the update is available. There you go install the updates until you get to android 5.0.2. GREAT YOU HAVE UPGRADED YOUR WATCH. There a few ways to get to 5.1.1 but I have not tried them out. I will post the instructions as soon as I have tried it. If your watch says that there is an update the go ahead and install it. Samsung does not push the update to all users at once as it may kill their servers but roll the update out in batches. If you want to sit tight and wait till it comes through or I will be posting a how to soon.
UPDATING TO 5.1.1 AND TO 6.0
Hey, figured out how we can upgrade without waiting. It is actually really simple and easy. You will need to have a locked bootloader to do this or apply any stock update. It does not work with an unlocked bootloader. Your computer will not recognize your watch when sideloading if you have an unlocked bootloader. So let's get started. Download the ota update zip from the links below leave it in the downloads or move it wherever you want it. Open a terminal window or cmd window to the location of the zip either by shift+rightclick (only windows) or by cd’ing you way. At the location of the zip prepare your watch for sideloading. Reboot to recovery by commanding “ adb reboot recovery” or “ adb reboot bootloader” then going to recovery, or going to fastboot the hard way then to recovery. The choice is yours. Once you are in recovery select adb sideload. Now go back to your computer and hit " adb devices ". You should see your device and sideload. If not then something is wrong. Since you are already in the folder where the zip exists simply enter “adb sideload LIVE.zip” and it should send the file to devise. Don't panic if you interrupt the transfer. It will not apply the changes until the entire file has been transferred. Just redo the steps above to resend it. After the update is complete you can restart your device. Upon restart, you will see that your device has upgraded to 5.1.1. Congratulations. Now to go to 6.0 just go to software update and search for another update. I am starting to love this watch at what it can do in 6.0 so I suggest you upgrade.
Thank you, all and I hope this helped a lot of people out there.
Links:
Stock OS:
Android 5.1.1 OTA:
ADB AND FASTBOOT:
I will post inks as soon as I upload them.
-Soma