Database Develop

Help! Totally messed up device!

OK so I tried to use ADB to push an modded Launcher2.apk. For some reason (even though I copied and pasted the commands into the prompt) the launcher force closes over and over. I cannot do anything on the device. Tried a hard-reset but it survives, again force closes over and over.
How can I go back to COMPLETELY STOCK without being able to access the device?
EDIT: FIXED! Thanks grainysand for giving instructions. I'll also take this opportunity to flip the e-bird to the folks who snidely responded with things that not only didn't help, but just makes XDA that much less accessible. I hope those folks got a huge boner off of it. But again, thanks to those who did help.

Plug it into your PC and try rebooting into recovery via ADB commands?

No idea how. If you know what commands to use that'd be greatly appriciated!

adb reboot recovery

Just replace the file you just pushed with it's original, providing you still have it. If you don't find it, and then push it back over the top. It will still mount as adb, if you don't have debugging on persist through the popups and turn it on, adb push.

MatMew said:
Just replace the file you just pushed with it's original, providing you still have it. If you don't find it, and then push it back over the top. It will still mount as adb, if you don't have debugging on persist through the popups and turn it on, adb push.
Click to expand...
Click to collapse
I do have it, and I tried this, it didn't work. I cannot get to the device whatsoever, the launcher will not run, it repeatedly force closes. Tried pushing it back via ADB, the prompt says it copied correctly, but on reboot, same thing. I'm going to need to flash, just don't know how.

Just restore the Nand backup you made before trying to push the modded launcher over.

uansari1 said:
Just restore the Nand backup you made before trying to push the modded launcher over.
Click to expand...
Click to collapse
I didn't make one, which yeah, I know I should had; but I was in a hurry and I thought pushing the backup file back over would be fine if it messed up. But now that I can't get that done, not sure what else to do.

level5music said:
I didn't make one, which yeah, I know I should had; but I was in a hurry and I thought pushing the backup file back over would be fine if it messed up. But now that I can't get that done, not sure what else to do.
Click to expand...
Click to collapse
Return it to Google and buy a prepaid candybar phone that is not a smartphone.

By no means is your phone bricked, or even close to it. Do as we've suggested, there are tons of options that aren't listed here. Wipe, flash, etc. As I stated, push a launcher that won't clash with your system.

ScottC said:
Return it to Google and buy a prepaid candybar phone that is not a smartphone.
Click to expand...
Click to collapse
Look how awesome you are! Dude, could we not have these kinds of posts? If you can't help, don't post.

level5music said:
I didn't make one, which yeah, I know I should had; but I was in a hurry and I thought pushing the backup file back over would be fine if it messed up. But now that I can't get that done, not sure what else to do.
Click to expand...
Click to collapse
I already knew that... but thought someone should make the point. You should be able to fix this issue relatively easily by booting into recovery and flashing a custom ROM again. It should overwrite launcher2.apk, if I'm not mistaken.

uansari1 said:
I already knew that... but thought someone should make the point. You should be able to fix this issue relatively easily by booting into recovery and flashing a custom ROM again. It should overwrite launcher2.apk, if I'm not mistaken.
Click to expand...
Click to collapse
I'm not sure how to do this.. only ADB? I'm fairly new to Android, it's not like booting WinMo devices to bootloader and running an exe of course. I'm really dumb at ADB at the moment, so commands would really help me out. I do appreciate the help though guys!

We already told you to boot into recovery and go from there. Did it not work or something?

I'm not rooted, but IIRC, turning off the phone, then restarting it while holding the volume down button will give you the option to boot into recovery, no? So all you have to do is copy the ROM that you originally flashed to the phone onto the root of your SD card, go into Recovery (I'm assuming you're running Amon_RA's Recovery, which is an excellent product), and flash the zip file.
If what I wrote sounds confusing or you don't understand it, then you were premature in rooting your phone and messing around with files therein, and you need to do some researching and reading on this site (including the G1 forum) for all the info regarding these processes.
Anyway, don't freak out... your phone will be fine. I'm going back to bed...but I'm sure someone can give you a step by step to what I said if need be (hopefully you know how do to this though)...

grainysand said:
We already told you to boot into recovery and go from there. Did it not work or something?
Click to expand...
Click to collapse
What does the filename have to be? What if I only have the regular recovery? I tried the file unzipped and recovery just sat there.

Ok I kept Googling and trying stuff. I got a stock rom from MDC and tried to flash it in stock recovery (I dont think it was amon-ra's, no real way to tell that I could see).. tried to flash the stock rom and it says Verification Failed. Ugh.. does anyone have step by step instructions? I'm really failing here.

You can tell it's Amon_RA's. It's got a... well, depending on which version you got it'll either have the Nexus logo or a green or pink Carebear.
Anyway.
Download the Amon_RA recovery if you haven't already. Flash it (fastboot flash recovery filename.img).
Type:
adb reboot recovery
You should now be in Amon_RA's recovery. Select wipe and wipe everything. Then select "Flash from SD card" and flash whichever ROM you downloaded.

Can someone help me get back into recovery?

Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!

I've been searching and I should add that my bootloader is not unlocked

Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.

Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !

1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons

Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.

Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.

Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?

Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here

About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.

Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.

I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!

Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.

Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!

Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??

well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"

Do you have Busybox installed?

Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?

Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.

Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.

[Q] No functional recovery image... now what.

Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.

A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!

Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.

Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me

Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120

Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?

Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery

Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).

zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D

are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!

Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.

I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.

Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?

Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.

For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.

[Help] Atrix HD won't enter recovery mode no matter what!

I've got an Atrix HD and I've been trying to flash HoloBlur since a while now.
I'm presently on 4.1.1 (98.4.20.MB886.ATT.en.US).
I used the Motochopper tool to gain root access. Success.
I used the Motoapocalypse tool to unlock bootloader. Success.
I've used the Myth Tools to flash the inbuilt CWM as well as other versions of it. I've also tried installing CWM through fastboot. All of the methods which I use tell me that the recovery was flashed successfully. However I cannot enter recovery mode at all. I've used to Myth Tools to enter recovery. Failure. I've powered down and tried the Vol-Up and Power button combination. Failure. I just get the image of the dead Android.
Also, in the fastboot mode, pressing the Vol-Up or Vol-Down buttons does not do anything.
I know for sure that I'm rooted. The Super User app is fully active. I've removed AT&T bloatware to confirm this. The app is fully functional.
I also am certain that the bootloader is unlocked. I've verified this through the fastboot mode.
I don't have a clue about what am I doing wrong. I just cannot enter recovery mode at all.
Any help regarding this will be greatly appreciated!

Reinstall cwm through adb? Is the phone still working?
Sent from my MB886 using Tapatalk 4

salafra 367
The phones working perfectly fine. The only problem is that I can't enter recovery mode no matter what. I've tried flashing recoveries through fastboot, adb, toolkits, everything. The phone merely shows the dead Android when it enters recovery.

Rabie Haider said:
The phones working perfectly fine. The only problem is that I can't enter recovery mode no matter what. I've tried flashing recoveries through fastboot, adb, toolkits, everything. The phone merely shows the dead Android when it enters recovery.
Click to expand...
Click to collapse
Try starting from scratch using RSD Lite to flash yourself back to stock. Then begin the process again, minus unlocking the bootloader, since you already did that.

I really don't want to do that. Since I dont have access to any recovery at this time, I cant make a Nandroid backup. Which means in case things go bad with the flashing, Ill be stuck with a bricked phone.

did u rename the file install_recovery.sh?

devilsking said:
did u rename the file install_recovery.sh?
Click to expand...
Click to collapse
No. However I just tried doing this.
I downloaded CWM Touch 6.0.3.6 from m0ndul's thread.
I extracted the package. Copied the recovery image to moto-fastboot folder as well as recovery folder for Myth Tools.
I entered fastboot and used 'fastboot flash recovery recovery.img'. Fastboot gave me success notification.
I restarted the phone and entered recovery. The phone shows the dead Android image.
So then I renamed the file to 'install-recovery.sh' in both fastboot and Myth folders.
Both fastboot and Myth Tools give me success notification.
However on entering recovery the same dead Android image comes up. :crying:

You should definitely RSD or MythTools back to complete stock and do the process over again, as mentioned above. It is the only conceivable fix to this strange problem at the time. As long you don't unplug the chord during RSD flashing then nothing will go wrong, I've had to do it about 3 times. I may be wrong, but I'm pretty sure that if an RSD flash was unsuccessful you wouldn't be able to use that nandroid backup in the first place, fastboot would be pretty much the only place you can go.
Even if it didn't work (very highly unlikely), this is another way to do it that will definitely work: http://forum.xda-developers.com/showpost.php?p=40929335
Here's all you need: http://sbf.droid-developers.org/dinara/list.php The third ATTUS and the Mexico Retail are the only two that will work.
I have the AT&T model as well and I have used the Mexico Retail zip every time without fail.
Replace the XML file inside of the zip with this one so that it flashes properly: https://www.box.com/s/num1eshkf0c2or2h4160
It is completely safe, just don't do it during shceduled power outages, storms, don't touch the data cable, and let it do its thing until it boots back up.

Can you boot your phone? If you can, install Root Explorer and change the recovery file name by adding .bak to the end, then try to install cwm.

