Call for information on various Moto G models to help rom development - Moto G General

I need to collect some information from stock Moto G. All feedback is appreciated. This will allow me to make CM builds for various models/variants.
Model Number: (e.g XT1034)
The following need to be done either in adb shell or terminal application:
Code:
getprop ro.build.motfactory
getprop ro.hw.device
getprop ro.boot.fsg-id
getprop ro.mot.build.customerid
getpropro.hw.radio
Please just pase the results as a reply, and thanks a lot.

XT1032
Code:
ro.build.motfactory: prop not set
ro.hw.device: falcon
ro.boot.fsg-id: prop empty, but set
ro.mot.build.customerid: RTGB
ro.hw.radio: 0x1
EDIT: in case it matters, it's still running JB

pmzqla said:
XT1032
Code:
ro.build.motfactory: prop not set
ro.hw.device: falcon
ro.boot.fsg-id: prop empty, but set
ro.mot.build.customerid: RTGB
ro.hw.radio: 0x1
EDIT: in case it matters, it's still running JB
Click to expand...
Click to collapse
Thanks and no those are the same on 4.3 and 4.4

XT1032 Chile
Code:
ro.build.motfactory: prop not set
ro.hw.device: falcon
ro.boot.fsg-id: prop empty, but set
ro.mot.build.customerid: AMXCL
ro.hw.radio: 0x1

XT 1033 from Brazil, Retail model.
Code:
ro.build.motfactory: empty
ro.hw.device: falcon
ro.boot.fsg-id: empty
ro.mot.build.customerid: RETBR
ro.hw.radio: 0x5

vbdss said:
XT 1033 from Brazil, Retail model.
Code:
ro.build.motfactory: empty
ro.hw.device: falcon
ro.boot.fsg-id: empty
ro.mot.build.customerid: RETBR
ro.hw.radio: 0x5
Click to expand...
Click to collapse
XT1033, remember, is a version with 16GB and dual-sim, and the only version with 16GB of internal memory being sold in Brazil.I suppose this is the Moto G version that will give more work. But we have some users willing to test. Including me.

XT1032 Global GSM 16GB KitKat
Code:
getprop ro.build.motfactory: empty
getprop ro.hw.device: falcon
getprop ro.boot.fsg-id: empty
getprop ro.mot.build.customerid: retusa_glb
getpropro.hw.radio: 0x1
You're welcome.

Code:
[email protected]:/ $ su
[email protected]:/ # getprop ro.build.motfactory
[email protected]:/ # getprop ro.hw.device
falcon
[email protected]:/ # getprop ro.boot.fsg-id
[email protected]:/ # getprop ro.mot.build.customerid
retusa_aws
[email protected]:/ # getpropro.hw.radio
This is from a UK Tesco 16gb

XT1033 (Brazilian, retail, 8GB, dual-sim, stock JB 4.3)
Code:
getprop ro.build.motfactory: [B]empty[/B]
getprop ro.hw.device: [B]falcon[/B]
getprop ro.boot.fsg-id: [B]empty[/B]
getprop ro.mot.build.customerid: [B]RETBR[/B]
getpropro.hw.radio: [B]0x5[/B]

XT1032 (UK 16GB) - how can I find that number with adb anyways?
Code:
getprop ro.build.motfactory: [B]empty line[/B]
getprop ro.hw.device: [B]falcon[/B]
getprop ro.boot.fsg-id: [B]empty line[/B]
getprop ro.mot.build.customerid: [B]RTGB[/B]
getprop ro.hw.radio: [B]0x1[/B]

XT1034 US 16GB
In order....
empty
falcon
empty
retusa_aws
0x6
Sent from my XT1034 using XDA Premium 4 mobile app

US - Verizon - CDMA
Code:
[email protected]_cdma:/ $ getprop ro.build.motfactory
getprop ro.build.motfactory
[email protected]_cdma:/ $ getprop ro.hw.device
getprop ro.hw.device
falcon
[email protected]_cdma:/ $ getprop ro.boot.fsg-id
getprop ro.boot.fsg-id
[email protected]_cdma:/ $ getprop ro.mot.build.customerid
getprop ro.mot.build.customerid
verizon
[email protected]_cdma:/ $ getprop ro.hw.radio
getprop ro.hw.radio
0x3

XT1032 (Movistar Chile)
ro.build.motfactory: empty
ro.hw.device: falcon
ro.boot.fsg-id: empty
ro.mot.build.customerid: TEFCL
ro.hw.radio: 0x1

