>> The first thing you all folks should know, that the modem TP-Link M7350 V 1.0 is an Android Device <<
All flies that I post here are to download from my personal account:
Download link: I'm a new user, and I'm not able to post outside links. Write to me for this files. (maybe moderator could allow me to share to mega upload link)
1. Alcatel_windows_10_x64_driver_M7350_TP_Link.zip
2. Android_AIO_Flasher.rar
3. M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip (copy from TP-Link website)
4. CKT Qwrite_Writer.rar
5. M7350(UN) 1.0_1.0.11 build 141126 Rel.1014n_User.zip (older firmware)
1. This file is a driver that connect this Android Device to Windows 10 x64 peer USB 2.0 cable. (If this driver does not work by you, write to me)
2. Universal Android Flash program, I downloaded from google.
3. Firmware in ZIP file format for M7350 downloaded from official TP-Link web page.
4. After installing drivers you can view your Imei and WiFi numbers.
What I have try do make:
I have try to upload to device the boot.img file that's in M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip with success, but my device is still locked on TP-Link logo.
Next step was to reboot the device from Universal Android Flash program, and it rebooted (means connection is ok). ADB Shell is working in Universal Android Flash, and normally also. I have try peer normal adb program to command:" adb reboot recovery" and then adb sideload firmware.zip but I get error "closed". I see all files on the device but I can not connect it from command line to WLAN, or update firmware.
What is the problem ?
Device use Qualcomm MDM9225 chip, files inside firmware:
appsboot.mbn ; qdsp6sw.mbn ; sbl1.mbn ; boot.img
I have seen that the same files are by flashing Qualcomm Phones by using QFIL.
QFIL is seeing this modem as ALCATEL HS-USB Diagnostics 9025 (COM7), I can also make an QCN Backup.
But not upload this firmware, because there is no XML data for this firmware.
Hours searching on google I have found some application there I could chose which files to flash.
Maybe someone has solved this problem, the driver from ALCATEL is ok, they use the same chip.
If moderator allows me to share some links and pics, I will re-write this post.
Thx 4 Help
Hi,
I have the same problem.
Have you solved this?
If yes, can you post the steps that you followed here?
Thanks
Hi,
I have a TP link M7350 stuck in boot loop could you give me a link for your drivers ?
Thanks
yakuzja said:
>> The first thing you all folks should know, that the modem TP-Link M7350 V 1.0 is an Android Device <<
All flies that I post here are to download from my personal account:
Download link: I'm a new user, and I'm not able to post outside links. Write to me for this files. (maybe moderator could allow me to share to mega upload link)
1. Alcatel_windows_10_x64_driver_M7350_TP_Link.zip
2. Android_AIO_Flasher.rar
3. M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip (copy from TP-Link website)
4. CKT Qwrite_Writer.rar
5. M7350(UN) 1.0_1.0.11 build 141126 Rel.1014n_User.zip (older firmware)
1. This file is a driver that connect this Android Device to Windows 10 x64 peer USB 2.0 cable. (If this driver does not work by you, write to me)
2. Universal Android Flash program, I downloaded from google.
3. Firmware in ZIP file format for M7350 downloaded from official TP-Link web page.
4. After installing drivers you can view your Imei and WiFi numbers.
What I have try do make:
I have try to upload to device the boot.img file that's in M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip with success, but my device is still locked on TP-Link logo.
Next step was to reboot the device from Universal Android Flash program, and it rebooted (means connection is ok). ADB Shell is working in Universal Android Flash, and normally also. I have try peer normal adb program to command:" adb reboot recovery" and then adb sideload firmware.zip but I get error "closed". I see all files on the device but I can not connect it from command line to WLAN, or update firmware.
What is the problem ?
Device use Qualcomm MDM9225 chip, files inside firmware:
appsboot.mbn ; qdsp6sw.mbn ; sbl1.mbn ; boot.img
I have seen that the same files are by flashing Qualcomm Phones by using QFIL.
QFIL is seeing this modem as ALCATEL HS-USB Diagnostics 9025 (COM7), I can also make an QCN Backup.
But not upload this firmware, because there is no XML data for this firmware.
Hours searching on google I have found some application there I could chose which files to flash.
Maybe someone has solved this problem, the driver from ALCATEL is ok, they use the same chip.
If moderator allows me to share some links and pics, I will re-write this post.
Thx 4 Help
Click to expand...
Click to collapse
I have the same problem. May you send me the links to the driver and I post it here?
Thank you very much!!!
I have same problem
hi
I have same problem too
I have Problem
hi bro
i'm not see download link , please check and allow and fix download link .best regards
Welcome to 4pda:
Code:
_ttp://4pda.ru/forum/index.php?s=&showtopic=669936&view=findpost&p=95895999
hw rev. 1-3
For M7350 I did:
1. Launched telnet;
2. The choice of usb compositions (with adb + ...);
3. Access by ssh, scp;
4. Installed sftp-server;
5. Fix ttl;
6. Access to AT Commands.
7. change imei;
8. and more ....
(Sorry for my english - this is google translator).
Please help me with Tecno f3 clone factory firmware
Hey guys i have the same problem and it solved with replacing the pmic (pm8019).
yakuzja said:
>> The first thing you all folks should know, that the modem TP-Link M7350 V 1.0 is an Android Device <<
All flies that I post here are to download from my personal account:
Download link: I'm a new user, and I'm not able to post outside links. Write to me for this files. (maybe moderator could allow me to share to mega upload link)
1. Alcatel_windows_10_x64_driver_M7350_TP_Link.zip
2. Android_AIO_Flasher.rar
3. M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip (copy from TP-Link website)
4. CKT Qwrite_Writer.rar
5. M7350(UN) 1.0_1.0.11 build 141126 Rel.1014n_User.zip (older firmware)
1. This file is a driver that connect this Android Device to Windows 10 x64 peer USB 2.0 cable. (If this driver does not work by you, write to me)
2. Universal Android Flash program, I downloaded from google.
3. Firmware in ZIP file format for M7350 downloaded from official TP-Link web page.
4. After installing drivers you can view your Imei and WiFi numbers.
What I have try do make:
I have try to upload to device the boot.img file that's in M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip with success, but my device is still locked on TP-Link logo.
Next step was to reboot the device from Universal Android Flash program, and it rebooted (means connection is ok). ADB Shell is working in Universal Android Flash, and normally also. I have try peer normal adb program to command:" adb reboot recovery" and then adb sideload firmware.zip but I get error "closed". I see all files on the device but I can not connect it from command line to WLAN, or update firmware.
What is the problem ?
Device use Qualcomm MDM9225 chip, files inside firmware:
appsboot.mbn ; qdsp6sw.mbn ; sbl1.mbn ; boot.img
I have seen that the same files are by flashing Qualcomm Phones by using QFIL.
QFIL is seeing this modem as ALCATEL HS-USB Diagnostics 9025 (COM7), I can also make an QCN Backup.
But not upload this firmware, because there is no XML data for this firmware.
Hours searching on google I have found some application there I could chose which files to flash.
Maybe someone has solved this problem, the driver from ALCATEL is ok, they use the same chip.
If moderator allows me to share some links and pics, I will re-write this post.
Thx 4 Help
Click to expand...
Click to collapse
Hi dear friend
I downloaded your files,but unfortunately my laptop doesnt detect modem through USB,please help me about it
Thanks
yakuzja said:
>> The first thing you all folks should know, that the modem TP-Link M7350 V 1.0 is an Android Device <<
All flies that I post here are to download from my personal account:
Download link: I'm a new user, and I'm not able to post outside links. Write to me for this files. (maybe moderator could allow me to share to mega upload link)
1. Alcatel_windows_10_x64_driver_M7350_TP_Link.zip
2. Android_AIO_Flasher.rar
3. M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip (copy from TP-Link website)
4. CKT Qwrite_Writer.rar
5. M7350(UN) 1.0_1.0.11 build 141126 Rel.1014n_User.zip (older firmware)
1. This file is a driver that connect this Android Device to Windows 10 x64 peer USB 2.0 cable. (If this driver does not work by you, write to me)
2. Universal Android Flash program, I downloaded from google.
3. Firmware in ZIP file format for M7350 downloaded from official TP-Link web page.
4. After installing drivers you can view your Imei and WiFi numbers.
What I have try do make:
I have try to upload to device the boot.img file that's in M7350(UN) 1.0_1.1.1 Build 150204 Rel.1023n_User.zip with success, but my device is still locked on TP-Link logo.
Next step was to reboot the device from Universal Android Flash program, and it rebooted (means connection is ok). ADB Shell is working in Universal Android Flash, and normally also. I have try peer normal adb program to command:" adb reboot recovery" and then adb sideload firmware.zip but I get error "closed". I see all files on the device but I can not connect it from command line to WLAN, or update firmware.
What is the problem ?
Device use Qualcomm MDM9225 chip, files inside firmware:
appsboot.mbn ; qdsp6sw.mbn ; sbl1.mbn ; boot.img
I have seen that the same files are by flashing Qualcomm Phones by using QFIL.
QFIL is seeing this modem as ALCATEL HS-USB Diagnostics 9025 (COM7), I can also make an QCN Backup.
But not upload this firmware, because there is no XML data for this firmware.
Hours searching on google I have found some application there I could chose which files to flash.
Maybe someone has solved this problem, the driver from ALCATEL is ok, they use the same chip.
If moderator allows me to share some links and pics, I will re-write this post.
Thx 4 Help
Click to expand...
Click to collapse
hello please i need the files
Related
Hi there,
it seems like ASUS just provided a firmware update on 2016-02-05, listed as ASUS MeMO Pad (ME176C_CX)Software Image Version: V 12.10.1.36(Android 5.0)For WW SKU only(Lollipop To Lollipop)* on the asus support page (no links allowed for me yet).
I got this update as OTA but it failed (without a useful note), now I try to update manually. I've downloaded the file and put it on an SDcard's root folder. When booting to recovery it is not installed automatically. Unfortunately adb sideload is impossible too (the device as not recognized by my notebook when in recovery mode).
Me device is not rooted an running V12.10.1.33 (stock).
Any suggestions?
Hello drohhyn,
I'll pm you the link for the drivers. That should help you with the issue that the device is not recognized by your notebook when in recovery mode. At the moment I am prevented to post links
load temporary recovery and flash the zip on the sdcard (make sure to delete first line on updater_script in meta-inf)
hi,
my micromax a1 was runnning marshmallow 6.0.1 when during a security patch update installation got stuck and failed to boot again. now just booting into "dead android with exclamation mark". upon pressing power button and volume up and going into recovery(Android stock recovery) menu , cant wipe partition or data as it throws error "E: failed to mount/ cache" errors..
upon trying to install with any SD card also throws same error.
then i tried to install through ADB, while connecting to PC , PC not detecting mobile in recovery mode but detecting in bootloader mode. with fastboot flash command (for installing TWRP/CWM) in bootloader mode, error coming as "sending recovery failed(unknown status code)" .
Kindly help...
same happened to me yesterday . do you find any solution ??
Hi there !
STEP 1: DOWNLOAD the FLASH TOOL from this this link :LINK TO DOWNLOAD FILE
It is almost 30 MB in Size. And EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) of your computer.
STEP 2: DOWNLOAD LOLLIPOP FLASH FILE
DOWNLOAD LINK FOR LOLLIPOP: HERE
After downloading this flash file EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) on your computer.
STEP 3: NOW INSTALL DRIVERS:
YOU NEED TO BE ON WINDOWS 7 TO INSTALL DRIVERS (WINDOWS 8 DOESN'T SUPPORT THIS DRIVER / PHONE IS NOT DETECTED)
DOWNLOAD DRIVERS from this link : HERE
EXTRACT AND INSTALL THE DRIVERS : Next next next and finish If you see an security warning ( a red coloured pop up ) choose INSTALL IT ANYWAY
IT IS RECOMMENDED YOU TO RESTART YOUR PC.
STEP 4:
Now we have Extrated /unziped 2 files. One is FLASHTOOLS and other is FLASH FILE and Extracted it or unziped it to Desktop or Somewhere.
One of it having the name SP_Flash_Tool_exe_windows_v5.1424.00 or open both folders then one of it having the flashing tool. OPEN THE FOLDER NAMED SP_Flash_Tool_exe_windows_v5.1424.00
it contains an application named fashtool.exe OPEN IT
NOW THE APPLICATION IS ASKING FOR SCATTER LOADING FILE
its a txt file which is on the extracted flash file folder
BROWSE it by clicking Button named Scatter Loading
click OPEN
STEP 5:
HERE IN THE DROPDOWN BOX, IT SAYS DOWNLOAD ONLY, CLICK ON IT AND SELECT FIRMWARE UPDATE ONLY.
IF YOU SELECT FORMAT + DOWNLOAD, THEN YOU WILL LOOSE IMEI NUMBER.
NOW CLICK DOWNLOAD BUTTON ( GREEN ARROWED BUTTON NAMED DOWNLOAD )
IN CASE YOU LOOSE IMEI NUMBER, THEN REFER HERE
STEP 6:
Now SWITCH OFF your PHONE and REMOVE BATTERY
STEP 7:
CONNECT your PC via USB CABLE
wait for the driver Detection.
THE FLASHING PROCESS WILL START AUTOMATICALLY you can See the progress in progress bar which is on bottom of flashing tool Application.
WHEN IT IS FINISHED DISCONNECT USB AND RESTART YOUR PHONE.
NOW YOU WILL GET LOLLIPOP UPDATE IMMEDIATELY.
NOW REFER HERE TO ROOT MARSHMALLOW
HIT THANKS IF HELPED
if link do not work here properly then just google 'canvas a1 stuck on startup' ... and follow link in associated with xda
Device is dead
My phone is neither switching on, nor charging.
I flashed the stock ROM due to some problem with the rooted device through SP Flash tools. It completed successfully, but the device is not switching on or charging.
KIndly help
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 G8xPlease help me to get this files ASAP as i have hard bricked the mobile, all partitions deleted
Procedure For Flashing/recovering your Garlic using QFIL/QPST Tool
REQUIREMENTS :
-A working PC.
-Qualcomm Drivers.
-QFIL Tools (I'd prefer and recommend ver2.0.05 as it is much more efficient than the newer ones) *Required .Net Framework 4.5 or higher
-ADB Drivers (just in case if your phone ain't bricked and you don't know how to boot into edl mode)
-N/M Full Firmware files (No the N-Firmware or M-firmware files provided by me).
-Back up your internal storage as this would wipe the internal (I prefer it this way)
-If you are using the QFIL 2.0.05, then you should install the tool.
-Extract the Firmware file and copy it to <directory where you installed qfil>/Qualcomm/bin/ this is to avoid sahara failed error.
-In simple words, keep the extracted firmware files inside the QFIL's folder.
-Connect your phone to PC and type in adb reboot edl in adb terminal to boot into EDL mode, or reboot edl in terminal emulator.
-If you have installed all drivers properly, your phone should be listed under Ports in Device Manager as Qualcomm Diganostic Device xx9008 (note this number, this is important) if your are getting 900E or 9003 (in case of bricked phone) you need to make it boot into 9008 mode using Deep Flash Cable (Guides to this will be provided soon, or you could just refer Google).
PROCEDURE :
-Open QFIL Tool.
-Once the phone is connected in EDL mode, it will show up under the ports (automatically selected, still if for any reason, open up and select port)
-Select Flat Build.
-Select the Programmer Path. It will open up the file browse window, go to the location where you have extracted the firmware and select Programmer_emmec_firehorse file.
-Select Patch File and select raw_unspare.xml file.
Now select Patch.xml.
-Click Download Button and flashing process will begin. Wait till it finishes and hold down your power button to boot your phone.
DOWNLOADS :
- Stock N Qfil
- Stock M Qfil
CREDITS : Athul
pritish1998 said:
- Stock N Qfil
- Stock M Qfil
CREDITS : Athul
Click to expand...
Click to collapse
Can you reupload Stock N Qfil?
Rose in YU YUREK∆ BL∆CK - TINNO p7201 | OFFICIAL
Tap here to view all notes in this chat.
t.me
user74354 said:
Can you reupload Stock N Qfil?
Click to expand...
Click to collapse
Notice this will VOID YOUR WARRANTY.
I am not to blame for BRICKED DEVICE.
Do this at YOUR OWN RISK.
Things you need :
1: OnePlus Nord N100 - Oxygen OS 11.0.5.BE83BA
2: Computer with Adb and Fastboot Installed - check google for adb and fastboot
3: Unlocked Bootloader - https://source.android.com/devices/bootloader/locking_unlocking
4: Adb Enabled in developer options aka USB debugging
5: The Boot.img - below
6: Magisk.apk - https://magiskmanager.com/
Guide :
Step 1: Patch Boot.img with Magisk
Open the magisk app and select Install>Select And Patch a File>Boot.img>Let's go
And then wait for :
Output file is written to
/storage/emulated/0/Download/magisk...img
- All done!
Press the arrow at the top and close Magisk for now
Step 2: Connect to the Computer with adb and fastboot installed
On Phone :
Allow the computer to browse files
On Computer :
Go in the file explorer to your phones downloads( This Computer\BE2013\Internal shared storage\Download ) folder and find the magisk...img
Copy the magisk...img to your desktop or any other folder if you can find it in Command Prompt(Windows)
Then Open Command Prompt(Windows)/Terminal(Linux)
Cd to your work folder(Desktop) or the "any other folder"
cd Desktop(Windows)
Step 3: Boot the device into bootloader
Do a check if the device is connected with:
adb devices
On phone :
Allow USB debugging
If nothing shows up on the phone or it says the phone is unauthorized reconnect the phone and try again.
On Computer :
Next we reboot the phone to bootloader with :
adb reboot bootloader
The phone will restart and you shall see a big START
Step 4: The Final Step Test & Install Root
Testing if everything works as expected eg Wifi, Bluetooth, Hotspot, Other stuff because these things broke for me once because I used the wrong version of boot.img.
Id still test them.
On Computer :
fastboot devices
If there is the same device as in Step 3 adb devices command all should be working expected.
Optional :
fastboot boot magisk...img Tip Use TAB to autocomplete in Command Prompt(Windows)
Next up test if all of the wireless stuff is working eg Wifi, Bluetooth, Hotspot, Other stuff
You can also open magisk to see if the device is Rooted.
Going back to bootloader is important for the next sub step("Flashing").
adb reboot bootloader
Flashing :
Did you boot the magisk...img?
If yes did everything work?
If not do not do this part!
fastboot flash boot magisk...img
fastboot reboot
Done!
Sorry for any typing mistakes if there is any.
If you have any questions ill be slow to respond if I even respond.
Sincerely Maxi
Where did you get this boot image?
I am getting the same behavior I get when trying to patch the global boot image - will not boot this TM model phone.
bouyakasha said:
Where did you get this boot image?
I am getting the same behavior I get when trying to patch the global boot image - will not boot this TM model phone.
Click to expand...
Click to collapse
I extracted the boot image from OTA update.
What do you mean with TM model phone? This is for the BE83BA.
hello someone does not have a rom 11.0.1be83ba I formatted the whole system unfortunately
Grilmama said:
hello someone does not have a rom 11.0.1be83ba I formatted the whole system unfortunately
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
https://otafsg-cost-az.coloros.com/OnePlusN100_EEA/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/patch/amazone2/GLO/OnePlusN100Oxygen/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/OnePlusN100Oxygen_14.E.25_OTA_0250_all_2203311235_0a17ce328283d7.zip
Hi. Anyone can you extract Oxygen OS 11.0.5. BE83BA boot.img for me? Thank you! Can't access PC.
VPH20 said:
https://otafsg-cost-az.coloros.com/OnePlusN100_EEA/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/patch/amazone2/GLO/OnePlusN100Oxygen/OnePlusN100Oxygen_14.E.25_GLO_0250_2203311235/OnePlusN100Oxygen_14.E.25_OTA_0250_all_2203311235_0a17ce328283d7.zip
Hi. Anyone can you extract Oxygen OS 11.0.5. BE83BA boot.img for me? Thank you! Can't access PC.
Click to expand...
Click to collapse
The post has been updated. It includes the updated boot.img.
Ma_x11 said:
The post has been updated. It includes the updated boot.img.
Click to expand...
Click to collapse
Thank you very much!