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.
Related
I have a Kyocera Echo which has decided to forever loop in the start up instead of doing anything and since I can't hold power and volume down to factory restart I thought it was dusted
but if i read this thread correctly,
HTML:
http://forum.xda-developers.com/showthread.php?t=1129735
I might be able to do a hard rest through fastboot.
I have installed, all the drivers from the Kyocera website, I have the sdk, I know where to go into command prompt, etc. But my phone is not being detected by the fastboot tool. when I type Fastboot devices, I get nothing, not even the ? mark they mentioned and it just hangs on when I do fastboot -w saying it's waiting for the the device.
Even though its looping my computer will detect the phone and when I have placed it in what i think is download mood (power + plus both volume buttons) it has detected the right drivers to install and though it loops will kind of pop up the phone on my computer.
But when I put it it in what I guess is fastboot mode (power + volume up) Window's says it found new hardware, "Android," just plain android. I tried to direct to install the usb drivers from the Android-sdk/extras/ folder, but that doesn't work and Window is not finding anything automatically.
I assume the problem is that I need to find the right driver for the "Android," but I can't seem to figure what driver that is.
Or is it that my phone is not rooted, they didn't mention anything in the thread about needing it, but I'll admit I'm uncertain about that, but I assume I can't root it now anyhow or if that would even help.
Any help please?
Guys I'm not sure what the heck I did wrong, but I flashed a modem file linked earlier in the RR forum by another member in ALKA TWRP in an attempt to increase my signal strength , and it completely destroyed my device. No power on, No fastboot, no recovery, no EDL. Flashed a red LED on USB connection and shows as HS USB 900E. I guess I need to use test-point method to unbrick it?
My device was unlocked using official method, running latest Resurrection Remix, Radon Kernel, Alka TWRP 3.0. The modem flashed fine and didnt report any errors, but as soon as I hit the "Reboot System" button the phone completely died on me.
I see some other methods such as this : http://xda-developers-1.blogspot.ca/2016/04/unbricking-redmi-note3-from-hardbrickhs.html
I would prefer to use a method like this, but the tutorial is for other phones and a lot of the required files have been taken down
Any help?
What about this thread on MIUI?
I can't get into the proper fastboot mode or EDL mode
I tried using this method of disconnecting the battery and USB cables but it didnt work
http://en.miui.com/thread-274589-1-1.html
Getting into edl mode using the volume buttons is very tricky. Never managed it myself.
On thread you linked they say "press vol+ and vol- and connect the usb" where I have read before that you connect the power first and then quickly press both volume buttons.
http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/
Ive been trying that one but i keep getting into 900E mode instead of EDL mode every time
Warrimonk said:
Ive been trying that one but i keep getting into 900E mode instead of EDL mode every time
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Read here: http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
That Won't work because I cant reboot into fastboot. Step 2) Reboot into fastboot.
I guess you have to use testpoint method then. Just a tip for the future dont flash roms/zips unless they are confirmed to be legit/working.
Another site suggests a different method with the volume buttons.
Make sure you hold the phone in a way that you can comfortably press both volume buttons. Now press the Volume up (+) and Volume down (-) buttons simultaneously and connect the USB cable. The key of success here is timing. Make sure you press both volume buttons and the same time as pluging USB cable in.
Click to expand...
Click to collapse
http://xiaomitips.com/guide/how-to-unbrick-redmi-note-3-snapdragon-best-solution/
---------- Post added at 07:44 PM ---------- Previous post was at 07:22 PM ----------
Found the solution to get into EDL without volume button tricks.
[Tools, Tips & Tutorials] [kenzo]Entering EDL mode via Test Mode Screen
Who cannot enter EDL mode from standard Android boot and have no abilty to boot an image from FastBoot mode, you could try the following:
Switch the phone off.
Press and hold both Volume keys and Power key.
As Mi logo appears on the screen, release all buttons.
After several seconds, Test Mode Screen should appear (SYSTEM INFO, KEYPAD BACKLIGHT etc.).
Open Device Manager in Windows.
Connect the phone to the Windows computer (no matter which cable end is inserted first).
If ADB drivers are installed, "Android device" branch should appear in Device Manager, containing "Android Composite ADB Interface" and "Xiaomi Composite MDB Interface". Addionally, there should be "Portable devices" branch with "Redmi Note 3" device. If some drivers are not installed, install them.
Execute "adb devices" command to check if ADB connection is established.
If no devices are shown by ADB, wait a minute until "Redmi Note 3" device gets the "!" mark. Repeat "adb devices" command.
If "Redmi Note 3" device is not marked by "!" after a minute and ADB does not list the phone ID, try to disable "Redmi Note 3" in Device Manager.
As the phone ID becomes listed by ADB, execute "adb reboot edl" command.
Click to expand...
Click to collapse
Keep repeating "adb devices" until it reports connected.
Just tested and can report it works.
I did the test point method. It seems to be booting now
Warrimonk said:
I did the test point method. It seems to be booting now
Click to expand...
Click to collapse
What button combination eventually worked for you?
After putting it all togeather it seems the edge of the back caught my volume UP button and broke it /sigh
At least the phone is working now. Getting recovery booted and installed was a bit of a challenge. (fastboot boot recovery.img then copy new recovery and rom to device, flash everything at once)
Warrimonk said:
After putting it all togeather it seems the edge of the back caught my volume UP button and broke it /sigh
At least the phone is working now. Getting recovery booted and installed was a bit of a challenge. (fastboot boot recovery.img then copy new recovery and rom to device, flash everything at once)
Click to expand...
Click to collapse
you can buy replacement parts on aliexpress, if you need new vol button (or whatever part, ribbon cable ..etc, new battery's are $7).
ie:
http://www.aliexpress.com/item/Batt...sing-hongmi-note-3-back-case/32616561037.html
Does anyone know how I can update my baseband/modem using TWRP? My signal is still crap on RR ROM. I am afraid to flash another modem file which will risk bricking my device again. Or am I supposed to flash modem and then reflash the ROM?
Flashing in TWRP "should" be fine. Nor is flashing the Rom after needed because custom roms (9/10) don't touch these partitions on purpose. Now if ya using stock, that's different.
But I don't kno because I don't have the device yet (arrive Monday ). To eliminate risk, use ADB to flash the modem instead.
Again idk exactly what's going on with this device and it's methods yet.
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Wow that can't be good. I'm new to the oneplus stuff, normally I would say boot into recovery and reflash to stock but since we do not have roms yet I have a feeling your going to have to take it back to tmobile or oneplus and exchange it.
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Restore with hard reset or Recovery mode OnePlus Nord N200 5GRestore with hard reset or Recovery mode your OnePlus Nord N200 5G can solve problems that have not been solved with a normal factory reset.
1- First turn off your OnePlus Nord N200 5G completely. If you can not unlock the screen, press and hold the power button for about 20 seconds and the phone will turn off.
2- Keep holding on volume down and power keys together for a few seconds in your OnePlus Nord N200 5G. In some devices according to the Android version the combination can be the power key and the volume key up.
3- When the OnePlus logo is displayed, release the buttons.
4- Move through the menu with the volume up and volume down keys until you reach the “Recovery Mode” option and press the power button to access.
If the device menu appears in Chinese characters, click here to see how to reset a mobile in Chinese
5- Use the volume up and volume down keys to select the “wipe cache partition” option and press the Power button to activate the option and clear the mobile cache.
6- After a few seconds you will return to the previous screen, with the volume buttons go to the option “wipe data / factory reset” and press the power button to enter. A screen with many NOes and a YES will appear, with the volume keys again go to the YES and press with the power key.
7- After finishing again with the volume keys, click on “reboot system now” and press the power key of your OnePlus Nord N200 5G, the device will reboot and take several minutes to start while restoring the device to its factory state and optimizing the applications pre-installed in the system Android 11, OxygenOS 11.
Click to expand...
Click to collapse
edale1 said:
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Click to expand...
Click to collapse
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
fogles2021 said:
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
Click to expand...
Click to collapse
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
edale1 said:
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
Click to expand...
Click to collapse
I can only boot into fastboot, recovery just boots back to "your device is corrupt'.
I can connect usb but i can't find drivers for the phone, its connect as QUSB.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
edale1 said:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
Click to expand...
Click to collapse
I've installed these and it still comes up as qusb bulk.
Yeah, selecting recovery from fastboot goes to corrupt message, too.
Just going to make a aservice request.
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
daboross said:
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
Click to expand...
Click to collapse
Can u give me a link to platform tools, also..my computer is detecting the phone as QUSB BULK:"
From one of my other threads:
------
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
Click to expand...
Click to collapse
------
Basically, you need to manually update the drivers through device manager.
edale1 said:
From one of my other threads:
------
------
Basically, you need to manually update the drivers through device manager.
Click to expand...
Click to collapse
I can't get it to work...
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
From the first update drivers dialog (your phone should be in fastboot mode):
"browse my computer for drivers"
"let me pick from a list of available drivers on my computer"
"have disk"
And the drivers should be at
Code:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Once you select the .inf, you'll want to select this from the resultant list:
"Android Bootloader Interface"
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
Your phone is in EDL mode, also known as hard brick. It seems like the phone thinks both of your system partitions are empty or corrupt, as well as the bootloader is perhaps corrupt, due to which it is now gone to EDL mode as a last resort.
Typically, the only way to come out of it is to flash in EDL mode using MSMDownload Tool. Unfortunately for you, I don't see that Oneplus has released the MSMDownload Tool for the N200.
There are 4 things you can do at this stage.
1. If the phone is in return period, get it exchanged for another one.
2. Assuming the phone is under warranty, get it repaired under warranty
3. Wait for Oneplus to release the MSMDownload Tool for the N200. From past experience, Oneplus has eventually released it for every one of their phones. Once it is released, it is literally a 5 minute fix to get your phone to factory refreshed stage.
4. As a long shot, we can try to see if the bootloader is not corrupt, and if that is working, try to check if either of the 2 system partition is still intact, as @edale1 is suggesting above. Try the following
a. Press Volume Down+Power when phone is power off stage, and see if you can get the phone in fastboot mode.
b. Go to the folder when you have downloaded the Android SDK Toolkit. Alternately, search for the folder containing "fastboot.exe" on your hard drive. Open a command prompt in that folder containing fastboot.exe.
c. Run "fastboot devices" in the command prompt.
d. If you get a response of "no devices", then that means either phone is not in fastboot mode ( Go to Step a and repeat a,b,c until it is in fastboot mode) or bootloader is corrupt (nothing can be done other than Steps 1, 2 or 3 I have outlined above)
e. If you get a response of "XYZ fastboot" where XYZ is a random string/number, then bootloader is not corrupt. Proceed to Step f.
f. Type "fastboot getvar all" in the command prompt.
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device, either 'a' or 'b'
g. Follow @edale1's instruction above to change active partition to the *opposite* of whatever currently active partition e.g. if it says 'a' as the active partition in Step f above, then type in "fastboot --set-active=b" in command prompt, and vice-versa i.e. if it says 'b' as the active partition in Step f above, then type in "fastboot --set-active=a" in command prompt
h. If you get success in Step g, type "fastboot reboot" in command prompt, and keep your fingers crossed that it boots up normally. If not, that means both system partitions are corrupt. Follow Steps 1, 2 or 3 above.
Good luck!
fogles2021 said:
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Click to expand...
Click to collapse
No stock rom on oneplus/tmobile website
Im having a device corrupt error and cannot access phone anymore. Im trying to find the stock rom to flash with MSM tool but cantyfind it anywhere. You'd think oneplus would have it up on their website already. Anyone?
forum.xda-developers.com
Had the same problem, had to do a warranty replacement
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Ethanvio said:
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Click to expand...
Click to collapse
If you didn't enable OEM unlocking in developer options before you bricked your phone, you can't unlock those fastboot commands.
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