azangerle said:
US - Verizon - CDMA
Code:
[email protected]_cdma:/ $ getprop ro.build.motfactory
getprop ro.build.motfactory
[email protected]_cdma:/ $ getprop ro.hw.device
getprop ro.hw.device
falcon
[email protected]_cdma:/ $ getprop ro.boot.fsg-id
getprop ro.boot.fsg-id
[email protected]_cdma:/ $ getprop ro.mot.build.customerid
getprop ro.mot.build.customerid
verizon
[email protected]_cdma:/ $ getprop ro.hw.radio
getprop ro.hw.radio
0x3
Click to expand...
Click to collapse
Can you post the build.prop for the verizon model please?

Code:
[email protected]_cdma:/ $ getprop build.prop
getprop build.prop
it doesnt return anything, but honestly i may be messing something up. I will help in anyway i can.

azangerle said:
Code:
[email protected]_cdma:/ $ getprop build.prop
getprop build.prop
it doesnt return anything, but honestly i may be messing something up. I will help in anyway i can.
Click to expand...
Click to collapse
NO I just mean to upload /system/build.prop as an attachment please

dhacker29 said:
NO I just mean to upload /system/build.prop as an attachment please
Click to expand...
Click to collapse
Here it is.

azangerle said:
Here it is.
Click to expand...
Click to collapse
Thanks and the caps was an accident didn't mean to shout lol

I get getprob command not found :/

cra1g321 said:
I get getprob command not found :/
Click to expand...
Click to collapse
it should be getprop and you might have to be root to do it

Related

[WIP] Unlock LTE Bands (TW/CN to WW)

