Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
nappi90 said:
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
Click to expand...
Click to collapse
It seems to me that there is no EEA version for your device.
What code name, elish, dagu, enuma?
nappi90 said:
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
Click to expand...
Click to collapse
I guessed you downloaded and flashed the wrong firmwares/ROM to your device. This caused serious brick (the hardest brick) to your device. All the wrong firmwares have been flashed to every single partitions of your device. That's why your device can neither boot up nor enter fastboot mode. I got my Lenovo Yoga Tab 13 and some other Qualcomm devices into this serious brick. I got my Lenovo Yoga Tab 13 this brick by relocking bootloader. The only method that can fix your device error is to use QPST QFIL.
Requirements:
1.Windows 10 x64 preferred or above with WSL (Windows Subsystem for Linux) enabled. Because QFIL in QPST requires Sahara server (Linux) to run on your Windows.
2.Download and install HS-USB QDLoader 9008 driver for your Windows version.
3.Download and install QPST to your PC.
4.Download and unzip the correct fastboot ROM for your device to your PC. There are files with .img inside the zipped file. For example, boot.img, recovery.img and many others.
I am not sure if Mi Pad 5 Pro requires Provision process to flash via QPST or not? Some Qualcomm devices, for example Chuwi Hi Pad Pro, require Provision before getting permission to flash via Download mode using QPST.
Watch this tutorial to see the how-to-use-QFIL video. This video is quite old. There may be some chages in QFIL. You can google the newer tutorial about QFIL.
While your device does not show nothing but the black screen, follow the steps below:
1.Assumingly you have completed all the requirements above, open QFIL.
2.Connect USB from your PC to your device.
3.Load XML by matching all the files of rawprogram#.xml with patch#.xml. For example, If there are 6 files of rawprogram0.xml to rawprogram5.xml. You have to add rawprogram0.xml matching patch0.xml until rawprogram5.xml matching with patch5.xml to the Download list.
4.Press Download button in QFIL.
5.Hold volume Down (Some Qualcomm devices are volume UP and some are both volume at the same time) and press power button many times until the download process of QFIL starting up. This means your device has entered Download Mode.
6.Wait until the download process completed. Hopefully there is no error or no Provision process required.
7.Disconnect the USB from your device.
8.Your device should boot up showing Mi logo. If not, hold power button to try booting up your device.
Hope you can fix this. Or your device will turn into one of the most expensive paper weight.
Before step 3, i have to choose one programmer out of these:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In step 3 I matched one by one rawprogram and patch file, but in the box it only shows the last pair. Do I have to click every time on download e.g. I choose rawporgram1.xml and patch1.xml and then press download or do I match all of them first like below, then there is only the last one visible.
In the end I get some failed to open com port handle messages. Do you know where this comes from?
NOSS8 said:
It seems to me that there is no EEA version for your device.
What code name, elish, dagu, enuma?
Click to expand...
Click to collapse
unfortunately, it seems you are right... this is the reason.....
nappi90 said:
Before step 3, i have to choose one programmer out of these:
View attachment 5770983
In step 3 I matched one by one rawprogram and patch file, but in the box it only shows the last pair. Do I have to click every time on download e.g. I choose rawporgram1.xml and patch1.xml and then press download or do I match all of them first like below, then there is only the last one visible.View attachment 5770981
In the end I get some failed to open com port handle messages. Do you know where this comes from?
Click to expand...
Click to collapse
1.Choose prog_ufs_firehose_sm8250_ddr_5.elf
2.Have you enabled WSL on your Windows 10 or above? Read requirement #1 of my post.
siamese007 said:
1.Choose prog_ufs_firehose_sm8250_ddr_5.elf
2.Have you enabled WSL on your Windows 10 or above? Read requirement #1 of my post.
Click to expand...
Click to collapse
to 2: yes, i did.
About the rawprogram1 - rawprogram5: Do you know, if i need to download after matching each pair e.g. rawprogram1 = patch 1; click download; rawprogram2 = patch 2; click download etc.
nappi90 said:
to 2: yes, i did.
About the rawprogram1 - rawprogram5: Do you know, if i need to download after matching each pair e.g. rawprogram1 = patch 1; click download; rawprogram2 = patch 2; click download etc.
Click to expand...
Click to collapse
Add all the rawprogram0.xml to rawprogram5.xml matching with patch0.xml to patch5.xml files to the Download list at once and press download button.
My experiment:
I have put my Mi Pad 5 Pro 5G into Download Mode (EDL) and run QFIL > Partition Manager. QFIL cannot access the partitions of my device. This probably means my device may require Provision to do this. So it may mean yours requires Provision to flash the firmware with QFIL also.
Now it's come to my most fear that you will need the Provision file which is not included in the fastboot firmware/ROM. You have to ask this file from Xiaomi Customer Services. And your device's warranty has been voided since you have unlocked bootloader.
Try 1 of the following methods.
1.Ask someone who has the same device as yours to ask Xiaomi Customer Services for Provision file. Tell them you need the file to back up partition of your device. The Customer Services may ask the serial number and other info about that person's device for verify the customer warranty.
2.Ask Xiaomi Customer Services for the Provision file for your deivce by yourself. Tell them that your device got brick and can be accessed only by Download Mode (EDL) via QPST or QFIL.
3.Google to find the Provision file for your device on the internet. It's very difficult. I still cannot find the Provision file for my old Redmi K30 5G released in Jan 2020, around 3 years ago.
4.Google the method to work around your Sahara error. And hope your device does not need Provision to flash the firmware via Download Mode (EDL).
5.No offense. If you have extra money, buy the new one and ask Xiaomi Customer Services for the Provision file. Or buy Lenovo devices. They are not required Provision to flash firmware via Download Mode (EDL).
If you have the Provision file, ask me again of how to do Provision. Or google the way to do Provision on the internet.
Wish you best luck.
siamese007 said:
Add all the rawprogram0.xml to rawprogram5.xml matching with patch0.xml to patch5.xml files to the Download list at once and press download button.
My experiment:
I have put my Mi Pad 5 Pro 5G into Download Mode (EDL) and run QFIL > Partition Manager. QFIL cannot access the partitions of my device. This probably means my device may require Provision to do this. So it may mean yours requires Provision to flash the firmware with QFIL also.
Now it's come to my most fear that you will need the Provision file which is not included in the fastboot firmware/ROM. You have to ask this file from Xiaomi Customer Services. And your device's warranty has been voided since you have unlocked bootloader.
Try 1 of the following methods.
1.Ask someone who has the same device as yours to ask Xiaomi Customer Services for Provision file. Tell them you need the file to back up partition of your device. The Customer Services may ask the serial number and other info about that person's device for verify the customer warranty.
2.Ask Xiaomi Customer Services for the Provision file for your deivce by yourself. Tell them that your device got brick and can be accessed only by Download Mode (EDL) via QPST or QFIL.
3.Google to find the Provision file for your device on the internet. It's very difficult. I still cannot find the Provision file for my old Redmi K30 5G released in Jan 2020, around 3 years ago.
4.Google the method to work around your Sahara error. And hope your device does not need Provision to flash the firmware via Download Mode (EDL).
5.No offense. If you have extra money, buy the new one and ask Xiaomi Customer Services for the Provision file. Or buy Lenovo devices. They are not required Provision to flash firmware via Download Mode (EDL).
If you have the Provision file, ask me again of how to do Provision. Or google the way to do Provision on the internet.
Wish you best luck.
Click to expand...
Click to collapse
Thanks a lot for your big effort to help me. Seems like i need this EDL mode. Currently, i am in Beijing in lockdown and its not the best time to go around and find a mi customer service. Meanwhile, i look for a solution for the sahara problem (see point 4).
@siamese007 hi,
I tried your method to unbrick a Mi pad 5, but unfortunately an authorization is needed...
I am trying to ask Xiaomi help. I don't have any answer for the moment...
If I try to ask them the Provision file, what I should do with ?
Could you explain me your method ? Do you think it’s a file they’re capable of giving away?
Thank you in advance,
Nicolas
Heavymistick said:
@siamese007 hi,
I tried your method to unbrick a Mi pad 5, but unfortunately an authorization is needed...
I am trying to ask Xiaomi help. I don't have any answer for the moment...
If I try to ask them the Provision file, what I should do with ?
Could you explain me your method ? Do you think it’s a file they’re capable of giving away?
Thank you in advance,
Nicolas
Click to expand...
Click to collapse
Hello,
What happened with your device? Is your device Mi pad 5 nabu? Why can you not flash your device with Mi Flash Tool?
If you want to flash your device with QFIL in EDL mode, all Xiaomi devices require provision files to do it. Provision file is not supposed to be secret of company use only. Some devices have done provision for users at their factories. Otherwise users will be required to do provision by themselves. IMO provision files should be added to the firmware zip file for EDL mode.
For normal case, users can use Mi Flash tool to flash firmware. So Xiaomi might think provision files are not needed.
siamese007 said:
Hello,
What happened with your device? Is your device Mi pad 5 nabu? Why can you not flash your device with Mi Flash Tool?
If you want to flash your device with QFIL in EDL mode, all Xiaomi devices require provision files to do it. Provision file is not supposed to be secret of company use only. Some devices have done provision for users at their factories. Otherwise users will be required to do provision by themselves. IMO provision files should be added to the firmware zip file for EDL mode.
For normal case, users can use Mi Flash tool to flash firmware. So Xiaomi might think provision files are not needed.
Click to expand...
Click to collapse
Thanks a lot for your answer,
I brick my tablet by corrupting UFS files after a fake manip by following a tutorial. It is indeed a tablet pad 5 with as code name "nabu".
Only EDL works, i can't boot fastboot or recovery (black screen). Mi Flash tool needs a Xiaomi authorization to flash with EDL mode. I don't know if Xiaomi can give me a temporary permission for that ?
I tried to flash the ROM with QFIL in EDL but i had an error "Only nop and sig tag can be recevied before authentication.".
So I guess I have to get the file you were talking about to go further?
Heavymistick said:
Thanks a lot for your answer,
I brick my tablet by corrupting UFS files after a fake manip by following a tutorial. It is indeed a tablet pad 5 with as code name "nabu".
Only EDL works, i can't boot fastboot or recovery (black screen). Mi Flash tool needs a Xiaomi authorization to flash with EDL mode. I don't know if Xiaomi can give me a temporary permission for that ?
I tried to flash the ROM with QFIL in EDL but i had an error "Only nop and sig tag can be recevied before authentication.".
So I guess I have to get the file you were talking about to go further?
Click to expand...
Click to collapse
I tested with my device to access its partition tables but could not. And got error saying something about "authentication". So I guess yes you need to do provision before being able to flash the ROM in EDL mode with QFIL.
From my experience, the provision file is xml with some code to access the system on the chip that allows QFIL to flash firmware in EDL mode. Not sure if this provision for the SoC can be used widely across any devices with the same chipsets. You may look for the provision file from other devices with the same chipset as your device's. I will explain how to do provision later.
Related
So it looks like some of you really need help with unbricking your device - let me guide you.
This is my first Xiaomi device (K20 Pro) and i hard bricked it after 30h of usage.
fastboot locked and "your system has been destroyed" message - nice!
So yeah, i was looking for some unbrick methods and didn't found any, so i researched a bit and after a few hours it was done.
Unfortunatly this method isn't free - but it is the cheapest solution out there without a needed appointment - aka fully automated.
For the moderators: this is the one of few available services to authorize a EDL flash, it is the cheapest and the only automated service.
I do not intend to do any kind of promotion here. Once a free method or cheaper service will be available, i'll update the thread accordingly.
Step 1: Open your phone - take off the backpanel and mainboard shield
JerryRigEverything K20 Pro Teardown - https://www.youtube.com/watch?v=Sd6KpX5MRtI
Note: only top mobo shield needs to be removed, you can use a thin guitar pick instead of the razorblade (to prevent damage)
Step 2: Get your K20 Pro/Mi 9T Pro into EDL mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. First of all, unplug the battery connector (blue) from the phone.
2. Now short the 2 points (red) and keep them shorted.
3. Last but not least, plug the usb cable into your usb 2.0 port
(yes, the battery must be disconnected, yes, while doing so you must have the test points shorted)
4. Your phone should now show up in device manager as "Qualcomm HS-USB QDLoader 9008" or "QHSUSB_BULK"
5. if your phone appears in device manager as "QHSUSB_BULK", you have to install the proper driver before proceeding,
please check out this tutorial: https://xiaomibuzz.com/downloads/download-qualcomm-qdloader-usb-driver.html
Step 3: Flash your device
1. Make an account at https://s-unlock.com
2. Press "Add fund" in the main navigation bar
3. Add 15$ to your account, i prefer to pay via PayPal - this would be 0.98$ fees - so after fees you pay 15,98$
4. After clicking on "+Add Fund", you'll be redirected to an invoice where you can pay through paypal
(paypal express selected in payment gateway option) via the "Pay Now" button
5. now the necessary credits will be available in the credits balance in the main navigation bar
6. download and install the latest version of xiaomitool (v0.2 currently) here: https://xiaomitool.net/download
7. after installation is complete, open the program and copy the "Fingerprint" from the "Login Area" section
8. open the site where you can order the needed service for the edl flash https://s-unlock.com/users/server-order?server_service_id=172
9. paste the previously copied fingerprint from xiaomitool into the fingerprint input field of the website and input quantity 15 (just like shown on the screenshot)
Note: the username and password on the order site do not have to match your s-unlock user account, you can pick a different username/password - just remember them!
10. press submit - your credit balance on the s-unlock site should show 0 now - don't worry, your credits have been transferred to the xiaomitool account
11. Open xiaomitool again and login with the credentials you chose during the order process (see step 9)
12. after clicking login, the program connects to the server and shows your current balance of 15 credits
13. download the correct fastboot-firmware for your phone from here https://mirom.ezbox.idv.tw/en/phone/raphael/
Note: Chinese variant requires chinese firmware on locked bootloader, same applies to india, russia, eea (eu) and global.
14. extract the downloaded fastboot firmware through winrar
15. select the extracted firmware folder in xiaomitools
16. Press "EDL flash" - it should detect your phone as "Qualcomm HS-USB QDLoader 9008 Device" and request an edl authentication for 10 credits
17. confirm the popup - and the flash process starts if you did everything right
18. Congrats, you unbricked your device - and i'm sure you are able to reassemble it again by yourself
very detailed guide, thanks!
I have two questions,
how was your device bricked?
why does this work? why normal edl flash method wouldn't work?
IMTLD said:
very detailed guide, thanks!
I have two questions,
how was your device bricked?
why does this work? why normal edl flash method wouldn't work?
Click to expand...
Click to collapse
some pictures are still missing, but they'll be added soon.
i locked my chinese k20 pro while beeing on the eea rom, turned out that was a bad idea.
well, xiaomi requires an edl flash to be authorized, and they just do that for service centers for example.
regards
Great, thx.
That's it... I have no intention to brick my device, but is really nice to know that, if all goes wrong, we still has a last solution. This forum needs this tutorial...
Congrats.
Great tutorial bro.
why shouldn't we try authorised service centres first?
sanjib734 said:
why shouldn't we try authorised service centres first?
Click to expand...
Click to collapse
You can, but if you've bought the phone from a different region they will probably refuse to look at it. If they will look at it, they will charge more than the cost of s-unlock credits.
Nice tutorial , useful for someone in the situation that you was are in to.
I have one other question that you probably do not have the answer to.
If you flash using this method an for example GLOBAL rom on CN device, will it unlock all the bands?
Using this method does it flash the modem firmware? Because the 855 modem supports all the available bands, but some are disabled by software.
vasil_d said:
Nice tutorial , useful for someone in the situation that you was are in to.
I have one other question that you probably do not have the answer to.
If you flash using this method an for example GLOBAL rom on CN device, will it unlock all the bands?
Using this method does it flash the modem firmware? Because the 855 modem supports all the available bands, but some are disabled by software.
Click to expand...
Click to collapse
No. You cannot unlock radio bands by flashing the modem firmware. If it was this easy there would be no point to Xaiomi setting different bands for different regions.
I have a question about rom, the model of my redmi k20 pro is M1903F11A, during my research to get rom I saw that for this model would be rom Davinci and not Raphael, or am I mistaken? Does this process you describe only work with this raphael rom?
ZteRacerUser said:
I have a question about rom, the model of my redmi k20 pro is M1903F11A, during my research to get rom I saw that for this model would be rom Davinci and not Raphael, or am I mistaken? Does this process you describe only work with this raphael rom?
Click to expand...
Click to collapse
it is raphael - k20 pro.
This process can be also applied to other xiaomi devices, but would need other fastboot firmwares.
Regards
So we need to add credit if we need to flash again?
SkipperRyujin said:
So we need to add credit if we need to flash again?
Click to expand...
Click to collapse
yes, 15$.. its the cheapest solution available atm
Why this(Hard Brick) happened exactly?
last doubt before trying
Hello,
One last question, as I'm afraid of just spending another $ 15 and further increasing my $ 280 loss.
When you needed to do the procedure was your cell phone completely dead like mine? No bootloader, no fastboot, only black screen, no led on? Just being recognized in Window as QDloader 9008?
I am finding it very strange that my mobile is recognized as QDLoader 9008 without having to do the testpoint procedure. When I do testpoint nothing changes, continues QDloader 9008.
And another question, with $ 15 I only have one try? Or one flash successfully completed?
ZteRacerUser said:
Hello,
One last question, as I'm afraid of just spending another $ 15 and further increasing my $ 280 loss.
When you needed to do the procedure was your cell phone completely dead like mine? No bootloader, no fastboot, only black screen, no led on? Just being recognized in Window as QDloader 9008?
I am finding it very strange that my mobile is recognized as QDLoader 9008 without having to do the testpoint procedure. When I do testpoint nothing changes, continues QDloader 9008.
And another question, with $ 15 I only have one try? Or one flash successfully completed?
Click to expand...
Click to collapse
++1
ZteRacerUser said:
Hello,
One last question, as I'm afraid of just spending another $ 15 and further increasing my $ 280 loss.
When you needed to do the procedure was your cell phone completely dead like mine? No bootloader, no fastboot, only black screen, no led on? Just being recognized in Window as QDloader 9008?
I am finding it very strange that my mobile is recognized as QDLoader 9008 without having to do the testpoint procedure. When I do testpoint nothing changes, continues QDloader 9008.
And another question, with $ 15 I only have one try? Or one flash successfully completed?
Click to expand...
Click to collapse
it'll authorize first before flashing everything but it sends a package to test everything to the device before, otherwise i can only suggest to pick a USB2.0 port while flashing.
And yes, i think its also possible to enter edl mode through a modified usb cable. Give it a try, it should work if you flash your original rom -> rom the device came with.
Regards
Ok, thanks for the tips, I will try this weekend calmly and well rested :good:
Although I am not very confident as i do not know so far if may phone is in EDL mode at all.
ZteRacerUser said:
Ok, thanks for the tips, I will try this weekend calmly and well rested :good:
Although I am not very confident as i do not know so far if may phone is in EDL mode at all.
Click to expand...
Click to collapse
Let us know how it went, otherwise open it up and get it in tespoint manually again through the method described in OP - just to make sure you don't fail and have to pay for a second attempt.
Regards
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of incorrectly flashing your device.
Hey guys, similar to all of @Some_Random_Username's unbrick threads, here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N200 5G.
Important: This is only for the T-Mobile variant of the N200. This will not work on the factory unlocked variant and may or may not work for the Metro variant.
Downloads:
11.0.1.5.DE18CB
Original archive
Google Drive
7z format (thanks @edale1)
AnddoidFileHost
MEGA
zip format (thanks @nv270)
Rethink Files
Also available at https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Others" 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
Press and hold the 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:
@Some_Random_Username for help getting files and for the mirror
@edale1 and @nv270 for repacking and mirroring the files
@nache2001 for testing the tool out on his device
OnePlus for the device and OS
@Nache and others who have the unlocked version from the oneplus store and have the bootloader locked and phone bricked .. This version will not work with your phone as i just tried it myself today .. hopefully someone gets a hold of the msmdowmload from the tech support ..
patiently waiting for the unlock
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
xentonix said:
So just to confirm: For those of us with Tmobile version, this will install default rom from OnePlus and get rid of all the bloatware from Tmobile and technically make our devices be like they are originally purchased from OP?
And of course, in order to use this our bootloader needs to be unlocked?
Will this lock bootloader again?
And do we unlock it with same code we got from OP first time?
Thanks!
Click to expand...
Click to collapse
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
edale1 said:
My understanding is the T-Mobile MSM Tools will restore a T-Mobile variant phone to the state it was in coming from T-Mobile; meaning if you debloated the phone, the bloat will be back.
You can use the MSM Tools even with a locked bootloader.
If your bootloader is unlocked, I believe this will lock it. (it may SIM lock your phone again as well, unsure...)
I think the same unlock token will work, but I'm hesitant to say 'yes' without someone testing it first.
Click to expand...
Click to collapse
lzgmc said:
1. Nope, this will revert your device back to the T-Mobile stock ROM, including all the bloatware. Thsi does not convert your device into an unlocked variant.
2. This works whether your bootloader is locked or unlocked. If your bootloader is unlocked, using this tool will lock it again, and you will need to unlock it by flashing unlock_code.bin again.
Click to expand...
Click to collapse
Thank you!
I read an article that was bit unclear and pointed to this so I wanted to confirm.
Also, from everything else I gathered, there is still no way to flash Tmob variant with non Tmob rom?
I was interested to try LineageOS but that's not available also seems like.
Phone's too new still. I think we need the MSM Tools for all the variants available before someone can figure out how to flash one variant into another, and we currently only have the T-Mobile variant's MSM Tools.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
incoming August 176 patch
I have update installed.
You can use restore image on Magisk uninstall before you start. If you encounter problem, you can use original boot image and run "mock patch"
Install update and switch to Magisk when you're prompted to restart, and let Magisk to install in unused partition, and restart after finished
If you have problem with CTS after update, install riru from Magisk and download safetynet fix, and install in Magisk as well (you have to reboot twice)
I've successful restored my N200 phone several times using the MSM, but this most recent time it appears the process was interrupted and I get the following error when turning on the phone. I can not boot the phone back into EDL mode to run MSM tool again. Every 10 or so boots the phone will boot into fastboot instead of throwing the error. I tried flashing a backed up boot.img and super.img, but no luck getting past the error. Any way to recover?
automatic ddr failed
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
I got bootloader unlock code. I need SIM unlock "One Plus Nord N200 5G" by Metro. Help me!
towardsdawn said:
Thank you! I could only get this to work by:
Unplug phone
Open MSMDownloadTool, don't click start
Hold down volume up and down
Plug phone into USB 2.0 port
Release volume up and down, verify device shows up as QDLOADER in Device Manager
Click "Enum" in MSMDownloadTool
Click on the device in the list and click "Start"
Click to expand...
Click to collapse
I bricked my phone late last night and found this forum & thread; my problem was that each time my computer kept showing my phone as "Kedacom" until I scrolled through and found this post.
You guys saved my ass AND saved me a trip to T-Mobile too! I owe you guys big time!
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
bleezycheesy said:
I successfully flashed a metro-pcs device using the tool in this thread. I bricked my device using the dsu loader in developer options. "Oem unlocking" is greyed out. Can anyone point me to a good bootloader unlocking tutorial for this devicel? Is it possible to use this tool with a rom that has already been rooted? Thanks,
Noob here. One thing to note: device was not recognized in the beginning. I held vol up/down at the same time and then plugged in device. Although the screen was black, the device was shown as "connected" and had no issues flashing. After 300 secs, voila!
Click to expand...
Click to collapse
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
towardsdawn said:
You can try this tutorial. It worked for me on Tmobile, no idea about MetroPCS. Key line is
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
MSMDownloadTool wipes the entire device and relocks the bootloader if it was unlocked, it doesn't care if you're rooted.
Click to expand...
Click to collapse
Thanks for the reference. It worked!
why no have msm tool for global n200 be2117,
jasmok said:
why no have msm tool for global n200 be2117,
Click to expand...
Click to collapse
OnePlus doesn't seem to want to release it.
bleezycheesy said:
Thanks for the reference. It worked!
Click to expand...
Click to collapse
no it doesn't works on metro variant
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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
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
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: 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:
@drfsupercenter for testing 11.0.3 version on his device
OnePlus for the device and OS
I can confirm this works for the "unlocked" version that I bought at Best Buy. Thanks for posting!
Here is a question
Can I convert T-Mobile version to global this way?
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
No, you can't convert T-Mobile variant to unlocked one with this tool.
Some_Random_Username said:
No, you can't convert T-Mobile variant to unlocked one with this tool.
Click to expand...
Click to collapse
The scenario is like 8T.
I remember somebody alter the project code to cross flash.
I have to find out
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
THANK YOU!!!! My paperweight is a phone again!
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I bricked my phone messing with it after the recent update they pushed out to official phones which broke 5g. Maybe more people than I did, I was pretty happy until then.
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I don't know how he got it, but it does work.
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
I'd imagine it would be the same as when I tried to flash the T-Mobile MSMTool to my unlocked phone. It just said wrong model and wouldn't continue.
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
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
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: 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:
@drfsupercenter for testing 11.0.3 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
great thanks lol
googlephoneFKLenAsh said:
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
Click to expand...
Click to collapse
I changed everything related to project ID and everything in that post, but mine still says
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
The project code should be for N200 not other models
mingkee said:
The project code should be for N200 not other models
Click to expand...
Click to collapse
That's what I put.
I even control+f'd it for anything that says "2083c" or "ID" and "project", yet it still somehow got that error.
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
ok i'll do that in a bit and i'll probably release it here.
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
well
okay i give up
justauserthatusesaphone said:
View attachment 5653443
well
okay i give up
Click to expand...
Click to collapse
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
googlephoneFKLenAsh said:
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
Click to expand...
Click to collapse
I can't tell what's wrong.
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="0" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="anxKohPaJKUq2kVPIbXgD7RXNa96iUeGFZa1GzbYH6OIorf7RCneJCCgkJlSlN" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-77" BuildTime="1631716601" ApplicantIP="not sure if this is sensitive" />
Everything you listed is changed, the unlocked ops is also put into the tmobile msm
for example, here's the tmobile one
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="1" CarrierNoneEnable="true" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="CQLTBL0oxs4BM2pdtK1y8Q1rvzgUtd033KWDfU1dM3mh3bKuwJs4jrtcqa6iB7lERIP4kOf5RRmS16MxPDz74tjvRq" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-74" BuildTime="1626183302" ApplicantIP="eeeeeeee" />
You are a godsend. Thank you so much, this is exactly what I needed!!
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!
Hello !
I've discovered a new way to root oppo a5s ( CPH1909) after the new security update which removed the mtk-easy-su root
(NOTE : YOU WILL REQUIRE :
1- THE LATEST FRIMWARE UPDATE TO OPPO A5S
2- A PC / Laptop
3- MTK Client Tool -link will be sent here in comments <uploaded by me>
4 - mediatek driver auto installer (link is provided)
5 - SP flash tool <link is provided>
6 - a usb cable
6 - Scatter File (WILL BE UPLOADED HERE IN COMMENTS )
7 - Magisk Manager for your phone (v.26) <from github>
8 - UNLOCK BOOTLOADER USING MTK CLIENT TOOL (No data wipe needed + STEPS WILL BE PROVIDED HERE TOO)
9 - ( optional) MCT MTK BYPASS REV4 ( BUT DOWNLOAD IT IF THERE IS A PROBLEM FLASHING IN SP FLASH TOOL) + <link is provided>
NOTE BEFORE STARTING : If links have problems or it is inaccessible , please tell me to send new links in comments .
also , MAKE SURE YOUR DEVICE IS UPDATED TO THE LATEST VERSION (A.46) BECAUSE IF YOU FLASHED THE BOOT.IMG (you will know what does this file do here later ) WHICH IT IS FOR THE LATEST UPDATE AND YOUR DEVICE IS OLDER THAN IT , YOUR DEVICE MAY BRICK , AND I AM NOT RESPNSIBLE FOR ANY DAMAGES FOR YOUR DEVICE
but , if anything happens , tell me , i might help you .
BIG ULTRA NOTE BEFORE STARTING : If you will share these steps in your website, your youtube video, or anything else , please do not forget to mention the source !!!
So , let's start
STAGE 1 : PATCHING BOOT.IMG
1 - download the latest frimware here
2 - choose the latest version (a.46)
3 - after downloading and extracting the file , you will find many folders > Enter the folder (frimware) , find and copy the boot.img file to your phone
4- patch it by magisk manager
5 - copy the patched boot.img ( usually located in Downloads folder in your phone)to your pc ( note : you will need it later )
6 - replace the patched boot.img with the original one in the folder you have extracted the rom in ( but before it, please backup the original one in an external folder , and also change the patched boot.img to ( "boot.img")
Note : I uploaded the boot.img file if you want to save time instead of downloading the whole rom !
STAGE 2 : Installing MEDIATEK usb Drivers
7- open Mediatek driver auto installer
8 - while the program is opening , a window appears which asks yo if you allow the installer to make changes ... blabla , just click allow (ok)
STAGE 3 : UNLOCKING BOOTLOADER
(NOTE BEFORE STARTING : THERE IS NO DATA WILL BE LOST , AND DO NOT ENABLE THE OEM UNLOCK IN DEVELOPER OPTIONS , THE MTK CLIENT TOOL WILL GIVE AN ERROR DURING UNLOCKING , JUST KEEP IT DISABLED !!!!)
8 - After the program installed the drivers , go to MTK CLIENT TOOL , choose the device name ("OPPO A5S") , choose "UNLOCK BOOTLOADER"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9 - turn your phone off , and then press these keys (" VOLUME UP + VOLUME DOWN <<in the same time>> ") and plug your phone in using the usb cable , once you hear a sound from your pc ( the usb connection sound) , you can stop pressing , because the phone is in BROM mode ( which you can flash anything but when you unlock the bootloader first
10 - click "Start" button in MTK CLIENT TOOL in your pc , when you see messages appear on the right of the MTK CLIENT TOOL APP , DON'T UNPLUG YOUR PHONE !!!!
When the progress bar achieves 100% in the program , unplug your phone and press power button , if you found a warning message while booting , so , unfortunately....
YOU SUCCESSFULLY UNLOCKED YOUR BOOTLOADER !!!!! XD
So , do not panic if it appears !
The message will say (" your device is unlocked and cannot be trusted , rebooting in 5 seconds ") and then another message appears (" dm-verity error,
Your android system / device is corrupted, please select whether you want to boot in E10 mode or RESTART mode ")
It will give you two choices , you SHOULD choose the RESTART mode by pressing VOLUME DOWN , and tadaaaa your phone is booting normally and the data DIDN'T LOST AT ALL ( like me )
BIG ULTRA NOTE : IF THE WARNING MESSAGE DIDN'T APPEAR , SO YOUR BOOTLOADER ISN'T UNLOCKED Successfully , I ADVICE YOU TO DO THE STAGE 3 STEPS AGAIN AND KEEP AN EYE ON THE MESSAGES APPEARANCE ON THE RIGHT OF THE MTK CLIENT TOOOOL ( IF IT SHOWS THE DEVICE MODEL , THE PROCESSOR , ETC ) SO , CONTINUE THE STEPS UNTIL YOU FINISH STAGE 3 STEPS ! (as this error appears usually when unlocking bootloader)
STAGE 4 ( optional) : BYPASS
Note : you might need this stage if you found an error in sp flash tool (" VERIFIED BOOT IS ENABLED") as it is usually doesn't appear in an unlocked device !
1- open MCT MTK BYPASS , choose the chipset ( MT6765 )
2 - REBOOT your phone into brom mode ( vol up + vol down)
3 - connect your device and click start , and done !
Stage 5 ( the last stage) : Flashing
1- open SP FLASH TOOL
2 - locate the scatter file that I'll provide it in comments here !
NOTE ABOUT THE SCATTER FILE : the scatter file which comes with the frimware is CORRUPTED , I've tried to fix it and it worked !
because when I worked with this corrupted scatter file , it gave me an error while flashing !! , just editing it on my way has solved it anyway
3 - you will see a list of many files , just untick EVERY THING EXCEPT FOR THE BOOT.IMG (Make sure it is the patched one)
4 - BOOT your phone into brom mode (turn it off , press volume up + volume down , connect it with your pc)
5- once you hear the usb connection sound from your pc , click on "DOWNLOAD" button , and wait until a correct sign (√) appears in a window
6 - REBOOOOT
7 - let's Celebrate!
--thanks to the user @Anonymous V for being online when i applied these steps , he was answering every question i ask.
-- if you want anything , or need some help , type in comments here , and I and Anonymous V will be available .
(First time typing a thread )
IMPORTANT NOTE : Please put the boot.img + preloader.bin + the scatter file in a folder , then locate the scatter file using SP Flash Tool, Untick the preloader.bin to avoid bricking the device
ALSO , PLEASE DO NOT PUT THE BOOT.IMG AND THE SCATTER FILE AND FLASH THE BOOT.IMG WHILE PRELOADER.BIN IS NOT AVAILABLE IN THE SAME FOLDER , AN ERROR WILL APPEAR ( ERROR_INVALID_PRELOADER)
REPEAT : DO NOT FLASH PRELOADER.BIN , ONLY PUT IT IN THE SAME FOLDER WITH THE PATCHED BOOT.IMG AND SCATTER FILE, AND FLASH ONLY BOOT.IMG
Another note : Please install the MTK Drivers using MTK Driver Auto Installer + the drivers which comes with MTK Client Tool (UsbDK and choose your arch. 64bit or 32bit(86bit)
+Please ignore the x that i made in the MTK Client Tool screenshot
Thanks for @jimenezshown for providing this info !
MTK DRIVER AUTO INSTALLER : here
Scatter File : here
MTK CLIENT TOOL : here
MCT MTK AUTH BYPASS TOOL (uploaded by Mobile RTX website ) :here
SP FLASH TOOL : here
the patched boot.img file ( to save your time instead of getting the original file from the frimware (rom) and patch it , i thought that providing a patched boot.img by magisk app may help !) : here
note : it is patched by the latest magisk manager app (v.26)
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
Bruh
Just turn off your Windows Defender Real-Time protection and it will work
Just , patch it using Magisk Manager (v.26)
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
Get it from the rom file ( link is provided in replies) and patch it yourself from magisk manager , or you can get the patched boot.img file ( link in replies, too) and continue these steps as nothing happened
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
Also , try to open this program in windows 10
Because it did these steps using windows 10 , not 11
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Bro
I made this guide with all of its details to help advanced people , especially The Beginners
+ Bro, i concerned using MTK Client Tool to unlock bootloader , Warned people to backup the WHOLE DATA and flash the boot.img after patching (using SP flash tool)
But it is also a good point to flash any partitions if a brick happened or something else using SP flash tool
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
NOTE THAT I WARNED PEOPLE BEFORE DOING THIS
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
+ Why tf they backup the rom ?
as they can download the Flashable Official rom , and flash it using SP FLASH TOOL ( consider that you should untick preloader before flashing to avoid bricking your device)
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
@Anonymous V What are your comments about that ?
Zezo 089 said:
@Anonymous V What are your comments about that ?
Click to expand...
Click to collapse
actually he is just saying about what can you do using the MTK client tool not "what to do about it " and i dont know if he really read your tutorial because this guy " @Khalyl22 "
sounds that he just wants to sounds smart and also boring? i dont know why he said that but its better to give a long and detailed tutorial to give people more info and understanding about what to do to avoid error and to give comfort to people while doing it and i dont fcking know why he said that its not safe although you give all the necessary steps to avoid error while doing it including the warning " Please Backup you Phone before Doing This " and also i think his not aware about the MTK client Gui version which you used in your tutorial i recommend the Gui version for the people who cant handle the terminal version because they are afraid in getting error i think he is pointing about the MTK client terminal version which i often used, also bro there is a reason why he said backup your whole firmware before doing it and actually his right about that when you backup your whole firmware in your phone you can backup all the data,apps,system preferences,imei and other things which you can restore if the phone fcked up where as the stock flashable rom is different its because its already set by default or factory default by the manufacturer which means its back to old state when you bought the phone well it depends though if you dont care about the data in your phone you can just reflash the stock flashable rom and if you care about the data in your phone you can backup your phones firmware and use that later to restore your phone.
Mine doesn't want to let me enter in BROM mode, I can only hear a plug and unplug loop sound when I try to hold Vol UP + Vol down.