Most of the EDL related posts I've found are in relation to the Pixel 3. Since I've now encountered the EDL issue with my Pixel 4, and there doesn't seem to be a place for it yet, figured I'd get one started here.
There's nothing I can point to that could have caused the issue. Phone was working fine when I went to bed, and when I woke up, it had become a brick overnight. Restarting didn't help at all. Phone remains in EDL, confirmed by connecting to my PC. I was running the Android 12 Beta, though I don't believe it to be a contributing factor.
I'm assuming a catastrophic hardware failure at this point.
Have you already tried using the Pixel Repair Tool? It was specifically designed to work with Rescue Mode which is similar to EDL. Maybe a reflash is necessary.
V0latyle said:
Have you already tried using the Pixel Repair Tool? It was specifically designed to work with Rescue Mode which is similar to EDL. Maybe a reflash is necessary.
Click to expand...
Click to collapse
You need to have access to the Recovery Menu to be able to use the Pixel Repair Tool, specifically entering the Recovery mode. EDL is not the same.
@Amon Darthir are you able to get into bootloader? Hold volume down, then hold power button until phone restarts.
Is your bootloader unlocked? I'd try using the Android Flash tool and reflash all partitions.
sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.
V0latyle said:
@Amon Darthir are you able to get into bootloader? Hold volume down, then hold power button until phone restarts.
Is your bootloader unlocked? I'd try using the Android Flash tool and reflash all partitions.
Click to expand...
Click to collapse
Like Jojo said, EDL is not the same. The EDL is a layer BELOW the what we know as the bootloader. This is the bootloaders bootloader. If you are booting to the EDL, it's because the bootloader is likely corrupted. You can't boot to Fastboot, or what you'd think of as the normal Bootloader.
Essentially, without being Qualcomm, there's nothing you can do. (Unless you want to replace your main board for ~$450).
The issue is being tracked here, but support from Google is nearly non-existent.
Amon Darthir said:
Like Jojo said, EDL is not the same. The EDL is a layer BELOW the what we know as the bootloader. This is the bootloaders bootloader. If you are booting to the EDL, it's because the bootloader is likely corrupted. You can't boot to Fastboot, or what you'd think of as the normal Bootloader.
Essentially, without being Qualcomm, there's nothing you can do. (Unless you want to replace your main board for ~$450).
The issue is being tracked here, but support from Google is nearly non-existent.
Click to expand...
Click to collapse
I see, thanks
Hey!
I am glad I came up to this as I believe I may have a solution for you guys!!!!
V0latyle said:
I see, thanks
Click to expand...
Click to collapse
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode(like QFIL).
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"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"
}
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.
So these are some of my posts for some folks which had same problem, phone stuck at 9008 mode.
I have a lot of interest on this because I am working on a way to unlock any Google Pixel form it's career(which I already did), including the boot loader(which I am currently working on).
I am posting all of that on the Pixel 4 XL forums though.
The situation is this:
EDL mode is like a recovery mode which is available on any Qualcomm device, and it's the primary bootloader.
When the phone boots, it triggers the secondary bootloader(which is the one carriers lock, and it's this one you usually unlock when you want to flash stuff to your phone, like TWRP).
The idea behind this mode is to allow devs to use this to force flash firmware to get the device back and running in case Fastboot and ADB weren't available(basically, to solve the problem you guys are having).
In my case this is useful because I can use it to flash the unlocked firmware from Google and them unlock my phone (my phone is working perfectly on Android 12), and them flash stuff to it.
So if any of you guys try this, let me know how it went!
#mcl said:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode(like QFIL).
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
Click to expand...
Click to collapse
I no longer have my device, as I was able to wallop Google Support enough over the issue that they agreed to RMA the device, however, I'm curious how this would actually work.
The device only boots to EDL, so ADB isn't an option, neither is Fastboot. From what I've seen and understand, without a proper Firehose file, and an image from Qualcomm or Google themselves, there's basically no way to flash the device back to a working state (assuming it even can be).
Are there actual FULL Pixel images available, with bootloader and Android? (They sound to be packaged together). This would seem to be a very serious set of files to have out in the wild... (Which is part of the problem. No one has been able to find those images, otherwise, many would have tried using QPST already)
Amon Darthir said:
I no longer have my device, as I was able to wallop Google Support enough over the issue that they agreed to RMA the device, however, I'm curious how this would actually work.
The device only boots to EDL, so ADB isn't an option, neither is Fastboot. From what I've seen and understand, without a proper Firehose file, and an image from Qualcomm or Google themselves, there's basically no way to flash the device back to a working state (assuming it even can be).
Are there actual FULL Pixel images available, with bootloader and Android? (They sound to be packaged together). This would seem to be a very serious set of files to have out in the wild... (Which is part of the problem. No one has been able to find those images, otherwise, many would have tried using QPST already)
Click to expand...
Click to collapse
So let me explain.
From what I know you can download the firmware directly from Google from here.
For the firehose file, it's the one I send on 2 message. If you open Qualcomm QPST tool, and go to the download menu you will find a place to insert the phone image, though you can only put an image with an specific file system, the same as the files I shared. From what I saw on the web, you just need to flash that file.
If you use QFIL however, you will need and XML file as well.
I believe they are the firmware/Firehose files but I am not sure.
The IssueTracker updated today, with what appears to be an official response from Google:
"This issue occurred due to the natural lifecycle of a memory component. Memory components have a predefined lifecycle based on consumer use cases over time. The recommended solution is an out of warranty repair or replacement..."
Click to expand...
Click to collapse
So we now know that the issue is indeed a hardware fault, and that it is a fault in one of the memory components as suspected.
What's curious still is that these devices are encountering this issue, while much older devices continue to work. Wonder what the difference is.
Amon Darthir said:
The IssueTracker updated today, with what appears to be an official response from Google:
So we now know that the issue is indeed a hardware fault, and that it is a fault in one of the memory components as suspected.
What's curious still is that these devices are encountering this issue, while much older devices continue to work. Wonder what the difference is.
Click to expand...
Click to collapse
Hey!
That's a possible case, though I don't believe that for a few reasons:
1) Even though some components are consumable(like battery and SSD), RAM isn't one of them.
2) For a RAM to fail there is usually a cause, like working on extremely high frequencies, high temperatures and so on which obviously doesn't happen on a phone unless you leave it burning under the sun.
3) How many cases of faulty RAM modules did you see on the web, I didn't see any yet(at least not on phones)
So unless the user overheated its phone or drop it from an airplane XD, it seems to be a hard excuse for the problem.
I don't believe that there is a hardware failure, but I am not a phone engineer so I can't guarantee.
Anyway, if someone finds the cause please let me know
#mcl said:
Hey!
That's a possible case, though I don't believe that for a few reasons:
1) Even though some components are consumable(like battery and SSD), RAM isn't one of them.
2) For a RAM to fail there is usually a cause, like working on extremely high frequencies, high temperatures and so on which obviously doesn't happen on a phone unless you leave it burning under the sun.
3) How many cases of faulty RAM modules did you see on the web, I didn't see any yet(at least not on phones)
So unless the user overheated its phone or drop it from an airplane XD, it seems to be a hard excuse for the problem.
I don't believe that there is a hardware failure, but I am not a phone engineer so I can't guarantee.
Anyway, if someone finds the cause please let me know
Click to expand...
Click to collapse
Never said it was the RAM. It's likely the memory component that the bootloader is on, which is part of what has been speculated. I doubt my "memory component" the only thing they were referring to was RAM.
Amon Darthir said:
Never said it was the RAM. It's likely the memory component that the bootloader is on, which is part of what has been speculated. I doubt my "memory component" the only thing they were referring to was RAM.
Click to expand...
Click to collapse
The bootloader is on the SSD of the phone I think, and it doesn't fail as well, at least no so often...
#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
Sorry for bumping this old thread.
Like quite a few other reports I could find on the Internet, my Pixel 4 XL bricked itself overnight as well...Happy to come across your posts and interested in trying these files out.
Right now I can confirm that my phone is stuck in the EDL mode as I can see "QUALCOMM HS-USB QDLOADER 9008 COMx" in Device Manager when connected to a Windows computer, and I do see the phone in QPST Configuration, that says something like "QCP-XXX Sahara download".
However, unlike most QPST tutorials I found online (including the one you posted), the port status in QPST Configuration does not say "Enabled", but rather showing a half-way green progress bar all the time. I've tried to wait for about one hour just in case, and reinstalling the Qualcomm driver, restarting the computer etc. but nothing changed.
And if I just ignored that and go straight to flashing anyway, I couldn't get it to work with the MDN files you posted. QFIL would need a .xml file which is not included. Software Download reports an error message of "could not open the programmer file" (by this I was using the EU/.../pixel_free one).
Not sure what does it mean by "could not open" - is it the .mdn file is invalid, or it's just not the right file for this particular phone?
I suppose nobody has been able to use what @#mcl has posted back in 2021 to work? And the natural lifecycle of a memory component is only 3 years? That sucks.
Hi!
Yeah unfortunately there is close to nothing about this, probably because it's very low-level programming, and for security and economical reason Qualcomm won't share this kind of information. Only someone that work inside Qualcomm may have access to the needed files and documentation.
ObsidianTheRed said:
I wanted to confirm that removing com.google.android.apps.work.oobconfig as detailed in mcl's original post worked on a Verizon carrier-locked Pixel 5. Awesome!
Click to expand...
Click to collapse
bodayw said:
Sorry for bumping this old thread.
Like quite a few other reports I could find on the Internet, my Pixel 4 XL bricked itself overnight as well...Happy to come across your posts and interested in trying these files out.
Right now I can confirm that my phone is stuck in the EDL mode as I can see "QUALCOMM HS-USB QDLOADER 9008 COMx" in Device Manager when connected to a Windows computer, and I do see the phone in QPST Configuration, that says something like "QCP-XXX Sahara download".
However, unlike most QPST tutorials I found online (including the one you posted), the port status in QPST Configuration does not say "Enabled", but rather showing a half-way green progress bar all the time. I've tried to wait for about one hour just in case, and reinstalling the Qualcomm driver, restarting the computer etc. but nothing changed.
And if I just ignored that and go straight to flashing anyway, I couldn't get it to work with the MDN files you posted. QFIL would need a .xml file which is not included. Software Download reports an error message of "could not open the programmer file" (by this I was using the EU/.../pixel_free one).
Not sure what does it mean by "could not open" - is it the .mdn file is invalid, or it's just not the right file for this particular phone?
Click to expand...
Click to collapse
I still didn't gave up on any of the projects (the EDL thing and the unlock SIM & Booloader), but due to high complexity of those projects, the fact that I have a quite busy life which leaves me with very little time to bring live to these projects and that I am basically alone, means they will probably take some time.
Maybe try searching using different search engines, and try being very specific like "MBN file pixel 4".
Hope you find a solution to your problem!
Related
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"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"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.
Thanks
I shall keep going at it until it works or I find another solution.
PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.
korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?
korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.
korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.
korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help
Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck
Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??
Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.
is this solution applicable to non-intel memopad? (e.g. me172V)
playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
potemkinbuster said:
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
Click to expand...
Click to collapse
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
wulsic said:
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
Click to expand...
Click to collapse
I've tried this, but it takes forever and when it comes back with a response it only says (ERROR TOO MANY LINKS), which makes the use of fastboot commands useless
albatron34 said:
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
Click to expand...
Click to collapse
I wishi I could make it get into download mode xP
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
potemkinbuster said:
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
Click to expand...
Click to collapse
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
wulsic said:
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
Click to expand...
Click to collapse
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Godra said:
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
Click to expand...
Click to collapse
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
potemkinbuster said:
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Click to expand...
Click to collapse
so it partly like works, perhaps you can still get it to work but else you must do the hardbrick fix method from general. I can't say much other things how you could fix it if fastboot mode doesn't work recovery not then you must use that.
potemkinbuster said:
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
Click to expand...
Click to collapse
Yeah, its a bit tricky when doing it first time but its not that hard. I used this tutorial to open phone and short those capacitors. You just have to remove almost all conectors (but camera one) and remove everything to get to SoC.
I did try to shorten capacitors and removes all connectors but i suppose to shorten them when i put back connectors exept the battery , the probleme whene i reattach them i can no longer see the capacitors @@
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Godra said:
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Click to expand...
Click to collapse
that small metal piece is the volume boutton , and it seemd that they are not removable
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Godra said:
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Click to expand...
Click to collapse
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
kakashi_senpai said:
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
Click to expand...
Click to collapse
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Godra said:
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Click to expand...
Click to collapse
this is a pic from my phone can u please show where to put the wire please
{
"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"
}
kakashi_senpai said:
this is a pic from my phone can u please show where to put the wire please
Click to expand...
Click to collapse
Well first you need to remove the buttons plate as it's located underneath that. See the images if you don't know what I mean:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
The only video perhaps available I searched through the thread was this:
https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be
It isn't very clear with the unbricking situation but I unbricked my phone using the images too, Just try to read and see the images and you should be able to unbrick it only you need a thin wire kinda not too large. I couldn't find a smaller wire so it took me like 15 minutes to get it unbricked as I also had some fail attempts.
Yes sir thats my probleme , I tryd to remove the buttons plates but they are stuck with both side , in the video u gave , they are separated
---------- Post added at 10:59 PM ---------- Previous post was at 10:04 PM ----------
well i succeeded to remove button plate , and my device was read as bulk mode. and now i reattached battery and unplug usb connector, now i put back buttons ? and plug it again or what i do exactly ?
Hi, I was trying to update my LG G2 D800 to Lollipop using this guide:
http://webtrickz.com/how-to-update-lg-g2-to-official-lollipop-os/
However, after the device rebooted, it went to the LG logo screen, displayed this message in the top left corner, and went to an indefinite black screen.
boot certification error
secure booting error
cause: boot certification verify
Holding down the power button for about 15 seconds turns the device off, but sometimes it turns itself back on and does it again. Turning it off, then quickly holding volume down and power button, releasing on logo, then holding again brings it to a "Factory Data Reset" screen, however, doing a reset does nothing and puts me immediately back to the same problem.
Holding volume up and plugging it into my PC does the same thing, and when plugged in, windows recognizes about 20 "unformatted drives", and shows it as QHSUB_BULK in device manager, under other devices.
Before this, I was running stock 4.4.2, D80020y, rooted with towelroot. I had attempted to create a TWRP recovery, and it said it succeeded, however it was unable to boot to recovery.
I was going to try to fix it using this thread: http://forum.xda-developers.com/showthread.php?t=2582142
However, I am unable to find an img for D80020y.
I have access to a Win 8..1 desktop, and I can run whatever OS necessary in a VM.
Does anyone know where to find one? Or, can anyone provide me with one? Or, is there another way to fix this?
I'm just worried that my device is totally gone at this point, and considering I bought it used, I have no warranty, nor a phone to replace it, currently.
Thanks so much to anyone who can help me!
First off, why didn't you just do an OTA update to Lollipop (via settings/about phone) instead of trying to manually do it? It's a lot easier and you could of avoided all of this...
Anyways, I am not sure what exactly happened (maybe it was a bad flash or maybe you screwed up somewhere), but it looks like you've gotten yourself in a real mess.
Did you triple check that you followed the article step by step? Did other people state in the comments about any problems they faced when using the method?
I have tried that method you linked before, and I used Ubuntu, which is best for that method. However, it did not work for me. I remember going on and on with that and ultimately just flat out replaced my logic board when I had a bricked G2.
And I can totally relate to to the twenty unformatted drives, I have been in same exact situation with the endless windows popups when I plug in my phone, but I never really figured out the issue. I remember before I was stuck in fast boot mode, and after awhile I couldn't even get to fast boot.
Can you get into recovery? Is the phone still alive? If so, you can use this to get back to stock http://forum.xda-developers.com/showthread.php?t=2432476
Hope this helps a bit, I have never been in your situation but if you want a real, simple solution to this: I would purchase and replace your logic board (phone's motherboard). It is a definite fix. If you are not comfortable with that, then I would advise to go ahead and do some research about this. Unfortunately, I have no idea where you can get that img (I do not have a D800, but rather a VS980), but I am sure with some Google searches you can find it.
I have bricked a couple phones in the past, and we all learn from our mistakes!
Best of luck!
fischer12345 said:
*snip*
Click to expand...
Click to collapse
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Jtpetch said:
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Click to expand...
Click to collapse
Gotcha. I haven't ran into the issue you have been describing at all before, but I just wanted to try to understand this situation a little better, I wish I could tell you what exactly happened.
As far as your problem, here's what I would do. The phone is still alive correct? Contact LG and send that bad boy in. Tell them you used it for a couple of months and all of a sudden it does not work anymore. I think that would be your best bet. However, do not tell them you modified it or whatever you tried to do with it.
Be aware if you do send it in to LG, make sure you have not tried to open up the phone and screw around with it internally. They will not fix it if that is the case. Also, it can be quite pricey depending on your current condition.
Oh, and LG will not provide you with those files, they are there to help you with any kind of phone issue, but not these kinds of issues.
This my friend is the best advice I can give you! Again, another option would be replacing the logic board, but that is ONLY a last resort.
BTW, you didn't hard brick it so that's a plus
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
{
"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"
}
Jtpetch said:
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
Click to expand...
Click to collapse
can you enter download mode? pressisng VOL UP and then plug your phone and keep button press. does it goes to usb icon with curved arrows?
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Jtpetch said:
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Click to expand...
Click to collapse
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
raptorddd said:
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
Click to expand...
Click to collapse
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
do the QHUSB_BULK Fix when u try it (its in 4)
anyway i got my g2 in a much heavier brick,
i have a third party lab that can possibly fix my g2...
its not that expensive....
so I just need to hope they can fix it
Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
raptorddd said:
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
Click to expand...
Click to collapse
Yes, I am sure. I just tried it again, though, to confirm. Held volume up, plugged in USB, and it went to the LG logo screen, showed the same error text in the top left, and went to a black screen.
I am downloading the SRKtool right now, and will try as soon as i have it.
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Click to expand...
Click to collapse
am not sure but there isnta kdz for lollipop right? you may need to go to KK KDZ
ooo you have d800 same as me. you need to download this and use the kitkat
Download Installer - KitKat 4.4.2 D80020c
http://forum.xda-developers.com/showthread.php?t=2663369 do that and once you in KITKAT ill tell you
if you need helps just ask
Ah, ok, will do. And thanks so much for all the help!
Jtpetch said:
Ah, ok, will do. And thanks so much for all the help!
Click to expand...
Click to collapse
no problem just hit thanks it i helped, once you in KK ill tell you how to go from there.
Wow, it flashed and everything without a hitch. I'm in KK now, and everything seems all good. So how would I go about upgrading to lollipop?
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Jtpetch said:
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Click to expand...
Click to collapse
am glad you liked it, just pass the knowledge when someone is in the same shoes as you were..
i have the same problem as you please help
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
please guide me through what you did to get back to download
Click to expand...
Click to collapse
UPDATE: The issue was resolved and here is the [SOLUTION]first of all lets start with the problem, it doesn't matter if it's just hard reset loop or update loop problem, I actually did both, here's a thing this main issue comes with updates but somehow this time recovery mode was completely destroyed, so there is no escape you can only access fastboot which is a good thing in a way, follow the steps to unbrick your phone.
-if you can access recovery mode just download modified miflashpro and flash downloaded rom using it.
REQUIRMENTS: PC,USB CABLE,INTERNET CONNECTION.
SOLUTION:1. Install ADB on your PC with all the necessary drivers for your phone
2. Turn off your phone completely, press and hold volume down and power button together to go into fastboot mode
3. once you are in fastboot mode connect usb to phone and open cmd from adb directory and type in: fastboot devices (if device serial number is shown in fastboot mode everything is good so far... if not go to DEVICE MANAGER in your pc and check if driver is installed properly if anything ADB drivers and ANDROID USB drivers will come handy to install them manually)
4. now type in: fastboot continue
{
"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"
}
5. your device will boot into system if it fails try going into fastboot mode and going with fastboot continue command again try until it boot ups into safe mode
6. eventually it will boot into safe mode system without your files being touched because nor update nor hard reset was completed fully, phone will be in airplane mode.
7. DO NOT TURN ON WIFI OR MOBILE DATA it will crash your phone, if your phone storage is full remove some stuff plus the apps.
8. Turn on USB DEBUGGING,OEM UNLOCK MODE. open file transfers and download apk of MIUI updater from pc to your phone ( LATEST VERSION ) and install it.
9. now DEACTIVATE AIRPLANE MODE and turn on WIFI FROM SETTINGS
10. once you got internet connection wait a little bit for all of the notifications and stuff to pop up be careful, once it's all good go to settings about phone and system update and CHECK FOR UPDATES
11. let your phone download the update it should be around 1.7GB depends honestly let it decrypt and once you are ready click on INSTALL NOW.
12. it will take time to install and reboot will happen many time you might think that it gets stuck at 90.49% but let it finish be patient it happens it just needs time, once everything is done you are good to go
WELCOME TO MIUI 12
SIDE NOTE:
I - MAKE SURE YOUR PHONE IS CHARGED
II - I DID TRY EDL TEST POINTS BUT YOU DO NOT NEED TO OPEN UP YOUR PHONE NOR TO DO IT.
III - BE PATIENT
F
Unless you're willing to do a test point boot, take it to a Xiaomi service center, take a receipt with you or some proof of purchase.
You can try buying an EDL cable and testing your luck, I highly doubt tho since Xiaomi locks it's EDL mode.
got good news I managed to actually get in the system
using fastboot continue command it lags as hell but usb debugging is on
so from the looks of it recovery is gone
I am in phone adb devices are visible
anything that you might suggest ?
it took me three times to do this but it finally managed to do something
I think it's safe mode and this is why it's not crashing yet
XDHx86 said:
F
Unless you're willing to do a test point boot, take it to a Xiaomi service center, take a receipt with you or some proof of purchase.
You can try buying an EDL cable and testing your luck, I highly doubt tho since Xiaomi locks it's EDL mode.
Click to expand...
Click to collapse
anyways phone is on and going well charging but is in airplane mode trying to flash rom using miflash but not working... recovery is most likely gone... any ideas guys what to do?
Update:turning wifi makes it crash
UPDATE II: WHATEVER HAPPENS DO NOT TURN ON WIFI IT WILL CRASH AND KEEP ON CRASHING UNTIL YOU GET LUCKY AND TURN IT OFF YOURSELF
UPDATE THREE: I NEED A WAY TO FLASH RECOVERY WITHOUT FASTBOOT AND BOOTLOADER IS LOCKED
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
XDHx86 said:
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
Click to expand...
Click to collapse
I mean device is locked... there is no way to unlock it with that MI account BS
is there a way to flash twrp?
XDHx86 said:
You said your device is locked? If it's unlocked try flashing TWRP, and flashing a different ROM so this doesn't happen again.
Careful of rollback index when trying to flash a MIUI ROM so it doesn't cause a hardbrick.
Click to expand...
Click to collapse
If i somehow manage to get into recovery even if I will be able to install it I will flash rom and it's over
You can't force flash TWRP. You'll have to wait those days with MI Unlock, that's the only way.
There is this thread about an unofficial method of unlocking, I didn't bother looking tbh since I'm very sure you can't unlock it unofficially, but if you do find something then do it on your own risk.
good news managed to get wifi to work now trying to download update from the phone it's slowly going lets see if it installs safely this time boyz will update
gotta admit was a rough one
NikoWulf said:
good news managed to get wifi to work now trying to download update from the phone it's slowly going lets see if it installs safely this time boyz will update
Click to expand...
Click to collapse
NikoWulf said:
View attachment 5248941 gotta admit was a rough one
Click to expand...
Click to collapse
Well that's good, I've never heard a Xiaomi update bricking a phone except MI A3 recent Android 11 update. So most likely it will work fine. Make sure you have enough charge in the battery.
Gotta ask, how did you fix it? Did you do a test point?
well it's not over yet my dude,lets see how it's going to update this one hopefully everything will work fine
well I did had to use test points for nothing lmao, plus tweaking with right drivers from device manager and stuff...
well lets hope it works out... it was a nightmare bud
XDHx86 said:
Well that's good, I've never heard a Xiaomi update bricking a phone except MI A3 recent Android 11 update. So most likely it will work fine. Make sure you have enough charge in the battery.
Gotta ask, how did you fix it? Did you do a test point?
Click to expand...
Click to collapse
well I can't leave it like that until the update cause I can see it's buggy plus I removed SIM
so airplane mode was deactivated
activated Wifi it works pretty decent rn laggy a bit but at least I am able to download so lets see where will this update take me
been stuck here for a while now
BOYS phone turned on without a problem ladies and gentleman
PROBLEM IS SOLVED
NikoWulf said:
well I can't leave it like that until the update cause I can see it's buggy plus I removed SIM
so airplane mode was deactivated
activated Wifi it works pretty decent rn laggy a bit but at least I am able to download so lets see where will this update take me
Click to expand...
Click to collapse
Well I know I'd want a way out of this fast, so if you're still looking for a way to flash another ROM I think Hydra tool can unlock bootloader through EDL mode.
NikoWulf said:
BOYS phone turned on without a problem ladies and gentleman
PROBLEM IS SOLVED
Click to expand...
Click to collapse
Although if everything is working fine then I advice against it.
XDHx86 said:
Well I know I'd want a way out of this fast, so if you're still looking for a way to flash another ROM I think Hydra tool can unlock bootloader through EDL mode.
Although if everything is working fine then I advice against it.
Click to expand...
Click to collapse
Thanks might try it out if this one gets funky again but so far everything is going smooth
Hi,
what to do Xiaomi phone (Snapdragon) does not show anything, the LED is on (when it is discharged and then it does not turn on) and "Qualcomm HS-USB Diagnostics 900E" is displayed in the device manager, the phone was discharged to 0% and the bootloader was unlocked. SparkOS is installed and I don't know what now.
SEBILOWSKI said:
Hi,
what to do Xiaomi phone (Snapdragon) does not show anything, the LED is on (when it is discharged and then it does not turn on) and "Qualcomm HS-USB Diagnostics 900E" is displayed in the device manager, the phone was discharged to 0% and the bootloader was unlocked. SparkOS is installed and I don't know what now.
Click to expand...
Click to collapse
Device auto sent to Qualcomm HS-USB Diagnostics 900E mode is not a good signal, what do you think you did, so device may turn bricked?
If you think, nothing bad was done, try charging the battery, with a 20% it's enough, and try to reboot it, by pressing the three buttons at the same time, for about 8 or 9 seconds,
I don't think this may be the case, anyway, some custom ROMs don't support the device to stay on at a minimum battery level.
SubwayChamp said:
Device auto sent to Qualcomm HS-USB Diagnostics 900E mode is not a good signal, what do you think you did, so device may turn bricked?
If you think, nothing bad was done, try charging the battery, with a 20% it's enough, and try to reboot it, by pressing the three buttons at the same time, for about 8 or 9 seconds,
I don't think this may be the case, anyway, some custom ROMs don't support the device to stay on at a minimum battery level.
Click to expand...
Click to collapse
I can't see anything on the screen at all. A million percent I installed the correct ROM because I've installed it before and never had problems. I will try to do as you wrote and let you know.
SEBILOWSKI said:
I can't see anything on the screen at all. A million percent I installed the correct ROM because I've installed it before and never had problems. I will try to do as you wrote and let you know.
Click to expand...
Click to collapse
If you press the three buttons for about 9 seconds, and nothing, or your device got again to that mode, then it turned out bricked, maybe some bad file in the zip, double check if the md5sum gets something wrong.
If this is the case, you have to start the EDL mode recovering method.
After those 9 seconds, nothing happens. The diode is lit as if it was still discharged and it is not because I had it in electricity for 3 hours. I checked and md5sum is correct. So what about this EDL now? How to do this method?
SEBILOWSKI said:
After those 9 seconds, nothing happens. The diode is lit as if it was still discharged and it is not because I had it in electricity for 3 hours. I checked and md5sum is correct. So what about this EDL now? How to do this method?
Click to expand...
Click to collapse
SubwayChamp said:
If you press the three buttons for about 9 seconds, and nothing, or your device got again to that mode, then it turned out bricked, maybe some bad file in the zip, double check if the md5sum gets something wrong.
If this is the case, you have to start the EDL mode recovering method.
Click to expand...
Click to collapse
.
SEBILOWSKI said:
.
Click to expand...
Click to collapse
Now that your device is booting to Qualcomm HS-USB Diagnostics 900E, then you have to update the drivers to Qualcomm QDloader 9008, this is one of the guides out there about update drivers from https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
Once you get it, the process is to flash the device as if it was in fastboot mode, using MiFlash tool. And just ignore, the threads claiming to open the motherboard or short-circuiting pins (test point), because your device is effectively booting to EDL mode, so not required.
In that process, if you are lucky and the damage was not serious, then you will be able to do it, in few seconds, but if somewhat the motherboard get "damaged" then it would require more effort to get it work, specially, a technician may be required.
SubwayChamp said:
Now that your device is booting to Qualcomm HS-USB Diagnostics 900E, then you have to update the drivers to Qualcomm QDloader 9008, this is one of the guides out there about update drivers from https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
Once you get it, the process is to flash the device as if it was in fastboot mode, using MiFlash tool. And just ignore, the threads claiming to open the motherboard or short-circuiting pins (test point), because your device is effectively booting to EDL mode, so not required.
In that process, if you are lucky and the damage was not serious, then you will be able to do it, in few seconds, but if somewhat the motherboard get "damaged" then it would require more effort to get it work, specially, a technician may be required.
Click to expand...
Click to collapse
I did everything as in this tutorial but still device manager detects this earlier name. I opened MiFlash but it does not detect the phone.
SEBILOWSKI said:
I did everything as in this tutorial but still device manager detects this earlier name. I opened MiFlash but it does not detect the phone.
Click to expand...
Click to collapse
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
{
"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"
}
If this box is checked, only these items are listed...
And when you uncheck this box, you'll see other options
So, don't worry, you don't need to find more drivers, nor do anything more, JUST update correctly the drivers, in this specific item where is listed under a Port COM.
SubwayChamp said:
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
View attachment 5825601
View attachment 5825603
View attachment 5825605
If this box is checked, only these items are listed...
View attachment 5825607
And when you uncheck this box, you'll see other options
View attachment 5825609
View attachment 5825611
View attachment 5825613
View attachment 5825615
View attachment 5825617
Więc nie martw się, nie musisz znajdować więcej sterowników, ani robić nic więcej, PO PROSTU zaktualizuj poprawnie sterowniki, w tym konkretnym elemencie, gdzie jest wymieniony pod Port COM.
Click to expand...
Click to collapse
SubwayChamp said:
I just pointed out one of the lot of guides that exist around the theme, but the guide seems to be not complete.
Qualcomm USB drivers (tab at your right side) contains all the modes listed under device manager Qualcomm tab (at your left) once you tap on it, the important part is unchecking where it says, "Show only compatible drivers" or something similar.
I'll show you, from my PC, the part that the guide lacks of. Sorry, it's in Spanish, but I guess it's self-explanatory.
View attachment 5825601
View attachment 5825603
View attachment 5825605
If this box is checked, only these items are listed...
View attachment 5825607
And when you uncheck this box, you'll see other options
View attachment 5825609
View attachment 5825611
View attachment 5825613
View attachment 5825615
View attachment 5825617
So, don't worry, you don't need to find more drivers, nor do anything more, JUST update correctly the drivers, in this specific item where is listed under a Port COM.
Click to expand...
Click to collapse
However, I had to manually enter the EDL, but I get these problems:
1. Cannot accept hello packet
2. Write time out, maybe device was disconnected
3. Only nop and sig tag can be recived before authentication
SEBILOWSKI said:
However, I had to manually enter the EDL, but I get these problems:
1. Cannot accept hello packet
2. Write time out, maybe device was disconnected
3. Only nop and sig tag can be recived before authentication
Click to expand...
Click to collapse
A device bricked it's easy to send to EDL mode, anyway, the drivers need to be updated, as seems you now got it.
MiFlash tool needs an authorized account, to start the flashing, so a lot of errors you may encounter in the process, specially the 3rd it's directly related to that. BUT, keep in mind, that also the motherboard, depending on what exactly you did flash may get corrupted, so a replacement may be required.
SubwayChamp said:
A device bricked it's easy to send to EDL mode, anyway, the drivers need to be updated, as seems you now got it.
MiFlash tool needs an authorized account, to start the flashing, so a lot of errors you may encounter in the process, specially the 3rd it's directly related to that. BUT, keep in mind, that also the motherboard, depending on what exactly you did flash may get corrupted, so a replacement may be required.
Click to expand...
Click to collapse
I still don't know how to solve this, can I contact you through something other than XDA and help me?
SEBILOWSKI said:
I still don't know how to solve this, can I contact you through something other than XDA and help me?
Click to expand...
Click to collapse
What is actually the status of your device?, you just keep getting errors from Mi Flash tool?. Upload some screenshot.
SubwayChamp said:
What is actually the status of your device?, you just keep getting errors from Mi Flash tool?. Upload some screenshot.
Click to expand...
Click to collapse
I keep getting it, don't know what to do with it anymore
SEBILOWSKI said:
View attachment 5846575
I keep getting it, don't know what to do with it anymore
Click to expand...
Click to collapse
I´m pretty sure, unfortunately, that the motherboard got damaged, and needs a replacement.
I had the exact situation, with a device in the past, no matter what I did, I couldn´t get it to work, but then, replaced the motherboard, and need to flash something through EDL mode, at the first attempt it worked fine,
There are another repairing method. that is anyway, up to the service center, the motherboard can be repaired, but, most of times, they consider, that the effort don´t worth it, and they ask just for a replacement, the procedure is called reballing, but again, like most of times, they don´t want to do it, not even, will mention that.