yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] TheGhost1951:
If I borrow my wife's phone long enough, I can get it. She has the same LE2127 9 Pro....🥴
[OnePlus 9 Pro] TheGhost1951:
Here you go....
[OnePlus 9 Pro] TheGhost1951:
if it works, let me know and include the steps you took....please!
[OnePlus 9 Pro] razercortex:
Hi all,

In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.
[OnePlus 9 Pro] TheGhost1951:
You successfully got rid of Target is IN with this? How do you check it?
[OnePlus 9 Pro] TheGhost1951:
Yaaaaaaa....!!!!!!
[OnePlus 9 Pro] razercortex:
You'll need to generate new unlock token after you flash this, otherwise you won't be able to unlock bootloader.
[OnePlus 9 Pro] razercortex:
Try to flash regular TMO MSM.
[OnePlus 9 Pro] Appreciative:
I'm so happy for you bro!!
[OnePlus 9 Pro] razercortex:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
[OnePlus 9 Pro] Nathanhenning:
Oh my god. I've been dealing with this stupid indian thing for months, I gave up on trying anymore. No matter what I did , I could never get a normal UNMODDED TMobile msm to run for me.

But I got it now.

Followed the steps above. Unlocked bootloader, went into fastbootd and flashed the param.bin from above, and immediately after that I shut the phone off right from fastbootd mode. Started my TMobile msm tool , plugged it in and we are good!
[OnePlus 9 Pro] Nathanhenning:
I'm shocked at how easy of a solution this was, I was trying so many other long drawn out trial and errors and it was truly this easy
[OnePlus 9 Pro] TheGhost1951:
hold on...
[OnePlus 9 Pro] Appreciative:
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.

It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time
[OnePlus 9 Pro] TheGhost1951:
Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!
[OnePlus 9 Pro] razercortex:
I'm going to refrain from doing so because it can potentially cause side effects, but if anyone wants to do so, by all means.
[OnePlus 9 Pro] Appreciative:
At least we know it's possible now. Do you think we need a pure virgin new in box param or do you think there are specifics to the device and that's why he ( @razercortex ) needed persist also? (I was under the impression that persist was device specific)

I also understand your reservations @razercortex, I suppose we can point people here when it comes up, they can read the thread and understand the risks. I'm not stuck on IN but I knew it was possible to undo something the msm package did and I'm glad to see @TheGhost1951 was finally able to undo it. I knew he felt the same way about undoing whatever was done by the IN msm. Maybe someone can piece together a custom repair msm using a virgin param...but maybe I'm getting ahead of myself
[OnePlus 9 Pro] razercortex:
I believe persist and param are both device specific, one holds calibration and FP stuff, the other holds a custom unlock_code you need to flash. That's why I didn't want to freely advertise it.
[OnePlus 9 Pro] TheGhost1951:
The one thing I don't understand is, if your TargetID is IN, and you take an original TMO MSM tool and MOD the settings.xml to target the India profile, why wouldn't the TMO param.bin file correct it back to TMO..... hummm
[OnePlus 9 Pro] TheGhost1951:
the virgin TMO param.bin flashed in fastbootd works. After flashing my phone with my wife's param.bin I was able to use the pure TMO MSM tool and it worked. Saw my TargetID as TMO.
[OnePlus 9 Pro] Nathanhenning:
I can 2nd that it works, Atleast to the point of knocking the IN targetid off the phone thus allowing it to use the original MSM tool for tmobile. What I did notice was that when i went to go use my unlock_code file from a few months ago, The phone rejected it. So i went on the website to get a new one, It obviously gave me the one i already had which doesnt work.

I'm curious if it can be done where, If you dont have you orignal files backed up, and you use a fresh param.bin and maybe even the persist file if you can get the unlock_code file to work again..
[OnePlus 9 Pro] TheGhost1951:
go to fastboot mode and get the unlock code.... you will find that when you apply for a new token that it will say serial or unlock code invalid. Email support with all the information, model, serial, email, and the new unlock code and ask for a new token explaining the website rejected your information.... also the second part with question is something to think about. But is persist device specific?
[OnePlus 9 Pro] Nathanhenning:
Awesome. Thank you for that info.

