Related
Is a sad day for me...i didn't knew about the Hardware Lock of Vibrants and i rooted and applied lag fix to my phone. After this i just updated the phone via Kies to JI6 then when phone rebooted got stucked after the second stage of booting with a blank screen. I tried many methods of get into Recovery or Download to flash again but can't because of Hardware Lock. Anyone knows if my problem have a solution?? Im very sad plz help.
Have you tried holding volume down and power until it boots?
Sent from my T-Mobile G2 using XDA App
Yah....Nothing!!
Try all methods:
http://forum.xda-developers.com/showthread.php?t=771247
I think you may need to use ADB commands to force it to reboot into download.
You may need to do method #4.
You may want to keep adb up and keep typing 'adb devices' to see if it sees the device when you try these different methods. If so - reboot into recovery from that.
You should be able to get into DL mode. Do you have ADB on your computer? If not, get it. Put it on the root of your C:\ and than make sure you get the drivers installed on your PC. Get ODIN and have it open. When that is done, connect your phone to your PC and boot it up. Open a cmd prompt (if you are in windows 7 you may need to open as admin) and navigate to C:\ (or where ever you decided to put ADB). At the command prompt type this exactly minus the parenthesis: "adb reboot download" Should shoot you right into DL mode. At that point you will need to flash a new ROM via ODIN, so make sure you read up.
Hope this works/helps.
I tried all that but cant get into recovery or download mode, my phone is not stuked on vibrant logo it just go to the second logo and then blank screen. Fabrication date is 08-10.
I tried unlocking the bootloader an atrix that was given to me about a month ago, and it had 3.4.6 (or something like that) and I couldn't find an unlocker for that version so I tried the one for the previous version, which failed at some point in the process and now it just boots to "Failed to boot 1". I've been trying every method I can find to try to fix this, I even bought the little red adapter to change any cable into a dev cable, and i know it works because if I power it on with the volume up key pressed it says "power reason: factory cable".
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
I tried it on several different computers with the same results.
Is this a hard brick? Any advice would be very much appreciated.
Did you install the windows drivers?
Scrub13 said:
Did you install the windows drivers?
Click to expand...
Click to collapse
Yea. I did.
Tekzel said:
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
Click to expand...
Click to collapse
If you power on while pressing volume-up, it should go straight to fastboot since it's the first option available. What happens when you reboot with volume-down?
Also, if the phone says "Starting fastboot protocol support" it's not hard-bricked, even if it's seriously screwed up at the moment. If it says "Entering NVFlash recovery mode," that's the point where it's toast (from the user end anyway).
With your phone in fastboot, does your computer recognize either of the SD cards? Have you re-downloaded the Motorola drivers, just to be sure? If "fastboot devices" comes back blank, then either the phone isn't truly in fastboot mode or the drivers aren't up to date.
Tekzel said:
I tried unlocking the bootloader an atrix that was given to me about a month ago, and it had 3.4.6 (or something like that) and I couldn't find an unlocker for that version so I tried the one for the previous version, which failed at some point in the process and now it just boots to "Failed to boot 1". I've been trying every method I can find to try to fix this, I even bought the little red adapter to change any cable into a dev cable, and i know it works because if I power it on with the volume up key pressed it says "power reason: factory cable".
I've tried RSD lite when connected with the adapter, but device properties stays blank. I tried loading an image and pressing start but nothing happens. The computer is seeing the phone but it says that it doesn't recognize the device. Also, if I start it with the volume up pressed it goes STRAIGHT to the fastboot protocol thing, I never get the option to choose RSD protocol. "fastboot devices" is just blank.
I tried it on several different computers with the same results.
Is this a hard brick? Any advice would be very much appreciated.
Click to expand...
Click to collapse
This isn't a hard brick:good:
when you boot your phone don't hold down the volume button, then hit the volume down button right when the menu comes up. Then just cycle through and hit RSD and that should do it
here is a thread specifically talking about fixing this issue http://forum.xda-developers.com/showthread.php?t=1528729
also, in the future I would recommend using this tool for unlocking and rooting your phone, it's no sweat, and this tool even has an automatic fix for your current problem. if I'm not mistaken..I'm not totally sure
here is the thread where the automatic BL unlocker came from, though the link there is broken http://forum.xda-developers.com/showthread.php?t=1182871
sheeparecurious said:
If you power on while pressing volume-up, it should go straight to fastboot since it's the first option available. What happens when you reboot with volume-down?
Also, if the phone says "Starting fastboot protocol support" it's not hard-bricked, even if it's seriously screwed up at the moment. If it says "Entering NVFlash recovery mode," that's the point where it's toast (from the user end anyway).
With your phone in fastboot, does your computer recognize either of the SD cards? Have you re-downloaded the Motorola drivers, just to be sure? If "fastboot devices" comes back blank, then either the phone isn't truly in fastboot mode or the drivers aren't up to date.
Click to expand...
Click to collapse
Powered on with volume-up it goes to:
Failed to boot 1
PwrReason: FACTORY_CABLE
Starting Fastboot protocol support
With power down (which I didn't know about), I see something flash on the screen really fast and then it goes blank. The computer recognizes it, but it still says "unknown device".
I recently downloaded the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
This machine is Windows 8, but I also tried it on a Windows 7 machine with the same result.
With the phone in fastboot, as above, it the computer doesn't see the internal storage, but it doesn't have an SD card in it, I will put one in it today and see what happens.
I've downloaded the above software fresh on each of the three machines I have tried this on, two Windows 8 machines, and one Windows 7.
Thanks for the suggestions, I really appreciate it.
thewarhawk said:
This isn't a hard brick:good:
when you boot your phone don't hold down the volume button, then hit the volume down button right when the menu comes up. Then just cycle through and hit RSD and that should do it
here is a thread specifically talking about fixing this issue http://forum.xda-developers.com/showthread.php?t=1528729
also, in the future I would recommend using this tool for unlocking and rooting your phone, it's no sweat, and this tool even has an automatic fix for your current problem. if I'm not mistaken..I'm not totally sure
here is the thread where the automatic BL unlocker came from, though the link there is broken http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
Great, I'm glad to know it's not hard bricked!
When I boot the phone with nothing pressed, it goes straight to a single line:
Failed to boot 1
I never get the menu. Also, just tried some presses of the button as it was booting up and found that I don't need to hold either power up or down. If I power it on, and when it stops at failed to boot 1, I can press the power up once and it goes to the fastboot protocol support screen or power down and the screen goes blank.
I'll check out the links you posted, thanks!
Failed to boot 1 should be the same as rsd mode.
Tekzel said:
Great, I'm glad to know it's not hard bricked!
When I boot the phone with nothing pressed, it goes straight to a single line:
Failed to boot 1
I never get the menu. Also, just tried some presses of the button as it was booting up and found that I don't need to hold either power up or down. If I power it on, and when it stops at failed to boot 1, I can press the power up once and it goes to the fastboot protocol support screen or power down and the screen goes blank.
I'll check out the links you posted, thanks!
Click to expand...
Click to collapse
As I understood you wanted to unlock bootloader and failed. So I suggest you to try automatized bootloader unlock tool(@thewarhawk give you link) and then fix the "Failed to boot 1" because if you failed something now you probably hard brick your device I have experience whit one of my atrix. So I in your situation will do that:
1) manually in fastboot (better in win7) fastboot oem unlock (I just doest know command for unique device id in fastboot so it need you to search in xda)
2) then flash fully system partition whit fastboot
3) and then if device doesn't boot correctly try this http://forum.xda-developers.com/showthread.php?t=1528729 as you early said @thewarhawk
Hi, the problem is the windows 8 drivers,First download this. Then you need to boot the phone in fastboot mode, then go in device manager then you will see fastboot with an exclamation mark. Right click on it and select update drivers. Next do search for a driver on my computer, Then you do choose from a drivers list (or something along those lines). Select ADB interface -> Motorola -> Mot composite ADB interface. You will get a warning, say yes anyway then bang... your phone is detected by adb and fastboot.
I'm having trouble with a bootloop issue on an ematic EGP010 (an apparently unpopular device - I am unable to find much detail at all about it
I've posted a video to show what is happening here:
As you can see I get the boot logo, then it appears to attempt to install an update, then it restarts and repeats the process.
I've attempted to get into a system recovery but every key combination I try doesn't work:
-vol up + pwr causes it to shut off as soon as the logo shows up
-vol down + pwr does nothing to the device itself, but will allow a computer to recoginze it via USB
I can get the computer to recognize the device, but because the EGP010 is cheap an unpopuplar, I was not able to find specific drivers for it. I was able to get the generic drivers installed, and its listed as "This device is working properly" however no devices are listed when I run "adb devices"
I'm at a loss for what to try next. Any suggestions for next steps or other things to try?
Generic Disclaimer: By doing any of the process listed below you accept complete responsibility over any of your actions, I will not be responsible if you end up causing hard brick, data loss or any kind of loss to your personal property.
Hii XDA fellows,
So I have seen many people asking for noob friendly guide to restore original oxygen os firmware or basically unbrick device. There are several thread on this already but trust me I have tried them all and in my case I had to use my own brain. So I have compiled a noob friendly guide which I,myself have used to unbrick my device.
small warning this will wipe all of your data.
Firstly I wants to thank Some_Random_Username for bringing up MSM Unbrick tool for OnePlus Nord. His guide to unrick nord is also fairly good enough but in my case I was stuck in bootloop after installing a rom. My phone was not even booting to Qualcomm EDL Mode so that I can use MSM Tool.
Lets start with pre-requisites:
You must have unlocked bootloader.
Original Oneplus Type - C cable.
Windows PC.
ADB debugging turned on your phone.
Firstly Switch off your device, which I think most of you have already have as the device is bricked but in case your phone is stuck in bootloop or recovery or bootloader menu itself then try holding down voume up button and power button together hold them down till you get heptic feedback and screen goes off. Let it be cool down for about a minute.
Now Setup your PC:
Download MSM tool to from this guide : Click here
Setup adb environment in your PC if you havent already setup follow this guide
Download Qualcomm EDL drivers from here: Click here
Now download Unofficial TWRP recovery by Mauronofrio from here
On your PC right click on start menu icon and start Windows Powershell(Admin) and type this command bcdedit /set testsigning on This will turn off driver signature verifications on windows you will be required to restart your pc now after you restart your pc will boot into test mode and you'll see a watermark stating the same in bottom left of your desktop. Worry not we will undo this after we have finished restoring.
install Qualcomm EDL drivers by running the setup listed above.
Unzip MSMTool there you will see a file named MsmDownloadTool V4.0.exe run it, it'll take some time but after you see a pop up asking for user type user name and password, Select other as user type and leave other stuffs blank as it is and click next.
In the next window, In the target button select O2 while using global tool or India while using indian tool or EU when using european tool.
Now you have to boot into Qualcomm Emergency Download Mode
You can do this in several diffrent ways but one I am listing here is recommended :
Boot into fastboot/bootloader mode by pressing and holding Volume up, Volume down and power button together when you see a Menu pop up on your screen you can let go all the fingers at once.
Now connect your phone to your PC and go to that folder where TWRP recovery is located. Hold Shift button and Right click inside that folder you'll see an option "Open powershell window here click on it. In the powershell window type
fastboot devices and press enter your device will be listed as fastboot devices in powershell window. Now type
fastboot boot twrp1.img press enter
your device will boot up in TWRP recovery in twrp recovery go to reboot section and select Edl, This will boot your phone Edl mode your screen will go off as soon as it happens in the MSM tool window you'll see a device listed as com3/com5/com7.
Click on start button the restoration process will begin. Wait for about 400 secs and your device will automatically boot up.
Voila you've successfully unbricked your phone.
If you want to exit from Driver test mode on your pc simply start a powershell window with admin rights and type
bcdedit /set testsigning off
and restart your PC.
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thanks!
peppanzer said:
So first off all i want to say thanks for this guide.
So , i have a problem with my phone getting reconized by my pcs, so, my Phone just works fine but i want to restore it to stock, i'm using aospex 8.3.
Since a few days my phone dosnt get reconzied by my pc, i've tried windows and linux, both installations cant find my phone, i tried diffrent pc's,usb cables, driver, new installations of windows and linux mint, other phones dont have this problem, tried resetting , everything, do you have a idea what i could try or could it be just my phone port thats damaged and cant transfer data anymore, if anyone has an idea i would really be happy about an answer , thank
Click to expand...
Click to collapse
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
IamAlok said:
Seems like it's a software issue probably a bug in your rom rich out to the developer he might help you, as you have tried both with Linux and windows i don't think it's a driver issue, it could be an issue with the hardware also but chances are pretty low for this to happen. Try flashing other roms if you have backup of your phone, use orange fox recovery it has an option of taking nandroid backup.
Click to expand...
Click to collapse
the thing is that i cant flash other roms, my phone dosn't gets recognized in fastboot, recovery and edl, so with the aex recovery installed i have no chance to change the rom without a pc, reached out to the dev but seems i'm the only person with the proplem, but thanks for helping.
The TL;DR is, I bricked my phone (TMo Nord N200 5G, SIM unlocked, Bootloader unlocked). I'm trying to use the MSM to recover it. I can't boot to EDL (hold down volume up and volume down at the same time, while pressing power or plugging a USB cable into my PC). It just boots to Fastboot when I follow that procedure. I can't get to a place where I can use ADB commands (ADB shows device "unauthorized").
Longer version, my stock phone was upgraded to the June patch level, I think.
I did the SIM unlock, unlocked the bootloader, and installed the drivers.
I successfully flashed the latest PHH squeak FOSS by following this guide but it had some quirks that I wasn't completely satisfied with.
I flashed a SparkOS GSI linked from somewhere else, but it constantly beeped at me after I disabled Google Play Services, so I decided to move on.
I think the next OS I tried was CRdroid from the same place, but I also replaced the boot.img with a stock one that was patched for Magisk. I can't remember why I thought this was a good idea. There was also a thread that said Magisk doesn't like having nothing in system_a so flash this blank partition using these commands. It always errored out, but I tried it before rebooting.
At this point, my phone would either boot to Qualcomm CrashDump on its own, or Fastboot if I held volume down.
Using the latest Fastboot Enhance I was able to get into fastbootd by switching to "A" active, then rebooting to fastbootd. Have to remember to switch back to "B" active to get anything else to work.
I've tried flashing a few different things since I can get to fastbootd now. I'm no longer booting into the Qualcomm CrashDump, it reliably boots to fastboot as long as I'm "B" active. I just can't get anything resembling a working OS.
I've tried flashing the OTA TMo with Fastboot Enhance a few different times, and a few different GSIs through fastboot, and I really want to get back to stock now so I can start all over.
I've also tried a couple different MSM tool versions, but since my phone is never in EDL, it's never recognized.
Thank you for any assistance.
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
scanman0 said:
Holding the Vol +/- & power WILL force boot the N200 to EDL mode regardless of the software corruption as this is at the hardware level.
The thing you need to be concerned with is that you have the latest Qualcomm ADB tools installed so msmtool will recognise the phone while in this mode.
Install the latest adb driver and go into that folder when typing the command as you might have older adb installed already at another location (and in the system path) that is running instead.
Android MTK - How-to Guide and Root Tutorials
Android MTK is one of the best websites that provides the latest Root Tutorial, USB driver, Android Tool, Stock Firmware and How-to Guide.
androidmtk.com
Then you need to have msmtool running and ready to begin and the mouse button hovering over the start button. As soon as the first logo screen comes up, it will only go into EDL mode for about 3-4 seconds and then move on to booting and dump you into fastboot if the rom is corrupt/missing. You need to watch msmtool on the first line and the second it shows up, click start and it will flash.
If you are still missing it and in fastboot I think the the N200 supports the force phone to edl mode by fastboot command:
fastboot oem edl
Click to expand...
Click to collapse
Thank you for responding!
The command fastboot oem edl is returning either:
FAILED (remote: 'Command not supported in default implementation')
FAILED (remote: 'unknown command')
I'm running fastboot version 33.0.2-8557947, it's not in my system path.
From a full power off, holding the buttons and plugging in the USB cable, it's about 5 seconds until I see the OnePlus logo, then 2 more seconds before I drop into Fastboot. I'm not sure what I'm looking for, to confirm EDL mode. I'm not seeing my Device Manager update in that time, and the MSM tool isn't displaying anything, either.
try insert cable then volume + and - and power. keep it holding for 10-15 seconds or till you see qualcomm device in device manager
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
try holding both volume buttons (make sure its off!) then plugging your phone in to the computer with msm tool open (you can pre-press the start button) (make sure you have all the drivers installed)
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
yrrebeulB said:
How can I verify that I have all of the required Qualcomm drivers installed?
I've run pretty much every driver install in this thread, or that I could find by searching, and it still seems like my laptop isn't recognizing the phone.
Click to expand...
Click to collapse
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Same issue as OP, won't boot into edl
edit: use USB 2.0
You can try enumusb.exe here: http://www.temblast.com/windows.htm
Code:
C:\>enumusb.exe /l /v05c6 /p9008
It will list the first time that a QUSB_BULK was plugged into a port, even if there was no driver found/loaded.
If you want, you can clear past connections by (needs to be admin command line):
This does no harm. I clear everything out occasionally, it just means that next boot will take 5 seconds longer while it discovers "new" devices and installs the same drivers.
Code:
C:\>enumusb.exe /d /v05c6 /p9008
Or, if you don't like that, just plug your device into a different port and see if another port is listed in enumusb.exe /l
On that same page you can find usblog.exe
You just run it and it will show you what pops up and down.
But, this only shows devices that Windows has loaded drivers for.
swee08315 said:
Open up Device Manager in windows. and then attempt to connect it to the computer while in EDL mode. In EDL mode it will still look like it's off btw, that confused me a lot.
You're looking for a device to show up in Device Manager when you connect it. If you're in EDL mode and have the driver's installed correctly it'll say qualcomm-something-something. If you see unknown device, you don't have the drivers installed. If no new device is detected either you're not in EDL mode or you should try a different cable.
Click to expand...
Click to collapse
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
I re-installed the Qualcomm driver bundle while my phone was plugged in and in EDL mode, and MSM finally worked! Thank you kind stranger! I'm back to factory now.
Thank you Strangers ,
yrrebeulB , all of you​
Ytube21 said:
qualcomm drivers
Qualcomm_Drivers_Setup.exe
drive.google.com
Click to expand...
Click to collapse
thank you
yrrebeulB said:
THANK YOU!
I didn't know there was a mode where it was powered on and the screen stayed off.
I finally got there by this path: Fastboot -> Recovery (I think?) -> List of languages, I chose English -> Power off -> Yes, really -> Hold down VOL+ and VOL- until I noticed the Qualcomm device in Device Manager
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
this line literally saved me hours
yrrebeulB said:
So I'm in EDL mode now! But my MSM tool crashes immediately on launch. So new problem, at least.
Click to expand...
Click to collapse
Try my native Windows EDL client. It uses the same Firehose loader as your stock tool does.
At the very least this will give you a second opinion.
http://www.temblast.com/edl.htm