I'm having some trouble with the modem (and LTE compatability) on my XZ1 Compact, and I was wondering if anyone has experience with the different kinds of boot modes and/or Qualcomm transfers.
There's some Qualcomm software (QPST) that supposed to let you write to the modem partition. There are some instructions here
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
and here
Getting VoLTE and VoWiFi on unlisted carriers by flashing mbn file
I live in Canada and I have a BC72 (Asian version). I am struggling to get VoLTE and VoWiFi working. I know that mbn file is the key to getting IMS support and sony seems to block some carrier mbn files (only mbn in sales areas are available). So...
forum.xda-developers.com
That I was trying to follow along with, but doing the setopt doesn't seem to change the mode of my phone/usb connections, and so I can't update the drivers or connect the QPST software to read or write the filres.
There's also supposedly an EDL mode that Qualcomm phones can get into, which should also connect to the software
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
but those instructions don't work either - adb reboot edl just reboots the phone back into the rom, and fastboot oem edl tells me that's not a supported function.
Does anyone have experience getting either of these to work and/or updating the modem software?
I can't follow these steps:
XZ1 Compact - MetroPCS VoLTE + Latest Pie + Fingerprint + Wi-Fi Calling Step by Step Guide
Overview: This guide provides step-by-step instructions for flashing any existing Sony stock rom Android 8 or 9 to the latest Sony stock ROM Android 9 Build v47.2.A.11.228 for use on the MetroPCS network. The finalized flash is a hybrid of Sony...
forum.xda-developers.com
since I don't seem to have this overlay functionality baked into my rom.
I recognize that part of this might be something to do with my ROM - which I believe is AOSP based instead of stock based - but even in the worst cast scenario it seems like I should be able to override whichever default mbn file the phone is deciding to use (perhaps set from a partition flash?) with whichever one I'd like it to use, instead. I just can't figure out how to determine what my phone is currently picking, or how to correct it.
Any tips or suggestions would be greatly appreciated. Thanks!
I'm having some trouble with the modem (and LTE compatability) on my XZ1 Compact, and was trying to experiment with adjusting the files manually.
Does anyone have experience with the different kinds of boot modes and/or Qualcomm transfer?
I've tried on both an XZ1c and a Z5c, both of which result in similar behaviors.
Extra context:
There's some Qualcomm software (QPST) that supposed to let you write to the modem partition. There are some instructions here
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
and here
Getting VoLTE and VoWiFi on unlisted carriers by flashing mbn file
I live in Canada and I have a BC72 (Asian version). I am struggling to get VoLTE and VoWiFi working. I know that mbn file is the key to getting IMS support and sony seems to block some carrier mbn files (only mbn in sales areas are available). So...
forum.xda-developers.com
That I was trying to follow along with, but doing the setopt doesn't seem to change the mode of my phone/usb connections, and so I can't update the drivers or connect the QPST software to read or write the filres.
There's also supposedly an EDL mode that Qualcomm phones can get into, which should also connect to the software
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
but those instructions don't work either - adb reboot edl just reboots the phone back into the rom, and fastboot oem edl tells me that's not a supported function.
Does anyone have experience getting either of these to work and/or updating the modem software?
I figured I'd try asking in the cross-device forum since most of the Sony phones use a Qualcomm modem, so it seems like it should be applicable to more than just one model.
Any tips or suggestions would be greatly appreciated. If I get it working, I'll happily follow up with a guide for others.
Unfortunately, SONY seems to have banned edl from the factory. Unless your phone is an engineering sample.
laojiefang said:
Unfortunately, SONY seems to have banned edl from the factory. Unless your phone is an engineering sample.
Click to expand...
Click to collapse
NO, My xperia xz2 detect as edl mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cuynu said:
NO, My xperia xz2 detect as edl mode
View attachment 5774603
Click to expand...
Click to collapse
Can you use the public version of elf files to read your phone partition? Like this?
laojiefang said:
Can you use the public version of elf files to read your phone partition? Like this?View attachment 5774611
Click to expand...
Click to collapse
No, qfil say timeout error
cuynu said:
No, qfil say timeout error
Click to expand...
Click to collapse
First of all, according to your screenshot, you don't seem to have the edl driver installed. Second, your xz2 is a retail phone, which cannot use edl mode for all operations.
Sorry for the delay; it's been a weird week.
laojiefang said:
Unfortunately, SONY seems to have banned edl from the factory. Unless your phone is an engineering sample.
Click to expand...
Click to collapse
Interesting, thanks for this info! It at least explains why I was unable to get into it, despite the Qualcomm modem.
Do you have any experience with the "setprop persist.usb.eng 1" setting, and what it's doing?
As far as I can tell that's sometimes doing triggering a similar mode for folks, with some ROMs, but I don't understand it enough to grok why it's not doing the same for my device, and if it's even possible to get it working or if I need to switch to a completely different ROM.
It seems like the modem configuration should be independent of the ROM, but I have a sneaky suspicion that backing up, switching/re-configuring, then restoring my current one won't end up with it working any better.
laojiefang said:
a retail phone, which cannot use edl mode for all operations.
Click to expand...
Click to collapse
Do you know anything about which operations are or aren't possible? The Xperia 1 III post suggests that some of them are possible - at least to download and upload files, which is hopefully enough here to tweak my settings so I'd have better LTE/VoIP compatibility.
Thanks again for your insight!
tonsofquestions said:
Sorry for the delay; it's been a weird week.
Interesting, thanks for this info! It at least explains why I was unable to get into it, despite the Qualcomm modem.
Do you have any experience with the "setprop persist.usb.eng 1" setting, and what it's doing?
As far as I can tell that's sometimes doing triggering a similar mode for folks, with some ROMs, but I don't understand it enough to grok why it's not doing the same for my device, and if it's even possible to get it working or if I need to switch to a completely different ROM.
It seems like the modem configuration should be independent of the ROM, but I have a sneaky suspicion that backing up, switching/re-configuring, then restoring my current one won't end up with it working any better.
Do you know anything about which operations are or aren't possible? The Xperia 1 III post suggests that some of them are possible - at least to download and upload files, which is hopefully enough here to tweak my settings so I'd have better LTE/VoIP compatibility.
Thanks again for your insight!
Click to expand...
Click to collapse
Do you mean that you can use certain ROMs to trigger edl mode? (I'm sorry that I'm Chinese, and I can't understand your words with machine translation.)
I don't know if it's the same as EDL mode, but it seems like certain ROMs (likely stock at least) can get into some kind of Qualcomm mode by following the instructions outlined here:
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
Otherwise, the instructions probably wouldn't exist.
I just can't get it to work on _my_ ROM.
Happy to try and rephrase if you can point out what wasn't clear in the translation!
tonsofquestions said:
I don't know if it's the same as EDL mode, but it seems like certain ROMs (likely stock at least) can get into some kind of Qualcomm mode by following the instructions outlined here:
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
Otherwise, the instructions probably wouldn't exist.
I just can't get it to work on _my_ ROM.
Happy to try and rephrase if you can point out what wasn't clear in the translation!
Click to expand...
Click to collapse
Oh I see, this mode is not edl mode, it is Qualcomm diag port, it is used to modify the xml configuration file of the phone to remove some software level band restrictions. For example, in mainland China where I live, LG mobile phones cannot use 5G. By this method, you can use 5G in mainland China by brushing the xml file of the Chinese version of LG mobile phones
OK, that makes sense.
In my research to be able to do this, I saw mentions of both the diag and edl modes, but nothing highlighted the distinctions, so I thought they were different names for the same thing.
So if edl mode is disabled by Sony for these devices, perhaps the correct question to ask is "how can I enable this diag mode/port", if this command is not available? Is it part of the ROM, or available in some other way?
For that matter, if it's a software level-band restriction, is that software itself in the ROM or the modem files? Do changes persist across ROMs?
For example, if you fix the 5G settings in one setup, then switch to a different OS build/version, will you still be able to use 5G, or would you have to reconfigure again?
tonsofquestions said:
OK, that makes sense.
In my research to be able to do this, I saw mentions of both the diag and edl modes, but nothing highlighted the distinctions, so I thought they were different names for the same thing.
So if edl mode is disabled by Sony for these devices, perhaps the correct question to ask is "how can I enable this diag mode/port", if this command is not available? Is it part of the ROM, or available in some other way?
For that matter, if it's a software level-band restriction, is that software itself in the ROM or the modem files? Do changes persist across ROMs?
For example, if you fix the 5G settings in one setup, then switch to a different OS build/version, will you still be able to use 5G, or would you have to reconfigure again?
Click to expand...
Click to collapse
edl mode is disabled at the factory. diag port is not disabled. I have never seen a phone with diag mode disabled.
LG mobile phones need to be re-cracked after changing the SIM card in mainland China, because the carrier_policy.xml file will change with the change of the SIM card, but after the cracking is completed when the SIM card is inserted, the third-party ROM such as MIUI does not need to be re-cracked. However, after replacing the SIM card, it cannot be cracked through the diag port again, unless the original firmware is flashed back. Sony I'm not sure if that's the case.
If you want to enable diag on a phone that is disabled by default, you must root the phone and then open it using adb shell command in the Android debug bridge (like the link you sent me).
tonsofquestions said:
Sorry for the delay; it's been a weird week.
Interesting, thanks for this info! It at least explains why I was unable to get into it, despite the Qualcomm modem.
Do you have any experience with the "setprop persist.usb.eng 1" setting, and what it's doing?
As far as I can tell that's sometimes doing triggering a similar mode for folks, with some ROMs, but I don't understand it enough to grok why it's not doing the same for my device, and if it's even possible to get it working or if I need to switch to a completely different ROM.
It seems like the modem configuration should be independent of the ROM, but I have a sneaky suspicion that backing up, switching/re-configuring, then restoring my current one won't end up with it working any better.
Do you know anything about which operations are or aren't possible? The Xperia 1 III post suggests that some of them are possible - at least to download and upload files, which is hopefully enough here to tweak my settings so I'd have better LTE/VoIP compatibility.
Thanks again for your insight!
Click to expand...
Click to collapse
here is my post with info about persist.usb.eng:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
and this one in particular:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
concerning EDL mode (as discussed a different thing to diag mode) - you can boot into EDL with retail xz1c using a kernel patch which re-adds support for 'adb reboot edl', but it is not useful, because it needs sony signed EDL image that is loaded via usb (I happen to have it, but all interesting commands are protected by sony authentication, so it is not useful anyway)
laojiefang said:
LG mobile phones need to be re-cracked after changing the SIM card in mainland China, because the carrier_policy.xml file will change with the change of the SIM card, but after the cracking is completed when the SIM card is inserted, the third-party ROM such as MIUI does not need to be re-cracked. However, after replacing the SIM card, it cannot be cracked through the diag port again, unless the original firmware is flashed back. Sony I'm not sure if that's the case.
If you want to enable diag on a phone that is disabled by default, you must root the phone and then open it using adb shell command in the Android debug bridge (like the link you sent me).
Click to expand...
Click to collapse
Yes, the phone is rooted (thus the custom ROM, though I guess you could unlock and not root, but that just seems silly).
Thanks for the context on changing the SIM card, perhaps that's my underlying issue, and I'll just have to bite the bullet and go back to the original firmware.
j4nn said:
here is my post with info about persist.usb.eng:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
and this one in particular:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
concerning EDL mode (as discussed a different thing to diag mode) - you can boot into EDL with retail xz1c using a kernel patch which re-adds support for 'adb reboot edl', but it is not useful, because it needs sony signed EDL image that is loaded via usb (I happen to have it, but all interesting commands are protected by sony authentication, so it is not useful anyway)
Click to expand...
Click to collapse
Ah, this is super interesting info, thank you j4nn! I am on Oreo, so maybe it's just as easy as setting a few of the extra props. I'll read through the read more later this evening.
Very neat about being able to custom-patch in the EDL reboot, and it makes sense that it wouldn't support random unsigned flashes, even if the phone is bootloader unlocked.
Do you have any additional experience with unlocking additional bands from the diag mode? I'm not sure what you were experimenting with at the time - if it was for your root exploit or something else.
no, I do not have any experience unlocking additional bands, I do not know any other stuff about that diag apart from what has been posted there
but I find following thread very interesting and I guess it might be related to what you want too:
XZ1 Compact - MetroPCS VoLTE + Latest Pie + Fingerprint + Wi-Fi Calling Step by Step Guide
Overview: This guide provides step-by-step instructions for flashing any existing Sony stock rom Android 8 or 9 to the latest Sony stock ROM Android 9 Build v47.2.A.11.228 for use on the MetroPCS network. The finalized flash is a hybrid of Sony...
forum.xda-developers.com
Yup, I'm well familiar with that thread. I helped eparr with the guide a little, and gave him the older stock image that he couldn't find online anymore.
We also had a separate conversation about a similar problem I was/we were having (relevant to this discussion) here: https://forum.xda-developers.com/t/carriers-for-xperia-xz1-compact-in-us.4477627/ where we talked about his guide, custom flashing, the Sony CustomizationSelector app, modem overlays, and a few other things.
I think because I'm running an AOSP-based (rather than stock-based) ROM, some of these options aren't available to me, which is why I was trying to investigate EDL and diag modes to connect with and adjust the modem configurations directly.
I should probably explore some alternative ROMs but since this phone is also my daily driver, there's a high cost/interrupt to wiping, reinstalling, and repeatedly experimenting, so I've been reluctant to do anything too extreme until the holidays.
Did you test LOS? I believe they have implemented very special stuff for modem and customizations handling there...
I have not yet. I'm currently running an Oreo AEX build. But LOS is one of the ones on my list to experiment with when I get a chance to upgrade.
I think this is the stuff integrated in LOS:
GitHub - whatawurst/OpenCustomizationSelector
Contribute to whatawurst/OpenCustomizationSelector development by creating an account on GitHub.
github.com
Related
Introduction:
This post is a guide to show how to perform the NV edit required to unlock US GSM carriers(AT&T and T-Mobile etc.) on the VZW XT907/926 RAZR M/HD stock modem using a Motorola serviceware tool called RadioComm.
This is simply a different method to perform the same hack that was discovered by Arnold Snarb in the main thread about ATT/T-Mobile here.
http://forum.xda-developers.com/showpost.php?p=37123644&postcount=158
Despite the fact that he thanked me for leading the way in that post, he did some really brilliant analysis of the logs in QXDM to isolate this NV Item and saw something in the them that I had missed as well as guessing correctly about it's significance, and deserves all of the credit for this hack.
Everyone should please go and thank him in that post for the outstanding work.
He used a tool called DFS to access and edit NV Item 8322 and change the value of the first byte from 01 to 00 which disables the checking of the MCC/MNC against a list of banned networks and flags MCC 310 as Invalid Country Code.
That method requires booting into BP Tools mode from the boot menu and loading the Qualcomm diagnostic device interfaces.
The problem is that there are no signed 64bit drivers available and you must force load the drivers on Win7/8 64 bit for the diagnostic port in order to see the device properly and have NV read/write access.
This has been a stumbling block for many users and makes the NV editing unnecessarily difficult.
This method uses Factory boot mode and allows RadioComm to have full diagnostic mode access via the Motorola USB Networking driver that loads normally with the standard USB driver set. I will demonstrate 2 different ways to perform the edit, one manual and one using a preconfigured SEEM table file that writes the value in a single operation.
Neither of these methods is as easy as an update.zip install from custom recovery would be, but we don't have a binary that supports the motorola.update_nv function that we used for prior MDM6600 based devices available to us for the MSM8960 devices.
Given that some form of diagnostic mode software and a PC is required, I feel that RadioComm is probably an easier option for most users as it avoids the driver problems and has a clearer and simpler interface for NV read/write access than DFS.
Once you have the latest Motorola drivers installed and RadioComm loaded, this guide should make it very easy and safe to perform what is generally a complicated and potentially dangerous task of editing the radio NVM(Non Volatile Memory).
RadioComm itself is a terrifyingly complex piece of software with a GUI that can bring even the most seasoned and experienced phone hacker to their knees wondering what all the various windows, modules and buttons do.
It is the premier Motorola serviceware application and is designed by and intended for use by top level radio engineers and technicians.
It is an extremely powerful application that can access all models and chipsets of Motorola devices and perform a vast array of diagnostic testing and configuration operations and can be fully automated via multiple scripting languages.
It's just plain scary and confusing and very dangerous if not taken seriously.
Warning and disclaimer:
DO NOT PLAY AROUND WITH ANY FEATURES OR RANDOMLY HIT ANY BUTTONS IN RADIOCOMM!!!
YOU CAN RENDER YOUR PHONE DYSFUNCTIONAL OR UNBOOTABLE IN SECONDS!!!
This cannot be emphasized strongly enough!
Follow the instructions exactly as they are written and shown in the screenshots and you will find it very simple to use have no trouble doing the edit with either method.
You, the user, are the only person responsible for your actions and performing this hack will absolutely void your warranty the same way rooting or any other modifications to your device's software does!
That said, this hack will be undetectable and have no outward visible signs of having been performed other than the fact that any GSM SIM should work afterward.
Root is NOT required and this can be safely done and undone at will without making any other changes on the device and all normal services function properly on VZW's network with the edit in place. It appears to only affect the US GSM network block and nothing else.
Prerequisites:
You need to have a recent set of Motorola USB drivers v. 5.9.0 or greater installed on your PC with a full USB 2.0 compatible port.
You need a standard Motorola micro USB cable.
RadioComm 11.12.xx I have included a link to 11.12.2 below.
https://dl.dropbox.com/u/7632904/RadioComm_v11.12.2_Install.zip
This has been tested on Win7 64bit and WinXP SP3 32bit with .NET Framework 4.0 installed.
Method:
This guide assumes you already have RadioComm and the drivers properly installed and have rebooted both PC and the phone afterward.
The first instructions and screenshots describe the initial setup and manual method using the FTM Common 1 tab and the NV Access window in RadioComm.
When you first open RadioComm you will get a popup stating that the version is more than 2 months old. Just close it and continue.
Now go to the top left corner and hit the Main button and select the MA: Common/MDM6x00 as shown in the first screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, go to Settings/USB and select PST USB Driver as shown in the second screenshot.
Test Command Format should default to P2K05 lower in Setings menu.
Leave all other options default.
Now we are ready to connect the phone and perform the edit.
Make sure you have Connect as Media Device in USB settings and USB Debugging enabled in Developer Options.
Power off the phone and then hold both Vol Up and Down + Power to enter the boot menu.
Use the Vol Down key to scroll down in the menu to Factory and then Vol Up key to select and the phone will boot.
Connect the USB cable and RadioComm will enumerate the phone and the radio button in the top right will change colors.
It will cycle sever times red to yellow and eventually go green when the device is fully enumerated and shows as XT907 in the status bar
at the bottom of the screen. You can read the Software Version and MEID/ESN/pESN buttons to make sure everything is working properly.
Each successful read the GUI will flash green and the Command buffer will turn green and any selected button will be green.
Any unsuccessful attempt will turn red.
If not, then restart everything and check over all settings again before proceeding.
Now go to the tabs bar across the top middle of the GUI and select FTM Common 1 tab and go to the NV access window in the center right of that tab and select the top menu Item "FFFF Manual Entry" as shown in the third screenshot.
Now hit the Read button and you will get 2 popup windows.
In the first window you will enter the Decimal NV Item ID 8322 and in the second you will enter the byte length to be read 1 as shown in the fourth screenshot.
When you hit ok it will read the NV Item and flash green and display the data in the hex output buffer below and you will see 01 for the value as shown in the fifth screen shot.
Now highlight the 01 and change it to 00 and hit the write button and this time it will only popup once asking for the Decimal NV Item ID 8322. When you hit OK the item will be written and the GUI will again flash green for a successful write as shown in the sixth screenshot.
You are now finished and can either use the restart button at top right of RadioComm to reboot or manually restart the phone.
The last screen shot is edited to show the steps to use the NV/SEEM feature with a SEEM table file I have provided below to do all of the steps as a single operation. Some users may find this easier than manually editing in the NV Access window but it's really almost the same number of steps.
Go to the top left and hit Features and select NV/SEEM and another window will open and the radio button will cycle again a couple time as it re enumerates the device again it will go green finally. Follow the instructions in the seventh screenshot and be sure to use the Restart button in the main window after you close NV/SEEM because its suspends the phone and it will be black screen and unresponsive and require holding Vol keys and Power for 10 secs to reset it otherwise.
Congrats! All done now and the rest is just putting in a SIM and selecting GSM/UMTS in Network Settings and everything should just work!
Below is the link for the .NVM SEEM table file.
https://dl.dropbox.com/u/7632904/TBH_RAZR_M_GSM_Unlock.NVM
Please use this thread to discuss issues relating to this method and RadioComm and keep general discussion of the phone on US carriers in the other thread, thank you!
<Reserved>
Thanks man.. gonna try this when I get home tonight. I was actually just thinking about switching vendors from VZW to someone else and didn't really want to buy a new phone.
Maybe now I don't have to. Proof is in the pudding though, maybe I'll by a cheap month of Straight Talk to see if it works?
Yehudah said:
Thanks man.. gonna try this when I get home tonight. I was actually just thinking about switching vendors from VZW to someone else and didn't really want to buy a new phone.
Maybe now I don't have to. Proof is in the pudding though, maybe I'll by a cheap month of Straight Talk to see if it works?
Click to expand...
Click to collapse
Running RAZR M in US on straight talk now. Works wonderful!!!
Thanks a lot! im a total noob when it comes to most of this, but it worked perfect for me!!
Hmm, MDM6x00? Won't that work on the OG RAZR XT912 / Droid 4 as well?
Skrilax_CZ said:
Hmm, MDM6x00? Won't that work on the OG RAZR XT912 / Droid 4 as well?
Click to expand...
Click to collapse
The MA used in RadioComm is the same chip set base as the RAZR/D4 because it's the closest to the MSM8960 available in this version, which is more than 18 months old now.
What we really need is an updated version of RadioComm with full support for the newer chip sets.
This specific NV Item 8322 does not exist on the MDM6600 chip set devices and I have not been able to find a similar boolean switch item for those phones, unfortunately.
I have been logging with QXDM extensively searching for a way to disable the MCC/MNC block on MDM6600 without success so far.
I have dumps of all of the readable NV items from 0000-12000 from many devices running various builds and even a dump from Chinese engineering build on P3Droid's Dev model where everything is working as it should with open GSM on US carriers.
I would love some help from someone with a better understanding of the radio and diagnostic mode access than myself.
Very few people know how to use the software to even start analyzing the problem.
Remember to install the latest Motorola drivers and *especially* highlight the entire 01 and type 00. I was backspacing only the 1 and it did not "stick" when writing. So HIGHLIGHT, don't backspace. Works perfectly.
is it possible to write the NV item to the Droid 4 then edit ? ?
cellzealot said:
The MA used in RadioComm is the same chip set base as the RAZR/D4 because it's the closest to the MSM8960 available in this version, which is more than 18 months old now.
What we really need is an updated version of RadioComm with full support for the newer chip sets.
This specific NV Item 8322 does not exist on the MDM6600 chip set devices and I have not been able to find a similar boolean switch item for those phones, unfortunately.
I have been logging with QXDM extensively searching for a way to disable the MCC/MNC block on MDM6600 without success so far.
I have dumps of all of the readable NV items from 0000-12000 from many devices running various builds and even a dump from Chinese engineering build on P3Droid's Dev model where everything is working as it should with open GSM on US carriers.
I would love some help from someone with a better understanding of the radio and diagnostic mode access than myself.
Very few people know how to use the software to even start analyzing the problem.
Click to expand...
Click to collapse
Can I use a similar way to unlock XT902(Japanese Razr M)? I can't find 8322 in XT902.......
Followed instructions and worked perfectly. The key for me was the latest Motorola drivers AND the Motorola USB cable that came with the phone. I tried other cables that both charged and synced but the only that worked for this was the Moto cable. Using Win XP SP3 ( 12 year old OS on brand new work laptop. WTF!)
i was wondering if this works on other networks such as boost mobile,net10, criket etc...? i honestly dont have enough money to buy a new phone and whatnot. the whole reason why i did this is because i lost my job and now i cant pay my phone bill and it keeps getting higher and higher.
AKG0214 said:
i was wondering if this works on other networks such as boost mobile,net10, criket etc...? i honestly dont have enough money to buy a new phone and whatnot. the whole reason why i did this is because i lost my job and now i cant pay my phone bill and it keeps getting higher and higher.
Click to expand...
Click to collapse
Boost - No
Cricket - No
They're both cdma. This is to allow the GSM side (SIM CARD based) of the phone to work on other carriers. With that said, your best options are
Net10, Straight Talk, ATT, T-Mobile, Simple Mobile, H20, Orange, and there's a plethora of others out there. Post paid and pre-paid.
@DSDD
I beleive your XT902 is GSM by default. So if what your asking is will this bypass the network lock, no, the device needs to be unlocked by code. Then you can use it outside of the current carrier/country.
after boot, it is set back to 01 again @ address 8322
my phone version is Bsmq_vzw-user 4.1.1 9.8.1Q_27-2 4 release-keysSM_BP_1139.000.32.62P
after write to 8322 with zeros, I read it again the confirm it is written, but after rebooting the phone, the value is back to 01 again.
I guess the verizon driver may override this value during rebooting?
any help?
should I root the phone?
==
thanks
cellzealot said:
Introduction:
This post is a guide to show how to perform the NV edit required to unlock US GSM carriers(AT&T and T-Mobile etc.) on the VZW XT907/926 RAZR M/HD stock modem using a Motorola serviceware tool called RadioComm.
This is simply a different method to perform the same hack that was discovered by Arnold Snarb in the main thread about ATT/T-Mobile here.
http://forum.xda-developers.com/showpost.php?p=37123644&postcount=158
Despite the fact that he thanked me for leading the way in that post, he did some really brilliant analysis of the logs in QXDM to isolate this NV Item and saw something in the them that I had missed as well as guessing correctly about it's significance, and deserves all of the credit for this hack.
Everyone should please go and thank him in that post for the outstanding work.
He used a tool called DFS to access and edit NV Item 8322 and change the value of the first byte from 01 to 00 which disables the checking of the MCC/MNC against a list of banned networks and flags MCC 310 as Invalid Country Code.
That method requires booting into BP Tools mode from the boot menu and loading the Qualcomm diagnostic device interfaces.
The problem is that there are no signed 64bit drivers available and you must force load the drivers on Win7/8 64 bit for the diagnostic port in order to see the device properly and have NV read/write access.
This has been a stumbling block for many users and makes the NV editing unnecessarily difficult.
This method uses Factory boot mode and allows RadioComm to have full diagnostic mode access via the Motorola USB Networking driver that loads normally with the standard USB driver set. I will demonstrate 2 different ways to perform the edit, one manual and one using a preconfigured SEEM table file that writes the value in a single operation.
Neither of these methods is as easy as an update.zip install from custom recovery would be, but we don't have a binary that supports the motorola.update_nv function that we used for prior MDM6600 based devices available to us for the MSM8960 devices.
Given that some form of diagnostic mode software and a PC is required, I feel that RadioComm is probably an easier option for most users as it avoids the driver problems and has a clearer and simpler interface for NV read/write access than DFS.
Once you have the latest Motorola drivers installed and RadioComm loaded, this guide should make it very easy and safe to perform what is generally a complicated and potentially dangerous task of editing the radio NVM(Non Volatile Memory).
RadioComm itself is a terrifyingly complex piece of software with a GUI that can bring even the most seasoned and experienced phone hacker to their knees wondering what all the various windows, modules and buttons do.
It is the premier Motorola serviceware application and is designed by and intended for use by top level radio engineers and technicians.
It is an extremely powerful application that can access all models and chipsets of Motorola devices and perform a vast array of diagnostic testing and configuration operations and can be fully automated via multiple scripting languages.
It's just plain scary and confusing and very dangerous if not taken seriously.
Warning and disclaimer:
DO NOT PLAY AROUND WITH ANY FEATURES OR RANDOMLY HIT ANY BUTTONS IN RADIOCOMM!!!
YOU CAN RENDER YOUR PHONE DYSFUNCTIONAL OR UNBOOTABLE IN SECONDS!!!
This cannot be emphasized strongly enough!
Follow the instructions exactly as they are written and shown in the screenshots and you will find it very simple to use have no trouble doing the edit with either method.
You, the user, are the only person responsible for your actions and performing this hack will absolutely void your warranty the same way rooting or any other modifications to your device's software does!
That said, this hack will be undetectable and have no outward visible signs of having been performed other than the fact that any GSM SIM should work afterward.
Root is NOT required and this can be safely done and undone at will without making any other changes on the device and all normal services function properly on VZW's network with the edit in place. It appears to only affect the US GSM network block and nothing else.
Prerequisites:
You need to have a recent set of Motorola USB drivers v. 5.9.0 or greater installed on your PC with a full USB 2.0 compatible port.
You need a standard Motorola micro USB cable.
RadioComm 11.12.xx I have included a link to 11.12.2 below.
https://dl.dropbox.com/u/7632904/RadioComm_v11.12.2_Install.zip
This has been tested on Win7 64bit and WinXP SP3 32bit with .NET Framework 4.0 installed.
Method:
This guide assumes you already have RadioComm and the drivers properly installed and have rebooted both PC and the phone afterward.
The first instructions and screenshots describe the initial setup and manual method using the FTM Common 1 tab and the NV Access window in RadioComm.
When you first open RadioComm you will get a popup stating that the version is more than 2 months old. Just close it and continue.
Now go to the top left corner and hit the Main button and select the MA: Common/MDM6x00 as shown in the first screenshot.
Next, go to Settings/USB and select PST USB Driver as shown in the second screenshot.
Test Command Format should default to P2K05 lower in Setings menu.
Leave all other options default.
Now we are ready to connect the phone and perform the edit.
Make sure you have Connect as Media Device in USB settings and USB Debugging enabled in Developer Options.
Power off the phone and then hold both Vol Up and Down + Power to enter the boot menu.
Use the Vol Down key to scroll down in the menu to Factory and then Vol Up key to select and the phone will boot.
Connect the USB cable and RadioComm will enumerate the phone and the radio button in the top right will change colors.
It will cycle sever times red to yellow and eventually go green when the device is fully enumerated and shows as XT907 in the status bar
at the bottom of the screen. You can read the Software Version and MEID/ESN/pESN buttons to make sure everything is working properly.
Each successful read the GUI will flash green and the Command buffer will turn green and any selected button will be green.
Any unsuccessful attempt will turn red.
If not, then restart everything and check over all settings again before proceeding.
Now go to the tabs bar across the top middle of the GUI and select FTM Common 1 tab and go to the NV access window in the center right of that tab and select the top menu Item "FFFF Manual Entry" as shown in the third screenshot.
Now hit the Read button and you will get 2 popup windows.
In the first window you will enter the Decimal NV Item ID 8322 and in the second you will enter the byte length to be read 1 as shown in the fourth screenshot.
When you hit ok it will read the NV Item and flash green and display the data in the hex output buffer below and you will see 01 for the value as shown in the fifth screen shot.
Now highlight the 01 and change it to 00 and hit the write button and this time it will only popup once asking for the Decimal NV Item ID 8322. When you hit OK the item will be written and the GUI will again flash green for a successful write as shown in the sixth screenshot.
You are now finished and can either use the restart button at top right of RadioComm to reboot or manually restart the phone.
The last screen shot is edited to show the steps to use the NV/SEEM feature with a SEEM table file I have provided below to do all of the steps as a single operation. Some users may find this easier than manually editing in the NV Access window but it's really almost the same number of steps.
Go to the top left and hit Features and select NV/SEEM and another window will open and the radio button will cycle again a couple time as it re enumerates the device again it will go green finally. Follow the instructions in the seventh screenshot and be sure to use the Restart button in the main window after you close NV/SEEM because its suspends the phone and it will be black screen and unresponsive and require holding Vol keys and Power for 10 secs to reset it otherwise.
Congrats! All done now and the rest is just putting in a SIM and selecting GSM/UMTS in Network Settings and everything should just work!
Below is the link for the .NVM SEEM table file.
https://dl.dropbox.com/u/7632904/TBH_RAZR_M_GSM_Unlock.NVM
Please use this thread to discuss issues relating to this method and RadioComm and keep general discussion of the phone on US carriers in the other thread, thank you!
Click to expand...
Click to collapse
---------- Post added at 11:14 PM ---------- Previous post was at 10:48 PM ----------
tried again for couple of times, this time it actually works.
maybe last time I reboot the phone too early?
sipida said:
my phone version is Bsmq_vzw-user 4.1.1 9.8.1Q_27-2 4 release-keysSM_BP_1139.000.32.62P
after write to 8322 with zeros, I read it again the confirm it is written, but after rebooting the phone, the value is back to 01 again.
I guess the verizon driver may override this value during rebooting?
any help?
should I root the phone?
==
thanks
Click to expand...
Click to collapse
Glad you got it working. There is no VZW software on the phone capable of writing to the radio NV, so it's not being reverted by anything.
If anyone else has similar issues I would suggest trying the NV/SEEM method as that will definitely write the item properly.
queberican351 said:
@DSDD
I beleive your XT902 is GSM by default. So if what your asking is will this bypass the network lock, no, the device needs to be unlocked by code. Then you can use it outside of the current carrier/country.
Click to expand...
Click to collapse
XT902 has sim lock, and there is no way to key in unlock code. So I think it maybe unlocked by modifying another NV item.
Does this tutorial unlock mobile data usage on other carriers. I cannot seem to get data working on my XT907 in Australia. GSM and MMS work fine, so why doesnt Data?
I don't know for certain because I only have experience with domestic US GSM carriers, but I tend to doubt it.
You can try it and see and revert it easily if it doesn't work. You can also try flashing the Telstra XT905 NON-HLOS.bin(modem) and fsg.mbn(carrierEFS/NVM config).
This was the method used to get US GSM service on XT907 before the method shown here was discovered.
It works but is limited to GSM/EDGE data services here in the US.
I am inclined to think it is some other problem with the device because it should work as a global capable phone by default.
dsdd said:
XT902 has sim lock, and there is no way to key in unlock code. So I think it maybe unlocked by modifying another NV item.
Click to expand...
Click to collapse
If it has a sim lock and you can acquire the code open your dialer and press #073887* (#0SETUP*) and it'll prompt you for the code.
Several people have PMd me questions about this method and I would much prefer that they be posted here in the thread so that everyone may benefit from the information.
Please include as much information about your PC and driver versions and be as thorough as possible in explaining your problems.
This thread is for those that picked up a T-Mobile G Pad X 8.0 from the free after rebate promotion, here's a good thread to ask questions until we get a separate forum. Our device will initially get what XDA calls Enhanced Tags (ET)/(Topics). This means threads for the device can be found listed together when someone looks up the device finder/search. These ET devices, if they prove popular and achieve around 4 pages of threads are then given a full set of dedicated forums. Once achieved, we can request a dedicated LG G PAD III/X 8.0 Forum. Information will be filled in as other members report them or as I find them. This tablet is very similar to the LG G Pad III in South Korea (v525) and Canada (v522). This tablet is exactly the same, hardware wise, as the LG G Pad X 8.0 for AT&T (v520). While this thread is mainly focused on the T-Mobile variant, you'll find information, bounties and development applicable/compatible with other variants as well.
Root (?)
Root has been achieved for the v521 (T-Mobile). Follow this guide to root your device. The v522 (Canada) has not been rooted yet. The v520 (AT&T) has not been rooted yet.
Root Bounty
US variant pledges are available for @tungkick to claim via PMing the pledgers.
OS (?)
CyanogenMod is not available for this device.
An AOSP ROM is not available for this device.
iPioneer Stock by @xtremelora is available
ROM Bounty
Bootloader Unlock (?)
The tablet bootloader is not unlocked by default. This is required for rooting the LGV521 (T-Mobile). You may unlock it by following these steps:
Warning: A bootloader unlock will wipe your tablet.
1. Enable Developer Settings (About tablet > Software info > Build number Tap 5 times)
2. Enable USB Debugging (Developer options) (Example)
3. Enable OEM Unlock (Developer options)
4. Install Android Debug Bridge (?)
5. Install LG Device Drivers if needed (Available below)
6. Open 'Command Prompt' and type in 'adb shell'
7. Enter these commands into ADB Shell for your device:
reboot bootloader
fastboot oem unlock
fastboot reboot
8. Check if the bootloader is unlocked by entering:
fastboot getvar unlocked
NOTE: While the bootloader is unlocked, you will get the "The software on this device cannot check for corruptions" message upon boot unless you install a modified boot image and kernel to get rid of the message.
Network Unlock (?)
Official Methods:
T-Mobile - You must have paid your device balance in FULL to request an unlock from T-Mobile.
AT&T - Please check your eligibility here..
Telus - Please check your eligibility here.
Rogers - Please check your eligibility here. There will be a $50 fee for a device unlock.
Bell - Please check eligibility here. There will be a fee upwards of $50 for device unlock.
Fido - Please check your eligibility here. There will be a $50 fee for device unlock.
Contact Customer Care for your carrier to request the Mobile Device Unlock code for your tablet.
From any Home screen, tap the Apps icon.
Tap Contacts.
Tap the Search contacts field.
Enter 2945#*521#.
Tap the Add contact [+] icon in the top-right.
Tap Network Lock. (Example)
Enter your 16-digit Mobile Device Unlock code.
Make sure the 'SIM Network Unlock Successful' message displays.
NOTE: You ONLY have three (3) tries to enter the unlock code correctly before the device becomes permanently locked, please contact customer service if the code returns 'Unlock Unsuccessful.'
Wait for the tablet to automatically restart.
Your tablet is now unlocked.
Unofficial Methods: There are 3rd party sites that offer network unlock codes. Members have reported success on the following sites:
1. http://mobileunlock24.com/gb/lg/unlock-lg-g-pad-x-80
2. http://www.mobileincanada.com/ - Canada
Recovery (?)
TWRP 3.0.2.0 is available for all device variants
Kernel (?)
A custom kernel has not been developed yet. Learn more about the benefits of a custom kernel.
Xposed (?)
Xposed framework has been tested and is functional. Download the latest 32-bit version (ARM) for Marshmallow.
Debugging
Device Drivers:
Source 1 - Multiple Options
Source 2 - Quick Download
Android Debug Bridge: (?)
Source 1 - PC Quick Download
Source 2 - PC Minimal Download
Source 3 - PC Minimal Download
Source 4 - PC Download
Source 5 - Android SDK Download
More for Linux, Mac and PC
Modifications
Disable KnockON:
1. Download QuickShortcutMaker
2. Search for "KnockON" and you'll see it under the Settings Activity or look under the settings Activity
3. Tap on 'Try' and it will open the hidden settings menu for disabling.
4. Toggle the setting 'Off' and the change will be immediate.
Adoptable storage: (?)
1. Open your command window / terminal on your computer and type the 'adb shell' command with your phone connected.
2. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 or disk:179,160).
3. Partition the disk. To partition the disk above as fully adopted storage, use the command 'sm partition disk:179,160 private'. If 50/50 split between adopted and regular is desired, use the command 'sm partition disk:179,160 mixed 50'
4. Migrate data (Example)
NOTE: You will need 'Developer settings' enabled, Android Debug Utility installed and 'USB debugging' enabled to be able to follow these steps.
Credit: @paulobrien
Setup Inspiration
Troubleshooting
Q: My tablet says 'Cannot record video when another app is using audio' when trying to record a video.
A: This may be because Google Now 'Ok Google' is enabled on all screens. Try disabling this option.
Q: My tablet is having trouble with playing videos in MX Player and other 3rd party players.
A: This may be because of the 'Improve Playback Quality' option in Display settings. Try disabling this option.
You can post further questions in a dedicated thread here and post the link to that thread in this thread for a response or help.
Cases, Screen Protector and Accessories
Folio Case (eBay) - $8
Folio Case (Amazon) - ~$10
TPU Case (eBay) - ~$8
Tempered Glass Screen Protector (LG G Pad X 8.0/G Pad 3 8.0) - ~$6
Samsung EVO+ microSD card | PRO+ microSD card - Good for Adoptable Storage
More on Amazon | eBay
Specifications (?)
OS: Android 6.0.1
Android security patch level: July 2016
Baseband version: MPSS.TA.1.0.c3-00055-8952_GEN_PACK-1.56400.1.59543.1 (T-Mobile version)
Build number: MMB29M (T-Mobile version)
Software version: V52110C (T-Mobile version)
Processor: Snapdragon 617 1.5GHz Octa-Core
GPU: Adreno 405
RAM: 2GB
Screen Resolution: 1920 x 1200
Internal Storage: 16GB (Canadian & USA versions) 32GB (Korean version)
Camera: Front - 5MPX (Canadian, Korean & USA versions); Back - 5MPX (Canadian & USA versions, 8MPX (Korean version)
Slots: microSD up to 2TB, one (1) Full-Sized USB and one (1) nanoSIM
Mirroring: DLNA, Miracast - NOT SlimPort Compatible
Battery: 4650mAh (Canadian & USA versions) 4800mAh (Korean version)
Dimensions: 124.10 x 210.70 x 7.90 centimeters, 8.3 x 4.8 x 0.31 inches
Weight: 309.00 grams, 10.9 ounces
Wi-Fi standards: 802.11 a/b/g/n/ac
Bluetooth: v4.20
Bands: Quad Band GSM; LTE: 2, 3, 4, 7, 12; UMTS: Band I (2100), Band II (1900), Band IV (1700/2100), Band V (850)
Canadian Variant: LGV522 | Korean Variant: LGV525 | USA (T-Mobile) Variant: LGV521WG | USA (AT&T) Variant: LGV520
Suggestions
If there are any issues with this thread, anything you'd like to add, any suggestions you'd like to provide or to get my attention - quote one of my posts or private message me.
Unlocked bootloader, but what do we need to make TWRP and a custom ROM (looking mostly for AOSP)?
Reserved Space
I got paid 15 bucks to take this tablet off T-Mobile's hands and it has an unlocked bootloader!? Amazing stuff!
---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------
mr_verystock said:
Unlocked bootloader, but what do we need to make TWRP and a custom ROM (looking mostly for AOSP)?
Click to expand...
Click to collapse
Someone smarter than you or I.
Great spec tablet with great price point! I like almost free to cheap!
Needs some optimization though. Would love to see some root for this thing and a custom recovery. Hell Maybe Fulmics on this thing
Any way to get rid of the "The software on this device cannot check for corruptions" screen after unlock bootloader?
Sent from my SM-N900T using XDA-Developers mobile app
googlephone said:
Any way to get rid of the "The software on this device cannot check for corruptions" screen after unlock bootloader?
Sent from my SM-N900T using XDA-Developers mobile app
Click to expand...
Click to collapse
That is due to android 6.0, going forward any device unlocked will do this.
runderekrun said:
I got paid 15 bucks to take this tablet off T-Mobile's hands and it has an unlocked bootloader!? Amazing stuff!
---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------
Someone smarter than you or I.
Click to expand...
Click to collapse
its not hard to port twrp, i very much doubt im smarter than you, and ive ported recovery to over 20 devices.
avishah395 said:
I believe we need a software update, then you can use those files to make TWRP. I do not know how to make TWRP and a custom ROM.
Click to expand...
Click to collapse
http://opensource.lge.com/osSch/list?types=ALL&search=V521
at teh bottom, software list. once we have a file there i can downlaod it, rip out recovery.img and build TWRP
I have no plans to work on any AOSP based rom for this device, my days of spending hours working on a device are over. however i have this tablet so anything that i do work on will be released.
@avishah395 http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/ a guide to enable adoptable storage without root. anyone trying this needs to make sure they read the list of disks carefully, mine was 179,64 not 179:64
googlephone said:
Any way to get rid of the "The software on this device cannot check for corruptions" screen after unlock bootloader?
Sent from my SM-N900T using XDA-Developers mobile app
Click to expand...
Click to collapse
For now, you'll need a modified boot image and kernel to get rid of the message.
shabbypenguin said:
That is due to android 6.0, going forward any device unlocked will do this.
its not hard to port twrp, i very much doubt im smarter than you, and ive ported recovery to over 20 devices.
http://opensource.lge.com/osSch/list?types=ALL&search=V521
at teh bottom, software list. once we have a file there i can downlaod it, rip out recovery.img and build TWRP
I have no plans to work on any AOSP based rom for this device, my days of spending hours working on a device are over. however i have this tablet so anything that i do work on will be released.
@avishah395 http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/ a guide to enable adoptable storage without root. anyone trying this needs to make sure they read the list of disks carefully, mine was 179,64 not 179:64
Click to expand...
Click to collapse
I don't have an SD card for this device yet. Did LG hide the adoptable storage menu?
avishah395 said:
I don't have an SD card for this device yet. Did LG hide the adoptable storage menu?
Click to expand...
Click to collapse
its up to the oem, lg and samsung dont allow it by default.
shabbypenguin said:
That is due to android 6.0, going forward any device unlocked will do this.
its not hard to port twrp, i very much doubt im smarter than you, and ive ported recovery to over 20 devices.
http://opensource.lge.com/osSch/list?types=ALL&search=V521
at teh bottom, software list. once we have a file there i can downlaod it, rip out recovery.img and build TWRP
I have no plans to work on any AOSP based rom for this device, my days of spending hours working on a device are over. however i have this tablet so anything that i do work on will be released.
@avishah395 http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/ a guide to enable adoptable storage without root. anyone trying this needs to make sure they read the list of disks carefully, mine was 179,64 not 179:64
Click to expand...
Click to collapse
How many hours would it take to make an AOSP rom? I'm sure a few people would be willing to pay for a rom, including me.
avishah395 said:
How many hours would it take to make an AOSP rom? I'm sure a few people would be willing to pay for a rom, including me.
Click to expand...
Click to collapse
sorry, im not for sale
aosp roms are fairly time consuming, i spent probably 17-20 hours making the moto g 4g have a 85% complete CM rom. depending on the manufacturer and "sister" devices it can be easy like the moto g 4g, or it can be much harder. with this having a qualcomm cpu it is easier to get up and running, but to where its official and in is no small task and would probably take 2-3 months (after twrp gets ported).
shabbypenguin said:
sorry, im not for sale
aosp roms are fairly time consuming, i spent probably 17-20 hours making the moto g 4g have a 85% complete CM rom. depending on the manufacturer and "sister" devices it can be easy like the moto g 4g, or it can be much harder. with this having a qualcomm cpu it is easier to get up and running, but to where its official and in is no small task and would probably take 2-3 months (after twrp gets ported).
Click to expand...
Click to collapse
Ah I see. Oh well. OS is fairly decent compared to LG G Pad F. I'll try tinkering with the System UI a bit. I wish it was as easy as sideloading something like Good Lock.
So I'm curious about this. I went in to upgrade my two phones today and I ended up walking out with one of these as well for my son (it's free minus the $38 tax, why not). I was looking for a screen protector for it but only LG G Pad 8.0 comes up. Is there a difference between that and this X 8.0?
http://www.xtremeguard.com/LG-G-Pad...g-g-pad-8.0-screen-protector.htm#.V2X5vfkrK00
Thanks for any insight guys.
Pretty neat tablet so far!
uoY_redruM said:
So I'm curious about this. I went in to upgrade my two phones today and I ended up walking out with one of these as well for my son (it's free minus the $38 tax, why not). I was looking for a screen protector for it but only LG G Pad 8.0 comes up. Is there a difference between that and this X 8.0?
http://www.xtremeguard.com/LG-G-Pad...g-g-pad-8.0-screen-protector.htm#.V2X5vfkrK00
Thanks for any insight guys.
Pretty neat tablet so far!
Click to expand...
Click to collapse
That XTREMEGUARD is for a different model. The front-facing camera is in a different place on this model, and the curve is slightly different.
I went with this - http://www.ebay.com/itm/Premium-Tem...ard-For-LG-G-Pad-2-3-F-8-0-V940-/331852399759 (FOR LG G PAD 3 8.0)
and this case - http://www.ebay.com/itm/301985372936
LG G Pad 3 8.0 is the option you selected?
EDIT- Just saw you clarified that lol. Thank you.
I have extra tempered glass for G Pad F 8.0. It's smaller a bit, but it's the best alternative.
I think G5 and V10 (6.0) root method should work.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
avishah395 said:
This thread is for those that picked up a T-Mobile G Pad X 8.0 recently from the Fathers Day promotion, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General. The information will be filled in as other members report them or as I find them once I get the tablet. This tablet is very similar to the LG G Pad III in South Korea (v525)
Root
Root has not been attempted.
Bootloader Unlock
The tablet bootloader is not unlocked by default.
1. Enable Developer Settings (About tablet > Software info > Build number Tap 5 times)
2. Enable USB Debugging (Developer options)
3. Enable OEM Unlock (Developer options)
4. Install ADB (Android Debug Bridge)
5. Enter these commands into ADB:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
NOTE: While the bootloader is unlocked, you will get the "The software on this device cannot check for corruptions" message upon boot unless you install a modified boot image and kernel to get rid of the message.
OS
No ROM development has been planned at this time.
Recovery
TWRP coming soon (Thanks @shabbypenguin)
Kernel
Nothing here yet!
Xposed
Xposed has not been tested on this tablet
Adoptable storage
1. Open your command window / terminal on your computer and type the 'adb shell' command with your phone connected. You will to follow all the same steps for bootloader unlocking except the OEM unlock setting and the commands.
2. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 or disk:179,160).
3. Partition the disk. To partition the disk above as fully adopted storage, use the command 'sm partition disk:179,160 private'. If 50/50 split between adopted and regular is desired, use the command 'sm partition disk:179,160 mixed 50'
Credit: @paulobrien
Click to expand...
Click to collapse
Make sure the following will work
Code:
fastboot flash recovery <filename>
fastboot boot recovery <filename>
They're disabled with G5.
If that happened, flashing tot with LGUP is alternative option.
shabbypenguin said:
That is due to android 6.0, going forward any device unlocked will do this.
its not hard to port twrp, i very much doubt im smarter than you, and ive ported recovery to over 20 devices.
http://opensource.lge.com/osSch/list?types=ALL&search=V521
at teh bottom, software list. once we have a file there i can downlaod it, rip out recovery.img and build TWRP
I have no plans to work on any AOSP based rom for this device, my days of spending hours working on a device are over. however i have this tablet so anything that i do work on will be released.
@avishah395 http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/ a guide to enable adoptable storage without root. anyone trying this needs to make sure they read the list of disks carefully, mine was 179,64 not 179:64
Click to expand...
Click to collapse
You need to find other places for software because you will never see they put anything under the software list ay the bottom for any LG devices.
Sent from my LG-v410 using XDA Premium App
googlephone said:
You need to find other places for software because you will never see they put anything under the software list ay the bottom for any LG devices.
Sent from my LG-v410 using XDA Premium App
Click to expand...
Click to collapse
You can find everything you need in the zip file.
There's 2 gz files. You can unpack both.
mingkee said:
You can find everything you need in the zip file.
There's 2 gz files. You can unpack both.
Click to expand...
Click to collapse
Please read about what we were talking about before you chime in.
This was what shabbypenguin said:
http://opensource.lge.com/osSch/list?types=ALL&search=v521
at teh bottom, software list. once we have a file there i can downlaod it, rip out recovery.img and build TWRP
I was talking about there will never be any file in the software list at the bottom. So don't wait for anything showing up there.
What you talked about was the source code released by LG under the "Model list" tab.
If LG release a firmware, which may be needed to extract recovery.img for building TWRP, you can find it through
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR IMEI
Currently, there is nothing there.
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Screenshots and photos:
Screenshot of About Phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot of dual VoLTE:
Photos of the filed card tray inside RP2:
The original Samsung tray:
And after filing:
Reserved for minor fixes
that's interesting
i have tried this, but the second imei doesn't appears what am I doing wrong?
ps: i find second imei in QCN backup
IMG
I finally got it
i updated to rom deodexed and zipalign from Warrior1988
after that I looked at the settings, the second Imei appeared
then I put sim card, android recognizes then it worked
PS: i modded SIM Card with MicroSD, now i have dual SIM with MicroSD :laugh:
IMG
unfortunately, now i see this message on starting, but starts normally (don't shutdown) :victory:
IMG
Update: you can remove this with command
reboot "dm-verity enforcing"
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
th3cavalry said:
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
Click to expand...
Click to collapse
I did this method, and used default sim card tray
and thanks for command
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Did you have any issues with PDC in the beginning?
updateing said:
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Click to expand...
Click to collapse
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
PDC works for me from the beginning. Please check:
1. Did you install the correct driver for the RmNet device?
2. There is a combo box in PDC window with nothing selected by default. Could you choose HS-USB WWAN Adapter in its dropdown list?
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
for me the second IMEI only worked after I installed this https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502
and to PDC work i used this driver https://androidfilehost.com/?fid=11410963190603864074
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Gamesoul Master said:
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Click to expand...
Click to collapse
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
updateing said:
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
Click to expand...
Click to collapse
Makes sense. I suppose I shouldn't trivialize the process. It mostly just surprises me that the hardware (and some of the software) is there at all. They must have had plans to do dual-SIM up until almost the last minute, because otherwise I can't imagine why they wouldn't save the money needed to put that extra hardware in there. And I can't imagine they'll release any such thing at this point. They basically shut down their mobile phone division, and haven't even released a software update in months.
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
aura:/ #
---------- Post added at 02:27 PM ---------- Previous post was at 02:10 PM ----------
t-mobile_mda said:
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
aura:/ #
Click to expand...
Click to collapse
i think it is not working on oreo..tried again on pie and worked again...
Code:
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>adb shell
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
What are the chances of breaking my phone with these steps?
Just like anything else, trial and error.
So does this kill WiFi calling?
I tried this and I jacked it up a bit. i got it to get both SIMs working (TMOUS and KT). The WiFi calling for TMOUS stopped working and also if I went to "Mobile Data" it reset the radio and never opened the menu. So i tried to revert and it got stuck in a boot loop and when i did get in the cell was completely not working, No sim, no IMEI. Luckily i flashed an older ROM (shipped 8.1MR0) and progressively upgraded through the ROMs from there and have service again. This tells me that the Stock Razer Images from their developer site don't have 'everything' for a full restore.
t-mobile_mda said:
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
Click to expand...
Click to collapse
Grab the Stock ROM for your version then extract it: https://developer.razer.com/razer-phone-dev-tools/factory-images/
All of them have "modem.img" used in there flash script in this command:
Code:
%fastboot_cmd% flash modem_a modem.img
%fastboot_cmd% flash modem_b modem.img
I don't think this works on 9MR2
Initial post for Sailfish Os for the Samsung Galaxy S2 (i9100) device.
Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! W A R N I N G !!
!! !!
!!(Although I am using this on my backup phone)!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! ROM IS NOT SUITABLE FOR DAILY DRIVE !!
!! ONLY FOR EXPERIMENTAL PURPOSES !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Making this port was challenging because Sailfish OS, from version 3, doesn't support kernel version 3.0 which is apparently the kernel on the S2.
Fortunately, the SailfishOS-porter guys do very seriously know their business and they are extremely helpful.
From here I would like to emphasize my gratitude towards them for helping me in this project! Thank you!
Requirements:
Before you start to download anything, please read it carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
For this ROM you can either use the stock partitions or you can re-partition to give more space to /system and /data. It doesn't matter which one you chose, I tried and both worked well.
Or if you scroll down to the New partition layout, you can use a completely unique partition layout which gives the most of the internal storage to Sailfish OS. (I currently use my device with this setup.)
Installation instructions:
1. Download all files, CM12.1 zip, Sailfish OS zip, twrp2.8.7.img and kernel*.img to the external SD card on the phone
2. Reboot into TWRP (hold buttons: Power on + Home + Volume up)
3. Do a factory reset
At this point if you want you can repartition the S2 internal storage. (Later you can put the stock layout back if you want to go back to Android.)
The steps for repartitioning are:
Download the 'Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB' or the 'Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB' .zip file and put into the external SD card. (The difference between these two is explained down at the New partition layout section
Then boot into TWRP and flash the zip as any other zip file. The script first will warn you that it cannot do the partitioning with mounted partitions and it also copies the script itself into /tmp. You just simply need to flash the copied version from /tmp and that will do the trick. The script will format the new partitions accordingly, so once it is completed you can go ahead with the next step.
4. Still in recovery, flash the CM12.1 image
5. Still in recovery, flash Sailfish Os image
6. Still in recovery, flash twrp2.8.7.img to recovery partition
7. Still in recovery, flash kernel*.img to boot partition (this step is not required since sfos 4.4, kernel is installed by flashing the zip file)
8. Reboot
9. Enjoy the latest (4.4.0.68) Sailfish OS on your i9100.
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on CM 12.1.
Downloads:
kernel12_mtp.img for Sailfish OS 3.2.1.20
kernel33016.img for Sailfish OS 3.3.0.16
kernel34024.img for Sailfish OS 3.4.0.24
kernel41024.img for Sailfish OS 4.1.0.24
kernel43015.img for Sailfish OS 4.3.0.15
twrp2.8.7.img for i9100
CM 12.1 for i9100
Sailfish OS 3.2.1.20 for i9100
Sailfish OS 3.3.0.16 for i9100
Sailfish OS 3.4.0.24 for i9100
Sailfish OS 4.1.0.24 for i9100
Sailfish OS 4.3.0.15 for i9100
Sailfish OS 4.4.0.64 for i9100
Sailfish OS 4.4.0.68 for i9100
Sailfish OS 4.4.0.72 for i9100
Odin v1.83
AOSP-LP-Kernel+_25-08-2015_TWRP-2.8.7.0.tar
Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB
Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB
Stock partition pit file
kernel07_flatpak (kernel with Flatpak support. Flatpak install/usage instructions.)
Some useful tips:
Low power mode aka ambient mode (in Fingerterm):
Code:
mcetool --set-low-power-mode=enabled
Disable lock screen animation (in Fingerterm):
Code:
mcetool --set-lockscreen-animation=disabled
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community-made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
Now the old clunky method is no longer needed. Once you flashed the twrp2.8.7.img to the recovery partition you can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Instructions for Bluetooth (On Sfos 4.3, BT works normally, don't need this magic)
BT works however turning it on/off is not as user friendly as I hoped. Here is a little instruction/troubleshooting.
Turn BT on (It only works from Settings/Bluetooth!!!!! DON'T try from TOP MENU!!):
If BT hasn't turned on since last boot:
go to Settings/Bluetooth
tap on the dot next to the Bluetooth option
If BT has turned on at least once since last boot:
go to Settings/Bluetooth and tap on the dot next to the Bluetooth option
go back to Settings
go to into Settings/Bluetooth again
tap on the dot next to the Bluetooth option (if it is not turned on repeat from Step 2! Eventually, BT should turn on.)
Turning BT off: Go to Settings/Bluetooth and tap on the white dot next to the Bluetooth option.
Notice: Never try to tap on the white dot twice without going back to the main menu of Settings.
Never try to turn BT on from Top Menu.
However, if you accidentally did any of these BT cannot be turned on again unless you:
reboot the device (this is the easiest) or
in a command line as root issue the following command 'systemctl restart bluetooth-rfkill-event.service' (this will restart the bluetooth-rfkill-event service)
I am not sure how pairing works with different devices.
New partition layout
I mentioned that I tried this Sailfish OS installation with the stock partitions and with another what created for Android 7.1.2. With the stock partitions however was a bit more sluggish than the other one. No wonder as in the stock partitions the /system has only 0.5GB and the /data has only 2GB storage and the rest 12GB is the separate internal storage (eMMC). In Sailfish the entire os (rootfs) including all directories (like /home) live on the /data partition so the 2GB was a bit tight. (The OS itself consumes about 1GB so not much left for apps and other stuff.)
With the other partition layout, the picture was a bit better as the /system had 1GB, the /data got 4GB and the rest 9GB remained for the internal storage. But the partition where the OS lives was separated from the 9GB partition. When I installed a few apps and copied some big files into the /home, I felt the limitation very soon.
Although this layout was sufficient for android but not good enough for Sailfish.
Therefore I have created my own partition table where I restructured the sizes accordingly to my need. (The lanchon repit zip file is available in the download section.)
In this new layout I gave 1GB for the /system (the prior 0.5GB was also fine as the CM12.1 base consumed only 400MB which let a 100MB free space, but I thought that might be not enough in the future so I have chosen 1GB here), I gave only 8MB for the internal storage (eMMC which is mounted into /android directory in this rom), and this made me possible to gave all the rest 14GB to the /data partition. So basically the Sailfish apps and /home can utilize the entire internal storage.
As an extra, on the S2 there is a 0.5GB /preload partition which is hidden and unused by default. In my partition setup I set 7MB to this and the rest almost 0.5GB is also added to the /data.
Go back to stock partitions
In case you would like to do this, you can download the stock partition pit file from the download section.
For this use Odin v1.83 which is also in the download section.
The steps are:
Boot the device into download mode and connect to the PC.
Open Odin v1.83 and tick the 'Re-partition' checkbox at the Option.
Then click on the PIT button and select the downloaded stock pit file.
Then click on the PDA button and select the downloaded TWRP (AOSP kernel) file.
Then click on start.
Done. You need to boot into TWRP and wipe all partitions (system, data, emmc) then you can install the stock rom back. (or if you select the stock rom at PDA instead of the AOSP kernel, it will do the repartition and install the stock rom as well. In this case, you don't need to wipe anything and the device will reboot into the stock Android at the end.)
Changelog:
15.02.2022
=========
General advice:
Patience! All (except camera) apps do start and work but they do need time. This is true for websites. When you clicked on something, wait patiently, eventually, it will start/load.
Work:
Same as previously
Improvement: Stock browser stable and works!
Do not work:
The camera app crashes the device into reboot.
03.09.2021
=========
Work:
Same as previously
Bluetooth does work, but once it is off, needs to be toggled a few times in Settings to make it turn on again.
14.06.2020
=========
Work:
Same as previously + Mobile data is fixed! (To make it work: change Protocol to IP in Settings/Mobile network/Data access point.)
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
06.05.2020
=========
The latest version of Sailfish OS 3.3.0.16 is available to download. This requires a different kernel. Both of these can be found in the download section.
Note: With the new version the patch that displays the provider logo at the bottom on the lock screen stopped working. This issue is not related to the OS. The owner of the app should fix it.
Update: In openrepos Kodi is fixed for SFOS 3.3.0.16!
29.04.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
MTP
Bluetooth (instruction is above)
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (Can be changed to 0.82 which is more appropriate for the device's screen. to do this as root run the 'kimmoli-diyicons.sh 0.82' command. It will fail to install imagemagick but will set the ratio to 0.82 and as we have all icons in place it will work.)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
the charging icon does work properly, however, there is a little delay
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
kernel and recovery .img can be flashed from TWRP (no need for PC to flash Sailfish OS, kernel and recovery)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
The softkeys (each side of the home button) work as notification leds
Do not work:
Mobile data (WIP)
Video recording (It doesn't really work in other 3.x versions either. See my test results here.)
There is an extra little issue that is a delay in screen refresh which is related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin. I managed to improve this but there is a little delay still. Probably this is the reason why we need to jump back to Settings every time before trying to turn BT on, but I am not sure.
04.04.2020
=========
Work:
Same as previously + Softkeys are used as notification leds
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
23.03.2020
=========
Work:
Same as previously + with 'kernel12_mtp' the MTP works!
Bluetooth partially works (to switch on BT requires a reboot or issue a command manually, it is still WIP)
Do not work:
Same as previously
25.02.2020
=========
Work:
Same as previously + with 'kernel07_flatpak' the Low Power Mode (AKA "sneak peek" or "ambient display") works! (install instruction is in this post)
Do not work:
Same as previously
23.02.2020
=========
Work:
Same as previously + but from now on you don't need PC and heimdall to flash kernel and twrp
Do not work:
Same as previously
19.02.2020
=========
Work:
The same as listed earlier + with the new kernel (kernel06) I attached you can boot into TWRP with the usual button combination (hold buttons: Power on + Home + Volume up)
Do not work:
Same as previously except the TWRP/Sailfish OS boot which has fixed.
08.02.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_
(where _sdcard_name_ is the name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (can be changed, I set 0.82 which is more appropriate for the device's screen resolution see the download section)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
Do not work:
Mobile data
Bluetooth (the bt driver is in the kernel, so in theory, with some config file changes on the device it can work)
MTP
Video recording (It doesn't really work in other devices with CM12.1 base.)
Screen delay in refresh (related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin)
the charging icon doesn't work properly: when the device is not on charger still shows it's charging (when I unplug the cable the message appears: "Charging..."
cannot boot into TWRP recovery (See Notes above)
Battery life:
In my experience the battery life is good. On standby, it can survive 10 days. (Almost 11.) I have checked once or twice daily during this period.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pictures:
App drawer
Top menu
Settings
About product
In case somebody missed these I would like to highlight some improvements since day 1:
Now both the kernel and twrp can be flashed as an .img from twrp (no need for PC and heimdall anymore)
Plus I uploaded a kernel with Flatpak support
With kernel07_flatpak, I have installed Flatpak and Angelfish but got an error when started Angelfish.
It looks like this is a limitation of the old kernel, but there might be a workaround.
I'll keep you posted.
With kernel12_mtp, MTP works. (and bluetooth partially)
The soft keys each side of the home button are used as notification leds. As this device doesn't have leds, the softkeys can be re-used as "leds". They do blink if the device is fully charged or there is an unread incoming text message. When the device is on charger they are on, otherwise both of them are off.
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Galaxyninja66 said:
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Click to expand...
Click to collapse
Sorry for delay in my reply.
The necessary repos in github are:
local manifest
dhd (in here the dhd submodule has to be refreshed from mer-hybris repo upgrade-3.2.1 branch)
droid-hal-i9100
droid-hal-version-i9100
android_device
kernel
The file (path to android base kernel image) command gives me: "Linux kernel ARM boot executable zImage (little-endian)"
A new image has been generated and can be downloaded. This one includes the patch of reusing the two softkeys (each side of the home button) and they do work as a notification leds!
Currently I am working on the mobile data and bluetooth (this latter partially works but is not reliable yet).
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Galaxyninja66 said:
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Click to expand...
Click to collapse
I am not sure what you d understand under 'any service' but except the mobile data, everything else works fine (calls in/out, texts in/out).
I don't know the difference between the i9100 and i9100m but on the internet you probably can find something about it.
One suggestion, before you start porting, install an android onto and boot into that and note the mounting points. This can save a little time when you need to set the fixup_mountpoints in hybris-boot.
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
I think the reason why this doesn't get more hype because this is a very old device and except some old fashioned folks like us, not many are using anymore. I don't mind it because this is my hobby. I am going through a to-do list until all I wanted works.
Currently, as the new version 3.3.0.14 is out) I am working on to update my port to 3.3.0.14. Unfortunately currently there is no OTA but hope eventually it will be sorted.
Changing the pixel ratio is not essential as the default 1.0 is ok-ish. I have found the 0.82 better so I included the icons into my image. As the script (kimmoli-diyicons.sh) is also included, we just need to run one command as root. I may try to set the 0.82 out of the box but currently it is not my to priority. As I will need to re-build everything for 3.3.0.14, I will try to set 0.82 in the pattern file.
Please keep me posted with your progress.
edp17 said:
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
Click to expand...
Click to collapse
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Galaxyninja66 said:
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Click to expand...
Click to collapse
I remember that I built gstreamer and un-commented the related stuff in the pattern file. I don't know whether easier to build now because I don't know how difficult it was before. I only can compare this project against my hammerhead one a few months earlier. For the hammerhead I needed to build the image with MIC, now the rpm/dhd/helpers/build_packages.sh command does everything for you. (For this you need to export the RELEASE, EXTRA_NAME values in your .hadk.env)
Unfortunately I still don't have OBS account so I couldn't add this device into the wiki. Thank you for doing that! Unfortunately new account creation on the mer bug wiki is restricted at the moment.
I have checked the wiki you have added and if you don't mind I would like you to amend a few things:
LED works (the two softkeys have repurposed as notification leds)
GPS works
Sensors Gyro and Magnetometer both work
(I need to double check the RTC alarm and USB net.)
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Galaxyninja66 said:
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Click to expand...
Click to collapse
Thank you for the update and for the congrats but I think it is only partially my merits. I probably couldn't done this without the help of sailfishos-porter guys.
As I mentioned in the main comment, I am using my S2 with this image on it as a secondary phone already. Mobile data is not crucial as my main phone can be a hotspot and with my S2 I can connect to it via wifi. Of course this doesn't stop me trying to make that work. (The BT was almost done but I then broke something.)
The camera is a different story. Afaik the video recording generally is broken in the CM12.1 base that I chosen for this device. (That doesn't work on my hammerhead which is also using CM12.1 base.) So I think that will remain outstanding unless I try to port with a different android base.
I think will stop with this for while because the new version (3.3) is out soon and would like to upgrade to it first, then continue working on the missing bits.
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Galaxyninja66 said:
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Click to expand...
Click to collapse
I think the video recording also works in cm12.1 on the android side, but the problem is a, between the android and Sailfish or b, on the Sailfish side. I am not sure but when I tried to fix it on the hammerhead (same cm12.1 base) I was told the recording was broken in general with cm12.1 base. I'll see how it works (what I can do about it) after Sailfish 3.3 is out.
Have you thought about to purchase a cheap android phone to use as daily driver and using the i9100m for your Sailfish project? (You probably can get a decent second hand android phone for sub 20 maybe with better spec than the i900.)
Thanks again for the kind words. This phone (the S2) is my favorite old friend. It is indestructible . I have soft bricked so many times and managed to install many other OS but as couldn't find Sailfish OS, so I though worth a try to port. And with support of the Sailfishos-porters guys, my dream became real :good: .
Sailfish
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I am glad you managed to install it. Have you tried to re-partition the internal memory as I advised?
Yeah, the bt and mobile data is still WIP status. Hopefully will have some time to complete them soon.
For the browser, the native one doesn't hang for me. You can try to look for and install one from the openrepos. (I suggest to install the Storeman as you will find more useful apps for Sailfish OS.)
I don't know linusdan but have seen he has checked this post already. Hope he also found it useful.
I am aware of the postmarketos for the S2 and tested it on my S2. At that time (about a year ago) there was no mainline linux kernel option for the S2. Unfortunately the mainline kernel doesn't help with Sailfish because the Samsung proprietary blobs are missing from there. This means Sailfish wouldn't work. It needs the drivers from the Android layer.
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I forgot to mention that there should be a folder '/edp17packages/bluetooth' where you can find the missing packages for the bt. Once you installed it, probably only need to tweak some config files and need to create some scripts. I currently started working on it.
Enable 5G and DSS on OnePlus 8T
As you may or may not know OnePlus didn't add proper changes into EFS configs to allow us use 5G on every network in the world. This guide will help you unlock 5G access and DSS (Dynamic Spectrum Sharing) and doesn't require root access until you don't want to access 5G in SA (standalone) mode.
I'm NOT responsible to any damage you make to your phone. There's barely any chance to damage anything, but you've been warned.
Requirements:
EngineerMode apk installed on your phone.
USB Debugging enabled on your phone.
OnePlus drivers installed on your desktop.
QPST app installed on your desktop.
Qualcomm diagnostic drivers.
Downloads:
EngineerMode apk: ApkMirror
QPST app: Mediafire
Qualcomm drivers & my configs: GDrive
Instruction #1 - enable 5G:
On your phone, dial *#801# > use EngineerMode > enable Engineer Mode Toggle (ON) and connect your device to your Desktop via USB.
On your Desktop, open Device Manager. You should see two new 'other devices'. Update their drivers by: right click > Update Driver > Browse my computer [...] > Let me pick [...] > All devices > then browse for Qualcom diagnostic drivers you've downloaded & use qcmdm.inf > choose something called 'Android Modem 9018'.
Open QPST. You should see devices in Active Phones and Ports list. If not: Add new port > add two devices shown in the list. Then: Start Clients > QPST EFS Explorer and select SDX55 device. This may take a few seconds.
Once you see EFS Explorer go to /policyman, then copy to a separate folder following files as a backup: carrier_policy.xml, carrier_policy.xml_Subscription01.
Delete those 2 files from the EFS Explorer. Find my corresponding configs and copy them over to the /policyman.
On your phone, disable Engineer Mode Toggle, disconnect from your PC and reboot.
Once booted, dial *#*#4636#*#* > Phone Information > Set preferred network type to NR/LTE/TDSCDMA/GSM/WCDMA. Now you should have 5G NSA enabled.
* To enable (force) 5G SA, you have to use Network Signal Guru app to change NR5G Mode from NSA to NSA/SA or SA. But this will require root access.
You can make sure everything is working correctly by using CellMapper app and checking 5G Status. RESTRICTED means your plan doesn't allow you to use 5G, NOT_RESTRICTED means you are too far from the cell, try to move closer, CONNECTED means everything is working perfectly. However, this method isn't ideal - every software update or SIM card change you will loose all modifications.
Instruction #2 - enable DSS:
Dynamic spectrum sharing (DSS) provides a very useful migration path from LTE to NR by allowing LTE and NR to share the same carrier.
Follow 1st and 3rd step from Instruction #1.
Once you see EFS Explorer go to /policyman and copy lte_feature_restrictions.xml file to your computer - we're going to edit it, so make a backup somewhere.
Open the file with a text editor of your choice.
You should see a section like this:
XML:
<plmn_list name="dss_plmns" ns="global">
228-01 505-01 505-11 505-39 505-71 505-72 204-04 262-01 262-06 204-16 204-20 232-03 232-07 204-04 311-480 240-02 238-06 240-01 206-01 204-08 204-12 204-18 204-69 238-01 238-10
</plmn_list>
These are the networks allowed to use DSS. Now you should go to MCC-MNC and find a proper mcc-mnc
codes for your network. Add them to the file as shown above.
Now you should find section looking like this:
XML:
<lte_feature name="NR_DSS">
<all_of>
<boolean_test name="carrier:dss_is_enabled" />
<serving_plmn_in list="dss_plmns" />
</all_of>
</lte_feature>
And change it to this:
XML:
<lte_feature name="NR_DSS">
<any_of>
<boolean_test name="carrier:dss_is_enabled" />
<serving_plmn_in list="dss_plmns" />
</any_of>
</lte_feature>
All you have to do now is to save the file, copy it over to the /policyman in the EFS Explorer and copy step 6. and 7. from Instruction #1. And that's it!
Remember: OP8T from different regions with support of the same 5G bands would sometimes not work in the NSA mode in your carrier network because of different ENDC combos and different LTE anchors. Check if your device would support your carrier network at cacombos.com.
More on how to properly edit carrier plicy files at MT-TECH Blog. Guide tested on KB2003: Play/P4, KB2007: T-Mobile and KB2005: Verizon.
Special thanks to:
Mr. Minh Truong
Mr. Abdullah Alshehri
Evenshop Themobilestore
Can you verify the driver model to install in step 2? The lowest number "MDM Diagnostics" model is 9031.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've found other diagnostic drivers with the "9018" in them, but they don't say MDM.
jefffeely said:
Can you verify the driver model to install in step 2? The lowest number "MDM Diagnostics" model is 9031.
View attachment 5165055
I've found other diagnostic drivers with the "9018" in them, but they don't say MDM.
View attachment 5165057
Click to expand...
Click to collapse
You should use qcmdm.inf and then browse for 'Qualcomm Android Modem 9018' (it should be right on top of the list). I will add this to the main post. Sorry, my bad
bemolx said:
You should use qcmdm.inf and then browse for 'Qualcomm Android Modem 9018' (it should be right on top of the list). I will add this to the main post. Sorry, my bad
Click to expand...
Click to collapse
That fixed it, thanks!
Well I did all these steps and it made no difference for me. I still can't get 5g. I used to get it here and now I don't. I don't know if something changed on my phone or if a tower went down or what. The CellMapper app has zero 5g information in it for me, and I'm not paying $50 for the upgrade for Network Signal Guru to tell me more information. When I forced to 5G, I get absolutely nothing ):
When 5g was working it was only about 10mbps, and LTE is 100mbps, so it makes sense to stick with LTE for now. I was excited to be able to try out DSS though.
If nothing else, thanks for this guide. It was nice to get QPST up and running again. It had been a long time since I used it.
jefffeely said:
Well I did all these steps and it made no difference for me. I still can't get 5g. I used to get it here and now I don't. I don't know if something changed on my phone or if a tower went down or what. The CellMapper app has zero 5g information in it for me, and I'm not paying $50 for the upgrade for Network Signal Guru to tell me more information. When I forced to 5G, I get absolutely nothing ):
When 5g was working it was only about 10mbps, and LTE is 100mbps, so it makes sense to stick with LTE for now. I was excited to be able to try out DSS though.
If nothing else, thanks for this guide. It was nice to get QPST up and running again. It had been a long time since I used it.
Click to expand...
Click to collapse
I saw you have KB2007 so you must be in the different region. If it got worse (no 5G at all) I suggest sticking to the MT-TECH.FI blog and trying to modify carrier policy files the way Mr Minh did.
The first time I was trying to get 5G working I used many guides with many configs but none of them worked. So I followed his instruction.
It seems like every model may have different configs. I'm sorry it didn't work for you
bemolx said:
I saw you have KB2007 so you must be in the different region. If it got worse (no 5G at all) I suggest sticking to the MT-TECH.FI blog and trying to modify carrier policy files the way Mr Minh did.
The first time I was trying to get 5G working I used many guides with many configs but none of them worked. So I followed his instruction.
It seems like every model may have different configs. I'm sorry it didn't work for you
Click to expand...
Click to collapse
Sorry I wasn't clear, your guide didn't make things worse. I stopped receiving 5g at my house a couple weeks ago. I was just hoping your guide would bring it back.
In fact, I drove over to a tower today to test out your configuration. Worked great there!
jefffeely said:
Sorry I wasn't clear, your guide didn't make things worse. I stopped receiving 5g at my house a couple weeks ago. I was just hoping your guide would bring it back.
In fact, I drove over to a tower today to test out your configuration. Worked great there!View attachment 5165877
Click to expand...
Click to collapse
Ah I see. Good to see it's working.
Maybe the carrier operator decided to move the cell away or upgrade it in the near future at you home place if it was such bad at performance. Who knows
bemolx said:
Ah I see. Good to see it's working.
Maybe the carrier operator decided to move the cell away or upgrade it in the near future at you home place if it was such bad at performance. Who knows
Click to expand...
Click to collapse
I just flashed back to T-mobile's 011.0.1.3.KB09CB and 5g is back at my house, just only 5mbps lol. I am now suspecting that they changed the modem for 11.0.4.6 so that it would only switch to 5g if it had a stronger signal.
jefffeely said:
I just flashed back to T-mobile's 011.0.1.3.KB09CB and 5g is back at my house, just only 5mbps lol. I am now suspecting that they changed the modem for 11.0.4.6 so that it would only switch to 5g if it had a stronger signal.
Click to expand...
Click to collapse
Can you extract and post here carrier policy files while you're on 11.0.1.3? I'm curious to see how do they look like.
bemolx said:
Can you extract and post here carrier policy files while you're on 11.0.1.3? I'm curious to see how do they look like.
Click to expand...
Click to collapse
Here's the whole folder. I had already pulled it to compare lol.
I am on tmo using the 8t purchased at a tmo. Do i need this? I am on global rom.
kevkid said:
I am on tmo using the 8t purchased at a tmo. Do i need this? I am on global rom.
Click to expand...
Click to collapse
T-Mobile's configs are different than mine, however my configs also work just like @jefffeely posted here.
If you're lacking 5G connectivity you can try either my or jefffeely's configs. It really depends how the carrier has developed the 5G architecture around you.
Can you explain something for me?
I deleted the whole policyman folder, and there was no difference, the phone functions as if there was no problem at all, so what is going on guys?
even 5G and Volte is working well
Mod edit - translated by https://translate.google.com:
I tried to extract hydrogen files in China based on your method. I hope these XML can help you improve this operation.
The download address is
I tried to extract nitrogen files in China according to your method. Hope these XML can help you improve this operation. The download address is
**************************
我根据你的方法尝试提取了中国地区氢的文件，希望这些XML可以帮助您完善此操作。
下载地址是
我试图根据您的方法在中国提取氮气文件。希望这些XML可以帮助您改进此操作。下载地址是
chinabackup.rar
drive.google.com
Engineering Support said:
Can you explain something for me?
I deleted the whole policyman folder, and there was no difference, the phone functions as if there was no problem at all, so what is going on guys?
even 5G and Volte is working well
Click to expand...
Click to collapse
Interesting. I would like to know that as well. Was it still gone after reboot?
I also want to know what made you decide to delete the whole folder
I can confirm that this guide worked on Verizon in the U.S, at least on the n5 band. However, 5G speeds are still slower for me than 4G. While it may prove more useful in the future, I don't think 5G is mature enough to replace 4G just yet.
Engineering Support said:
Can you explain something for me?
I deleted the whole policyman folder, and there was no difference, the phone functions as if there was no problem at all, so what is going on guys?
even 5G and Volte is working well
Click to expand...
Click to collapse
That's kinda strange. I can't really tell what's going on, I wonder if you've rebooted your phone.
z9999xc said:
我根据你的方法尝试提取了中国地区氢的文件，希望这些XML可以帮助您完善此操作。
下载地址是
我试图根据您的方法在中国提取氮气文件。希望这些XML可以帮助您改进此操作。下载地址是
chinabackup.rar
drive.google.com
Click to expand...
Click to collapse
Thanks for sharing it! I'll review this in the morning.
parker.stephens said:
I can confirm that this guide worked on Verizon in the U.S, at least on the n5 band. However, 5G speeds are still slower for me than 4G. While it may prove more useful in the future, I don't think 5G is mature enough to replace 4G just yet.
Click to expand...
Click to collapse
It really depends how the 5G is developed at your location. I've tested NR NSA in different parts of a single city and sometimes it's worse than 4G too. As you said - not mature enough yet.
bemolx said:
Enable 5G and DSS on OnePlus 8T
As you may or may not know OnePlus didn't add proper changes into EFS configs to allow us use 5G on every network in the world. This guide will help you unlock 5G access and DSS (Dynamic Spectrum Sharing) and doesn't require root access until you don't want to access 5G in SA (standalone) mode.
I'm NOT responsible to any damage you make to your phone. There's barely any chance to damage anything, but you've been warned.
Requirements:
EngineerMode apk installed on your phone.
USB Debugging enabled on your phone.
OnePlus drivers installed on your desktop.
QPST app installed on your desktop.
Qualcomm diagnostic drivers.
Downloads:
EngineerMode apk: ApkMirror
QPST app: Mediafire
Qualcomm drivers & my configs: GDrive
Instruction #1 - enable 5G:
2. On your Desktop, open Device Manager. You should see two new 'other devices'. Update their drivers by: right click > Update Driver > Browse my computer [...] > Let me pick [...] > All devices > then browse for Qualcom diagnostic drivers you've downloaded & use qcmdm.inf > choose something called 'Android Modem 9018'.
Click to expand...
Click to collapse
Hi,
I am stucked in the 2nd step.
I have a KB2003 and I can't update the devices with the driver you provided.
It says that the drivers are not compatible with the device.
I can't go further.
Thanks for your help.
docles
docles said:
Hi,
I am stucked in the 2nd step.
I have a KB2003 and I can't update the devices with the driver you provided.
It says that the drivers are not compatible with the device.
I can't go further.
Thanks for your help.
docles
Click to expand...
Click to collapse
Have you tried disabling signature verification enforcement?
Are you sure you've enabled file transfer via USB?