Develop Bugs

LG G3 Stuck in a Boot Loop. Someone please help me

I think I bricked my G3 :/
I tried usual methods but couldn't get into recovery or download mode, then a few days ago I realized I could get it into this fastboot mode by holding volume up and plugging into USB as you would normally do to get into download mode but you have to hold up for a minute or so (it shows the download mode icon for a few seconds and then goes to fastboot) when in fastboot it connects to the computer and shows in device manager as "android device" and the phone says "processing commands" So I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2785089 to return it to stock, but I couldn't get it to show up in the LG software.
I read some forum posts about fastboot mode and found that by using the command "fastboot boot twrp.img" (the recovery image I downloaded) in command prompt it would send it to the phone and the phone would display some info and then reboot into TWRP, from here I tried to install a correct rom but the installation starts and there are some errors and then it hangs. I also tried the command "fastboot flash recovery twrp.img" but it fails. This is as far as I have got with it.
It came to me in this condition but the previous owner said he was running Cyanogen and it was working fine until he tried to update it with a nightly build. I suspect he might've tried to install the wrong rom for the phone or the rom was corrupt.

ou could try to revive the phone doing a testpoint and then use boarddiag tools (look in xda thread).
Here is how to make a testpoint: http://forum.xda-developers.com/showpost.php?p=65002893&postcount=17

Tried flashing CM13, now can't enter normal boot

So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks

Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.

ROOT Elephone S7 4gb on Windows 10x64 at last!

For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!

I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk

When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?

vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success

I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?

stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!

dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look

During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...

Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)

Firmware Update

Recently i've unlocked my bootloader in order to install a custom ROM. Everything went fine until i flashed twrp image. Whenever i try to get into recovery ( power+vol up ) it pops a window saying "Firmware Update". In the cmd log it says that recovery flashed successfully. I've enabled OEM unlocking and adb in the dev settings. BL is unlocked. Device was connected to the PC at the moment of flashing ( obviously ) aswell as at the moment of entering the recovery.
Please help me find a solution, thanks.

fastboot flash recovery twrp.img and then enter recovery by holding power + vol down (to get into bootloader) and then choose recovery mode and enter.

Exactly what Przemcio said. Flash the TWRP from your PC using fastboot, and then boot into it from the bootloader. I never use Pwr+Vol_Up, I always use Pwr+Vol_Dn to get into whatever I want.

Vol up is for LG Flash tools only.
I flash recovery via fastboot. Press vol down
Sent from my Pixel using Tapatalk

yeah, it's orange encrypted and now i have to decrypt.

i just can't bypass this message "your device cannot be checked for corruption". Whenever i try to choose the recovery this pops up and then phone reboots. I flashed stock google image for nexus 5x and it didn't solve the issue, nor fomratting data thru adb.

How to stop Stock ROM overwriting the Custom Recovery?

I was trying to flash a Custom Recovery(TWRP) on my Friend's phone(Realme 3) It was officialy supported by TWRP and was listed on their website so I downloaded the Custom Recovery. Then I unlocked the bootloader of his phone but yes a strange thing happened there after it asked for pressing the volume button to be pressed it unlocked the bootloader but after that there was option "Select boot type"(Not sure what it said). It had three options Boot to Bootloader, Boot to recovery and last Normal boot and also there was a arrow on the bootloader option. And there were some instructions something like volume up for select and volume down to move. But I tried every button but the arrow was stuck on the bootloader option. So I connected it to my device and used the "fastboot reboot" command to restart the device after restarting at the realme logo it was saying "You are unlocked you cannot be trusted" But after it booted normally and the phone was Factory Reset. After this in the Developer options the OEM unlocking was grayed out saying Bootloader is unlocked. Ok so we were successful in unlocking the bootloader. After that I pasted the twrp img file in the platform tools directory and put the command adb reboot bootloader and after the device was in bootloader I used the command fastboot flash recovery name.img to flash the recovery. It said sending and then writing in my terminal after that I used the command fastboot reboot and the the key combinations(power+volume down) for the device which used to get into recovery for that phone but this time instead of going into recovery it was in the bootloader. So again I tried fastboot reboot command and this pressing the power+volume up but the phone booted normally so this time I tries adb reboot recovery but it booted into stock recovery so again I tried flashing the recovery and tried using fastboot reboot recovery but it didn't work. And yes I know that after flashing the custom recovery the phone should first boot into the recovery but as I said neither the key combinations nor the fastboot reboot recovery command so what can I do to prevent the system from overwriting? PS: Sorry for long paragraph...