yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S23 Ultra] lampon:
Sorry for responding to this months-old thread. Just came across this. I switched CSC to GCF (U firmware) but don't see any additional toggles. Anybody know how to make that work?

FWIW, SamFw had GCF in its list for my phone, I didn't write it in manually or anything. Also ran Info after switching and rebooting and CSC does indeed come up GCF.

Edit: I'm an idiot. In case anyone else has the same issue - I was looking for additional settings to pop up in SIM Manager to set primary for data and calls/text. That's not how it works - the toggles pop up underneath quick tiles as shown in the screenshot earlier in the thread. Trick is to set the default SIM to the one for calls/texts in SIM Mgr and then SINGLE press on the "Mobile data" toggle to set the appropriate SIM for data. Oddly this seems to switch the default SIM in SIM Manager to the one for data but I believe it still defaults to the correct one for calls/texts, I.e. Samsung dialer shows SIM 1 for outbound calls and Google Messages used the correct SIM for an outbound SMS. Additionally, RCS didn't get disabled on SIM 1 as was happening when I actually set my data SIM as primary (even though it currently shows as primary). For the love of god I hope this sticks.

Thank you @peacey8 & @waqqas.khokhar!!!
[Samsung Galaxy S23 Ultra] JeffATL:
Where are you looking for the toggles? They are in the notification menu when you pull it down. Not in settings. I have some issues with GCF. My visual voicemail that I have with XAA gets disabled/hidden and I can't receive MMS on Verizon based carriers
[Samsung Galaxy S23 Ultra] lampon:
Yes thank you. I did see the toggles in notifications but kept trying to long press them instead of single click, and then I kept going to SIM Manager and not seeing any new settings (facepalm). Edited my reply to reflect that.

As for the issues you're having, I haven't received any VMs yet (and tend to use GV anyhow) but I was just able to send a test MMS from GV to myself (Mint) so perhaps it's Verizon specific?
[Android Head-Units] jdw22:
Hey Guys,

so i got a PX5 with Android 9 (before it was 8) and everything works fine expect Bluetooth. When i start the Bluetooth App i wont find any devices and i can fill in a name and password, but i wont display on the screen. So name and password is always blank.

i tried:

-delete the cache of the app

-reset the bluetooth settings

The other problem i got is that i cant open factory settings but thats since i got the radio. I got the correct password and than its just a black screen.

Thanks for any advice :)
[Android Head-Units] jdw22:
Also i cant go back to Android 8, if i try to update it says.

Update cant be completed cause i got K3368 and not a PX5
[Nothing Phone 2] mattyb132:
Is it at all possible to enable any other cell bands on the Nothing Phone 2? There's a method for doing so on Qualcomm based Samsung phones and I wanted to know if it's similar with this phone.
[Nothing Phone 2] morphius88:
You can't enable bands that that the phone doesn't have capability for. While some Samsung phones might have had some disabled/blocked bands from the factory for whatever reason, it is unlikely that the Nothing Phone has anything like that going on.
[Huawei P20 Questions & Answers] richyg81:
So I ran through a list of debloating packages and all is good apart from one issue, as the title states, the app overview (square icon) is no longer functioning, as is swiping across the fingerprint button, which should perform the same action.

On digging further in settings, if I go to System > System Navigation, select Off screen key navigation and tap settings, I get a black screen. So whatever package I've removed clearly has had some impact on this function.

I tried to keep an accurate list of packages remove below. I would be so grateful if someone could suggest a way forward so I can have this basic function returned on my phone.

Here is the list:

com.huawei.health

com.huawei.mycenter

com.huawei.tips

com.huawei.appmarket

com.huawei.browser

com.huawei.browserhomepage

com.huawei.gamebox

com.huawei.game.kitserver

com.google.android.music

com.huawei.hwdetectrepair

com.huawei.phoneservice

com.huawei.android.FloatTasks

com.huawei.hwpanpayservice

com.huawei.wallet.sdk.walletsdk

com.huawei.hwread.dz

com.huawei.contactscamcard

com.huawei.search

com.huawei.searchservice

com.huawei.hifolder

com.huawei.himovie.overseas

com.huawei.multimedia.hivideoplayengine

com.huawei.parentcontrol X

com.huawei.pcassistant

com.huawei.vassistant

com.huawei.hisuite

com.android.providers.partnerbookmarks

com.huawei.synergy

com.huawei.android.launcher

com.huawei.hicard

com.huawei.android.totemweather

com.touchtype.swiftkey

com.huawei.intelligent

com.huawei.hitouch

com.android.mediacenter

