Related
I got a lenovo vibe shot z90-7 which was using Android 5.1. I found an upgrade rom on needrom to 6.0. I flashed it using qfil (qualcomm flashing tool) and it went all right, all functional. But I also wanted to unlock the bootloader and install a twrp (I found a procedure and twrp image on a russian forum). I followed the steps but it didn't work, I still wasn't able to unlock the bootloader. Thus, I was not able to enter fastboot anymore: from adb I was typing "adb reboot bootloader" and the device would reboot normally, not in fastboot mode. I decided to change to another rom (from needrom) which was claiming would allow you to unlock the bootloader. So, without hesitation I flashed it in qfil (edl mode) and it went all right, but I got stuck in boot loop. After the splash screen, the device shuts the screen off and does a long vibration and stays like that. If I connect it via usb to my pc I get a some "need to format drive" alerts, and in qfil I see "Qualcomm HS-USB Diagnostic 9006 (COM5)". If then I try to flash the rom I get this log:
Code:
Start Download
COM Port number:5
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
It's seems like I need to get in Edl mode first, but I cannot use adb and pushing vol+ and plug the usb at the same time (or a little bit first one or the other, I tried all) does't do anything but booting the device normally.
I also tried getting in fastboot mode (keep vol- and power button) but it doesn't work.
I read of an "engineering mode" by keeping vol- on boot. It does something, the screen becomes black, but it's on. On my pc the adb driver comes in in the popup, like if I'm in fastboot or adb, but on "fastboot devices" I can't see anything, while on "adb devices" I see a device, which is "? unauthorized". Strange to me, I can't do much with it since it's unauthorized and the screen on the device remains black. And after a few seconds (about 30) it gets back to long vibration and screen off state.
I can get into the stock recovery by holding vol+, vol- and power, but it's a very poor recovery. All I can do is reboot, shut down, wipe data and update. I tried to use "update" and put a zip file of an official rom downloaded into the sd card and named "update.zip" as suggested by the recovery, but I get an error (with no technical information about what kind of error), so no luck with that either.
I tried to force the qualcomm driver from "Qualcomm HS-USB Diagnostic 9006 (COM5)" to "Qualcomm HS-USB QDLoader 9008 (COM5)", then tried to flash using qfil, but I still get an error, even if this time is different:
Code:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I finally tried to download the rom in .qsb format and get in engineering mode again, but the screen remains black and no sign of flashing possibilities.
Please help, I tried everything it came to my mind.
I also tried with miflash, but still got errors...
Thank you
Hello, did you solve the problem? i have the same as you....
regards
Hi guys.
I had the similar problem few moths ago. I tried to remember what i've done to fix it, but I don't remember all things, I hope this steps helps to find the solution.
Check this:
-Use Windows 7 (I tried with Windows 10 and always appears some errors)
-Use original miniUSB cable or good quality cables
-Install Lenovo Usb drivers
Turn ON phone and press Vol+ and Vol-, hold 3 seconds
If you cant enter Recovery mode (because is corrupt or bricked), phone will vibrate for 1-2 seconds and screen keep black. Now connect USB cable (check drivers, also if Qualcomm HS-USB QDLoader 9008 was installed)
Once you done, use QSFL or MiFlash (but not 2016 version!, never works to flash)
NOTE: I had some problems with my desktop computer with Windows 7 but no problem in laptop. So check it in more than one...
Good luck.
How I fixed this
I fixed it installing a update.zip via recovery (vol + plus vol - plus power) I found here
http://forum.xda-developers.com/android/development/vibe-shot-6-0-update-root-xposed-t3409989
This not fixed the phone , but allowed me to unlock bootloader entering in fastboot mode (vol + plus vol - plus plug usb) using this
http://lenovo-forums.ru/topic/18149-lenovo-vibe-shot-разблокировка-bootloader/
Then I was allowed to install TWRP as explained here
http://lenovo-forums.ru/topic/18150-lenovo-vibe-shot-расширенное-рекавери-twrp-by-sevenmaxs/
Then I was able to go to TWRP terminal and type
reboot edl
Phone went into downloader mode and I was able to install this rom with QFIL
http://www.needrom.com/download/lenovo-vibe-shot-android-6-0-1-1625-encn-unlocked/
and I restored NVRAM with a qcn file I found in Ebay after putting the phone in diagnostics mode. Then I changed imeid, meid and esn to the original ones I found in the box. Phone fixed.
Just note that this file was for a Z90-7 rom and it will not work with a Z40a20 rom.
Hope this helps someone.
francesco9696 said:
I got a lenovo vibe shot z90-7 which was using Android 5.1. I found an upgrade rom on needrom to 6.0. I flashed it using qfil (qualcomm flashing tool) and it went all right, all functional. But I also wanted to unlock the bootloader and install a twrp (I found a procedure and twrp image on a russian forum). I followed the steps but it didn't work, I still wasn't able to unlock the bootloader. Thus, I was not able to enter fastboot anymore: from adb I was typing "adb reboot bootloader" and the device would reboot normally, not in fastboot mode. I decided to change to another rom (from needrom) which was claiming would allow you to unlock the bootloader. So, without hesitation I flashed it in qfil (edl mode) and it went all right, but I got stuck in boot loop. After the splash screen, the device shuts the screen off and does a long vibration and stays like that. If I connect it via usb to my pc I get a some "need to format drive" alerts, and in qfil I see "Qualcomm HS-USB Diagnostic 9006 (COM5)". If then I try to flash the rom I get this log:
Code:
Start Download
COM Port number:5
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
It's seems like I need to get in Edl mode first, but I cannot use adb and pushing vol+ and plug the usb at the same time (or a little bit first one or the other, I tried all) does't do anything but booting the device normally.
I also tried getting in fastboot mode (keep vol- and power button) but it doesn't work.
I read of an "engineering mode" by keeping vol- on boot. It does something, the screen becomes black, but it's on. On my pc the adb driver comes in in the popup, like if I'm in fastboot or adb, but on "fastboot devices" I can't see anything, while on "adb devices" I see a device, which is "? unauthorized". Strange to me, I can't do much with it since it's unauthorized and the screen on the device remains black. And after a few seconds (about 30) it gets back to long vibration and screen off state.
I can get into the stock recovery by holding vol+, vol- and power, but it's a very poor recovery. All I can do is reboot, shut down, wipe data and update. I tried to use "update" and put a zip file of an official rom downloaded into the sd card and named "update.zip" as suggested by the recovery, but I get an error (with no technical information about what kind of error), so no luck with that either.
I tried to force the qualcomm driver from "Qualcomm HS-USB Diagnostic 9006 (COM5)" to "Qualcomm HS-USB QDLoader 9008 (COM5)", then tried to flash using qfil, but I still get an error, even if this time is different:
Code:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I finally tried to download the rom in .qsb format and get in engineering mode again, but the screen remains black and no sign of flashing possibilities.
Please help, I tried everything it came to my mind.
I also tried with miflash, but still got errors...
Thank you
Click to expand...
Click to collapse
Hi, did you slove the problem? Same situation with me. But I managed to install twrp ( Chinese) but I can't install any rom .. After successful flashing it reboot with lenovo logo, then long vibrates.. When I connect it to PC. It show number of partition and need to format popup.. I tried different ROMs.. All via twrp. I don't use miflash or qfil.. If you have solved it please share how. Thanks.
i know how to enter in edl mode in z90-7 or z90a40
Hello
This is nisar I successfully entered in edl mode and flashed rom to know the procedure pm me on +919743392420 WhatsApp
Bricked Vibe Shot - multiple partitions in device manager - no edl
having read all the above I'd like to share small info once again, it is all about correct qualcomm drivers, you can get them from androidurdu.net, do not search on the site but click on mobile drivers then scroll down and download qualcomm usb drivers.zip . unpack and use "checked" folder within the zip, they are signed and work on any windows including 10th. You see, your brick might be having an edl times, but PC doesn't know without proper drivers installed. You might want to remove all earlier/bad driver versions, for example try sigverif command or just install below qualcomm drivers and try away.
1. connect phone with good usb cable, 2. press power button till it shuts, then release power button and press volume up and down same time and phone will enter edl mode itself almost instantly, if you had twrp installed then it'll enter there, if so run from terminal "reboot edl"; keep device manager open and comm tree will appear along.
other way is via adb reboot edl command, if fastboot doesn't work, or fastboot reboot-edl
on miflash when refreshed you see the short port name and the number like com4 or 3. now it's time to flash, but the last proven flash I did with QiFL, Miflash works as fine.
i used latest international marshmallow version. after first boot, within dev mode unlocked oem + enabled adb and connected to PC with phone turned on in order to accept handshake prompt.
unlocking bootloader is easy via adb command: adb reboot bootloader, then: adb bootloader unlock-go .
all files are available online via some russian speaking forum, you just need to install twrp, then place su.zip onto phone (I copied on internal memory), boot into twrp and flash; if clean - no errors flash then you got neatly rooted marshmallow phone.
my struggle with bricked vibe shot was worth it. earlier I noticed cpu was running high, all cores all the time. also many google apps which I wanted to eliminate for draining the battery and uploading stuff all the time.
right after flashing su.zip boot into phone and install kernel adiutor from play store, then take control of how your 8 cores behave. I discovered the minimums were set at 800+Mhz so I dropped them to 200, then below within cpu section enabled all "disabled" options for boost + enabled "ondemand" + plus few more. You got to understand the process and enjoy tuning your phone your way.
I've charged my vibe shot 3 hours ago and was randomly chatting on whatsap until now and I have 73% battery. Day before yesterday before the bricking, full charge would not last more than 3 hours, incredible battery performance thanks to "adiutor" .
One more important thing, use correct rom version for your phone because of advanced camera and specific drivers camera won't work well.
Names of files used to make my phone a super hero:
1. adb-setup-1.4.2.exe
2. Miflash_140509.exe
3. Qualcomm_USB_Drivers.7z via androidurdu.net
4. TWRP-3.0.2.0_Z90a40_by_SevenMaxs.rar - has .bat files inside; enter bootloader mode and shoot
5. UPDATE-SuperSU-v2.76-SYSTEMMODE-PRO.zip (I pay for my apps including supersu pro)
6. Z90a40_Android-L_unlock_7M.7z , or use command line via adb shell.
7. Z90a40_S363_160625_ROW_QPST.7z - latest intl Mashmallow Os , to make it more perfect download marshmallow google dialer - patched.apk.
8. QPST / QIFL , used to flash the above rom
I'm not a pro so small mistakes are acceptable, I hope.
ciao.
francesco9696 said:
I got a lenovo vibe shot z90-7 which was using Android 5.1. I found an upgrade rom on needrom to 6.0. I flashed it using qfil (qualcomm flashing tool) and it went all right, all functional. But I also wanted to unlock the bootloader and install a twrp (I found a procedure and twrp image on a russian forum). I followed the steps but it didn't work, I still wasn't able to unlock the bootloader. Thus, I was not able to enter fastboot anymore: from adb I was typing "adb reboot bootloader" and the device would reboot normally, not in fastboot mode. I decided to change to another rom (from needrom) which was claiming would allow you to unlock the bootloader. So, without hesitation I flashed it in qfil (edl mode) and it went all right, but I got stuck in boot loop. After the splash screen, the device shuts the screen off and does a long vibration and stays like that. If I connect it via usb to my pc I get a some "need to format drive" alerts, and in qfil I see "Qualcomm HS-USB Diagnostic 9006 (COM5)". If then I try to flash the rom I get this log:
Code:
Start Download
COM Port number:5
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
It's seems like I need to get in Edl mode first, but I cannot use adb and pushing vol+ and plug the usb at the same time (or a little bit first one or the other, I tried all) does't do anything but booting the device normally.
I also tried getting in fastboot mode (keep vol- and power button) but it doesn't work.
I read of an "engineering mode" by keeping vol- on boot. It does something, the screen becomes black, but it's on. On my pc the adb driver comes in in the popup, like if I'm in fastboot or adb, but on "fastboot devices" I can't see anything, while on "adb devices" I see a device, which is "? unauthorized". Strange to me, I can't do much with it since it's unauthorized and the screen on the device remains black. And after a few seconds (about 30) it gets back to long vibration and screen off state.
I can get into the stock recovery by holding vol+, vol- and power, but it's a very poor recovery. All I can do is reboot, shut down, wipe data and update. I tried to use "update" and put a zip file of an official rom downloaded into the sd card and named "update.zip" as suggested by the recovery, but I get an error (with no technical information about what kind of error), so no luck with that either.
I tried to force the qualcomm driver from "Qualcomm HS-USB Diagnostic 9006 (COM5)" to "Qualcomm HS-USB QDLoader 9008 (COM5)", then tried to flash using qfil, but I still get an error, even if this time is different:
Code:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I finally tried to download the rom in .qsb format and get in engineering mode again, but the screen remains black and no sign of flashing possibilities.
Please help, I tried everything it came to my mind.
I also tried with miflash, but still got errors...
Thank you
Click to expand...
Click to collapse
have you try
adb reboot edl
Hey, I have the same problem as you, trying to do the step you did, but I get stucked at the first step,
I cannot find the file UPDATE.ZIP in the page from your link....
Could you help?
Thanks
josepgb said:
I fixed it installing a update.zip via recovery (vol + plus vol - plus power) I found here
http://forum.xda-developers.com/android/development/vibe-shot-6-0-update-root-xposed-t3409989
This not fixed the phone , but allowed me to unlock bootloader entering in fastboot mode (vol + plus vol - plus plug usb) using this
http://lenovo-forums.ru/topic/18149-lenovo-vibe-shot-разблокировка-bootloader/
Then I was allowed to install TWRP as explained here
http://lenovo-forums.ru/topic/18150-lenovo-vibe-shot-расширенное-рекавери-twrp-by-sevenmaxs/
Then I was able to go to TWRP terminal and type
reboot edl
Phone went into downloader mode and I was able to install this rom with QFIL
http://www.needrom.com/download/lenovo-vibe-shot-android-6-0-1-1625-encn-unlocked/
and I restored NVRAM with a qcn file I found in Ebay after putting the phone in diagnostics mode. Then I changed imeid, meid and esn to the original ones I found in the box. Phone fixed.
Just note that this file was for a Z90-7 rom and it will not work with a Z40a20 rom.
Hope this helps someone.
Click to expand...
Click to collapse
Sorry if it's reviving the thread but i found a way to unbrick the device from this state. Not sure if will work for all models because this one was a really weird one (almost all button combinations were different than any described on the internet). So my phone was from China (Z90-7 - later it showed that it's a Z90A40 and I had to flash that firmware) with a international chinese ROM and it god badly bricked (no edl, no lenovo recovery, locked bootloader etc. etc.). Now, when holding [vol+]+[vol-]+[pwr] (usually recovery mode according to the internet) it went into the Qualcomm 9006 diagnostics mode that shows a million partitions. There was no way i could get it into edl mode but there was the so called factory mode that is accessed by holding [vol-] and plugging in the usb before it vibrates. Through this I managed to flash firmware in .qsb format from a SD card and successfully unbricked the phone that I almost threw into the bin.
1. Check if your phone has "factory mode" [vol-]+[pwr] then release [pwr] or hold [vol-] while inserting usb cable.
- make sure to try different combinations, the button combinations on my phone were much different than what I mostly found on the internet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Download Vibe Shot firmware in .qsb format (Google it, the phone will warn you if it's not the right one (A40 or -7))
3. Copy the .qsb file into SD:/sdfuse
4. Insert the SD card into the phone (maybe a restart will be needed for it to be detected, you should see a message saying "DEV: External storage" when you select sd flash)
5. Select "SD update" and follow the instructions.
I hope this helps someone who can access the factory mode. This is so easy and I couldn't believe that there is so little information on flashing it this way.
Good luck.
i wonder how do you change HS-USB Qualcomm 9006 become HS-USB Qualcomm 9008?
Hi,
I'm after some advice, how do I place the Moto G5 in Qualcomm mode or EDL mode.
I have entered the bootloader by holding down and turning the phone on, this allows me to use fastboot.
From there I can scroll down to QCOM, but when I press the power button it boots into the normal system instead of EDL mode.
I have also attempted from within fastboot to use:
fastboot oem edl
fastboot oem qcom-on
fastboot reboot emergency
and
fastboot reboot-edl
Although non of these have been sucessful.
I also have access to an EDL cable, although, when I plug the phone in, then flick the switch 10 seconds later, it does not enter EDL mode, it just charges.
The phone sometimes shows as File Storage Linux USB Gadget in device manager, although it is inaccessible, I have updated the laptop to use the qualcomm drivers, although I don't think it will ever recognise it if I can't put the phone into qualcomm mode to begin with.
Any help would be much appreciated.
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
TheFixItMan said:
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
Click to expand...
Click to collapse
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
jameswstubbs said:
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
Click to expand...
Click to collapse
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
TheFixItMan said:
Sounds dodgy to me - sounds like your trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
It's not dodgy, but I fully understand.
Thank you anyway.
try fastboot -i 0x2b4c oem reboot-edl (it's working for LENOVO ZUK Z1 and ZUK Z2)
You can try (if you can/have the TWRP image) to flash TWRP and in reboot options select EDL.
In case the bootloader isn't unlocked you can also use fastboot boot [TWRP image name] to boot directly into TWRP without flashing and then repeat, go into reboot options and select edl.
Not sure if it works for you, if it does let me know that I have helped!
TheFixItMan said:
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
Hello,
We've had this phone for almost 2 years now. Never rooted, it was used by an elder in the house for watching youtube videos and reading news. A few days back, the device went into Fastboot mode (with only two choices available, once in fastboot mode - Reboot & Recovery) for inexplicable reason (no I wasn't trying to root or flash a custom rom; I'm a techie but not this much into Android) and no matter what I tried, it would keep booting back to the same mode. None of the following worked:
1. Keeping the power button pressed for 15-30 seconds.
2. Clicking Reboot.
3. Clicking Recovery.
After the aforementioned measures didn't work, I took the phone to a service center. They claimed that software was not getting downloaded into the device and that it's motherboard needed to be replaced (I should point out that before this issue popped out of nowhere, the phone was working perfectly fine; no battery issues, no performance problems, etc.). I refused to get the motherboard changed, brought back the phone and hooked it up with a PC and ran a few fastboot commands. Here are the observations:
1. "fastboot devices" - shows device id (which means drivers are fine and device is accessible).
2. "fastboot reboot" - phone reboots to fastboot mode (again!)
3. "fastboot continue" - phone moves beyond fastboot mode. Almost instantaneously, Vivo logo comes up and in the top left corner, I see the message " any key to shutdown" (the word "Press" before "any" is not visible).
4. "fastboot oem unlock" returns "unknown command" error. (NOTE: I had never enabled "OEM Unlocking" in Developer Options.)
5. all other fastboot commands return "unknown command" error.
After some digging, I learned about the EDL mode, how to enter it and flash stock ROM using QFIL for unbricking purposes. I was able to successfully enter EDL mode after shorting the test points. After several attempts to flash stock ROM, my swift progress was finally halted by the EDL authorization issue:
INFO: Target Said: ret_auth = -1
INFO: Target Said: "Warning: Unauthorized tag 'program'"
(I can post the full log, if needed).
So here's my question: how do we get past this EDL authorization issue ? I've gone through the forum for Vivo V9 and also scoured the web but have not seen anyone getting past this issue successfully. I'm not particular in bypassing this security mechanism by any shady means; I'd be really glad if Vivo service center or customer support helped. But Vivo hasn't been helpful at all; they're maintaining that their service center's diagnosis is final. Apparently there's no grievance redressal process by which I can get a more senior support team to double-check the conclusions of the service center.
Looking forward to inputs from the community here; any help would be appreciated.
Thanks,
AS.
I was using my oneplus 7T normally without root and with bootloader locked when it decided, out of nowhere, to fall into "Qualcomm Crashdump Mode". When I tried to reboot it, it just went into "Qualcomm Crashdump Mode" again. So I went into fastboot mode, unlocked it, and flashed an european ROM from here: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T/ . However when the device tried to boot up it just went to "Qualcomm Crashdump Mode" again, so I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) ( https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/ ) and it worked, but this time when the device attempted to boot up it went into EDL mode and the bootloader was locked and when I tried to unlock it, it gave me an error related to "OEM unlock" not being enabled in developer options. So I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) again, and somehow this time it actually booted up. Still, after 10 seconds it went into EDL mode AGAIN (note: at this point, I couldn´t get out of EDL mode, I could only boot into anything else after the battery died, in the first boot). So I downloaded another ROM for msm but this time it gave me the error: Firehose GetUsInfo Failed, and the phone seems to disconnect and reconnect. From here I tried multiple ROMs for msm and always received the same error, even using the one I used originally. (Note: I have been waiting for my battery to die for 5 days, and it still has power; also tried removing the battery )
Commands I tried to unlock bootloader:
fastboot oem unlock; fastboot oem unlock-go; fastboot flashing unlock; fastboot flashing unlock_critical
Can someone help me with this issue?
Sorry if the description was too confusing, long, or had any mistakes in terms of English. I am just trying to be as complete as possible.
Hello @All,
I bought myself a new toy: a bricked Nexus 5x. The only thing I can do is enter the bootloader mode. Otherwise the phone is showing the Google logo.
In bootloader mode the last two lines are "Secure Boot - Enabled" and "Device State - Locked". The "fastboot devices" states that the device is present.
I can neither access any recovery nor install one (because bootloader locked). The device isn't rooted. Parallel to posting this I am searching the depths of the web. Of course without a solution.
Can I do anything else?
hmm, did you try going into the recovery and resseting it, if that didnt work go on your computer, go to bootloader mode, and on your computer try typing: fastboot flashing unlock or fastboot oem unlock, if none of those work, then try reflashing the firmware trough recovery or fastboot, here is the rom for adb sideload trough recovery...
here is a direct download cuz it wouldnt post the zip https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
I can't access the recovery, but I'll try fastboot again. "fastboot flashing unlock" and "fastboot oem unlock" don't work. I get a " FAILED (remote: 'oem unlock is not allowed')" message.
ok, try this, go in fastboot, and run this command, fastboot flash boot N2G47Z_4Cores.img with the img that i send you, if it works, then see if iit boots up!
it doesnt wanna send it, heres a link to download it https://www.dropbox.com/s/tm7qt98r6d7q2a6/N2G47Z_4Cores.img?dl=0
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Heinz- said:
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Click to expand...
Click to collapse
hey is there a way you can send me a video of what happens when it boots up and when you try to enter recovery, maybe i can still help.
if you cant here send it to my mail [email protected] , this is my mail since 2016 and zombie was mostly for minecraft . but then i was young, so yeah.
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Heinz- said:
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Click to expand...
Click to collapse
well it looks like a problem with either the ram, vibrator, or the partitions, sadly this happened with old nexus devices, so its a brick forever sadly. but if you want you can sell it online for parts.
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Heinz- said:
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Click to expand...
Click to collapse
Sorry if this is too late but are you sure you can't do anything with the phone?
To enter Bootloader Mode press and hold Vol Down + Power. You will automatically enter Fastboot Mode. You will see the settings of 'Secure boot' and 'Device State'
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
If you select Recovery Mode, wait until you see the 'Robot lying down' image and "No command" text appear on screen. Now hold Power button and briefly press the Vol up button. The 'Android Recovery' screen should now appear.
To enter LG 'Download Mode':
Power Off your phone.
Now press the Vol. Up button and hold it
Now Plug your phone into your computer using a USB cable
After a few seconds 'download mode' should appear on your phone screen, followed by a 'Firmware Update' screen.
If it doesn't enter LG Downoad Mode then check in your Windows Device Manager under COM/PORTS. See if you have connected in Qualcomm 9008 EDL (Emergency Download ) Mode. The connection will appear as Qualcomm HS-USB QDLoader 9008. You might have to download the Qualcomm driver for this to work.
If you can get into Recovery Mode or EDL mode you still have options! It depends how much time and effort you want to spend on a 7 year old phone with no sd card option.
You can become 'obsessed' like me, and buy a hot air gun solder rework station to try and reflow the solder under the MSM8992 chip to fix the 'bootloop of death'! NOTE: I have tried it on 3 bricked Nexus 5X and only got a temporary success on one phone - the other two I did a very good job of frying the chip! Mind you I now have alot of spare parts!
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Heinz- said:
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Click to expand...
Click to collapse
You will have to keep us updated. I looked at those motherboards but wasn't sure about them. What version of Android is installed? Do they come with a new IMEI or are they blank? etc. Taking a 5X apart is very straightforward with a couple of simple phone tools. There are plenty of Youtube videos that show you how to do it - it might save you having to pay "handy-Doc"!
No, it doesn't work. I can plugin the phone when it's in "Download Mode" but nothing more happens. After a few seconds the phone tries to boot again. The "Handy Doc" man gave me back the phone without asking for payment.
The motherboard is on its way from China to Germany. This can take several weeks.
Hi
I am sorry if I am posting this at the wrong place.
I bricked my Nexus 5x device flashing DivestOS on it.
I flashed two different LineagOS on this device successfully in the past and the genuine Android when I was rolling it back. It always worked, but not this time.
Trying to roll it back to genuine Android, there were errors that several ".img" was missing in the archive.
I tried to chat with Android developers on Matrix chat and also reported this problem here, on DivestOS forum, but they blame hardware and/or user mistake.
I took it farther to sort the device problem and made it unresponsive, the screen is black and it does not react to anything at all now.
All I needed to know if there is ANY way to bring this device back to life.
I found some "LGFlashTool_2.0.1.6" on one of the old forumes of (2016), but I did not try it, I believe it will not work, and wanted to know from Android developer's oppinion before I try anything else.
Thank you
---Update:
I opened it, unplugged and re-plugged the battery.
Was able to boot it into the fastboot menu.
1. secure boot - enabled
2. device state - unlocked
-Tried to flash the genuine Android (I did it several times and I know it works)
No success!
Please see the terminal screenshot attached for errors.
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
bjlabuk said:
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
Click to expand...
Click to collapse
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
balakarpo said:
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
Click to expand...
Click to collapse
Yea, looking at the log everything appears to be okay until that last line. Did you use flash-all.bat from the factory image bullhead-opm7.181205.001-factory-5f189d84.zip?