Develop Bugs

N975F Early Access Combination (Factory) and Retail Firmware Link

- The one labeled Factory is the Combination file; the other one is consumer/retail firmware
- As with other current devices, I'm assuming that "Odin 3.13 3b patched" will be needed in order to flash the stock firmware, and that the Combination file will fail to flash, until a method is found
- Once the device is released, retail firmware will be available via SamFirm and other sources, so I'm really only providing this now as early access, for anyone that wants to dig in and play around and see what they can find, etc
- I compress extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=297936

There's a working firmware released already.
Thanks for the Combination ROM.
Cheers.

JazonX said:
There's a working firmware released already.
Thanks for the Combination ROM.
Cheers.
Click to expand...
Click to collapse
did you flash combination?

iBowToAndroid said:
- The one labeled Factory is the Combination file; the other one is consumer/retail firmware
- As with other current devices, I'm assuming that "Odin 3.13 3b patched" will be needed in order to flash the stock firmware, and that the Combination file will fail to flash, until a method is found
- Once the device is released, retail firmware will be available via SamFirm and other sources, so I'm really only providing this now as early access, for anyone that wants to dig in and play around and see what they can find, etc
- I compress extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=297936
Click to expand...
Click to collapse
Thanks my dear, I am not sure if this will fix my problem, but I feel it will, I lost the EFS file by mistake and lost the IMEI.
Best Regards

tarik2 said:
Thanks my dear, I am not sure if this will fix my problem, but I feel it will, I lost the EFS file by mistake and lost the IMEI.
Best Regards
Click to expand...
Click to collapse
Hello There
Did it fix your issue?

Tarar said:
Hello There
Did it fix your issue?
Click to expand...
Click to collapse
Hi,
No, I tried a lot to install it but since Samsung S10 and above Samsung made a special security things to stop us installing the Combination ROM, I used all available methods like TWRP but the ROM never boot, but you can see my fix here: https://forum.xda-developers.com/ga...nt/fixed-repair-imei-fix-deleted-efs-t4011433

Tarar said:
Hello There
Did it fix your issue?
Click to expand...
Click to collapse
I am still trying, please check https://forum.xda-developers.com/galaxy-note-10+/help/n975f-restarting-flashing-combination-t4063557

I've figured out how to do it.
Not free though

can someone find Combination (Factory) for N9750 with U2 N9750ZSU2CTD1 or N9750ZSU2BTC1 firmwares.
I got FRP lock after instalation last firmware with root. Cant enter in recovery, load only in download mode

Question [Question] Who has rooted TMOBILE 9Pro Stock ROM

I understand I can convert to EU.... However, I don't wish to do that. I just want to root my stock TMOBILE ROM.
My sim is unlocked and I have the unlock.bin from OnePlus for my phone. For anyone who has rooted TMOBILE stock ROM, which boot.img did you patch? I've read that AA boot image can work, but no firsthand accounts confirming this.
Ideally, I'd like to use my own boot.img but I can't find a tutorial or guide anywhere advising how to obtain my boot.img without root.
Thanks!

use AA boot img, but recommend unlocking Bootloader and backing up your tmo modem a/b imgs

How to guide
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com

Use partitions backup (app) to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..

galaxyuser88 said:
Use partition magic to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
Click to expand...
Click to collapse
What is partition magic? An app? Software?

Pain-N-Panic said:
What is partition magic? An app? Software?
Click to expand...
Click to collapse
Sorry meant to say partitions backup. Which is an app.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com

Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out

Pain-N-Panic said:
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Click to expand...
Click to collapse
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..

galaxyuser88 said:
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
Click to expand...
Click to collapse
Yep, confirmed, 9pro and my computer can talk. The whole MSM thing is what is worrying me. In the MSM tool, it says it is the TMO -EU MSM. So, once it does it's thing and flashes it all, it should wipe the phone, it would be on the EU rom?
From there, I would need to follow the steps, unlock BL, flash modems, and then download oxygen updater to be able to locally download updates and install?

{SOLVED} Downgrading to a previous Android version

Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?

{Temp_User} said:
Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?
Click to expand...
Click to collapse
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp

JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Hi, thank you for the reply.
Sorry for the late reply. I will try this today

JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?

{Temp_User} said:
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?
Click to expand...
Click to collapse
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware

I have with me the latest (previous) android 10 . I have extracted correctly ( used 7-zip zstd ) the lz4 files and flashed the vendor, system and kernel in that order.
upon reboot, I can not get past the splash screen. However i do see that an error appears on top left of my screen as CHECK FAIL binary 7(BOOT). The words are not clear though.
What did i do wrong?

JuanTamqd21 said:
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware
Click to expand...
Click to collapse
please provide an in-depth process?

Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORS​You cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)​Boot into system normally.(make sure the OEM unlock is greyed out.​Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )​Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.​Pay attention to what exactly you are wiping.​With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.​Flash/Install the image files in your recovery. Be patient.​
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.​Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)​​You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
​​