Is the persist.img something that should also be flashed, or do you know if the param.bin once flashed will fix whatever else is off ?

Cause I only did the param.bin and as far as I can tell anyway.. everything seems fine on the network and use of phone anyway
[OnePlus 9 Pro] razercortex:
I wouldn't recommend flashing that persist.img, I've been told it contains calibration data that's unique for every device.
[OnePlus 9 Pro] Nathanhenning:
Good to know. I appreciate it.
[OnePlus 9 Pro] Appreciative:
This is interesting to me in the following way:

If someone created a custom msm that was essentially changing persist and or param (and potentially boot or abl.img) to a phone with a known-working unlock.bin, if then that person could use that bin to unlock the bootloader, root, and drop their originals back in after the fact. Something of a Tmo-branded bootloader bypass that could work outside of the Eu bypass and potentially other versions of Android after 11 if the custom A13 msm becomes a reality.

Does anyone know with certainty if the unlock.bin generated is purely handled by boot.img, param, persist, abl, or a combination of these things? I would assume not only boot.img because they generate them from the imei which wouldn't be stored there. Although it's possible they just use the imei for their own lookup on the unlock.bin database. Even tho our device already has the Eu oos11 bootloader bypass available, it could be good info to know for the future or for someone in a different case.

🤔 I'm waiting for the right deal to pop up on another le2127. Something I can play around with for thoughts like these ... and not have any downtime on my daily driver. I am interested to see if flashing a newer/older abl (say from f.17) would function at all in A11/12. Or one from A12 function in A11/13. If anyone has already tried these things, please tag me and let me know
[OnePlus 9 Pro] razercortex:
Param is what has the unlock code. You would need to flash one param and then you could theoretically have a universal unlock bin unless it's calculated with something else in conjunction with param.
[OnePlus 9 Pro] Appreciative:
Any idea how much identifying/device info is in param? Imei? Serial? Hw serial (the one used for sim unlock)?
[OnePlus 9 Pro] TheGhost1951:
Why couldn't the param.bin from an original TMO MSM tool be used to fix the India TargetID? Also, does anyone know how to display the TargetID of phone without using the MSM tool to flash the phone? Getting weary here from too many phone setups....... especially with my main everyday phone.
[OnePlus 9 Pro] TheGhost1951:
Incase anyone wants to try this param.bin! I just flashed it in fastbootd mode and everything on phone is working normal..... just trying to help out everybody! If it works for you please post back if it works to get you off of the TargetID IN.......
[OnePlus 9 Pro] Nathanhenning:
I think somewhere in my phone it still thinks it's indian brand. Only reason I say this is because I get the ad for red cable club, and unless I'm mistaken, that's an Indian thing.

