Related
Hi there,
I have a problem that my LG will not boot the device is stuck at the logo, I've also done a hardware reset but the process also depends on the logo proof and 10min not happened.
In the download mode, I'm not coming.
About the fastboot mode I try to start TWRP, but it appears the TWRP logo and nothing else happens.
How did you manage to get it to this point? What did you do before it didn't boot anymore?
Also, if you manage to get adb access somehow you can just reflash the recovery again
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
So you cant enter download mode or recovery? And you cant turn on phone?
No download mode is not only possible fastboot mode. If I we want to install Recovery in fastboot mode, shown below
Command: fastboot flash recovery recovery .img
Error on LG G3:
Error: Command never completed
Error: Auto CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror:Command completed with errors
Failed to send stop command
Failed Writing block @1
SourceCoder said:
No download mode is not only possible fastboot mode./QUOTE]
Could you please explain this.
Is comma missing somewhere?
Click to expand...
Click to collapse
The following screen appears:
lgg3root.com/wp-content/uploads/2014/08/howto-unroot-unbrick-lgg3-2-690x492.jpg
And then immediately this screen:
android-hilfe.de/attachments/root-custom-roms-modding-fuer-lg-g3/345262d1415303724-lg-g3-kein-download-modus-mehr-img_20141106_093950.jpg
This screen does not appear:
androidheadlines.com/wp-content/uploads/2014/07/LG-G3-Download-Mode-AH-1.jpg
SourceCoder said:
I ran a SuperSU update and then he appeared dialog that I should restart the system and since I have the problem.
How can I flash the recovery again?
If I want to flash TWRP on the fastboot mode, only the TWRP logo and then nothing happens appears.
Click to expand...
Click to collapse
Something does not compute in this at all. SuperSU should not have caused your phone to brick like that.
Is there something else you are not telling us about how your phone was set up? Were you doing anything before you updated SuperSU? This looks like a case of where you flashed the wrong image on your phone, if you ask me.
SuperSU is not phone specific, so I'm having a hard time believing SuperSU did this.
Something else must have happened that you are not telling us. You need to lay out in order, everything you did to your phone up to the point of updating SuperSU.
Also, SuperSU asks how to update: normal or via recovery. Which way did you choose? Either one shouldn't matter, but it's a start.
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
SourceCoder said:
I had the ROM KNVIRUS V11, since I got the message that an update to SuperSU are available. The update I installed then I get the message that the device must be restarted for the update to be finished and since I have the problem.
I wanted to start the download mode just in fastboot mode, unfortunately without success.
command to start the download mode: fastboot boot laf.img
Result: fs2.directupload.net/images/141219/p68gn6y5.jpg
What I do not understand whatever I command in fastboot mode I enter I get these error messages:
Error: Command never completed
Error: Car CM012 error
Error: Command completed with errors
Error: Command timeout error
Errror: Command completed with errors
Failed to send stop command
Failed writing block @ 1
Click to expand...
Click to collapse
Did you flash the correct laf.img file for your model of phone? If not, that could be part of it. What model of the G3 are you using and where exactly did you obtain the laf.img file from?
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
SourceCoder said:
SuperSU update should I install because the PlayStore has shown that there is an update.
laf.img I downloaded here: http://forum.xda-developers.com/showthread.php?t=2766437
I found a thread has to ängliches problem: http://forum.xda-developers.com/lg-g3/general/guide-how-to-restore-download-mode-t2897257
Click to expand...
Click to collapse
Well, there you go. I have NO idea for what version of the G3 that thread was for. The guy never states which version it is. You do not, repeat, do NOT flash anything to system, boot, etc for this phone unless you know for sure it's for YOUR model of the G3. There are various models of the G3. For example, mine is the Verizon model (VZ985). There is an AT&T model (DS855), and numerous others, especially for those overseas. I would not and should not flash the DS855 boot image to my VS985 boot image. It will brick the phone as you have found out the hard way from what I can tell.
You just flashed something you have NO idea which version it was for. You may have completely bricked your phone. I'm not entirely sure, but you need to find the correct stock images for your phone and flash them back.
You need to go here and figure out which model of G3 you have:
http://forum.xda-developers.com/showthread.php?t=2791269
After that, you need to go and find the correct stock image files and flash those back onto your phone. Since this are NOT img files, you cannot fastboot flash them. You muse use either KDZ or TOT files depending on which ones are available for your model of phone:
http://lg-firmware-rom.com/
or
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
Then, you have to use the correct tool to flash these files depending on if they are KDZ or TOT file:
http://forum.xda-developers.com/showthread.php?t=2785089
Hopefully, flashing back to the correct stock image will fix you up. However, you better make darned sure which model of phone you have BEFORE you even attempt it. Once you figure out which model of G3 you have, post here and ask. Otherwise, you could bork your phone up even worse to where it may not be recoverable. Hopefully, it's not at that state right now.
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Again, did you verify with the link you posted for the image file that it was indeed for YOUR model of your phone? If not, you probably have bricked it.
You need to go and follow the links I posted which tell you how to flash back to stock.
There was no reason to go into fastboot mode for SuperSU. I don't know why you felt you had to do that.
Also, the second link you posted has the thread pretty much deleted. The OP said he was incorrect in what he posted (whatever it was I don't know since he deleted it), so it was removed due to it not working as stated.
Go back to the links I posted to flash back to stock on your model. If what you say you have is the European model, then this would be the KDZ file you want:
http://storagecow.eu/Xda/LG G3/Stock/Europe Common 16G D85510A_00.kdz
I would verify for sure that is what your phone is before continuing or else, you'll bork your phone up even worse than it is already.
The boot image you flashed is probably for the Korean version of the phone and that's why everything is messed up.
If you are not sure on how to do this, then you might want to find someone near you who does.
Just remember, just because a post says it's for the G3 doesn't mean it's specifically for YOUR model of the G3. You need to verify for sure that it is. Most have the model number in the thread's title.
LG G3 Fastboot
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
[1700] fastboot mode started
razaaliarain said:
well i have the same problem for a week every command was giving error, but then used this command "fastboot boot twrp.img" i was able to get into the recovery from there i wiped everything and then rebooted but nothing happened but then somehow (I DO NOT KNOW HOW) i was able to get into the download mode so i flashed the stock firmware of my lg g3 D855 and everything was going good and i was just setting up my phone and then suddenly it turned off and again booted into the fastboot mode, WTF , i was just installing some apps from playstore man, and now when i try to boot into twrp it is just stuck on twrp image on the whole screen
Click to expand...
Click to collapse
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
_narisha_ said:
i was facing the same problem and "fastboot boot twrp.img" worked. it took me to twrp where i flashed my ROM. i had freaked out that my G3 was bricked.
Click to expand...
Click to collapse
But now i am stuck again on fastboot mode and this time i was not rooted and did not had twrp installed so now when i try to use the "fastboot boot twrp.img " my device will reboot and then will be stuck on twrp logo on the screen
I have the same problem...
I ran stock OTA update 20f, since a couple of weeks ago. While I had my phone on the table and it was runing voice recorder soft it restarted once and then after a couple of minutes again. This time it never booted but stuck at the LG screen.
Never rooted, never installed anything other than the OTA 20e and 20f updates. I have not flashed anything to the phone other than the official OTA.
Doesn't boot to anything other than fastboot. Recovery starts but after confirming twice it reboots and stuck still.
If I boot to Download Mode it goes to fastboot, if I wait long enough on regular boot that only shows the LG logo it will eventually go to fastboot.
Running "fastboot.exe boot openrecovery-twrp-2.8.4.0-d855.img" gives me the same error messages, stuck at the TWRP logo screen. I found the ADB port is connected but when running "adb devices" it says "LGD855..... offline". I didn't enable ADB before the device crashed and I can't enable it in TWRP because it doesn't start properly.
I have the 32GB D855 European unlocked. I belive this is hardware problem and will send it for repairs.
SourceCoder said:
I have LG G3 16GB EU version.
As I have written on the first page, I get nothing into download mode so I can not flash it.
What I can not understand why no command in fastboot mode works no matter what I type, I always get the error message: FAILED (remote: flash write failure)
Click to expand...
Click to collapse
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
gee2012 said:
Oeps, `flash write failure` brings back memory`s of the emmc failure with Samsung devices where the sdcard is no longer readable and can not be written on. Send it in for repair, there is no other way and they`ll probably replace the motherboard.
Click to expand...
Click to collapse
That's right. I tested to boot Philz recovery and it freezes at the text.
Mine says actually:
Error: Command never completed
Error: Auto CMD12 error
Error: Command never completed
Error: Command timeout error
Failed to send stop command
Failed reading block @ 1
mmc read failure misc 2048
The CMD12 is according to emmc spec a "Stop command".
So this is a hardware fault and not a software one.
I managed to get in to a fastboot(ish) environment on my K420N after using this tool to zero out my laf partition and then rebooting using the vol+
However, every command i try to use gives me an error:
FAILED (remote: unknown command)
did i screw up or is there a way to get it to work?
anyone?
update: aoarently some commands DO work:
fastboot getvar unlocked
unlocked: no
finished. total time: 0.001s
Click to expand...
Click to collapse
MRMACGEEK said:
I managed to get in to a fastboot(ish) environment on my K420N after using this tool to zero out my laf partition and then rebooting using the vol+
However, every command i try to use gives me an error:
FAILED (remote: unknown command)
did i screw up or is there a way to get it to work?
Click to expand...
Click to collapse
Sir, Can you give us a step by step guide how you entered Fastboot. We are eagerly waiting for it.
@pvineeth97
Well i dont see why not... Just be aware that most important functions dont work so basically you lose download mode and gain nothing... But for those who want to try... Just remember i will bot be responsible if you brick or anything.
Remember to ibstall driver prior to doing this.
1. Boot into download mode (vol-up + power)
2. Hook up your phone to your pc.
3. Use partitions.py to format you laf partition(i dont kbow the ezact command and cant check it because i cant enter sl mode anymore)
4. Reboot woth vol up again
MRMACGEEK said:
@pvineeth97
Well i dont see why not... Just be aware that most important functions dont work so basically you lose download mode and gain nothing... But for those who want to try... Just remember i will bot be responsible if you brick or anything.
Remember to ibstall driver prior to doing this.
1. Boot into download mode (vol-up + power)
2. Hook up your phone to your pc.
3. Use partitions.py to format you laf partition(i dont kbow the ezact command and cant check it because i cant enter sl mode anymore)
4. Reboot woth vol up again
Click to expand...
Click to collapse
Root isn't required?
What is the first screen you saw after rebooting it with vol up again? What's the exact key combination and for how long we should hold it?
How did you use "partitions.py"? Something like this? "python partitions.py"?
What's the software version of your phone when you did this?
We here on XDA will treat you as a king if this works!
First. Im on 6.0 so no root.
2nd. Its the same as booting into download mode. Axtually yoy delete download mode usong this method.
3rd. I would like to join the club who treats the one makibg this useful as a king. Because FLASHING DOES NOT WORK!!!!
Also. Basically you get a acreen telling you its listening for fastboot commands
MRMACGEEK said:
Also. Basically you get a acreen telling you its listening for fastboot commands
Click to expand...
Click to collapse
Add on WhatsApp group!
https://chat.whatsapp.com/37Ik7i5wWDU4YjfnIvYQon
Forgot to mention. Yes use python. That info is on thengithub page too btw
I have tried everything and everywhere I hit a brick wall,
So my screen stopped working and I got that replaced by Asus. When my Phone came back all appeared to be working well untill 2 weeks after.
My cameras stopped working, the flashlight stopped working, the sd card slot stopped working and the SIM slot 1 stopped working.
So I wiped the cache and now the Phone does not boot anymore.
Tried to update rom via ADB in recovery: permission denied,
tried to backup via adb in bootloader: cant find device
Tried flashing the bootloader, permision denied,
tried using Xfstk, screen on xfstk remains blank
Updating via sd is not possible anymore since the SD card does not get mounted in the bootloader...
Anyone any idea?
Does the phone's correct serial # appear when you type "fastboot devices"?
When you say the xFSTK screen stays blank, do you mean you can't see any writing? If this is the case, did you install the drivers before installing xFSTK?
audit13 said:
Does the phone's correct serial # appear when you type "fastboot devices"?
When you say the xFSTK screen stays blank, do you mean you can't see any writing? If this is the case, did you install the drivers before installing xFSTK?[/QUOTE
Yes
and yes I did install the drivers in safe mode before installing Xfstk
"C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.592s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.726s"
Click to expand...
Click to collapse
I'm not sure if you need to install the Intel USB drivers in safe mode but I just installed them as an Admin and then ran iFSTK as an Admin.
There is no need to flash a boot.img file because iFSTK will install a temp bootloader and boot into fastboot mode. Then, run Asus Flash Tool as an admin and flash a raw file to the phone.
audit13 said:
I'm not sure if you need to install the Intel USB drivers in safe mode but I just installed them as an Admin and then ran iFSTK as an Admin.
There is no need to flash a boot.img file because iFSTK will install a temp bootloader and boot into fastboot mode. Then, run Asus Flash Tool as an admin and flash a raw file to the phone.
Click to expand...
Click to collapse
I can get into fastboot mode, however everything I do in it gives the message permission denied. Maybe I do not need xFstk, but Asus Flash tool does not run as it quits with the message permission denied
Are you flashing a RAW file in AFT?
audit13 said:
Are you flashing a RAW file in AFT?
Click to expand...
Click to collapse
Yes
Was the phone running MM or LP?
Maybe re-flash a stock recovery and sideload a stock ROM?
audit13 said:
Was the phone running MM or LP?
Maybe re-flash a stock recovery and sideload a stock ROM?
Click to expand...
Click to collapse
It was running last MM
I tried flashing the last two available (both LP) raw roms
It may be that the bootloader is locked. Try flashing a stock MM recovery and then use the "update from SD card" option to flash a stock ROM from the SD card, assuming the SD card is recognized by recovery or try to sideload a stock ROM.
audit13 said:
It may be that the bootloader is locked. Try flashing a stock MM recovery and then use the "update from SD card" option to flash a stock ROM from the SD card, assuming the SD card is recognized by recovery or try to sideload a stock ROM.
Click to expand...
Click to collapse
Well apperantly sideloading works again (sd card is out on recovery, can not mount)
however:
C:\adb>adb sideload UL-Z00A-WW-4.21.40.184-user.zip
serving: 'UL-Z00A-WW-4.21.40.184-user.zip' (~53%) * failed to read command: Invalid argument
and then the Phone crashes
Same with differend roms
% differ
Do you see the phone's serial # in fastboot mode? If not, try pressing volume up 3 times.
audit13 said:
Do you see the phone's serial # in fastboot mode? If not, try pressing volume up 3 times.
Click to expand...
Click to collapse
Yes I do in fastboot
ADB does not detect.
ADB sideload does but the 1234567abdcde
You see 1234... on the phone's screen in fastboot mode? If yes, press volume up 3 times and look at the screen again as it should show the correct serial #.
audit13 said:
You see 1234... on the phone's screen in fastboot mode? If yes, press volume up 3 times and look at the screen again as it should show the correct serial #.
Click to expand...
Click to collapse
Fastboot has the serial on screen
When using AFT, the phone is detected and starts to flash?
audit13 said:
When using AFT, the phone is detected and starts to flash?
Click to expand...
Click to collapse
Yes,
but aftert flashing for some time it says permission denied
I'm not sure but it could be that the bootloader is locked so it can't flash the entire ROM which results in a permission denied error.
Did you try powering off the phone, opening iFSTK as ad admin, change the settings as required, start the download, connecting the phone, press and hold the power button for about 2 seconds, release the power, and let iFSTK try to load a bootloader?
audit13 said:
I'm not sure but it could be that the bootloader is locked so it can't flash the entire ROM which results in a permission denied error.
Did you try powering off the phone, opening iFSTK as ad admin, change the settings as required, start the download, connecting the phone, press and hold the power button for about 2 seconds, release the power, and let iFSTK try to load a bootloader?
Click to expand...
Click to collapse
Ifstk does only show a blank screen on all my pc's just tried 5 of m,
If iFSTK shows a blank screen, you should uninstall the program, re-install the USB drivers, reinstall iFSTK, and try again. I also had the blank screen problem in iFSTK but was able to get it working by restoring a Win7 image and starting over.
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Code:
D:\Programs\Minimal ADB and Fastboot>fastboot.exe flash recovery twrp-3.1.1-0-addison.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11374 KB)...
OKAY [ 0.255s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.246s]
finished. total time: 0.510s
Is there a way to avoid this error ?
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
FSabbane said:
Hi,
I want to enable dualsim on my singlesim device and for that the TWRP has to be installed. After checking many threads, which less or more describe the same steps, I managed to unlock the bootloader and downloaded an "unofficial" twrp image for the Moto Z Play. But on the last step while trying to flash it I got the error "Image not signed or corrupt" and the image is not installed. Here is the output by flashing:
Is there a way to avoid this error ?
Click to expand...
Click to collapse
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Jimi Mack said:
Use: "fastboot flash recovery twrp.img" no quotes. I change the filename to just "twrp.img" less chance of typing something wrong.
and no the .exe you did.
Click to expand...
Click to collapse
I've changed the filename to "twrp.img" and used the command:
Code:
fastboot flash recovery twrp.img
The output is exactly the same as before.
Kap_Tutan said:
I think it is flashed. After flashing the twrp via fastboot and u see that error then just ignore it, instead directly boot your phone in recovery mode using the volume buttons and look for the word "recovery" then press on power button then it booted there.
Click to expand...
Click to collapse
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
FSabbane said:
unfortunatly not, after entering the recovery mode I see the message "no command" and I have to hold the power button and press volume up to enter into the Android Recovery menu.
Click to expand...
Click to collapse
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Kap_Tutan said:
Try to redownload the twrp again, try to use the lower version not the updated one. And after u flash that then update it with the newest one. Lets see if its work
Click to expand...
Click to collapse
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
FSabbane said:
I've tried with the following images:
twrp-3.1.1-0-addison.img
twrp-3.1.0-0-addison.img
twrp-3.0.2-0-addison.img
which were downloaded from the url: https://www.androidfilehost.com/?w=files&flid=126925
The result is the same by all of them.
Just to be sure, the image should be copied within the "ADB/Fastboot" folder on my PC and not on the device storage/SD card, isn't it ?
Click to expand...
Click to collapse
Did u unlock bootloader?
Yap it should be in pc adb folder
Kap_Tutan said:
Did u unlock bootloader?
Yap it should be in pc adb folder
Click to expand...
Click to collapse
Yes, I did unlock it with the unlock key received from motorola:
Code:
fastboot oem unlock UNLOCK_KEY
After that a message is displayed at each start:
your device has been unlocked and can't be trusted
ID: bad key
your device will boot in 5 seconds
Click to expand...
Click to collapse
FSabbane said:
Yes, I did unlock it with the unlock key received from motorola:
After that a message is displayed at each start:
Click to expand...
Click to collapse
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
flashallthetime said:
After flashing twrp do not boot the phone otherwise the stock recovery will over write twrp,
After twrp is flashed while still in fastboot mode, use the volume buttons and select recovery on the menu.
Click to expand...
Click to collapse
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
still doesn't work for me
FSabbane said:
That was it, at each boot the recovery partition was overwritten.
Thank you very much for the help !
Click to expand...
Click to collapse
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
This is not an error. If your bootloader is unlocked this message will display at every boot.
velpoori said:
I am still getting error saying your device is unlocked can't be trusted and will be restarted in 5 seconds,
please help me out. Also need adb zip file
Click to expand...
Click to collapse
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
FSabbane said:
As Fandroid mentioned, it's not an error. My device also diplays it at startup.
I've added to this post a zip file that contains adb, fastboot and twrp version used to configure my device.
Click to expand...
Click to collapse
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
velpoori said:
Have you installed twrp successfully and which OS r u running on your moto z play right now, how is it?
Click to expand...
Click to collapse
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
My OS is the Moto Android 7.0.
What is the issue that you have now ?
Click to expand...
Click to collapse
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
velpoori said:
As I told earlier I am not able to install twrp due to which I am not able to install custom rom. I tried many times to install twrp, everytime it showed "image is not found" as you guys said I tried going recovery but again it shows you already unlocked boot loader, your device can't be trusted then says " your device will reboot in 5 seconds" this is what my issue is.
Click to expand...
Click to collapse
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
FSabbane said:
So that we can see where you're stuck at the moment, please follow this guide and tell us which step didn't work :
https://www.obeygeek.com/install-twrp-recovery-on-moto-z-play/
P.S.: use the adb, fastboot and twrp image I've sent you in the previous post.
Click to expand...
Click to collapse
I will try once I reach home by 6pm, you are so helpful thank you...
FSabbane said:
I wanted twrp just to create a backup and configure my device to support dualsim. Therefore and as mentioned in a previous post, TWRP is installed only momentarly and after a reboot it would be overwritten.
Click to expand...
Click to collapse
It makes no sense then to flash it. Why don't you just use
fastboot boot twrp.img
when you want to start it? Then no flash will be involved, and twrp will be just booted for this single usage. You can repeat this whenever you need it.
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.