So my LG G2 popped up a message telling me there was an update available (yay lollipop). Having TWRP installed I didn't take the update at first. However, I found an app that allows you to switch between a custom recovery and a stock recovery. When I switched to stock, I booted into the recovery to test it and it worked. So I went ahead with the OTA. Instantly, my phone was stuck in fastboot mode and I cannot get into download mode or anything else at all. Any options anyone?
I'm trying to use fastboot with adb to re-flash the stock firmware now. When I open command prompt in the platform-tools folder and type in "adb devices" it shows none. When I type in "fastboot devices" it shows a question mark. If I type in "fastboot reboot" it will communicate with the device and reboot it. I can't tell if I have a driver issue or what the problem really is.
Related
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
hey guys i have a question.. i made a total n00b mistake and now i am not sure what to do..
I have a htc one s
-i rooted the phone and put twrp 2.8 the newest one then i tried to load a custom rom.. i read somewhere on line that you did not need s off to do this so i tried and now everytime the phone boots it loads the htc screen but goes to a black screen which is kind of dim .. anyway my bootloader is unlocked its version 2.15 and i can get back in to my recovery and mount it i tried several roms but none work.. i was wondering if someone here has a stock rom or something that can get my phone to boot in to a os.. i have tried using fastboot to try and s off but everywhere i read it says u need debugging on my drivers are installed correctly but when u do adb devices it shows empty space.. ive tried many drivers even the google generic i cannot get it to work for the life of me... any help will be appriciated
cheers
Sam
Well let's take it easy. There were some things you've missed when reading so that's why you run into problems.
First thing you missed is that YOU MUST FLASH THE KERNEL IN FASTBOOT if you're S-On. That is EVERYTIME you flash a ROM.
Second, when you're in fastboot, you won't have "ADB devices" command working, you'll have to use "fastboot devices" command instead, ADB does not work while in fastboot.
What you'll have to do is like this:
1. Take any ROM you'd like to flash, place it on your sdcard (while you're in recovery you can mount sdcard to be accessible from pc)
2. Extract from the rom and save it on your pc (in the same folder where adb/fastboot commands are, usually /android-sdk/platform-tools) the "boot.img" file that's in the root of the ROM zip. That'll be called generic "the kernel".
3. Flash the ROM in recovery
4. Reboot to bootloader then while still connected to pc via USB, select fastboot mode. On your screen the "fastboot USB" will be shown.
5. Check if fastboot drivers are installed and fastboot commands are working by issuing "fastboot devices" command. If it'll not return your device then check if drivers are installed properly and you are not using an USB 3.0 port on windows 8.1 (were reported some issues with this configuration).
6. Having fastboot working, open command prompt in the location where fastboot is (and where you have saved the boot.img file) and issue the command: "fastboot flash boot boot.img"
7. Reboot
Now your new ROM should boot and work. Pay attention to choose the right ROM for your hboot and don't forget to do these steps EVERYTIME you're flashing a ROM.
If you're still looking for a stock ROM to flash, there's a thread with all RUUs linked, choose the one for your carrier or model type and run that one but I guess you won't need that
Good luck
Sent from nowhere over the air...
I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
threemor said:
I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
Click to expand...
Click to collapse
You probably don't have ADB enabled on your OPO, but you don't even need it for this. "adb reboot bootloader" is just a handy way of rebooting to fastboot without shutting down and holding the up volume button while turning it on. Once you get into fastboot by doing that, continue on as the guide says! (i.e. "fastboot flash recovery xxxx.img")
Hey folks,
i have a problem with my shieldtablet. The fastboot doesn't work properly. I cannot load anything via "fastboot flash blablabla.img". Minimal ADB and Fastboot just shows "waiting for device" and if i check the devices via "fastboot devices" is just shows nothing but the normal command prompt.
Then i did a mistake and flashed the twrp 3 version with an older one, so i am unable to enter the recovery-mode. If i chose Recovery Mode via bootloader (or if i restart the tablet into recovery mode) it has a short bootloop and then after some trials it starts normal into Blisspop.
How could i flash this without the fastboot? Is there any trick i could use?
The tablet is unlocked. I had several custom-roms installed. Currently Blisspop 6.4 without playstore.
That looks like your PC is not seeing your tablet. Boot into fastboot mode, connect it to your PC and look in Windows device manager for the device.
Thanks a lot! ADB worked fine on Win10. Last time I flashed the recovery was on my old Win7-System. It seems, that the Upgrade deleted just the fastboot drivers.
One last question: is it normal, that if i chose the fastboot protocoll entry on the bootloader, that it restarts the bootloader?
Yes, that's normal. The menu entry is redundant because when you see it you are in fastboot mode already.
Hey !
I bought a used LG V10 H900 from market yesterday. It's on Android 5.1.1 with software version H90010f. I'm not using an AT&T sim card, ofc. So I assume it had to be network unlocked (not sure about it. I'm new). Anyways, I wanted to update it to MM, found a thread showing how to force update it with ADB. But I realized the download mode or fastboot mode isn't there. "adb reboot download" simply reboots it, so does "adb reboot- bootloader" and "adb reboot fastboot". I assume download mode and fastboot mode are missing. What should I do?