Code:
###Disclaimer###
I am not responsible if your phone will be damaged, broken, boot looping.
YOU are choosing to make these modifications and accept the fact that something might go wrong.
Thanks @-=MoRpH=- for Moto Z Play guide
you will need to root your device.
I did this mod on LineageOS 14.1, on stock 6.0.1 ROM I will do later, after downgrade and root.
Edit: can't do on 6.0.1 as I upgraded to 7.0 and 7.1.2 and no way to go back to 6.0
FYI: If you update OTA to Android 7.x you won't be able to downgrade to 6.0, I did and I can't, If knew before I would not upgrade yet, one reason is, there is no Xposed for 7.x yet.
You can upgrade to 7.x manually w/o replacing the bootloader.
You can use guide from benzinerwin which works w/o root, you need to unlock bootloader:
https://forum.xda-developers.com/showpost.php?p=72015833&postcount=6
to enable Dual SIM I tried first in TWRP Terminal (I think maybe as su would work)
Code:
setprop persist.radio.multisim.config dsds
but did not work, don't know why, so I tried Multisim Toggle and it worked
https://forum.xda-developers.com/android/apps-games/app-multisim-toggle-t2830647
reboot and make sure you got the dual sim options in the Settings. (see picture below)
According to @-=MoRpH=- guide, https://forum.xda-developers.com/moto-z-play/how-to/guide-to-enable-dualsim-singlesim-t3570601
you have to delete both, griffin_2.img.gz and griffin_row.img.gz files and rename both DSDS files but I did delete just griffin_2.img.gz and renamed griffin_dsds_2.img.gz and it works, so don't know if it's necessary to delete and rename both files (I'll have to research and update later)
do the same for sheridan files, also see post from @ottmi https://forum.xda-developers.com/showpost.php?p=72045868&postcount=36
Edit:
I just flashed AOKP ROM and renamed both files and also works.
Make backup of both files, /fsg/griffin_2.img.gz and /fsg/griffin_row.img.gz and/or backup /fsg partition with TWRP
for both, delete and rename, I booted to recovery TWRP and did it in TWRP File Manager
delete the baseband your phone use normally, on EU devices griffin_2.img.gz
rename the dsds files from griffin_dsds_2.img.gz to griffin_2.img.gz
Reboot to bootloader (Vol- and Power button) and on your PC/Mac enter
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
now you should have both cards working.
This is work in progress, will be updated later.
Below the Dual SIM tray to see how to place the 2nd SIM
You can modify the original SIM tray to fit 2nd sim, see pic 3, you have to cut the extra material on both sides
Do it on your own risk, if you do something wrong you may brick your phone or damage SIM card tray or connectors.
Please don't PM me for a how-to step-by-step guide.
--reserved--
Sounds interesting...
Did you have to cut the SIM holder?
Also, was you second IMEI a zero or a valid number?
aoleg said:
Did you have to cut the SIM holder?
Also, was you second IMEI a zero or a valid number?
Click to expand...
Click to collapse
if you use microSD with 2nd SIM then no need to cut the SIM holder if you glue the SIM to microSD, otherwise you may need to cut the extra material
https://static.mydealz.de/live/comments/full_screen/HBsjw/13883078.jpg
2nd IMEI is 0
https://static.mydealz.de/live/comments/full_screen/FKQ3y/13887167.jpg
In case "setprop persist.radio.multisim.config dsds" as well as Multisim Toggle does not work, try this alternative:
Applies to Lineageos, with root enabled (e.g. supersu installed)
Option A: command line mode
activate developer mode
developer options: enable terminal app
run terminal app, grant root access when requested
Code:
su
mount -o rw,remount /system
cd /system
cp build.prop build.prop.orig
echo ro.hw.dualsim=true >>build.prop
mount -o ro,remount /system
reboot
Option B: root file explorer mode
you need a root-enabled file explorer, e.g. FX or Root Explorer, ES File Explorer etc.
navigate (in root mode) to /system
make '/system' read/writable (menu: 'mount read/write')
optional: make a copy and rename it to e.g. build.prop.orig
open build.prop in a text editor and move to the very end
append the following line:
Code:
ro.hw.dualsim=true
save the file
make /system read-only again, or just ...
reboot
Can someone please confirm what the basband version should read after the switch to dual sim? Mine used to be "M8996_1239.53.01.126R SRS" and is now "M8996_1239.53.01.126R SRD". Does that seem right?
I'm asking because the phone still doesn't detect the 2nd SIM card. Could be a mechanical problem though as I wasn't sure where to exactly place it on the tray..
I ordered a (supposedly) dual-SIM version of the SIM tray from Aliexpress. The seller was not quite sure about whether or not the tray can take two SIM cards, but I decided to get it anyways: if I need to cut anything, I'd rather cut a spare.
ottmi said:
Can someone please confirm what the basband version should read after the switch to dual sim? Mine used to be "M8996_1239.53.01.126R SRS" and is now "M8996_1239.53.01.126R SRD". Does that seem right?
I'm asking because the phone still doesn't detect the 2nd SIM card. Could be a mechanical problem though as I wasn't sure where to exactly place it on the tray..
Click to expand...
Click to collapse
with AOKP nightly_2017_04_23_0933, I have "M8996_1223.32.01.109R"
Sometimes, when the 2nd sim is placed too much to the top then I don't get contact but I just glued it with double side tape to a microSD
aoleg said:
I ordered a (supposedly) dual-SIM version of the SIM tray from Aliexpress. The seller was not quite sure about whether or not the tray can take two SIM cards, but I decided to get it anyways: if I need to cut anything, I'd rather cut a spare.
Click to expand...
Click to collapse
I have two original moto z single sim trays so I just cut the extra material on the spare tray.
You don't need to cut the material if you going to use microSD+2nd SIM hybrid mod but then you have to "cut" the 2nd SIM
here the 2nd sim orientation
xequtor said:
with AOKP nightly_2017_04_23_0933, I have "M8996_1223.32.01.109R"
here the 2nd sim orientation
http://i.imgur.com/0jyLvhp.jpg
Sometimes, when the 2nd sim is placed too much to the top then I don't get contact but I just glued it with double side tape to a microSD
I have two original moto z single sim trays so I just cut the extra material on the spare tray.
Click to expand...
Click to collapse
Doh. I didn't even consider that the orientation of SIM2 would be different from SIM1. I've just turned it around and now it works. Thanks a lot!
ottmi said:
Doh. I didn't even consider that the orientation of SIM2 would be different from SIM1. I've just turned it around and now it works. Thanks a lot!
Click to expand...
Click to collapse
glad it works for you.
which ROM do you use?
xequtor said:
glad it works for you.
which ROM do you use?
Click to expand...
Click to collapse
Stock Nougat with March 2017 patches, i.e. Build NPLS25.86-31-1
ottmi said:
Stock Nougat with March 2017 patches, i.e. Build NPLS25.86-31-1
Click to expand...
Click to collapse
Basically just run through the steps in Post 1, stick the SIM into the tray, change the modem and off you go?
That sounds way to simple, Imho
Any chance, you could post a picture of your sim tray?
Thanks!
I'm a total root/custom rom noob, but shouldn't DualSim work with a DualSim tray and an official version of the Moto Z Android from a country where DualSim works (e.g. France)?
sameasy said:
I'm a total root/custom rom noob, but shouldn't DualSim work with a DualSim tray and an official version of the Moto Z Android from a country where DualSim works (e.g. France)?
Click to expand...
Click to collapse
in theorie yes, but I did not see any FR ROM so I did not try.
linuxartist said:
Basically just run through the steps in Post 1, stick the SIM into the tray, change the modem and off you go?
That sounds way to simple, Imho
Any chance, you could post a picture of your sim tray?
Thanks!
Click to expand...
Click to collapse
Exactly, I didn't root the OS but only unlocked the bootloader and set the multisim property in TWRP. I will post a pic of my SIM tray later tonight, but it's really ugly as I did cut both, the SIM and the tray.
sameasy said:
I'm a total root/custom rom noob, but shouldn't DualSim work with a DualSim tray and an official version of the Moto Z Android from a country where DualSim works (e.g. France)?
Click to expand...
Click to collapse
There is only a generic European firmware. The differentiation happens in the bootloader where the ro.boot.dualsim flag is set accordingly. Init then sets persist.radio.multisim.config and this is the property the phone app (and others) later evaluate. That's why dual-sim can be enabled by setting the persist.radio.multisim.config property in TWRP. Another way would be to modify the boot.img and the init script accordingly.
ottmi said:
Exactly, I didn't root the OS but only unlocked the bootloader and set the multisim property in TWRP. I will post a pic of my SIM tray later tonight, but it's really ugly as I did cut both, the SIM and the tray.
There is only a generic European firmware. The differentiation happens in the bootloader where the ro.boot.dualsim flag is set accordingly. Init then sets persist.radio.multisim.config and this is the property the phone app (and others) later evaluate. That's why dual-sim can be enabled by setting the persist.radio.multisim.config property in TWRP. Another way would be to modify the boot.img and the init script accordingly.
Click to expand...
Click to collapse
you unlocked in Developer Settings or did you send ID to motorola and got unlock ID?
If I just new it before
With this mod: is it possible to use both sim cards in the parallel? Let's say, sim1 for data and sim2 for phone calls?
ottmi said:
Exactly, I didn't root the OS but only unlocked the bootloader and set the multisim property in TWRP. I will post a pic of my SIM tray later tonight, but it's really ugly as I did cut both, the SIM and the tray.
There is only a generic European firmware. The differentiation happens in the bootloader where the ro.boot.dualsim flag is set accordingly. Init then sets persist.radio.multisim.config and this is the property the phone app (and others) later evaluate. That's why dual-sim can be enabled by setting the persist.radio.multisim.config property in TWRP. Another way would be to modify the boot.img and the init script accordingly.
Click to expand...
Click to collapse
Could it be possible for Lenovo to enable DualSim via an Android Update (so users don't have to root)? DualSim out of the box (with the appropriate tray) would be a great selling point for the Moto Z.
topcaser said:
With this mod: is it possible to use both sim cards in the parallel? Let's say, sim1 for data and sim2 for phone calls?
Click to expand...
Click to collapse
yes, that's what I'm doing.
Related
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Morecrabs said:
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Click to expand...
Click to collapse
1. No
2. Yes
You need to be on stock ics firmware for the NV edit to succeed and stick.
Use Android 4.0.4 Blur_Version.77.8.14.XT897.Sprint.en.US - http://sbf.droid-developers.org/phone.php?device=3
If you're downgrading from jellybean, you have to remove the line with flash gpt_main0.bin from the xml file, otherwise the flashing via rsdlite will fail.
Code:
[STRIKE]<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />[/STRIKE]
The firmware thread is here: http://forum.xda-developers.com/showthread.php?t=2095536
Then you can follow this (RadioComm):
http://forum.xda-developers.com/showthread.php?t=2166542
or this (CDMA WS) guide:
http://forum.xda-developers.com/showthread.php?t=2386871
After it's done, you should flash the stock Android 4.1.2 via rsdlite, then install CM10.2 (or any other custom ROM) again.
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Morecrabs said:
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Click to expand...
Click to collapse
That development ID is simply for identifying your device under debugging circumstances like ADB, every device has them. Also, flashing another ROM changes this value.
Sent from Google Nexus 4 @ CM11
ok so that was a dumb decision to come to, but its not something id ever seen on any of my other android devices, Droid 1,2,4 samsung captivate glide, so i figured it was related to the developer Models
Do I need to run my copy of radio Comm on a 32 bit machine to accomplish this hacking?
my 64 bit machines seem to have driver related issues with the software
was wondering if anyone could help me setup the drivers, I keep getting errors with Radio comm and cdma workshop, and it all boils down to driver issues, with cdma workshop i cant get the QC port setup because IM missing a driver, and with radio comm, I cant get it to communicate properly with the phone once i boot into fastboot any help suggestions? ive installed the moto drivers and setup on a PC with a 32 bit version of win7 starter to allow radio comm to setup properly
In radio comm it will ID the phone as xt897 and i can get software version if its booted into OS, but it will do nothing else
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http://bork.cs.fau.de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
Code:
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https://github.com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
EDIT2: This is now included as "unlock-us-gsm" in CM12.0 and up on XT897, XT907 and XT926. To use it run "unlock-us-gsm" in a root shell:
Code:
[email protected]_c:/ # unlock-us-gsm
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Reading value of NV-item 8322...
GSM locked in the US: 1
Setting value of NV-item 8322 to 0...
Reading value of NV-item 8322...
GSM locked in the US: 0
Setting logging_mode to usb...
Regards,
Michael
stargo said:
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer
Click to expand...
Click to collapse
Excellent! I picked a good day to try to figure out how to do this, I was making notes of all the various steps (install ics on phone, use radiocomm on pc, install jb on phone, then cm on phone) when I got to this post and realized I won't need to do any of that, thanks much!
Terminal Emulator Question
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http //bork cs fau de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
[CODE
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
[/CODE]
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https //github com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
Regards,
Michael
Click to expand...
Click to collapse
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
DroidRazrMv said:
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
Click to expand...
Click to collapse
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
arrrghhh said:
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
Click to expand...
Click to collapse
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
DroidRazrMv said:
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
Click to expand...
Click to collapse
Still confused as to where you're having issues - we are both talking about the same post. If you look, kabaldan's post redirects to the one I am referencing....
So once these steps are used to unlock the phone, which carriers can be used and how does flashing of carrier info occur?
Just want to say thanks again Michael. I just got my new Photon Q back from having sim card slot installed, ran your program and it worked perfectly on 21OCT2014 CM nightly.
I did also change a couple settings in the phone menu too, cuz I put an AT&T sim card in it, but sprint kept calling me to activate. Seems to be working well now, but not sure I understand everything, does this seem right - in regular CM11 settings menu under Mobile network settings, I set Preferred network type to "GSM/WCDMA Auto".
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
Click to expand...
Click to collapse
CAT has not yet managed to put official stock images or the kernel source code available - even for their oldest phones (even though they are required to)... so here's at least a beginning.
Every firmware archive contains the four partitions UBOOT, BOOTIMG, RECOVERY and ANDROID (/system). These are flashable using spFlashTool, a howto is here: http://forum.xda-developers.com/android/help/howto-firmware-flashing-cat-b15q-t2989627.
Please note that these firmware files were dumped from an EMEA B15Q, dual-sim - there are reports of other models being available under the B15Q model name. In doubt, always make a full backup using spFlashTool's readback mode before flashing one of these. (You should be doing these anyway before every firmware upgrade, CAT doesn't test stuff like compatibility with root!)
Credits for the scatter file go to bigal1337. Credits for spFlashTool and the driver package go to Russian website mtk2000.ucoz.ru.
1.019: https://mega.co.nz/#!UEp0hS7b!6aiqETvAu1Q9voNZtMLWoztbF7FGX0j9Pnj4rBhwoD4
1.022: https://mega.co.nz/#!YEAwmbxI!rVonLybVo6PL2bhNloGStR0EacKwE3-3hILzY9ri0NY
Scatter file: https://mega.co.nz/#!UEp0hS7b!6aiqETvAu1Q9voNZtMLWoztbF7FGX0j9Pnj4rBhwoD4
Tested tools:
MTK Driver package: http://mtk2000.ucoz.ru/down12/MTKUsbAll_0.9.2.rar
spFlashTool: http://mtk2000.ucoz.ru/down12/SP_Flash_Tool_exe_windows_v5.1420.00.rar
Do note that the drivers appear to be modified Google drivers and thus have no digital signature; you will need a 32-bit system to use them.
Flash mode needed for spFlashTool is achieved by removing the battery, starting the flash/readback in spFlashTool and then plugging in the USB cable. You may put in the battery afterwards.
The recovery, fastboot and factory test methods are entered by shutting down the phone and then:
recovery mode: press power + volup for 2 seconds, then release power, release volup as soon as recovery has booted
fastboot mode: press power + center for 2 seconds, then release power, release volup as soon as recovery has booted
test mode: press power + voldn for 2 seconds, then release power, release volup as soon as recovery has booted
In case that a B15Q or general CAT board is opened (for the B15, B15Q and the flagship S50), I request that this thread is moved into its rightful place. And in case anyone wants to help me with a CyanogenMod port, please PM me.
CWM Recovery
Using mtkdroidtools, I have built a CWM Recovery image to be flashed with spflashtool, all based on 1.022 firmware. There are two variants:
using stock Mediatek USB IDs: https://mega.co.nz/#!FRxxiRSC!EN5gORcYPtFONlH3V8-Yco3_w9RGhE8jevicedlT2kI
using Samsung USB IDs: https://mega.co.nz/#!8MowBZCJ!fhs-mXpGZR36g9JJh3IONIlOKBHIktFBDIrpynlK84M
The difference between them is that recovery #1 uses the same Mediatek USB id's as the stock image (and thus requires the Mediatek drivers in Windows, which sucks because these are not signed), and recovery #2 uses the USB IDs from a Samsung tablet - so you need the Samsung ADB driver instead, which is digitally signed and far more stable than the Mediatek.
Samsung USB ID fix
See above for the reason; the boot.img with Samsung USB IDs is at:
1.022: https://mega.co.nz/#!gcREQJKD!FCrxl9-PWSWM0_2Nh9D1KeA-zFV4nS9dmd6zjVnqPLc
Hybrid SD Card
And the CWM Recovery + boot.img for those who want to try out the "hybrid SD card" from http://forum.xda-developers.com/android/help/howto-external-sd-card-internal-storage-t2989650, the two images of 1.022 are here:
boot.img: https://mega.co.nz/#!MMYx1BYY!Rlnrxl1MURMgnx2luvPdYKJjMmNMbYVIGyFlGeRVcMY
recovery.img: https://mega.co.nz/#!wZQ1FIrS!iXAYfF3pgSySYsQ3f8ygGkDWE3Ulebx3JFgzRKXWNjs
I used this, it's great! Now I have 16gb of "internal phone memory" and 14 of "external" sd card. Did not see any performance issues with my SanDisk Extreme III. Do not need root anymore, I wanted it only for link2sd. Thanks harddisk_wp!!!
walckenaerius said:
I used this, it's great! Now I have 16gb of "internal phone memory" and 14 of "external" sd card. Did not see any performance issues with my SanDisk Extreme III. Do not need root anymore, I wanted it only for link2sd. Thanks harddisk_wp!!!
Click to expand...
Click to collapse
Great to hear someone was crazy enough to replicate my hack But I strongly advise you to keep off OTA updates with the hack enabled.
harddisk_wp said:
Great to hear someone was crazy enough to replicate my hack But I strongly advise you to keep off OTA updates with the hack enabled.
Click to expand...
Click to collapse
i have got a message that my sd card is damaged... and there is no way to remove that notification? any ideas?
thanks!
mccloud90 said:
i have got a message that my sd card is damaged... and there is no way to remove that notification? any ideas?
thanks!
Click to expand...
Click to collapse
With or without the SD hack? Try putting the SD card into a Windows machine, chkdsk the fat32 partition. Then plug it into a linux machine and run e2fsck on the data partition.
harddisk_wp said:
With or without the SD hack? Try putting the SD card into a Windows machine, chkdsk the fat32 partition. Then plug it into a linux machine and run e2fsck on the data partition.
Click to expand...
Click to collapse
I tried the sd hack. There was a problem with my sd card partitions... but i reformated it with partition magic and now it works like a charm. No lag or anything.
Better than i was thinking
Greatings!
after one week
OKAY,
after one week of usage my phone became laggy and unstable.
Maybe this is because of my sd card but.... its 10class, i dont know
So i reflashed with the original partitions and now its fast and stable
Custom Rom
Will there be any possibility to create a Lollipop rom for this device?
proximity sensor problem
Do someone have the problem with the proximity seonsor that i have? There is a screen turning on immediately after turning of when the phone is placed next to my head when i am calling. This leads to a lot of changes in settings and everything that my face is changed durring the phone call.
I tried a lot of apps from play store that "fix" the problem but... they work not on 100% proper.
The sensor is working at 100% i have checked it already.
Please give me suggestions because its very annoing!!
Hi!
mccloud90 said:
Do someone have the problem with the proximity seonsor that i have? There is a screen turning on immediately after turning of when the phone is placed next to my head when i am calling. This leads to a lot of changes in settings and everything that my face is changed durring the phone call.
I tried a lot of apps from play store that "fix" the problem but... they work not on 100% proper.
The sensor is working at 100% i have checked it already.
Please give me suggestions because its very annoing!!
Click to expand...
Click to collapse
I had the same problem. CAT support told me to reset the phone to factory. I tried a lot of other things but only the factory reset helped me. My sensor was also working correctly, I also tried several Apps to chack this.
Give it a try. I know it's a lot of work, but it was (in my case) worth it. I changed the time an date settings with my face which lead to missed alarms and oversleeping
Greets,
Doggy
Current ersion?
Doggy77 said:
Hi!
I had the same problem. CAT support told me to reset the phone to factory. I tried a lot of other things but only the factory reset helped me. My sensor was also working correctly, I also tried several Apps to chack this.
Give it a try. I know it's a lot of work, but it was (in my case) worth it. I changed the time an date settings with my face which lead to missed alarms and oversleeping
Greets,
Doggy
Click to expand...
Click to collapse
You have hard reseted to what rom version? 1.19 or 1.22
I will give it a try
I need the phone rooted and i am not sure if the cwm recovery can be flashed over 1.19 as it was my original rom and i flashed it to 1.22 from files here on the forum
any news about any cyanogenmod rom?
Just to tell you that the new official update is awsome!!! Upgrade as fast as possible Greatings!
CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/showthread.php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/showthread.php?t=2263455
Best regards,
proximity sensor problem
I also have the proximity sensor problem.
I have tried the factory reset but the problem is the same.
It has 1.026 rom.
Can anybody post the 1.026 software? Thanks!
yo2lzp said:
I also have the proximity sensor problem.
I have tried the factory reset but the problem is the same.
It has 1.026 rom.
Click to expand...
Click to collapse
Hallo my friend,
i had the same problem and that was so anoyng... so i went back to the shop where i bought my phone and told them about the problem.
After one week they called me and my phone was with changed whole display with everything inside and now i have working proximity sensor
So... i suggest you to go back to the store and tell them about your problem !
All the best!!
After a lot of attempts, I found a way to force upgrade to Android 6.0 MM on AT&T LG V10 H900.
Before you start these steps:
•Make sure you have ADB installed on your computer and running. If you don’t, follow this guide to set it up. Or if you don't want the whole Android Studio, try this guide to setup Minimal ADB and Fastboot
•Make sure your phone is stock non rooted. If not here is the link to the stock tot file. And here is the link to the instructions for using tot file.
Instructions:
1. Download the Android 6.0 MM OTA zip file.
2. Unzip the file, and you get a 20N.up file
3. Copy 20N.up file to /Internal storage/SoftwareUpdate/ not external SD card (if folder doesn't exist, just create it)
4. Activate USB Debugging on phone and plug into computer
5. Open CMD window in C:\Users\YOURUSERNAME\AppData\Local\Android\sdk\platform-tools by holding shift and right clicking and selecting open command window here. (Path may be in different location based on your installation of SDK)
6. Type the following command in CMD window:
Code:
adb devices
Check and see if your device appears listed. If not, check on phone and select to trust computer if prompted. Run command again once you added computer to trusted list.
7. Run this command:
Code:
adb shell
This should appear: [email protected]:/ $
8. Run this command in ADB shell:
Code:
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
Phone Screen should show OFTA Easy Upgrade screen for a few seconds and then reboot to software update.
Note:
This does not give you root, it simply forces the update to marshmallow.
Edit: This method has now worked for everyone who tested it. If it doesn't work for you, just ask for help and either myself or one of the other fine members of the community can try and see what we can do to help.
Special Thanks To:
@kangi26
@syndicator
@LGMONO
@@autostrada048
@betasp
@shepcontracting
RESERVED
Reserved
Tested works
Thanks for this. After flashing back to stock my phone wouldn't show that I had an update no matter what I tried. This method worked perfectly.
For those who do not want to install the whole android studio to get ADB you can use this to get it.
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
That is what I used.
silentmage said:
Thanks for this. After flashing back to stock my phone wouldn't show that I had an update no matter what I tried. This method worked perfectly.
For those who do not want to install the whole android studio to get ADB you can use this to get it.
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
That is what I used.
Click to expand...
Click to collapse
Thanks @silentmage for Minimal ADB and Fastboot link! Added link to OP.
I can't decide if give up root and update. I use root mainly for adblock
So I don't currently have a SIM in my V10, it's in my Nexus 6P, but when I check for the MM update I've been told there is no update. This has happened since the MM update was released. My question is can I use this method to update to MM even if there is no SIM in the phone?
I wouldn't think that having a SIM would be require to update but maybe it uses the SIM to auth to the AT&T servers?
manny18pr said:
I can't decide if give up root and update. I use root mainly for adblock
Click to expand...
Click to collapse
You can technically adblock without root, if that's the only thing holding you back from an update.
http://forum.xda-developers.com/showthread.php?t=2726443
This worked perfectly! Thanks, TheBobMiller. Glad we figured out what I was doing wrong.
rcook55 said:
So I don't currently have a SIM in my V10, it's in my Nexus 6P, but when I check for the MM update I've been told there is no update. This has happened since the MM update was released. My question is can I use this method to update to MM even if there is no SIM in the phone?
I wouldn't think that having a SIM would be require to update but maybe it uses the SIM to auth to the AT&T servers?
Click to expand...
Click to collapse
I'm honestly not sure if this method would work for you or not. I am unaware if any of the testers or anyone who has used this method has done so without a sim card. In theory it should work since it's an AT&T version of the phone just missing the sim card. If you try, let me know the outcome please.
Worked great. Thanks!
takkuso said:
You can technically adblock without root, if that's the only thing holding you back from an update.
http://forum.xda-developers.com/showthread.php?t=2726443
Click to expand...
Click to collapse
Have you tried this?
manny18pr said:
Have you tried this?
Click to expand...
Click to collapse
Yep! Did it today. Working like a dream. Adblock was the main reason for rooting, but I really wanted marshmallow.
Best of both worlds!
takkuso said:
Yep! Did it today. Working like a dream. Adblock was the main reason for rooting, but I really wanted marshmallow.
Best of both worlds!
Click to expand...
Click to collapse
Can you post a screenshot of the apn settings you used?
manny18pr said:
Can you post a screenshot of the apn settings you used?
Click to expand...
Click to collapse
http://imgur.com/a/GO5KX
takkuso said:
http://imgur.com/a/GO5KX
Click to expand...
Click to collapse
When I set the apn settinga and hit save it said that the apn name was invalid
manny18pr said:
When I set the apn settinga and hit save it said that the apn name was invalid
Click to expand...
Click to collapse
Are you naming it the same as the original? I'm not sure, but I'd bet they can't have the same name. Other than that, I'm not sure what the issue would be. Maybe length of name, or invalid characters?
takkuso said:
Are you naming it the same as the original? I'm not sure, but I'd bet they can't have the same name. Other than that, I'm not sure what the issue would be. Maybe length of name, or invalid characters?
Click to expand...
Click to collapse
I'm trying again. I'll let you know
Edit: I managed to change the apn.
I now don't know what to manage in the adblock plus.
Deleted
TheBobMiller said:
I'm honestly not sure if this method would work for you or not. I am unaware if any of the testers or anyone who has used this method has done so without a sim card. In theory it should work since it's an AT&T version of the phone just missing the sim card. If you try, let me know the outcome please.
Click to expand...
Click to collapse
I hate to say this but it was all of 5 seconds to put the SIM back into the phone and then perform the update in the thread which worked fine. Sorry I just wanted to update the phone.
I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Wow! Well done
Root question
Is there a way to do this without root by using say newflasher and just changing the SIN file?
Firmware File Location
htcmage said:
I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Click to expand...
Click to collapse
Hi there,
How did you find the firmware file? Did you extract the SIN from the localized firmware (for example custom U.S. or via another method? Also does this work for Xperia 1 or only Xperia 1 II
veerasammy778 said:
Root question
Is there a way to do this without root by using say newflasher and just changing the SIN file?
Click to expand...
Click to collapse
If you have Xperia 1. Just to enable VoLTE, either flash SEA firmware or Just flash these from the Japanese version.
Put these in a New folder.
oem.map
oem_other.map
oem_other_X-FLASH-CUST-A2CD.sin
oem_X-FLASH-CUST-A2CD.sin
newflasher.exe
I'm using Android 9 and Flashed OEMs from Japanese latest .191 firmware which you can get by downloading using XperiFIrm and Newflasher from @munjeni .
@jeoleo7 I have Xperia 1 SO03L docomo version single sim phone. Unlocked carrier for use in India. Currently on android 11 version.
Can I flash below files and enable volte ?. Hope this will not affect sim unlock status to locked again. Need your help !
Quote"
Put these in a New folder.
oem.map
oem_other.map
oem_other_X-FLASH-CUST-A2CD.sin
oem_X-FLASH-CUST-A2CD.sin
newflasher.exe"
Will you be able to share the above file because I dont know how to extract it from android 11
@ralf_waldo
I have tried on my J9110 dual.
These files I have listed are just the OEM only and are region specific.
I easily achieved HD voice calls on LTE in my phone when I was using firmware from Ukraine or any other region.
I also tried Single sim variant flashing on my dual sim version.
I tried J8110 EE UK (found the clock and few changes different from my original).
Hence, just flashing these files won't lock your phone since its already unlocked.
You may backup your important things before doing anything.
Customized_JP_OEM_332.zip
drive.google.com
i need enable Volte on Sony experia 1 model : SO-03L please help me.
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!