Related
Hello,
My carrier (SFR France) doesn't recognize the One SV, because it's not in their database.
How can i make the carrier believe the phone is another phone, like a Desire 601?
Thanks,
Did you try to edit build.prop?
Thanks for the answer. i didn't think it was that easy. However i'm not ready to root my phone. (Warranty, risks etc...)
I've manage to open, read, copy to SD card and modify with text editor, but how can i push it back (and not loose modifications after reboot)
(adb, something else? )
anyway. I've check the build.prop and found i need to change the ro.product.model= xxx
Now i just need to push it back. Could ADB or Fastboot do it ?
Any idea on how device identification works when it's not an android phone ?
Regards,
Well I never try to use adb without root, but I think without root you can't edit system files. Fastboot will not work. You need root or costume recovery.
Ivory_75 said:
Thanks for the answer. i didn't think it was that easy. However i'm not ready to root my phone. (Warranty, risks etc...)
I've manage to open, read, copy to SD card and modify with text editor, but how can i push it back (and not loose modifications after reboot)
(adb, something else? )
anyway. I've check the build.prop and found i need to change the ro.product.model= xxx
Now i just need to push it back. Could ADB or Fastboot do it ?
Any idea on how device identification works when it's not an android phone ?
Regards,
Click to expand...
Click to collapse
Unless you unlock your bootloader and root then there is really nothing you can do to the build.prop file. Restrictions won't allow you to make changes.
Sent from my K2_CL using Tapatalk
Question is in the title is there any way to get the selinux status to permissive on the AT&T note pro12.22 using stock rom?
I have already tried the sm P905 method for Qualcomm on here without success. I do have root but it is not enough as most of my root apps such as usb bt joycenter gold need the permissive state to function properly. I was just wondering if anybody knew if this is possible or if AT&T customers have been brickwalled again as with the note 3 and the bootloader locked
Xenoghost42 said:
Question is in the title is there any way to get the selinux status to permissive on the AT&T note pro12.22 using stock rom?
I have already tried the sm P905 method for Qualcomm on here without success. I do have root but it is not enough as most of my root apps such as usb bt joycenter gold need the permissive state to function properly. I was just wondering if anybody knew if this is possible or if AT&T customers have been brickwalled again as with the note 3 and the bootloader locked
Click to expand...
Click to collapse
Someone needs to build a permissive kernel for the p907a.
Xenoghost42 said:
Question is in the title is there any way to get the selinux status to permissive on the AT&T note pro12.22 using stock rom?
I have already tried the sm P905 method for Qualcomm on here without success. I do have root but it is not enough as most of my root apps such as usb bt joycenter gold need the permissive state to function properly. I was just wondering if anybody knew if this is possible or if AT&T customers have been brickwalled again as with the note 3 and the bootloader locked
Click to expand...
Click to collapse
I wanted to know the same thing when I first bought my note pro as it couldn't read my external drive formatted NTFS. I was never able to set the kernel to permissive (needed for apps that mount ntfs drives) so I ended up reformatting my hard drive to exFat. The only bad thing is now I can't store a disc image for my windows laptop as it wants the file system to be NTFS to begin the backup! I'm not sure whether to sell my tablet now as the locked bootloader is a real pain. If its a laptop replacement then it has to read my hard drive and I need it formatted NTFS.
jordant2 said:
I wanted to know the same thing when I first bought my note pro as it couldn't read my external drive formatted NTFS. I was never able to set the kernel to permissive (needed for apps that mount ntfs drives) so I ended up reformatting my hard drive to exFat. The only bad thing is now I can't store a disc image for my windows laptop as it wants the file system to be NTFS to begin the backup! I'm not sure whether to sell my tablet now as the locked bootloader is a real pain. If its a laptop replacement then it has to read my hard drive and I need it formatted NTFS.
Click to expand...
Click to collapse
Yes sir this tablet is entirely too tied down too be any sort of laptop replacement. It's essentially a tablified sm n900a (AT&T note 3) with the bootloader being locked and all. If it's any indicator given how robust the development community is for that device and how minute the one for this one is......I doubt we will see an unlocked bootloader at all seeing as how the n900a's remains yet to be unlocked and it has been out for nearly a full year now. All well price you pay for lte I guess. I really wish AT&T would stop alienating their customers though
I also have the p907a and am trying to disable the selinux or set it to permissive. I have completely deleted the files related to knox, and I am fully rooted. Mine also doesn't print an error for setenforce 0, it just doesn't work. I have also tried wanam xposed which claims to be able to set permissive, it also didn't work.
I have been spending time looking for the bootloader partition in hopes that like desktop linux, I can edit the kernel params sent before booting and just add selinux=0. If anyone has any clue which /dev/block device it is hiding under please let me know
I have also found and tried setprop ro.build.selinux.enforce 0. This also is ignored by the system. The 2 /dev/block devices that seem promissing are:
/dev/block/mmcblk0p6 alias aboot and /dev/block/mmcblk0p14 alias boot. Now I don't know if these are generated on install and therefore different for each system but I am attaching the image files of these block devices. aboot is identified as "Hitachi SH big-endian COFF object, not stripped" the other one as data. Anyway Maybe someone else on here can help figure out next steps. As they are binary that is out of my skill level.
ok looking around on the forums boot.img is a packed kernel and ramdisk. Hopefully the settings are in the ramdisk or something. Does anyone have the tools to unpack the boot.img and internal zimage and ramdisk for OSX? I see there are tools for windows and linux, but I couldn't find any for mac
Thanks
Most forums frown on making new threads when the subject is already covered. The op may have given up but I haven't... Do I open my own thread????
Is there any new instruction how to force VoLTE and VoWifi to work on PIXEL3?
Features works great on S9, SIM card is provisioned. The IMS options are blacked out on PIXEL.
Does any Custom ROM forces the feature to work even if carrier says that they don't officialy support it?
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
wangdaning said:
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
Click to expand...
Click to collapse
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
mxtuu222 said:
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
Click to expand...
Click to collapse
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
wangdaning said:
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
Click to expand...
Click to collapse
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
mxtuu222 said:
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
Click to expand...
Click to collapse
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
wangdaning said:
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
Click to expand...
Click to collapse
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
mxtuu222 said:
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
Click to expand...
Click to collapse
That is problematic, as looking at the modem files (on my device), their is nothing under the folders for PLAY network. That would mean you could get the modem file from another similar device that has it, but the magisk setup would need to change two files instead of one. You would have to mock load a mbn file for your provider. You would need to change /mcfg_sw/generic/"modem file you want to try" and /mcfg_sw/mbn_sw.txt to include the directory of the file you want to include.
In reality, those mbn files you get might never work. This is google borking their work. For us in China, the modem files are their, they just refuse to reference them. For you the files are not even there it seems.
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
wangdaning said:
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
Click to expand...
Click to collapse
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
mxtuu222 said:
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
Click to expand...
Click to collapse
I am pretty sure you will need to keep root, as magisk is mocking the modem file you need. It somehow could cause the phone to connect and after the phone stays connected, but I do not see how that could work.
I'm mostly worried about the Note 20 Ultra, but I don't believe this question is specific to that phone.
Are the CSC/HOME_CSC .tar.md5 files you can download with Frija and push with Odin signed in any way to prevent modification?
I have to assume they are, but I can't find where the signature is for the life of me. The only thing directly embedded in the file is the md5, which is easily changeable.
Even within the tarball and the images inside, I can't find any sort of signature file. Does the simg file format include a signature?
Basically, I'm trying to add some MCC MNCs to a particular sales/carrier code so when a SIM is inserted with that MCC/MNC, it triggers the automatic change over. The U (branded phones) CSC has this MCC MNC in the XMLs, but it's not in the U1 (unlocked) version of the CSC config for whatever reason. The problem is with the U CSC, it won't trigger a change when a new SIM is inserted because of other config changes in the customer.xml. The goal is to be able to do the change without tripping Knox or needing root, because that'd mean my work's MDM would prevent me from connecting.
what are you trying to do?
I remove the .md5 extension. but if you're worried about tripping knox
Don't go ahead with it.
vegadoom said:
I'm mostly worried about the Note 20 Ultra, but I don't believe this question is specific to that phone.
Are the CSC/HOME_CSC .tar.md5 files you can download with Frija and push with Odin signed in any way to prevent modification?
I have to assume they are, but I can't find where the signature is for the life of me. The only thing directly embedded in the file is the md5, which is easily changeable.
Even within the tarball and the images inside, I can't find any sort of signature file. Does the simg file format include a signature?
Basically, I'm trying to add some MCC MNCs to a particular sales/carrier code so when a SIM is inserted with that MCC/MNC, it triggers the automatic change over. The U (branded phones) CSC has this MCC MNC in the XMLs, but it's not in the U1 (unlocked) version of the CSC config for whatever reason. The problem is with the U CSC, it won't trigger a change when a new SIM is inserted because of other config changes in the customer.xml. The goal is to be able to do the change without tripping Knox or needing root, because that'd mean my work's MDM would prevent me from connecting.
Click to expand...
Click to collapse
We aren't going to help you bypass your employer's policies/standards in how the device is used. The device belongs to the company, they are the owners, not you, you just use the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
We aren't going to help you bypass your employer's policies/standards in how the device is used. The device belongs to the company, they are the owners, not you, you just use the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
No, this is my personal device that I own, and I just happen to have my work email and calendar on it. I'd like to keep work access because it's convenient, not because it's an actual requirement of my job.
Regardless, the point is to see if the FW would be rejected during flashing, or if the phone would accept it and trip knox. I'd much rather the phone straight reject the new tarball than accept it and trip knox.
vegadoom said:
No, this is my personal device that I own, and I just happen to have my work email and calendar on it. I'd like to keep work access because it's convenient, not because it's an actual requirement of my job.
Regardless, the point is to see if the FW would be rejected during flashing, or if the phone would accept it and trip knox. I'd much rather the phone straight reject the new tarball than accept it and trip knox.
Click to expand...
Click to collapse
Yes, it is possible to modify the various .tar files from the firmware then convert them back to .tar files and flash them successfully. But, it may depend on things like your bootloader and/or the binary version of the firmware files being flashed versus the binary version of the firmware already installed on the device. It may or may not require using a modified/patched version of Odin to get the modified .tar to flash without issues.
As long as you aren't modifying the bootloader, kernel or system.img, tripping Knox should not be a problem, I would think. Knox is only a watchdog that is mainly looking at bootloader status, kernel state and system status.
Sent from my SM-S767VL using Tapatalk
That's great to know, thanks.
I did manage to find a less intrusive workaround, fortunately. See here: https://forum.xda-developers.com/showpost.php?p=83552501&postcount=82
I just bought a Xperia XZ2 H8276 since the sim pins finally broke in my Xperia X Performance after about 4 year, word of advice don't make a sim work. Was not finding a Xperia XZ2 compact under $200 and the newer 5's are expensive, so that was the choice I made. It did not dawn on me that the move to volte only would make it hard to get newer unlocked phones on a nework. In trun looking into options pertaining to volte, switching to verizon was the only one that seemed to have a viable path. Talked with at&t where I found them unwilling to add my imei and don"t see a mdn that is clear cut for them, do see a mdn for tmobile but no service by my house. Verizon dose have dmd and they got the XZ2 compact, so there was light at the end of the tunel. So got the cheapest volte phone that I could find to activate a sim on, a moto e5 play is what I found. Will get to aguing with them now to add my imei since it work, unsure how that is going to go.
To get statrted a activated sim is needed and was done using the moto e5. After activation, need to talk with someone and have them check that sim the sim is CDMA-less with HD voice only. Best place I found to do that is start a chat with someone on this page, click chat in bottom right.
Verizon HD voice
For how I got the XZ2 to work on verizon gose like this based on many failed attempts. What I ended up doing is flashing H8216 Vodafone_Global_52.1.A.3.49-R9C firmware with H8314 Customized US_52.1.A.3.137-R7C oem sin files with newflasher, you can get these these off xperiafirm.
NewFlasher
XperiaFirm
Now with that in order, the verizon mbn needs added but need root to do so. If you dont have twrp that need installed and be sure to sideload magisk at the same time, other wise you will have boot loop to deal with.
TWRP
Magisk
After the phone has booted into the os, you need to now install the magisk app. Run this from whre you downloaded the application to your pc or install from the browser on the phone, need to cd to the place of download first if using terminal.
adb install Magisk-v23.0.apk
Magisk app
Here is the verizon mbn I pulled from the XZ2c modem sin.
Verizon mbn
That needs copyed to the phone SD card and use Root explorer to copy the mbn where it gose. I tryed PDC but could not get the drivers to work.
Root Explorer
You can you use this to install it if debug is on or down from the phone browser, cd to where you downloaded the file then...
adb install RootExplorer.apk
Now in root explorer, this is the destination to go and can only go there if root has been granted. If you dont get the promt to grant root go into magisk, click the shield at boot then the slider by the app. To copy the generic folder here from the sd card, click and hold it till hilighted where you can click the two papers stacked at the top. There will now be a clip board icon in the bottom right, do to the destination and click it.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw
The internal and external sd card will be one these two locations, ether use "adb push" or mtp to the put the directory on the sd card.
/storage/*-* *=a string of letters and numbers
/storage/emulated/0
/storage/self/primary
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see this under current modem config
row/verizon/vl/us
Now dial this.
*#*#4636#*#*
Under phone information set network type to lte only and should see voice type lte. If all went well, you should now be able to make phone calls.
I would like to move on to installing lineage-os but volte was not working there. I need to use this phone for work, so am not going to get into debuging that. Be my guess to try but Im not sure what brakes installing that.
I got some help from junkie2100 and give thanks to those that have posted info/software that lead me this far in gettting volte working. Here are some the clues that aided in the journey.
clues
clues
clues
As for tmobile, you might be able to replicate this but intead use oem sin's from the xz3 H8416 US along with pulling its mdn out its modem sin. Not sure what is special in the oem sin that pertains to setting up the given carrier, so unsure what is needed to get at&t to work but you free to experiament if you choise just I will not be much help.
Thanks for taking the time to put this together, the information on getting VoLTE working in the US on the XZ2 seems to be pretty scattered across various threads over the last several years, so I appreciate you placing this here.
I am not on Verizon, but I have been trying to figure out how to get this working on T-Mobile. I have followed some other threads that point to downloading the XZ3 OEM sin files as part of its Customized US Firmware like you mentioned, replacing those in the stack for the XZ2 firmware of a matching/similar version, and flashing to my device. I noticed after doing that VoLTE is provisioned (greyed out but turned "on"), but the modem config when checking my settings is still "Unknown." In addition to that, setting the device to "LTE Only" causes calls to not be placed, and "LTE Preferred" leads to calls dropping down to 3G like they originally were before trying to flash anything.
I could maybe use a little help in understanding what you mean be "pulling the mdn out of the modem sin." Is this an additional step to just flashing the two OEM files mentioned above and if so, where would I find it and go about setting it up?
Appreciate it.
The mbn file you need is in the modem sin from the xz3 firmware and this is the binary you need to extract it, put both the unsin binary and modem_X-FLASH-ALL-B6B5.sin in the same folder. This is the config file used by the oem sin to setup the volte.
unsin binary
Now cd to the folder that has both those and run these commands.
./unsin ./modem_X-FLASH-ALL-B6B5.sin
mkdir ./modem
sudo mount -t vfat -o loop modem_X-FLASH-ALL-B6B5.img modem/
You now have the modem sin extracted and the image mounted in folder modem. From there you need a copy of this tmobile folder and move it to the sd card on the phone.
/image/modem_pr/mcfg/configs/mcfg_sw/generic/row/tmobile
Now you can umount the modem image.
sudo umount -t vfat modem_X-FLASH-ALL-B6B5.img modem/
Now on the phone in root explorer that tmobile folder gets copyed to here.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/row
In this file you will also need to add these two lines so the mbn can be found.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw//mbn_sw.txt
mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn
mcfg_sw/generic/row/tmobile/vlvw/us/mcfg_sw.mbn
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see one these under current modem config
row/tmobie/vl/us
row/tmobile/vlvw/us
Would anyone care to guess if a rooted/ rom'ed 8216 model of the XZ2 will work on T-mobile now that they have declared many older phone models incompatible (perhaps related to VoLTE capability)? 1mouse3 does your phone still work on T-Mobile? Thanks!