{Temp_User} said:
Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORS​You cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)​Boot into system normally.(make sure the OEM unlock is greyed out.​Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )​Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.​Pay attention to what exactly you are wiping.​With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.​Flash/Install the image files in your recovery. Be patient.​
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.​Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)​​You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
​​
Click to expand...
Click to collapse
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:

Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).

vmirrimv said:
Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).
Click to expand...
Click to collapse
So long as we both happy and got what we wanted. I finally have a working android 10 on my device(coming from a11)

vmirrimv said:
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:
Click to expand...
Click to collapse
You are correct. I gave up on changing the binaries after seeing it was impossible.

Camera should still work on custom android 10 one ui roms and GSI. I think I tested them before.

How To Guide LE2127 OnePlus 9 Pro Custom ROM (T-Mobile)

I am seeing a lot of folks who are still (year later) unable to enjoy custom ROM with T-Mobile devices, so I wanted to quickly post this easy method for enjoying your device with FULL DATA. If you are using a T-Mobile branded OnePlus 9 Pro and have accepted all normal OTA updates as of 9/8/22, you should be on C.19 firmware.
Assuming you have already unlocked your bootloader, you can safely upgrade to EU C.62 firmware found at:
OP9PRO_Android12_C62_EU_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
I completed this process while already on Nameless but it should work for others too. No more dodgy modules, hacked MSMDownloadTools or sorta working phones. Note, firmware and local updates are NOT the same. You are not cross-flashing to an entirely new software but ONLY required firmware modules for latest custom ROMs. Hope this helps!
P.S. if you receive any error while sideloading your new firmware, DO NOT unplug or reboot your phone. Repeat the process until it's completed successfully.

So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??

nextbigleap said:
So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??
Click to expand...
Click to collapse
That's exactly what I am saying, fastboot flash the firmware only and say goodbye to data issues.

My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?

MudaTrucka said:
My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?
Click to expand...
Click to collapse
No user data removed.

Appreciate this post. Do you plan on keeping this updated as EU gets updates?

SaintZ93 said:
Appreciate this post. Do you plan on keeping this updated as EU gets updates?
Click to expand...
Click to collapse
I will do my best!

Why does this work where the eu msm converter has problems with the modem? After you flash this firmware can you take future ota updates without modem issues as well?

The latest firmware from non-branded OnePlus 9 Pro is now available!
OP9PRO_Android12_C63_NA_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
This finally brings those of us on T-Mobile, especially closer to the bleeding edge.

Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.

rageoner said:
Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.
Click to expand...
Click to collapse
Of course, it's modified because OnePlus doesn't create firmware packages for our community. However, the files within the package are original dumps.
You can easily sideload this fix through your custom recovery using adb sideload OP9PRO_Android12_C63_NA_Firmware.zip for example.

Ok, one last question, are we able to take ota updates after doing the sideload? I know this is the latest firmware so there won't be any but in the future are we able to take ota?

Question:
1-what room is best for my LE2127 for daily use
2-Hasselblad camera exist a app
3-what TWRP are we using now
thanks in advance

Could someone please post steps to sideload Le2127 to EU / Global C.62EU / C.63NA No data loss ?

can I sideload this from t-mobile c.17? Also what recovery can I use? TWRP is for android 11

I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com

luckylui said:
I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
Click to expand...
Click to collapse
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.

MudaTrucka said:
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.
Click to expand...
Click to collapse
Do the other option and go from there.

The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !

Bulauski2005 said:
The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !
Click to expand...
Click to collapse
You can't help folks that don't want to help themselves.

Question Is any way to root devices without BL unlocked?

I have an interesting idea, but I don't have enough technical skills to implement it.
I noticed that edload mode can brush all partitions without BL unlocked. So i`m think, if i can modify init_boot.img and package it into the flashing package, can I bypass the BL lock and forcibly flash root into the device?
If that available, I can own rooted devices without data loss, fingerprint also does not appear abnormal.

No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.

CrazyMoney said:
modify init_boot.img and package it into the flashing package
Click to expand...
Click to collapse
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.

zSyntex said:
No. Root require a patched boot.img, so you have to get access to other partition.
To do this the unlocked bootloader is needed.
Click to expand...
Click to collapse
I remember Andriod 13 need patch init_boot.img instead of boot.img. And edload mode doesen`t need anything because that used a underlying layer.

aaa.bbb111222 said:
AFAIK this won't work because this image needs to be signed. If we can patch init_boot.img, sign it, flash it and also flash signature of this file, we might be able to relock bootloader. Try with caution: unless there's good instruction for EDL unbricking, you might end up with a bricked device without any free way to fix it.
Click to expand...
Click to collapse
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.

CrazyMoney said:
I think you are right. But in the past, I can make fake signature in the past, just don`t know how to deal now.
Click to expand...
Click to collapse
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.

zSyntex said:
From the past a lot of things had changed.
Now you need to unlock the BL to get root in the correct and safe way.
Click to expand...
Click to collapse
Maybe, but everything only by trying can step foreward. Isn`t it?
I'm just sharing my ideas, not necessarily implementing them, just discussing a possibility.