Related
When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse
jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.
In the past I have unlocked the boot loaders for Pixel, Pixel 2 and Pixel 3 always on first try and I know how to do it. But my new Pixel 5, US unlocked version, arrived today, will not boot loader unlock. I have dev options enabled, USB debugging on, and allow OEM unlock set on. I'm using a Mac so my fastboot commands are ./fastboot___. With the Pixel 5 in fastboot mode, ./fastboot devices gives a correct response, the device responds with its serial number. But then with ./fastboot flashing unlock nothing happens. Just sits there. When I give the command the terminal cursor moves down to the next line but there is no response from the device. I've turned off, rebooted, repeated multiple times, same result. I tried the old ./fastboot oem unlock and that does not work either (as expected).
Has anyone else encountered this? Advice?
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Michael1200 said:
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Click to expand...
Click to collapse
Thanks, Michael. I am using the latest SDK with current platform-tools, and don't have another computer. Tried several different cables, no luck. However, I've decided to forgo unlocking the BL and just set it up locked. I no longer use root nor custom ROMs and future TWRP is very unlikely so I'm going to stay boot loader locked for the first time in many years. Will see how it goes. I really have not needed/used it since OS10.
Thanks again.
Hey there,
I wanted to install a custom recovery on my MI8, I"m currently on MIUI Global 11.0.5.0 QEAMIXM, bootloader unlocked
I have tried several tutorials, such as:
https://www.the***********.com/how-to-root-xiaomi-mi-8-and-install-twrp-recovery/
https://www.getdroidtips.com/root-twrp-recovery-xiaomi-mi-8/
https://clickitornot.com/install-twrp-recovery-and-root-xiaomi-mi-8/
https://wiki.orangefox.tech/en/guides/installing_orangefox
https://forum.xda-developers.com/mi-8/development/official-orangefox-recovery-project-t4039531
everytime I reboot into fastboot, fastboot on my laptop doesnt recognize my phone, I mean if I type in "fastboot devices", it just isnt there, but adb recognizes my phone and also reboots into fastboot per command line....I just dont know what to do - I also used the all in one tool version 2, after reboot it just waits for my device which is already in fastboot..I just dont understand what I am doing wrong
I installed all needed USB drivers, my laptop recognizes my phone in device manager, everything is as it should be (also enabled ADB debugging on my phone)
If I type the command to flash recovery.img, it just get stuck there and nothing happens...
It is a very strange behaviour and I am sick of it right now - wasted the last three hours for this :crying:
Maybe someone could help?
Also I have several questions regarding finding the right ROM for my phone - I want MIUI 12 without any bloatware from XIAOMI, also want Viper4ANDROID if it is still a thing - also where I can read for some information regarding magisk? I never used it and I have no idea how it works, I just remember some things from my previous phones, such as Samsung Galaxy S5 or HTC EVO 3D, but this time it is all different...
I would be really thankfull, if someone could help me out
Hey, dear community,
First of all: I'm using Linux. The Version of Fastboot is 33.0.3p1-android-tools. The device I thought I'm experienced enough to install Lineage OS on is the Asus Zenfone 8. Yes, I asked google - for hours. And I think I am really ****ed now.
Cause the Smartphone (Asus Zenfone 8) was not cheap. And it does not boot anymore. I don't get in Recovery mode anymore. And I'm not able to connect via Fastboot anymore.
But let's start at the beginning.
I was pissed, cause my smartphone forced me to use google. Even if I skipped the Google-Part in the setup, it forced me to agree to send Google information. And I read it. They (quote: may) send Google **a lot** of data. Data I don't want to share - and I don't need to share IMHO! I didn't like to use such a intransparent Device anyway - but this convinced me to try this thing named LineageOS.
I thought about myself I am not a bloody beginner. I mean, I use Linux as my daily driver - for years. And my phone (Asus Zenfone 8) was in the list of supported devices - so I had to try it. I thought if I just install these tools, adb and fastboot, and do these things in the wiki carefully, step by step, what could happen?
And it worked. It worked to unlock device, to connect via adb, to connect via fastboot. It worked to flash the vendor_boot image, It worked to flash the recovery image. But then, just before I wanted to start with the "Installing LineageOS"-part, and therefore boot into recovery mode - it didn't work. I was stuck in the bootloader. I am. still.
There are the options "START", "Restart bootloader", "Recovery mode" and "Power off". No matter what I try to enter, the device restarts (at least it looks like) - It shows "Powered by android", and then the bootmenu again. And again. And again.
When fastboot was still connected, I tried to flash the images again. I even tried to boot directly into the recovery image using `fastboot boot image.img`. But it did not work. And then, the device even stopped showing up when I ran `fastboot devices` - it disconnected.
"Power off" is the only option, wich still appears to work (when not plugged in).
What should I do? Is it even still possible to do something? Please help me.
PS: It would be nice if you tell me, wether the tools or guides you recommend to me work on Linux, in a Windows VM or only Windows Bare Metal. I will do everything to bring my phone back, but it safes a lot of time, not to try using a tool in Windows VM if it only works bare metal anyway.
May be this thread could help you
https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Schaukelstuhl said:
Thanks, but my phone does not get into fastboot mode anymore, therefore I cannot connect to my phone via fastboot to flash new images.
Click to expand...
Click to collapse
I had the same problem. Only bootloader with no device showing with "fastboot devices".
Luckily I tried another cable. An Apple USB C cable behind a hub (screen) got fastboot working. Then I flashed android 13 beta.
And I am sure the other cable worked before with ADB and fastboot.
Try other cables and USB ports... Good luck!