Neighbor808 said:
You should definitely RSD or MythTools back to complete stock and do the process over again, as mentioned above. It is the only conceivable fix to this strange problem at the time. As long you don't unplug the chord during RSD flashing then nothing will go wrong, I've had to do it about 3 times. I may be wrong, but I'm pretty sure that if an RSD flash was unsuccessful you wouldn't be able to use that nandroid backup in the first place, fastboot would be pretty much the only place you can go.
Even if it didn't work (very highly unlikely), this is another way to do it that will definitely work: http://forum.xda-developers.com/showpost.php?p=40929335
Here's all you need: http://sbf.droid-developers.org/dinara/list.php The third ATTUS and the Mexico Retail are the only two that will work.
I have the AT&T model as well and I have used the Mexico Retail zip every time without fail.
Replace the XML file inside of the zip with this one so that it flashes properly: https://www.box.com/s/num1eshkf0c2or2h4160
It is completely safe, just don't do it during shceduled power outages, storms, don't touch the data cable, and let it do its thing until it boots back up.
Click to expand...
Click to collapse
SOLVED!
I followed instructions from the CWP thread by some other members.
I've had dozens of Androids and I've flashed things hundreds of times but nothing got as messy as AHD did.
In short, bootloops, nuclear warfare and whatnot later, I'm running HoloBlur.
Thanks a million for your assistance.

Rabie Haider said:
SOLVED!
I followed instructions from the CWP thread by some other members.
I've had dozens of Androids and I've flashed things hundreds of times but nothing got as messy as AHD did.
In short, bootloops, nuclear warfare and whatnot later, I'm running HoloBlur.
Thanks a million for your assistance.
Click to expand...
Click to collapse
How did you fix it?
UPDATE:
Nevermind... JUST Remove ~/system/etc/install-recovery.sh it keeps on overwriting the recovery when you boot.

Just That?
MGA2009 said:
How did you fix it?
UPDATE:
Nevermind... JUST Remove ~/system/etc/install-recovery.sh it keeps on overwriting the recovery when you boot.
Click to expand...
Click to collapse
Just that?
you did the whole thing to replace files on the rsd thing? or this is the noobsafe method to get into the recovery?
BTW i'm noob...

clopezloud said:
Just that?
you did the whole thing to replace files on the rsd thing? or this is the noobsafe method to get into the recovery?
BTW i'm noob...
Click to expand...
Click to collapse
That's way to install custom recovery since renaming that file is the necessary step before flashing custom recovery.

Can't enter recovery mode???

I can't seem to figure out how to enter into recovery mode on my T-Mobile G4. It's running everything completely stock. I have tried holding power button and volume up until the logo comes on and releasing both buttons and then immediately holding them both down again waiting.. and nothing happens. I've even tried waiting for one second after I initially release to hold them down again. Same outcome. It always just boots back up into Android. I have tried volume down instead.. Nothing. Can someone please show me how to boot into recovery mode? Again, running stock rom.

I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.

Demati said:
I had the same issue. This is what I did to resolve it.
1. Enable Developer Options (see here).
2. root the phone (see here).
3. Download TWRP for the LG G4 H811 from here.
4. Install Flashify from the Play store.
5. Open Flashify and select Recovery Image -> Choose file and select the file from Step 2 to install TWRP
6. Reboot to TWRP from Flashify
When I was on the factory ROM I had to repeat steps 5 & 6 any time I wanted to boot into recovery (TWRP). None of the other boot options worked for me. Not button combinations and not even using adb (adb reboot bootloader). So what I did next is I decided to try another ROM. I installed one of the CM12.1 nightlies. Now running on CM12.1 I can boot into recovery without issue. I have no idea what is in the stock ROM that made it impossible to boot to recovery. I haven't been very motivated to go back to the stock ROM to do any further troubleshooting.
Click to expand...
Click to collapse
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..

From the T-mobile website: https://support.t-mobile.com/docs/DOC-21911

stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.

That's not what I'm talking about. That's talking about factory resetting your phone with the hardware keys. I'm talking about entering recovery mode (kinda like the bios of the phone) using the hardware keys.. It's different.

Demati said:
If there is a way I didn't find one. There very well may be a way to do this. I just didn't put in more than a couple of hours of effort.
Click to expand...
Click to collapse
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.

stringz90 said:
So, you're saying that there is no other way to get into recovery, but to root the phone first? I was hoping I didn't have to do that.. I haven't researched how to properly save the stock rom in case I need to get back to it because I need to bring it to the store for some reason or another..
Click to expand...
Click to collapse
stringz90 said:
I'm starting to think T-Mobile did something different with their variant to disable people from entering recovery mode.. This is irritating. I'd like to have the option of doing so in case I need to re-calibrate my battery or anything else that I'd need access to the recovery for.
Click to expand...
Click to collapse
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?

Demati said:
I have been trying a few different ROMs over the last few days. The modified stock ROM (Genisys) is pretty much the same as the stock minus some bloatware and it is rooted. I have no issue booting into recovery from it. Maybe that is worth a try for you?
Click to expand...
Click to collapse
Alright.. I guess, I'll have to try that, but first is there any way to do a backup of some sort in case I have to go back to stock rom rooted? I got my G4 about a month ago and haven't done much research on rooting this specific device. I haven't had a high end phone with rooting and rom options in a long time. The last phone I had a chance to root and install cool custom roms on was a Samsung Galaxy S2. If you can guide me in the right direction I'd appreciate it. I guess I have to start from square one again. In the past I remember that in order to go back to completely stock you had to have a usb jib to reset the flash counter. Is it the same for this case? I welcome anyone's helpful input. Thanks, everyone.