Related
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
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.
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
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot.
I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore.
I can boot it in fastboot mode but flashing in normal fastboot mode doesn't work with locked bootloader and lenovo rescue tool can't help me either.
Edit: Weirdly I managed to boot it up and it shows as a "motorola edge 30 pro" and I can control my screen with a USB mouse.
But when I try to enable "OEM unlocking" in developer options the settings app just crashes.
But my problem stays the same, i'm still stuck with a locked bootloader
Is there any chance to trick this phone into EDL mode or any working blankflash?
Any suggestions? i'd appreciate it
jody2k said:
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot.
I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore.
I can boot it in fastboot mode but flashing in normal fastboot mode doesn't work with locked bootloader and lenovo rescue tool can't help me either.
Edit: Weirdly I managed to boot it up and it shows as a "motorola edge 30 pro" and I can control my screen with a USB mouse.
But when I try to enable "OEM unlocking" in developer options the settings app just crashes.
But my problem stays the same, i'm still stuck with a locked bootloader
Is there any chance to trick this phone into EDL mode or any working blankflash?
Any suggestions? i'd appreciate it
Click to expand...
Click to collapse
It doesn't matter if the oem lock is on to flash the stock firmware.
You can directly flash the right firmware via fastboot. Lenovo rescue tool may not flash...
cascade128 said:
It doesn't matter if the oem lock is on to flash the stock firmware.
You can directly flash the right firmware via fastboot. Lenovo rescue tool may not flash...
Click to expand...
Click to collapse
Hi thanks for the response, how to flash directly stock firmware? which method should I use? This is what I get when I try to flash anything through adb (phone in fastboot mode) I added a screenshot from adb in windows and took a picture from my phone to show in which fastboot mode it shows.
Tried several things flashing directly from adb but it always says permission denied because of the bootloader lock, maybe i'm doing something wrong.
It's not adb, it's fastboot mode.
Where you are is right.
It will be in the mode in the screenshot of the device, that's right.
Use the one in the file i gave you.
Here are the guidelines.
01. Download the latest Firmware from lolinet
02. We extract the firmware.zip, open servicefile.xml and copy the contents into this website
03. Download the mfastboot.rar ADB i gave and put it in the rom folder you extracted.
04. We put the flashfile.bat we created (Step 02. Extract, open servicefile.xml and copy the content to this site) into the rom folder you extracted.
05. Reboot your phone into fastboot (adb reboot fastboot or press and hold Power + Volume Down)
06. Everything is ready, click on the ''flashfile.bat'' file.
07. Don't disconnect the phone until the update has finished.
cascade128 said:
It's not adb, it's fastboot mode.
Where you are is right.
It will be in the mode in the screenshot of the device, that's right.
Use the one in the file i gave you.
Here are the guidelines.
01. Download the latest Firmware from lolinet
02. We extract the firmware.zip, open servicefile.xml and copy the contents into this website
03. Download the mfastboot.rar ADB i gave and put it in the rom folder you extracted.
04. We put the flashfile.bat we created (Step 02. Extract, open servicefile.xml and copy the content to this site) into the rom folder you extracted.
05. Reboot your phone into fastboot (adb reboot fastboot or press and hold Power + Volume Down)
06. Everything is ready, click on the ''flashfile.bat'' file.
07. Don't disconnect the phone until the update has finished.
Click to expand...
Click to collapse
Hi thanks for helping me, I downloaded the right firmware, uploaded the servicefile.xml to the site you gave me and created the flashfile.bat. Pasted the flashfile.bat into the samen folder as the rom and also extracted the mfastboot.rar into the same rom folder.
Then clicked on the flashfile.bat but sadly I get the same error's (Permission Denied)
My phone is still in fastboot mode (right screenshot)
Any idea's?
jody2k said:
Hi thanks for helping me, I downloaded the right firmware, uploaded the servicefile.xml to the site you gave me and created the flashfile.bat. Pasted the flashfile.bat into the samen folder as the rom and also extracted the mfastboot.rar into the same rom folder.
Then clicked on the flashfile.bat but sadly I get the same error's (Permission Denied)
My phone is still in fastboot mode (right screenshot)
Any idea's?
Click to expand...
Click to collapse
Very interesting, it shouldn't give such an error. You are flashing Motorola signed images, you don't need the bootloader unlocked for this Sorry i can't be of more help, i hope you can recover your device...
cascade128 said:
Very interesting, it shouldn't give such an error. You are flashing Motorola signed images, you don't need the bootloader unlocked for this Sorry i can't be of more help, i hope you can recover your device...
Click to expand...
Click to collapse
Yea indeed well thanks anyway, my only hope left is a third party recovery tool that supports this phone in future.
I'll put the X40 in my closet until then and buy another new phone in the meanwhile don't have much of a choice lol.
Hello!
Did you try RSDLite tool to flash firmware?
thunderman75 said:
Hello!
Did you try RSDLite tool to flash firmware?
Click to expand...
Click to collapse
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work with this phone in normal fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
jody2k said:
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
Click to expand...
Click to collapse
This looks promising:
Motorola Unbrick Tool: Unbrick any Moto Device via EDL Mode
In this comprehensive guide, we will show you the detailed steps to unbrick any Motorola device booted to EDL Mode using the Unbrick Tool.
droidwin.com
thunderman75 said:
This looks promising:
Motorola Unbrick Tool: Unbrick any Moto Device via EDL Mode
In this comprehensive guide, we will show you the detailed steps to unbrick any Motorola device booted to EDL Mode using the Unbrick Tool.
droidwin.com
Click to expand...
Click to collapse
Yeah let's hope my device model (X40) get's support soon
@mark332 Any idea's?
I have the same problem, because I did the same thing hahaha, I tried these methods and nothing was successful, I tried to use Lenovo's RSA, but it only installs the correct firmware and Fastboot, but when it comes to rescuing it just has a "Warning" message.
zequinhaBR said:
I have the same problem, because I did the same thing hahaha, I tried these methods and nothing was successful, I tried to use Lenovo's RSA, but it only installs the correct firmware and Fastboot, but when it comes to rescuing it just has a "Warning" message.View attachment 5872305
Click to expand...
Click to collapse
Guess we are in the same boat loll xp having indeed the exact same message. I think the RSA tool detects the right device but it checks for some sort of keys/verification and sees it isn't the right firmware so it stops flashing.
I have found out you can also enter recovery mode by selecting "recovery" in fastboot mode with the key buttons.
Then you need to press power button + down key for 3 seconds, then short the volume up key.
Youll get a other menu with also fastboot mode and adb sideload etc...
but again sadly neither fastboot or adb sideload did work for me
When I tried to flash the original firmware in sideload mode trough ADB it gives a"verification error"
In fastboot mode it says that it can't flash with locked device
I hope this info will be any useful for people stumble upon this topic in the future and maybe help to unbrick this phone.
jody2k said:
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work with this phone in normal fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
Click to expand...
Click to collapse
New hope on horizont for your phone...Machine with Windows10(32-bit) and Moto USB drivers(32-bit).
Phone booted in fastboot mode and connected to PC,recognized instantly.
Screenshot of my Moto Edge 30 ultra connected to above mentioned PC.
Good luck!!!
thunderman75 said:
New hope on horizont for your phone...Machine with Windows10(32-bit) and Moto USB drivers(32-bit).
Phone booted in fastboot mode and connected to PC,recognized instantly.
Screenshot of my Moto Edge 30 ultra connected to above mentioned PC.
Good luck!!!
Click to expand...
Click to collapse
Hey man thanks for your response, sadly i'm on a 64bit windows 11 version. Would it be any different than the 64bit driver vs 32bit you think? Because have tried this several times can't get RSD lite detect my phone . In device manager it's detected first as "fastboot rtwo s" and when the moto 64bit driver is installed it's detected as "motorola ADB interface" so it's correctly detect by the system.
My phone is also in fastboot mode never the less RSD lite tool doesn't detect anything
Guess I could try to install windows 10 32bit i'll keep this updated
jody2k said:
Hey man thanks for your response, sadly i'm on a 64bit windows 11 version. Would it be any different than the 64bit driver from motorola you think? Because have tried this several times can't get RSD lite detect my phone . In device manager it's detected first as "fastboot rtwo s" and when the moto 64bit driver is installed it's detected as "motorola ADB interface" so it's correctly detect by the system.
Never the less RSD lite tool doesn't detect anything
On which mode is your edge 30 phone, fastboot or edl?
Click to expand...
Click to collapse
I also have 64 bit Win11 machine with RSD Lite installed and it can't detect phone.
But when I connect it to my old laptop(Win10-32 bit,RSD Lite) phone is detected instantly.
Try to find someone who has machine with 32 bit Windows and try to rescue your phone.
Tip from professionals: RSD Lite works best with older version of a 32 bit Windows...
thunderman75 said:
I also have 64 bit Win11 machine with RSD Lite installed and it can't detect phone.
But when I connect it to my old laptop(Win10-32 bit,RSD Lite) phone is detected instantly.
Try to find someone who has machine with 32 bit Windows and try to rescue your phone.
Tip from professionals: RSD Lite works best with older version of a 32 bit Windows...
Click to expand...
Click to collapse
Just tried on my older 32bit computer with windows 10 and installed the 32bit driver for motorola. Sadly the issue is the same, RSD lite doesn't detect the moto x40. Where did you download the driver?
Motorola USB Driver for Windows 32-Bit/64-Bit - Driver Market
Download now the latest and official Motorola USB Driver for Windows. We shared the latest Motorola USB Driver for Windows.
www.drivermarket.net
Reinstall driver and restart PC(mandatory),it should work then.
thunderman75 said:
Motorola USB Driver for Windows 32-Bit/64-Bit - Driver Market
Download now the latest and official Motorola USB Driver for Windows. We shared the latest Motorola USB Driver for Windows.
www.drivermarket.net
Reinstall driver and restart PC(mandatory),it should work then.
Click to expand...
Click to collapse
Tried that too several times but thanks for the suggestion anyways.
Took my time also this evening to reinstall a clean windows 32bit version, installed 32bit moto driver again from your link.
Reboot, nope
Same issue, RSD lite doesn't detect anything while the driver and device is recognized in device manager whatever I tried last 2 weeks.
I also opened the phone and searched on the motherboard for EDL test points, no avail too.
I think the RSD tool lite or the usb driver needs a update for this device or someone needs to find out how to get this phone into EDL mode. This can take months maybe years who knows lol
I just gave up and bought myself a new phone (xiaomi 13)