Related
When I start my P6 the Huawei Logo shows up shortly, but then the screen turns black. (The phone is still on)
When I try to shut it down, it always restarting and stucking at the same point.
Is there a way to force the p6 into fastboot? (I want to flash the orginal recovery)
Holding the VolumeDownButton and connecting the wire may should work, but therefor the P6 has to be off.
Can anybody help me?
Infos about my BRICK:
My phone had the Chinese B120 Firmware and was rooted.
I booted into Recovery over TouchRecoveryInstaller-v1_01.apk
There I flashed:
1. TWRP_Recovery_R03.1.zip,
2. EMUI2.3V100R001C00B014EDGE-U00-Beta.zip (Created out of UPDATE.APP)
I thought that the firmware may has overwritten TWRP, so I flashed TWRP again.
At this moment my P6 froze.
Mixer0 said:
When I start my P6 the Huawei Logo shows up shortly, but then the screen turns black. (The phone is still on)
When I try to shut it down, it always restarting and stucking at the same point.
Is there a way to force the p6 into fastboot? (I want to flash the orginal recovery)
Holding the VolumeDownButton and connecting the wire may should work, but therefor the P6 has to be off.
Can anybody help me?
Infos about my BRICK:
My phone had the Chinese B120 Firmware and was rooted.
I booted into Recovery over TouchRecoveryInstaller-v1_01.apk
There I flashed:
1. TWRP_Recovery_R03.1.zip,
2. EMUI2.3V100R001C00B014EDGE-U00-Beta.zip (Created out of UPDATE.APP)
I thought that the firmware may has overwritten TWRP, so I flashed TWRP again.
At this moment my P6 froze.
Click to expand...
Click to collapse
Try rebooting holding Vol up + Vol down + Power for 10+ seconds. This should send you to the stock recovery to flash the dload/UPDATE.APP
recovery defekt
abequer said:
Try rebooting holding Vol up + Vol down + Power for 10+ seconds. This should send you to the stock recovery to flash the dload/UPDATE.APP
Click to expand...
Click to collapse
I tried this, but the recovery seems to be destroyed too.
The phone switched off over night.
I tried to connect it to my pc while holding VolDown.
I'm not sure if it worked. Now my phone shows the "Huawei Ascend"-logo all the time and the LED is blinking red.
My pc recognized my phone as "Android Sooner Single ADB Interface",
but I can't find it using ADB:
C:\Users\Mixer\Desktop\android_tools\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Mixer\Desktop\android_tools\adb>
Mixer0 said:
I tried this, but the recovery seems to be destroyed too.
The phone switched off over night.
I tried to connect it to my pc while holding VolDown.
I'm not sure if it worked. Now my phone shows the "Huawei Ascend"-logo all the time and the LED is blinking red.
My pc recognized my phone as "Android Sooner Single ADB Interface",
but I can't find it using ADB:
C:\Users\Mixer\Desktop\android_tools\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Mixer\Desktop\android_tools\adb>
Click to expand...
Click to collapse
Then you are already in fastboot mode...
From there use:
fastboot devices - You should see your device strangely named with a lot of signs.. Don't worry, it means your phone is there and recognized...
fastboot flash recovery recovery.img - this will flash stock recovery to the phone and after completed do:
fastboot reboot
Make sure you have fastboot.exe and stock "recovery.img" in the same folder as adb.exe
If you need stock 4.2 recovery you can get it here:
http://www.androidfilehost.com/?fid=23252070760973876
Just unpack and extract recovery.img...
Once the recovery is installed you can get into it by the 3 button combo...
worked
jimbo77 said:
Then you are already in fastboot mode...
Click to expand...
Click to collapse
Thanks alot.
What a stupid mistake...
You made my day
My p6 is working again. <3
I can't boot up my device it's have blink sleeping android error. (my device is ze551ml running WW_2.19.40.22 firmware and never ever ROOT!!! )
I tried hold power button and press volume up button but its doesn't work.
I also can't access to recovery mode too.
It's have the same blink error message and can't pass by hold power button and press volume up button.
Oh but i can access to fastboot page.
and my computer don't recognize my phone at all(i already install driver)
Before this problem happen I get in to recovery mode try to wipe cache but i miss press and i selected "apply update from adb"
and that time my phone doesn't connected with PC. I don't know what to do so I turn off my phone.
then I open recovery mode again and select wipe cache then I go out to take a bath.
I came back and see my phone is off so I boot it.
It's booting about 2-3 mins and nothing happen so i go to recovery mode again but this time they have problem like i explain before(blink error message that can't pass by hold power button and press volume up button)
So anyone have a solution for my problem. please I really need your help!
Sorry for my bad english
Hi,
I had this when I went to wipe my system cache and it failed. Your best bet, especially if you can't get into recovery is to fastboot flash the recovery again if you have an unlocked bootloader.
If you don't you'll want to unlcok the bootloader and follow the instructions for using ADB if you're new to it: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
How can I unlock my boot loader when i can't even open up my phone.
stultus136 said:
How can I unlock my boot loader when i can't even open up my phone.
Click to expand...
Click to collapse
If you hold volume down and power, it should go to bootloader first, then you have your choices for recovery....Get it to the bootloader screen, then run the commands to unlock it...
Could you please tell me everything step by step on how to cure my phone?
I'm very noob.
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
stultus136 said:
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
Click to expand...
Click to collapse
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Same Problem
smokinjoe2122 said:
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Click to expand...
Click to collapse
Hey I'm having the same problem, how'd you get the computer to recognize that the phone was plugged in? My computer does not recognize that the phone is on when I have the flashing error screen, so ADB doesn't recognize that there is a device connected.
Hi,
I had the exact same problem, and I managed to boot up again thanks to you!
What I did :
Install ADB and Drivers
Boot my phone into Fastboot (Power+Volume Up at boot, keeping VolumeUp button pressed while booting). Don't go into any menu (do not select recovery or so). At this point your computer should recognize your Android phone when you plug it in through USB.
Open up a cmd with admin rights, navigate to adb install path by typing : cd C:\adb
Then type : fastboot erase cache
It should trigger an action on your device, and the prompt should display sth like "Cache successfully erased" (I don't remember exactly)
Finally type : fastboot reboot, press volume up while booting again, and access Recovery like usual!
Now you can try wiping your partition cache again.
Worked like a charm for me! Thanks a lot
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
EDIT: IT FIXED ITSELF. I just had to let it sit for like 15 hours. It's ridiculous that it took that long.
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
Click to expand...
Click to collapse
Same thing happened for me. Had to wait 14 hours and it finally completed.
LiquidPlacidity said:
Same thing happened for me. Had to wait 14 hours and it finally completed.
Click to expand...
Click to collapse
Haha whaaaat? 14? That's crazy. I might try it though, I'm running out of options. I'm trying to clear the bootloader cache and reflash the firmware via fastboot, but I keep getting "FAILED" messages that say I don't have permission. I can't do **** with this phone right now.
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
Click to expand...
Click to collapse
The same happened to me. In htcmania (an Spanish web like xda) there's a tutorial that worked for me:
ht tp://w ww.htcmania. com/showthread. php?t=1028393 (erase the spaces)
You don't have to follow all the steps. Just run the indicated cwm bat, wipe cache and reboot. It worked for me and without losing any data. I hope it helps you. If you have any question about the language, send me a message.
The solution for the OP and me was to simply wait it out. As LiquidPlacidity said, it can take over 12 hours for this to complete, it seems to take longer the more data you have on the device. OP messaged me saying it took them 12 hours, as LiquidPlacidity said it took them 14 hours, and for me it took a total of 22 hours to complete. My device was nearly full, but this is unforgivable on the part of Asus, they really need to fix this.
This happened to me I flashed recovery.img stock firmware recovery I downgraded to unlock bootloader then tried it again and it done it in 10mins
Just an update for anybody that finds this thread: I just had to let it sit for a stupidly long time. Like, maybe fifteen hours. I found somebody else that had to let it sit for 22 hours.
Any update to this problem !
xlaxplaya said:
Just an update for anybody that finds this thread: I just had to let it sit for a stupidly long time. Like, maybe fifteen hours. I found somebody else that had to let it sit for 22 hours.
Click to expand...
Click to collapse
I bought an Asus phone same like you and the same problem is happening ! USB debugging < I satule you
Solution found !
I've found a solution for this problem
All you need to find is a same device which is normal or BUY a new one ! OR BEG,Borrow, or steal from a friend
Find a asus zenfone 2 from a friend and enable usb debugging
Download intel driver
Just google it
Download Abd driver installer from the link bellow
Just google it
Just enable the usb debugging mode from the phone which you found
Open the adb driver intaller and fetch the abd driver directly from the installer for your asus phone
After that, download the following adb interface
Google it like " Abd interface for asus fastboot"
Then, extract the file , hold shift and right click the folder you will see a option in cmd option
Click that and a cmd window will be opened
Turn off your phone
Hold volume up and power button
After the phone vibrates realease from power button and keep holding volume up button
Boot loader will open and press volume up until you see "continue in fastboot mode"
Keep it the mode and connect your device to pc
It will directly intstall usb driver and adb driver after that
Just go back to your pc and type "fastboot format cache" and the process will continue
You will know when the process is over from the cmd in your pc
After that reboot your phone and you will still see the error
Click power and volume up button and the recovery mode will apear
Just wipe your data and every thing is going to be ALRIGHT
It is turning off after 10 minutes, how can I make it to 15 hours if it is turning off.. ?
have the same problem with my device too... i removed my battery once because i couldnt boot into recovery mode without turning it off...but its still in the erasing screen...will removing the battery cause any problem?
It's actually helps
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
EDIT: IT FIXED ITSELF. I just had to let it sit for like 15 hours. It's ridiculous that it took that long.
Click to expand...
Click to collapse
Same happened to me, but i found the way to fix it quickly. First of all i have find out that to properly wipe zenfone 2 , you have to firs wipe it from android software by going to Settings - Backup & reset - Factory data reset, and then wipe it from recovery menu and it will wipe it with normal speed it still will take 10-15 minutes but it's not 22 damn hours!!!
SO, The thing is that you still can get in fastboot mode and if you'll connect device to PC it will detect it. To get in fastboot you have to turn off your device(to do that you need to hold button "volume up" + "power" button, hold them untill phone is turned off,while you doing that the phone must be disconnectet from PC or it woun't turn off) then you press and hold "volume up" button and press and hold "power" button untill you feel the double vibrating and then you gonna let go the "power" button but still hold "volume up" button and then the menu will apear on the screen, you are in fastboot mode.
At this moment i'm sure that you have all Android (and official asus)drivers installed and all platfom-tools installed so i'm not gonna tell how to install it and i'm expecting that you know how to use platform-tools.
So... you go to cmd and from there to adb(usualy you do it by typing: cd c:\adb ) make sure that fastboot.exe is in adb folder, if not then download fastboot.exe and copy it in adb folder, then you type : ' fastboot devices' to see if PC deteced device you'll get 'F4AZFG04X560 fastboot' and it means that device is detected, then you type :
- ' fastboot format cache' wait till it's done
- 'fastboot erase userdata -w' wait till it's done
- 'fastboot erase system' wait till it's done
- 'fastboot erase recovery' wait till it's done
By doing all of these commands you're kind of doing factory reset by yourself.
Then you put recovery.img(recovery.img from OTA "older" than you had... if you had 165 then you take 164 or 139, or even OTA 97, it worked for me fine) and last firmware, for zenfone2 (from official asus site) in folder with adb and rename firware to 'update.zip' then run cmd from this folder and you can check if PC detected your device, by using command ' fastboot devices' and you'll see something like 'F4AZFG04X560 fastdoot' than you type command: ' fastboot flash recovery recovery.img' than you'll see :
" C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.684s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.193s'
then you choose recovery menu, by pressing "volume down" button, then phone boots it recovery mode and you see little droidbot "error", then you press and hold "power" button and press "volume up" button apears recovery menu, choose "apply update from adb", device is still connected to PC(if not, connect it), type in adb : ' adb sideload update.zip' wait till it's done(about 20-30 mitutes you'll see load in cmd)when it's done choose reboot in recovery menu... that's all.
P.S. sorry for my English it's not my native language.
The erasing has already started.
Now what should i do to make it quick?
It is really really bad. It is taking very long time.
Please advice
---------- Post added at 01:42 PM ---------- Previous post was at 01:22 PM ----------
I spent too much money on this useless phone. There are so many companies who give quality phones with quick os updates.
agriz said:
The erasing has already started.
Now what should i do to make it quick?
It is really really bad. It is taking very long time.
Please advice
---------- Post added at 01:42 PM ---------- Previous post was at 01:22 PM ----------
I spent too much money on this useless phone. There are so many companies who give quality phones with quick os updates.
Click to expand...
Click to collapse
Turn off device and follow by steps o described
what i do when the phone stuck on erasing :
1. At least wait for 30 minutes and make sure you have 60%+ battery before resetting or erasing the phone.
2. Turn off by pressing power till the phone turn off
3. Go to recovery mode by pressing volume + and power button together, and then select recovery by pressing volume + or volume -, the press power button to confirm it.
4. Done. It will continue erasing, but it just take 1-2 minutes then the phone will reboot.
I'm just sharing what i have done when this happen. If something happen to your phone, don't blame me
Testerov23 said:
Same happened to me, but i found the way to fix it quickly. First of all i have find out that to properly wipe zenfone 2 , you have to firs wipe it from android software by going to Settings - Backup & reset - Factory data reset, and then wipe it from recovery menu and it will wipe it with normal speed it still will take 10-15 minutes but it's not 22 damn hours!!!
SO, The thing is that you still can get in fastboot mode and if you'll connect device to PC it will detect it. To get in fastboot you have to turn off your device(to do that you need to hold button "volume up" + "power" button, hold them untill phone is turned off,while you doing that the phone must be disconnectet from PC or it woun't turn off) then you press and hold "volume up" button and press and hold "power" button untill you feel the double vibrating and then you gonna let go the "power" button but still hold "volume up" button and then the menu will apear on the screen, you are in fastboot mode.
At this moment i'm sure that you have all Android (and official asus)drivers installed and all platfom-tools installed so i'm not gonna tell how to install it and i'm expecting that you know how to use platform-tools.
So... you go to cmd and from there to adb(usualy you do it by typing: cd c:\adb ) make sure that fastboot.exe is in adb folder, if not then download fastboot.exe and copy it in adb folder, then you type : ' fastboot devices' to see if PC deteced device you'll get 'F4AZFG04X560 fastboot' and it means that device is detected, then you type :
- ' fastboot format cache' wait till it's done
- 'fastboot erase userdata -w' wait till it's done
- 'fastboot erase system' wait till it's done
- 'fastboot erase recovery' wait till it's done
By doing all of these commands you're kind of doing factory reset by yourself.
Then you put recovery.img(recovery.img from OTA "older" than you had... if you had 165 then you take 164 or 139, or even OTA 97, it worked for me fine) and last firmware, for zenfone2 (from official asus site) in folder with adb and rename firware to 'update.zip' then run cmd from this folder and you can check if PC detected your device, by using command ' fastboot devices' and you'll see something like 'F4AZFG04X560 fastdoot' than you type command: ' fastboot flash recovery recovery.img' than you'll see :
" C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.684s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.193s'
then you choose recovery menu, by pressing "volume down" button, then phone boots it recovery mode and you see little droidbot "error", then you press and hold "power" button and press "volume up" button apears recovery menu, choose "apply update from adb", device is still connected to PC(if not, connect it), type in adb : ' adb sideload update.zip' wait till it's done(about 20-30 mitutes you'll see load in cmd)when it's done choose reboot in recovery menu... that's all.
P.S. sorry for my English it's not my native language.
Click to expand...
Click to collapse
Hi, im having different issue than what was originally posted, but thought to give it a try the steps you described.
my problem is that my son forgot his pin code on the phone and has not a secondary method to unlock it, so i knew that i can just do a hard reset thru recovery mode and will be ok. but when i access to recovery mode only shows 3 options -reboot system -update via adb and -update via sd card. and is not showing the wipe/erase data option.
so i tried to follow your steps here all was good until writing on command
'fastboot erase recovery'
this is what i get back :
erasing 'recovery' ...
FAILED (remote: unable to format)
finished. total time : 0.891s
what can i do? either to continue with your steps or to do the hard reset on the phone?
thanks for any response
xlaxplaya said:
So I decided to do a factory reset, erase all data. During the process, it got stuck on "erasing". Left it overnight, for NINE HOURS, still stuck.
I can boot into fastboot mode, but I CAN'T GO INTO RECOVERY MODE. When I select "recovery mode" (by choosing the option with volume keys and then selecting with power button), it just boots back into the "erasing" dialog.
I've installed the driver from Intel, but I can't get ADB to recognize my device. Does it have to be in recovery mode to recognize the device, or should it recognize in just fastboot mode?
Kind of at a loss here. Honestly, this kind of sounds like the dreaded Nexus 7 brick problem from earlier this year.
P.S. am I using the correct vocabulary here? Fastboot is the menu where you choose the boot method, and recovery mode is where you can choose to restore to factory settings or flash a new image?
EDIT: IT FIXED ITSELF. I just had to let it sit for like 15 hours. It's ridiculous that it took that long.
Click to expand...
Click to collapse
Guys? My phone didn't fix itself. It has been 29 HOURS. And nothing is happening.
domrocks1337 said:
Guys? My phone didn't fix itself. It has been 29 HOURS. And nothing is happening.
Click to expand...
Click to collapse
Somebody else said it took 22 hours. So as ridiculous as it sounds, I think you should keep waiting. Try not to interrupt the process by restarting, we're not sure if it picks up where it left off.
If you don't have a backup phone or can't stand waiting, I would check to see if it's still under warranty and maybe do an RMA. You could just buy a phone with a 30 day return policy and just return it if this phone finally starts working again.
Hi
I have the same problem. It has been 28 Hours!
I can't access to Recovery Mode
Testerov23 said:
Same happened to me, but i found the way to fix it quickly. First of all i have find out that to properly wipe zenfone 2 , you have to firs wipe it from android software by going to Settings - Backup & reset - Factory data reset, and then wipe it from recovery menu and it will wipe it with normal speed it still will take 10-15 minutes but it's not 22 damn hours!!!
SO, The thing is that you still can get in fastboot mode and if you'll connect device to PC it will detect it. To get in fastboot you have to turn off your device(to do that you need to hold button "volume up" + "power" button, hold them untill phone is turned off,while you doing that the phone must be disconnectet from PC or it woun't turn off) then you press and hold "volume up" button and press and hold "power" button untill you feel the double vibrating and then you gonna let go the "power" button but still hold "volume up" button and then the menu will apear on the screen, you are in fastboot mode.
At this moment i'm sure that you have all Android (and official asus)drivers installed and all platfom-tools installed so i'm not gonna tell how to install it and i'm expecting that you know how to use platform-tools.
So... you go to cmd and from there to adb(usualy you do it by typing: cd c:\adb ) make sure that fastboot.exe is in adb folder, if not then download fastboot.exe and copy it in adb folder, then you type : ' fastboot devices' to see if PC deteced device you'll get 'F4AZFG04X560 fastboot' and it means that device is detected, then you type :
- ' fastboot format cache' wait till it's done
- 'fastboot erase userdata -w' wait till it's done
- 'fastboot erase system' wait till it's done
- 'fastboot erase recovery' wait till it's done
By doing all of these commands you're kind of doing factory reset by yourself.
Then you put recovery.img(recovery.img from OTA "older" than you had... if you had 165 then you take 164 or 139, or even OTA 97, it worked for me fine) and last firmware, for zenfone2 (from official asus site) in folder with adb and rename firware to 'update.zip' then run cmd from this folder and you can check if PC detected your device, by using command ' fastboot devices' and you'll see something like 'F4AZFG04X560 fastdoot' than you type command: ' fastboot flash recovery recovery.img' than you'll see :
" C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.684s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.193s'
then you choose recovery menu, by pressing "volume down" button, then phone boots it recovery mode and you see little droidbot "error", then you press and hold "power" button and press "volume up" button apears recovery menu, choose "apply update from adb", device is still connected to PC(if not, connect it), type in adb : ' adb sideload update.zip' wait till it's done(about 20-30 mitutes you'll see load in cmd)when it's done choose reboot in recovery menu... that's all.
P.S. sorry for my English it's not my native language.
Click to expand...
Click to collapse
I'm into the multi hour format thing of hell, i wonder why u must have to erase system and recovery, shouldnt it be enough to format userdata and cache? why do u do everything else? , in any case where do u get the official recovery? i dont wanna mod the phone, i wanna get OTA updates in the future.
long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...
ron8899 said:
long story short, incase any of these are the reason why my phone can't get twrp recovery.
History:
Around 3-4 months ago I updated my phone to Color os 2.0.8i(if not mistaken). Not sure if I did root my phone or not. My phone screen broke, and touch screen spoiled, not using it until I repaired it few days ago. After repair decided to use CM13 and took me awhile to figure out how to flash TWRP and took me quite sometime to root my phone. After successfully rooting my phone, I started to install CM13 snapshot bcos i tot the nightly is not stable. But it failed. My phone can't turn on and can't go to recovery. Keeps boot to fastboot. Figured out i need to use some code like fastboot oem unlock(can't really rmb if this was the code I used) then flash my recovery again and my recovery works. But my phone still can't turn on. I use TWRP recovery to flash the same rom again to see if it works this time, but no it doesn't. i think i did try the CM13 nightly rom but it doesn't work too so i searched a lot about how to install CM13 on Find7. This link(http://forum.xda-developers.com/fin...0-marshmallow-unofficial-cm13-oppo-7-t3227311) said that Color OS 2 &2.1 needs to flash Color OS 1.2.8 and i did it. I did not flash the stock recovery. I use fastboot boot stockrecovery.img. Then, I install the stock rom using the stock recovery. The link says let it boot, and after that reboot back to TWRP recovery. After successfully booting into Color OS 1.2.8i, I switch off my phone and press down button + power button but the stock recovery came out. From that onwards i keep trying to flash TWRP recovery to my phone but it failed. I used fastboot flash recovery twrp.img and press volume down button + power button, fastboot boot twrp.img, fastboot erase recovery and fasboot flash recovery twrp.img and fastboot boot twrp.img all that doesn't work even the cmd said okay twice. All it does just either boot up the oppo logo and turn back off and turn on again with the logo and turn on the phone normally. OR it just boot up the stock recovery. I have read it some where that some stock rom will overwrite the custom recovery with its stock recovery so needs to delete some recovery file and edit the updater script. I did it and try to install the rom again after editing, but it failed. I tried installing another 1.2 color os(without editing the inside hoping this rom doesn't have the ability to overwrite the custom recovery) it did tried to install but up to about 40% of the loading bar, it says fail. I tried many times, I even factory reset my phone and try installing again but TWRP just can't be booted.
Problem:
- I can't get to TWRP recovery.
- Without TWRP I can't install custom rom or root my phone
Please help me. I have wasted about 4 days time just to install the CM13...
Click to expand...
Click to collapse
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
My steps with fastboot oem unlock
tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
ron8899 said:
Hi, thanks for your reply. It didn't work again. Here is what I did maybe you can see what mistake i made:
1) volume up + power button get to fastboot.
2) plug my phone in to computer
3) right click in platform-tools folder + shift and choose open command window here
4) fastboot erase cache
result
5)******* Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.029s]
finished. total time: 0.029s
i continued
6) fastboot oem unlock
result
7)...
OKAY [ 0.003s]
finished. total time: 0.003s
i continued
8) fastboot flash recovery twrp-3.0.2-0-find7.img
result
9) target reported max download size of 536870912 bytes
sending 'recovery' <10894 KB>...
OKAY [ 0.344s]
writing 'recovery'
OKAY [ 0.163s]
finished. total time: 0.507s
10) i unplug the phone from computer
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
tropical cactus said:
You forgot fastboot oem unlock. Also not all twrp versions work. Try and see. Recap: fastboot erase cache, fastboot oem unlock and fastboot flash recovery followed by twrp. img. After that press and hold power and volume down simultaneously and you should be in twrp.
Click to expand...
Click to collapse
i realise something different this time. i switch off my phone and hold volume down + power button to go to the recovery. Usually it goes to the stock recovery but this time it doesn't it just turn on the phone like just now. it repeat these steps.
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
alright thanks i'll go and try
tropical cactus said:
All steps correct. Try earlier twrp versions. I remember 2.8.6.0 works.
Click to expand...
Click to collapse
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
ron8899 said:
I tried the 2.8.6.0 twrp. i repeated all the steps. erase cache, oem unlock, flash twrp and hold the volume down + power. this time it shows oppo logo. after awhile at the oppo logo screen, it glitch a little. Then it shows a black screen with light. but there is nothing. I tried to touch the screen nothing seems to happen...
i also tried 2.8.5.0 and it repeat this
11) i hold volume down + power button until i feel vibration i release
12) oppo logo showed up
13) screen goes off and vibrate again
14) oppo logo showed up again and the phone turn on normaly.
Click to expand...
Click to collapse
Well, sorry to hear that. I'm out of ideas.
tropical cactus said:
Well, sorry to hear that. I'm out of ideas.
Click to expand...
Click to collapse
Alright thanks anyway. Hopefully someone out there can help?
ron8899 said:
Alright thanks anyway. Hopefully someone out there can help
Click to expand...
Click to collapse
Have you tried CWM recovery?
tropical cactus said:
Have you tried CWM recovery?
Click to expand...
Click to collapse
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...
ron8899 said:
I haven't tried cwm yet. Cos i have used twrp on this phone before... wondering why i can't use twrp now...
Click to expand...
Click to collapse
Try it. It might work. Does the same thing anyway.
tropical cactus said:
Try it. It might work. Does the same thing anyway.
Click to expand...
Click to collapse
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...
ron8899 said:
i tried. using the X9007_CWM_recovery.img.
OKAY twice.
used volume down + power button.
logo showed up and stuck at the logo for a long time
the 3 buttons(back, home & menu buttons) light up
if i used fastboot boot method, the fastboot screen lightup brightly, and stuck there. and the three buttons light up too...
Click to expand...
Click to collapse
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.
tropical cactus said:
Okay. Last one. Since you have unlocked bootloader i. e. Fastboot oem unlock, try using flashify from play to install twrp and see if that works. Try a few versions of twrp.
Edit. Go back to stock recovery first and start again. Good luck.
Click to expand...
Click to collapse
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?
ron8899 said:
U mean I should try flashing stock recovery using cmd, after that then I use flashify flash twrp?
Click to expand...
Click to collapse
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.
tropical cactus said:
Yes, so you have a working recovery. Check that it is installed first. Then fastboot erase cache and fastboot oem unlock. Reboot, download flashify and flash twrp. img and then try to enter recovery.
Click to expand...
Click to collapse
Alright, I saw two flashify in play. Which one is it? The one with the requires root?
ron8899 said:
Alright, I saw two flashify in play. Which one is it? The one with the requires root?
Click to expand...
Click to collapse
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.
tropical cactus said:
Yes, the one from rashr. Skip all warnings and proceed. Put your twrp.img on sd card first.
Click to expand...
Click to collapse
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397
ron8899 said:
oh.... i can't get my stock recovery work... it always shows half of the reocvery screen only.... and the recovery screen keeps glitch. what should i do?
this is where i download the stock recovery
http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397
Click to expand...
Click to collapse
Now we know where the problem is. I re-read your post. New LCD screen. Flash this stock recovery. Once you see it can work, then proceed with the erase cache, oem unlock and twrp 3.0.0.0.
The links here: https://drive.google.com/file/d/0B_5WCvt_2elTU0pKR0V1Mm1jWk0/view?usp=sharing
https://drive.google.com/open?id=0B_5WCvt_2elTbmZ5MERKTzVPQTQ
---------- Post added at 06:36 AM ---------- Previous post was at 06:26 AM ----------
Oh, and by the way, CM 13 not compatible with our LCD screen. Omni supports new screen. Read before flashing rom. If not you'll have more problems.
There's a snapshot CM 13 for new LCD in oppo forum. The links are dead but if you ask someone there, they might upload. I've erased mine. Again, there's some requirements there, so read up.
---------- Post added at 06:46 AM ---------- Previous post was at 06:36 AM ----------
community.oppo.com/en/forum.php?mod=viewthread&tid=46578&extra=
Crap, link incomplete. Nevertheless, go to find 7 third party development section. It's all there.
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Try to get into lgup to flash a kdz, if you cant do that you might be SOL
LGUP does not detect phone, download mode is not working
hi
Prosjak said:
LGUP does not detect phone, download mode is not working
Click to expand...
Click to collapse
Please contact me, I can help you recover the device
PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
How to contact you and how you can help me.
If you want to help write this here to help this benefit to anyone who has this or similar problem
Thank you
Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Fastboot --set-active=a
LameMonster82 said:
Fastboot --set-active=a
Click to expand...
Click to collapse
Thank you for your reply
The problem is that the bootloader is locked
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
Problem solved
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day
What version of G7 use?
Sent from my LM-G710 using Tapatalk
PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
i got this problem too.. please help with that
Prosjak said:
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day
Click to expand...
Click to collapse
how i can do this?
My G710EM has a problem with my lockback BL. I can't boot the system and it will prompt "Your device has failed a routine safety check and will not boot. This may be a temporary problem. If this message occurs repeatedly, visit this link on Another device and refer to the red case:g.co/ABH Your device will power off automatically after a while.” With LGup brush kdz brush does not go in, fastboot “fastboot flash unlock unlock.bin” prompt is invalid
* Target reported max download size of 536870912 bytes
Sending 'unlock' (1 KB)...
OKAY [ 0.004s]
Writing 'unlock'...
FAILED (remote: Flashing Unlock is not allowed
)
Finished. total time: 0.011s
I don't know what to do.
I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
At first, you'll need a working fastboot environment, you'll find out how to set it up on your own. Then you'll need the laf.img, I can upload mine if you want or I could help you extracting one out of a kdz file. Put the laf.img in the same folder like your fastboot.exe, then hold shift and right click, then click on "open command panel here" or however it's called in English. Type "fastboot flash laf laf.img" (Edit: It would probably better to use "fastboot boot laf.img" instead because of the bootloader lock). If that works, you at least have a working download mode.
Click to expand...
Click to collapse
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again
Garlikus said:
I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again
Click to expand...
Click to collapse
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I recall I also had some error msg, it could've been the same. Now I don't remember what I exactly did next as most my actions were more or less random. Either I tried the same command but with other laf.img file (from the rom I used before), or I tried to restart the phone into download mode (vol- and power together and then vol+ after screen goes black) or tried the same file again.
Hope it helps.
davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I have the same problem as well. I follow the guide but I received the same error message
domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
Check if the phone is recognized in LG Bridge. If so, then choose update error recovery from software update tab. Again, I don't remember if it worked immediately or did I need to reinstall drivers and/or choose a proper driver in device manager (generic ADB vs LG...) and/or restart the phone.
domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
I have same error too ...
DenisVelev said:
I have same error too ...
Click to expand...
Click to collapse
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
install the LG Bridge updater software on a computer, go to updates, click the "correct update errors" button. Then plug in your turned-off phone while holding down the volume up button. It should switch to download mode and reinstall all software from the PC. Yes, this will erase all data but it should unbrick your phone (unless the hardware's broken I guess)
Click to expand...
Click to collapse
Garlikus said:
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
Click to expand...
Click to collapse
Cannot put in download mode. Only Fastboot. For a secound show download mode after that show fastboot mode.