Related
Hi,
i've a rooted pixel 3, is there a way to enable diag port? Thanks
Yeah but manipulations are impossible. Like, if you're looking to use pdc tool to flash mbn files , just quit now.
Xdevillived666 said:
Yeah but manipulations are impossible. Like, if you're looking to use pdc tool to flash mbn files , just quit now.
Click to expand...
Click to collapse
Is it possibile to do things like enable volte? Thanks
tekno281 said:
Is it possibile to do things like enable volte, change imei or meid? Thanks
Click to expand...
Click to collapse
Volte has to be allowed by your carrier first. I had a first gen pixel and my carrier didn't support it for vllte. Contacted them and they pushed he settings from their end. I had to do some manipulation to trigger the proper mbn file and it ended up working.
However that was when debugging aosp vendor image from Google allowed diag mode . They don't now.
So short answer is no for enabling volte. In regards to the other stuff, I wanna say no as ell.
Imei spoofing might be an option
Meid, no idea
You can do the mods via magisk, but VoLTE must first be allowed by your carrier.
help
imei spoofing possible with that? because i'm in a country where the phone gets blocked by the imei, and i want to rewrite one. Yes it isn't legal but no other option instead of wasting my phone.
Xdevillived666 said:
Volte has to be allowed by your carrier first. I had a first gen pixel and my carrier didn't support it for vllte. Contacted them and they pushed he settings from their end. I had to do some manipulation to trigger the proper mbn file and it ended up working.
However that was when debugging aosp vendor image from Google allowed diag mode . They don't now.
So short answer is no for enabling volte. In regards to the other stuff, I wanna say no as ell.
Imei spoofing might be an option
Meid, no idea
Click to expand...
Click to collapse
imei spoofing possible with that?
luqman.mirza said:
imei spoofing possible with that?
Click to expand...
Click to collapse
Not that I'm aware of
Xdevillived666 said:
Not that I'm aware of
Click to expand...
Click to collapse
But you said you were able to connect with the qpst. so did it get detected properly or not? because i want to make some changes in qcn under qpst. and can you please confirm the steps exactly you followed to enable diag port.
luqman.mirza said:
But you said you were able to connect with the qpst. so did it get detected properly or not? because i want to make some changes in qcn under qpst. and can you please confirm the steps exactly you followed to enable diag port.
Click to expand...
Click to collapse
Phone and ports are recognised ,yeah but it doesn't open in qpst .like I can't modify anything. Only ever tried on pie . Haven't touched it on q. I followed pixel 2 qxdm thread where they have custom built magisk and module for it.
luqman.mirza said:
But you said you were able to connect with the qpst. so did it get detected properly or not? because i want to make some changes in qcn under qpst. and can you please confirm the steps exactly you followed to enable diag port.
Click to expand...
Click to collapse
lol...
just bcuz someone can connect in qpst doesnt mean theres not other security features in place that could prevent you from messing with qcn or imei.. functions are probably limited/restricted
luqman.mirza said:
imei spoofing possible with that?
Click to expand...
Click to collapse
imei spoofing is also illegal in many countries.. you tryna spy on someone or get free service lol
elliwigy said:
imei spoofing is also illegal in many countries.. you tryna spy on someone or get free service lol
Click to expand...
Click to collapse
for your information pal, i want to fix my imei which is showing something 0044 instead of my original one and there is no carrier detection as well. LOL
Also, i'm able to get detected in qpst via modem port and made a backup of qcn file and even to restore it as well but it says read-only memory and no changes were made. LOL
pixel 3 diag port enable is ok but when u re lock bootloader or factory reset every change made on qcn or qxdm will revert
luqman.mirza said:
help
imei spoofing possible with that? because i'm in a country where the phone gets blocked by the imei, and i want to rewrite one. Yes it isn't legal but no other option instead of wasting my phone.
Click to expand...
Click to collapse
hi luqman did u successfully spoofed imei on pixel 3 .i made it but after a factory reser it resets to some 00204000......numbers
BADAMI said:
hi luqman did u successfully spoofed imei on pixel 3 .i made it but after a factory reser it resets to some 00204000......numbers
Click to expand...
Click to collapse
I have the same problem the factory reset then those numbers but to fix it it’s just 20 seconds.
only problem is, when I flash CalyxOS on it, I can’t enter Diag mode.
do you know any way around it?
cant seem to root calyx, I just need to enter Diag mode in caly, or is there a way I can root caly?
Hello everyone...
i'm facing issue while enabling diag port on Pixel 4 xl.
when i write adb shell then ok... after that i write "su" it says permission denied...
Nouman0114 said:
Hello everyone...
i'm facing issue while enabling diag port on Pixel 4 xl.
when i write adb shell then ok... after that i write "su" it says permission denied...
Click to expand...
Click to collapse
When you execute "su", you should receive a popup on the phone where you have to grant superuser permissions. You have only a few seconds to reply by default. Check Magisk, Settings, Superuser, for these 3 options:
Automatic Response
Request Timeout
Superuser Notification
Make sure none of them are set to Deny or None.
dcarvil said:
When you execute "su", you should receive a popup on the phone where you have to grant superuser permissions. You have only a few seconds to reply by default. Check Magisk, Settings, Superuser, for these 3 options:
Automatic Response
Request Timeout
Superuser Notification
Make sure none of them are set to Deny or None.
Click to expand...
Click to collapse
dcarvil said:
When you execute "su", you should receive a popup on the phone where you have to grant superuser permissions. You have only a few seconds to reply by default. Check Magisk, Settings, Superuser, for these 3 options:
Automatic Response
Request Timeout
Superuser Notification
Make sure none of them are set to Deny or None.
Click to expand...
Click to collapse
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
TheInfiniteAndroid said:
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
Click to expand...
Click to collapse
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Master One said:
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Click to expand...
Click to collapse
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
Do you happen to know if there's a way to find it through Activity Manager, finding it hard to navigate
@TheInfiniteAndroid, sorry, can't help with this, don't know Activity Manager.
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
razenxd said:
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
Click to expand...
Click to collapse
You may want to try another profile in that case, as there is no other way to solve this.
Master One said:
You may want to try another profile in that case, as there is no other way to solve this.
Click to expand...
Click to collapse
Aah really? That sux
Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
razenxd said:
Aah really? That sux Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
Click to expand...
Click to collapse
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Master One said:
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Click to expand...
Click to collapse
That's what i'm doing at the moment.
No luck so far
On RN10 Pro my carrier works just fine, I already have extracted the .mbns from RN10 Pro's firmware but now i need to find which one is actually is using and a way to insert it to my device!
Master One said:
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Click to expand...
Click to collapse
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
treebaard said:
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
Click to expand...
Click to collapse
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, up to the step of my phone being recognized, as it isn't automatically recognized at all by qpst config. And since there is no faq of any kind on what to do if the phone isn't recognized by QPST, I'm stuck.
I presume the issue is that I don't see any ports listed in the ports view. But I installed the Qualcomm usb driver already, so not sure how to fix that
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
treebaard said:
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
Click to expand...
Click to collapse
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
PDC you will find it in the folder with the installed program QPST.
I did it. Sorry for my English.
Master One said:
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
Click to expand...
Click to collapse
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
treebaard said:
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
Click to expand...
Click to collapse
The QPST folks have nothing to do with this, maybe (I mean hopefully) @gardiol can comment on DIAG mode support in the current version of LOS.
Can this have anything to do with the MUIU vs. OSS vendor?
I'm still running an older version of ArrowOS with the MIUI vendor, but possibly the DIAG mode problem came up with the move to OSS vendor?
How to disable pocket mode on oneplus nord 2 5G. _I have a DN2103 version of oxigenOS V11.3 with android 11. This new "feature" has been activated without my permission and I don't see where to turn it off. Thanks.
You can't, the option doesn't exist (for now) in the Oxygen OS version of the Nord 2.
sirwuku said:
You can't, the option doesn't exist (for now) in the Oxygen OS version of the Nord 2.
Click to expand...
Click to collapse
You can already say that you have seen one that has pocket mode and that to deactivate it you have to go into developer options and uncheck the lock screen, the problem is that the phone is left without any security system (fingerprint, code, etc). OnePlus Spain, after an hour in the chat, we have not been able to find how to disconnect said screen without going into developer options. If you know of any solutions, it would be appreciated. Thanks for answering.
edulcorante1 said:
You can already say that you have seen one that has pocket mode and that to deactivate it you have to go into developer options and uncheck the lock screen, the problem is that the phone is left without any security system (fingerprint, code, etc). OnePlus Spain, after an hour in the chat, we have not been able to find how to disconnect said screen without going into developer options. If you know of any solutions, it would be appreciated. Thanks for answering.
Click to expand...
Click to collapse
The only way I was able to find is with a rooted device, as explained in this thread.
Basically you would go to your Phones files:
Code:
/system/etc/feature_list
Then add:
Code:
,\n {\n "featureName": "OP_FEATURE_ENABLE_POCKETMODE_SWITCH"\n }\n
to the list
Python + MTK client + update DN2103 A19 = working. Update from A19 to A20, ok, wipe data, plus +adb reboot fastboot + fastboot flashing lock= bootloader lock. In original recovery delete data and reboot. Install official update and no more re-rooting the phone, at least this one. I give it to a family member. The order of the bootloader lock is not exact, but if it is done after installing update 20 it is done with a single command.
How can I turn off pocket mode on a OnePlus Nord 2 5G with a DN2103 version of OxygenOS V11.3 and Android 11, Flip an image as it was activated without my consent and I cannot locate the option to disable it?
vinny000 said:
How can I turn off pocket mode on a OnePlus Nord 2 5G with a DN2103 version of OxygenOS V11.3 and Android 11, Flip an image as it was activated without my consent and I cannot locate the option to disable it?
Click to expand...
Click to collapse
Settings>Utility>Pocket Mode
In this case, the proximity sensor has failed. It was canceled and the problem disappeared.
For Android 11, go to "Settings > Utilities > Pocket Mode" to turn the feature off
geometry dash
Hello recently I tried to root my phone, wanting to fix ghost touch, I did something wrong and the phone stopped working, "Only official binary blah blah blah ..." popped up during startup, I decided to reinstall the official stock, the phone started working normally, even ghost touch repaired, I looked at the Root Checker application if I have root, it turned out not, which is all right, but when I want to add the card to google pay or open McDonald's applications, I get a message that the phone is rooted or was somehow rooted modified, what can I do in such a situation, please help me, I tried to install other stocks from other operators and restore the phone to factory settings: _ (
I saw one solution, probably in this forum where someone wrote to enable OEM Unlock and USB Debugging then disable and enable again, something like this, but I don't see OEM Unlock in the developer option, I know that with a failed root attempt, I somehow unlocked this option, but I don't remember how and I prefer someone to help me as best as he can, because I don't want to break anything anymore, I just want Google Pay to start working for me
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware
But I use official firmware from some Samsung firmware site, i think my bootloader is locked, anyway do you have any solves to make work google pay?
I tried to unlock OEM but this solution with data & time doesn't work for me.
Hey, when I go to Google Play Shop there is an information that my device isn't certified, I tried to register my ID Device and still doesn't work can It be a problem, because of that Google Pay doesn't work?
syonox said:
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware.
Click to expand...
Click to collapse
If i wait 7 days OEM option should unlock automatically?
Is it good idea to root this device correctly and use magisk to make google pay work good or for example root this device and then unroot to make work google pay?
Eco24 said:
If i wait 7 days OEM option should unlock automatically?
Click to expand...
Click to collapse
before you do this if odin says you are in custom mode backup all your data before doing this. no it wont automatically, first you have to go to odin mode and hold up for a bit until the screen shuts and shows the question (do you wanna lock your bootloader) you select yes once done if you are on custom it will bring up only odin mode before anything thats where u flash firmware, now that should get rid of the root, and then if u wanna disable oem connect to wifi disconnect date and time unselect automatically and go 7 days ahead and the option will appear.
How to check if i have custom mode and what i have to hold up?? please explain better because i don't know what i have to do
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"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"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .