Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, here is the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord to Oxygen OS 11
You can also rollback your phone to a previous release of OOS with them if for some reason you would like to go back to an older firmware
You can download the following versions:
Only for Indian Devices
ANDROID 11:
[Mod Edit] Download link removed (URL shortener used to gain profit)
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select India
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)
Power your device off.
Let it cool down for one minute.
Maintain volume up and volume down keys for at least 40 seconds to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
Credits :
@Some_Random_Username thanks for providing the text layout for this post.
Nice !!! Now don't have to hope between Android 10 and 11 every goddamn time
Hi, how did you get .ops file for android 11, I am looking for Europe Oxygen 11 file for msm flashing. Any help is appriciated
Any way we can retrieve the file?
saikiransalama said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, here is the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord to Oxygen OS 11
You can also rollback your phone to a previous release of OOS with them if for some reason you would like to go back to an older firmware
You can download the following versions:
Only for Indian Devices
ANDROID 11:
[Mod Edit] Download link removed (URL shortener used to gain profit)
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select India
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)
Power your device off.
Let it cool down for one minute.
Maintain volume up and volume down keys for at least 40 seconds to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
Credits :
@Some_Random_Username thanks for providing the text layout for this post.
Click to expand...
Click to collapse
any hope to get this tool?
Related
I have an LG E435g. I tried to flash another version of stock firmware (V20a_00) using KDZ updater tool. It did flash, but my phone is f***d. The screen is totally black (no logo,etc.). My PC recognizes that it is connected, but I cannot load MTP driver for file transfers. It was in debug mode during flash, but isn't now because I can't use adb. Have tried everything in forums, nothing changes. I will pay ANYONE to fix as I am at wits end and know just enough to screw s**t up. Totally unable to get into download mode, emergency mode,etc. Phone is not rooted and the bootloader is locked.
No problem
brdbat416 said:
I have an LG E435g. I tried to flash another version of stock firmware (V20a_00) using KDZ updater tool. It did flash, but my phone is f***d. The screen is totally black (no logo,etc.). My PC recognizes that it is connected, but I cannot load MTP driver for file transfers. It was in debug mode during flash, but isn't now because I can't use adb. Have tried everything in forums, nothing changes. I will pay ANYONE to fix as I am at wits end and know just enough to screw s**t up. Totally unable to get into download mode, emergency mode,etc. Phone is not rooted and the bootloader is locked.
Click to expand...
Click to collapse
THIS GUIDE IS FOR UN-BRICKING ALL KNOWN TO ME LG Lx PHONES ON WINDOWS BASED COMPUTERS
(Virtual Machine Will Work )
THIS GUIDE ASSUMES YOU HAVE DRIVERS INSTALLED
>>>>>FOUND HERE IF YOU CAN'T USE GOOGLE<<<<<
THIS GUIDE ASSUMES YOU HAVE KDZ UPDATE PROGRAM
>>>>>FOUND HERE IF YOU CAN'T USE GOOGLE<<<<<
THIS GUIDE ASSUMES YOU HAVE .kdz FIRMWARE DOWNLOADED
>>>>>FOUND HERE IF YOU CAN'T USE GOOGLE<<<<<
1. Plug USB cable to PC
2. Take battery out of phone
3. Press and hold VOL- button or VOL+ or VOL+ and VOL-
4. Plug USB cable to phone
5. Wait few seconds ... (it should display "Download Mode" on black screen)
6. Put battery back in phone
7. UPDATE YOUR KDZ NOW
8. navigate to phone settings and security and preform wipe/master reset (not obligatory but ensures "clean rom" )
Enjoy your NEW OLD phone
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
have you tried to re-install the Driver? make sure that you only use win 64 bit for flashing, many issues occurred when you try to flash using win 32 bit
I am using Windows 10 64 bit. Moreover, I have installed ADB drivers separately (although these seem to come with the Mi Flash utility too).
I think it's intended behavior not to be able to flash via Fastboot with the bootloader locked? I was hoping to be able to restore via Mi PC Suite but it can't seem to see the phone, although the computer does and Mi Flash does too.
try using Mi PC Suite, http://en.miui.com/thread-92720-1-1.html, After Mi PC Suite is installed, make sure that your phone is in fastboot mode, connect your phone to a computer, and select the correct ROM file to flash
"I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too)."
For some reason, Mi PC Suite is not detecting the phone.
Ultimatum99 said:
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
Hello there,
I faced the same situation, but unfortunately in download mode, the phone is not detected in MiFlash, it detected as QHSUSB_BULK in Windows. Phone is detected while in fastboot and normal mode, but not in download mode. Do you have any idea what to do?
I expect this is a driver issue, but I can't figure out what.. I'm using Windows 64 bit, disabled driver signature enforcement, and installed all driver from MiFlash installation (there were 3 of driver notification prompt).
noersetiawan said:
Hello there,
I faced the same situation, but unfortunately in download mode, the phone is not detected in MiFlash, it detected as QHSUSB_BULK in Windows. Phone is detected while in fastboot and normal mode, but not in download mode. Do you have any idea what to do?
I expect this is a driver issue, but I can't figure out what.. I'm using Windows 64 bit, disabled driver signature enforcement, and installed all driver from MiFlash installation (there were 3 of driver notification prompt).
Click to expand...
Click to collapse
You need to update QHSUSB_BULK to the Qualcomm driver.
Device Manager > Select QHSUSB_BULK > Update Driver Software > Find manually the location of the driver, most likely: C:\Program Files (x86)\Xiaomi\MiPhone\Qualcomm\Driver
The driver should now appear as Qualcomm something, and Mi Flash should be able to see the phone.
Does this work?
Ultimatum99 said:
You need to update QHSUSB_BULK to the Qualcomm driver.
Device Manager > Select QHSUSB_BULK > Update Driver Software > Find manually the location of the driver, most likely: C:\Program Files (x86)\Xiaomi\MiPhone\Qualcomm\Driver
The driver should now appear as Qualcomm something, and Mi Flash should be able to see the phone.
Does this work?
Click to expand...
Click to collapse
Hi,
Thank you for the help. Unfortunately it doesn't work straight away, fortunately this leads me to the right direction, after I tried to point the driver to Xiaomi directory, a window dialog says the driver is 32 bit thus noninstallable for my PC, then I looked around for 64 bit driver for Qualcomm, installed it. I can finally install the driver but the phone is detected as unknown USB device, after removing it from Device Manager, restarted my PC, and tried again, it's still the same, on the third try it finally detected properly. It's working now, thank you very much.
Really weird why did MiFlash comes with noninstallable driver.
Ultimatum99 said:
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
My 3s prime is locked bootloader, developer option off, oem disable thus not able to flash as device is in bootloop.
Garu8 said:
My 3s prime is locked bootloader, developer option off, oem disable thus not able to flash as device is in bootloop.
Click to expand...
Click to collapse
you have to flash in edl mode not fastboot so google on how to take redmi 3s into edl mode then you can flash the rom in locked bootloader.in redmi 3 we use volume up and volume down and power button.press all three at the same time and it will take u to edl mode.screen becomes all black but if you plug it to ur computer and press refresh in miflash then it will show as com 10 or 20.thats for redmi 3.maybe redmi 3s has the same steps
jokerpappu said:
you have to flash in edl mode not fastboot so google on how to take redmi 3s into edl mode then you can flash the rom in locked bootloader.in redmi 3 we use volume up and volume down and power button.press all three at the same time and it will take u to edl mode.screen becomes all black but if you plug it to ur computer and press refresh in miflash then it will show as com 10 or 20.thats for redmi 3.maybe redmi 3s has the same steps
Click to expand...
Click to collapse
I have already tried to switch to edl mode using cmd with "fastboot oem edl" command but it enter bootloop. It happen because oem is locked alongwith usb debugging as I didn't unlock developer option.
Garu8 said:
I have already tried to switch to edl mode using cmd with "fastboot oem edl" command but it enter bootloop. It happen because oem is locked alongwith usb debugging as I didn't unlock developer option.
Click to expand...
Click to collapse
then you should buy a usb cable which has a button in it which forces xiaomi devices to boot into edl mode.i forgot its name but i think you can google to find it
jokerpappu said:
then you should buy a usb cable which has a button in it which forces xiaomi deveot into edl mode.i forgot its name but i think you can google to find it
Click to expand...
Click to collapse
I believe you are talking about dfc a.k.a deep flash cable. I have searched alot I couldn't find it on any e-commerce site except alibaba which doesn't ship at my place. Can yousuggest any seller or website if you ever came across selling dfc cable? Deep flash method is the only last resort for my problem other than sending phone to service centre. Could you suggest any website to make dfc cable manually?;as I have searched youtube but non of the method mentioned in it seemed liable to me.
Garu8 said:
I believe you are talking about dfc a.k.a deep flash cable. I have searched alot I couldn't find it on any e-commerce site except alibaba which doesn't ship at my place. Can yousuggest any seller or website if you ever came across selling dfc cable? Deep flash method is the only last resort for my problem other than sending phone to service centre. Could you suggest any website to make dfc cable manually?;as I have searched youtube but non of the method mentioned in it seemed liable to me.
Click to expand...
Click to collapse
i saw it on ebay also.i think that seller will ship worldwide to any country.
here is the link
http://www.ebay.com/sch/i.html?_fro...le.TRS0&_nkw=xiaomi+deep+flash+cable&_sacat=0
You don't need deep flash cable use button combo to put in edl mode. From device manager update driver for QHSUSB_BULK. \After that reboot pc with driver signature disabled, then open mi flash and phone should be recognised. Just found the thread I used to remove vendor rom.
http://en.miui.com/thread-254606-1-1.html
JUST MAKE SURE YOU DOWNLOAD THE ROM FOR YOUR DEVICE!:crying:
jazz452 said:
You don't need deep flash cable use button combo to put in edl mode. From device manager update driver for QHSUSB_BULK. \After that reboot pc with driver signature disabled, then open mi flash and phone should be recognised. Just found the thread I used to remove vendor rom.
http://en.miui.com/thread-254606-1-1.html
JUST MAKE SURE YOU DOWNLOAD THE ROM FOR YOUR DEVICE!:crying:
Click to expand...
Click to collapse
As I have already said edl mode won't work since developers option was not activated as edl requires oem activated. I had already tried all the methods.
By the way thanks to u all at xda as I have successfully flashed new rom using deep flash cable method...
Nexus 10 rooted in a bootloop
Hi folks! I'm a newbie with this stuffs so I'll do my best to explain the issue. I've recently rooted my Nexus 10 with Nexus root toolkit 2.1.9( I believe). All was fine until I turn it off and back on. Now I'm in a bootloop. I could use the Unroot+flash command but my windows 7 won't detect the device. It only detect it when my tablet is connected and turn off. In that case shows as MTP. Can anyone help me reinstalling the driver or else? Thank you
Novice12 said:
Hi folks! I'm a newbie with this stuffs so I'll do my best to explain the issue. I've recently rooted my Nexus 10 with Nexus root toolkit 2.1.9( I believe). All was fine until I turn it off and back on. Now I'm in a bootloop. I could use the Unroot+flash command but my windows 7 won't detect the device. It only detect it when my tablet is connected and turn off. In that case shows as MTP. Can anyone help me reinstalling the driver or else? Thank you
Click to expand...
Click to collapse
Hi,
This is Redmi 3 section. The correct section for your device is here. Please explain your issue there. Good luck!
Sent from my Redmi 3 using XDA Labs
Unbrick Xiaomi Redmi 3s prime with unlocked boot loader
Hi all,
I've a Xiaomi redmi 3s prime with rooted and unlocked bootloader. I tried unrooting from SuperSu and the phone is in bootloop now. I had TWRP recovery mod installed and a nandroid back up in my phone. But, I can't even enter the recovery mode now. Fast boot is working. Please help me to unbrick it without losing the data or recover the nandroid back up at least.
Thanks!!
Ultimatum99 said:
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
look
you got bootloop and its very very different from brick
update your title
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004)
Follow the following steps:
1. Get SP flash tools (Latest version)
2. Download your phone's firmware (from manufacturer site or needrom.com etc) and extract it.
3. install Mediatek Preloader drivers as per your OS version (win x7 , 8 10 etc) and architecture (32/64bit).
4. Run Flash tools with admin as administrator
5. select the scatter file from the firmware folder you downloaded and wait for it to load. (Do not connect your phone yet and leave the battery inserted)
6. Select Download Only
7. Hit the download button
8. Now plug in the micro/type C usb end of your cable to your phone but dont plug to PC. yet
9. While hold down both volume buttons i.e up and down buttons, (Do not press the power button), Insert the Usb cable end to your PCs usb port (Please choose a port thats very reliable).
10. After a while, P Flash tool will begin to upgrade your phone, dont release the buttons yet, let it lapse about 2mins then release them, the firmware upgrade will still continue and it will display a tick pop-up when done (this may take between 5-10mins).
Now unplug your phone, remove and re-insert the battery and power-up your phone. You phone is now unbricked.
Note that the first boot will longer than a regular boot.
This saved me
Oh my god. I was searching for hours and hours for a solution. This post saved my back side.
Perfect Solution for ZTE Blade A520
Thank you very much. This worked like a charm. Very helpful
adisa said:
FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004)
Follow the following steps:
1. Get SP flash tools (Latest version)
2. Download your phone's firmware (from manufacturer site or needrom.com etc) and extract it.
3. install Mediatek Preloader drivers as per your OS version (win x7 , 8 10 etc) and architecture (32/64bit).
4. Run Flash tools with admin as administrator
5. select the scatter file from the firmware folder you downloaded and wait for it to load. (Do not connect your phone yet and leave the battery inserted)
6. Select Download Only
7. Hit the download button
8. Now plug in the micro/type C usb end of your cable to your phone but dont plug to PC. yet
9. While hold down both volume buttons i.e up and down buttons, (Do not press the power button), Insert the Usb cable end to your PCs usb port (Please choose a port thats very reliable).
10. After a while, P Flash tool will begin to upgrade your phone, dont release the buttons yet, let it lapse about 2mins then release them, the firmware upgrade will still continue and it will display a tick pop-up when done (this may take between 5-10mins).
Now unplug your phone, remove and re-insert the battery and power-up your phone. You phone is now unbricked.
Note that the first boot will longer than a regular boot.
Click to expand...
Click to collapse
Thank you very much Sir, you are awesome!
Thank you very much Sir, you are awesome! I have made my dead phone alive following your post. You are the Life Saver of my phone. I have no word to thank you. I salute your hard work. Thank you very much. I want to share your post to everyone who are seeking solution like me.
mohidulhaq said:
Thank you very much Sir, you are awesome! I have made my dead phone alive following your post. You are the Life Saver of my phone. I have no word to thank you. I salute your hard work. Thank you very much. I want to share your post to everyone who are seeking solution like me.
Click to expand...
Click to collapse
New Error Now-
Error : S_AUTH_HANDLE_IS_NOT_READY(5000)
i have this error "Failed to Connect DA: S_AUTH_HANDLE_IS_NOT_READY". i dont know how i do
Ndanou jean-claude said:
i have this error "Failed to Connect DA: S_AUTH_HANDLE_IS_NOT_READY". i dont know how i do
Click to expand...
Click to collapse
Hi!
You should watch this video and tutorial, it was helpful for me too.
https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I did use Maui Meta tool in the past to restore IMEIs on slitely older MTK devices, but My current phone is based on MTK6768 with secure boot, needed the IMEIs to be written after flashing firmware. I can use SP flash tool with "sec boot" utility to flash ROM successfully, But unable to connect to Maui Meta tool. I have Modem meta tool Version 10.2044, after launching the program as an admin, it is doing the following:
1. Clicking "connect" and plugging the cable to phone in turned off state: windows make a hardware connect sound, a new port appear in device manager, followed by a disconnect sound after 1 second, that hardware disappear and phone boot-up in offline charging mode or to the welcome/lock screen. The "meta tool" remain at looking for device connection.
2. Holding the Volume down while plugging the Cable in, do the exact same - "meta Tool" remain in waiting for connection.
3. Holding Volume Up: it connect, then disconnect and went to Stock recovery - "meta tool" remain in waiting state.
4. Holding Power+Volume up: Windows continue making connect and disconnect sounds again and again and the Port under device manager keep coming in and out. Phone boots up as soon as I leave the buttons. "meta Tool" remain in waiting for connection, or sometime move to "getting Kernel Port" and get stuck at it.
5. Holding both volume buttons: do the exact same as point Number 4 above.
6. Holding both volumes+power buttons: do the exact same as point number 4 above.
Definitely, all MTK drivers are installed and working because I can use SP flash tool in conjunction with secBoot utility without any problem. I tried other similar tools like “SN writer” and “read and write tool v1.3” and faced almost same behaviour. It means my device is not going into Meta mode properly with these tools. Please contribute in helping me with your valuable suggestion, as I’m not being able to use this device due to cellular network unavailability.
You need to use Preloader Mode not MTK mode, look at Com Port driver, try boot device to normal mode and make power off then hold up and connect USB must get preloader device if get mtk USB port only not work, see mtk preloader to enter META mode
MA7MOD_GSM said:
You need to use Preloader Mode not MTK mode, look at Com Port driver, try boot device to normal mode and make power off then hold up and connect USB must get preloader device if get mtk USB port only not work, see mtk preloader to enter META mode
Click to expand...
Click to collapse
bro. he literally said preloader comes, but disconnects, + it gets stuck on getting kernel on sn flash tool.
I tried sn flash tool, it got stuck, I tried aftersalestool, it does not stuck, but it says:error code 6 get kernel port.
What do i do? I need to fix my IMEI very badly!
Abdullah5490 said:
I did use Maui Meta tool in the past to restore IMEIs on slitely older MTK devices, but My current phone is based on MTK6768 with secure boot, needed the IMEIs to be written after flashing firmware. I can use SP flash tool with "sec boot" utility to flash ROM successfully, But unable to connect to Maui Meta tool. I have Modem meta tool Version 10.2044, after launching the program as an admin, it is doing the following:
1. Clicking "connect" and plugging the cable to phone in turned off state: windows make a hardware connect sound, a new port appear in device manager, followed by a disconnect sound after 1 second, that hardware disappear and phone boot-up in offline charging mode or to the welcome/lock screen. The "meta tool" remain at looking for device connection.
2. Holding the Volume down while plugging the Cable in, do the exact same - "meta Tool" remain in waiting for connection.
3. Holding Volume Up: it connect, then disconnect and went to Stock recovery - "meta tool" remain in waiting state.
4. Holding Power+Volume up: Windows continue making connect and disconnect sounds again and again and the Port under device manager keep coming in and out. Phone boots up as soon as I leave the buttons. "meta Tool" remain in waiting for connection, or sometime move to "getting Kernel Port" and get stuck at it.
5. Holding both volume buttons: do the exact same as point Number 4 above.
6. Holding both volumes+power buttons: do the exact same as point number 4 above.
Definitely, all MTK drivers are installed and working because I can use SP flash tool in conjunction with secBoot utility without any problem. I tried other similar tools like “SN writer” and “read and write tool v1.3” and faced almost same behaviour. It means my device is not going into Meta mode properly with these tools. Please contribute in helping me with your valuable suggestion, as I’m not being able to use this device due to cellular network unavailability.
Click to expand...
Click to collapse
I have this same issue where my device can't get detected by any IMEI writer as itneeds to be in meta mode. Do you have any success on this ?
K!r!to26 said:
I have this same issue where my device can't get detected by any IMEI writer as itneeds to be in meta mode. Do you have any success on this ?
Click to expand...
Click to collapse
I also got the same Issue, But it gives a kernel error, Idk, what error it is, and what's the fix, The Local Tech Repair shop did the restoration, but gave me the mobile without IMEI, so, I am stuck, I am also afraid to re flash the stock rom, because I dont know what the hell they did, Maybe they did some kernel change, or the kernel is the same as the wrong one? Idk, Maybe I would say, Reflash your mobile, and check it.
Having the same-ish issue on redmi note 8 pro. any progress?
Abdullah5490 said:
I did use Maui Meta tool in the past to restore IMEIs on slitely older MTK devices, but My current phone is based on MTK6768 with secure boot, needed the IMEIs to be written after flashing firmware. I can use SP flash tool with "sec boot" utility to flash ROM successfully, But unable to connect to Maui Meta tool. I have Modem meta tool Version 10.2044, after launching the program as an admin, it is doing the following:
1. Clicking "connect" and plugging the cable to phone in turned off state: windows make a hardware connect sound, a new port appear in device manager, followed by a disconnect sound after 1 second, that hardware disappear and phone boot-up in offline charging mode or to the welcome/lock screen. The "meta tool" remain at looking for device connection.
2. Holding the Volume down while plugging the Cable in, do the exact same - "meta Tool" remain in waiting for connection.
3. Holding Volume Up: it connect, then disconnect and went to Stock recovery - "meta tool" remain in waiting state.
4. Holding Power+Volume up: Windows continue making connect and disconnect sounds again and again and the Port under device manager keep coming in and out. Phone boots up as soon as I leave the buttons. "meta Tool" remain in waiting for connection, or sometime move to "getting Kernel Port" and get stuck at it.
5. Holding both volume buttons: do the exact same as point Number 4 above.
6. Holding both volumes+power buttons: do the exact same as point number 4 above.
Definitely, all MTK drivers are installed and working because I can use SP flash tool in conjunction with secBoot utility without any problem. I tried other similar tools like “SN writer” and “read and write tool v1.3” and faced almost same behaviour. It means my device is not going into Meta mode properly with these tools. Please contribute in helping me with your valuable suggestion, as I’m not being able to use this device due to cellular network unavailability.
Click to expand...
Click to collapse
Ok Fixed this Problem: https://forum.xda-developers.com/t/...ote-7-x690-x690b-x690c.4592491/#post-88605287
View this thread, Explained in detail.
i need help qboot is not recognizing my Moto g power 2021 Borneo i try to hold power and volume down button nothing happen and i'm using Linux is there anything i can do to fix it without taking it apart and try to find EDL PIN
KILLFIREY1389 said:
i need help qboot is not recognizing my Moto g power 2021 Borneo i try to hold power and volume down button nothing happen and i'm using Linux is there anything i can do to fix it without taking it apart and try to find EDL PIN
Click to expand...
Click to collapse
Not sure what the rules are for posting links/urls so I hope I'm not breaking any but here's one to some blank flashes just incase you didn't already visit there.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The one I used was: blankflash_borneo_usc_RZBS31.Q2-143-27-11-1.zip
I use Ubuntu and occasionally Windows 7 because I'm not a fan of anything made after that but I was having some trouble getting it to work through Linux. (possibly because I'm an amateur and didn't want to work to hard to get it to work). As soon as I switched to Windows 7 and started the .bat file it worked first try so hopefully that helps a little. Try them all if one doesn't work.
The build I was on prior to brick was: motorola/borneo_retail/borneo:10/QZB30.Q4-43-35/7ad68:user/release-keys
But like I said the one I posted worked fine but I had to do it on windows not Linux so I'd highly recommend giving that a try.
After it flashed and rebooted back into fastboot I used LSMA (Lenovo Smart Assistant) and had it detect and download the correct firmware and then just flashed it through fastboot.
If Windows doesn't detect the drivers press and hold the power+volume down buttons together for about 20 seconds or until you see it appear. Unplug and plug back in and then do that again if it didn't work but it should without having to download drivers separately I believe.
I'm not sure if it's required but I had "driver integrity checking disabled" and it was in "test mode build 7601" both can be set through the windows command prompt but I don't remember windows commands at all so Google would be your friend on that one if it's even needed. That was also doing it on Windows 7.
Just a reminder I'm not an expert just a normal guy who's dealt with it and this fixed it for me. Try at your own discretion although you don't have much to lose once your in hard brick territory I suppose.
Best of luck.
still don't recognizing my devices when i have windows 10 install and i hold volume down power
Look up Qualcomm QDLoader drivers for windows 10. Possibly called QCOM HS-USB Loader 9008 or something along those lines. If it's not even throwing an error just says waiting for device it's a driver issue not even being able to notice a device is plugged in.
Like I mentioned also make sure driver integrity enforcing is disabled and Enable test mode build 7601 if that's still a feature(s) that apply to windows 10.
i have anther issue it don't show ports on windows 10 after i install drivers
no port tab at all and i have the drivers install and it still don't recognizing my devices when i have the drivers install and i hold volume down power for 2Min and 1Min still nothing