Everything else works.
[OnePlus 9 Pro] TheGhost1951:
I don't get the ad.....
[OnePlus 9 Pro] razercortex:
The param.bin from the OG TMO MSM won't work because it's BLANK.
[OnePlus 9 Pro] razercortex:
So instead of providing a target ID at all, it will simply report "no valid trg id".
[OnePlus 9 Pro] TheGhost1951:
ahh, ok, thanks for the input..... are all MSM param.bin files blank? I am learning for an old man.....:) if that is the case about the MSM tool param, then how did the targetID get changed to India in the first place?
[OnePlus 9 Pro] razercortex:
Yes, unfortunately all of them are blank. The reason you get IN as target is because MSM writes information to param after flash completes
[OnePlus 9 Pro] TheGhost1951:
humm.... The biggest problem here is TMO requiring a token to unlock the bootloader.... that hinders us from playing around with solving issues. I tried getting away from the branded (TMO) phone (after flashing a TMO param.bin) flashing a stock TMO MSM tool then flashing a modded Glo MSM tool to flash over TMO. Everything went fine until updating to OS 12 then started losing cell signal. Tried flashing the TMO modem but even that didn't help. So ended up flashing back to TMO unlocking the bootloader before doing so. The modded MSM I used does not re-lock the bootloader....
[OnePlus 9 Pro] luckylui:
OOS 11 and 12 you need the Magisk Data Retention. Not needed on 13.. I have a 2127 converted to 2125 and it's on OOS13.
[OnePlus 9 Pro] TheGhost1951:
ok guys, had reverted back to the IN variant a while back, just tried to flash the param.img in fastbootd mode, but it didn't work this time. Trying to figure out why. Any ideas?
[OnePlus 9 Pro] TheGhost1951:
OK, finally flashed a param.bin, but it changed the unlock code. I am intouch with OnePlus support for a new token to unlock the boot loader. After flashing the param.bin, I used the TMO 11.2.3.3 msm to flash and it worked. Just to make sure all was good, I flashed the 11.2.6.6 TMO msm and it worked... so I am fully TMO variant and just waiting to unlock the bootloader... Yaaaaaa!
[OnePlus 9 Pro] Appreciative:
I don't know if my param changed since I flashed EU a few times and currently on EU. But if it could help you, I can pull my param and give you my unlock.bin to test that idea. I don't know for sure if it's tied to imei and serial outside of param or not
[OnePlus 9 Pro] TheGhost1951:
It is. Unlock code, serial IMEI and possibly the PCB number.... But thanks for the offer. I should have the token in a few days....
[OnePlus 9 Pro] TheGhost1951:
Don't know why TMO has to require an unlock token to unlock the bootloader. Kind of silly I think.
[OnePlus 9 Pro] TheGhost1951:
getting an error when trying to flash unlock_token....

FAILED (remote: 'Error - Verify Failed ! (6:-2)' oneplus 9 pro

Corrupt token maybe?
[OnePlus 9 Pro] TheGhost1951:
this is the full text when trying to flash unlock_token

C:\adb>adb reboot bootloader

C:\adb>fastboot devices

bf389d13 fastboot

C:\adb>fastboot flash cust-unlock R2_Token.bin

Warning: skip copying cust-unlock image avb footer (cust-unlock partition size: 0, cust-unlock image size: 288).

Sending 'cust-unlock' (0 KB) OKAY [ 0.002s]

Writing 'cust-unlock' FAILED (remote: 'Error - Verify Failed ! (1:-2)')

fastboot: error: Command failed

C:\adb>

any ideas guys.....been searching but haven't come up with anything
[OnePlus 9 Pro] TheGhost1951:
Just asking, what all is in the param.bin....anyone know?
[OnePlus 9 Pro] coquettto65:
does anyone know why my 9pro 2127, wake up when is off, in the last update 13.1 june version? any one with this problem?
[OnePlus 9 Pro] TheGhost1951:
My LE2127 with stock TMO A13 has done it a couple times in the past..... But not a recurring issue... Don't know why.
[OnePlus 9 Pro] Appreciative:
You may have an alarm set with this feature turned on?
[OnePlus 9 Pro] coquettto65:
I will .....check out
[Google Pixel 6] sukiheaven:
Hello I wanted to pass to android 13 (rooted) from anrdorid 12 (rooted). I followed this tutoriel :

and find out that was not the good method...

After that i had a "you're device is corrupted" and the google logo staying on my screen.

I tried to go on the android recovery and "wipedata/factory reset" but it didn't work :

View attachment 5841267

I don't know what to do now and i'm lost. Did i just lose my phone ? Can somebody help me ?
[Google Pixel 6] yyz71:
I suggest using Android flash tool to fix it
[Google Pixel 6] yyz71:
Android Flash Tool

flash.android.com
[Google Pixel 6] sukiheaven:
Thank it worked !
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
View attachment 5841235

KernelSU for Nubia Z17 Based on Android 13

Overview of KernelSU

KernelSU is working in Linux kernel mode, it has more control over userspace applications.

Only App that is granted root permission can access `su`, other apps cannot perceive su.

KernelSU supports modify /system systemlessly by overlayfs, it can even make system writable.

More information: KernelSU Official Website

If you do not use modules or only use simple modules, KernelSU is not detected by default. You don't need to worry about hiding root, because the default is hiding.

(As shown in Figure 3, "Zygisk on KernelSU" module will let you loss hidden root.)

Choose one of the two download methods

Download(Github release)(stable)

Kernel HERE (Include a default one and a permissive one for GSI user)

Manager APK HERE (just download apk like this KernelSU_v0.5.7_10866-release.apk)

Notice that: I tested the Github release kernel and I wrote the system I used.

View attachment 5918547

Please use the same system

(Optinal, but if you have bug may be your system is not match to my kernel)

Download(not recommend)(GitHub actions)(latest)

Kernel HERE

Manager APK HERE

Install Guide

Backup your boot.img, If something wrong, flash your original boot.img. You can get it in /dev/block/by-name/boot or your ROM.zip.

For nubia z17 (nx563j), It may work on

LineageOS 20.0(may work)

PixelExperiencePlus13(I tested)

other ROMs based on LineageOS 20.0 kernel(may work)

Use TWRP flash the kernel(boot.img) given by me.

OR use "fastboot flash boot boot.img" flash the kernel(boot.img) given by me.

Install the KernelSU's manager.apk.

Enjoy it.

Thanks

LineageOS Project

KernelSU Official Website

BugReport

@Dispossible

酷安@霁月难逢彩云亦散
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] 0157horst:
sorry can i get a link to directly downloading?
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] 0157horst:
and also for manager ... ;)
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] 0157horst:
and aljoscha81@ ...... ;)

would also thank you ... ;)
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] 0157horst:
don't know why my old member name is now shown..0157horst you know ;)
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
I will add a easier download guide
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] 0157horst:
maybe a new hoster not git you know ;)
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
Add sourceforge download link.
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] dd805bb:
How do you install the lsposed module? Like magisk but flash in kernelsu?
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
As shown in figure 3.

Use zygisk on kernelsu https://github.com/Dr-TSNG/ZygiskOnKernelSU/releases

And lsposed on zygisk (zygisk version) (not riru) https://github.com/LSPosed/LSPosed/releases
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] dd805bb:
Do you get a systemless host module running? Looking for how to get Adaway up and running.
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
Maybe the same as Magisk. I install a host module to prevent MIUI update, it just for test. I just copy a module randomly from another phone.
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] RealMooni:
Is it also work on OneUI 5.1? I have that kernel name: 5.15.41-android 13-8-25800099-abS918BXXU1AWC8 #1 Fri Mar 24 09:14:54 UTC 2023

My device is Samsung Galaxy S23 Ultra

Thanks in advance
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] nicky-xda:
Have you found a solution?
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] theoneofgod:
Module for KSU
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
@dd805bb @nicky-xda @theoneofgod

Here is the same module as in the picture.

download and edit /system/etc/hosts in the module, and install the module.
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
Releases · tiann/KernelSU

A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.

github.com

go to this release link.

download the AnyKernel3-android13-5.15.78_2022-05.zip this one. and use TWRP to flash it.
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Tims Fong:
请教：刷谷歌官方的GSI：gsi_gms_arm64-exp-UPB2.230407.014.A1-10066424-22683335 ，也会出现开机红色警告，为什么？

Ask: Google official GSI: gsi_gms_arm64-exp-UPB2.230407.014.A1-10066424-22683335, there will be a red warning when booting, why?
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
我也不知道，你动boot分区了吗？这个boot开其他系统可以吗？

I don't know. Do you edit the boot partition？This boot partition can boot other GSI rom？
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Tims Fong:
这个文件boot_permissive，只要是A13 phh GSI，都可以起到permissive的作用,且不会出现开机红色警告。对于Nippon GSI和谷歌A14 GSI，没有刷这个文件，也会出现开机红色警告，我想这个与permissive无关。

