Develop Bugs

[Guide][Fix] How to solve "Stuck in CWM or TWRP recovery boot loop"

I have seen some people suffering this issue like I did before and Other guys just offering the advice of " Use LG flash tools to flash to stock"
Yes, it could solve the problem. But it takes so much effort and hustle to fix such a easy issues.
There is always a easy way to solve a problem. Keep reading.
This method should work for LG Optimus G Pro using the same recovery. Like E980, E985, E986. I only try this on my phone (AT&T E980)
Issue:
Your phone keep boot into CWM or TWRP all the time, no mater what you did- factory reset, wipe system, install new rom. It just keep going into recovery all the time.
What might cause this:
You install recovery in your phone and when you are in stock rom, you accidently hit "check update" and " install update".
You might not remmeber you did that , and the system just pop up showing " update available", and you click it....That is how the nightmare starts.
How to fix
If you are using CWM, try this method: http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70 But I personally like the TWRP method below ( just flash TWRP over CWM and use the TWRP method bellow)
remember hit thanks to @chappatti
Following these steps:
1.a. If you are stuck on CWM OR TWRP boot loop DO NOT DO ANYTHING YET to the phone or anything. All you need to do is delete the "fota" file. keep reading
1.b. YOU MUST HAVE ADB INSTALLED AND WORKING.
1.c. Open cmd prompt as admin and run "adb devices". If you get
"List of devices attached
XXXXXXXX recovery" GO TO STEP 7.
If you HAVE adb installed and get no device output....continue from 2.
Otherwise, INSTALL ADB.
2. With the phone in CWM plug it into the computer.
3. Your computer MAY not see the phone. i.e you will get the ping noise for USB cnnection, but if you look under
COntrolPanel>>>>DeviceManager you will see a yellow exclamation mark. The next part I figured by trial and error.
If your phone is seen properly go to step 5.
4. If 3: although I installed the drivers again, if you had the phone working on adb before try this step:
4.b. Press and hold the Volume DOWN (volume decrease) button and hold the power button.
NOTE: I am not 1000% whether volume up or down did it. Try each one.
HOLD until the phone goes off and reboots. After the LG logo release the power. You will see black and white text as the phone tries to go into factory reset. It will ask if you want to factory reset...... SAY NO by pressing volume down button. During reboot my computer saw my phone and installed the driver. Phone was still on CWM recovery now.
4.c. If 4.b. did not work reinstall following drivers (attached rar): I do not know which worked, if any
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.1 0.1
minimal_adb_fastboot_v1.1.3_setup
UniversalAdbDriverSetup
LGPCSuite_Setup
http://www.mediafire.com/download/1j...nd STUFF.rar
5. These steps I got from this forum post here: I DO NOT CLAIM ANY CREDIT http://forums.androidcentral.com/t-l...ot-loop-2.html
6. Open cmd promt as administrator.
7. Run "adb devices"
You will get
"List of devices attached
XXXXXXXX recovery" Now you are good to proceed
Enter the following one by one
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
it will say xxxx info in and out or soemthing each time.
Type "exit" to leave adb shell.
Then "adb reboot". This will reboot your phone and all is great !!
If you are using TWRP, or the method above did not work for you, flash TWRP as your recovery, then using this TWRP method.
remember to hit thanks to @thecubed here is the post: http://forum.xda-developers.com/showthread.php?t=2451696
you can simply use TWRP's awesome "terminal command" option to run the following code
go to "Advance" " Terminal Command", select the current folder( root folder), and type the following code:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
I took no credit for these method, they are work of other XDA members.
Hit thanks if any of us help you solve your problem.

This is VERY good work! THANK YOU!
Sent from my LG-D415 using XDA Free mobile app

[SOLVED] Soft-bricked my device

Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.

with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue

Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.

gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back

rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.

have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815

leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.

gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out

gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.

I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..

rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.

AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.

unable to adb reboot recovery reinstall (unable to reinstall twrp)

