Related
Hi,
A friend of mine gave me his LG Spirit H440 with the boot error: Secure booting error
In his words he tried to update the software, the phone started to lag and after a reboot the error occurred.
The guy is simple user so installing custom recovery or rooting are out of the question.
Here is a video I made of the problem:
https://www.youtube.com/watch?v=fONioh6uNms
After removing the battery the phone starts for 2-3 seconds with Secure booting error and then powers off. After that it cannot start again until the battery is removed and then everything repeats.
I tried to connect it to the PC with Windows 8.1 and installed LG drivers, but nothing happens. It's not recognized.
Also tried to enter download mode with Vol Up and connecting the USB cable, but again it just displays the error and shuts down.
Is this soft or hard brick? I'll be grateful for any help and guidance.
Try to set it in "upload mode" and flash stock rom kdz
Sent from my LG-H440n using XDA-Developers mobile app
septix said:
Try to set it in "upload mode" and flash stock rom kdz
Sent from my LG-H440n using XDA-Developers mobile app
Click to expand...
Click to collapse
hey
how do i enter "upload mode"???
i have the same issue. please help.
dydbg said:
Hi,
A friend of mine gave me his LG Spirit H440 with the boot error: Secure booting error
In his words he tried to update the software, the phone started to lag and after a reboot the error occurred.
The guy is simple user so installing custom recovery or rooting are out of the question.
Here is a video I made of the problem:
https://www.youtube.com/watch?v=fONioh6uNms
After removing the battery the phone starts for 2-3 seconds with Secure booting error and then powers off. After that it cannot start again until the battery is removed and then everything repeats.
I tried to connect it to the PC with Windows 8.1 and installed LG drivers, but nothing happens. It's not recognized.
Also tried to enter download mode with Vol Up and connecting the USB cable, but again it just displays the error and shuts down.
Is this soft or hard brick? I'll be grateful for any help and guidance.
Click to expand...
Click to collapse
how did you solve this crappy error??
No I didn't manage to find a solution and no one was able to help me.
I returned it to my friend and he bought a new phone.
Sorry.
1. Power down the phone.
2. Connect USB cable to computer.
3. Hold Volume DOWN and insert the USB cable.
4. ??
5. Profit.
septix said:
1. Power down the phone.
2. Connect USB cable to computer.
3. Hold Volume DOWN and insert the USB cable.
4. ??
5. Profit.
Click to expand...
Click to collapse
im sorry for ignorance but FastBoot=Upload mode?
Same problem, is there a BOARD DIAG option for this phone?
Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all
phorcus said:
Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Rebel7022 said:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
finally it got detected but when i run MSM8994DownloadTool.exe as administrator and click on start nothing happens
https://1.bp.blogspot.com/-ZZ-sHUBv...ExaIdiLCYRNQCLcB/s1600/Screenshot+%284%29.png
this is where i am stuck please help guys i am in a fix :'(
Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.
pitrus- said:
Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.
Click to expand...
Click to collapse
yes i did still it doesn't work, any help would be appreciated
If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.
pitrus- said:
If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.
Click to expand...
Click to collapse
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager
phorcus said:
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager
Click to expand...
Click to collapse
Could it be that the actual screen is dead on your phone? But still, since the PC detects the debug port, it should start restoring the phones partitions when you start downloader tool and press the download button up to the left.
My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Used Twrp to flash Custom ROM, EDL still not fixed
sauerkraut17 said:
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Click to expand...
Click to collapse
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
levittc5280 said:
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
Click to expand...
Click to collapse
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
sauerkraut17 said:
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
Click to expand...
Click to collapse
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
Have the same issue as you do after installing the bootstack. but even with the adb reboot edl command my phone just restarts normally.. But my OS is working fine, is there any way?
Try to use volume up and volume down only and plugging in USB cable........
stinka318 said:
Try to use volume up and volume down only and plugging in USB cable........
Click to expand...
Click to collapse
Tried everything already. Can only get to DFU mode..
So, I have a similar problem: after flashing a new version of TWRP, now Recovery doesn't start. The problem is that I haven't any OS installed and the last chance to save the phone should be reflash stock by EDL... BUT EDL mode doesn't start if I press vol UP + vol DOWN during power on... (it became black with a red light, but if I digit "ADB devices" on ADB, no devices seems connected, and in the same way it's impossible to use Axon7Toolkit). So: no Recovery, no EDL mode, no OS installed, my phone is a paperweight.
Is there a method to save my Axon 7?
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
levittc5280 said:
My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
Click to expand...
Click to collapse
I had the same problem a few days ago. When I booted to EDL Mode the red led was instantly on but the PC recognized it somthing like ZTE Handset Device Mode.
1. You can download TWRP Treble by NFound and flash it via your TWRP. Then reboot to recovery again and under the reboot tab its possible to boot to EDL/9008 Mode.
2. You build a EDL Cable to get the device from the red light to EDL mode. Just open some usb cable and connect the green and black (all four) together, plug it in the device and press the power button
until the red light is gone and hold on two additional seconds. Then remove the cable and plug another working cable in and the PC recognize it as Qualcomm in EDL mode.
This is literally how I unbricked my device.
Syberclone said:
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
Click to expand...
Click to collapse
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
Did you resolve problem?
spasacamen said:
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
No need to order that cable... If you still can cancel it i'd tell you to do that. You made a mistake by changing the drivers, you had the "ZTE Handset Diagnostic Interface (DFU)" driver, and replaced it with the EDL driver.
This of course does not work because your phone is in DFU MODE instead of EDL. What you have to do is uninstall the device via device manager and also tick "Uninstall driver software for this device", then turn the phone off and enter DFU again, and then use MultiDL from this forum to enter EDL. After that, use MiFlash or EDL Tool, and try flashing a FULL EDL file
By the way ADB will only work on FTM mode or the recovery or on a working system. You won't get ADB on edl mode or dfu mode because they simply don't have adb working, it's normal
i never use xda but this quote thing is what i have aswell
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
all i see is the red light in edl, whatever i try it Always just goes to a red light and a black screen. this happened after trying to unlock the bootloader. i was in android 8 and tried to lock it, it messed it up as my Phone could not boot anymore, i flashed the stock android 6.0 or something that came with the axon 7 toolkit and it did work but when trying to unlock the bootloader as the device state suddenly was locked it broke the whole thing and i oped edl could save me but even that is broken just like what the person in the quote has
Well the only fix to get EDL mode is through test point, there's a thread of unbricking Axon 7 using test point, find it, you'll need to open your back cover to do this
This in case nothing works to get into EDL mode.
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Waancho said:
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Click to expand...
Click to collapse
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
ibphantom said:
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
Click to expand...
Click to collapse
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Waancho said:
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Click to expand...
Click to collapse
Okay, well even from there it's not showing up in XiaoMiFlash's device list
ibphantom said:
Okay, well even from there it's not showing up in XiaoMiFlash's device list
Click to expand...
Click to collapse
Did you try the edl tool AND different cables? I always test cables just to be sure.
Waancho said:
Did you try the edl tool AND different cables? I always test cables just to be sure.
Click to expand...
Click to collapse
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
ibphantom said:
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
Click to expand...
Click to collapse
Did you try flashing a full edl image for your phone?
Waancho said:
Did you try flashing a full edl image for your phone?
Click to expand...
Click to collapse
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
ibphantom said:
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
Click to expand...
Click to collapse
Have you tried using the EDL Tool?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Stupid question, did you take the SD card out?
Three days ago, my phone went off by itself and I had a hard time starting again, it was just loading the bootanimation, I tried to reinstall the ROM, but it did not go into TWRP, although the message Recovery appears on the screen, I insisted and after several attempts, I got into the recovery, formatted everything and I installed the AICP ROM again, and I had to restart,my phone freezes in the LeEco bootloader, then again I insisted until the ROM finally started, but soon realized that it was taking too long to start (30 minutes waiting and nothing).
So I rebooted again, and from then on, I can not go into any mode anymore, trying to access the TWRP, the phone only stays on the Recovery screen until reboot after 2 minutes, when letting the phone try to start the ROM, it only stays on the LeEco screen and restart after 2 minutes, when entering Fastboot, it enters the screen in Fastboot mode, but is not recognized by the computer, not even as unknown device, the same for Download mode.
Is there anything I can try?
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
tsongming said:
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
Click to expand...
Click to collapse
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode.sl Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Well that sucks, if you feel like sending to the phone to China for repair, you can find several shops that are offering to repair any damaged Leeco for $10 and an average cost of $30 for resoldering. On the TaoBao website, use Chrome for translation. Some of their ads mention overseas repair
If it's memory it would be an easy fix for them.
If you don't want to fix it, I highly recommend the Mi8 if it's within your budget, its a perfect phone and you can find them for close to $300. My brother has a Redmi note 6 Pro which is also really nice. He paid $190.
Good Luck.
Sent from my Xiaomi MI 8 using XDA Labs
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Check out this possible do it yourself fix : https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71