Hey y'all,
I have a customer with a google nexus 4, at least he thought so when he bought it from someone. After opening the package all the descriptions belonging to the phone where in chinese, which is weird but it still could bw a chinese produced phone. When googling the kernel number and discovering there was no play market nor support for google accounts I decided the device was a fake chinese piece of crap.
But forget all of the above, I found a way to install gapps anyway on this fake device, by just pushing all the folders of the flashable zip to the device, see the script I mirrored with DropBox. Unpack the script to some folder on your desktop and make sure usb debugging is turned on on your device. Then click install_gapps.bat and reboot your phone after the script is finished if it doesn't do this by itself.
I implemented the gapps for ICS-4.0.x, but if you want to install another gapps just place the "system" folder of the zip in de folder you just unpacked. In the script you can change wat you want to be pushed to your phone, the part which enables google accounts on your phone is located in system/lib I believe but I'm not sure so mod the script the way you want. The way it is now, it will enable google accounts
After this the phone has become a practically genuine nexus 4, with the exception is has different hardware and can't receive updates .
Please come back here for troubleshooting, I will try to help.
Hit the thanks button if this helped. If you even want to donate, you can go here: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=URRJAZ77AD4MG
Mirror 1:
https://dl.dropbox.com/u/49462631/install_gapps_fake_nexus_4.zip
We need a sub forum for the Fake N4 I guess
Ehhrrm, whaat? This probably belongs somewhere else mate..
Why would people even bother using a fake n4?
1: send it back for a refund
2: if refund is not an option then throw it in the bin
3: buy a genuine N4!
Problem solve
Why is this in the forums? This isn't development.
See Pictures : http://www.trustedreviews.com/lenovo-k900_Mobile-Phone_review
Lenovo K900 key specifications
1) 5.5-inch 1080p IPS capacitive touch display
2) Intel Atom Z2580 2GHz dual-core processor (Clover Trail+)
3) 2GB RAM
4) 16GB internal storage
5) 13-megapixel camera with Sony's Exmor BSI sensor
6) 2-megapixel front camera
7) Android 4.2 Jelly Bean
Video (Lenovo executive telling about market availability) : http://www.youtube.com/watch?feature=player_detailpage&v=w2LFxXwqVNo#t=147s
will be sold in China, India, Russia, Philippines, Vietnam and Indonesia in first phase.
More images Benchmarks and detailed preview (use google translate) : http://hi-tech.mail.ru/review/misc/Lenovo_K900-prev.html
For Root and Google apps(if missing) :
Credit to cyman for finding this out
Cyman said:
Everything I write here is originally from lenovoforum.net (http://www.lenovohome.net/thread-161530-1-1.html) so every credit goes to them and also Google Translate, who helped me to understand that Chinese stuff
1) So, first you have to download their package. Because it's a very slow connection, I'll offer it via my Dropbox. Please, can someone upload it on another hoster? This would be great, thanks. Anyway, the download link is: https://www.dropbox.com/s/ilxyuc9gimzpa0q/联想K900纯净版含google谷歌服务框架版已root线刷包 (1).rar PW for unpacking: www.lenovohome.net
2) You have to install the things which you can find in one of the folders in this order: First IntelAndroidDrvSetup1.2.0 (you may try to install it with compatibility mode Windwos XP, worked for me), then iSocUSB-Driver-setup-1.0. 2.exe (during this process it will tell you, that you have to plug in your phone and turn it off with holding the power button for longer than 10 seconds and then turn it on again). If you suceed you will see that it installs a new driver "Colvertrail". At last, you may install ManufacturingFlashTool_Setup_6.0.2.exe.
3) Now let's prepare the ManufacturingFlashTool for flashing our K900.
I don't know how to put screenshots in here. So I just tell you: Go to settings and put in this values: SOC devices: VID: 8086, PID: 09EE / Android Devices: VID: 8087, PID: 09ef
Check "Override". You'll find a screenshot of the settings in one of the Chinese Word files in the download folder
4) Now you can open a file in ManufacturingFlashTool and you'll open the xml-File, which is in the Firmware-Folder (calles "flash-DVT3-CPU-sign")
5) Now the program is ready to flash and says: "waiting for device". So this is what you have to do: Power off your K900 with holding the power button for 11 seconds. It may be black now but it is running! Plug the phone in and now it should detect it and automatically begin to flash. Wait until it's100%. Sometimes it reboots and it says "waiting for device" but it will finish.
6) When you have completed 100%, you may detach the phone and power it on. It may take a few minutes for the first time but now you'll have Google Apps
7) How to get ROOT: Go to superuser and hit the settings button in the right upper corner. Set "security" "Automatic response" to "allow". No you cann go back in the superuser app and hit "update", it should do a root now. For a better x86-compatible Root Explorer, you can install the apk in the attachement
Please excuse my English. Maybe somebody can write a better Guide with pictures? But I know you wanted it fast By the way: If you can't execute the exe-Files, try to pack them into a new folder because Windwos seems to have problems with the folders with Chinese signs.
Click to expand...
Click to collapse
olegfusion said:
I'm here for help you, and yes I bought K900
Here is the international .inb file to flash.
Part One: How flash international version:
1. create SDFUSE folder in the / of sdcard.
2. insert inb file there
3. go to fastboot mode (Vol+ + Power) and choose sdfuseupdate
4. done.
you'll get official international 47 rom (ROW region). It has google apps, it has play store.
INB file is here:
https://mega.co.nz/#F!xNdywAJA!AFbE_HikuoFODLpoc1j7Yg
Part Two:
I made HEX research and separated files from INB files. You'll not find those files in the internet, I didn't find it. So, I decided to research .inb
For debug, you can find them here:
https://mega.co.nz/#F!1YE1xDxC!IflBj13Im1549nu0feBvnw
Part Three:
I made root in the international 47 ROM.
how to?
1. download this system.img.gz:
2. go to fastboot mode (make sure you flashed 47 INB file already).
3. install manufacturing tool, all tools can be found here. https://mega.co.nz/#F!0UlDnLLR!IuQdqFqT-oIXtvRlQNtLBw Find fastboot in the program files folder, you'll need this fastboot.exe tool for intel phone.
4. use cmd,
fastboot erase system
fastboot flash system system.img.gz
by using those commands you re-flash system.img.gz that I made, it includes root (su library) and superuser. Superuser doesn't respond when need to allow or reject root, so you need to go and manually allow root rights in superuser for any application.
system img rooted: https://mega.co.nz/#F!MZ0SXRIT!R1ZAawbEjKcRm3ZXFJ0siA
Root was made by me, you'll not find this info in other sites. I write this info on xda first time.
Enjoy!
do not brick your phones, I'm not responsible if something you do wrong, but I tested and it works fine at my K900.
Click to expand...
Click to collapse
olegfusion said:
Yes.
But I found one more interesting thing. First time I flashed .inb file after chinese rom, but now I found full pack of fastboot files and flashed it (same 47 rom).
https://mega.co.nz/#F!IJF2hLYI!GpcLinegjjcRM6puQa0GXg
Wonder, but I have less heat releasing from the phone on the load of CPU.
I don't know why.
I recommend to flash full fastboot pack first, then boot and then step 4 - root.
p.s. files are uploaded
Click to expand...
Click to collapse
Nice
Markets : China, India, Russia, Philippines, Vietnam and Indonesia
still waiting for sertification in indonesia
Released in China http://thedroidguy.com/2013/05/lenovo-k900-china-availability-price-p780-massive-battery-release/
I hope it will be availible in Germany.
Sent from my Lenovo A789
Doesn't IBM own Lenovo? Anyway's great high end company. Makes great laptop and desktop. If price is good I would buy this then note2. Is this first android run on intel? I love the finish and the specs. But it's only a 3g .
jcervantes11 said:
Doesn't IBM own Lenovo? Anyway's great high end company. Makes great laptop and desktop. If price is good I would buy this then note2. Is this first android run on intel? I love the finish and the specs. But it's only a 3g .
Click to expand...
Click to collapse
Before this there were smartphones based on intel soc but only single core ones.
nikhiltanwar said:
Before this there were smartphones based on intel soc but only single core ones.
Click to expand...
Click to collapse
But on android? Is these atom as powerful as desktop atoms because desktop cpu and mobile cpu are totally different class.
jcervantes11 said:
But on android? Is these atom as powerful as desktop atoms because desktop cpu and mobile cpu are totally different class.
Click to expand...
Click to collapse
These are different but efficient.... like u see Dual core intel soc in this k900 matches performance of Octa core Samsung galaxy S4 ... there is difference of 6 cores and still it matches that performance.... desktops are still different class though... mobile devices cant score that kinda performance because of size of chip... Laptops have a powerful and bigger chip
$536 in china http://www.gsmarena.com/lenovo_k900_now_available_in_china_priced_at_536-news-6062.php
I can bet it wont be available in Europe because it is dual sim phone so it wont be available from operators.
robdevil said:
I can bet it wont be available in Europe because it is dual sim phone so it wont be available from operators.
Click to expand...
Click to collapse
will be available unlocked. but in later phases. Phase 1 is Asian countries
Hope so!
nice smartphone ,i'm already using it now ,but ,i need somebody help me find a way to get root~ because lenovo have install many apps can't be removed ,i don't need them。。。~!~
tadimy said:
nice smartphone ,i'm already using it now ,but ,i need somebody help me find a way to get root~ because lenovo have install many apps can't be removed ,i don't need them。。。~!~
Click to expand...
Click to collapse
Please post video.
---------- Post added at 08:29 PM ---------- Previous post was at 07:29 PM ----------
wait so it is only a 2g if i use tmobile? It goes up to 3g but why isn't it so it can be used on 4g network? This phone isn't worth nothing if data isn't quick.
It was rumooured to come on 10th mat for under 25 k..
Still not arrived and priced around 536$ 30k...
Now i dont think i would buy that ...
Instead i would prefer a note 2...
jcervantes11 said:
Please post video.
---------- Post added at 08:29 PM ---------- Previous post was at 07:29 PM ----------
wait so it is only a 2g if i use tmobile? It goes up to 3g but why isn't it so it can be used on 4g network? This phone isn't worth nothing if data isn't quick.
Click to expand...
Click to collapse
I just ordered one from China, so I'll find out if it works with T-Mobile. Intel's modem chip definitely supports UMTS 850/900/1900/2100. But if for some bizarre reason it's blocked by Lenovo, it should work at least on AT&T's 2100.
But it appears that it probably should work with T-Mobile as well. See this: http://forum.xda-developers.com/showthread.php?t=2286627
MacGuy2006 said:
I just ordered one from China, so I'll find out if it works with T-Mobile. Intel's modem chip definitely supports UMTS 850/900/1900/2100. But if for some bizarre reason it's blocked by Lenovo, it should work at least on AT&T's 2100.
But it appears that it probably should work with T-Mobile as well. See this: http://forum.xda-developers.com/showthread.php?t=2286627
Click to expand...
Click to collapse
What is the top speed of AT&T's 2100. I want a phone to run straight talk tmobile but i want the tmobile 4g speed. Or att 4g speed.
---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------
MacGuy2006 said:
I just ordered one from China, so I'll find out if it works with T-Mobile. Intel's modem chip definitely supports UMTS 850/900/1900/2100. But if for some bizarre reason it's blocked by Lenovo, it should work at least on AT&T's 2100.
But it appears that it probably should work with T-Mobile as well. See this: http://forum.xda-developers.com/showthread.php?t=2286627
Click to expand...
Click to collapse
Please post picture and videos.
I bought one from China. Its an awesome device so far. Will be posting an unboxing on youtube later today. The part that sucks right now is no Google Play. I've just been sideloading my apps, but no google apps. I am trying to find information on how to root it. So far I haven't found anything. Please chime in if you have any info on that.
I'm writing this post to track my efforts to enable VoLTE and WiFi Calling on my X Compact. To begin with, I don't have a solution yet. I think I understand a lot of how it's supposed to work, but there are still some things I don't know. Hopefully others will be able to chime in and provide some answers.
I use my phone on MetroPCS in the USA. They are an MVNO for T-Mobile (and also owned by T-Mobile). I know that they support both features as my wife's Moto X4 is able to use them.
The X Compact does support VoLTE:
https://support.sonymobile.com/us/x...do-i/801930746ffcf563015c0bfaac370057e6/#gref
The problem is, it's only supported on specific carriers. The first requirement is that the carrier supports VoLTE (MetroPCS). The second requirement is that the feature has to be approved by Sony to be used on that carrier. This is where people have problems. I don't know how Sony makes the approval list, but my carrier isn't on it.
Before digging into this, I had planned on upgrading to the XZ1 Compact because it is specifically advertised as having VoLTE working on T-Mobile. I bought one and expected it to work out of the box on MetroPCS, but it didn't. I went back and forth with both MetroPCS and Sony and it still didn't work. This goes back to the list I mentioned above. If your carrier isn't on it, the phone won't work.
So I'm stuck with a phone that would work perfectly well with these features, but due to carrier/manufacturer approval issues, won't. Moving forward, I'll discuss the things that I've tried to get it to work.
Try making the XC work like the XZ1C
As I mentioned above, the XZ1C supports both features natively on T-Mobile. Why it works on T-Mobile came up in the following thread trying to get VoLTE and fingerprint support at the same time on T-Mobile:
https://forum.xda-developers.com/xperia-xz1-compact/help/volte-tmo-fingerprint-sensor-t3666387
So why does the XZ1C work on T-Mobile? @pbarrette did a good job of explaining the process in this post:
https://forum.xda-developers.com/showpost.php?p=74159245&postcount=105
The XZ1 and the XZ Premium both use the same chipset as the XZ1C, but those features don't work on T-Mobile. In trying to figure out why, @pbarrette determined the mechanism Sony uses to enable this feature. That work is covered in the following thread:
https://forum.xda-developers.com/xz-premium/help/volte-t-mobile-enabled-t3627567/
Simply, the XZ1C has additional files which are triggered to be used when a T-Mobile SIM is placed in the phone. To get the features to work on the XZ1 and XZP, you need to copy the appropriate files on to the phone. @pbarrette created a flashable zip file which does this and it works for those phones. The most important file to get the features working is the proper modem binary file (/etc/customization/modem/), tmobile_us_ims on the XZ1C. Unfortunately, there's no corresponding file on the XC.
I thought that I could just copy the binary file from the XZ1C, but the phones use different hardware so it's likely that a file from one phone won't work on another. I did a file comparison of the default (XC: amss_fsg_kugo_tar.mbn, XZ1C: amss_fsg_lilac_tar.mbn) and T-Mobile (XC: amss_fsg_kugo_tmobile_us_tar.mbn, XZ1C: amss_fsg_lilac_tmobile_us_tar.mbn) modem binary files from each phone, and they're quite different. So it seems like that option won't work.
Even if the XZ1C files did work on the XC, the problem still remains that the XZ1C doesn't work on MetroPCS. So I'd get a franken-ROM that doesn't do what I want it to.
Afaik your operator need to enable volte for your specific device. Here, my operator doesn't support xc and even if I force enable volte it still doesn't work. I contacted them and they said that they have to do some tests and then enable it to use volte.
maluus said:
Afaik your operator need to enable volte for your specific device. Here, my operator doesn't support xc and even if I force enable volte it still doesn't work. I contacted them and they said that they have to do some tests and then enable it to use volte.
Click to expand...
Click to collapse
You might be right, but some of the success stories that I've read lead me to believe that it's not device specific. I'll dig into that in a later post. I've contacted my carrier and according to them, everything is set on their end, so that just leaves the device being the issue.
Try making the XC work like the XZ1C, Part 2
Per @pbarrette, the proper files are loaded only when a SIM with the correct ID is inserted into the phone. For the XZ1C, this info is located in /overlay/com.sonymobile.customizationselector-res-305.apk in a file called configuration_selectors.xml. A file of the same name is also present in the same location on the XC. The sim_config_id can be found by entering the following command with USB debugging enabled:
Code:
adb shell getprop persist.sys.sim_config_ids
When I enter this, I get S8957.1. That value isn't in the configuration_selectors.xml list so the proper files aren't loaded and the default modem binary is used. If it were in the configuration_selectors.xml list, a config_id value of 400 would be associated with the sim_config_id (408 for XZ1C). Your config_id value can be found using the following command:
Code:
adb shell getprop ro.semc.version.cust.active
When I enter this command, I end up with a blank. I believe that this is because the default modem binary is being used, but this is just a guess. Ultimately, it means that the SIM isn't recognized and therefore the features won't work.
There's another file that's part of /overlay/com.sonymobile.customizationselector-res-305.apk, and that is service_providers.xml. I believe that this is where the proper sim_config_id is selected, based upon the MCC and MNC for the carrier. In my case, those values are 310 and 260, respectively. There are two entries which match these values:
Code:
<service_provider_sim_config sim_config_id="S8957.1">
<mcc>310</mcc>
<mnc>260</mnc>
<sim directory="7FFF" file="6F3E">6D</sim>
</service_provider_sim_config>
<service_provider_sim_config sim_config_id="S264.8">
<mcc>310</mcc>
<mnc>260</mnc>
</service_provider_sim_config>
There have been times in the past that my phone has been assigned the sim_config_id or S264.8, but most of the time it's S8957.1. I'm not sure what the sim directory tag refers to. If anyone knows what this means, please let me know as it might be helpful.
So my first strategy of trying to mimic the way the XZ1C works doesn't appear to be an option. A question for others: would it be possible to decompile the relevant files, change the xml files to reference the id's that I'm seeing, recompile and replace the APK's, all without sending my phone into a bootloop? Yes, see below.
But even if that were to work, there's no corresponding modem binary file on the XC, so probably no VoLTE. But there are other modem binary files. Could I just rename one of those? Would using the file from the XZ1C crash the modem on the XC? Yes, see below.
Try making the XC work like the XZ1C, Part 3
Alright, I've had partial success. Using some of the overlay files from the flashable zip that @pbarrette created, I was able to get the VoLTE and WiFi Calling menus to show up in settings. Here's a summary:
Flash old firmware. I used this one available on XperiFirm: F5321_34.1.A.1.198_Commercial and Journalists (1305-9054). It's not strictly necessary to flash the old firmware, but you need root, and root requires an unlocked bootloader, and unlocking the BL will delete your TA partition. I wanted to backup the TA partition for my DRM keys. In order to use the backup tool, you have to use an older version of Android so that the exploit used by the backup tool is still available.
Backup TA partition
Flash current firmware (34.4.A.2.118)
Unlock bootloader (use the Sony Mobile website for this)
Root phone (I used the method described here with the DRM fix option. The use-your-own-TA option didn't work for me.
https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
Install the following files from the @pbarrette flashable zip:
/oem/modem-config/408/modem.conf
/oem/overlay/android-res-305.apk
/oem/overlay-408/android-res-310-408.apk
/oem/overlay-408/com.android.carrierconfig-res-310-408.apk
/oem/overlay-408/com.android.phone-res-310-408.apk
/oem/overlay-408/com.android.settings-res-310-408.apk
/oem/overlay-408/com.android.systemui-res-310-408.apk
/oem/system-properties/408/config.prop
You also need to install /oem/overlay/com.sonymobile.customizationselector-res-305.apk, but I had to modify the file from the XZ1C to get things to work. Within the APK, there's one XML file that needs to be updated to include the sim_config_id I'm seeing on MetroPCS. That is /res/xml/configuration_selectors.xml. I modified it to look like the following (with my addition in red):
Code:
<?xml version="1.0" encoding="utf-8"?>
<configurations>
<configuration config_id="408">
<sim_config_id>S264.1</sim_config_id>
<sim_config_id>S264.2</sim_config_id>
<sim_config_id>S264.3</sim_config_id>
<sim_config_id>S264.4</sim_config_id>
<sim_config_id>S264.5</sim_config_id>
<sim_config_id>S264.6</sim_config_id>
<sim_config_id>S264.7</sim_config_id>
<sim_config_id>S264.8</sim_config_id>
<sim_config_id>S264.9</sim_config_id>
<sim_config_id>S264.10</sim_config_id>
<sim_config_id>S264.11</sim_config_id>
<sim_config_id>S264.12</sim_config_id>
<sim_config_id>S264.13</sim_config_id>
<sim_config_id>S264.14</sim_config_id>
<sim_config_id>S264.15</sim_config_id>
<sim_config_id>S264.16</sim_config_id>
<sim_config_id>S264.17</sim_config_id>
<sim_config_id>S264.18</sim_config_id>
<sim_config_id>S8663.1</sim_config_id>
[COLOR="Red"]<sim_config_id>S8957.1</sim_config_id>[/COLOR]
</configuration>
</configurations>
To do this, I decompiled the Sony APK from the XZ1C, changed the file, recompiled the APK, signed the file, then placed the file in the /oem/overlay directory with Solid Explorer, and made sure the file permissions were correct.
It's worth mentioning that /oem/modem-config/408/modem.conf lists the modem binary file to be loaded when a T-Mobile SIM is detected. On the XZ1C, this is tmobile_us_ims and that's what modem.conf lists by default. You'll need to change this to one of the modem binary files contained on the XC. I tried using the tmobile_us_ims modem binary file from the XZ1C and it sent my phone into a bootloop. So it's confirmed that the XZ1C modem binary files aren't compatible with the XC. Just pick one from the /etc/customization/modem folder, like amss_fsg_kugo_a1_austria_ims_tar.mbn and list this in the file. You'll need to cut out the prefix and suffix, so just a1_austria_ims for this example. The prefix and suffix will get added by the phone when selecting the file.
Trigger a SIM check by CustomizationSelector. To do this, I deleted the file /data/data/com.sonymobile.customizationselector/shared_prefs/com.sonymobile.customizationselector_preferences.xml and rebooted (as suggested by @pbarrette here: https://forum.xda-developers.com/showpost.php?p=74560870&postcount=76 and here https://forum.xda-developers.com/showpost.php?p=74560870&postcount=77). After a couple of minutes, my phone stated that it needed to reboot to optimize for my network. Once it loaded back up, the proper overlays had been loaded and I could see the settings for VoLTE and WiFi Calling.
This is where my success stops. Without the proper modem binary file, it's a bit of a crapshoot to see if an existing file will work. To do this, just repeat steps 8 and 9 with a different modem binary file. I've tried a handful of these files, but no luck yet. There are 127 files, but I'm sticking with the ones that mention IMS or VoLTE. This reduces the total to 88, but it's still a lot of rebooting and waiting. The files I've tried so far are listed below.
amss_fsg_kugo_a1_austria_ims_tar.mbn
amss_fsg_kugo_a1_austria_volte_vowifi_tar.mbn
amss_fsg_kugo_bouygues_france_ims_tar.mbn
amss_fsg_kugo_bouygues_france_volte_vilte_tar.mbn
amss_fsg_kugo_ee_ims_tar.mbn
amss_fsg_kugo_singtel_ims_tar.mbn
amss_fsg_kugo_telefonica_uk_ims_tar.mbn
amss_fsg_kugo_telekom_germany_ims_tar.mbn
amss_fsg_kugo_tmobile_us_tar.mbn
amss_fsg_kugo_vivo_ims_tar.mbn
amss_fsg_kugo_vodafone_germany_ims_tar.mbn
amss_fsg_kugo_vodafone_spain_ims_tar.mbn
amss_fsg_kugo_vodafone_uk_ims_tar.mbn
amss_fsg_lilac_tmobile_us_ims_tar.mbn
So that's my current status. I'm not planning on doing anything else at this point, because I figured out a way to get my XZ1C working on MetroPCS with VoLTE and WiFi Calling. I'll write a bit about that over in the XZ1C forum. If anyone wants to continue looking into it, please provide an update.
Software Used
In case someone wants to work through this process on their own, here is the software that I used:
Flashtool: Used for flashing firmware to the XC via FTF files. This can also be used to extract the contents of some older SIN files.
http://www.flashtool.net/index.php
newflasher: An alternative to Flashtool. I didn't use this, but I saw it referred to a lot.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
UnSIN: This program can be used to extract the contents of more modern SIN files.
https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106
ext2explore: Tool to explore ext4 image files. Once you've used UnSIN, you end up with an ext4 file. This tool can explore the ext4 file and extract files from it.
https://sourceforge.net/projects/ext2read/files/Ext2Read ver 2.0/ext2explore 2.0 beta/
Google platform tools: This includes ADB, fastboot, etc. It comes with the Android SDK, but that file size is massive so Google conveniently packaged just the platform tools in a much smaller zip file.
https://developer.android.com/studio/releases/platform-tools
apktool: This is a tool to decompile/compile APK files. There are other tools out there, but this is the one that I used.
Tool download: https://ibotpeaches.github.io/Apktool/
Guide I used: https://forum.xda-developers.com/showthread.php?t=2213985
Flashable zip guide: I ended up editing the flashable zip from @pbarrette to include only the files I listed above. It was pretty straight forward to edit the script just looking at it, but this was a good resource for explaining things in more detail.
https://forum.xda-developers.com/an...-complete-shell-script-flashable-zip-t2934449
Dirtycow-based TA Dumper for Sony Xperia Devices: This what I used to backup my TA partition.
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
sgs2toext4: This tool can convert an IMG file (eg. boot.img) to ext4. I used it in some of my tinkering (trying to get use-your-own-TA root option working) but I don't think you'll need it
https://forum.xda-developers.com/ga...n-zipalign-t1132724/post15333542#post15333542
Mate there is a magisk module to enable that menu options. But although enabled, neither volte nor vowifi does work without operator support. Does your operator list supported devices for volte? If so, you can risk to change the signatures of your device with a supported and identical platforms.
maluus said:
Mate there is a magisk module to enable that menu options. But although enabled, neither volte nor vowifi does work without operator support. Does your operator list supported devices for volte? If so, you can risk to change the signatures of your device with a supported and identical platforms.
Click to expand...
Click to collapse
Interesting. I've not heard of that module. MetroPCS doesn't list compatible devices as far as I know, but I know of unlocked devices that do work. Could you please provide a link to that module you mentioned?
I don't have Magisk installed but you can search volte in modules library. I think name was the volte enabler or something similar
maluus said:
I don't have Magisk installed but you can search volte in modules library. I think name was the volte enabler or something similar
Click to expand...
Click to collapse
Was it this one? If so, the module isn't doing anything that I'm not already doing. Is there a module that allows for using the Modem Switcher on Sony phones?
https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613
camdecoster said:
Was it this one? If so, the module isn't doing anything that I'm not already doing. Is there a module that allows for using the Modem Switcher on Sony phones?
https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613
Click to expand...
Click to collapse
Yes it is. Btw I noticed a phrase in OP which points out the problem as I stated earlier.
"My carrier supports VoLTE/VoWiFi but not on my device. I made this module to forcefully enable it to test if it worked (it hasn't so far)."
I don't know your provider but still it seems operator support is based on individual devices as it is in my case. When I first call the support center of my carrier the person told me that if my phone does support volte there shouldn't be a problem. I insisted that my phone supports volte and she said that she ll check with tech department and a few minutes later called me back saying indeed they don't support my device. long story short I can't use volte as of now. they support a device from loire platform so may be if I change identification of device to that one to trick the operator network to believe I use the supported device it may work but I have my doubts about consequences so I did not dare yet
maluus said:
Yes it is. Btw I noticed a phrase in OP which points out the problem as I stated earlier.
"My carrier supports VoLTE/VoWiFi but not on my device. I made this module to forcefully enable it to test if it worked (it hasn't so far)."
I don't know your provider but still it seems operator support is based on individual devices as it is in my case. When I first call the support center of my carrier the person told me that if my phone does support volte there shouldn't be a problem. I insisted that my phone supports volte and she said that she ll check with tech department and a few minutes later called me back saying indeed they don't support my device. long story short I can't use volte as of now. they support a device from loire platform so may be if I change identification of device to that one to trick the operator network to believe I use the supported device it may work but I have my doubts about consequences so I did not dare yet
Click to expand...
Click to collapse
My carrier does offer VoLTE and WiFi Calling and those features do work on unlocked phones, so I'm pretty sure it's a Sony problem. In fact, I recently got those features working on an XZ1C. It could work on an XC too, but I'm moving on to the XZ1C. I hope someone gets it to work. Good luck with your carrier.
Don't know if anyone interested, but I found this on a Chinese forum - http://bbs.gfan.com/forum.php?mod=v...rby=lastpost&typeid=&typeid=&orderby=lastpost Apparently, if you flash the 2 files in the link, (http://bbs.gfan.com/android-9530989-1-1.html), it will work. I was going to test it out, but you need an account with some Chinese file sharing service, and I didn't feel like trying to figure it out...
Thank you for the information.
Unfortunately, I am unable to register as the registration needs SMS code received on a Chinese phone number.
I hate when some service requests my phone number (or other irrelevant data) without any way to avoid it…
mp107 said:
Thank you for the information.
Unfortunately, I am unable to register as the registration needs SMS code received on a Chinese phone number.
I hate when some service requests my phone number (or other irrelevant data) without any way to avoid it…
Click to expand...
Click to collapse
2 files on that post (thanks [email protected] ).
Oreo flash CT_v1_xzs.zip , Pie flash CT_v2_xzp.zip .
BUT, that's for XZs and XZP, not for XC. If failed, you can flash oem.sin only (from .FTF firmware) to restore.
To enable VoLTE and Wifi Callling, we need two parts of modem configs.
1. core: *.mbn modem config of specific local carrier that locate in /system/etc/customization/modem/ .
2. guide: modem configs in /oem.
The 2nd part can be import easily from other sony models, but the KEY is 1st part config. If the specific local carrier config can't be found in /system/etc/customization/modem/ , we have to use QPST to put parameters manualy, or no way to enable VoLTE/VoWifi.
camdecoster said:
My carrier does offer VoLTE and WiFi Calling and those features do work on unlocked phones, so I'm pretty sure it's a Sony problem. In fact, I recently got those features working on an XZ1C. It could work on an XC too, but I'm moving on to the XZ1C. I hope someone gets it to work. Good luck with your carrier.
Click to expand...
Click to collapse
Yes, it's Sony's problem. To Sony, importing VoLET/VoWifi parameters of all support carriers is a piece of cake.
There's a post on a Chinese BBS about enable VoLTE：http://bbs.gfan.com/android-9543428-1-1.html
XG_Zepto said:
There's a post on a Chinese BBS about enable VoLTE：http://bbs.gfan.com/android-9543428-1-1.html
Click to expand...
Click to collapse
Has anyone here tried this for a US carrier? I tried to follow along with the translated version but my lack of fully understanding the process and the rough translations have made it very difficult.
Does anyone have experience with the X Compact on T-Mobile?
I was going to change from the iPhone SE (tired of Apple, but need a small phone), which has VoLTE and Wifi Calling out of the box. I have a Note FE which was made for Singapore and I was able to change the CSC to get VoLTE, but not Wifi Calling.
W/O VoLTE it's totally not worth it. Besides not being to use LTE while on a call, I read in the thread the OP referenced regarding the XZ1C, that getting Band 12 w/o VoLTE is also a problem.
And then there's the fingerprint sensor. If I install a European ROM to get it...
Will Rooting help any of the above?
Am I stuck with Apple? That's really depressing...
I understand that this may be considered duplicate. However due to the title of the previous thread clearly stating that the effort there is closed, I though I open this up. I would really love to get more 4g bands working as I have no LTE service in my area. Here is a post from the aforementioned thread.
-------
Maybe Possible Solution
Just found this thread after I unlock carrier locked my Hisense B16C2G phone that can't be unlocked for almost 3 years. This is just hypothesis, I suggest to try this with concern.
There are several file that determine bands capability in the devices. Most of it is in NV partition, but from the discussion I know that you guys have tried some popular ways to unlock it, but it failed. Like my phone at first i believe its hardware locked too, but i just discovered some Chinese article about unlocking oneplus device. Maybe you can try it too.
Here it is:
1. Connect to QPST and open EFS explorer
2. In policyman folder there are 3 file that most likely can be the cause of this network restiction
carrier_policy.xml
post.xml (in my phone there is none)
rat_mask (in my case this file that restrict my network even after I change NV values to support all bands)
3. Compare all three file with other phone's that most likely have same architechture (maybe MI8 or Pixel). For rat_mask, make sure it have same bits number(compare with Hex Editor)
4. replace that carrrier_policy.xml(and any file that contain this name) and rat_mask with modified files or use you can use other unrestricted phone's instead
These file originally in modem.img. Some phone replace them back with the original file when boot, you can modified init.radio.sh to prevent that.
We can modify carrier_policy.xml in modem.img and flash it to the phone but i cant find where rat_mask located
5. Reboot and hope if it solve your problem
I can't find any reference about how to generate unrestricted rat_mask and device_config so make sure you backup your original file before you make modification. Sorry I can confirm whether it will work or not because i don't own poco
NB: I solve my problem just with replacing carrier_config.xml and rat_mask. There is a file called device_config, be careful with this file because it control how the phone modem interact with qpst too, wrong modification can cause you cant connect to PC even in diag mode.
https://forum.xda-developers.com/poco-f1/help/poco-f1-lte-bands-unlock-t3835467/page22
-------
Does the above information help at all with this effort? I'm not quite savvy enough to pursue this on my own. I also found the below thread which describes a process which is apparently still working for many Qualcomm devices including Xiaomi. Has this method been attempted with the Poco F1?
http://in.c.mi.com/thread-527028-10-1.html
I sold my Poco and took over my GF's which was on 10.2.3. I had LTE at my place, confirmed with speed test and LTE app. After upgrading to 10.3.4 today I no longer have LTE. I've tried switching back and forth between APNs to no avail. Any ideas?
Any updates, did you got it working? I need to unlock B5 and 28.