I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
ken.yong said:
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
Click to expand...
Click to collapse
I believe its v+/pwr when logo appears release both then press an hold v+ an hold it....chk YouTube if im wrong
Leofire_72 said:
I believe its v+/pwr when logo appears release both then press an hold v+ an hold it....chk YouTube if im wrong
Click to expand...
Click to collapse
Nope, doesn't work. Which Youtube link please?
Vol down + Power when connected to a charger/USB. You can get into fast boot by immediately hitting Vol up + Power after you see the clearly drunk/passed out green Android
I want the same answer but everyone here is a ****. No one knows how to enter brom mode in any android especially like oppo.
I hate those "press these three buttons while standing on your head" instructions.
It's probably my fault that I'm untalented.
The bottom line, any device will go to boot ROM if it can't make any sense of anything.
Irrespective of model, if you can defeat/confuse/muddle access to the flash memory it will go to boot ROM.
Ok, there may be simpler device-specific methods.
Rule #1: Don't short arbitrary things that you don't know what they are.
Rule #2: A 100 ohm resistor is logically as good as a short without risking anything melting down.
Rule #3 Try grounding test points near the flash memory through a 100 ohm resistor to ground.
Rule #4 Don't blame me for anything.
Renate said:
I hate those "press these three buttons while standing on your head" instructions.
It's probably my fault that I'm untalented.
The bottom line, any device will go to boot ROM if it can't make any sense of anything.
Irrespective of model, if you can defeat/confuse/muddle access to the flash memory it will go to boot ROM.
Ok, there may be simpler device-specific methods.
Rule #1: Don't short arbitrary things that you don't know what they are.
Rule #2: A 100 ohm resistor is logically as good as a short without risking anything melting down.
Rule #3 Try grounding test points near the flash memory through a 100 ohm resistor to ground.
Rule #4 Don't blame me for anything.
Click to expand...
Click to collapse
But I don't want to open my oppos back . Any other solution??
ken.yong said:
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
Click to expand...
Click to collapse
For what purpose you need to enter brom mode ?
You might be able to get there from ADB: adb reboot edl
You might be able to get there from fastboot: fastboot reboot edl, fastboot reboot-edl, fastboot oem edl...
You might be able to use an EDL USB cable (although I've never had any success).
You can short the proper EDL test points.
You can disable the flash by disabling a signal to it using a load resistor.
You can erase the SBL/XBL. If you do this and the EDL loader doesn't work you are seriously bricked.
Me, I use the proper EDL test points. I also hate opening devices. So I put in a magnetic reed switch so I don't ever have to again.
(The white connector is the root console, which goes out a hole in the back of the case.)
MohanTheMass said:
For what purpose you need to enter brom mode ?
Click to expand...
Click to collapse
Would like to root it. No customized roms though
ken.yong said:
Would like to root it. No customized roms though
Click to expand...
Click to collapse
Okay
ken.yong said:
I tried all 3 combo with the volume and power key to no avail. Any help will be appreciated!
Click to expand...
Click to collapse
I've only ever been able to enter BROM using Mtk client. Easiest in Linux but you have to go through the process of setting it up but once you do, you can pull the main partitions as well as unlock the bootloader (once oem is toggled). I could enter fastboot on my BLU View Mega but i could toggle OEM unlock and, using Mtk client, unlock the bootloader. Now to the steps:
(Assuming you've set it up)
1. Power off device and remove usb
2. Start Mtk client
3. Plug in usb while holding VOL - & VOL +
The client will automatically recognize the device, thus allowing you to pull, flash, unlock bootloader etc.
I've used this method to pull the boot from multiple mtk devices to repack inside twrp. The files pull as BIN but i just convert them to IMG. Well worth the setup for what it can do
KMerrimanJr said:
I've only ever been able to enter BROM using Mtk client. Easiest in Linux but you have to go through the process of setting it up but once you do, you can pull the main partitions as well as unlock the bootloader (once oem is toggled). I could enter fastboot on my BLU View Mega but i could toggle OEM unlock and, using Mtk client, unlock the bootloader. Now to the steps:
(Assuming you've set it up)
1. Power off device and remove usb
2. Start Mtk client
3. Plug in usb while holding VOL - & VOL +
The client will automatically recognize the device, thus allowing you to pull, flash, unlock bootloader etc.
I've used this method to pull the boot from multiple mtk devices to repack inside twrp. The files pull as BIN but i just convert them to IMG. Well worth the setup for what it can do
Click to expand...
Click to collapse
EDIT: I meant to say I could NOT enter fastboot on my BLU device, so I had to use the client to unlock the bootloader
MohanTheMass said:
For what purpose you need to enter brom mode ?
Click to expand...
Click to collapse
100% success pulling boot from multiple mtk devices (stock/unrooted) using Mtk Client to enter BROM. Also able to unlock bootloader and flash on devices that allow OEM unlock toggle but can't fastboot.
mtk client hardly gets a successful handshake on my device.
.....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
.....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
I want to use the below cmmand to force brom mode.
python mtk crash
But I need more light on arguments [--vid=vid] [--pid=pid] [--interface=interface]
before proceeding.
I also need asap more light on the risks involved in executing the command above.
@patrick7777777 did u ever figure it out? Im guessing ur on a tv as well like me im on a hisense 43a6h android 11 google tv and have some issues. I don't have oem unlock option on my google tv but id love to unlock the bootloader and root it and backup the stock rom. I can get it to reboot to fastbootd mode is what it says but it also says fastboot mode. Thats if i use a usb male to male in the usb port closest to the screen it has 2 usb 2.0 ports and if i type adb connect Android.local it connects if i have the adb drivers install but idk about the fastboot drivers and if I type adb reboot bootloader the tv turns off and wont turn back on via the remote or button on tv must reset the power to get it to turn back on idk if i can interface with it in bootloader mode but im sure i can in fast boot mode its just that the command adb reboot fastboot works in all but fastboot devices doesn't report any devices. Thanks
It's a Mediatek MT9612 chip inside.
Installed all requirements to run that python script?
Related
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.
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till developer option appear on setting. set enable usb debugging there. and try flash it again.
I can't get anything to start!
~~~~
...Well said:
]
---
~~~~I've try to reflash my device again, but then i couldn't be able to enter to flashmode
~~~~{ with the device off; press vol- and then connect to usb}
~~~~after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
~~~~then i activate dev mode: [usb debuggin and OEM UNLOCK]
~~~and try to get to fastboot mode, but the same results...
~~~~i got my device recognized by {ADB DEVICES}
~~~~but can't get fastboot
-----
.~~~~.. nothing wrong.... except well, i can't enter any -mode- now..
~~~~any help?
~~~~Thanks
Click to expand...
Click to collapse
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.[/QUOTE]
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
did you flashed hole ftf using flashtool or only the mencioned partitions above?
PiSpecialist said:
did you flashed hole ftf using flashtool or only the mencioned partitions above?
Click to expand...
Click to collapse
I still can't enter any-mode, so i haven't flash any ftf
me too
merwinaleman said:
I still can't enter any-mode, so i haven't flash any ftf
Click to expand...
Click to collapse
Same Here - is there no-one willing to help?!?
anyone know how to physically cause a device to self test, or reload defaults, ....or.... boot from sd by shorting a pin OR SOMETHING???
grrr - help:crying:
well... a little progress after 100s of reboot attempts!
i see a HD in the Device manager.
I can't access the disk, but it isn't constantly rebooting..
any one have a suggestion for my next move?
Error 7/24/2016 8:40:41 AM DeviceSetupManager 121 None
Device USBSTOR\Disk&Ven_SONY&Prod_Mass_storage&Rev_0310\YT9115VK6R&0 was configured.
Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.10586.0
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0006
Matching Device Id: GenDisk
Outranked Drivers: disk.inf:GenDisk:00FF2002
Device Updated: false
Parent Device: USB\VID_0FCE&PID_E1AD\YT9115VK6R
...still need help....
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
merwinaleman said:
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
Click to expand...
Click to collapse
dude... PLEASE tell me what mysterious, magical stuff happened?!?!!?!?!? I've been having exactly your issue for days now and can't get past it!!! Please
Ugh. I'm having the same problem. Magical stuff isn't very helpful :/
Boot loop
trechurch said:
~~~~
[~~~~QUOTE=shouqinz;67837866]try enable usb debugging. go to setting, about phone, then scroll to build number. tap it repeadly till ~~~~developer option appear on setting. set enable usb debugging there. and try flash it again.
Click to expand...
Click to collapse
Girlfriend tried to update her Sony Aqua M4 e2306...
she says that the boot loader was unlocked, and she installed the twrp update... and the root check came back rooted.... she powered off the phone and put it on a charger. ...
a few hours later she tried to restart it and only got the Sony Xperia screen then reboot loop.
I've spent 2 days reading everything that i can find and trying various solutions but most won't work because it won't stay connected long enough to use companion, adb, fastboot, bootloader, etc. When the devices is seen by pc it is only for a moment and comes up as a generic MTP device or a hard drive i can't open.
I can get the occasional green or blue lights and sometimes a generic battery symbol by powering off and pressing + or - with power, but never get a recovery or boot load screen... only alternating "sony Xperia" and darkness
also, Emily won't update.
I've tried multiple solutions using different versions of SDK, ADB, sony and xperia Companion, fastboot, bootloader, odin, pwm, and more on multiple machines from XP to Win10, but nothing seems to even make a dent!
I've removed the back and disconnected the battery for 2 hours and am currently trying to research a more physical hack/repair using riff jtag.
i see many people with "boot loop" issue , but no one seems to follow through and say how to get out if you don't have the option of booting to anything....[/QUOTE]
I have the same issue. I have an unlocked bootloader and booted with boot.img. everything was fine for a day or two, and when I started to factory reset my phone it is causing bootloop issues. sony logo and black screen. It never appears on my computer when connected to use adb. Any idea on how to fix this?
My mob is not able to flsh the stock rom......der s a error showing cannot open bundle....help me out plz
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Try this, jesus bless you
merwinaleman said:
Well, i've flashed the ftf file downloaded directly from xperifirm {E2306_26.3.A.0.131_R2C_Customized GEL_1294-3902}
-update-
some mysterious, magical stuff hapened and i entered fastbootmode
can boot recovery and boot.img from fastboot and now everything is fine
<3
thanks everyone
then, i've try to install root (following a tutorial for this device and this comp.) but i could not enter to FASTBOOT MODE
try using:
- (vol+) + (plug the phone)
-(power btn) + (vol+) + (plug the phone)
-(power btn) + (vol+) + (vol-) + (plug the device)
and the only thing that happened is: -Vibrate + sony logo ---> normal boot
----
Then i try to enter fastboot using the adb command {ADB REBOOT-BOOTLOADER}
but it just reboot normally (sony logo and then start normally)
[[ADB do recognize my device and all drivers were properly installed; but can't enter to fastboot mode]]
---
I've try to reflash my device again, but then i couldn't be able to enter to flashmode
{ with the device off; press vol- and then connect to usb}
after several attempts using - [(power btn) + (vol-)] i entered flashmode and reflash my device...
----
then i activate dev mode: [usb debuggin and OEM UNLOCK]
and try to get to fastboot mode, but the same results...
i got my device recognized by {ADB DEVICES}
but can't get fastboot
-----
Then the user who's helping me told me to reflash using this config
[in excludes section check all except AMSS_FSG, AMS_FS1, AMS_FS2,BOOT DELIVERY, KERNEL. Don't check anything else.]
But i can't get flashmode now... i try all the combinations, try in ubuntu 16, and windows 10... but nothing
the device starts normally nothing wrong.... except well, i can't enter any -mode- now...
any help?
Thanks
Click to expand...
Click to collapse
1. Turn off OEM Unlock
2. Keep USB Debugging on
3. Enter Fastboot mode
4. Done
5. Jesus Bless You
Thymue said:
When i do VolumeUp & connect my phone it connects to windows with blue led on phone and after ~6 seconds it just disconnects and shows battery charging thing
Click to expand...
Click to collapse
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
iFlashed said:
I'm having the same issue.
Anoyone knows how to fix? Maybe is a problem of the cable?
PD: Tested with official cabled and turning Off OEM unlock and still the same.
Click to expand...
Click to collapse
also for me :´(
Thales720 said:
also for me :´(
Click to expand...
Click to collapse
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Hi7m3up said:
Not sure what your problem is exactly but it is most likely a problem with the cable or the s1 driver's(if your using window's?) one or the other ,
However i need to point out that you must have your OEM lock at the SWITCHED ON position(allow the device to be oem unlocked) or you will trip the frp at the next reboot and will have to reflash your firmware unnecessarily , so to sum up Oem unlock at the switched on position
Click to expand...
Click to collapse
the drivers are all installed correctly, I tried doing this with the OEM off and on and it did not work
none of the methods works, adb does normal boot
recovery reboot (and other apps) crash or boot normal too
volume (+) and power button only makes the phone vibrate (and sometimes the Sony logo appears)
I can't stress to you enough that Enable Oem need's to be on the "on position" so switch it on (allow the device to be oem unlocked)and leave it alone it's nothing to do with you not being able to get to fastboot. If you trip the frp on your phone you will not be pleased.
with that said with your phone switched on and USB DEBUGGING SWITCHED ON plug into your usb on computer open a command window and input the following command- adb reboot bootloader you will now see your blue light on the phone this means your sony is now ready for you to flash a custom recovery (assuming you have unlocked your bootloader ?)
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.
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
!!! Whatever you do, it is at your own risk !!!
This procedure will unbrick any Axon 7, returning it to stock. It fixes any kind of brick as long as your hardware is not damaged. You can't damage your hardware using software so if you have a healthy unit, you can recover it from any flashing "accident".
1. GET THE SOFTWARE
You need a Windows PC, Windows 10 is highly recommended. Do this:
01. Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
02. Download the EDL flashable stock firmware package for your model:
A2017 (China): B14_MIFAVOR5 Android: 7.1.1
A2017G (Europe): B10_NOUGAT Android: 7.1.1
A2017U (Americas): B35_NOUGAT Android: 7.1.1
03. Unzip the firmware ZIP file to a folder in your hard drive.
2. ENTER EDL MODE
Option A: USING THE REBOOT COMMAND
If you still have access to your system but not to recovery or fastboot, then you just need to install any terminal app, open it and at the app's command prompt enter:
Code:
reboot edl
. You device will reboot into EDL mode. Now you can safely plug your Device to your computer. In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you'll need to explore the next option.
Option B: USING THE BUTTON COMBO
04. Press the VolUp and VolDn buttons in your device and keep them pressed.
05. Now press the power button until the red LED flashes, it does it really quick. Then release the buttons, starting by the power button.
06. Plug the device to your computer.
In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you need an EDL cable.
OPTION C: USING THE EDL CABLE
So, you need to get a Qualcomm EDL cable. With it you can recover from any situation. I use this one, DrakenFX uses this other model. There are cables out there not working properly so do not try to save 4 or 5 bucks and get yours from a reliable source. Alternatively you can solder your own by following this guide. If you are in an emergency (or your patience threshold is very low) and have a thin wire around you, then you can follow this DIY hack video.
Do you already have the EDL cable? then follow these steps:
07. Connect your bricked Axon 7 to your PC using the EDL cable.
08. Press the EDL cable button and keep it pressed.
09. Press the Power button of your bricked unit and keep it pressed too.
10. Wait 20 seconds.
11. Release the power button.
12. Wait 10 seconds.
13. Release the button of the EDL cable.
Voilà, your device is now in EDL mode. The device manager in your PC, under the ports category, should detect it as Qualcomm HS-USB QDLoader 9008. Now you can proceed to the flash section. If this procedure doesn't work, then your unit could have a hardware problem. Your only hope is to dissemble it by following this last resort guide.
3. FLASH FIRMWARE
14. Open MiFlash in your computer.
15. Click Browse button and select the folder you created in step 03 with the stock firmware files.
16. Click Refresh button and your device will appear listed as virtual COM port.
17. Click Flash button and wait for a few minutes until it finishes. Note that the bottom options are not applicable.
18. Now you have a stock Axon 7. Your data partition will still have garbage data, so you should enter recovery by pressing VolUp while rebooting your device with the power button. Release VolUp only when you reach Recovery. Using Recovery do a Factory Reset of your device.
That was the last step. Hopefully now you have a fully functional stock Axon 7.
By the way, this guide can also be used to return to stock any working device for selling or service!!!!
Cheers!!!!
Nice! I just disassembled mine and did it that way the other day.
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
@Oki
Thnx for this guide :good:
Find the latest A2017G N-B10 here
Harmtan2 said:
Nice! I just disassembled mine and did it that way the other day.
Click to expand...
Click to collapse
Glad to see you solved your issue.
mb0 said:
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
Click to expand...
Click to collapse
I don't know what you mean about converting an A2017 into an A2017U. They are the same device except for the radio, that that's a hardware difference. You should always use the right modem firmware for your radio hardware so you should use the A2017 modem firmware. After unbricking your unit, you can unlock it again and flash any universal firmware the same way you did before. It is a long but safe process.
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
mb0 said:
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
Click to expand...
Click to collapse
If you flashed the A2017U radio in a A2017 hardware and worked fine for you, then you can use the A2017U B35 stock firmware.
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
My phone shows up as Handset Diagnostic Interface (DFU) (COM3) but it doesn't get detected on Miflash program......
aLexzkter said:
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
Click to expand...
Click to collapse
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Oki said:
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Click to expand...
Click to collapse
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3).
Edit: I managed to get into EDL mode thanks to Axon 7 EDL Tool but I got a "File analysis: error" "not important files found" so I went back to MiFlash and also got an error about the files. Will update the post when I get it to work.
aLexzkter said:
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3)
Click to expand...
Click to collapse
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Oki said:
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Click to expand...
Click to collapse
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
aLexzkter said:
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
Click to expand...
Click to collapse
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Oki said:
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Click to expand...
Click to collapse
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
aLexzkter said:
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
Click to expand...
Click to collapse
Well, I am considering to link the older Marshmallow ROMs since the Nougat ROMs have some issues with fastboot. Anyway. It is going to take some time to test the alternatives. Thanks for letting us know!
Some of the most recent firmware for Axon 7 (@NFound's B12 bootstack, I think) doesn't support the EDL button combo. But if you have TWRP installed, you can boot to recovery, then reboot to EDL from there.
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Flogisto said:
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Click to expand...
Click to collapse
There ate several ways to remove that. One involves TWRP 3.2.1-7 and the other Axon 7 EDL tool, if you dont have TWRP then use the second . Jusy go to the unlock menu and apply the google unlock.
A third way would be to setup the phone with your old google account and do afactory reset from within Android, not from the bootloader. That would remove also the owner safety.
Thank you so much for your guide and software bundle.
I even had to make a EDL cable to restore my device.
After flashing, I do not see vendor as a partition but looks like it is a folder. Is it OK for future ROMs ?
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