Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
{
"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"
}
pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
TheGhost1951 said:
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
Click to expand...
Click to collapse
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
And it is pretty interesting.. As far as i know EDL connection only alive for 5-10 sec, but currently MsM tool shows Connected until my phone was plugged in (even after refreshing it)
pmppm said:
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
Click to expand...
Click to collapse
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
TheSayaMan said:
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
Click to expand...
Click to collapse
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
pmppm said:
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
Click to expand...
Click to collapse
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
TheGhost1951 said:
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
Click to expand...
Click to collapse
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
TheSayaMan said:
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
Click to expand...
Click to collapse
Would this not work?
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
V0latyle said:
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
Click to expand...
Click to collapse
It is called the MSM Download Tool. And it is device specific and ready available.
TheGhost1951 said:
It is called the MSM Download Tool. And it is device specific and ready available.
Click to expand...
Click to collapse
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Odin is for flashing Samsung devices. Samsung and now OnePlus are the only two devices I have worked with.
pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
India device or global devices
And tip
Reboot to edl
Power off the phone
And press and hold pressed the voll up and voll down
And putt in the usb cable and hold pressed the voll up and voll down
And try msm tool
V0latyle said:
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Click to expand...
Click to collapse
Not only specific to OnePlus but also specific to OOS versions.
Might try to uninstall Qualcomm drivers, make sure PC driver signing is disabled. Reboot PC, then re-install latest Qualcomm drivers, re-boot PC and try again with MSM tool. The windows sound when plugging in before is the sound of a device plugged in but couldn't recognize it and threw it out of device manager. That was the reason for the TWO sounds you heard. Also try holding down on vol + - and pressing power and holding it down to try to boot into fastboot mode. If it does, flash boot boot TWRP.img and then boot into edl from there with phone connected to PC and MSM tool in start mode ready to flash as soon as device is connected.
Related
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
You tried xdadevelopers search box ?
RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Not yet actually . Can't find it under TOOLS . Is this available yet ?
RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Fredelbert said:
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Click to expand...
Click to collapse
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
RuedasLocas said:
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
Click to expand...
Click to collapse
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
OK, it will take some time downloading and trying it. I'll be back when having results
THANX
ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
{
"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"
}
Fredelbert said:
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
Click to expand...
Click to collapse
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Fredelbert said:
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Click to expand...
Click to collapse
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
ThePiGuy said:
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Click to expand...
Click to collapse
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Fredelbert said:
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Click to expand...
Click to collapse
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
Look at the firmware(laf): v20g
That's his bootloader stack
He flashed freedom ROM which has v29a as base that's why system shows v29a.
Sent from my LG-H815 using XDA Labs
ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
That has no effect, same behaviour as before
RuedasLocas said:
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
Click to expand...
Click to collapse
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Fredelbert said:
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Click to expand...
Click to collapse
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
RuedasLocas said:
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
Click to expand...
Click to collapse
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Fredelbert said:
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Click to expand...
Click to collapse
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
RuedasLocas said:
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
Click to expand...
Click to collapse
OK, then I will search for the mentioned Kdz file and download it. I will be able to continue tomorrow. Thanks to everybody so far. I will post the result as fast as I can
Hi,
soo I wanted to go from a Android 6 RR ROM to the newest Android 9 one.
Flashed new TWRP, and then the ROM using TWRP. Didn't boot, I looked it up and found that I needed to flash a 2.5 or 3.5 ZUI first.
I tried flashing a 3.5 ROM for about 5 hours using QFIL, with various errors (pretty much tried everything).
I was finally able to flash it using a 2016 MiFlash version (it reported "success").
I then plugged out the phone and tried rebooting it. Now, whatever I do (even just plugging in the cable), it vibrates once, and then over and over again every 12 seconds or so. No LED flashes.
I tried every possible key combination to get it back into EDL, unsuccessfully (while having to disconnect the battery lead each time because I can't get it to turn off).
I would greatly appreciate any help, as I'm now completely lost here. I've never seen a phone that is able to be bricked that hard before.
Kind regards
I bricked my Z2 Plus on two separate occasions whilst trying to flash ROMs. The first time I was able to get into EDL mode using the hardware buttons on the device, but it was incredibly difficult and relied on precise timing because the device was stuck in a reboot loop to the bootloader screen, hence it kept switching off whilst trying to do the button combination.
The second time I bricked this phone, I was unable to get into EDL mode using the hardware buttons. So I had to resort to making a 'deep flash' cable using the USB Type-C cable that came with the device. You have to strip the coating off the cable and then stick a pin through two of the wires to force the phone into EDL mode.
There's a guide here that I used to help:
https://zukfans.eu/community/thread...-from-hard-brick-state-9008-mode-easily.3504/
Alternatively you can purchase a proper 'deep flash' EDL cable from somewhere like eBay or AliExpress. It's just a normal USB cable with a button on it that you can press to get into EDL mode. Hope this helps.
Thanks. I managed to get the phone into EDL mode by making the cable suggested, but I still find myself unable to flash anything properly. The port shows correctly as Qualcomm HS-USB QDLoader 9008 (using Qualcomm driver 2.1.22).
I now tried flashing a 2.5 ROM and the 3.5 one again using MiFlash (version 2016.03.30.0) and it fails with various errors (Reached EOF while receiving hello packet etc.).
Trying to flash using QFIL (version 2.0.1.1, installed using QPST) gets me this error:
Code:
14:43:15: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
14:43:15: ERROR: function: sahara_main:924 Sahara protocol error
14:43:15: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
I already tried many of the steps suggested to fix that (like shortening the path etc.), but even before bricking I could only get past the Sahara Fail error a few times.
Thanks a lot
I tried again using MiFlash and it got to flashing but crashed in between with
Code:
Fatal Error(0x8000ffff: Send configure command)
d0ntflash said:
I tried again using MiFlash and it got to flashing but crashed in between with
Click to expand...
Click to collapse
Install latest qfil ,load rom in it
Click on download as soon as phone boots to edl
JV Spartacus said:
Install latest qfil ,load rom in it
Click on download as soon as phone boots to edl
Click to expand...
Click to collapse
I installed it from QPST.2.7.460.zip, is that the latest version?
d0ntflash said:
I installed it from QPST.2.7.460.zip, is that the latest version?
Click to expand...
Click to collapse
I think QPST 2.7.474 is the latest. I would also recommended you use QFIL 2.0.1.9 instead of MiFlash. As JV mentioned you must start the flash process quickly after the phone enters EDL mode. If there's a delay then that can cause errors to appear.
Ok, this is the furthest I got so far:
https://pastebin.com/EQgXDwEe
And the last (relevant) lines from the mentioned logfile:
https://pastebin.com/3ZmMiBZA
Do I have a damaged image file? I downloaded it from this thread (This file: http://cdn.zui.lenovomm.com/downloa...SER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip)
Thanks
Got a little further with the 2.5 Image, but not quite there yet:
https://pastebin.com/c0xGg2qy
Is it a connection problem?
I finally managed to flash 2.5 using QFIL and get the phone to boot again. Thank you very much!
This is how you make a proper "deep flash" cable guys
{
"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"
}
Cheers!
d0ntflash said:
This is how you make a proper "deep flash" cable guys
Cheers!
Click to expand...
Click to collapse
That's pretty good. You even managed to fit a button!
Since 3 days I could not be able to boot my zuk z2 plus, my phone is completely bricked now. Every time I press the power button of the phone it gives a small vibration and nothing cames out in the screen. It starts when I was in aex 5.8 rom and someone in xda provided a zui 2.5 rom ( twrp). I tried to flash it and it fails. I wipe the dalvik , cache and accidentally pressed reboot system and that thing is started. When I try to flash stock rom via qfil it always show as 900E port and when I press the download button it says, "fail to switch to edl" . Please help me . I need my phone back as soon as possible.
Rit2005 said:
Since 3 days I could not be able to boot my zuk z2 plus, my phone is completely bricked now. Every time I press the power button of the phone it gives a small vibration and nothing cames out in the screen. It starts when I was in aex 5.8 rom and someone in xda provided a zui 2.5 rom ( twrp). I tried to flash it and it fails. I wipe the dalvik , cache and accidentally pressed reboot system and that thing is started. When I try to flash stock rom via qfil it always show as 900E port and when I press the download button it says, "fail to switch to edl" . Please help me . I need my phone back as soon as possible.
Click to expand...
Click to collapse
Hallo,
i am in the same circle. Cable with button = created, backcover of tablet = removed, in device manager showing only iagnostic 900E (never see 9008 or something else).
Rescue and Smart Assistant cannot switch tablet to EDL, cannot rescue, cannot flash stock...
2Rit2005: your tablet is ok right now?
2ALL: can someone help me, please?
Krabat
krabat said:
Hallo,
i am in the same circle. Cable with button = created, backcover of tablet = removed, in device manager showing only iagnostic 900E (never see 9008 or something else).
Rescue and Smart Assistant cannot switch tablet to EDL, cannot rescue, cannot flash stock...
2Rit2005: your tablet is ok right now?
2ALL: can someone help me, please?
Krabat
Click to expand...
Click to collapse
I am having the same EDL problem on my ZUK Z2 Pro. Always 900E.
Screen is out. Buttons method doesn't work (holding Volume+ button for 15sec, pressing Power button for 0,5sec and pressing and holding it and finally plugging in the cable into USB port).
I have made the deep flash cable (I connect black and blue wires as I am left with pink and white), but I get notifications from windows 10 that it does not recognize the device when I have the wires connected ( I assume it is ok).
When I disconnect the wires I don't get 9008 in Device Manager ports.
Need help with that pretty please whoever can
Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
{
"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"
}
Then I faced a similar problem described in this topic https://forum.xda-developers.com/re...-3-pro-boot-recovery-destroyed-t3938481/page3
When you turn on the phone an error pops up for 20 seconds and then phone reboots and everything goes in a circle.
If you press the power button once, the reboot process stops and the phone turns off.
I tried to enter fastboot mode by pressing the power + volume button -
But I didn't succeed.
Can you tell me what I'm doing wrong ?
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
kkffiirr said:
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
Click to expand...
Click to collapse
Thanks for the answer, but unfortunately due to this error fastboot does not load.
If you can tell me how I can flash the phone I will be very grateful.
I would not like to contact an unofficial service...
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
kkffiirr said:
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
Click to expand...
Click to collapse
Before lock, I installed TWRP, but idk if it's still there.
UMF cable will help me ?
Me i too i got same your problem i bricked my realme x2 i still didnt find the solution to flash it again
Maybe contact service center
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medusa Box; they seem to have underground connections with manufactors, they may provide a solution too.
EDIT. Thanks to the clarification from @T1MOXA, you can enter EDL mode by holding VolUp and VolDown and plugging the switched off phone to a computer.
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
yakovpol said:
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medisa Box; they seem to have underground connections with manufactors, they may provide a solution too.
Click to expand...
Click to collapse
I've tried this option before, but it led me to the same error screen.
I turned off the phone with a single press of the power button, then pressed all the buttons at the same time.
razu031 said:
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
Click to expand...
Click to collapse
I just got the same error.
When you connect the cable, the phone boots with the same error.
narshi shukla said:
Maybe contact service center
Click to expand...
Click to collapse
Unofficial ?
They too bad in my country.
They can easily make it worse.
I can buy a UMF cable, but whether it will help me I do not know.
What do you think ?
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
T1MOXA said:
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
Click to expand...
Click to collapse
Most phones will be able to flash in this mode using qfil tool,
But first you need to find necessary firmware, idk if stock rom downloaded from official site will work or not, maybe fastboot one will work.
This mode is called emergency download mode (edl).
But pls do a lil research as its a newly launched device and you can easily mess it up.
BTW exact same error(boot recovery destroyed) is common error on realme Phones and it can be fixed by flashing vbmeta.img using fastboot.
See attached image for reference only
The 1kb vbmeta is modified to bypass boot verification.
Idk if such vbmeta is available for x2.
If not then flashing stock vbmeta might work.
T1MOXA said:
Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
Click to expand...
Click to collapse
I have the same problem. On 4pda there is a firmware for MsmDownload Tool and the tool itself, but it requires a username and password. Are there alternative options to restore your phone?
Problem: The current image have been destroyed and can not boot
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Iamsanthoshravi said:
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Click to expand...
Click to collapse
Look friend i had the same problem and i fix it u have to download the firmware RMX1991 not ozp file then u have to buy the password of the firmware there are sone website they ask you to install teamviewer because thet gonna flash your phone online ok friend i did as i mentioned and i fixed so there is no other way to fix it i cant put the link of firmwares because last time xda warned me
I got same
Hey bro can you fix your phone?
Today I experience same.
What can I do now?
Hello guys
Today I'm going to tell you about how to bring your phone back to life when it is bricked and also you don't have access to fastboot.
few days ago when I wanted to turn back to Xiaomi EU weekly ROM from HOS, the fastboot script which is provided by Xiaomi EU team in order to flash the ROM gave me to many errors when it was trying to flash "super" partition and mistakenly I had rebooted my phone and then I realized the the phone is dead, it didn't show any sign of life (I mean no vibration, no fastboot and no screen light, literary nothing at all).
After some research I found out that Qualcomm powered devices have something called EDL which is stand for (Emergency Download mode) and it is there to flash fastboot ROMs when you don't have access to fastboot (as matter of fact EDL mode is one level lower than fastboot and let you to access the phone when it is dead and also it cannot be erased with fastboot).
Important: with this tutorial you can fix your phone by yourself and also there will be no need to pay anyone with authorized xiaomi account to connect to your personal computer and do the flash for you.
Lets head to tutorial:
Requirements:
1- A windows system
2- EDL drivers which can be found here
3- Original USB cable
4- Xiaomi pro tool which can be found here <Moderator Edit>: warning, comes up as Trojan:Script/Wacatac.B!ml in Windows Defender.
5- Fastboot ROM for your phone which can be found here
method:
1- first you need to boot your phone into EDL mode (you can do this by holding volume up button and connect your phone with its USB cable and check "device manager" on windows to check if your PC recognized your phone or not. you should see "Qualcomm HS-USB QDLoader 9008" under "ports" section (look at below picture)
{
"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 it didn't showed up follow this tutorial to install drivers
2- then open the Xiaomi pro tool,register on it then change the "select model" to your phone model (in this case POCO F3(Alioth)) and next change port to EDL booted device (should be like this: Qualcomm HS-USB QDLoader 9008)
3- <Moderator Edit>: not allowed
4- go to "xiaomi firmware flasher" page on xiaomi pro tool app and locate the downloaded ROM (you should locate "image" folder (downloaded ROM/images)) after that you will see that it loaded files correctly.
5- Disconnect your phone and hold power button for 15 second then press and hold volume up button and connect your phone with its USB cable to boot to EDL mode again and check thee "ports" on the tool app again (it should be same as step 2)
6- Click on flash device which is on the bottom right of the xiaomi pro tool app then it will ask for using your credits in order to flash device that you should click on "yes" button and after that you will see that flash processing is going on.
7- The tool will reboot your phone automatically but if you find your phone completely dead after the flashing process(not responding to anything and not going to EDL mode again (which was my case)) just don't panic, your phone maybe out of charge so just connect your phone to a charger and wait, after some minutes you will see the battery icon on your device.
8- hooray, you made it. you can enjoy your phone now
This is sweet, how much are the credits?
11214 said:
This is sweet, how much are the credits?
Click to expand...
Click to collapse
It depends on your country but it is about 1 US dollar per credit
raminta said:
It depends on your country but it is about 1 US dollar per credit
Click to expand...
Click to collapse
That's great, much better than the €25 I had to pay.
Thanks for the guide.
raminta said:
Hello guys
Today I'm going to tell you about how to bring your phone back to life when it is bricked and also you don't have access to fastboot.
few days ago when I wanted to turn back to Xiaomi EU weekly ROM from HOS, the fastboot script which is provided by Xiaomi EU team in order to flash the ROM gave me to many errors when it was trying to flash "super" partition and mistakenly I had rebooted my phone and then I realized the the phone is dead, it didn't show any sign of life (I mean no vibration, no fastboot and no screen light, literary nothing at all).
After some research I found out that Qualcomm powered devices have something called EDL which is stand for (Emergency Download mode) and it is there to flash fastboot ROMs when you don't have access to fastboot (as matter of fact EDL mode is one level lower than fastboot and let you to access the phone when it is dead and also it cannot be erased with fastboot).
Important: with this tutorial you can fix your phone by yourself and also there will be no need to pay anyone with authorized xiaomi account to connect to your personal computer and do the flash for you.
Lets head to tutorial:
Requirements:
1- A windows system
2- EDL drivers which can be found here
3- Original USB cable
4- Xiaomi pro tool which can be found here
5- Fastboot ROM for your phone which can be found here
method:
1- first you need to boot your phone into EDL mode (you can do this by holding volume up button and connect your phone with its USB cable and check "device manager" on windows to check if your PC recognized your phone or not. you should see "Qualcomm HS-USB QDLoader 9008" under "ports" section (look at below picture)
View attachment 5547309
If it didn't showed up follow this tutorial to install drivers
2- then open the Xiaomi pro tool,register on it then change the "select model" to your phone model (in this case POCO F3(Alioth)) and next change port to EDL booted device (should be like this: Qualcomm HS-USB QDLoader 9008)
View attachment 5547333
3- You need to buy at least 5 credits in order to flash ROM on your device you can buy it on the internet just google "credits for xiaomi pro tool" (Iranian users can use this site to buy credits)
4- go to "xiaomi firmware flasher" page on xiaomi pro tool app and locate the downloaded ROM (you should locate "image" folder (downloaded ROM/images)) after that you will see that it loaded files correctly.
View attachment 5547349
5- Disconnect your phone and hold power button for 15 second then press and hold volume up button and connect your phone with its USB cable to boot to EDL mode again and check thee "ports" on the tool app again (it should be same as step 2)
6- Click on flash device which is on the bottom right of the xiaomi pro tool app then it will ask for using your credits in order to flash device that you should click on "yes" button and after that you will see that flash processing is going on.
7- The tool will reboot your phone automatically but if you find your phone completely dead after the flashing process(not responding to anything and not going to EDL mode again (which was my case)) just don't panic, your phone maybe out of charge so just connect your phone to a charger and wait, after some minutes you will see the battery icon on your device.
8- hooray, you made it. you can enjoy your phone now
Click to expand...
Click to collapse
that's absolutely i done but for those people who don't have access to buy credit can search patched hose but till now no one has patched for our device poco f3. for patching it requires reverse engineering skill which i don't have.
why are the credits needed? this program is going to be likely used by desperate users that destroyed the phone and they even have to pay? i get the developers need money but its just bad...
pedrosantosobral said:
why are the credits needed? this program is going to be likely used by desperate users that destroyed the phone and they even have to pay? i get the developers need money but its just bad...
Click to expand...
Click to collapse
The only other option is paying €25 to a random person on the net to tunnel into your PC and do the job for you.
Nice
It's difficult to trust these random programs, but desperate users with bricked phones don't have many other options...
I had to pay 25€ to get mine running again. The fact that you have to pay sucks. It shouldn't be like that.
I paid more than $30 to random person I found on youtube and I still had to disassemble my phone myself to put it on EDL mode (was it really necessary? - since my phone has an unlocked bootloader).
WARNING! Xiaomi Tools Pro contains a backdoor virus
Win32/Bladabindi!ml - Virus
This will allow the hacker to gain control of your computer and potentially draining your bank accounts/bitcoin.
you have been warned.
I have always bought Xiaomi Products but after reading all the trouble that you have to go through and zero customer support with most software infected by ****ty backdoors, I have to go back to some oneplus or pixel or mainstream phones.
Hello everyone,
I just wanted to say I followed the instructions above and it worked fine. I paid 10€ for 10 credits at <Moderator Edit>: (removed) and I used the tool and everything went smooth with my poco f3. Just like it says in the tutorial, if it does not reboot automatically, just charge your phone for a few minutes and voilá. Just wanted to leave my input in here, so if anyone is in this situation, you CAN fix your phone.
<Moderator Edit>: Thread closed. @raminta look for my PM shortly.
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
{
"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"
}
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
try 'fastboot --set-active=other' or unbrick with MSM Download tool or https://github.com/bkerler/edl
chizari said:
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
View attachment 5813705
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
Click to expand...
Click to collapse
bro just use the msm tool. there's a tool for every variant of the 9 pro (LE2120-2125). Look for the post on our Device xda and use it.
aIecxs said:
try 'fastboot --set-active=other'
Click to expand...
Click to collapse
cmd says: fastboot: unknown option -- set-active=other
I think it doesn’t understand what‘s --, maybe ’cause i dont have libraries or drivers
ishansnp said:
bro just use the msm tool. there's a tool for every variant of the 9 pro (LE2120-2125). Look for the post on our Device xda and use it.
Click to expand...
Click to collapse
i know about msm tool, but i cant enter in qualcomm emergency mode, cause when i connect phone to pc, it starts charging and when phone starts charging it can’t load “charge image” and gives same error as in the attachment
chizari said:
i know about msm tool, but i cant enter in qualcomm emergency mode, cause when i connect phone to pc, it starts charging and when phone starts charging it can’t load “charge image” and gives same error as in the attachment
Click to expand...
Click to collapse
turn off the phone fully, press volume up and down fully for 3 seconds then while still holding those buttons, plug in the phone with MSM open on your laptop. it should immediately detect the device. the phone screen will still be black and thats normal. once device is shown as connected, just select target O2 and start
disconnect usb, let battery drain, ensure it is really powered off, press both volume keys, connect usb
chizari said:
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
View attachment 5813705
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
Click to expand...
Click to collapse
MSM Tool time. What model do you have?
aIecxs said:
disconnect usb, let battery drain, ensure it is really powered off, press both volume keys, connect usb
Click to expand...
Click to collapse
ok, i ll try
TheGhost1951 said:
MSM Tool time. What model do you have?
Click to expand...
Click to collapse
LE2123
chizari said:
LE2123
Click to expand...
Click to collapse
Get the MSM tool for LE2123 from this thread....
How To Guide OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
Does somebody know how long it takes to let battery drain from 100%?
And maybe, Are there some advices how to let battery drain faster?
You will also need to 1) disable driver signature see this https://www.techpout.com/disable-driver-signature-enforcement/ then reboot computer 2) install latest OnePlus USB drivers then 3) install latest Qualcomm driver then reboot PC 4) start the MSM Tool uncheck 256 and check use lite firehose the click start. 5) start phone in edl mode with button sequence.... MSM should automatically start flashing!
As for edl mode, check to see if you can get to fastboot by holding vol + and - and power buttons down and hold them to see if fastboot loads. This is if you cannot get to edl the button wat as described above.
TheGhost1951 said:
As for edl mode, check to see if you can get to fastboot by holding vol + and - and power buttons down and hold them to see if fastboot loads. This is if you cannot get to edl the button wat as described above.
Click to expand...
Click to collapse
Fastboot menu loads
Now i need to wait few days to let battery drain…
Maybe you know any advices how to let it drain faster?
chizari said:
Fastboot menu loads
Now i need to wait few days to let battery drain…
Maybe you know any advices how to let it drain faster?
Click to expand...
Click to collapse
No need to wait.... Do you have the latest platform-tools installed on PC?
TheGhost1951 said:
No need to wait.... Do you have the latest platform-tools installed on PC?
Click to expand...
Click to collapse
Yeah, i installed it with android studio
chizari said:
Yeah, i installed it with android studio
Click to expand...
Click to collapse
Good now download this file and save it to the platform-tools folder and change the name to twrp.img.... https://dl.twrp.me/lemonadep/twrp-3.7.0_11-0-lemonadep.img make sure the phone is connected to PC in fast boot mode if you have already installed all the drivers....
TheGhost1951 said:
You will also need to 1) disable driver signature see this https://www.techpout.com/disable-driver-signature-enforcement/ then reboot computer 2) install latest OnePlus USB drivers then 3) install latest Qualcomm driver then reboot PC 4) start the MSM Tool uncheck 256 and check use lite firehose the click start. 5) start phone in edl mode with button sequence.... MSM should automatically start flashing!
Click to expand...
Click to collapse
here you mentioned qualcomm drivers, you mean Qualcomm HS-USB QDLoader 9008 Drivers
chizari said:
here you mentioned qualcomm drivers, you mean Qualcomm HS-USB QDLoader 9008 Drivers
Click to expand...
Click to collapse
Yes