Database Develop

Unable to find device in RSDLite

Hi guys, I'm using Motorola Milestone and my bootloader is 90.78. I opened RSDLite and plug in the phone in bootloader mode but my RSDLite is unable to detect my device.
I have already installed the motorola drivers. Anyone has any ideas?

bryant_16 said:
Hi guys, I'm using Motorola Milestone and my bootloader is 90.78. I opened RSDLite and plug in the phone in bootloader mode but my RSDLite is unable to detect my device.
I have already installed the motorola drivers. Anyone has any ideas?
Click to expand...
Click to collapse
Same issue here. I have bootloader 90.74. On my Windows 7 there's no way...
Drivers 4.1 and 4.6 tested...but no way...

Anyone has any ideas about this issue?

Weird problem :s Works fine on my Win 7 VM. You could maybe try to uninstall and reinstall the driver :/

Some people have issues with RSDLite on Windows 7 64 bits.
I used to have the same problem and finally I had to install it on my netbook which has W7 32 bits and it worked fine.
Did you managed to install it in an other computer ?

The latest RSDLite versions didn't worked for either but version 4.5.3 works good under Windows 7 for me!

I found a solution
Like the rest, I too had the same problem. Then I found out how to make it work by accident.
I am using RSDlite version 4.5.7 on Windows 7 (32-bit version).
This is what you must do.
Step 1:
Download Open Recovery Version 1.46 for Milestone from http://www.modmymobile.com/forums/downloads.php?do=file&id=28089
Step 2:
It is a rar file, so use any free software to extract out the contents of this OpenRecovery_v1_46_SHOLS.rar file to a new folder on your desktop.
After u have extracted it, look for a file called vulnerable_recovery.sbf. Copy out this vulnerable_recovery.sbf file to somewhere on your pc for example to the root of your C drive on your PC.
Step 3:
Download from this script to disable the recovery check for signed recovery menu (so that we can apply update.zip later) from
http://modmymobile.com/forums/attac...le-recovery-disable_recovery_check_by_ota.zip.
Unzip the file and there should be a file called Disable_recovery_check_by_OTA.sh
Step 4:
Copy the Disable_recovery_check_by_OTA.sh file to a sub folder called scripts that is within the OpenRecovery folder (which we have already extracted earlier) (eg. OpenRecovery\scripts).
Step 5:
Boot up the phone as per normal and then connect the phone to PC via USB cable
Step 6:
Change the USB Connection to Memory Card Accessl
Step 7:
Go to the desktop of your PC and open up the folder where the contents of the extracted OpenRecovery_v1_46_SHOLS.rar file is. You should then copy the update.zip to the root of your phone's SD card (eg. SDcard\update.zip).
Also copy the whole OpenRecovery folder also to the root level of your SD card (eg. SDcard\OpenRecovery)
Step 8:
Change the USB Connection to Portal & Tool. This is the trick that will allow RSDLite to detect your phone.
Step 9:
Launch RSDLite ver.4.5.7
Step 10:
It will take a few seconds for your phone to appear in the device list of RSDLite
Step 11:
Click on the "..." button and locate and open the vulnerable_recovery.sbf file which we have extracted earlier and had copied out to somewhere (eg. root of C drive).
Step 12:
Click on the "Start" button.
Step 13:
Immediately you would see something in the status progress of RSDlite. RSDlite will switch your phone to the Bootloader mode by itself.
Step 14: - Very Important Step
Pay attention to the status of the Bootloader on your phone. Halfway thru the progress of flashing the vulnerable_recovery.sbf, RSDlite will initiate a reboot of your phone.
When that happens, you must prevent the phone from rebooting into the normal Android mode and get it to boot into the Bootloader mode by quickly pressing & holding up on your D-pad in horizontal (landscape) position.
I would suggest that b4 RSDlite initiate the reboot, you should be prepared for it by sliding out the keyboard first and hold it in the horizontal (landscape) position and get ready to press up on the D-Pad.
by quickly turning your phone to the horizontal position (landscape) and press and hold up on the D-Pad of your phone. Hold the up key of your D-pad for about 3 to 4 seconds before release it and it should be now back in the bootloader mode.
Do not do anything yet. You will know when the flashing of the vulnerable_recovery.sbf is completed and successful when the result in RSDLite device list window says "PASS".
Step 15: - Also very important step
Once the flashing of the vulnerable_recovery.sbf is complete (after you see "PASS" in RSDlite), you may close RSDlite and then unplug the phone from the USB cable.
The phone is still in the bootloader mode. Now be prepared to boot into the recovery mode. This is very important. If you fail to boot into the recovery mode then you will have to repeat from Step 8
The technique that I use on my Motorola Milestone to boot into the recovery mode is by using the 3 button technique. I press the "x" key + power button + camera button together at the same time and hold it until the recovery mode icon appears which is a an exclamation mark within a triangle.
Step 16:
While in the recovery mode, slide the keyboard back in. Then press and hold the volume up button first and then press the camera button once and when you see the recovery menu you can quickly release the volume up button.
Step 17:
Slide the keyboard out. Use the D-pad to navigate. If you are holding the phone in vertical position, then to navigate up and down the recovery menu, just press up or down on the D-pad. To confirm your selection, press down on the middle of your D-Pad.
Using your D-Pad, scroll down to the part it says "apply sdcard:update.zip" and press the middle of your D-Pad to select it.
You should see something packages being downloaded to your phone which is part of the installation process of the Motorola Milestone Open Recovery Menu which is not the stock Recovery Menu.
Step 18:
Once you are in the Motorola Milestone Open Recovery Menu, scroll down to the option that says "Run Script". Select that option.
Step 19:
Then you should be able to see a list of scripts and one of them should be "Disable_recovery_check_by_OTA.sh". Select that script.
Step 20:
Once that "Disable_recovery_check_by_OTA.sh" has been applied, the phone will no longer check for signed recovery menus like this Motorola Milestone Open Recovery Menu when ever you go into the stock recovery menu to "apply sdcard:update.zip". This means you can install different types of "Open Recovery Menu" for different custom roms for Motorola Milestone.
Besides using this Motorola Milestone Open Recovery Menu, I have also tried the following 2 "Open Recovery Menu" on my Milestone:
1) Androidiani OpenRecovery 3.3 - http://forum.xda-developers.com/showthread.php?t=796679
2) G.O.T OpenRecovery (for installing G.O.T custom FROYO rom) - http://groupoften.wordpress.com/g-o-t-s-openrecovery/
Important Note:
Before you start to install custom roms please do a Nandroid back up of your phone in case something goes wrong during the installation of the custom rom, you can restore your phone back to stock rom.
The Nandroid back up and restore option is available within all 3 "Open Recovery Menu" mentioned above.

I have Windows 7 Ultimate 64-bit and I use Motorola USB Drivers 4.7.1 and RSD Lite 4.9. So it would be good to download these versions, which are the latest. If this wont work, do a factory reset on your Milestone.

[ROM] [STOCK] [Unbrick] [x3_row] Lenovo VIBE X3 ROW (X3a40) Stock Firmware Flashing

DISCLAIMER: I am not responsible for anything that happens while/after flashing these files. Your device's destiny is your own responsibility. Proceed at your own risk.
After days of waiting, a stock ROM package for Vibe X3 is finally available(or rather leaked).
This thread and all its contents are meant solely for the ROW variant X3a40.
This thread will come handy for restoring both working or bricked devices back to stock state.
There are two ways to flash the stock ROM:
Using QFIL tool on PC: This should be handy for bricked devices and also for working devices. Guide in post #2.
Using Qualcomm Diagnostic mode on device: This should be handy for people willing to downgrade a working device to an older stock firmware. Needs access to internal storage so doesn't make sense to use for a bricked device. Won't work if on custom ROM (modded stock ROMs should work). Guide in post #3.
DOWNLOADS
X3a40_S237_170803_ROW QFIL Package (1.6 GB) | Alternative .7z File (1.4 GB) | Follow post #2 | Latest
X3a40_S217_160623_ROW QFIL Package | Follow post #2
X3a40_S130_151122_ROW QFIL Package | Follow post #2
X3a40_S130_151122_ROW QSB Package | Follow Post #3
Drivers + QFIL | Windows 10 | Windows 7 | (UPDATED: 5/4/16)
Credits: http://lenovo-forums.ru/forum/590-lenovo-vibe-x3-прошивки/
The file sizes differ due to different compression levels and format.

With Windows PC Flashing Guide
WARNING: Everything apart from data in external SD card will be wiped. Make sure to backup everything.
Download the QFIL flash package ZIP and appropriate ZIP from Drivers+QFIL.
Extract the ZIPs to a folder whose complete path has no spaces (space characters) at all. A number of people have reported issues when this folder is on the same partition as Windows(mostly C: ) so prefer D: or any other partition.
Make sure you uninstall any other phone's PC Suite/drivers as they may cause conflicts. Microsoft Emergency Driver (installed for restoring Lumia devices) is known to conflict, please uninstall it.
Go to Drivers+QFIL folder extracted in Step 2, run the appropriate 'INSTALL_DRIVERS_&_QFIL.bat' and follow the instructions.
Backup contacts, SMS, apps, etc. as well as the entire internal storage as they will all be wiped(you will setup a new phone). Internal storage WILL BE erased when using the QFIL flash method.
Run 'QFIL' program. Let it load, close and run it again. This restart is only needed if you haven't used QFIL on that PC before and failing to do so might cause Sahara related errors.
Select 'Flat Build' as build type.
Click on 'Browse', select the 'prog_emmc_firehose_8992_ddr.mbn / prog_emmc_firehose_8992.mbn' file from the 'X3a40_S130_151122_ROW_QFIL' folder which you extracted.
Click on 'Load XML' and select 'rawprogram0.xml' followed by 'patch0.xml'.
Make sure you completed each step precisely, the USB cable is connected ONLY to USB port (USB 2.0 preferably) of PC and not to device yet, the device is powered off and is charged (at least 40%).
Now boot into EDL by plugging in the USB cable to device and then QUICKLY(within a second of plugging in) pressing and holding power button for ~1 second. QFIL's 'No port available' text should change to 'Qualcomm HS-USB QDLoader 9008 (COMXX)'. The display will stay off so, don't worry about it.
Within ~5 seconds put the device on a stable surface (so that it doesn't move around or shake) and press the 'Download' button on QFIL. If you are late, the device starts to power on normally and you need to go back to Step 11 and continue.
Wait for the flash to complete and 'Download Succeeded' message appear at the bottom.
Press and hold the power button for ~10 seconds to boot normally. If display doesn't turn on press and hold the power button again for longer time, it will boot.
Once you see the Lenovo logo, unplug the phone.
Once you have finished the initial set up, open dialer, dial '####682#', choose your region and confirm.

Without PC (QSB) Flashing Guide
WARNING: All the contacts, SMS, apps, etc. will be wiped. Make sure to backup them. Data in internal storage (sdcard0) and external SD card will not be wiped.
Download the QSB package and extract the ZIP.
Place the "sdfuse" folder extracted from the ZIP in internal storage of your device.
Backup contacts, SMS, apps, etc. as they will all be deleted(you will setup a new phone). Internal storage will not be erased when using the QSB flash method. But, to be safe, back up the data in internal storage too.
Boot to Qualcomm Diagnostic mode (not recovery) by pressing and holding Volume down + Power button together until Lenovo logo appears and flickers once(release the buttons after flicker).
Goto 'SD Update' using volume rockers and touch on 'Enter'.
Touch on 'Start'.
Once finished touch 'Restart'.
Once you have finished the initial set up, open dialer, dial '####682#', choose your region and confirm.
That's it.

TIPS & INFORMATION
The various modes X3a40 can boot into:
Recovery mode: Press and hold Volume up + Volume down + Power together until Lenovo logo shows up and flickers once. Release the buttons and you will reach the recovery. This opens up the recovery of the device.
Qualcomm Diagnostics mode: Press and hold Volume down + Power button together until Lenovo logo shows up and flickers once to boot into this mode. This opens up the Qualcomm Diagnostics screen which has a number of hardware testing and other tools along with ability to flash the stock ROM. It is also used for further Diagnosis using a PC.
Fastboot mode: Press and hold Volume up + Volume down and plug in the USB cable(already connected to PC). You may also use the ADB command "adb reboot bootloader". Obviously, you need a working device with USB Debugging turned on and ADB installed on PC. This enables the traditional Fastboot interface. NOTE: Device stays on Lenovo logo while in Fastboot mode.
EDL mode: Plug the USB cable and then QUICKLY(within a second of plugging in) press and hold the power button for a little while. Device stays in EDL only for ~5 seconds unless you start firmware flash via QFIL. You can also use ADB command "adb reboot edl". This will put your device in Qualcomm Emergency Download Mode which is meant to flash stock firmware using QFIL tool on working/bricked devices.
Normal mode: This is what you boot by normally pressing the power button. I don't need to say much about this one.
Keep your NV data (IMEI, Serial No., etc.) backed up from QFIL>Tools>QCN Backup Restore. Device must be in Qualcomm Diagnostics mode. There are many more ways to do this.

Thanks

Thank you!!!
Thank you for sharing. I was waiting for this, now we can experiment our device without any fear.

Hey. Can we see some guides since it's weekend

thank you

I cracked my device's display. :crying:
Wouldn't be able to work on root for next 10-15 days.
Meanwhile, the 138 update is nice.

That's sad news

Arpit. Meanwhile someone has suggested in the lenovo forum to copy the file (downloaded from the Russian site) and flash it thru recovery mode.. My question is will it work.. As this is my primary and only device

Work, its my post in lenovo forum, everythings works

maxpaynezm said:
Work, its my post in lenovo forum, everythings works
Click to expand...
Click to collapse
me video flash stock rom https://www.youtube.com/watch?v=GC955AFBACk

No need to download this rom and use SD update. I got update right from the system settings. But thanks for those links.

this is not update,but original stock rom s130,because the update drain more battery

arpit_nnd said:
DISCLAIMER: I am not responsible for anything that happens as a result of flashing these files. Your device's destiny is your own responsibility.
After days of waiting, a stock ROM package for Vibe X3 is finally available.
Hey Thanks a lot !!
Recently i have shifted from samsung Note 2 to Vibe x3. Is there any means(may be themes) to have toggles similar to Samsung TW. I feel that samsung TW appearance is much better than Lenovo.
I am using nova launcher as its better than stock lenovo theme.
Also is there any means to have sound on boot animation.Current feel is similar to any CM ROM
Click to expand...
Click to collapse

maxpaynezm said:
me video flash stock rom https://www.youtube.com/watch?v=GC955AFBACk
Click to expand...
Click to collapse
Thanks for this video mate !

Noob Question: When you say newer and tested drivers, what does it mean?

HarveySpecter said:
Noob Question: When you say newer and tested drivers, what does it mean?
Click to expand...
Click to collapse
I haven't uploaded that package yet.
Sorry about that.
I need to get my device's display fixed. I will complete this thread then.

Looks like we can expect a custom rec now.

Brick Me176C K013 - ASUS logo - HELP

I tried to downgrade from LP to KK, but I did something wrong ME176c K013!
Now I can not get into recovery nor fastboot, it's in ASUS logo and power by android!
Can someone help me?
Thank you.
Solved:
I had just installed ADB Asus drivers and it lacked installing Intel USB Drivers.

I rooted my ME176C that already had Lollipop without problems. But after that I tried to install xposed on it and now the tablet only shows Asus logo and the circle cicling all the time. I can get into the recovery mode but neither factory reset or wipe partition solve my error.
Maybe I installed an xposed that was not compatible wiht my tablet. Any could help me to solve this?
Thank you.

pgharg said:
I rooted my ME176C that already had Lollipop without problems. But after that I tried to install xposed on it and now the tablet only shows Asus logo and the circle cicling all the time. I can get into the recovery mode but neither factory reset or wipe partition solve my error.
Maybe I installed an xposed that was not compatible wiht my tablet. Any could help me to solve this?
Thank you.
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814
Give your tablet 15mins to boot.

MARCOSOFT said:
Try https://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814
Give your tablet 15mins to boot.
Click to expand...
Click to collapse
I tried in this mode
Step 1:
I have windows 8.1 64 bits on my pc, then I installed
Installed 7-Zip for 64-bit Windows x64 (Intel 64 or AMD64) - 7-Zip 17.00 beta (2017-04-29) for Windows:
Installed Notepad++ 6.7.9.1
Downloaded IntelAndroid-FBRL-05-16-2015-PTR.7z but it only have 5MB instead of the 26Mb detailed on the download page.
Step 2
Downloaded UL-K013-WW-12.10.1.36-user.zip. Unzipped and also unzipped the esp.zip to esp folder inside the UL-K013-WW-12.10.1.36-user.zip
I selected this ASUS MeMO Pad (ME176C_CX)Software Image Version: V 12.10.1.36(Android 5.0)For WW SKU only(Lollipop To Lollipop)*
because I have already installed Lollipop in that device in the past without problems
Step 3
Deleted the 2 first line and saved
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
Step 4
Used the 7-Zip to generate Update.zip with normal compression mode
Inside the zip was the other zip archive (called esp.zip) and I unzipped it in a folder called esp following the spep number 2 but the first time I deleted the esp.zip when doing the step number 4 and the tablet aborted the installation saying file_read /tmp/esp.zip failure, installation aborted and some more things but I generated again the update.zip once again letting inside the esp folder created and also the esp.zip archive.
Step 5: Put update.zip in the root of your micro sd card. Insert your micro sd into your tablet. Done.
Step 6: "Open IntelAndroid-FBRL-05-16-2015-PTR" and the folder inside that. Open "launcher.bat". Done.
Step 7: Power off the tablet. Hold the Volume-Down key in, while holding the Volume-Down press and hold the Power button until the screen says Asus, release the Power button at this point. You should be in recovery. Plug your tablet into your pc.
At this point in my personal case I´m not really in Recovery mode, I´m in whe following window where I can select between Recovery mode, Restart bootloader, Normal boot and Power off.
http://prntscr.com/fp602m
at this point I understood that i have to let the tablet in this window without selecting any option
Step 8. Done
Step 9: Done
Finally your solution worked perfect avoiding my mistakes in the meadle. Now I want to root and install xposed again because I want the FAKE WIFI CONNECTION option.
Thank you so much.
PGH

[GUIDE] How to return to Stock/Flash Images with QFIL

Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download either of the firmware from here
Download the support files (Firehose/rawprogram0.xml/patch0.xml) here
Extract the firmware and support files to the same folder so you can easily access them like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash individual partitions you can edit your rawprogram0.xml to only include the ones you want. (patch0.xml stays the same) I have linked below 2 examples, one of them flashes just a boot.img and one that just flashes the recovery.img. But you aren't limited to those.
Recovery
Boot

Mine just in case

Awesome, thanks for this post! it will really help us in upcoming projects!

Managed to revive my phone using the B12 files but it crashes after completing system.img, I think the problem is userdata.img, my phone boots but I lost the imei and I don't know how to get it back, I'm still trying.

ZTE 971 not recognized by either QPST or QFIL
Thanks for all the detailed instructions. But my ZTE 971 is not visible to either qpst or qfil eventhough the phone shows in windows 8.1. In the Developer Options menu, I noticed Select USB Configuration, RNDIS (USB ethernet) option cannot be enabled. I wonder if this has anything to do with it. OEM unlocking, USB debbugging are already selected. Any suggestions, please? Thanks.
ps. I live in Turkey. I got this phone last year from AT&T and have unlocked the sim.

My PC is not detecting my ZTE MAVEN 3
I have installed all drives but still facing the issue. I am using it on Windows 10.

I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.

Mega says that link for the driver is invalid, but the driver is included in your QPST download anyway.

000Nick said:
I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.
Click to expand...
Click to collapse
solucionaste hermano
Mod edit:
you solved brother
Click to expand...
Click to collapse

it says qhsusb_bulk when I connect the the software is not working in the mobile and it is stuck at bootloader screen but I used the press both buttons to go to edl mode method and it said in the device manager a device connected with name : qhsusb_bulk
help pls

Hello All.
I am not able to get the following files
rawprogram.xml and patch.xml for LG G8x​Please help me to get this files ASAP as i have hard bricked the mobile, all partitions deleted

Redmi 9, bootloop after "reboot to recovery" in custom ROM

Hello, I chose "reboot in recovery" on Pixel UI Plus A11 ROM and now ended up with bootloop on "Redmi" logo.
If I press power+down, the screen turns off and MediaTek USB Port appears in Windows Device Manager for a moment and then disappears and "Redmi" logo shows up again.
If I press Up+Down+Power at the same time, the screen turns off, after around 30 seconds the phone vibrates once and then screen is still blank. At this time, "MediaTek USB Port" device keeps reconnecting in Device Manager. I can't turn off the phone with these 3 buttons. Should I disassemble the phone and disconnect the battery?
How can I repair my phone? Please help.

Hello. I had a similar issue that I tried to solve, that happened after I flashed a recovery image. It took me several hours to figure out how to fix it, but after some search, I can provide a good solution for this issue.
First, you going to need some things. For this procedure you will need the SP Flash Tool (I suggest downloading and installing MiFlashPro if you want to mess with modifications, because it installs all the tools you may need), VD171's MTK bypass tool and a fastboot MIUI ROM for your device (you can choose your preferred version here). I also suggest using the 7zip file manager, because it will be needed as well (for example, you have to extract the fastboot images from the .tar.tgz file).
After getting the files and installing the programs I mentioned above, you should follow the instructions from the MTK bypass tool thread I linked and run the batch file. In case that you get any error from the Python script and it doesn't actually run, you can try installing VSCode/VSCodium, open the main.py file, click on "Run and Debug" (you may have to install a Python debugger first) and then click on the "Run and Debug" button and it should work just fine. Connect your device while it still works, it will be detected by the script. Don't disconnect your device.
If you got the "Protection disabled" output from the MTK bypass tool, you're ready to flash the ROM. Extract the fastboot ROM files (if you haven't already extracted them) and launch the SP Flash Tool. Go to Options>Option>Connections and choose UART, the COM port that appears in the choices and choose "921600" as the baud rate. For the Download Agent, click on "Choose" and use the "DA_6765_6785_6768_6873_6885_6853.bin" file. For the Scatter-loading file, go to "Choose", go to the directory you extracted the files of the fastboot ROM > images > "MT6768_Android_scatter.txt" (or similar). Then, a list of image files will appear. Check all of them. You don't need an authentication file.
Then choose "Download Only" from the dropdown options and click on Download. If you get a warning after seeing the bottom bar loading, change the dropdown from "Download Only" to "Firmware Upgrade" and click on download. Then you have to wait for a few minutes. After that, your device will be able to boot properly. The only downside is that it locks the device and you have to unlock it again.
That's how I fixed my device. I hope my instructions to be useful to you.

getimiskon said:
Hello. I had a similar issue that I tried to solve, that happened after I flashed a recovery image. It took me several hours to figure out how to fix it, but after some search, I can provide a good solution for this issue.
First, you going to need some things. For this procedure you will need the SP Flash Tool (I suggest downloading and installing MiFlashPro if you want to mess with modifications, because it installs all the tools you may need), VD171's MTK bypass tool and a fastboot MIUI ROM for your device (you can choose your preferred version here). I also suggest using the 7zip file manager, because it will be needed as well (for example, you have to extract the fastboot images from the .tar.tgz file).
After getting the files and installing the programs I mentioned above, you should follow the instructions from the MTK bypass tool thread I linked and run the batch file. In case that you get any error from the Python script and it doesn't actually run, you can try installing VSCode/VSCodium, open the main.py file, click on "Run and Debug" (you may have to install a Python debugger first) and then click on the "Run and Debug" button and it should work just fine. Connect your device while it still works, it will be detected by the script. Don't disconnect your device.
If you got the "Protection disabled" output from the MTK bypass tool, you're ready to flash the ROM. Extract the fastboot ROM files (if you haven't already extracted them) and launch the SP Flash Tool. Go to Options>Option>Connections and choose UART, the COM port that appears in the choices and choose "921600" as the baud rate. For the Download Agent, click on "Choose" and use the "DA_6765_6785_6768_6873_6885_6853.bin" file. For the Scatter-loading file, go to "Choose", go to the directory you extracted the files of the fastboot ROM > images > "MT6768_Android_scatter.txt" (or similar). Then, a list of image files will appear. Check all of them. You don't need an authentication file.
Then choose "Download Only" from the dropdown options and click on Download. If you get a warning after seeing the bottom bar loading, change the dropdown from "Download Only" to "Firmware Upgrade" and click on download. Then you have to wait for a few minutes. After that, your device will be able to boot properly. The only downside is that it locks the device and you have to unlock it again.
That's how I fixed my device. I hope my instructions to be useful to you.
Click to expand...
Click to collapse
my phone not recognized as mediatek usb port any solution??