Related
Hello my friend just made an update of his phone which is a redmi 3 pro
His little bro shutdowned the phone while update was in process. The result is that now the phone have a bootloop, can't access the recovery (blackscreen when trying) and have a locked bootloader.
So I am not sur how to unlock the BL if I can't install a dev rom and can't boot. Not sur how to get into the recovery with the 2 same problems.
Could anyone help me for this one? Which is hard to me.
Thanks
PS: I tried to do something with unpacking boot and remove a ",verify" thing in the ramdisk but I guess I'll need the unlockedbootloader to flash the new boot.img?
Kicroy said:
Hello my friend just made an update of his phone which is a redmi 3 pro
His little bro shutdowned the phone while update was in process. The result is that now the phone have a bootloop, can't access the recovery (blackscreen when trying) and have a locked bootloader.
So I am not sur how to unlock the BL if I can't install a dev rom and can't boot. Not sur how to get into the recovery with the 2 same problems.
Could anyone help me for this one? Which is hard to me.
Thanks
PS: I tried to do something with unpacking boot and remove a ",verify" thing in the ramdisk but I guess I'll need the unlockedbootloader to flash the new boot.img?
Click to expand...
Click to collapse
I have the similar problem with my Redmi3. The Fastboot screen is the only screen that I can get now. Let me know if you have answer. Thanks.
If you can acces fastboot then just connect the phone to computer in fastboot and enter fastboot oem edl in cmd (maybe you will need Minimal ADB and fastboot to do it). Then flash official ROM via MiFlash.
ohoh seems interesting then it won't say couldn't verify or smthg? will tell that to my friend asap, thanks
EDL mode allows flashing with locked bootloader. Some models have this mode locked, but I think that is not the case with Redmi 3.
Kicroy said:
ohoh seems interesting then it won't say couldn't verify or smthg? will tell that to my friend asap, thanks
Click to expand...
Click to collapse
to go to edl mode just turn off your phone.plug the cable to your laptop or desktop but not to your phone.now be ready to press both volume up and down button as you plug the usb cable to ur phone.immediately after inserting the usb cable press both volume buttons at the same time.it should vibrate and go to edl mode.edl mode appears in black screen so to know if its in edl mode or not open miflash and click refresh ,your device should be shown as com10,20 or com something like that .once you go to edl mode you know what to do if you have used miflash to flash roms.hope this helps you.
jokerpappu said:
to go to edl mode just turn off your phone.plug the cable to your laptop or desktop but not to your phone.now be ready to press both volume up and down button as you plug the usb cable to ur phone.immediately after inserting the usb cable press both volume buttons at the same time.it should vibrate and go to edl mode.edl mode appears in black screen so to know if its in edl mode or not open miflash and click refresh ,your device should be shown as com10,20 or com something like that .once you go to edl mode you know what to do if you have used miflash to flash roms.hope this helps you.
Click to expand...
Click to collapse
I have a problem with my redmi 3. It makes reboot and it does not charge if its not closed.
Can you help me to fix or do you now where i can find a solution.....
geuthym said:
I have a problem with my redmi 3. It makes reboot and it does not charge if its not closed.
Can you help me to fix or do you now where i can find a solution.....
Click to expand...
Click to collapse
Well about that i dont know.but your best bet to solve it is by changing the software.if that does not helps then you should take your device to a technician for repairing.
jokerpappu said:
Well about that i dont know.but your best bet to solve it is by changing the software.if that does not helps then you should take your device to a technician for repairing.
Click to expand...
Click to collapse
When i bouht it the software it was unnoficial then i put with miflash the china dev. All the problem start when i make updates apps and the android web view.
geuthym said:
When i bouht it the software it was unnoficial then i put with miflash the china dev. All the problem start when i make updates apps and the android web view.
Click to expand...
Click to collapse
try flashing official global rom then see if the problem still persists or not
Hey! I am back with some news of my friend!
He tried to run the EDL mode but when he does that the phone simply goes into the bootloop again... He asked a vendor from Aliexpress to get a french rom, is there a way that the phone doesn't have EDL because of the rom or something like that? I mean is EDL a hardware-thing or a software-thing
same problem
cukru said:
If you can acces fastboot then just connect the phone to computer in fastboot and enter fastboot oem edl in cmd (maybe you will need Minimal ADB and fastboot to do it). Then flash official ROM via MiFlash.
Click to expand...
Click to collapse
I have same problem, but this way is not work, because bootloader is locked. Im forget for replacing recovery.img in update package with twrp.
I had this problem before few monthes
my solution was to "force" putting this device on EDL mode
I clicked on vol up + vol down + power together and got into EDL mode, then miflash it.
google - xiaomi understanding download mode
it will send you into miui forum
then second method, download mode, it is what I've described
So, i installed Xposed, and like many people, i got stuck in the logo... No big deal there... Went to look for some help, and it said to go to fastboot, so I went, but it got stuck in the fastboot logo. Then I connected it to the computer and when I try to list the ADB devices I Ialways get an error saying the server is outdated...
I really need some help! I can't find anything online to help me!
Thanks in advance!
Edit: I submitted a bootloader unlock request to Xiaomi earlier today, but I can't see if its approved or not because phone doesn't work
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
nishant2222 said:
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
Click to expand...
Click to collapse
I tried, but i cant seem to go to edl mode through fastboot, any tips? and because of bootloader lock i cant flash fastboot rom with MI Flash
Edl mode needs a specific fastboot version.
For the Redmi Note 3 Pro / Special Edition
Download and extract this package on your PC.
Enter fastboot mode by holding Power and Vol- at the same time. Wait until the Mi Bunny appears, then connect the phone to the PC.
Run reboot.bat in the extracted package. A command prompt will appear. Press a key to reboot the phone to EDL mode.
Upon entering EDL mode, the screen should turn blank. The notification LED might be blinking red. Done.
To get out of EDL mode, hold the Power button for about 10 seconds.
Click to expand...
Click to collapse
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
corkiejp said:
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
Click to expand...
Click to collapse
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
KaiZix said:
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
Click to expand...
Click to collapse
Mate, watch any video on YouTube. You're not understanding from text instructions.
AtomR said:
Mate, watch any video on YouTube. You're not understanding from text instructions.
Click to expand...
Click to collapse
Can't find any... Recommendations?
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
corkiejp said:
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
Click to expand...
Click to collapse
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
KaiZix said:
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
Click to expand...
Click to collapse
Installing Mi Flash should have put the correct drivers on your PC.
But can be got from here: - https://xiaomifirmware.com/downloads/download-pc-drivers-xiaomi-redmi-note-3/
And I already linked adb/fastboot tools.
IF your comfortable opening your device, there is also a test point method you could try.
http://en.miui.com/thread-244814-1-1.html
Could not find a English video, so maybe try googling more and you might find one.
If not, you could ask at local repair shop, if they would fix it for you. Using Cable/ TP method.
Note for other readers:- MIUI roms need a special version of xposed, for it to work. And installing from an app would more than likely would have use the wrong version. Should never be done on a locked bootloader, only asking for trouble. (Rovo89 is currently trying to bring MIUI support to the official version for nougat roms)
Edl Mode locked
I've read that in some instances Edl mode isn't accessible via button combo or adb.
I had this happen and thankfully help is at hand.
The Edl tool by @djkuz
Has the answer, Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
OK to fix this
Download and install to your PC or laptop
Run this from the root directory drive C: or D:
Make sure all drivers are up to date
Open the app, Run as admin.
Boot your phone into FTM.
Turn your phone off.
Press and hold Vol dn + power till you see the FTM screen.
Plug your phone into PC or laptop and follow the on screen instructions.
Then select unlock > then Edl fix.
Let the app run.
When finished you should have a working Edl again
Just boot into FTM and follow instructions in edltool.No need to use Unlock EDL Fix
Predatorhaze said:
Just boot into FTM and follow instructions in edltool.No need to use Unlock EDL Fix
Click to expand...
Click to collapse
Yes, edl does work via the app. Edl fix is to return the button combo.
Here is a reply from @sToRm1nG thank you
"Thanks for your reply, I stumbled upon your thread before I guess but wasn't sure if this is gonna help me."
"Unfortunately, I am not able to get into FTM..."
"However, I am able to boot into EDL mode, so do you think the EDL fix will also work if I am in EDL mode?"
*EDIT*
"I tried it and it worked!"
"Thank you so much for your input!"
Click to expand...
Click to collapse
Hopefully this can help others
So by now most of you have seen the DFU MultiDL tool by @raystef66 only you had to switch from Multi tool to Miflash or Edl Tool.
I have worked out how to get Edl working in this tool.
First of all this tool was designed to run on Windows 7 so in Windows 10 it didn't seem to function properly.
So I set it to Windows 7 compatibility first off to see if it would work.
I had better results with phone detecting and saying connected instead of disconnect.
Next the phone needed to be booted into FTM mode if you are just flashing an Edl package, if your phone is in DFU it skips this step as per the instructions below.
Next I found it was better to place the Edl package within the MultiDL tool folders.
C:\program files > DFU MultiDL tool > DA > SMT > firehose and overwrite the exsiting firehose file.
Pics posted below show instruction (tranlated from Chinese to English) and MultiDL tool in flashing progress (sorry they are not very clear)
I hope this helps
I am trying to relock my bootloader to send my phone in for a warranty replacement, but EDL mode is disabled because I'm on B35. Can I use this tool to achieve that? I'd appreciate any help...
parmar.saab said:
I am trying to relock my bootloader to send my phone in for a warranty replacement, but EDL mode is disabled because I'm on B35. Can I use this tool to achieve that? I'd appreciate any help...
Click to expand...
Click to collapse
Boot your phone into FTM mode to start the process, it should switch to Edl mode.
This tool won't lock the bootloader, however some Edl packages will have a locked boot image.
If your Edl is still locked try the Edl tool by Djkuz.
Start Edl tool as admin, boot into FTM to start, follow the on screen instructions then unlock then choose Edl fix.
You may be able to lock the bootloader with Edl Tool or use the Axon 7 tool kit to relock.
I hope this helps
Syberclone said:
Boot your phone into FTM mode to start the process, it should switch to Edl mode.
If your Edl is still locked try the Edl tool by Djkuz.
Start Edl tool as admin, boot into FTM to start, follow the on screen instructions then unlock then choose Edl fix.
I hope this helps
Click to expand...
Click to collapse
This is the error I get in the EDL tool:
parmar.saab said:
This is the error I get in the EDL tool:
Click to expand...
Click to collapse
I can't get the pic to show properly, what is the error?
Make sure you have the Edl tool in the root directory of the drive.
Eg: C:\ or D:\ for it to operate properly.
Can you boot to FTM?
parmar.saab said:
This is the error I get in the EDL tool:
Click to expand...
Click to collapse
What happens if you use the key combination? Hold Vol+, Vol- and power. If there's a constant red LED then you're on DFU. Right after just use this tool and you'll get to EDL
But I don't get it? If you want to relock the bootloader, you'll have to roll back to B19. If you'll do so just flash the stock recovery and use a B19 package from ZTE US
Choose an username... said:
What happens if you use the key combination? Hold Vol+, Vol- and power. If there's a constant red LED then you're on DFU. Right after just use this tool and you'll get to EDL
But I don't get it? If you want to relock the bootloader, you'll have to roll back to B19. If you'll do so just flash the stock recovery and use a B19 package from ZTE US
Click to expand...
Click to collapse
Here's my situation:
I have an A2017U, that was initially running 15.1 and developed an issue that requires me to send it in for a warranty exchange. I found a thread to return it to stock, which left me on B35 stock with TWRP still intact. However, my bootloader if still unlocked, and I need to relock it before sending the phone in. I am somewhat of a noob when it comes to this, but what exactly would I need to do in order to relock the bootloader? I'd greatly appreciate it if you could point me in the right direction.
parmar.saab said:
Here's my situation:
I have an A2017U, that was initially running 15.1 and developed an issue that requires me to send it in for a warranty exchange. I found a thread to return it to stock, which left me on B35 stock with TWRP still intact. However, my bootloader if still unlocked, and I need to relock it before sending the phone in. I am somewhat of a noob when it comes to this, but what exactly would I need to do in order to relock the bootloader? I'd greatly appreciate it if you could point me in the right direction.
Click to expand...
Click to collapse
well, as a first you could respond to my question ?
If you can get into EDL by the key combination, then you're done. Just use a B19 EDL package to go back and you'll have fastboot there. After that, run the command to relock
Choose an username... said:
well, as a first you could respond to my question
If you can get into EDL by the key combination, then you're done. Just use a B19 EDL package to go back and you'll have fastboot there. After that, run the command to relock
Click to expand...
Click to collapse
That's the problem, the key combination doesn't work to get the phone into EDL mode (I'm guessing it's because it is disabled on B35). In essence, I don't have fastboot access. I tried relocking in FTM but get the error as shown in the picture.
parmar.saab said:
That's the problem, the key combination doesn't work to get the phone into EDL mode (I'm guessing it's because it is disabled on B35). In essence, I don't have fastboot access. I tried relocking in FTM but get the error as shown in the picture.
Click to expand...
Click to collapse
still you don't really respond. What HAPPENS when you use the key combination? Does it reboot? Does it stay black and show a red LED? Black with no LED?
Anyways, you can enter EDL simply by enabling adb and issuing "adb reboot edl" from the system. (or from FTM). it just seems weird that it would reboot, because usually the phone just goes into DFU when you use the combination
When I use the button combination, the phone shows a blank/black screen with a solid red notification light. However, I get no response on any commands from the Axon 7 Toolkit.
@Syberclone: Thanks for the recommendation to run the tool in Win7 compatibility mode, I have Windows 10 and the tool always shows as disconnected. I can use the tool to switch from DFU to EDL, no problem, but could never figure out how to use it to flash an EDL.
I'd like to point out that FTM isnt accessible if you're not running a stock-based ROM. In all my tests I was never able to boot into FTM on custom ROMs like LineageOS, AOSP Extended, etc.
However, if you can boot directly into EDL with the buttons, or can use this tool to switch from DFU to EDL, then access to FTM doesn't matter.
@parmar.saab: A black screen with a solid red light is DFU mode, you need to use the DFU MultiDL Tool to switch from DFU to EDL. EDL is a black screen too, but has a red light that will turn off if you use the button combo. In other words, it will blink rather than staying solid. Then you can use the Axon 7 Toolkit or Axon 7 EDL Tool to flash an EDL. Or you might be able to flash with the DFU tool, if you can get it to work.
@AnonVendetta No problem
It took me a while to work it out, a bit over 2 hours of testing and retesting using my Axon.
I didn't want to put it in to DFU to do a full test, however it worked a treat once I got it sorted.
FTM was as per the Chinese instructions not actually mine, apparently if the phone is in DFU the app will work accordingly.
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