This file boot_permissive, as long as it is A13 phh GSI, can play the role of permissive, and there will be no red warning when booting. For Nippon GSI and Google A14 GSI, if this file is not flashed, there will be a red warning when booting up. I think this has nothing to do with permissive.
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
好的，我没有用过nippon gsi以及谷歌a14 gsi，如果有条件的话我会去玩玩a14

Ok, I haven't used nippon gsi and Google a14 gsi, I would play a14 if I could
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] william tao:
How did you get the kernel version lower than 5.10, please let me know, thank you, sir.

你的内核版本低于5.10是怎么刷进去的，请教一下，谢谢大佬。

Mod. edit: post translated. alecxs
[ZTE Nubia Z17  ROMs, Kernels, Recoveries, & Other ] Dispossible:
Kernelsu development group provides some kernels based on GKI2.0. Now the new mobile phone may support GKI2.0 such as 8gen1. If it supports GKI2.0, it means that you can choose the right GKI kernel version and flash the GKI kernel. So kernelsu development group released some GKI kernels. For the z17, GKI is not supported, so this post provides a kernel with kernelsu for Z17.

kernelsu开发组提供的内核是基于GKI2.0的内核，现在的新手机比如8gen1以后一般支持GKI2.0，如果支持GKI2.0这意味着你在看清自己内核版本之后，可以随便刷GKI内核，因此kernelsu开发组会发布一些GKI内核。对于z17而言，并不支持GKI，所以本篇帖子提供了专属于z17的内核。
[OnePlus 10R / Ace] yashaswee.exe:
Few things to keep in mind before starting the process:

If you are on ColorOS12 make sure you are flashing OxygenOS12 and NOT OxygenOS 13; similarly if you are ColorOS13 you will have to use OxygenOS13 zip.

You must ALWAYS use OxygenOS newer than the ColorOS you have currently installed.

[English] Written Instructions

:

(

Note this is for 10pro, steps are the same but DON'T use any firmwares mentioned there)

How to Install Indian ROM on Chinese OnePlus 10 Pro

In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.

www.droidwin.com

[Chinese] Written Instructions:

关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安

Video Tutorial:

Downloads Links:

80W_C.15_OOS_Android13

150W_C.15_OOS_Android13

You can also follow the same instructions if you wish to convert to ColorOS. Just make sure you use ColorOS zip in that case.

Download link for ColorOS:

150W_ColorOS_C.17_Android13
[OnePlus 10R / Ace] 6cdh:
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.

Note:

Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.

Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.

Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.

Read it all before you touch your phone and PC!

Steps:

Prepare Fastboot Enhance (windows only), an OxygenOS rom.

Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.

Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.

Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.

Run fastboot flashing unlock to unlock partitions for flashing.

Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.

Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-cow partitions, but I didn't find these partitions. That's fine.

If everything success, you can reboot your phone and enjoy!

Troubleshooting:

Myphone is not recognized by PC.

That's because your Windows PC needs OnePlus driver, try step 3.

If you completed step 3, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.

My phone is hardbricked.

Don't worry.

Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.

One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.

Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
[OnePlus 10R / Ace] yashaswee.exe:
I

In the Step #7, it should be *-cow partitions, No?
[OnePlus 10R / Ace] 6cdh:
Ah, yes, it's a typo. edited.
[OnePlus 10R / Ace] sSjBlueVN197:
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.View attachment 5876919
[OnePlus 10R / Ace] yashaswee.exe:
Better use OxygenOS13 C.18

https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
[OnePlus 10R / Ace] sSjBlueVN197:
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot..... :(
[OnePlus 10R / Ace] yashaswee.exe:
Yes it's for 150W. What you said shouldn't happen! It has worked for others.

Are you able to boot into fastboot?

(Try all key combinations)
[OnePlus 10R / Ace] sSjBlueVN197:
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly