I bricked my metro n200 5g and can't boot into EDL mode.
I can access fastboot and tried rebooting from there but it gave me an error saying "fastboot: usage: unknown reboot target edl"
How can i unbrick my phone?
red5815 said:
I bricked my metro n200 5g and can't boot into EDL mode.
I can access fastboot and tried rebooting from there but it gave me an error saying "fastboot: usage: unknown reboot target edl"
How can i unbrick my phone?
Click to expand...
Click to collapse
Hi red5815,
Are you certain you can't boot into EDL mode? Try the procedures below and let me know If you still can't enter into EDL mode.
Note: Make sure you have all of the necessary USB drivers installed (So your PC can recognize the connected device when it is connected to EDL mode)
First Method
Turn off your device
If you are in CrashDump Mode, I think you must hold down the power and volume up buttons for around 8-10 seconds (Until the screen goes off)
Then, hold down the volume up and volume down buttons simultaneously, and your device should enter EDL mode
While holding down both volume keys, connect your device to your PC via a USB cable
Your device should be recognized
Release the volume keys and press the "Start" button on MSM Tools (This will wipe your entire device, and if the bootloader was unlocked, it will relock it)
Second Method
Start MSM Tools and wait for the "waiting for device" message to appear (Before you start, keep in mind that this process will erase your whole device and relock the bootloader if it was previously unlocked)
Turn off your device and connect one end of the USB wire to your PC
Then connect the opposite end of the cable to your device
For a few seconds, press and hold the volume up, volume down, and power keys simultaneously
Your device should be recognized, and the flashing process should be started
Edit: Added proper warnings
pressing and holding the volume buttons only make it boot to fastboot.
red5815 said:
pressing and holding the volume buttons only make it boot to fastboot.
Click to expand...
Click to collapse
Hi red5815.
It takes a few attempts to get it right. Just make sure that all of the correct drivers are installed. Also, perhaps try using a different cable than the cord that comes with OnePlus Nord N200.
Without being connected to your computer, complete the button combination, and after a second or so, plug your device into the PC with MSM tools open (While still continuing the button combo). The screen will produce a momentary flash of black/green and it will ultimately connect to the MSM tool.
If that doesn't work, try this:
Open MSM tools and pick the appropriate parameters
Make sure your device is turned off
Connect the USB cord to your computer and then connect the other end to the OnePlus Nord N200 while holding the volume up and down buttons
It will then display the "connected" status in MSM tools for perhaps 2 or 3 seconds
Immediately click "start" in MSM tools (This will erase the whole device and relock the bootloader if it was previously unlocked)
Edit: Added proper warning
ive tried installing the drivers but i cant seem to get the qualcomm ones installed
red5815 said:
ive tried installing the drivers but i cant seem to get the qualcomm ones installed
Click to expand...
Click to collapse
nvm i had to get it from several different sites, its working now and unbricked!
red5815 said:
nvm i had to get it from several different sites, its working now and unbricked!
Click to expand...
Click to collapse
Red5815, great job! I'm glad you were able to get your device operating again.
Related
hi all,
i just want to see which bootloader i have on my 710, but combination VOL+ POWER then plug in USB doesn't work,
even tryed VOL+ VOL - / VOL+ VOL - POWER, i have the short vibration but as soon as i plug in computer, windows phone load.
i am with Win7 and my phone has been updated recently via Zune.
any advice ?
bootloader
what are you trying to achieve here are you trying to check which bootloader you have or try to flash a custom rom or even sim unlock the device
to get the phone into flash mode its vol + and then power short vibration then plug usb lead in the computer should then detect it. all fails get nokia care suite flash the old firmware that has the unlocked bootloader, you could also plug your phone in as normal then load nss and choose the osbl option then click the arrow that will force the phone into flash mode
rob :good:
thx for the info, i'm trying first to check which boot-loader i have, but i didn't install nokia care suite yet. that's probably why the computer doesn't find the drivers and the phone boot normally in windowsphone. maybe i will install a custom rom to be more comfortable. anyhow it was not simlocked...
Alright. Recently i bricked my lg V10 tmobile.
I was flashing part 1 and part 2 of eliminators* rom and i forgot that my bootloader was locked for some reason and well now i have a total brick. No power from device what so ever. Only thing I have going is that my pc revognizes the device as usb qualcomm 9008 so thats something.
I've tried the debrick method with the sd card but to no avail any ideas?
If you can get into fastboot... . Turn off hold volume+ and plug in USB from your computer. If that gets you into fastboot then do an LG UP upgrade
kaluna00 said:
If you can get into fastboot... . Turn off hold volume+ and plug in USB from your computer. If that gets you into fastboot then do an LG UP upgrade
Click to expand...
Click to collapse
Well i get no sort of boot up. I even tried " Fastboot devices " but nothing appears
take the battery out. then put the battery back in.
hold the (VOLUME UP) button and then plug in your USB.
https://forum.xda-developers.com/ve...ic-add-rootsystem-tot-vs990-tungkick-t3336345
follow this guide. remember to DL your variants TOT file. GL.
I want to root my phone ( Huawei Y6 Pro ), but I am stuck at, or atleast can't enter bootloader mode. After I turn off my phone I press the Vol Down button and then connect the usb cable to my PC and then some menu shows up completely in chinese and all it does is just inform me with the specs of the phone. A few months ago I had no problem entering bootloader mode, but now I can not.
Shimun said:
I want to root my phone ( Huawei Y6 Pro ), but I am stuck at, or atleast can't enter bootloader mode. After I turn off my phone I press the Vol Down button and then connect the usb cable to my PC and then some menu shows up completely in chinese and all it does is just inform me with the specs of the phone. A few months ago I had no problem entering bootloader mode, but now I can not.
Click to expand...
Click to collapse
You probably mean fastboot mode. You may enable USB debugging and type this in minimal ADB and fastboot:
adb reboot bootloader
Or you could try to press volume down and power for about 5 seconds and then you should connect the data cable.
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 seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.