{
"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"
}
Caution: I'm not responsible for any damage that can occur trying my methods in your devices. Just proceed if you're an advanced user and conscious about what I'm doing here. Read this again. And again.
Hello. I've been searching a lot about this and after searching in lots of russian/chinese forums I've found that inside boot.img there is a config_init.sh file that loads phone's configuration depending on the phone's SKUID and many other parameters:
Attempt #1 - Change config_init.sh file
Code:
# software configuration related boot actions
#please sync to RF BAND
FULL_BAND=8
WW_BAND=0
TW_BAND=1
CN_BAND=2
US_BAND=3
TR_BAND=4
TEST_BAND=12
# ZX550ML RF BAND
WW_US_BAND=15
TW_CN_JP_BAND=0
WW_TEST_BAND=1
TW_TEST_BAND=8
# project ID
ZE550ML=23
ZE551ML=31
ZR550ML=28
ZX550ML=27
ZE551ML_CKD=30
RFSKUID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/rf_sku_id)
PROJID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/project_id)
COUNTRY_CODE=$(cat /factory/PhoneInfodisk/country_code)
log -p i -t config_init "PROJID: $PROJID_DETECT ,RFSKUID: $RFSKUID_DETECT"
if [ -n "$PROJID_DETECT" ]; then
case $PROJID_DETECT in
"$ZE550ML" | "$ZE551ML" | "$ZE551ML_CKD")
if [ "$COUNTRY_CODE" = "TH" ]; then
echo "V1_DSDA_ZE550ML_TH" > /config/local_config
elif [ -n "$RFSKUID_DETECT" ]; then
case $RFSKUID_DETECT in
"$FULL_BAND")
echo "V1_DSDA_ZE550ML_FULL" > /config/local_config
;;
"$WW_BAND")
echo "V1_DSDA_ZE550ML_WW" > /config/local_config
;;
"$TW_BAND")
echo "V1_DSDA_ZE550ML_TW" > /config/local_config
;;
"$CN_BAND")
echo "V1_DSDA_ZE550ML_CN" > /config/local_config
;;
"$US_BAND")
echo "V1_DSDA_ZE550ML_US" > /config/local_config
;;
"$TR_BAND")
echo "V1_DSDA_ZE550ML_TR" > /config/local_config
;;
"$TEST_BAND")
echo "V1_DSDA_ZE550ML_TEST" > /config/local_config
;;
*)
echo "V1_DSDA" > /config/local_config
;;
esac
else
echo "V1_DSDA" > /config/local_config
fi
;;
"$ZX550ML")
if [ -n "$RFSKUID_DETECT" ]; then
case $RFSKUID_DETECT in
"$WW_US_BAND")
echo "V1_SINGLE_ZX550ML_WW" > /config/local_config
;;
"$TW_CN_JP_BAND")
echo "V1_SINGLE_ZX550ML_WW" > /config/local_config
;;
"$WW_TEST_BAND")
echo "V1_SINGLE_ZX550ML_WW" > /config/local_config
;;
"$TW_TEST_BAND")
echo "V1_SINGLE_ZX550ML_WW" > /config/local_config
;;
*)
echo "V1_SINGLE_ZX550ML" > /config/local_config
;;
esac
else
echo "V1_SINGLE_ZX550ML" > /config/local_config
fi
;;
*)
echo "V1_DSDA" > /config/local_config
;;
esac
else
echo "V1_DSDA" > /config/local_config
fi
CONFIG_PATH=/local_cfg
PROPS_FILE=init.props
# Get selected software configuration
config=`cat /config/local_config`
mount -o bind /system/etc/catalog/$config /local_cfg
log -p i -t config_init "Activating configuration $config"
# Set properties for the selected configuration
# read all FeatureTeam's init.props file
for f in /local_cfg/*/init.props
do
while read l; do
# Ignore empty lines and comments
case "$l" in
''|'#'*)
continue
;;
esac
# Set property
setprop `echo ${l/=/ }`
done < $f
done
Based on this I expect we can change it in a way we can load WW information and so unlock LTE bands.
Code:
Update #1
#RFSKUID_DETECT=$(cat /sys/module/intel_mid_sfi/parameters/rf_sku_id)
RFSKUID_DETECT=$WW_BAND # this will set RFSKUID_DETECT=0
Changelog:
Update #1: Without changing RFSKUID it will load configuration as if it was WW version;
Attempt #2 - Change XML files
Code:
Change this file content /system/etc/catalog/V1_DSDA_ZE550ML_CN/telephony_config/V1_DSDA_ZE550ML_CN_726x.xml
In line where is mentioned (4g_active_bands) change bands to the wanted bands, as well as in the next 3 lines. Below there are 2 images to help you.
V1_DSDA_ZE550ML_WW_726x.xml example
V1_DSDA_ZE550ML_CN_726x.xml example
Changelog:
Update #1: Change 4G bands in XML file;
In order to unpack/repack boot.img you can use this great tool: http://forum.xda-developers.com/showthread.php?t=2319018
As my Zenfone 2 (CN) didn't arrive yet I cannot start testing this yet.
I expect you to help me discussing about this and replying with your opinions, if this is or not a good way or something else..
Best wishes
João Ramos
Reserved
hello ! !
I am also wainting for my zenfones to arrive (i bought 3) ! !
If i can help with something after just ask ! ! Lest hope there is a method to unlock some LTE bands, as we now LTE Band 20 (800Mhz) is one of the most important to us ! !
PS: i am form Portugal too
x4nick8r said:
hello ! !
I am also wainting for my zenfones to arrive (i bought 3) ! !
If i can help with something after just ask ! ! Lest hope there is a method to unlock some LTE bands, as we now LTE Band 20 (800Mhz) is one of the most important to us ! !
PS: i am form Portugal too
Click to expand...
Click to collapse
Hi there.
For now I really believe this method is reliable, as it will load WW configuration files.. if there are no hardware differences between WW and CN versions (which I believe share the same modem -> Intel 7262) it will work I guess :good:
Here in Portugal for example Vodafone uses 800MHz, 1800MHz and 2600MHz. As far as we have 1800MHz I don't know if we'll have some LTE signal.. we'll have to wait to see! Thanks for your support
FYI, what this does is build local config directory which further allow to load the files specific to WW or CN etc.I tried once to copy WW files to CN but no change in band support.
Have you still got radio working? I read here in XDA that there could be a kind of mechanism to sign files and so the file won't be loaded.. This way we don't touch .xml files. Have you tried this method?
Hi, im from Portugal too and have zenfone2 since July, and this is very interesting for me, but i wouldnt know to where to start to test it since im not very expert in this matters...
But i hope it works..
Let me see if i get it. I need to unpack boot.img, replace config file in it, pack it back up and flash it to get this tested?
If so, that did not work, still getting H+ only and code 2 in /sys/module/intel_mid_sfi/parameters/rf_sku_id
I have 551ML, WW version and I need Band 38 (LTE TD 2600 MHz) to use it in my country (Romania). How can I enable it?
Trimis de pe dispozitivul meu Asus ZenFone 2
bravas said:
I have 551ML, WW version and I need Band 38 (LTE TD 2600 MHz) to use it in my country (Romania). How can I enable it?
Trimis de pe dispozitivul meu Asus ZenFone 2
Click to expand...
Click to collapse
We are working in it [emoji16]
Enviado desde mi ASUS_Z00AD mediante Tapatalk
Intel 7262 + Intel 2230 suports all LTE Frequencies on-Chip, the load of modem radio fw is prior to the boot rom of the phone.
i'm guessing with some work, with a FULLdump of a WW version of zenfone 2 (modem radio / baseband) it will be possible to enable the needed frequencies.
As far as i know ther is NO limitation in hardware in this device.
DiGecko said:
Let me see if i get it. I need to unpack boot.img, replace config file in it, pack it back up and flash it to get this tested?
If so, that did not work, still getting H+ only and code 2 in /sys/module/intel_mid_sfi/parameters/rf_sku_id
Click to expand...
Click to collapse
It's normal to get code 2 in that file. Here we aren't changing that file, just changing the code that this script will load on boot. Have you tried to change the XML file which loads the corresponding file (WW, CN or TW)?
Thanks
x4nick8r said:
Intel 7262 + Intel 2230 suports all LTE Frequencies on-Chip, the load of modem radio fw is prior to the boot rom of the phone.
i'm guessing with some work, with a FULLdump of a WW version of zenfone 2 (modem radio / baseband) it will be possible to enable the needed frequencies.
As far as i know ther is NO limitation in hardware in this device.
Click to expand...
Click to collapse
These are great news. Since there are no hardware differences we're able to unlock all frequencies. So we'll need to find where the modem radio fw is loaded..
BTW, only Intel 7262 supports LTE. Intel 2230 is the modem for the second SIM-Slot.
jopframos said:
These are great news. Since there are no hardware differences we're able to unlock all frequencies. So we'll need to find where the modem radio fw is loaded..
BTW, only Intel 7262 supports LTE. Intel 2230 is the modem for the second SIM-Slot.
Click to expand...
Click to collapse
From Intel papers
The Intel® XMM™ 7262 modem shares the same platform as the Intel® XMM™ 7260 modem, which is now shipping commercially to customers including Samsung.
Delivering category 6 speeds of up to 300 Mbps, the Intel® XMM™ 7262 supports LTE TDD/FDD, WCDMA/HSPA+ and TD-SCDMA, TD-HSPA, and EDGE standards for world markets. The Intel XMM 7262 offers China and the global TD-LTE ecosystem a new cost-effective option for developing mass-market LTE devices. The XMM 7262 modem features:
Global mobility:
o Up to 23 LTE bands on a single SKU for worldwide coverage and roaming
o Multimode design provides seamless connectivity to 2G, 3G and 4G LTE networks.
o Powerful and flexible RF architecture to enable roaming solutions for a world phone market impact.
Carrier Aggregation up to 40 MHz combined bandwidth on a single RF transceiver
High quality, low-power connectivity and voice calling:
o Intel’s second-generation envelope tracking and antenna tuning minimizes power consumption, preserving battery life.
o Power-efficient voice calling over LTE (VoLTE)
Small footprint: Minimized PCB size enables attractive form factors across a range of products, from smartphones and tablets to M2M and connected devices.
We’re proud of our progress and there is more to come. By the end of 2014, we expect to see devices based on the Intel® XMM™ 726x platform available in Australia, China, Europe, Latin America, North America, South Korea and other regions. Onward!
More information on Intel XMM 726x platform is available here.
Visit www.intel.com/mobileto see Intel’s entire portfolio of device, connectivity and network solutions for mobile computing.
Click to expand...
Click to collapse
It will be a matter of time, seek and experiment to unleash the full lte bands.
First thing is to know how and when baseband files are loaded on the phone. Maybe this is firmware related...
So my phone was originally CN, but I changed sku to WW and running latest WW firmware with boot image and all. I have it rooted and have unlocked bootloader with TWRP, so testing things is easy. I changed the file that you modified and repacked and flashed boot.img with no results. If you have anything else to try - let me know.
I used this method to change to WW and got my boot.img and droidboot.img from here. in latest 139 firmware. Whats interesting is even though the phone is running WW firmware and thinks it's on WW sku for OTA, it still loads as CN for the radios.
x4nick8r said:
From Intel papers
It will be a matter of time, seek and experiment to unleash the full lte bands.
First thing is to know how and when baseband files are loaded on the phone. Maybe this is firmware related...
Click to expand...
Click to collapse
I was just wondering that there could be differences in the Asus motherboard or something else...
You have an error in script, because it loads ZX551 settings.
Also there is no sense to work with ramdisk image, because LTE is locked in modem FW, which flashes according to parameters flashed at factory.
The only way to change it is to somehow modify ifwi image.
Right now i have flashed WW version with WW modem at CN phone and WW bands are still not working (even if i manually select 'em with AT commands).
I did it by modifying /factory/PhoneInfodisk/country_code file content to "TH".
Justere said:
You have an error in script, because it loads ZX551 settings.
Also there is no sense to work with ramdisk image, because LTE is locked in modem FW, which flashes according to parameters flashed at factory.
The only way to change it is to somehow modify ifwi image.
Right now i have flashed WW version with WW modem at CN phone and WW bands are still not working (even if i manually select 'em with AT commands).
I did it by modifying /factory/PhoneInfodisk/country_code file content to "TH".
Click to expand...
Click to collapse
I didn't edit the PROJID_DETEC variable. Why do you say that?
You should also modify the / sys / module / intel_mid_sfi / parameters / rf_sku_id file too.. Have you tried it?
This won't change anything, I have flashed WW boot.IMG ,droidboot.IMG and recovery.IMG on my CN zenfone 2 and the bands didn't work so I returned back to stock CN.
If boot.img was responsible for the bands then they should have worked when I had the WW boot.img.
jopframos said:
I didn't edit the PROJID_DETEC variable. Why do you say that?
You should also modify the / sys / module / intel_mid_sfi / parameters / rf_sku_id file too.. Have you tried it?
Click to expand...
Click to collapse
WW_US_BAND is for ZX550 model, not for ZE551.
To modify rf_sku_id file we neet to modify kernel sources, recompile and flash it.
As i wrote few month ago:
LTE bands depends on RF_SKU_ID value.
In kernel sources RF_SKU_ID is defined based on "zenfone2.MR7.1-2.18.40\linux\kernel\arch\x86\platform\intel-mid\intel_mid_sfi.c" file.
Possibly, if we change it to static WW value "0", then LTE bands may become available.
Click to expand...
Click to collapse

Hidden service menu for LG G4 Marshmallow version

It seems if you are fortunate enough to have MM on board, this is the new code
*#546368#*xxx#
Note- Substitute xxx with your 3 digit model #
EX: 815 so I use *#546368#*815#
Already covered: http://forum.xda-developers.com/g4/help/how-to-enter-g4-hidden-menu-t3122373/post64142393
Already posted, see above.
Thread closed!
Forum moderator,
matt4321

[CAB] Lumia 640 XL Dual SIM RM-1067 IN Firmware Packages.

Model info
Phone model: Lumia 640 XL Dual SIM
PackageTitle: RM-1067 VAR IMEA IN CV
Product Code: 059X1J0
manufacturerHardwareModel: RM-1067
Firmware: 02177.00000.15184.36002
OS Version: 8.10.15148.160
Windows Phone 8.1 GDR Update 2 - Blue Firmware Packages.
http://pastebin.com/z6WXycm4
Change platform id
Can these cab files be used to change platform id via iutool ?
Specifically these 3 .
nokia.soc_qc8x26_16k.phone.efiesp.spkg_4314309fd585ba286797180af8d82a649a01f793.cab
nokia.device_makepeace_hspa_row_dsds.phone.efiesp.spkg_6a4a8c60031afca7b63e1f119ec526dbc0b6efba.cab
nokia.base.variant.efiesp.spkg_88d9d7c6e53256c7a312c43cb8f2b2c7bda20096.cab
Others who have done it on other models have the word plat instead of efiesp in the file name . Does that refer to the plat partition for rm 1067 ? Let me try this myself.
If it works you have no idea how many rm 1067 lost souls would have come across this post and missed the hidden treasure

Did anyone lose cat 12 (carrier aggregation) option with B581 ?

Did anyone lose cat 12 (carrier aggregation) option with B581 ?
b581 despite this runs good..but.. yeah cat 12 is important.
Yes I did. CA is not working as it should.

New Zealand 2degrees Product code

Hey guys and girls, I need someone that has an S10 plus or even maybe just an S10 from New Zealand that bought their phone from 2degrees.
I just after the product code, very simple to retrieve, root is needed.
It's just a product code that is set for all phones and is the same as all the rest, so nothing related to device id or anything similar.
It can be retrieved with terminal or file explorer.
Code:
su -c cat /efs/imei/prodcode.dat
Big thanks to you if you can, cheers!
*bump

Categories

Resources