Related
Hello XDA
As title say, I 'm going share my experience in this thread.
History
I purchased this device almost 8 month back.Purchased from a local store.Was very smooth and i was satisfied with the performance.Battery was good.Got regular update and these updates are from google,so why not install it,right?Then this Android N came,and i was so happy.7.0.0 was good.Then the nightmare 7.1.2 came.Phone started to lag continuously,Battery drained too much.But I was like Okay.May be this will fixed in new update.Then suddenly one day my phone was stuck.Not booting.Stucked at Google.I understood that phone already booted and fingerprint was too working but it showed nothing on display just black light.I was afraid as i didn't purchase it from Google Play or any authorized seller.So no warranty or chance of having replacement.So I started searching about this issue and found not only me many people are facing this.But there are no proper guideline or solving this issue.Tried everything and ended up with Locked Bootloader Irony!
Journey
As i never try to mess with my phone because it was Nexus 5x! So i never touch OEM or try to unlock the bootloader.So i tried to access stock recovery,But Alas! in recovery Volume up and down wasn't working.So I couldn't wipe or factory reset.So Now ended up with :
1.Locked Bootloader
2.Locked OEM
3.Recovery Stuck
Googled and found many solutions but none of them came to solve my issue.So i thought why not flash stock rom.But HOW! Cause fastboot only work with unlocked bootloader.And you can't unlock bootloader when your OEM is locked and you can't unlock it with fastboot.It can be only unlocked from developer option only.GOD!
Now I have only 2 options left:
1.Fastboot mod where no functions working
2.Download Mod (This will save you)
Now fastboot option is out and only download mod option is available.So what can i do with Download Mod?
LGUP TOOL helped me.Downloaded a tot file for Global version (LGH791) and flashed it and stucked at google logo and in recovery too.But next time i flashed the same file in a different way.Ok here it is:
1.Drivers are important here.I'm using windows 10.I have adb and fastboot and Lg drivers.Workplace okay.
2.Opened device manager and change the com port of Android phone 3 to 41. Port Changed!
3.Connected my phone to pc using 3rd party cable (Careful here,try to use original cable.) and entered into download mod and.
4.Opened LGUP Tool ,checked REFURBISHED mod,checked BIN file and select the tot file downloaded before.And quicky close it.(No need to click start)
5.Then again opened lg tool and click start.(BIN Checked and it showed the previously selected tot file).No need add anything new this time,just open and click START.
6.Rebooted and again stucked at Google screen.But wait! recovery is working.Pressing and holding volume up button for a while then a android logo with red cross inside will come up.Now holding power button and volume down button at the same time,Recovery will show and menu is working.Great!
7.Now Wiped cache and factory reset.And after that selected Apply update from Adb sideload
8.My device was connected to pc from the beginning,right? Now i downloaded a file previously called bullhead-ota-opp2.170420.019-c449d2bb.zip from Google Nexus 5x OTA update page.
9.In Adb folder,copied the file and named it ota.zip.Opened a command prompt using shift+right click in the folder.Phone was on Adb sideload mode.Typing this command adb sideload ota.zip
10.This took more than 8-9 minutes to finish.After flashing and phone rebooted.WOW
11.Couldn't believe my eyes.The OTA update was about Android O.I quickly enabled the developer menu and made oem unlcocked and usb debugging on.Boot into bootloader and unlock bootloader with this command fastboot flashing unlock
12.Now bootloader is unlocked and i flashed TWRP recovery for future need.
13.Rebooted the phone and after using for 1 minute the phone freezed again
14.This is the end of the story for today.
Planning
I'm thinking the OTA update was the problem.Now I'm downloading 6.0.1 version.And will do a clean install.Let's see what happens next.
Any kind of help is appreciated.If you think there is something i'm missing here then please suggest.
And Thanks to XDA.I got all these helps from here.Will update the post tomorrow.
You downloaded Android O Developer Preview. Final OTAs are here:
https://developers.google.com/android/ota
Just try flashing newest Factory Image via fastboot, but don't forget to flash TWRP back:
https://developers.google.com/android/images
TBH I NEVER thought this phone will be dead by hardware failure all of a sudden, I dont mind another few hundreds bucks but the problem now is the fking data within it.
Cant even pass google logo if you choose Recovery Mode
GG LG, well played
I have a 16gb variant dead....same issue like urs .....can i use the same lgh791 tot file?... in fastboot it says lgh791 16gb
usefully
usefully
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
same of my expirience, flash 4CoreOreo..
my nexus 5x now is fully working
the_uker said:
I STRONGLY recommend that the original post is corrected to change "Download mod" to "Download mode" in all of its four occurences.
Same for one ocurrence of "Fastboot mod".
It is horribly confusing as it is, as calling them "mod" implies some modification you have to apply to the phone (be it software or hardware).
Click to expand...
Click to collapse
I suppose that makes sense. Then again, when an instruction is telling you to boot into download mod.....using common sense I'm gonna understand that's a typo and they meant download mode. But you're right, for some folks that may be a bit of a challenge. Common sense isn't as common as it was when I was young.
And the links?
I'm brazilian and i'm having a hard time to find the links to download stuff. Mine is dead and bootloader blocked. The tutorial seems to work but i can't understand well
Interesting. Thanks
I will try to explain everything from the beginning. I was about to install a custom rom install (it was in 7.1.1 stock, unlocked bootloader) so when I was going to do full wipe with lastest TWRP there was an error. Wait for about 15 minutes just in case, but nothing happened so I decided to restart it to try again. But the phone stuck in the ZTE logo and if it tried to enter TWRP was stuck in the logo too, I tried with all versions of TWRP and no one works. Find a post that said I could use TWRP tenfars tool to recover my phone and had to enter the EDL mode. I managed to put the phone in edl mode but now I can not get out of it. I press and hold the power button for a minute and nothing happens (no vibration, no led, no ZTE logo) my pc just does the unplug windows sound. My pc recognizes the phone as QUSB_BULK. When I try to use the tenfars tool I get this message:
C:\Users\Alejandro Saavedra\Downloads\minimal_adb_fastboot_1.4.1_portable>axon7tool -w recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Also try using the xiaomi MiFlash tool (even change the drivers from QUSB_BULK to COM COM 5) but something similar happens, also tells me can not recive hello package.
I'm a little new to this so I beg you a little patience
Please work very hard to buy this phone, there has to be some way to unbrick it. :crying:
If you need any additional information just tell me
If you use axon7tool :
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
If you use MiFlash :
get latest version : https://www.androidfilehost.com/?fid=673368273298954241
check in Devices Manager if is called Qualcomm 8004.
CelesteBlue said:
check in Devices Manager if is called QLIBSD.
rename recovery.img to recovery.bin.
Click to expand...
Click to collapse
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Smedslund said:
You need two files, recovery.img and recovery.bin in same folder. (Don't forget to unzip tenfars TWRP and after that rename and make a copy)
Please read: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Best regards
Smedslund
Click to expand...
Click to collapse
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
CelesteBlue said:
anyway :
https://ab-exclusive.us/fileserver/uploads/twrp_rec_tenfar.zip
404 Not Found...
To flash a recovery file (STOCK or TWRP) with axon7tool, the file has to be called recovery.bin.
Click to expand...
Click to collapse
You will find tenfar 3.0.2-2 TWRP at download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Once unzipped, copy it to recovery.bin:
copy twrp_rec_tenfar.img recovery.bin
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
ale0796 said:
Thanks to everyone for your answers, I was able to recover my phone using miflash, qualcom usb drivers and this ROM https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip I put my phone in EDL mode and then flash the mentioned rom. It took me like 20-30 tries to finally get it. The last attempt I made was to unplug the device from the computer, I kept the power button for 10 seconds and connect it to the computer without ever releasing the power button. It was seen as always (black screen, not led) but for some reason this time works. I hope everyone can solve this problem. Can pm me if you need help, maybe i can help with something
Click to expand...
Click to collapse
That's because you reset the EDL that way. the method is weird but seemed to work...
If you hold the 3 buttons for ~10 secs while the device is in EDL it will reset it
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
Actually, it is a nice feature for the few seconds it lasts, but read HERE if you must. Be careful!
Good luck
CelesteBlue said:
@Choose an username... I am out of context, but I wonder if I can remove the ugly message on each startup telling it can't check if the device is not corrupted... I think this message is caused by the unlocked bootloader. A solution ? Thank you.
Click to expand...
Click to collapse
I'd advice against doing it... I had no trouble with it but a bunch of people now have paperweights. But yeah, the link is the one provided by the other guy above me
Thank you so much @Choose an username... and @amphi66 : that worked !
Anyway I am on G B04 (Nougat).
Do you know some cool mods I should do ?
Like debloat, remove the boot message (done), etc...
I was trying to update with LGUP application for firmware update but didn't success, so I removed the USB cable and pressed Volume down and power button to restart. But it went straight into Firmware Update and LGUP application can't find the port.
So, my phone is stucking in Firmware update screen, please help me how to restore the firmware and get out from Firmware Update screen, many thanks and greatly appreciated.
Hold the power button until you get a black screen. Download LG Mobile Support tool and the LG Drivers. Plug USB In and then hold the Power + Volume Up key. On your screen, click Upgrade Recovery. From there, you can do a factory reset through download mode of your phone.
Enter download mode and connect the phone in the PC. Download LG brige and open it. When you are inside the programe you will see a window of Software update enter here and there is an option that is for bad installation otas (to reinstall and correct errors). Use this and I think this will handle.
Another option I think is using LG Up you will see your device in download mode. Try to enter download mode and see if this works also.
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
In older LG phones work LG Flashtool (2014)...Maybe with this you can flash KDZ firmware https://forum.xda-developers.com/showthread.php?t=2797190
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
I have the same issue - I was on Lineage os and flashing the OTA update caused bootloop to recovery. So I wanted to flash back to stock using LGUP and 14A. I did that before without issues.
This time though all installed fine but after reboot the phone immediately goes to fastboot, exactly as described above. I just spend several hours trying to fix it but with no results. The LG Bridge won't recognize the phone no matter what I do in Windows (tried 3 different PCs). On a Mac it will start connecting and will end up saying "you need to enable MTP connection".
From what I garther the stock rom flashed fine - the factory reset works, even shows "erasing data", the LG UP recognizes the phone as 14A (I tried 11A, 13A too - seems to install fine but goes immediately to fastboot after reboot).
The only thing I realized I did different when flashing the stock rom with LGUP was not using the original LG USB cable. But reflashing with original cable makes not difference now - still going to fastboot.
Any help would be greatly appreciated.
Have you guys been able to do the Upgrade recovery in the LG support tool? Did it work? It starts fine for me but after downloading the recovery file I always get and error, see the screenshot.
I was able to grab the kdz file and tried to flash it with LGUP but still the same thing. It seems like it flashes fine but after reboot it immediately goes to fastboot
kloubik said:
Have you guys been able to do the Upgrade recovery in the LG support tool? Did it work? It starts fine for me but after downloading the recovery file I always get and error, see the screenshot.
I was able to grab the kdz file and tried to flash it with LGUP but still the same thing. It seems like it flashes fine but after reboot it immediately goes to fastboot
Click to expand...
Click to collapse
Sadly I'm in the same boat as well. I'll pull some of their error messages I've gotten with LG Flash Tool this afternoon. I've tried 2014 and 2017. Both to no success.
I suspect it may be something with the /misc partition. Im going out on a limb, but I'm guessing that the AOSP and Lineage ROMs may touch misc. That partition may have some key identifiers for the LG tools. And the KDZ doesn't have a misc partition embedded inside it.
I was hoping the kdz file I was able to grab from the Lg Support tool would be different from regular stock rom 14a that is available around the internet but it appears to be exactly the same file (based on the file size). My original hope was that the file would support "Refurbish" option in the LGUP tool but it only works with "Upgrade".
I wonder if the "Refurbish" option would fix this and re-flashed all partitions - if only we could find a kdz file that would work with the refurbish option. So far all files I tried (11a, 13a, 14a) only support the upgrade option.
Thanks for all of your helps, I used LGUP and WondersMobile application on the computer and LGUP can not see the port. I did un-install the WondersMobile and LGUP can see the port and finally upgraded to latest firmware.
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
kloubik said:
I have the same issue - I was on Lineage os and flashing the OTA update caused bootloop to recovery. So I wanted to flash back to stock using LGUP and 14A. I did that before without issues.
This time though all installed fine but after reboot the phone immediately goes to fastboot, exactly as described above. I just spend several hours trying to fix it but with no results. The LG Bridge won't recognize the phone no matter what I do in Windows (tried 3 different PCs). On a Mac it will start connecting and will end up saying "you need to enable MTP connection".
From what I garther the stock rom flashed fine - the factory reset works, even shows "erasing data", the LG UP recognizes the phone as 14A (I tried 11A, 13A too - seems to install fine but goes immediately to fastboot after reboot).
The only thing I realized I did different when flashing the stock rom with LGUP was not using the original LG USB cable. But reflashing with original cable makes not difference now - still going to fastboot.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I too am having same problem. I've tried all the images from 11A to 14A, all of them flash with no errors on LGUP and every time LGUP detects the phone as having the last version flashed. Unfortunately, the phone also boots to fastboot every time. Nothing else to add to your descriptions at this time I'm afraid...
gewecht said:
Sadly I'm in the same boat as well. I'll pull some of their error messages I've gotten with LG Flash Tool this afternoon. I've tried 2014 and 2017. Both to no success.
I suspect it may be something with the /misc partition. Im going out on a limb, but I'm guessing that the AOSP and Lineage ROMs may touch misc. That partition may have some key identifiers for the LG tools. And the KDZ doesn't have a misc partition embedded inside it.
Click to expand...
Click to collapse
I am absolutely positive my problem is at least in part due to a messed up /misc partition though. @gqo actually described what I did pretty thoroughly in his thread, albeit in a G5. Post #9 has the fix but it didn't work for me.
I've also stumbled upon a menu under the Firmware Update screen that I had never seen before and cannot fin any mention to... Would any of you guys know what it is for? It reads something like:
Code:
** SELECT MENU **
** Select : Power Key(Long) **
** Move : Power Key(Short) **
-> MA-USB(WIFI) DL
POWER OFF
PHONE INFO
BACK
Okay, I figured it out. The menu, at least the first option, appears to be for Wi-Fi firmware update. I wonder what file the phone actually downloads... And if it would be able to fix our phones. The only unprotected network I had in hand was a mobile hotspot in my not-so-LTE Nexus 5, so I got as far the firmware download start but didn't risk it on such a slow and unpredictable network. On top of that my Nexus 5 has also gotten pretty good at bootlooping, that's why I got this G6 in the first place. If anyone out there has a reliable unprotected network and nerves of steel it could be interesting to see if the outcome of this update is different from the LGUP one.
How do you access this menu?
What I started working on yesterday is trying to build a image file for the Qualcomm Flash Image loader and see if I can flash the phone using this tool... But I have never used this tool before, right now it does not detect my phone - I need to work on that + see if I can correctly build the image file from kdz. I found some youtube step by step tutorials so we will see. I will post update on the progress tonight or tomorrow.
kloubik said:
How do you access this menu?
What I started working on yesterday is trying to build a image file for the Qualcomm Flash Image loader and see if I can flash the phone using this tool... But I have never used this tool before, right now it does not detect my phone - I need to work on that + see if I can correctly build the image file from kdz. I found some youtube step by step tutorials so we will see. I will post update on the progress tonight or tomorrow.
Click to expand...
Click to collapse
I'm not sure if there's a better way to do it, but I access it by removing the usb cable after I successfully get in Download Mode. Then I'm not sure if there's any specific key combo, I've been randomly pressing the power and the volume down buttons and at some point I get into that menu. In the menu though, for some reason, I think I can only select an option if I long press both the volume down and power buttons. The "POWER OFF" option has come in handy because so far is the only way I can actually turn my phone off. The "PHONE INFO" hasn't worked for me yet. The menu also reacts when you add/remove the microsd card... I wonder if it can be used for something other than a WiFi firmware upgrade. I haven't had the chance to connect the phone to a computer to see how the device is recognized, if at all.
And that image you're working on sounds like a neat idea, I wish I could help but I'm afraid I wouldn't have the skill. I may be able to test though. Anyway, Godspeed!
Unundra said:
I too am having same problem. I've tried all the images from 11A to 14A, all of them flash with no errors on LGUP and every time LGUP detects the phone as having the last version flashed. Unfortunately, the phone also boots to fastboot every time. Nothing else to add to your descriptions at this time I'm afraid...
I am absolutely positive my problem is at least in part due to a messed up /misc partition though. @gqo actually described what I did pretty thoroughly in his thread, albeit in a G5. Post #9 has the fix but it didn't work for me.
I've also stumbled upon a menu under the Firmware Update screen that I had never seen before and cannot fin any mention to... Would any of you guys know what it is for? It reads something like:
Code:
** SELECT MENU **
** Select : Power Key(Long) **
** Move : Power Key(Short) **
-> MA-USB(WIFI) DL
POWER OFF
PHONE INFO
BACK
Okay, I figured it out. The menu, at least the first option, appears to be for Wi-Fi firmware update. I wonder what file the phone actually downloads... And if it would be able to fix our phones. The only unprotected network I had in hand was a mobile hotspot in my not-so-LTE Nexus 5, so I got as far the firmware download start but didn't risk it on such a slow and unpredictable network. On top of that my Nexus 5 has also gotten pretty good at bootlooping, that's why I got this G6 in the first place. If anyone out there has a reliable unprotected network and nerves of steel it could be interesting to see if the outcome of this update is different from the LGUP one.
Click to expand...
Click to collapse
I'll play around a bit and see if I can land on this menu. At this point I'll try anything. I'm on an iPhone until I get this fixed - so I'm motivated!
I can setup an open guest network off my main wi-fi this evening and see what I can find out.
EDIT Sorry, I tried playing around here, but I couldn't figure out how to get back into the the menu you uncovered. If you could give some instructions on how to do it, I'm happy to give it a shot on my device.
I was able to access the menu today...what worked for me was at the firmware screen unplug the usb cable and then press volume down and power button three times quickly. I tried to connect to a wifi and it does not really do anything. I think it just establishes wifi connection but it does not download anything on it's own - it's waiting for another connection.
Also I got stuck with building the image file from kdz, it has no information on partitions. At this point I decided to ship to LG for a quote and will see how much they will ask for a reflash.
I got as far as selecting a network and getting some sort of a download start screen, but I interrupted it right away so I wasn't sure the download would actually go through... Apparently it does not. If this menu has some sort of flashing capabilities though, it might be worth checking how secure it is. If someone can get it to download and flash a modded file perhaps there could be a chance of flashing a custom recovery or something... I'm thinking about those guys that have an unlockable bootloader (which we ironically also have now).
Anyway, all of this goes well beyond my skill so I followed your example and submitted a repair service request to LG. It'll take quite long but shipping is free, so I figured I'd give it a try. I'm assuming this is an easy fix with the right software tools, so I hope LG doesn't overcharge for it. I'm even half hoping they'll do it under the limited warranty... If I recall correctly unlocking the bootloader doesn't immediately void all warranty, there's room to prove the bootloader was never actually unlocked. And after all LG does say that once unlocked, it cannot be undone and our phones are, in fact, running stock firmware and have a locked bootloader.
Update: My phone was received today by LG. In LG's Track Repair page, the status briefly showed as Undergoing Diagnostic but quickly moved to Repair In Progress, it's current status. Given that LG was supposed to contact me in case the repair was not covered by the limited warranty, meaning that an extra fee would've to be paid, I'm assuming the phone will be fixed (if possible, that is) free of charge. I will update you guys again soon, but if anyone out there is still struggling with this issue I'd recommend considering sending the phone to LG.
I have the exact same problem. Please keep us in the loop of what happens to your phone with LG
My phone has been received by LG for this issue on 9/26. It quickly moved through diagnostic to "repair in progress" on the first day plus showed ETA back to me in 6 business days. Ever since that it's stuck in that mode, no update or contact from LG. I check the status every day - every day it says the same - ETA 6 business days. It's been a week and half now with no update. I kind of expected it's going to take 2-3 weeks but annoyed that they say 6 days ETA and then you don't hear from anyone for almost 2 weeks with no change in status.
Update #2: The status finally moved to Shipped To Customer. I haven't been contacted by LG yet, so I guess the phone could've been shipped fixed as much as it could've been shipped as is for being unfixable. Either way, I wasn't and most likely won't be charged. FedEx hasn't got an ETA for the delivery, but I'll let you guys know as soon as I get my phone back.
Edit: Got an e-mail from LG. It reads something like:
Defect: Software failure
Payment Type: NOT APPLICABLE
Repair Results: S/W upgrade (download)
Repair Cost: $ 0.00
Warranty Status: In Warranty
Tax: $ 0.00
Total: $ 0.00
I guess I got away with it, I hope you guys do too.
Sent from my Nexus 5 using Tapatalk
I ran into a bit of an issue and am stuck with a bootlooping G6 US997.
What got me into this pickle:
I unlocked the bootloader
I flashed TWRP successfully, by:
Running fastboot flash recovery TWRP.img
Unplugging USB and holding Vol- and Power from fastboot, then lifting and re-pressing Power when the LG logo appeared
Hitting Yes, Yes
Being in TWRP and allowing modification of System
Formatting Data (Wipe > Format Data > Yes)
I installed the DM verity and encryption file so that it would boot
I wiped Cache/Dalvik
I rebooted into System
It booted successfully so I went back to TWRP and installed Lineage OS, Open Google Apps, and the Lineage SU addon
This booted successfully, so I went and with OEM unlock disabled booted into fastboot to see if I could get rid of the annoying orange screen at the start saying that the bootloader was unlocked
To do this, I ran fastboot oem lock, not seeing/ignoring the red text at top telling me to Please check "Enable OEM unlock" in Developer options.
I then rebooted with fastboot reboot and I encountered a red warning: "Your device has failed a routine safety check and will not boot." It is now in a bootloop at that screen, cycling between black, the LG logo, and the warning.
I managed to enter recovery mode (with the key-combo) and got the stock recovery "factory reset and wipe" option, which I had been previously getting when entering TWRP, so I selected "Yes, Yes" and then it went back into the bootloop, completely avoiding TWRP.
Where I currently am:
I can get into fastboot mode (Vol- with usb plugged in) and I can get into the factory reset mode which is the gateway into TWRP. I cannot get into TWRP, and I cannot flash anything, boot into any images, or unlock the bootloader ( Please check "Enable OEM unlock" in Developer options). If I could do that I think I can get it fixed.
My questions:
How can I do the OEM unlock without access to Developer Options? (I have the unlock file to flash, just need access)
Or How can I bypass the red warning page and boot into Lineage OS?
Any help would be appreciated, I really would like to get this working.
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Killua96 said:
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Click to expand...
Click to collapse
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? If there were a way to keep it in download mode longer, that would really help. Thank you for replying, I've seen your name around the forums!
mwsundberg said:
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. It looks like it might still be in download mode, but interrupted by the warning, the way the screens flash. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? Thank you for replying, I've seen your name around the forums!
Click to expand...
Click to collapse
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Killua96 said:
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Click to expand...
Click to collapse
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
mwsundberg said:
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
Click to expand...
Click to collapse
You can't, fastboot is a mode that allows many things but it's not a God-like mode where you can do everything.
By locking the bootloader while having unsigned partions flashed you have essentially hard bricked the device, and if the only way to flash stock signed partitions (lgup+Uppercut) doesn't work it means that you have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Killua96 said:
You have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Click to expand...
Click to collapse
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
mwsundberg said:
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
Click to expand...
Click to collapse
It depends on how much it'll cost to you a new G6, they could ask you maybe 200-250 bucks.
mwsundberg said:
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Click to expand...
Click to collapse
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Killua96 said:
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Click to expand...
Click to collapse
Managed to get a messed up G6 from a friend working again. Thanks. XDA forever
Guys, need help !!!
I have tried to install SEA oreo version on Indian phone via LGUP... Flash was successful (100%) but it got stuck on LG Logo..
Procedure followed for H870DS (IND)
1. Downloaded SEA Oreo KDZ File (H870DS20a_00_OPEN_SG_DS_OP_0518.kdz)
2. Installed LGUP... Made new Common folder inside C/Prog file/LG/Model
3. Extracted DLL file from KDZ & renamed it LGUP_Common.dll and kept in Common folder
4. Entered in download mode
5. Opened LGUP.. selected KDZ and Upgrade..
6. Boom.. 100% completed.. it has shown that phone is rebooting..
7. But then it got stuck on LG Screen
I cant access recovery now
I can open Hard Reset option (Vol down+Power) only.. Made hard reset but no use
I cant enter in download mode
I dont know if it is charging or not
It is not even switching off by pressing power button for long time
Pl help me...
---------- Post added at 08:33 PM ---------- Previous post was at 08:30 PM ----------
it has anything to do with "Enable OEM unlock" in Developer options"
There is a way to enter download mode. Just hold down button and power button. Just when you see LG logo leave power button for a second. Push power button again and hold with down button. Now press yes twiche for the hard reset prompt. Now IMPORTANT, when screen goes black immediately press and hold up button. While holding up button plug usb cable into the PC. Now use Uppercut 1.0.0.0 and flash your kdz.
Same issue, Just that I was trying downgrade to Nougat. Oreo messed up my phone to the extent that, none of the sensors (including Fingerprint are not working). The load was a success, but after 1st restart it went into boot loop.
I only had USB Debug enabled in the DO before this issue, so it might work with the OEM unlock dissabled.
Software needed...
LG Bridge
Meathod...
Please charge the phone before this is done, at least 80%, will be better.
Connect the computer with LG G6 H870DS (Indian), might work for all models. "not tested"
If the USB debug is enabled, you will hear the USB disconnection and connection notification sound during bootloop
When you hear disconnection sound, press the "volume up key" until the Firmware Update mode appears
Once you are in Firmware Update mode, the USB connection will be stable (In bootloop, it keeps disconnecting)
Disconnect the USB cable
Start LG Bridge/Software Updates, connect when App asks to connect the phone
This will update you phone to the latest official software update..
This solution can work for all phones that have a hardware based menu to get into Firmware Update mode, definitely works on all LG phones to get out of bootloop. I have tested on LG G2, G4 and G6 Indian devices.
And a suggestion to all mates is, to enable USB debugging and the OEM unlock as soon as you get hands on your new devices. Always saves the hassle of running around the LG service center, its a big issue in India at-least. I love LG for its hardware quality but sadly LG smartphones have a bad history of software issues
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
I can abd sideload and update from SD card, but everything I have fails signature verification.
edit: so frustrating trying to find that 1 zip
Dizzee said:
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
Click to expand...
Click to collapse
Just use MiFlash, that one's guaranteed to work. Read my DFU unbrick guide to know how to use it. Just skip the part where you have to disassemble the phone, since you can get to EDL mode by (with the phone off and the USB cable connected to the PC) holding both volume buttons and inserting the USB-C cable to the phone.
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Dizzee said:
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Click to expand...
Click to collapse
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Choose an username... said:
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Click to expand...
Click to collapse
I got it from here: http://www.ztedevice.com/support
selected:- United Kingdom > Mobile Phone > Axon 7
it offers a file "AXON 7(ZTE A2017G) SD card software package(328540B2634ZTE A2017GV1.0.0B11)"
which hints at being compatible with A2017G... but is A2017V and is chinese, although you can change the language in settings there is still plenty here and there, plus chinese bloatware
and No, I didn't get cell signal.
I've gone back to Marshmellow, I will try again, didn't think it would be so different/difficult... Although wow at MiFlash.
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Dizzee said:
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Click to expand...
Click to collapse
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Choose an username... said:
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Click to expand...
Click to collapse
... after I finally got it working again (thanks for the assist), I thought relocking it was just making it secure again. I been rooting/unrooting and swapping out roms since the galaxy s2, who'd think you can't unlock and relock... I do think there should be warnings as it is too easy a mistake to make... lmao stop doing dumb stuff you start first
My phone is insured so I'm not overly fussed, but others will be less fortunate.
hello everywone...i have a troble to...my phone is A2017GV1.2.0B04 like this in post.
I bay this phone whit broken screen, i change the screen and try sim card but the phone is locked Whit google account... When I try my sim to test microphone, the phone it's work OK, but I unlock google account whit add tools and after that my phone don't have a service.
Phone tells no service or turned off airplane mode...what is not true... I can change the 4g/3g/2g connection to only 3g or something else... Wi-Fi and everything else work great but no service... The phone see what operator is on sim but no service... Somebody to help me please and tell me some tutorials how to fix?
I by this phone from Denmark and now I'm in Serbia... Eny help please
Thanks anyway Dragan
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
Mistake,whit adb tools...