Related
Hi, good afternoon, I'm having a problem with an icon pack, always return to the default after exiting the settings, as well as the source applied by MiCustomFont.
I tried to replace the native source folder with the same rooted device I did in previous versions of MiUi and did not succeed.
The only source I could change was NotoColorEmoji.
Right now I'm downloading the system to flash MiFlash, but before I change the source folder with the source I want along with emojis, (because I had a problem after root not recognizing the sim card and I needed it reinstall by TWRPto global rom)
A third problem is a problem that even seen here in the forum could not find a concrete answer, I need to fix the TWRPin my cell phone, because the procedures taught are difficult and depend on the luck of the person to start TWRP.
Please,
Thanks!
Breno Leoni
I found a different solution for installing fonts, different from when I just copied the folder with the fonts I wanted all renamed by a default to the system / fonts folder, it used to be okay, today in MiUi 10 not.
I got an installation of Emoji Unicode via TWRP, I changed NotoColorEmoji to one of my liking and I added my standardized source pack properly renamed with the name of the fonts that MiUi uses and it worked, I'm satisfied, this way is the most efficient to change cell phone fonts..
Now I just need to think about a solution to the problem. Icons do not return to the default and can fix the TWRP in the memory of Redmi 6
Galaxy S7/S7 edge is probably the latest Snapdragon "S" phone for international market in terms of radio capabilities. I would say it is even more functional than exynos S7.
Next Snapdaragon S8/S9 was built for US carriers and LTE bands.
Here is what was discovered:
Of course it supports all Europe LTE bands (1/3/7/8/20/38)
Moreover it supports a lot of CA combinations that is not enabled in EFS
As I understand phone scheme It supports noncontinuous 3xCA only if third carrier is "low frequency" like B20 or B8 because this antenna is connected to second transceiver.
Here is the list of combinations tested and fully working in Russia (from CA_tested.cmd)
Code:
3A2A-7A2-20A2 6
3A2-7A2A-20A2 6
3A2-7A2-20A2A 6
3A2A-7C2 6
3A2-7C2A 6
3A2A-7A2-7A2 6
3A2-7A2A-7A2 6
7C2A-20A2 6
7C2-20A2A 6
1A2A-7C2 6
1A2-7C2A 6
3A2A-20A2-38A2 6
3A2-20A2A-38A2 6
7A2-20A2A-38A2 6
1A2A-3A2-20A2 6
1A2-3A2A-20A2 6
1A2-3A2-20A2A 6
1A2A-7A2-20A2 6
1A2-7A2A-20A2 6
1A2-7A2-20A2A 6
Number of combos: 20
Max streams per combo: 6
Here is a simple instruction how to enable combinations listed above:
Enable Qualcomm diag port in *#0808# service menu (DM+MODEM+ADB)
Install Samsung drivers and find out the number of diag COM port in Windows Device Manager
Run the script CA_teste.cmd from attachment
Enter the COM port number when asked
The script result must look like this:
Code:
00000000: 4b 0b 24 00 78 02 00 00 0e 00 02 00 ca 70 c7 12 *K.$.x........p..*
00000010: 7e *~ *
If you got another one just reconnect the cable or reboot the phone and rerun the script.
Reboot the phone
Some more combinations a very likely supported, but not tested.
Code:
3A2A-7A2-20A2 6
3A2-7A2A-20A2 6
3A2-7A2-20A2A 6
3A2A-7C2 6
3A2-7C2A 6
3A2A-7A2-7A2 6
3A2-7A2A-7A2 6
7C2A-20A2 6
7C2-20A2A 6
1A2A-7C2 6
1A2-7C2A 6
3A2A-20A2-38A2 6
3A2-20A2A-38A2 6
7A2-20A2A-38A2 6
1A2A-3A2-20A2 6
1A2-3A2A-20A2 6
1A2-3A2-20A2A 6
1A2A-7A2-20A2 6
1A2-7A2A-20A2 6
1A2-7A2-20A2A 6
3C2A-7A2 6
3C2-7A2A 6
3A2A-3A2-7A2 6
3A2-3A2-7A2A 6
Number of combos: 24
Max streams per combo: 6
It would be nice you can test them if your local carriers support such combinations.
Run CA_not_tested.cmd instead of CA_tested.cmd to enable extended list of combinations.
Credits:
vvevvevve from 4pda.ru forum for most research and consultations
qtools developers for the qcommand.exe used in script
It supports 1AA-3A/1A-3AA at least as I thought.
Are the combinations CA_3A-7A and CA_7A-3A enabled in the EFS by default?
bla679832164 said:
Are the combinations CA_3A-7A and CA_7A-3A enabled in the EFS by default?
Click to expand...
Click to collapse
Definitely not
Here is the list of CAs on T version
Code:
Input file size: 300 bytes
Format verson: 0
Number of descriptors: 13
4A4A-12A2 6
4A4-12A2A 6
2A4A-12A2 6
2A4-12A2A 6
2A2A-4A2-12A2 6
2A2-4A2A-12A2 6
2A2-4A2-12A2A 6
12A2A-4A2-4A2 6
12A2-4A2A-4A2 6
Number of combos: 9
Max streams per combo: 6
A,P,U modems have disabled CA
I have nos seen V EFS backup, but pretty sure there is no 3+7 combinations
abyss7 said:
Definitely not
Here is the list of CAs on T version
Code:
Input file size: 300 bytes
Format verson: 0
Number of descriptors: 13
4A4A-12A2 6
4A4-12A2A 6
2A4A-12A2 6
2A4-12A2A 6
2A2A-4A2-12A2 6
2A2-4A2A-12A2 6
2A2-4A2-12A2A 6
12A2A-4A2-4A2 6
12A2-4A2A-4A2 6
Number of combos: 9
Max streams per combo: 6
A,P,U modems have disabled CA
I have nos seen V EFS backup, but pretty sure there is no 3+7 combinations
Click to expand...
Click to collapse
Thank you for the list!:good: I know for a fact that my mobile network provider has implemented CA_3A-7A, so if you find a way to add that combination into your cmd script I could test whether it works or not.
bla678932164 said:
Thank you for the list!:good: I know for a fact that my mobile network provider has implemented CA_3A-7A, so if you find a way to add that combination into your cmd script I could test whether it works or not.
Click to expand...
Click to collapse
It is already there. Check the second line in the list in start message
Will this survive factory reset?
turbozapekanka said:
Will this survive factory reset?
Click to expand...
Click to collapse
Yes, it will
It won't survive only full firmware reflash especially for another carrier.
Should I use CA+1.cmd or CA.cmd for Russia?
Is there a way to save and revert to original settings in case something goes wrong?
Can you please share the link to the original 4pda thread?
turbozapekanka said:
Should I use CA+1.cmd or CA.cmd for Russia?
Is there a way to save and revert to original settings in case something goes wrong?
Can you please share the link to the original 4pda thread?
Click to expand...
Click to collapse
1. It depends on your region and carrier, but nothing bad happened if you set more than used by carrier.
2. Yes, xQCN backup with QPST
3. Start from here http://4pda.ru/forum/index.php?act=findpost&pid=77244363&anchor=Spoil-77244363-5
1. Will this work without root?
2. I have a G930U with modem G930UUESACSI1 and Oreo, will it work on that one?
I have tried doing the steps listed above, but CA is still not working for me...
bla678932164 said:
1. Will this work without root?
2. I have a G930U with modem G930UUESACSI1 and Oreo, will it work on that one?
I have tried doing the steps listed above, but CA is still not working for me...
Click to expand...
Click to collapse
1. Yes, it will in general. You just need to enable diag port.
2. It won't work with U modem, you need V or T modem. I recommend T.
If I'm not mistaken U do not have enabled *#0808# code by default. You have to make it work by temporary flashing engineering kernel and replacing keystrings.dat or use other carrier firmware or any other way.
But it is out of this topic.
Tested and added the new combination 7CA-20A/7C-20AA
Also changed the OP and attachment
Now
CA_tested.cmd is for who wants just get working phone
CA_not_tested.cmd is for who wants to "See how deep the rabbit hole goes" or just help with testing.
Updated the OP with 1A-7C (of course it also supports 1A-7A)
Hi, i made a bit of a mess. I tried the script on a US Unlocked S10+ used in Bulgaria trying to enable CA but now the network broke down. I no longer have any network connectivity. How can i revert it back to stock? And is there a way to make it work on the phone? Thanks
The problem just got more complicated. I tried to reflash my original Firmware with CSC file and start from scratch but it didn't recover the network. Then tried to flash a T-Mobile branded Firmware, it didn't do anything and just reflash back to the original unlocked U1. It seems that the script changed something above the firmware level.
CuBG said:
Hi, i made a bit of a mess. I tried the script on a US Unlocked S10+ used in Bulgaria trying to enable CA but now the network broke down. I no longer have any network connectivity. How can i revert it back to stock? And is there a way to make it work on the phone? Thanks
Click to expand...
Click to collapse
It was not good decision to apply this script to US S10. As said in OP S7 was the last "universal" device.
The right way is restore EFS Backup, but I think you don't have it
- Firstly, you can delete "file" /nv/item_files/rfnv/00028874 in EFS via QPST (EFS Explorer). It make your network just work, but without any carrier aggregation.
- Ask some another owner of such phone give you original 00028874 and write it to your phone.
Unfortunately I have only from US Note 10.
abyss7 said:
It was not good decision to apply this script to US S10. As said in OP S7 was the last "universal" device.
The right way is restore EFS Backup, but I think you don't have it
- Firstly, you can delete "file" /nv/item_files/rfnv/00028874 in EFS via QPST (EFS Explorer). It make your network just work, but without any carrier aggregation.
- Ask some another owner of such phone give you original 00028874 and write it to your phone.
Unfortunately I have only from US Note 10.
Click to expand...
Click to collapse
Hi, thanks for the info. After spending the last couple of days educating myself on the matter i finally know what's going on. Can you give the 00028874 file from the US Note 10? I'd like to test it out since it's from a phone with the same SoC, same modem and from the same region FOR the same region. For now i can't find an original backup of that file from the same phone as mine, so the US Note 10 is the second best option to try Thanks again!
CuBG said:
Hi, thanks for the info. After spending the last couple of days educating myself on the matter i finally know what's going on. Can you give the 00028874 file from the US Note 10? I'd like to test it out since it's from a phone with the same SoC, same modem and from the same region FOR the same region. For now i can't find an original backup of that file from the same phone as mine, so the US Note 10 is the second best option to try Thanks again!
Click to expand...
Click to collapse
For example Hong Kong S10/S10+ are very different from Hong Kong Note 10/10+. The same SoC. The same Region.
You can try it on your own risk. It is in attachment.
abyss7 said:
For example Hong Kong S10/S10+ are very different from Hong Kong Note 10/10+. The same SoC. The same Region.
You can try it on your own risk. It is in attachment.
Click to expand...
Click to collapse
It didn't work I'll leave it at that. The phone is going back to Samsung for the upcoming S20U, so i don't care if the CA works or not when i fly back to the US. Thanks anyway :good:
When i get the S20U thought and bring it back to Bulgaria, then i am gonna do a FEW backups of these files and hope to find a solution on the CA in Europe
Good day everybody,
A few questions about upgrading my pixel 3 from 9 to 10. To preface I have an unlocked bootloader and am rooted on the June 2019 version of android. I would like to update to android 10 and am wondering if one of my modifications to the build.prop would still work. I use the following modification for enabling hotspot:
net.tethering.noprovisioning=true
Can anybody confirm that this still works on Android 10?
Also, huge noob question - Where is the guide for updating from 9 -> 10 with root/unlock, and do I lose my data in the process? I can't seem to find anything but how to sideload monthly updates.
Thank you in advance for any help
To edit /system or /vendor you need to use magisk and do it systemlessly. A10 no longer allows you to directly modify these partitions. There is some discussion about exactly what you want to change under the guides section in the Pixel 3xl forum. For the second one, there is a guide somewhere in the guides section in this forum. You will need to do a full wipe with a version change. Look into different ways to back up your stuff before you switch. For apps and app data I did a twrp backup before switching then used titanium backup once on A10 to extract the app/data and restore it. For other stuff you might need to do it manually.
Follow this method for the Magisk based tethering modification:
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
(Works on Pixel 3)
Hi everyone.
The latest version of OOS 11.0.6.8 on the 8t EU seems to have enabled 5g in the settings / connection in France.
These network parameters are not yet available for the 8 pro.
As any luck is that a charitable soul could put me please a link drive or other of the two following files:
- carrier_policy.xml
- carrier_policy.xml_Subscription01
These two files can be found in the policyman folder using the qpst explorer.
These two files contain the operator parameters to activate 5g in particular.
I am in a 5g zone but these settings have not been activated for the 8 pro.
Thank you again for the one who will waste some of his time for this request
Hey Guys,
So along with my struggle of loading MBN files, I eventually used a Xiaomi Mi 11 Ultra (Global Edition) for a few days. This is another device that runs on the Same Snapdragon 888 SOC, and has the exact same Modem (Codename Lahaina). On the Mi 11 Ultra, Both my carriers have 5G / VoLTE working perfectly fine and had no issues whatsoever.
I opened up both the modem.img files (Can be viewed with 7Zip) and even the file structure is identical including the codenames, with the difference Xiaomi modem having more MBN files for many more carriers (I posted the MBN file extracted over here), (including the two MBN files my carriers use). On the other hand ASUS Modem.img has a very limited number of MBN files, which looks like they haven't updated it since the summer of 1969.
This is the Xiaomi Mi 11 Ultra Modem.img
File on MEGA
mega.nz
This is the ZS673KS (ROG 5) Modem.img
File on MEGA
mega.nz
Since there is no way to upload MBN files to the ROG 5 - Does anyone know whether we can fastboot flash the Modem image ?
Edl try
Akkaya34 said:
Edl try
Click to expand...
Click to collapse
Modem can be flashed over Fastboot.
Not required EDL.
But need to verify whether this has any risks. Only the chip (SOC) brand is same, but internally there might be other differences, and the image sizes are not the same either. So worried of hard brick.
BLOB images have the same code but very different interface to the kernel in most cases, so it's not likely anything will work
yurishouse said:
BLOB images have the same code but very different interface to the kernel in most cases, so it's not likely anything will work
Click to expand...
Click to collapse
Thanks a lot of the headsup !
Would the idea work better with rog 5 u.s modem blob?
Heero0101 said:
Would the idea work better with rog 5 u.s modem blob?
Click to expand...
Click to collapse
US version might have hardware differences .. So im not really sure.
Confirmed not working, restored partitions previously backed up for next surgical op.
katalinscrob said:
Confirmed not working, restored partitions previously backed up for next surgical op.
Click to expand...
Click to collapse
Thanks a lot for trying! Much appreciated!!
No pb! The main issue now that I have volte working along real 5G on both sim slots, is vowifi... PDC was the ideal method, but if sysprop vendor.usb.diag 1 command triggers correct diag mode, then for sure is another issue here, A11 related I guess...
katalinscrob said:
No pb! The main issue now that I have volte working along real 5G on both sim slots, is vowifi... PDC was the ideal method, but if sysprop vendor.usb.diag 1 command triggers correct diag mode, then for sure is another issue here, A11 related I guess...
Click to expand...
Click to collapse
How did you get VoLTE working?
Did you have the MBN inside already?
PDC is sadly blocked in A11 OS mode. However OnePlus Users They have a FTM mode - Which allows Efs tools / PDC to communicate. Hopefully something should come around for Asus.
You need root first of all.
There are 2 ways for permanent volte/vowifi toggle menus:
1. *#*#4636#*#*, set preffered network type NR/LTE, then back to original.
2. Magisk module Pixel5_VoWIFI.VoLTE_magisk_module_V1-MINI.zip (search github)
After this, via EfsTools method just copy to NV your carrier mbn from attached folder, reboot. Tried all of them until found compatible one from my carrier but no VoWIFI sadly.
katalinscrob said:
After this, via EfsTools method just copy to NV your carrier mbn from attached folder, reboot. Tried all of them until found compatible one from my carrier but no VoWIFI sadly.
Click to expand...
Click to collapse
Which thread did you follow?
I had a problem with my device not connecting via WIFI.
Full support 5G+VoLTE+VoWIFI:
1. Flash last A11 firmware WW-18.0840.2201.229 and root it.
2. Through QPST and AsusVOLTE apk, connect via wifi /same IP option ( I used IPV4+IPV6).
3. Download and unrar attached EfsTools, which contains the mcfg.mbn** and load it to NV.
4. Flash A12 firmware WW-31.0810.1226.57.
5. Root again, install voenabler*** module in magisk, restart.
**A11 banner mbn in .rar is for GermanyVodafone.
*** voenabler or any other method you agree with for enabling 4G/VOWIFI menus in settings.
In A12 banner is HW_DEFAULT instead any previous A11 carrier specific mbn, which means that ASUS finally resolved this problem for good.
Later edit: will try to extract and upload modem.img already modded for easy fix this entire stupid issue which Asus could have been more responsive to buyer's needs ...
Enjoy!
Since after .77 update lost again volte and vowifi, so disapointed... Respawned .mbn and voila, back in time with only volte capability, no vowifi.
Because I don't want to get through previous posted procedure, as I would be stuck in .57 basically, I found an alternative solution that could offer updates advantages and minimum-hassle procedure for regaining volte/vowifi, which basically is copying working mbn unpacked files to efs partition via efsExplorer in QPST. I tried mbn from an identical X60 qualcomm/lahaina chipset (found on xiaomi12t) and volte/vowifi working again, but no 5G this time. Anyway, is a matter of pacience and time for testing.
Another solution would be modifying modem.img extracted from Asus payload.bin but I didn't found an easy way to unpack/repack, only managed to open it through 7zip and get some resources. If you can find a solution to this, I think this would be the most elegant way for us to have all modem's capabilities activated, by simply restore modified-modem.img after every update.
And yes, tried AIK, various .img unpackers etc...