The current image(boot/recovery) have been destroyed and can not boot. - Realme X2 Questions & Answers

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?

Related

Sprint LG G2 Brick - Not showing in device manager - Download mode working!

Hey guys, my friend recently bought an LG G2 on Sprint, but switched carriers to T-Mobile. He rooted his phone successfully, and tried to install custom recovery but downloaded some app that screwed up his phone (not completely sure what happened... he told me he installed a flashing app that flashed recovery but long story short, his phone is in a boot loop.) I can access download mode, and fastboot. When I connect the phone to the computer, my Windows 8.1 Laptop, nothing pops up. I already installed ADB and Fastboot, and when I put the phone into fastboot mode and plug it into the computer, it is recognized but keeps saying "oops!" connection to USB failed trying again.... fastboot ready! etc. etc. I installed the LG Flash tool but the computer won't recognize my device in device manager! I'm really frustrated why it won't recognize it. It shows nothing except ACER Fastboot Device. I just want it to recognize it in download mode so i can flash it back to stock with the LG Flash tool.
Pls halp.
I had to download lg universal drivers for my laptop to recognize my phone in download mode give that a try
im in the same boat as the op. i have tried to install various drivers. im able to get into download mode but no communication with the comp. i try going to recovery but it is gonna and i see some type of fastboot. unsure where to go from here...
This is exactly what i did
Www.rwilco12.com/forum/showthread.php?tid=96
My phone wasnt recognized by laptop until i was in download mode with flash tool running
not finding the ports under device manager anywhere.
Hi
I also have issue with don't recognized device in device manager. Did you solve this issue?
P.S. I have another G2 with normal running android. This G2 has normaly recognized in device manager. So problem not in cable or usb port's.
kdm212 said:
not finding the ports under device manager anywhere.
Click to expand...
Click to collapse
does the computer make a noise when you plug in the device? Also are you sure your in download mode ? (not just the dots) If you have just the dots, then go info fastboot mode and flash both the boot.img and laf.img then reboot into download mode and see if it works
I just put my g2 in download mode and pluged her up. in device manager it poped up under lge android modem, in the modem section of device manager.
Look there first. Then you will have to change the port to 41 so the flash tool will work
If you have qpst it will Tell you what port
Sent from my LG-LS980 using XDA Free mobile app
jcwxguy said:
does the computer make a noise when you plug in the device? Also are you sure your in download mode ? (not just the dots) If you have just the dots, then go info fastboot mode and flash both the boot.img and laf.img then reboot into download mode and see if it works
Click to expand...
Click to collapse
Have the same problem as the OP.
PC don't make any noise.
Yes sure, have a download mode screen on display.
Can't access to fast boot:
1) When i press Vol Up + plug the cable, have a download mode, but PC show nothing in device manager.
Stuck on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) When i press Vol Down + power, have a factory hard reset screen which stuck if i agreed to factory reset.
3) When i press Vol up + Vol down + power, have a Hardware key control mode screen.
DEFNUB said:
I just put my g2 in download mode and pluged her up. in device manager it poped up under lge android modem, in the modem section of device manager.
Look there first. Then you will have to change the port to 41 so the flash tool will work
If you have qpst it will Tell you what port
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
OP says that device is not recognized in device manager!
demos98 said:
Have the same problem as the OP.
PC don't make any noise.
Yes sure, have a download mode screen on display.
Can't access to fast boot:
1) When i press Vol Up + plug the cable, have a download mode, but PC show nothing in device manager.
Stuck on this
View attachment 2912813
2) When i press Vol Down + power, have a factory hard reset screen which stuck if i agreed to factory reset.
3) When i press Vol up + Vol down + power, have a Hardware key control mode screen.
Click to expand...
Click to collapse
what i had to do when this happened to me, was swap out the device at sprint (had insurance), without insurance you can swap it for $75ish plus tax or if its still under warranty, go through LG
Could also try this thread :
http://forum.xda-developers.com/showthread.php?t=2582142

[Q] LG G3 boot certification verify problem