com.huawei.hilink.framework

com.huawei.android.hsf

com.huawei.android.chr

com.huawei.iaware

com.google.android.apps.tachyon

com.google.android.feedback

com.google.ar.core

com.facebook.services

com.android.dreams.basic

Thanks in advance
[Huawei P20 Questions & Answers] RealDexxo:
Maybe com.huawei.phoneservice, but I suggest you to format your phone and don't do that again...
[Huawei P20 Questions & Answers] richyg81:
nevermind, I restored com.huawei.android.launcher using ADB AppControl which has fixed the problem

thanks for replying anyway
[Red Magic 8 pro] jacobw1ooo:
First of all, if this is not the correct forum, I apologize.

I have loaded my phone into fastboot mode (adb reboot bootloader)

These commands work

fastboot devices

fastboot oem device-info

fastboot reboot

fastboot getvar unlocked (returns locked)

Then attempted to unlock the bootloader, these commands return (FAILED (remote: 'unknown command')):

fastboot flashing get_unlock_ability

fastboot flashing unlock

fastboot oem unlock

fastboot oem nubia_unlock NUBIA_NX729S

Does anyone know what other command might work?

PS: i cant access the boot command block (do not being root) and find out what the OEM command might be.
[Red Magic 8 pro] aaa.bbb111222:
Assuming you did 'OEM Unlocking' in development settings, have you tried fastbootd mode (from bootloader it's 'fastboot reboot fastboot')?
[Red Magic 8 pro] jacobw1ooo:
fastbootd mode update (08/08/2023)

fastboot oem unlock

FAILED (remote: 'Command not supported in default implementation')

fastboot flashing get_unlock_ability

FAILED (remote: 'Unrecognized command flashing get_unlock_ability')

fastboot flashing unlock

FAILED (remote: 'Unrecognized command flashing unlock')

fastboot oem nubia_unlock NUBIA_NX729S

FAILED (remote: 'Command not supported in default implementation')

fastboot oem nubia_unlock

FAILED (remote: 'Command not supported in default implementation')

fastboot oem device-info

FAILED (remote: 'Command not supported in default implementation')

fastboot getvar unlocked

works returns: unlocked: no
[Red Magic 8 pro] aaa.bbb111222:
It seems that these commands were removed.

Could you please contact Nubia support and ask about the ability to unlock the bootloader? When OEMs remove these commands they usually add some custom method of unlocking.
[Red Magic 8 pro] jacobw1ooo:
i agree, i have already emailed them, waiting on a reply back. will post the fix once i have it.
[Red Magic 8 pro] jacobw1ooo:
After talking to and emailing they have refused to provide any assistance in unlocking the boot loader, i guess i will have to return it.
[Red Magic 8 pro] Admiral_Face:
Same problem here, guess I'll have to find a RedMagic 8 pro non-S instead, with an older firmware, root it, modify the kernel to support the higher clock speeds, and release it here. Wish I had read this before wasting my time and $800.
[Red Magic 8 pro] aaa.bbb111222:
Do you think it's up to kernel to support these higher clocks?

They say "we don't recommend", which is understandable. If I were you, I'd try to put some pressure on them to provide some unlocking method regardless of their recommendations. It's just ridiculous all these companies are still doing that 🍎-style of bs.
[Red Magic 8 pro] Admiral_Face:
Oh for sure, that was probably the only upgrade from the regular 8 pro. Maybe they used some binning and testing to ensure "maximum system stability" at those speeds but the kernel's cpufrequtils and gpufrequtils "MAX" variable is behind the increased clock speeds. There's no difference otherwise, any Snapdragon Gen 2 should be able to hit this kind of minor overclock without much issue, especially with the beefy cooling systems these things have.

I sent in a reply email:

The problem is there's no guarantee whatever I get off eBay for the 8 pro (at some abominable scalper prices) is going to be running the older firmware needed to properly unlock the bootloader. What I just don't understand is why just now? No previous version of MagicOS has had the fastboot commands locked down like this. It's just terrible, why limit your customer base like this, I just can't understand. Maybe it's to keep up with the illusion that this version is somehow magically faster because they changed 2 variables in the kernel. ZTE still hasn't even released Kernel sources for this thing either (in violation of US law on Copyrights) so I'm also reporting them to the free software foundation, whose lawyers will handle at least that mess.
[Red Magic 8 pro] aaa.bbb111222:
They will not. Qualcomm violates GPL for many years already (the distribute modified gnu binutils without source code) and it's been almost a year since I've last heard from them.

What's the version? They might be using the same one as for non-S. I starting to have strong suspicion that these are really the same device, so they are fully firmware compatible. Given that we have EDL package for non-S, you might try flashing older version via EDL (which should be unlockable). It's really dangerous, so don't try it unless you know what are you doing. And backup stock image beforehand.
[Red Magic 8 pro] Admiral_Face:
That's very unfortunate, seems like a legal nightmare to begin with.

You're right that it may be an identical kernel, minus a few modifications to the cpufrequtils and gpufrequtils, the NX729 does have sources on github. However, without an unlocked bootloader, or a payload.bin, there's no way I could even make a system image backup of this thing, let alone flash anything. That does give me an idea, maybe the payload.bin from the normal 8 pro could be used, if extracted from the latest firmware. I might be able to at least make a backup that way, maybe poke around the abl to see if I can detect what's wrong with fastboot, or what the manufacturer's tools are doing.
[Red Magic 8 pro] zo_parts:
Not solution
[Red Magic 8 pro] zo_parts:
So difficult unlocking boooader RedMagic 8S Pro
[Red Magic 8 pro] Admiral_Face:
I have discovered a number of new things. Firstly, this device really is just a NX729-J, it's running the same Firmware as the Original 8 Pro, with a slightly altered Kernel (as expected). I have been trying my best to mess around with the boot.img and init_boot.img dumped using the payload dumping section of fastboot enhance with the OTA image of the latest update to the normal 8 pro, but I can't seem to figure out any way to work with them, unpackbootimg leaves me with empty boot.img-base, boot.img-cmdline, voot.img-pagesize, and boot.img-zImage. abootimg just spits "no Android Magic Value" or "boot.img: ramdisk size is null."

Is there anyone here with more experience extracting the contents of boot images? I want to see what strings fastboot does have, and if it doesn't have anything useful, if there's some kind of system in place to unlock bootloader functions outside of fastboot. I still have yet to receive another reply from support. If there's anything that I find, it would only serve to benefit both 8S and 8 pro users both, as we might be able to find a means to unlock the bootloader on most recently updated devices.
[Red Magic 8 pro] JWnSC:
Do you have a link to the payload.bin for redmagic 8s pro?

Some Fastboot commands were removed from 8.0 firmware(see pic, from twrp dev).. would have to change abl.img I think.. Kinda risky
[Red Magic 8 pro] Admiral_Face:
No, as no OTA updates have been made available for the device, there's no possibility of getting a payload.bin for the 8S pro, however, as the firmware is identical in every way minus a total of three line changes in the kernel, the payload.bin from the original 8 pro's latest firmware image should be enough.

I don't think it's even possible to flash an abl.img, without having an unlockable bootloader. I can't even see what fastboot commands are available. Some of the ones in your picture don't work either, fastboot oem device-info is missing, and I don't even want to try the others. But if I had a list of the available commands for the 8 pro's latest abl, or had the ability to look at the binary at all, I think there's at least some clue I could gain.
[Red Magic 8 pro] Admiral_Face:
New response from staff, laughably unhelpful.
[Red Magic 8 pro] aaa.bbb111222:
Does it run the same 5.15.41 version or it's a bit newer? If it's really just the same device, it might be safe to just flash full OTA (3.40 will probably

I think this is because of GKI. Try unpacking other images (i.e. vendor_boot)

You'll need to run "binwalk -e" on abl.img

It will produce file named 1078 (at least it did this for me, your mileage may vary), you can run "strings" on it.
[Red Magic 8 pro] aaa.bbb111222:
Here's the kernel (unpacked for convenience). Which lines should be changed to unlock the "full 8g2 potential"?

Don't give up, they published the kernel source only after many people bombarded their support with that requests.

That's not entirely true, there is EDL package available for our device (firehouse/sahara), it can flash device (and read firmware) without unlocked bootloader.

Abl is actually open source, seems that zte removed some defines to disable unlocking.

BTW, have you tried local upgrade with full v3.28/4.28 OTA zip package?
[Red Magic 8 pro] Admiral_Face:
Thank you so much, this helps so much. What would you recommend for vendor_boot?

Linux localhost 5.15.41-android13-8-00024-g3605981d8a31-ab9291366 #1 SMP PREEMPT Mon Nov 14 20:51:00 UTC 2022 aarch64 Toybox

Build Number: REDMAGICOS8.0.8_NX729J_GB

HW Version: NX729J_V1AMB

fastboot oem device-info doesn't work.
[Red Magic 8 pro] Admiral_Face:
It would be the MAX_FREQ variables in kernel/drivers/devfreq/governor_performance.ko

If you could find one for kalama, it would be appreciated, I would love to have any means to backup the system images of this device, for study, if anything.

I'm too scared to try especially without an OTA package for my current hardware, are downgrades even possible without an unlocked bootloader? I do seem to have the fastboot flash command.
[Red Magic 8 pro] aaa.bbb111222:
It should contain devicetree, so you can use android image kitchen to extract it. It's the same android bootimg file.

You kernel is newer than mine (5.15.41-android13-8-00005-g779f29f1a22b-ab9196663 #1 SMP PREEMPT Wed Oct 19 23:38:42 UTC 2022 aarch64)

It was posted before, also V3.19 here
[Red Magic 8 pro] aaa.bbb111222:
I think it should be safe, if anything, OTA will simply not install. You can also record logcat to find where it fails
[Red Magic 8 pro] kh.v:
unfortunately, the answer is NO,

at the moment, the 8s pro (NX729s) come with os 8, and the OS itself DO NOT allow to flash anything in, therefore, you CAN NOT unlock the bootloader.

There is a way that we can get arround with this, by using the 9008 with firehose, however, the firehose for nx729s does NOT RELEASE YET !!!

THEN the answer is NO !
[Red Magic 8 pro] Timmy Turner10:
Unlocking the bootloader only depends on if you have OEM Unlocking in developer options and if you know what command to unlock it with. Flashing vs unlocking bootloader are two different things. Unlocked bootloader means you can flash. Android doesn't come with flashing by default, sure, but as said, you can unlock bootloader with the right command.

The redmagic 7 pro came with Android 12 and it can be rooted and therefore bootloader unlocked. This would be no different.

I've tried

fastboot flashing unlock

fastboot oem unlock NX729J

and a bunch of others, looking through older redmagic model guides might help come across something that works. I'll keep looking.
[Red Magic 8 pro] moric5:
So 8s is locked phone for ZTE politically. I don't buy it
[Red Magic 8 pro] Anegorami:
Guess I'll throw my two cents two. Found the following link while lurking across chinese forums for clues and insights:

http://romdownload.nubia.com/红魔8SPro/12MR/GEN_CN_NX729SV1.0.0B12MR_SD_WO_ERA.zip

My 8S is still several weeks away so I can't help much. Hope you find this useful.

Good luck. For we are many.
[Red Magic 8 pro] Timmy Turner10:
Well support was useless.

Me:

Hello Redmagic team. How do you unlock the bootloader on the Redmagic 8S Pro? There is OEM Unlocking and it's turned on in developer options in the Settings. In fastboot, no unlock commands work. Can I get some help? The option is there, I feel it's good to know how to do it, what commands to use. In fastboot, I've tried fastboot flashing unlock and fastboot oem unlock. I understand the warranty stuff, and unlocking it should be at the customer's risk, but I feel like we customers should be given instructions how to do it.

Red Magic:

We do not recommend you to perform related operations (unlocking the bootloader), which will affect the integrity of the mobile phone system, may cause unknown failures of the mobile phone and make your mobile phone out of warranty.

Me:

Yes, I understand that. But for those, like myself, who want to know, how can we find out how anyways? I see your point as valid, but we are responsible for damages we make to our devices.

Red Magic:

We do not have information to provide the steps to unlock the bootloader.

Me:

Anyone that does perhaps? Like tech department or anything?

Red Magic:

We don't have information about the steps to unlock the bootloader

Also tried a huawei bruteforce tool on github, after running for a few minutes I got nothing still. Tried changing the date to a month so it's above the usual 7 day mark for other oem's bootloader unlock, and of course, still nothing.

Something I also do not know, is if you can flash anything at all, including recovery image, with a locked bootloader?

Running out of ideas myself here. Where can I find the chinese forum or a US/Canada rom from that rom site? Tried different changes to that URL in hopes it'd go to a hierarchy of devices/roms, instead of just a single rom link.
[Red Magic 8 pro] kh.v:
I know your pain , however i do what i could so far to get the firehose for the 8s pro series. I cannot make any promise at the moment that when i can get it, i will share asap.

But for now, NO UNLOCK BL and DO NOT try to LOCK the BL if you update your phone (nx729j as the rm8p series to the os8) . You will be no longer can unlock it bl again (at least at this moment)
[Red Magic 8 pro] aaa.bbb111222:
Is it really different from non-S one?
[Red Magic 8 pro] kh.v:
8 pro series (nx729j)

8s pro series (nx729s)

Different firehose
[Red Magic 8 pro] aaa.bbb111222:
That's the question, how do you know this?
[Red Magic 8 pro] Timmy Turner10:
The 8S pro is already on OS 8 if you mean RedmagicOS8.0.9_NX729J_GB. That's the current software version. I believe out of the box it was a bit lower but still OS8.0.

EDIT: With the firehose for 8 Pro, I used QLMFlasher to try dumping the partitions. It said it was UFS storage, not emmc type, and the current rom is on slot b (also fastboot says this too), with no way to change that.

Below is the dumped boot and abl partitions. Can we search the abl for fastboot commands or something secret? Then patch the boot image with magisk and flash it after bootloader unlock is achieved?
[Red Magic 8 pro] Anegorami:
Stupid question: if firehose taken from 8 Pro seems to work and produce desired output, is it possible to use some tool (Qualcomm Flash Image Loader comes to mind) to backup, patch (Magisk) and flash init_boot partition back to gain root access without even touching the bootloader (and thus keeping the warranty)?

Spoiler content hidden.
[Red Magic 8 pro] aaa.bbb111222:
First one is mine (unlockable), second one is yours. View attachment 5978163
[Red Magic 8 pro] aaa.bbb111222:
You can, but it will brick the device because of AVB. One might try flashing older abl.img (i.e. the attached one) and unlock "the normal way". Something like this might work, but it's very risky. I wouldn't recommend anyone trying this, but even if one were to try, backup at least your persist.img first! Backing up other partitions wouldn't be redundant as well.

They can't take away the warranty for unlocked bootloader (until they prove that your actions caused the phone to malfunction).

The problem is that commands were removed. That's it. See abl source code here. Apparently, ZTE removed ENABLE_UPDATE_PARTITIONS_CMDS and ENABLE_DEVICE_CRITICAL_LOCK_UNLOCK_CMDS defines
[Red Magic 8 pro] Timmy Turner10:
So with this abl, you think it can be flashed via edl mode? I was thinking about waiting for Redmagic to put the update firmware on their website, so we can dump that in case it bricks, by flashing it by edl too.

EDIT: Nvm this post was useless lol. Guess I'll wait a bit for updates or what anyone finds next.
[Red Magic 8 pro] aaa.bbb111222:
There's no need for that. It should be possible to dump everything with edl.

It might be. At least given that NX729J firehose worked on NX729S, this abl might be compatible as well. But if not, one will have to restore it via edl.

BTW, can you check if your phone has secure boot enabled? This thread has more info about it.
[Red Magic 8 pro] Timmy Turner10:
Yep, it does. Fastboot getvar all gave everything as expected. This also showed it was in slot b for the OS. I will look into making sure my abl is backed up first, erm, everything, then patch it and test. Don't want this phone to go to waste too so have to take extra precautions. If it works well, then boom. Should have root :)
[Red Magic 8 pro] aaa.bbb111222:
Wait, you shouldn't be patching abl. You only need to flash one from abl_340.zip

Not yet. After abl was flashed and assuming all goes well, you should be able to unlock the bootloader with standard fastboot commands and flash patched init_boot.img (which you can get via edl as well).
[Red Magic 8 pro] Timmy Turner10:
I will flash abl then, test, give results. In case of brick, you mentioned the persist image. I have it backed up along with a lot of others (some were empty, 0kb as qlmflasherpro failed after dumping a few). Qlmflasher was all I could get to work, qfil wouldn't work.

Empty ones:

metadata, rawdump, userdata, vbmeta_system_a, vbmeta_system_b)

Will I need these you think in case it goes wrong? I won't do it yet if I do need them.

Oh, maybe qfil can't use the 8 pro firehose. Maybe we need to get ahold of the official one for 8s. I mean, qlmflasherpro worked decently for dumping but fails, and it's a paid tool. Any ideas on how to obtain the firehose? Redmagic support as we all know will not help. It's insane we have to do all this just to make our devices actually ours.
[Red Magic 8 pro] aaa.bbb111222:
I don't think you need these, especially userdata.

I'm not really familiar with this tool, but if it uses EDL, it must have some sort of firehose loader somewhere, so you can try extracting it. But it most likely uses the same 8 non-S pro firehose loader.

There also were few different ones posted on this forum, you can try searching for them.

Have you actually tried this tool?
[Red Magic 8 pro] Timmy Turner10:
Yes, when I open terminal in the repo folder and type the edl commands for dumping or loading firehose files, it prompted to choose which app to open 'edl' and python was not on the list, although it's installed.
[Red Magic 8 pro] aaa.bbb111222:
There are installation instructions for all major OS families.

And it's CLI tool, so you'll need to run it in cmd.exe