Related
Hello Everyone,
The following steps can be used to enable MMOS mode on the Alcatel Idol 4S with Windows 10:
1. download and install WPAK. It can be found at http://forum.xda-developers.com/attachment.php?attachmentid=3860780&d=1472659433
2. extract the files of the attached zip and put them in the same directory as "ffutool.exe".
3. Start your phone in Recovery mode (lightening bolt and gear), and connect it to the computer. (the Idol 4S, this is VolUp & Power.)
4. now open a command prompt as administrator and navigate to the path where WPAK is installed.
5. run the following command: "FFUTool.exe -setBootMode 1 ProfileName" Where "ProfileName" is one of the following:
a. "Default"
b. "Factory"
c. "FactoryFullOS"
6. wait for the device to reboot. While it is booting, the startup screen will say "Not For Resale."
To disable MMOS mode, perform the same steps as above, but replace the command used in step 4 with the following: "FFUTool.exe -setBootMode 0"
FactoryFullOS is useful immediately after a flash and before first boot because it will skip OOBE and let you just use the phone. This is good to install Interop Tools and make changes to the device before OOBE is run. Once you disable it after making changes, it will run OOBE. FactoryFullOS also enables the Qualcomm ports so you can use QPST and other Qualcomm tools to interact with the radio.
Here is a list of optional features that may be enabled only when Manufacturing Mode is enabled: https://docs.microsoft.com/en-us/windows-hardware/manufacture/mobile/optional-features-for-manufacturing-mode
NOTE: the "ProfileName" for other devices can be found at the following registry key: "HKEY_LOCAL_MACHINE\System\ControlSet001\Control\ManufacturingMode" The subkeys that are listed are the names that are used by FFUTool.exe. (There is no space between the M and the a, but the forum keeps adding one for some reason)
Thanks for sharing this. Could be getting closer at more development for this device. I have never used this mode for Windows phones, can you give anymore insight or details on this? Like how to add features manually or check for what is enabled already? I do see it opens the diag port like you said. So it could be possible to back up the qc partitions which is good.
@nate0 This mode is typically used by device manufacturers for the testing and debugging of retail devices. I think in WP 8 there was a hard-requirement to remove this from pure-retail devices. In Windows 10 Mobile, it is not required to remove these from retail images. I haven't played with it much myself, but it should let you do things that you couldn't normally do like editing the BCD store. If you expand the registry key that corresponds to the MMOS mode being used, it will show you the customizations that are taking place when that mode is used.
Thanks. I was actually able to dump a qcn file from the T-Mobile model last night.
This mode also works on the Madosma Q601. Have only used "setbootmode 1 factory" successfully.
I've been trying to enable US LTE bands on it. Dumped the nv memory prior and had to restore it after using qpst as I inadvertently blanked out the imei on accident. Good news is that I successfully restored the nv modem settings from the dumped qcn file which restored defaults and the imei.
new ffutool please
Could you please kindly help to upload a new version ffutool.exe and its dll ffucomponents.dll ?
My version was built on April 2014. which might too old to have the setbootmode option.
Thanks
Code:
PS D:\ffutool> .\ffutool.exe
Usage: FFUTool -flash <path to FFU file to apply to disk>
FFUTool -uefiflash <path to FFU, flashed from UEFI directly>
FFUTool -wim <path to WIM to boot from RAM>
FFUTool -skip
FFUTool -list
FFUTool -massStorage
FFUTool -clearId
FFUTool -serial
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
Unhandled Exception: System.TypeInitializationException: The type initializer for 'FFUComponents.FFUManager' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'ufphostm, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
at FFUComponents.FFUManager..cctor()
--- End of inner exception stack trace ---
at FFUComponents.FFUManager.Start()
at Microsoft.Windows.ImageTools.FFUTool.Main(String[] args)
Code:
C:\Program Files (x86)\Windows Kits\10\tools\bin\i386>ffutool.exe -setBootMode 1 Factory
Logging SimpleIO to ETL file: C:\Users\XXX\AppData\Local\Temp\ffutool23024.etl
[Device 0]
Name : Nokia.MSM8926.P6204.1.1
ID : 00000011-728a-c92f-0000-000000000000
Type : SimpleIODevice
Failed to reset to specified boot mode. Error 2147483662At least one of the devices failed to execute the operation.
Failed on Lumia 640 LTE RM-1073
augustinionut said:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
Unhandled Exception: System.TypeInitializationException: The type initializer for 'FFUComponents.FFUManager' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'ufphostm, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
at FFUComponents.FFUManager..cctor()
--- End of inner exception stack trace ---
at FFUComponents.FFUManager.Start()
at Microsoft.Windows.ImageTools.FFUTool.Main(String[] args)
Click to expand...
Click to collapse
I am updating the first post with the two missing files. I don't know why they are missing!
i can't enter MMOS mode. when i try to enter factory mode, it just shows bluescreen on boot.
Hi to all! Like the title said, i'm trying to extract from 7T product partition img, then i want to edit it and re-flash it back.
Which is the fastest way to do so?
to get to the image you can use the payload dumper and unpack the payload.bin contained in the firmware pack then you have the produckt.img whether you can edit this or whether it also has write protection I cannot tell you unfortunately .
Maybe you can do this using the edl.py script that's available on GitHub.
This script allows you to use some of the qualcomm sahara protocol commands for stuff like reading and saving partition from the phone to your computer, or to write a partition from the computer to the phone internal memory.
Also with msm tool, you can enable the readback mode that allows you to backup single or multiple partitions (you just have to check the ones you want).
I hard bricked an LG G7 ThinQ G710EAW by flashing the wrong firmware (T-Mobile) onto it via LGUP. It now goes into EDL mode after shorting test points, but I'm unable to revive it by following this unbrick thread. Loading up the partition images via Partition Manager in QFIL "succeeds", but it doesn't revive my phone. Doesn't get me to fastboot. Still nothing on screen.
I also tried the rawprogram*.xml option using the XMLs in that thread, but QFIL keeps erroring out that the partition sizes defined in the XML are different from what it sees on the device.
The OP for the thread seems to not be active any longer.
Can someone here please help me understand how to recover my phone?
Anyone? Happy to donate for help as well.
Bumping up this thread.
If I had another EAW motherboard, would it help unbrick my motherboard? Wondering how I can fix my phone
So, I was able to finally figure this all out, recover my LG G710EAW and bring it back to life! It was a mix of information from many threads. No boxes, and no payment to anyone. All free.
The OP of this thread is active but has completely stopped responding to his thread and to his DMs - he's likely uninterested in a 4-5 year old phone at this point. In his first post he mentioned creating rawprogram* XMLs by hand, and it taking hour+ to do so. However, I'm unsure why it took him that long and in the end the files don't even work for QFIL since the sector size in the XMLs (512B) is different from device sector size (4096B). Nevertheless, I was able to flash these via command line 'edl' which ignored the sector size, but it didn't recover the device.
Generating rawprogram XMLs is easy if you can figure out how to run this Python program mentioned in this thread. However, the files attached there no longer work in 2022, the links are dead, and Python 2.7 is a dinosaur. Someone in that thread mentioned a different, fixed, repo but it didn't work with Python 2.7 for the 'undz' part. After a lot of head banging, I tried Python3 and 'undz' worked.
Here are the steps:
- Download the firmware for your model in KDZ format
- Install QPST
- Install Python3.x
- Run: pip3 install setuptools zstandard
- Download ZIP for kdztools from the repo: https://github.com/ErickG233/kdztools (or the attachment)
- Unzip kdztools and CD into that directory kdztools-master. This version is bug-fixed and also generates rawprogram files for us.
- Copy the firmware KDZ into kdztools-master directory
- Run: python3 unkdz.py -f G710EAW30e_00_0916.kdz -x. This creates a DZ file in a new `kdzextracted` folder
- Move the extracted DZ file from the kdzextracted folder back one level up, into kdztools-master dir
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -c
- This creates a dzextracted folder here with all the files needed to recover your phone. Now all we need are the rawprogram XMLs.
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -r. This will create all the rawprogram XMLs you need to flash. No patch files are created, but that is OK.
- In my case, QFIL complained it couldn't find file "PrimaryGPT_0.bin", so I copied file gpt_main0.bin_0 and renamed the copy gpt_main0.bin_0_copy > PrimaryGPT_0.bin
- Load your phone into EDL mode. If you want to use test points, see the image in this thread.
- Load QFIL. Use the ELF programmer file from any of the threads linked thus far. Select flat build. Load all rawprogram XMLs generated previously. Hit cancel when it asks for patch file XMLs.
- Hit Download.
This will recover your phone so it's able to boot and all. However, in my case, the phone had lost serial number and IMEI numbers (dual SIM) as well.
- To restore your IMEI numbers, you will need your QCN file or a backup of your FSG (fsg.img) partition from before bricking. In my case, I had flashed, via LGUP, T-Mobile firmware on my Indian phone. I then dumped all the partitions using command line EDL. I have not used QCN method since it seems to require a lot of steps to put the phone into diagnostics mode. I had a backup of the FSG partition, so I used that instead.
- If you have a backup of your FSG partition, load QFIL > Partition Manager. Erase modemst1 modemst2 and fsg partitions. Then, load the backup FSG.img file onto FSG partition. Restart phone.
- Now, if you have the serial number from your bill or box, see this thread to restore it. Pay extra attention to the Firehose configuration section, or else, it may create some issues. It's best to restore S/N after restoring IMEI in my experience, but this could just be some randomness or bad Firehose config during S/N restore.
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
urover said:
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
Click to expand...
Click to collapse
Any luck in recovering the phone ??
QFIL Helper is a console app created out of the necessity to automate the process of partition backup with QFIL utility. As one of the “lucky” owners of the sprint branded LG v50, I was faced with the grim prospect of making manual backup of every available partition, every time I’d want to upgrade, downgrade, tamper with the system files or mess with Magisk modules.
While researching this subject, I've stumbled upon this guide explaining in great detail how to use fh_loader.exe supplied within QFIL (QPST) utility. Then I've decided to take it one step further and automate the entire process…
QFIL Helper v1.0.0.559 (GitHub)
Features:
◆ Backup Partitions
Performs an automated backup of all available partitions.
COM?_PartitionsList.xml must be up-to-date.
Userdata will be skipped due to its size.
◆ Backup LUNs
Performs an automated backup of LUNs 0-1-2-4-5.
LUN0 backup will exclude Userdata due to its size.
◆ Backup hidden partitions
Some partitions, like DDR, CDT (LUN3), DevInfo, Limits (LUN4) are hidden.
QFIL Partition manager won't display them nor export to PartitionsList.xml.
QFIL Helper will attempt to locate and save those partitions.
Enter the following command line argument to enable this option: -hidden
◆ Backup hidden LUNs
LUNs 3 and 6 are hidden and won't show-up in QFIL Partiton Manager.
There's no possible way for me to calculate the size of these LUNs properly for every model of v50/G8.
QFIL Helper will ask the user to enter LUN number (3,6) and its size in sectors.
Use this mode only if you're absolutely sure you know what you doing.
Enter the following command line argument to enable this option: -hidden
◆ Backup: ABL, Boot, LAF, XBL
Quick backup of all boot related partitions.
◆ Backup: FTM, Modemst, FSG, FSC
Quick backup of vital partitons.
◆ Detect connected COM ports
QFIL Helper will continiously query Windows for all connected devices.
If Qualcomm HS-USB QDLoader 9008 is detected, then your phone is connected in EDL mode.
◆ Flash firmware
Restore your partitions backup.
Restore your LUN backup.
Flash 3rd party images like Engineering ABL.
Use command line argument to enable flashing of entire LUN images: -advanced
The app was tested with Android 9/10 and LG V450PM. It'll probably work with G8, G8X and V60 as well. This release seems to be stable, backup of partitions and LUNs works without any issues. Flashing single partitions like abl or boot should be safe, flashing entire LUN backups or system/vendor/product/OP is probably safe too. I've tested this with my own phone as much as I could, but you never know... Last thing I want is for someone to brick their phones, so I've added a command line argument: -advanced. Without it, the program won't flash LUN backups.
When flashing firmware, the files must be placed in the "Flash" subfolder and named in compliance with any of the following formats:
lun#_partition_$.bin | parition_$.bin | partition.bin | lun#.bin | lun#_complete.bin
For example:
lun4_abl_a.bin - will be flashed into LUN4, Slot A
abl_a.bin - will also be flashed into LUN4, Slot A.
lun4.bin - will flash entire LUN4
How to use:
Connect your phone to the PC in EDL mode
Launch QFIL and open Partition Manager
Click on "Save Partition File"
Leave QFIL running with Partition Manager open
Run QFIL Helper
Thank you god bless you, this is amazing
thank you so much for detailed notes.
please add some screenshots as well, it will be the cherry on the cake
Beliathal said:
QFIL Helper is a console app created out of the necessity to automate the process of partition backup with QFIL utility. As one of the “lucky” owners of the sprint branded LG v50, I was faced with the grim prospect of making manual backup of every available partition, every time I’d want to upgrade, downgrade, tamper with the system files or mess with Magisk modules.
While researching this subject, I've stumbled upon this guide explaining in great detail how to use fh_loader.exe supplied within QFIL (QPST) utility. Then I've decided to take it one step further and automate the entire process…
QFIL Helper v1.0.0.559 (GitHub)
Features:
◆ Backup Partitions
Performs an automated backup of all available partitions.
COM?_PartitionsList.xml must be up-to-date.
Userdata will be skipped due to its size.
◆ Backup LUNs
Performs an automated backup of LUNs 0-1-2-4-5.
LUN0 backup will exclude Userdata due to its size.
◆ Backup hidden partitions
Some partitions, like DDR, CDT (LUN3), DevInfo, Limits (LUN4) are hidden.
QFIL Partition manager won't display them nor export to PartitionsList.xml.
QFIL Helper will attempt to locate and save those partitions.
Enter the following command line argument to enable this option: -hidden
◆ Backup hidden LUNs
LUNs 3 and 6 are hidden and won't show-up in QFIL Partiton Manager.
There's no possible way for me to calculate the size of these LUNs properly for every model of v50/G8.
QFIL Helper will ask the user to enter LUN number (3,6) and its size in sectors.
Use this mode only if you're absolutely sure you know what you doing.
Enter the following command line argument to enable this option: -hidden
◆ Backup: ABL, Boot, LAF, XBL
Quick backup of all boot related partitions.
◆ Backup: FTM, Modemst, FSG, FSC
Quick backup of vital partitons.
◆ Detect connected COM ports
QFIL Helper will continiously query Windows for all connected devices.
If Qualcomm HS-USB QDLoader 9008 is detected, then your phone is connected in EDL mode.
◆ Flash firmware
Restore your partitions backup.
Restore your LUN backup.
Flash 3rd party images like Engineering ABL.
Use command line argument to enable flashing of entire LUN images: -advanced
The app was tested with Android 9/10 and LG V450PM. It'll probably work with G8, G8X and V60 as well. This release seems to be stable, backup of partitions and LUNs works without any issues. Flashing single partitions like abl or boot should be safe, flashing entire LUN backups or system/vendor/product/OP is probably safe too. I've tested this with my own phone as much as I could, but you never know... Last thing I want is for someone to brick their phones, so I've added a command line argument: -advanced. Without it, the program won't flash LUN backups.
When flashing firmware, the files must be placed in the "Flash" subfolder and named in compliance with any of the following formats:
lun#_partition_$.bin | parition_$.bin | partition.bin | lun#.bin | lun#_complete.bin
For example:
lun4_abl_a.bin - will be flashed into LUN4, Slot A
abl_a.bin - will also be flashed into LUN4, Slot A.
lun4.bin - will flash entire LUN4
How to use:
Connect your phone to the PC in EDL mode
Launch QFIL and open Partition Manager
Click on "Save Partition File"
Leave QFIL running with Partition Manager open
Run QFIL Helper
Click to expand...
Click to collapse
How do I make a full system backup including the currently installed firmware version? I would like to do this before I root the device. I have Global C61 and can’t find a full installer for reinstall of anything newer than C48. Thanks
I'm interested in this also....in addition, if you are on A11 with TWRP, when backing up do you select all partitions?
My choice (if you have the space) is to use EDL (or ROM bootloader on other devices) to do a complete save of your flash (as one file).
Ok, you might want to save all the partitions individually too, that will allow you to do rollbacks but keep the current userdata.
In the final analysis you can't do too much backing up (if you have the space).
TheGhost1951 said:
if you are on A11
Click to expand...
Click to collapse
I have A12, C61
Renate said:
use EDL
Click to expand...
Click to collapse
How do I do this?
Renate said:
save all the partitions individually
Click to expand...
Click to collapse
How do I do this?
Renate said:
if you have the space
Click to expand...
Click to collapse
You mean on my computer or on the phone? I have plenty of space in both locations, though
Just use Oneplus clone phone
I meant space on your desktop, flash drives, SD cards.
I'm not familiar with any specific OnePlus tools.
I just meant this as general advice for any device where you can get R/W access to the flash without actively using any of it at all.
That means EDL for Qualcomm devices, MTKClient for MediaTek devices, FEL mode for Allwinner devices...
DroidShift79 said:
Just use Oneplus clone phone
Click to expand...
Click to collapse
That's not what he wants. He's talking about NAND backup.
DroidShift79 said:
Just use Oneplus clone phone
Click to expand...
Click to collapse
Doesn't backup app data....
I can backup all partitions with MSM tool, just need fastboot script to "flash all" so that it doesn't have to be one img at a time.
Oh yeah, I got it wrong, sry.
SwiftBackup or titanium backup could help with apps and app data.
And if that's still not enough I would consider EDL/ MSM Tool
TheGhost1951 said:
I can backup all partitions with MSM tool, just need fastboot script to "flash all" so that it doesn't have to be one img at a time.
Click to expand...
Click to collapse
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
That could lead you in the right direction.
Saving the entire flash is the simplest, most bombproof and yes, least versatile way.
Of course you can save partitions individually also.
It's not even rocket science to make a script out of a partition listing.
You can also restore just fine with EDL, you don't particularly need fastboot.
Edit: See, I just backed up 32GB on my device:
Code:
C:\>edl /r /c61071327 nul:
Found EDL 9008
Configuring... Nope, configuring... Ok
Requesting read ... Ok, receiving 100% Ok
Now, where did that file go?
Renate said:
Saving the entire flash is the simplest, most bombproof and yes, least versatile way.
Of course you can save partitions individually also.
It's not even rocket science to make a script out of a partition listing.
You can also restore just fine with EDL, you don't particularly need fastboot.
Edit: See, I just backed up 32GB on my device:
Code:
C:\>edl /r /c61071327 nul:
Found EDL 9008
Configuring... Nope, configuring... Ok
Requesting read ... Ok, receiving 100% Ok
Now, where did that file go?
Click to expand...
Click to collapse
That's an approach i didn't know. Are you in the mood of writing a short step by step guide
The basics are getting into EDL mode and having your desktop EDL client.
The MSM tool is one client but as I've never used it, I'm not sure of its capabilities.
https://github.com/bkerler/edl is a Python imlementation.
Then there's my Windows implementation edl.exe that's in my sig.
On Windows I prefer using WinUSB directly instead of silly Qualcomm VCOM drivers.
Use https://zadig.akeo.ie/ and install WinUSB on 05c6/9008
You'll be needing a "loader" which is basically a replacement for SBL/XBL which does useful things.
A collection of loaders can be found here: https://github.com/bkerler/Loaders/
The correct one (if it exists) can be found automatically if you are using B. Kerler's client and you've downloaded everything.
If you're using my code the rest of this all deals with the specifics.
You can get the HWID and Hash and either manually look for a loader or ask me.
Code:
C:\>edl.exe /l
Found EDL 9008
Serial: 12345678
HWID: 000cc0e100000000, QC: 000cc0e1, OEM: 0000, Model: 0000
Hash: 7be49b72f9e43372-23ccb84d6eccca4e-61ce16e3602ac200-8cb18b75babe6d09
(That's a slash-ell up above.)
Then you look for something somewhere called 000cc0e100000000-7be49b72f9e43372
You download it and rename it something sane, like "phone.bin".
Code:
C:\>edl.exe /lphone.bin
...
Sending phone.bin 100% Ok
Waiting for Firehose... Ok
C:\>edl.exe /g
...
lots of partition listing
...
If that works, you have eMMC. If the /g part didn't work then you have UFS, in which case you can add /u to all commands: edl.exe /u /g
Look at the partition listing take the last partition and add the offset and count and you have the total number of sectors (either 512 eMMc or 4096 UFS).
Then just do the same command as up above.
Code:
C:\>edl.exe /r /c6107132 mybackup
You could also edl.exe /r /p1 partition1 or edl.exe /r /pboot boot.img.
And when you're done having fun edl.exe /z.
And if you have everything in one big 32, 64 or 128 GB chunk and you suddenly need to get a copy of the boot partition,
there are tools in Windows and Linux to chop that all up into partitions.
How do I properly exit EDL mode? I was stuck in it for a while, black screen no usb devices, but it eventually fixed itself.
Also I seem to be running into issues actually taking a backup: (Trying to back it up before trying lineage/crDroid, twrp fails to take an image as well)
Code:
K:\OnePlus9Pro>edl /l
Found EDL 9008
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
K:\OnePlus9Pro>edl /l9proloader.bin
Found EDL 9008
Resetting Sahara
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
Sending 9proloader.bin 100% Ok
Waiting for Firehose... Ok
K:\OnePlus9Pro>edl /g
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving...
Could not read device
K:\OnePlus9Pro>edl /u /g
Could not find EDL device
K:\OnePlus9Pro>edl /l9proloader.bin
Could not find EDL device
K:\OnePlus9Pro>edl /l
Could not find EDL device
Next Session:
K:\OnePlus9Pro>edl /u /g
Found EDL 9008
Configuring... Ok
Requesting info...
<log value="ERROR: [ffu]FWversion:903." />
Ok
No LUNs found
K:\OnePlus9Pro>edl /r /u /l 9proloader.bin
Found EDL 9008
Resetting Sahara
Unknown cmd 6d783f3c in packet
K:\OnePlus9Pro>edl /g
Found EDL 9008
<log value="ERROR: Failed to run the last command -1" />
Configuring... Ok
Requesting GPT 0 header... No response
ajolly said:
How do I properly exit EDL mode? I was stuck in it for a while, black screen no usb devices, but it eventually fixed itself.
Also I seem to be running into issues actually taking a backup: (Trying to back it up before trying lineage/crDroid, twrp fails to take an image as well)
Code:
K:\OnePlus9Pro>edl /l
Found EDL 9008
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
K:\OnePlus9Pro>edl /l9proloader.bin
Found EDL 9008
Resetting Sahara
Serial: f709f1be
HWID: 001350e100514d67, QC: 001350e1, OEM: 0051, Model: 4d67
Hash: a26bc25799770106-f32c2856606a87ad-9c1e997d25b5e80f-f30b0e47e4c85e15
Sending 9proloader.bin 100% Ok
Waiting for Firehose... Ok
K:\OnePlus9Pro>edl /g
Found EDL 9008
Configuring... Ok
Requesting GPT 0 header... Ok, receiving...
Could not read device
K:\OnePlus9Pro>edl /u /g
Could not find EDL device
K:\OnePlus9Pro>edl /l9proloader.bin
Could not find EDL device
K:\OnePlus9Pro>edl /l
Could not find EDL device
Next Session:
K:\OnePlus9Pro>edl /u /g
Found EDL 9008
Configuring... Ok
Requesting info...
<log value="ERROR: [ffu]FWversion:903." />
Ok
No LUNs found
K:\OnePlus9Pro>edl /r /u /l 9proloader.bin
Found EDL 9008
Resetting Sahara
Unknown cmd 6d783f3c in packet
K:\OnePlus9Pro>edl /g
Found EDL 9008
<log value="ERROR: Failed to run the last command -1" />
Configuring... Ok
Requesting GPT 0 header... No response
Click to expand...
Click to collapse
I have yet to get twrp restore from backup to work properly. I just had to MSM my phone back to stock and start over from scratch cause TWRP restore messed things up....
TheGhost1951 said:
I have yet to get twrp restore from backup to work properly. I just had to MSM my phone back to stock and start over from scratch cause TWRP restore messed things up....
Click to expand...
Click to collapse
I've had success with older android versions, but not with 12. Annoyed that OnePlus updated the OS on me without warning, I thought I was just installing the latest security updates.
Just hoping to make a proper backup before flashing a new rom.
tk_xda said:
How do I make a full system backup including the currently installed firmware version? I would like to do this before I root the device. I have Global C61 and can’t find a full installer for reinstall of anything newer than C48. Thanks
Click to expand...
Click to collapse
Idk if this is what you're looking for but I love swiftbackup you can download it on the app store for free and move the file to your computer once it's complete or if you pay the fee you can back it up to whatever cloud storage you have it's only like 5 bucks for lifetime I believe, if you have root it'll also back up your app data so it restores all your apps as if you've just signed into them, they did put a warning recently of Google authenticator but mine still restored from a previous version
Renate said:
I meant space on your desktop, flash drives, SD cards.
I'm not familiar with any specific OnePlus tools.
I just meant this as general advice for any device where you can get R/W access to the flash without actively using any of it at all.
That means EDL for Qualcomm devices, MTKClient for MediaTek devices, FEL mode for Allwinner devices...
Click to expand...
Click to collapse
Hello dear i want to know
Are you in window 10? I mean which edl script you used is this in win10?
And is is there anyway to get rw in os12? In os11 its easy task
And about dump i try unpack ops and flash via dump command its take time and in the end get error
And device also not booted
I use this commamd
Edl py w extract