Related
I would like to know if someone could make a custom recovery and a stock version of android that I could put on my Blu Pure XR. I don't care if get rid of the 3d Touch on the phone. I just would like to have the stock android interface again and probably also the ram management will be better on the stock version.
I have the same request, would love to see TWRP. I'd like to install pixel launcher as system app and remove the adsup fota spyware.
The Pure XR is otherwise a great phone. Power management on stock is fantastic, i can get 6-7 hours of screen on time.
The Pure XR is essentially a Gionee S8 but sadly I dont see any custom recovery or development interest for that either.
Include me as well. Thanks
So the Pure XR is similar/same to the Symphony Helio S20...
There's a thread here that has a working twrp: https://forum.xda-developers.com/android/general/how-to-root-symphony-helio-s20-t3491123
I tested the recovery.img by loading it with fastboot without flashing and it worked!
You'll need adb/fastboot and the drivers first. Then boot the phone into fastboot mode by holding power + Up keys.
Select fastboot. After that, run: fasboot devices to make sure your phone is detected. Once detected:
fastboot oem unlock
reboot the phone, it'll do a force wipe
hold power+up keys again and boot to fastboot mode
Now, run this on your PC: fastboot boot recovery.img
Once the image is transferred, the screen goes blank...wait a min or two and TWRP will show up.
rom/firmware blu pure xr?
Anyone found a good stock ROM/Firmware for the Blu Pure XR?
if you finde one just tell us
ishman27 said:
Anyone found a good stock ROM/Firmware for the Blu Pure XR?
Click to expand...
Click to collapse
if you finde one just tell us
exciter0 said:
So the Pure XR is similar/same to the Symphony Helio S20...
There's a thread here that has a working twrp: https://forum.xda-developers.com/android/general/how-to-root-symphony-helio-s20-t3491123
I tested the recovery.img by loading it with fastboot without flashing and it worked!
You'll need adb/fastboot and the drivers first. Then boot the phone into fastboot mode by holding power + Up keys.
Select fastboot. After that, run: fasboot devices to make sure your phone is detected. Once detected:
fastboot oem unlock
reboot the phone, it'll do a force wipe
hold power+up keys again and boot to fastboot mode
Now, run this on your PC: fastboot boot recovery.img
Once the image is transferred, the screen goes blank...wait a min or two and TWRP will show up.
Click to expand...
Click to collapse
When I connect the phone through Fastboot and enter the command "fastboot devices," the phone is never recognized. I'm using Windows 10. Any help would be appreciated.
I used Linux instead. Have you installed the mtk and adb windows drivers?
exciter0 said:
I used Linux instead. Have you installed the mtk and adb windows drivers?
Click to expand...
Click to collapse
Yes, I installed the mtk and adb drivers however while adb works and detects my phone, fastboot does not.
Ok, I attempted using the SP Flash Tool on Windows 10 and successfully installed TWRP and rooted the phone. The only flaws are that the phone takes a few minutes to load into TWRP and unfortunately, there are still no custom roms on the device. It is a good start however.
Galaxxus_Rosarrius said:
Ok, I attempted using the SP Flash Tool on Windows 10 and successfully installed TWRP and rooted the phone. The only flaws are that the phone takes a few minutes to load into TWRP and unfortunately, there are still no custom roms on the device. It is a good start however.
Click to expand...
Click to collapse
Hey bud, big favor, would you describe step by step the rooting process, I used SP Flash Tool on windows 7 to install TWRP and it gave the ok check marK, then I tried to boot into recovery and I found out that TWRP was not installed. Do you have to unlock the bootloader to be able to install TWRP using SP Flash Tool? Thanks in advance.
Sent from my SM-G935T using XDA-Developers Legacy app
Hello everyone, I need your help, I've been trying to unlock my bootloader to root my phone, under setings I have developer options-OEM UNLOCK, but I only get as far as FASTBOOT MODE using my laptop as well as my pc, I tried this process with Windows 10, Windows 7 and latest Ubuntu. I tried different data cables, different usb ports 2.0 and 3.0 and nothing seems to work, I can put the phone on FASTBOOT MODE with my pc or lap, but then after that it looks to me that there is no comunication between my pc and phone. I installed all drivers several times and under DEVICE MANAGER everything looks good, as far as data cables I'm using 2 blu original data cables as well as aftermarket ones. Any help will be appreciated. Thanks in advance and have a good day.
Sent from my SM-G900T using XDA-Developers Legacy app
oscarmaldonado said:
Hey bud, big favor, would you describe step by step the rooting process, I used SP Flash Tool on windows 7 to install TWRP and it gave the ok check marK, then I tried to boot into recovery and I found out that TWRP was not installed. Do you have to unlock the bootloader to be able to install TWRP using SP Flash Tool? Thanks in advance.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I remember something similar to this happening to me when I used a different version of SP Flash tool. Try SP Flash Tool v5.1624.00.000. After this make sure you have the scatter file for the MT6755 as well as the recovery file for the phone. Make sure that you have selected the scatter file for the phone and that the recovery.img is in the same directory as the scatter file.
Once this is done, make sure that you have installed the preloader or VCOM driver for the phone. This is tricky as the opportunity to apply the correct driver comes when you are powering on the phone and in this time you must click on the device that pops up in this time, right click it, and click properties.
Once this is done, go back to SP Flash Tool and click download, your phone must be off and unplugged before doing this. Then after this step, plug in your phone and the download process should begin (this might take a while). After this, boot into recovery mode which also will take around 3-5 minutes maybe more. After this you will have TWRP installed and from there you can install various apps including SU.
Galaxxus_Rosarrius said:
I remember something similar to this happening to me when I used a different version of SP Flash tool. Try SP Flash Tool v5.1624.00.000. After this make sure you have the scatter file for the MT6755 as well as the recovery file for the phone. Make sure that you have selected the scatter file for the phone and that the recovery.img is in the same directory as the scatter file.
Once this is done, make sure that you have installed the preloader or VCOM driver for the phone. This is tricky as the opportunity to apply the correct driver comes when you are powering on the phone and in this time you must click on the device that pops up in this time, right click it, and click properties.
Once this is done, go back to SP Flash Tool and click download, your phone must be off and unplugged before doing this. Then after this step, plug in your phone and the download process should begin (this might take a while). After this, boot into recovery mode which also will take around 3-5 minutes maybe more. After this you will have TWRP installed and from there you can install various apps including SU.
Click to expand...
Click to collapse
Thank you very much, I'm gonna give it a try as soon as I get a chance, I'll report back. Thanks again.
Sent from my SM-N910T3 using XDA-Developers Legacy app
Hi everyone, TWRP has been released by lopestom here https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
Since the Pure XR threads are very slim here I thought I'd post this here.
Seems my XR's data has got very slow, signal strength weak, etc.
Trying to figure out if this is Cricket or something up with the phone. My wife has a Blu Life one X3 and the same Cricket and her signal and data speeds are always better than mine.
What are some things to check/look for? I've tried a few like manually choosing the Network, changing the APN settings, etc.
Any further advice would be greatly appreciated.
After long time research I have found a way how to restore hard bricked Meizu Pro 5.
It should work on phones:
1. With lost recovery and locked bootloader (fastboot) My case.
2. With lost bootloader
3. With lost recovery and bootloader
First case was tested by me with international version phone, but as restore procedure is very low level it should work and for other two cases and probably Chinese phones.
Unbrick procedure was done using 32bits. Windows 7 Professional Version 6.1 (Build 7601: Service pack 1) with installed all updates. 32 bit OS was used because I found only 32 bits. Drivers, not for the phone, but for Samsung Exynos7420. As you know this phone is based on 7420 chip.
Windows 10 won’t work.
The puzzle was solved after rethinking of information from these forum posts:
1. https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865
2. https://forum.xda-developers.com/meizu-pro-5/help/to-unlock-hardbricked-meizu-pro-5-t3566173
thanks these guys for showing me path.
The trick is to put phone in Exynos7420 mode and flash unlocked bootloader. Unlocked boot loader I took from link provided in this tread: https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-unlock-bootloader-meizu-pro-5-t3303127
First step.
Then I extracted unlocked bootloader as u-boot.bin.signed and the other three files:
1. fwbl1
2. el3.bin.signed
3. bl2.bin.signed
I took from multiUpgrade 4.8.5.rar archive, you could find them in it if you dig enough into subfolders. Extract from unlocked bootloader file I din’t succeed .
Steps:
1. Prepare 32 bit windows machine. (it could be even a virtual machine, I have done it using parallels desktop, but it is possible and with other virtualisation software, like vmware or of course bare metal)
2. Extract provided archive into somewhere It contains all necessary drivers, tools and files.
3. Install Drivers ~\Files\USB_Download_Tool_32bit\Disk1\Setup.exe
4. Install Microsoft Visual C++ 2012 ~\Files\vcredist_x86.exe
5. Copy ~\Files\USB_Download_Tool_32bit\WinDNWApi.dll and ~\Files\USB_Download_Tool_32bit\WinDNWApi.lib in in: c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
6. Rename c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\WinDNWApi.dat, just add something at the end, I renamed into to WinDNWApi.dat_
7. Run ~\Files\USB_Download_Tool_32bit\Multidownloader.exe and select file ~\Files\Bootloader\MeizuPro5.cfg
8. Boot into Exynos7420 mode Press and hold Vol + and Vol - and press one time power button, keep pressing both Vol buttons. Do not release them.
9. OS should detect device and install drivers, then in the Multidownloader.exe application window you should see connected device.
10. Select device and press start, wait until phone reboots into fastboot mode with unlocked bootloader. Now you can release both Vol buttons. Congratulations, now you have device in fastboot mode with unlocked bootloader.
11. Install Samsung drivers from ~\Files\Samsung Drivers\ using windows device manage and have disk method selecting right drivers file in ~\Files\Samsung drivers\android_winusb.inf. Now you have device in fastboot mode and accessible from fastboot.
12. RUN cmd and go to ~\Files\Rest\ then execute: “fastboot.exe devices”, it should return connected device.
13. Now we can flash TWRP recovery execute: “fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img”
14. Now flash bootloader execute: “fastboot flash bootloader bootloader"
What to do with unlocked bootloader and custom recovery I guess you know .
Because my phone was with corrupted partition TWRP couldn't flash images, so I made few more steps, but for most of the cases should be enough previous.
And of course, if you going to flash stock rom, don't forget to delete these 1) bootloader, 2) ldfw, 3) recovery.img files from update.zip, oversize you be forced to start everything from beginning.
Resources: https://megaupload.nz/Ae6fTegfb7/Files_7z
thank you very much you are my hero or the one of all, you could do it !!!!!!!!!!!!!!!
To solve this puzzle took me few month. Does it helped?
egmantas said:
To solve this puzzle took me few month. Does it helped?
Click to expand...
Click to collapse
you helped me a lot
you must edit the last line: "fastboot flash recovery bootloader bootloader" to "fastboot flash bootloader bootloader"
Guys,
How to get into Exynos mode? I know it is Vol+ and Vol- and one timer Power, but what is the starting point? Should the device be in fastboot mode, switched off or what? And how will I know that I am already in Exynos mode?
In theory I had some founded device on Multidownloader, but device did not reboot after installing bootloader. Of course bootloader is still locked.
pawelec415 said:
Guys,
How to get into Exynos mode? I know it is Vol+ and Vol- and one timer Power, but what is the starting point? Should the device be in fastboot mode, switched off or what? And how will I know that I am already in Exynos mode?
In theory I had some founded device on Multidownloader, but device did not reboot after installing bootloader. Of course bootloader is still locked.
Click to expand...
Click to collapse
To get to Exynos mode you could from every step, it is no necessary to be in fastboot or switched off, but from fastboot probably its more noticeable.
Steps:
To be sure you are in Exynos mode do these steps.
1. Run windows device manager
2. Vol+ and Vol- and one timer Power (I am holding power until I see new device in windows device manager, then continuing to hold only Vol+ and Vol-)
3. If drivers installed correctly in windows device manager com/LPT section you should see Exynos device, check its com port number.
4. Run Multidownloader and if its com port is the same as exynos device in windows device manager you will know what it is the same device.
5. Don't forget step 6 from tutorial, because WinDNWApi.dat contains map, which is not good, so simply rename file.
Everything I have done on fresh installed windows 7 32 bit. machine hosted in parallels desktop. But you could do it with bare metal.
I made everything just as you wrote. Still nothing...
Would you help me in PM?
@egmantas WOW, I was with the same situation,locked bootloader and no recovery .I do as you written and it work perfectly .
The only thing I do different is to install windows 7 32 bit on virtual machine using vmware software and it work as you said .I do it because I have windows 10 and I can not install windows 7 on this computer .
Thank you so much .
or965 said:
@egmantas WOW, I was with the same situation,locked bootloader and no recovery .I do as you written and it work perfectly .
The only thing I do different is to install windows 7 32 bit on virtual machine using vmware software and it work as you said .I do it because I have windows 10 and I can not install windows 7 on this computer .
Thank you so much .
Click to expand...
Click to collapse
I have done the same, but with parallels desktop
It works man! You are the best!
Thank you very much. :good:
With your CFG file as template, I was able to recover my Samsung SM-R760:
https://forum.xda-developers.com/showpost.php?p=78641965&postcount=700
:good:
Best Regards
great thanks!!
it works!!!
but i must mention, you need Windows 7 32 bit installation, what is capable to install windows updates (i had "tiny" or "lite" version of win 7 ultimate, and it was not capable to process this method.) so i did clean install of Windows 7 Professional.
Success!
egmantas said:
After long time research I have found a way how to restore hard bricked Meizu Pro 5.
It should work on phones:
1. With lost recovery and locked bootloader (fastboot) My case.
2. With lost bootloader
3. With lost recovery and bootloader
First case was tested by me with international version phone, but as restore procedure is very low level it should work and for other two cases and probably Chinese phones.
Unbrick procedure was done using 32bits. Windows 7 Professional Version 6.1 (Build 7601: Service pack 1) with installed all updates. 32 bit OS was used because I found only 32 bits. Drivers, not for the phone, but for Samsung Exynos7420. As you know this phone is based on 7420 chip.
Windows 10 won’t work.
The puzzle was solved after rethinking of information from these forum posts:
1. https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865
2. https://forum.xda-developers.com/meizu-pro-5/help/to-unlock-hardbricked-meizu-pro-5-t3566173
thanks these guys for showing me path.
The trick is to put phone in Exynos7420 mode and flash unlocked bootloader. Unlocked boot loader I took from link provided in this tread: https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-unlock-bootloader-meizu-pro-5-t3303127
First step.
Then I extracted unlocked bootloader as u-boot.bin.signed and the other three files:
1. fwbl1
2. el3.bin.signed
3. bl2.bin.signed
I took from multiUpgrade 4.8.5.rar archive, you could find them in it if you dig enough into subfolders. Extract from unlocked bootloader file I din’t succeed .
Steps:
1. Prepare 32 bit windows machine. (it could be even a virtual machine, I have done it using parallels desktop, but it is possible and with other virtualisation software, like vmware or of course bare metal)
2. Extract provided archive into somewhere It contains all necessary drivers, tools and files.
3. Install Drivers ~\Files\USB_Download_Tool_32bit\Disk1\Setup.exe
4. Install Microsoft Visual C++ 2012 ~\Files\vcredist_x86.exe
5. Copy ~\Files\USB_Download_Tool_32bit\WinDNWApi.dll and ~\Files\USB_Download_Tool_32bit\WinDNWApi.lib in in: c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
6. Rename c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\WinDNWApi.dat, just add something at the end, I renamed into to WinDNWApi.dat_
7. Run ~\Files\USB_Download_Tool_32bit\Multidownloader.exe and select file ~\Files\Bootloader\MeizuPro5.cfg
8. Boot into Exynos7420 mode Press and hold Vol + and Vol - and press one time power button, keep pressing both Vol buttons. Do not release them.
9. OS should detect device and install drivers, then in the Multidownloader.exe application window you should see connected device.
10. Select device and press start, wait until phone reboots into fastboot mode with unlocked bootloader. Now you can release both Vol buttons. Congratulations, now you have device in fastboot mode with unlocked bootloader.
11. Install Samsung drivers from ~\Files\Samsung Drivers\ using windows device manage and have disk method selecting right drivers file in ~\Files\Samsung drivers\android_winusb.inf. Now you have device in fastboot mode and accessible from fastboot.
12. RUN cmd and go to ~\Files\Rest\ then execute: “fastboot.exe devices”, it should return connected device.
13. Now we can flash TWRP recovery execute: “fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img”
14. Now flash bootloader execute: “fastboot flash bootloader bootloader"
What to do with unlocked bootloader and custom recovery I guess you know .
Because my phone was with corrupted partition TWRP couldn't flash images, so I made few more steps, but for most of the cases should be enough previous.
And of course, if you going to flash stock rom, don't forget to delete these 1) bootloader, 2) ldfw, 3) recovery.img files from update.zip, oversize you be forced to start everything from beginning.
Resources: https://megaupload.nz/Ae6fTegfb7/Files_7z
Click to expand...
Click to collapse
This worked very well, thank you for this guide.
I used VMWare Workstation Pro with Windows 7; VM Virtual Box did not work well.
Could someone just re-upload https://megaupload.nz/Ae6fTegfb7/Files_7z ?
Thanks
I have the same problem. Link to the files does not work
It says doesn't work on windows 10, what about Ubuntu 18? Thanks
New link to same file:
http://www.mediafire.com/file/7bi0di2pdjxkh9f/Files.7z/file
If someone knows more reliable file hosting site, not temporary, please share, I will this file to it.
Hi, no it does't work on any Ubuntu or linux versions as drivers are for windows. Of course you can use virtualization software in Ubuntu and install windows, then connect you phone to this virtual machine.
Someone with this problem did it.
Bandanaman said:
It says doesn't work on windows 10, what about Ubuntu 18? Thanks
Click to expand...
Click to collapse
Meizu pro 5 Ubuntu Touch
Guys I'm new to all this stuff and feel a bit in over my head! Is there anyone I can send my phone to (one of u guys maybe?) Who could do this for a fee?
I had a locked bootloader and broken recovery, аfter a failed installation of the last firmware with a missing serial number on my PRO 5.
I recently tried this method with different versions of windows and different PCs.
And always got the same error in Multidownloader.
The phone reboots into fastboot and there is still a locked bootloader.
It was possible to solve the problem only in the service center, using the MRT Dongle.
Are there any suggestions of what the problem might be? (for future generations)
i tried to do it my self. follow an instruction from a official website and other
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
https://www.getdroidtips.com/how-to...-plus-i3213-i4213-i4293-i3223/#Pre-Requisites
which i got stuck at, when i boot into bootloader mode . the phone seem to restart and appear only black screen with blue indicator.
then i tried to check if it still connect to adb or not, with {adb devices} its not listed there
PS.
-the drivers work fine
-my Xperia 10 plus model is I4293
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Zaben said:
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Click to expand...
Click to collapse
one thing weird
i using a Xperia Tool (Xperia Companion) and it display the text that my phone need to unlock the screen or allow to use data tranfer
which i already check a USB debugging to be on, and every time i connect it to my PC, it still ask me a permission to be allow or not
maybe this is a problem here ?
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Haxk20 said:
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Click to expand...
Click to collapse
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
ZimpleThing said:
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
Click to expand...
Click to collapse
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Haxk20 said:
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Click to expand...
Click to collapse
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
ZimpleThing said:
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
Click to expand...
Click to collapse
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Haxk20 said:
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Click to expand...
Click to collapse
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
ZimpleThing said:
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
Click to expand...
Click to collapse
There is a thanks button. Hit it instead of saying it.
Haxk20 said:
There is a thanks button. Hit it instead of saying it.
Click to expand...
Click to collapse
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Glad I could help
I know its been a long time but maybe someone can help me.
I can get into the bootloader but when I trie to use the unlock code, mentioned above, and the sony unlock key it always says waiting for device but nothing happens. Any clue?
Edit fixed the Problem
Xperia 10 plus stuck on waiting for device
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
I was using windows 10. From what I can remember, my problem is that I didn't install driver correctly (I'm not sure which one). I am not really sure if this fastboot driver the one I used. I saw my device in Device Manager, but I got waiting on device... just like you. So what I have done was locate my device in Device Manager and install the sony driver over that device. If sony's driver was not the correct one, then it was another driver that I can't remember, but the instruction still the same. Sorry for an unclear message, but I can barely remember anything now.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
Go in Windows Device Manager and check the device . If needed install drivers manually
Hello!
I know this must be a stupid question but couldn't find the solution!
I was trying to unlock the bootloader but it looks like the phone is not recognized by the system (adb devices find it correctly but when I give the "fastboot flashing unlock" command, it will wait for the device indefinitely).
The phone is not recognized in Control Panel -> System -> Devices (it has the yellow triangle warning) so I tried installing the official Xiaomi USB Drivers (downloaded xiaomi_usb_drivers.rar from the official xiaomi website) but it would not succeed.
So what drivers should I install? And where to find them?
Thank you
DBuffon said:
Hello!
I know this must be a stupid question but couldn't find the solution!
I was trying to unlock the bootloader but it looks like the phone is not recognized by the system (adb devices find it correctly but when I give the "fastboot flashing unlock" command, it will wait for the device indefinitely).
The phone is not recognized in Control Panel -> System -> Devices (it has the yellow triangle warning) so I tried installing the official Xiaomi USB Drivers (downloaded xiaomi_usb_drivers.rar from the official xiaomi website) but it would not succeed.
So what drivers should I install? And where to find them?
Thank you
Click to expand...
Click to collapse
Download pdanet for windows
It'll automatically install drivers
Connect your device in fastboot mode and install pdanet in your pc
Thanks. Do you mean "PdaNet for Android" by JuneFabrics?
DBuffon said:
Thanks. Do you mean "PdaNet for Android" by JuneFabrics?
Click to expand...
Click to collapse
For windows
Rajendran Rasa said:
For windows
Click to expand...
Click to collapse
Can you point me to it? I've googled but there are different things and softwares named pdanet, so I'm not sure which one is the correct one.
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)