Related
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.
You should be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.
BE81AA tools (global firmware):
ANDROID 10:
OOS 10.5.3
OOS 10.5.5
Mirror for first and last MSMs: https://onepluscommunityserver.com/
BE83BA tools (european firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.6
OOS 10.5.7
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@lsthps for testing 10.5.2 BA version on his device
OnePlus for the device and OS
Reserved
Worked great, thank you! Just one click and the device is back to life. Awesome!
Added MSM tool for global build (10.5.3 BE81AA).
So basically you can't flash convert a branded N100 to global software?
rafe83 said:
So basically you can't flash convert a branded N100 to global software?
Click to expand...
Click to collapse
Correct, you can't do that with this tool.
However, OnePlus 8 and 8T T-Mobile versions users have been able to flash global software via fastbootd, so if you're lucky enough same may eventually work for N100.
Do you happen to have the Metro branded MSM tool?
craznazn said:
Do you happen to have the Metro branded MSM tool?
Click to expand...
Click to collapse
Unfortunately no but feel free to DM me so that I can tell you how you can try to obtain it.
Added OOS 10.5.6 MSM (EU only)
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.
You should be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.
BE81AA tools (global firmware):
ANDROID 10:
OOS 10.5.3
Mirror for first and last MSMs: https://onepluscommunityserver.com/
BE83BA tools (european firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.6
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@lsthps for testing 10.5.2 BA version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
Can you add OOS 10.5.7?
Added OOS 10.5.7 (EU) and 10.5.5 (global) MSMs
yandere2016 said:
Can you add OOS 10.5.7?
Click to expand...
Click to collapse
Fyi you don't need latest version to unbrick your device, I just post them for the convenience of restoring to a newer build
So I've been trying to root my device and bricked it by using a process that won't work on my HD1907 T-Mobile Variant. Tried a few different methods and finally was able to get ADB/Fastboot to recognize my device as an "Android Device" by installing the OnePlus drivers for my phone. Well, now it's not working at all. Can't turn off the phone to get it into EDL since it just automatically boots up on it's own, but I can get it back into Fastboot mode. What sux is that I can't seem to get ADB to recognize the device anymore. Also, I haven't been able to use this method since my device shows up in Device Manager as an "Android Device", not the "QHUSB_BULK" that you mentioned in the post. Any tips on getting this method to work? Should I be able to just uninstall the OnePlus drivers and Install the Qualcomm drivers instead? Is there a way to get ADB to recognize my device and then try to flash a stock OS to the device that way?
Please, any advice would really be greatly appreciated.
Thanks, you are a lifesaver! I got myself into a weird position when trying to install Magisk (flashed the wrong boot.img) and this saved me. I got my phone from Amazon (listed as "OnePlus Nord N100 Midnight Frost Unlocked Smartphone, 4GB+64GB, US Version, Model BE2011") and although it was not the T Mobile variant, the pre-installed image lacked the ability to flash a local update (the gear icon was absent in settings -> system -> system updates). Now I have flashed stock Oxygen OS and all is well. As a side question, any clue what kind of weird build it may have shipped with?
can someone commen msmdownloader for realme x50 pro i downloaded other and they jist down wprk.
is it good for model BE2013?
THIS SAVED ME!
I just bought Nord N100 BE2011 from Best Buy (in California US)
I made the same mistake of extracting the updated boot.img 10.5.7 and patching it with Magisk without updating the rest of the system first. So the Boot partition was updated to 10.5.7 while the Oxygen OS and other modules were still on the stock 10.5.3
While the phone was rooted and I was able to install apps and google play etc.. the Phone and Voicemail Functions died with UI Error (SOFT BRICK)
This MSM Tool worked,
I did as the OP says, Download the File above (2.4 gb)
I downloaded the qualcomm drivers first from https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
then boot to edl using adb command:
adb reboot edl
Check to see if phone shows up in device manager as QDLOADER 9008. It is under COM ports
Then unplug the phone leaving it in EDL mode and run the MSM tool
when executing the MSM application it will prompt for login select: "other" from drop down
once the MSM program shows up plug in the phone
It should indicate that it is connected
press start.
On first attempt i received Error and followed the OP:
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
(to get it out of edl mode and into fastboot hold power and vol-up)
This worked and the download took 5 minutes.
Phone rebooted to factory settings (after being bricked) and I can receive calls
Cheers,
Alex
Hi,
Can I use this tool for Locked by Metro phone?
I received the Android 11 update and Wifi stopped working perfectly with constant drops. My version is EU, so I used this tutorial to revert to Adroid 10 and Global, and it worked perfectly.
Hi, could you add this unbrick tool for the oneplus nord ce 5G ? thanks
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2015 model with build tag BE82CF
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@absoluteparanoia for 10.5.8 MSM
OnePlus for the device and OS
Reserved
HI.
Can i Use another firmware(Global or EU)?
Thanks.
Today I decided to update Android 11. As my phone has been notifying me of system update every day. Updating went fine. I started rooting by downloading 11 Ota update for Europe. Magisk created patched file and i flashed file, like I did with Android 10.
This is where problems came: My phone will boot to somekind os where I have only two options when pressing power button(Power off and restart). Nothing on the screen, only power button menu works. So I did flash original 11 boot file and same thing happens. Only power button works.
To the topic: I did try this but some how my phone just wont go to EDL Mode. I have tried couple different drivers. MSMDownload tool won't find any thing. And Yes QDLOADER 9008 driver is installed. Only place I can use the phone is fastboot mode, atleast device manager finds it. If I boot anything else no connection.
I'm happy that my unlocked Nokia 6.1 still works. So I have no hurry, maybe some day someone releases working TWRP for this and I can flash something else to replace this Oxygen OS.
Edit: I finally managed to restore one of those restore images. Why it was not working before. Me and stupid com-ports. MsmDownloadTool should have changeable com-port setting or working autodetection.
Thank you sooo much I accidentally soft bricked my phone but got it working with this mthod!
When I use `adb reboot edl` - my BE2015 just restarts itself.
Any idea why I can't get into EDL mode?
Super legit!! I had rooted one phone then bricked it trying to put lineage on, then bricked another phone of the same model. This program came in clutch!! Only thing is I had to buy a windows laptop just to use it, but I got a 30;return policy
And I'm still gonna root these and try again.
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2015 model with build tag BE82CF
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@absoluteparanoia for 10.5.8 MSM
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
what if i do all of said steps. and my phone isnt detecting in edl mode i have a one plus nord n100 globally unlocked but i have access to recovery ... can i reinstall the boot img somehow .. thanks
For me I was able to get into edl thru twrp recovery. Just go boot twrp from recovery, then go to the reboot menu and select the option reboot in edl and if that don't work you can also use the adb command "adb reboot edl" if you unmount/disable the MTP.
Hi.
i hard-bricked my Redmi 9T while trying to flash a custom rom
i cant boot into recovery or fastboot, i only see "Qualcomm HS-USB QDLoader 9008" in the device manager when i connect the phone
when i try to flash the stock rom using MiFlash i get an error saying my account is unauthorized
i googled it and apparently what i need is a patched firehose file to bypass this authorization check, or get someone with an authorized account to help
i searched a lot but never found a patched firehose that works for my phone
if someone can give me some directions as to where i can find this file or how to patch the original myself, that would be great
Thanks!
Edit:
I ended up paying a russian guy to help me flash with an authorized account
he is MOD EDIT: Content Removed if anyone is wondering
i also contacted the guy.. didn't avail his services
but he passed my scam mockup.. he is legit..
Just buy Miracle Xiaomi Tool Login Edition and flash all rawprogram xml in edl (9008) mode
is there any free solution for this? i'm broke af and i have the same problem
same problem
AhmedSamir72 said:
same problem
Click to expand...
Click to collapse
hmmm...i dont own thhis device but i think u can try this way by miflash
First of all, ur device have to have the BL unlocked. Maybe also 9008 works.
download the stock ROM from here
remember to scroll down and download the .tgz file
after it finished, extract it
and open miflash (recommend version)
select to the folder u just extracted, and refresh (f in fastboot with BL unlocked, it shows ur device number; if in 9008, it shows as COM port.)
choose erase all (don't lock)
then just press flash
Hi, If you entered the engineering firmware mode (EDL) and can not flash the phone without a service account:
1. Download the firmware from here ENGINEERING ROM
2. Check that the device would be defined as Qualcomm HS-USB QDLoader 9008 in the device manager when connect the phone
3. Firmware using MiFlash engineering rom from paragraph 1
4. Loading to engineering rom
5. Overload to Fastboot mode
6. We flash the rom you need through Miflash
chiron001 said:
Hi, If you entered the engineering firmware mode (EDL) and can not flash the phone without a service account:
1. Download the firmware from here ENGINEERING ROM
2. Check that the device would be defined as Qualcomm HS-USB QDLoader 9008 in the device manager when connect the phone
3. Firmware using MiFlash engineering rom from paragraph 1
4. Loading to engineering rom
5. Overload to Fastboot mode
6. We flash the rom you need through Miflash
Click to expand...
Click to collapse
this method will damage imei ,best way is to find the No auth firehorse and replace it with the one inside firmware folder,then use miflash
I found a thread where he made a firehose programmer for this device.
Here's the link: https://forum.xda-developers.com/t/solved-i-need-help-edl-9t-lime.4385727/
The 3/2022 update from F(x)tec says it will be mere weeks to delivery, still nothing here!
Moderators emailed me after my last rant in another section - to you, I cannot reply from that email because the service only receives.
If there really is no activity on this device, at least periodically update the forum with a sticky with a dated status. Sure, I'm probably the only one who comes back in hopes of seeing some activity, but in case there are others, it is the least you can do. If the device is dead before arrival, say so!
When (if) this arrives, I plan to explore the different ROMS. F(x)Tec promised there would be at least three available: Ubuntu Touch, LineageOS, and Stock. I chose Ubuntu Touch, but I want to (safely) switch ROMS. While I am a developer, I have zero experience with Android development, so I can't whip it up myself. I need instructions, options, etc.
Will there be a TWRP or equivalent recovery? Can I back-up and restore the system without messing directly with ADB and fastboot? Does the Lineage team have any progress reports on porting to this device? Do they have one to work on? Will Stock be Android 12L? What other teams are creating or porting ROMS to this device? Will there be continued attention and updates for a few years? Will GSI ROMS work on this? Which variety?
Once again, I took this chance based on my perceived reputation of XDA. This is your phone, designed for geeks like me. Show me I am not playing a fool.
If it makes you feel better, upon arrival, I plan on porting as many of the different Android flavours as I can over to the Pro1X, along with sources. This includes TWRP.
My tracking number says it's currently in Alaska.
I just got mine and already broke it lul.
My fault for not taking a full backup image before messing with it.
@snortphome its not easily possible to brick this device.
Did you do the full recovery reflash using the provided EDL images?
Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)
NEW Version of guide here Below the original text:(above inserted by EskeRahn) If youre reading this, it seems like you miss the good old Android OS or youve accidentally fried your PrawnX already! Dont worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1...
community.fxtec.com
To flash using EDL and Linux:
Install EDL-Tool by berkele
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Put Pro¹ X in EDL mode using `adb reboot edl` when you got adb available. Else
Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.
If it is booting or showing fastboot, redo. I needed 5 tries first.
Check if the usb connected Pro¹ X is in EDL mode using lsusb, it should show:
`Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)`
Then become root or do the following with sudo each:
```
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .
```
If any of the commands get stuck, redo the finger combo and enter EDL again.
I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.
reboot prawn with
`edl --loader=prog_firehose_ddr.elf reset reboot`
F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon.
Above method is what testers used to install new firmware versions while no OTA mechanism was available.
eltmosen said:
@snortphome its not easily possible to brick this device.
Did you do the full recovery reflash using the provided EDL images?
Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)
NEW Version of guide here Below the original text:(above inserted by EskeRahn) If youre reading this, it seems like you miss the good old Android OS or youve accidentally fried your PrawnX already! Dont worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1...
community.fxtec.com
To flash using EDL and Linux:
Install EDL-Tool by berkele
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Put Pro¹ X in EDL mode using `adb reboot edl` when you got adb available. Else
Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.
If it is booting or showing fastboot, redo. I needed 5 tries first.
Check if the usb connected Pro¹ X is in EDL mode using lsusb, it should show:
`Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)`
Then become root or do the following with sudo each:
```
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .
```
If any of the commands get stuck, redo the finger combo and enter EDL again.
I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.
reboot prawn with
`edl --loader=prog_firehose_ddr.elf reset reboot`
F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon.
Above method is what testers used to install new firmware versions while no OTA mechanism was available.
Click to expand...
Click to collapse
Hi, thank you very much for your thorough instructions!
I'm sure they will be very helpful to both me when I mess something up more in the future and to others! I was not aware that EDL mode was existant, I was solely using fastboot.
As for me, it wasn't fully bricked, I still had the stock recovery (boot_a and boot_b were flashed over), and after a bit of hunting around, I found a google drive link (on the thread you linked, actually!) for the stock android on the fxtec community forums, as well as links to Ubuntu touch and SailfishOS builds which I was able to flash and achieve a usable operating environment.
I'm now having quite a lot of fun with this phone!
I got mine in my hands now. It already comes bootloader unlocked.
blackknightavalon said:
I got mine in my hands now. It already comes bootloader unlocked.
Click to expand...
Click to collapse
Have fun! And backup your persist partition to not loose the attestation keys by chance.
eltmosen said:
Have fun! And backup your persist partition to not loose the attestation keys by chance.
Click to expand...
Click to collapse
I've lost count of how many soft bricks I've had to fix on OnePlus devices alone. As long as I can back up my internal storage I'll be just fine.
abtekk said:
If it makes you feel better, upon arrival, I plan on porting as many of the different Android flavours as I can over to the Pro1X, along with sources. This includes TWRP.
Click to expand...
Click to collapse
It does. I'm hoping I like the phone and it lasts for years. I don't expect to replace my Pixel 6, and I want to see what all these other os's do.
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me
Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon
Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing
hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha
KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files
I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.
KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?
yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot
Damn!! I hope you find some way to fix your device. Good luck.
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?
yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)