Hi! I've just installed Cyanogenmod 14.1 in my LG g3 d855 and i wanted to install gapps. I have installed TWRP and it worked fine (i could install cyangenmod) but now when I reboot my device it gets into a blue screen and i can't do anything else (I have to remove the battery to restart the device).
So I decided to reinstall TWRP. First I tried from the app, but it didn't work so I also tried using ADB. I have installed the drivers and I am able to find the phone using the ADB and get into the bootloader using "adb reboot bootloader" in the CMD (I am using W10). But when it gets into the bootloader i cannot do anything else, if I write "adb devices" apears "List of devices attached" and nothing else, and if I write"fastboot flash recovery twrp-3.0.2-0-d855.img" apears " < waiting for device >" and I cant do nothing else....
[SOLUTION] It was simple, I just had to take the SD out before entering recovery.
Related
I am on Wolla 5.0 and elementalx 6 something but I don't think these caused the stuck as the phone had been working fine.
Right before the phone was stuck, I updated an app called Lucky Patcher; I then restarted the phone and it's been stuck.
Under Devices manager My HTC shows this device is working properly.
M8 was detected by Adb. But when I typed commands such as "fastboot reboot bootloader" or "fastboot reboot recovery" ADB shows and stuck at "Waiting for device".
it has been like this for two hours.
Please help.
Whileitlasted said:
I am on Wolla 5.0 and elementalx 6 something but I don't think these caused the stuck as the phone had been working fine.
Right before the phone was stuck, I updated an app called Lucky Patcher; I then restarted the phone and it's been stuck.
Under Devices manager My HTC shows this device is working properly.
M8 was detected by Adb. But when I typed commands such as "fastboot reboot bootloader" or "fastboot reboot recovery" ADB shows and stuck at "Waiting for device".
it has been like this for two hours.
Please help.
Click to expand...
Click to collapse
That's what you get for using Lucky Patcher I guess. Get rid of it and stop ripping developers off.
Okay........................ the problem is you are using fastboot commands while booted to system would be my guess.
Try this:
adb reboot bootloader
You can only use fastboot commands while booted into bootloader. While booted into system (into your ROM or recovery) you can only use adb commands
xunholyx said:
That's what you get for using Lucky Patcher I guess. Get rid of it and stop ripping developers off.
Okay........................ the problem is you are using fastboot commands while booted to system would be my guess.
Try this:
adb reboot bootloader
You can only use fastboot commands while booted into bootloader. While booted into system (into your ROM or recovery) you can only use adb commands
Click to expand...
Click to collapse
Hi, I already tried the adb commands (reboot, reboot recovery, reboot bootloader) along with the fastboot ones; the adb ones didn't even show "waiting for device", instead a new command line was show, i.e. as if it was not aware of the adb commands.
I let the battery ran out (nothing I could do about it anyway) and after a full charge, the phone is now working with god knows why/how. The app is also working fine and no further issues happen. I will keep an eye on it and see how it goes.
Although phone is working, I am still very curious with what exactly happened...
I've been trying to flash TWRP recovery to my rooted LG G3 D855 (running 4.4.2 KitKat). I used the "Bump" method (thread) since I don't have an unlocked bootloader.
I tried the ADB method in that thread, I tried the Flashify method, and I tried the Official TWRP App. Each time, the recovery flashed correctly. But when I attempted to reboot into recovery (using the method in the linked thread, or in the case of the apps, they prompted me to reboot into recovery), my phone didn't bring up TWRP recovery or even the stock recovery. It just brings up "fastboot mode started". It's not stuck though, it boots normally when I pull the battery and power on.
I also separately tried rebooting it into fastboot mode with it plugged into my computer. When I entered "adb devices" into the command prompt, the device came up. Then I rebooted it into fastboot mode and entered "fastboot devices" - then nothing came up. I entered some other fastboot commands and it said "< waiting for device >". So it appears I can't issue normal fastboot commands either.
Any thoughts on how I can succesfully flash TWRP? Thanks.
i have installed my TWRP via this app -- https://ulozto.sk/!lisJevpDG1oS/recovery-d722l-apk
try hope itll help you
Well, somehow you failed to install it. Upgrade to LP (preferably v21C) and try this
I tried to root my huawei g8 using twrp, i even took the backup, when i installed SU and tried to reboot it showed "your device is not rooted, swipe to root"...i did what it said...Now the phone directly boots into twrp and show no os installed.... I tried to flash a custom rom but it wont happen....i even tried adb sideload but it shows no device connected on the commnd prmpt(on pc)...Is there any way to recover??? :crying:
Here's my situation -
I was using my Whyred (Redmi Note 5 Pro) and it suddenly hung, so i tried forced reboot by long pressing the power key. But after that, the device never booted. It is stuck at MI bootlogo. I tried going to recovery, the recovery is also stuck at the Recovery Bootlogo (ie, OrangeFox Recovery Project logo as i am using OrangeFox Recovery), then i tried going to Fastboot and it shows a blank screeen with only the LCD backlight.
Device gets detected in 'fastboot devices' when in fastboot blank screen and also gets detected in 'adb devices' as a recovery device when stuck at recovery logo from a windows pc. The Bootloader was unlocked and i was using a custom ROM, Havoc OS Mod - last Pie build with OrangeFox Recovery and was rooted using Magisk. I didn't update the rom or firmware since past 4-5 months. I also tried "fastboot boot recovery.img" with 3 different recoveries (twrp,orangefox and skyhawk), but all of them gets stuck at their respective recovery logos and gets detected in adb devices on pc.
I have important files on my internal storage which i want very badly. It wasn't backed up (my bad:crying::crying. So i want to copy/backup the internal storage of the device to my pc before attempting to repair the device and after backing up i want to fix the device.
My Problem -
When the device is struck at recovery logo, i connect it to my pc and it gets detected as a recovery device on running "adb devices" and i can use adb shell. on writing "ls" in adb shell all the different directories gets listed but when i "cd" to storage,sdcard and some other directories they are empty. when i type 'su' in adb shell,it shows "/sbin/sh: su: not found" . "adb root" also doesn't work as it shows to allow permission on device and then terminates. I read online that i need root access in adb to see system files in adb shell which i am not able to get as the device is stuck at bootlogo. i want to use "adb pull" to copy my internal storage to my pc before attempting any repairs.
I have attached the screenshots of "fastboot getvar all" command.
So, looking at my situation, how do i backup my internal storage to my pc? I really want those files on the internal storage.
Is there any way i can get/backup those files from internal storage from fastboot or adb or any other way?
Also, after backing up, how do i fix my device?
It was running fine without much problems before this. The storage was pretty close to being filled up, other than that i don't remember having any other problems with the phone. It hung suddenly while using and after forced rebooting, never booted again. how do i fix it from fastboot or recovery? i am thinking about formatting the device from fastboot and then trying to boot the recovery and then rom. I didn't try it as i wanted to backup internal storage first. Some people in other posts say that they weren't able to fix their device in similar situations. Please suggest the correct way to fix my device.
Please read my problem and help me to fix it. Your help would really mean a lot to me.
This is my first post on xda-developrs so please let me know if am making any mistakes.
Fastboot getvar screenshots (can't post links as i am new user)-
ibb.co/Q82JWdN
ibb.co/4R8j9Jd
ibb.co/sK5Km57
ibb.co/1JGSrdn
hello,
I need help, my device is not being recognized by adb in fastboot mode, I've tried several versions of adb (my boot-loader is unlocked) when it's on it recognizes normally, but when I do the command to enter fastboot mode, it enters and adb stops recognizing it,
when I do "adb devices" there isn't even a device connected, but the pc recognizes the device normally modelo (XT1952-2) android 10 .
but that's not the strangest thing, even without recognizing it, I can still install TWRP, but I can't even use a command (flash), that is, I can't install TWRP permanently, I always have to put it manually, and TWRP It doesn't work either, I can only install it but it doesn't work, I tried to install root via magisk using boot.
img from my room with the magisk modification but as the flash commands don't work it gives an error and whenever I try I have to reinstall the rom using "Rescue and Smart Assistant", and I've tried using masgisk.zip in TWRP, it installs I say it's all right but when I go to see it's as if nothing had been done and the magisk still doesn't work
Change the usb port to 2.0 not 3.0
Or try wirelessly.