Hello,
I believe I bricked my phone last night.
I tried to update my LG to Android Lollipop. The phone is not rooted. I did everything too quickly and read badly, but now I'm stuck when I try to boot my phone I get this screen:
https://cdn-images.xda-developers.com/direct/2/4/5/7/4/0/6/20131216_141539.jpg
And then the phone turns off and the LED starts flashing. Hard resetting is not working either, because after I got to the factory reset menu it restarts and show that screen again.
My computer doesn't recognize the phone anymore, how can I solve this?
Thanks in advance,
Did you fix it? I have the same problem...
What did you used to update your G3?
Bump Bump!! this thread.
Anyone know how to get back boot????
You need to flash a bump'ed recovery, like this one: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
tobitege said:
You need to flash a bump'ed recovery, like this one: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
Click to expand...
Click to collapse
may i ask what does bumped mean? new to lg g3
Hi,
How do you bump when you cannot run the command adb shell? The G3 does not get picked up by the computer when connected to USB (LGUnitedMobileDriver_S51MAN313AP22_ML_WHQL_Ver_3.13.2 and LG_VZW_United_WHQL_v2.14.1.exe are installed).
When I put the phone in "Download Mode" to try and restore it with the LG Flash Tool 2014, it goes straight back to the "boot certification verify" screen about a second later. I can get the phone to show the "System recovery" menu, which has these options:
Continue Power up
Safe mode
USB debug mode
Factory data reset
Wipe cache
Power Down
However, none of these work. Selecting "Safe mode", "USB debug mode", "Wipe cache", or "Factory data reset" causes the phone to go back to the "boot certification verify" screen.
Any suggestions?
Bro you need to CSE flash the KDZ
This is because your phone's kernel and the inbuilt android bootloader dont match which is why if gives boot certification error
Hey,
I'm very familiar with the LG Flash Tool and have done the CSE flash using tot and kdz files; however, I can't get my phone to stay in the "Download Mode". When I enter the "Download Mode", it shows the "boot certification verify" in the same screen and then kicks me out of the download mode--not giving me enough time to get flash the KDZ files.
Any other suggestions?
xstahsie said:
Hey,
I'm very familiar with the LG Flash Tool and have done the CSE flash using tot and kdz files; however, I can't get my phone to stay in the "Download Mode". When I enter the "Download Mode", it shows the "boot certification verify" in the same screen and then kicks me out of the download mode--not giving me enough time to get flash the KDZ files.
Any other suggestions?
Click to expand...
Click to collapse
Then theres nothing you can do about it. Take it into a service center and tell them it happened when you tried updating it to lollipop
That happens because theres a version mismatch between your sbl (bootloader), aboot (android bootloader) and laf (download mode)
Damn. Same thing just happened to me. I'm hoping someone can come up with a fix. I can't find or figure out anything on this problem.
swiftinc said:
Damn. Same thing just happened to me. I'm hoping someone can come up with a fix. I can't find or figure out anything on this problem.
Click to expand...
Click to collapse
No custom recovery or fastboot mode + signature error = service.
YaDr said:
No custom recovery or fastboot mode + signature error = service.
Click to expand...
Click to collapse
Thanks for the useful information.
swiftinc said:
Thanks for the useful information.
Click to expand...
Click to collapse
Anyone with lg's tools. Mainly official services, but i would've googled for local unofficial service first. Official ones love to replace motherboards for $250 instead of reflashing them for 50$...
OK... I think I'm making some progress in this effort to try an unbrick the G3 and need help from the community on this now.
See the two screen shots.
Screen shot 1...
Basically, I got the phone to show "Qualcomm HS-USB QDLoader 9008" in Device Manager. What I did next was updated the driver by replacing the Qualcomm with the lgandbus.inf found in the "LG United Mobile Driver" ( go to C:\Program Files (x86)\LG Electronics\LG VZW United Driver).
You may need to restart your computer for the changes to take affect.
On to screen shot 2...
Load up "LG Flash Tool 2014". You should know where to find this tool on xda. Select your KDZ file, select CSE Flash and click on "START". However, this will not flash any files to the phone.
You can get the program to read the phone information, which looks corrupted.
Please give it a shot. If you get it to flash, please share!
{
"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"
}
xstahsie said:
OK... I think I'm making some progress in this effort to try an unbrick the G3 and need help from the community on this now.
See the two screen shots.
Screen shot 1...
Basically, I got the phone to show "Qualcomm HS-USB QDLoader 9008" in Device Manager. What I did next was updated the driver by replacing the Qualcomm with the lgandbus.inf found in the "LG United Mobile Driver" ( go to C:\Program Files (x86)\LG Electronics\LG VZW United Driver).
You may need to restart your computer for the changes to take affect.
On to screen shot 2...
Load up "LG Flash Tool 2014". You should know where to find this tool on xda. Select your KDZ file, select CSE Flash and click on "START". However, this will not flash any files to the phone.
You can get the program to read the phone information, which looks corrupted.
Please give it a shot. If you get it to flash, please share!
Click to expand...
Click to collapse
Flash tool won't work. However, unbrick from "Qualcomm HS-USB QDLoader 9008" is possible.
There was an unbrick package from QDloader state. Search this forum for "Qualcomm HS-USB QDLoader 9008".
EDIT: found it. Seems like it doesn't work, though.
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
Boot Certification Verify error happened to me yesterday as I was trying to upgrade to 23B. I've researched and there does not appear to be any way to bring the phone back to life. I called Verizon, explained the problem (not the reason for the problem) and they are shipping me a replacement LG G3 free of charge as the phone was still under warranty. Lucky for me I have a Moto X (2nd Gen) as a back up and it's a great phone.
I got this when I had flashed Multirom (most likely corrupt download) this was fixed by restoring stock from bumped TWRP. Maybe try flashing a stock image with something like lgtool or flashtool (should have the same effect as using an RUU on a HTC device.)
Edit: Looks like you already tried that. Have you tried the tool on a different machine? e.g. XP/ win 7
Offering Some Help
Hi Friends,
I learned how to manually update my LG G3 (D858HK variant, dual-SIM) from Kitkat to Lollipop via a "manual" method. I learned it from this thread. In the course of learning it, I did encounter "certification verify", "security error", and other nasty things. I documented my learnings and also put up a guide/how-to. I just thought of linking the thread over here and hope it can help: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
There's a lot of reading to be done there, please do so before doing anything.
EDIT: oh shoot...he has no custom recovery (i.e. TWRP) at all? My bad, I wasn't able to read through all the posts.
solution for no download mode, stuck logo, qhsusb bulk 9006 and 9008
Hi dear frends.
Its sad to know that all you guys cant go to download mode or facing security error.
And some guys stuck qhsuab bulk 9008
So the solution is here.
If you are unable to get into download mode then you need to force your g3 into qhsusb bulk mode by shorting the test point.
I will help u all guys.....
I will help u to unbrick ur any lg model wothout download mode or stuck in 9008 or anytype of problem.
Please let me know your problem in pm.

Hardbricked, can't get into EDL mode anymore

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

Question [HELP] Unbrick an almost completely bricked phone.

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.

Question How to unlock device state on “brick”

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

Categories

Resources