since this fone was having this issue i decided to try and restore from a working backup:
http://forum.xda-developers.com/g4/help/unable-to-make-phone-calls-dialer-t3278827
i am starting to think that this fones hardware is broken/defective somehow. the key combo to boot into recovery never works.
its supposed to be power+volume-down but it just boots normally.
power+vol-down/release power for 1 second goes into the erase all data: yes/no screen.
whether using android-5.1 or cyanogenmod, adb devices returns nothing; we tried on both windows and fedora; we enabled developer options/adb debugging/oem unlock.
so to test whether the original os could make fone calls i did a twrp wipe/restore of a previous backup. when it booted up it was very unstable/unusable; took a few minutes to respond to touches sometimes; process system has quit errors; random restarts; ...
no apps could launch so that meant i couldnt use quick boot to reboot recovery. adb and key combos dont work so there was no way to get back into recovery.
i put the fone in download mode (volume-up while plugging in usb) and we used LGUP_8994_DLL_Ver_0_0_3_23.msi/LGUP_Store_Frame_Ver_1_14_3.msi to install H81120i_00_0201.kdz which is the lg version of googles version of android-6.0. and we were able to make a fone call. we wanted to boot into twrp to backup but quick boot said that we are no longer rooted. ironically, adb devices now shows the serial-number of the fone so i did sudo adb reboot recovery but when it rebooted instead of going to twrp it showed a green android with a spinning blue cube thingy and rebooted into lg/google-android-6.0 where i had to sign/register for the first time and all our apps/settings were gone.
we origianlly installed twrp using the send_command.exe command on windows awhile back but it no longer works. we installed LGUnitedMobile_Win_Driver_Ver_3.14.1.exe; i run ports.bat and it tells me that the diag port is on COM5; i run Send_command \\.\COM5; it shows me the linux su prompt: #, but when i type in ENTER, it exits back to the windows-dos prompt (i also tried without first typing ENTER, if i try to run something like ls or whoami, it will display: fail).
do all these models have adb/recovery disabled or is this particular unit fubar in that regard ?
any alternative ways to install twrp/ cyanogenmod ?

It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.

bbenz3 said:
It is my understanding according to autoprime's thread that you must reinstall twrp after you install the kdz as it wipes that partition as well.
Click to expand...
Click to collapse
thanks, how does one install twrp without using send_command.exe.

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...

oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...

now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?

Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there

First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:

Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)

Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .

Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen

TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.

Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work

TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?

Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)

Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?

TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..

Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)

On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work

in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

ADB Waiting For Device, Device Stuck On Firmware Update Screen

LG G3 D852
Hey everyone, here's the summary of my whole situation: I've been trying to toy around with some roms for an old phone I had sitting around. Long story short, good phone busted so now back to this one.
Anyways, while trying to install literally every rom (except the one installed already, which I keep flashing to be able to text and all), no matter what ROM it was, it gave me an error saying, "Error executing updater binary in zip". I did some searching and read that it was because TWRP was outdated. Havent used this phone since 2016, so everything on it is outdated, made sense to me.
THIS IS WHERE MY REAL TROUBLE BEGINS!
So, while trying to update TWRP, I tried using different methods such as the Official TWRP App, as well as Flafishy, but all failed.
>>Booted into TWRP recovery, tried to update that way using the image file, followed instructions on the TWRP site, and it said it succeeded! But, when I went to power off and back on into recovery to make sure it went well, it started up in Fastboot Mode instead, and the only way to get that screen off was to take battery out. So now, every time I boot to recovery, it enters Fastboot Mode. However it CAN start up normally without issue.
>>>>The next issue I'm having is with updating TWRP through ABD.
After noticing it was only going to let me use Fastboot, I started the phone, made sure root access was given to Apps & ADB as well as made sure that Android Debugging was enabled.
Then, booted back to Fastboot screen and tried to flash the recovery file using the commands in cmd.
Made sure cmd was opened in the correct directory with the TWRP file, and after typing the flash command, command prompt sits at "Waiting for device" and the device doesnt respond, sits at the firmware screen completely frozen.
Here is what I typed for cmd;
C:\Users\Daqo\Desktop>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.199s]
finished. total time: 0.202s
C:\Users\Daqo\Desktop>fastboot flash twrp-3.0.0-0-d852
< waiting for device >
^^^Gets stuck here^^^
****Please note that after typing the bootloader command, the phone reboots normally and I have to manually press "Reboot to Bootloader" from the popup reboot screen (holding power button) in order to get to the firmware screen. I have tried rebooting to bootloader before and after typing the command to flash the file****
Any help is greatly appreciated