So as you already know the KitKat update started rolling for our beloved Moto G - but sadly for the moment only for those with the US Global / US GSM firmwares.
So first thing first you need to do is UNLOCK THE BOOTLOADER (guide here) and download the following files:
Drivers: http://d-h.st/5j0 or install Motorola Device Manager
Firmware: http://sbf.droid-developers.org/download.php?device=14&file=127 (US Global) or http://sbf.droid-developers.org/download.php?device=14&file=121 (US GSM aka for T-Mobile aka for AWS networks)
Minimal ADB & Fastboot: https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
mfastboot: http://dc342.4shared.com/download/i...&dsid=3oh7jy.ce197763503e738750fd87149655184b
1. Enable USB Debugging on the device and Install the drivers accordingly to the OS version you have - either x86 for 32bits or x64 for 64bits
2. Install Minimal ADB and Fastboot
3. Extract mfastboot.exe to the folder where you installed Minimal ADB and Fastboot
4. Now in the same folder where you installed Minimal ADB and Fastboot extract files from the firmware folder.
5. Start Minimal ADB and Fastboot using shortcut created or py_cmd.exe
6. Connect the device via USB cable and in the cmd window that opens type
Code:
adb reboot-bootloader
7. Your device should reboot in Bootloader now.
8. While in Bootloader paste the following lines one by one, and be sure you get an OKAY after each one (some bootloader errors may appear, ignore them)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
9. You should now be rebooted in the official US firmware.
10. Wait for the OTA update to come OR flash the official OTA update.zip - US Global is here (thanks to @ZealotRush) and US AWS is here (thanks to @antiquezip) OR if you are rooted and with CWM you can flash the REPACK 4.4 KitKat system here (thanks to @josalaito)
my first guide, hopes everything goes well. I would love some feedback from those who tries this - as it worked perfect for me
Did mobile data still work after you flashed it ? Did you leave the UK radio
Sent from my XT1032 using Tapatalk
I had to unlock the bootloader of my Telcel Moto G to flash the US Retail, with the locked bootloader doesn't let me flash the boot and the system files...
kyler084 said:
Did mobile data still work after you flashed it ? Did you leave the UK radio
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yes, my data connection works.
My device is a retail.de version.
joel_sinbad said:
I had to unlock the bootloader of my Telcel Moto G to flash the US Retail, with the locked bootloader doesn't let me flash the boot and the system files...
Click to expand...
Click to collapse
But did it worked? Si funciona con el bootloader desbloqueado?
Sent from my XT1032 using Tapatalk
thanks for the guide, did work like a charm on my European retail model. everything works perfectly, including FM-radio.
No OTA update yet, but the FW change worked.
Do you really need to unlock the bootloader?
xmattjus said:
If you want to change it back to default (in my case retail-uk) we just need to flash with the same process the previous firmware, right?
Click to expand...
Click to collapse
Even easier, as the European firmwares I tested all have a flash.bat that flash all the things automatically - you just need to reboot in bootloader and double-click a file in Windows
If i flash the us gsm firmware on the global us model will i get the other bands
Kfire21 said:
If i flash the us gsm firmware on the global us model will i get the other bands
Click to expand...
Click to collapse
US firmware presumably has the same config as the European ones. However, after flashing I can't get HSPA+ but only 3G.
darkeingel said:
US firmware presumably has the same config as the European ones. However, after flashing I can't get HSPA+ but only 3G.
Click to expand...
Click to collapse
But would it then work on T mobiles network aws 1700/2100
Kfire21 said:
But would it then work on T mobiles network aws 1700/2100
Click to expand...
Click to collapse
Theres an AWS retail firmware linked in the guide too, especially for T-Mobile
darkeingel said:
Theres an AWS retail firmware linked in the guide too, especially for T-Mobile
Click to expand...
Click to collapse
So you're saying if have the global gsm version and flash the t mobile firmware from the post, I can then use it on T-mobiles aws network
Kfire21 said:
If i flash the us gsm firmware on the global us model will i get the other bands
Click to expand...
Click to collapse
No you can't do that the phones have different model numbers.
Kfire21 said:
So you're saying if have the global gsm version and flash the t mobile firmware from the post, I can then use it on T-mobiles aws network
Click to expand...
Click to collapse
I can't confirm that, as I didn't try but it should be working.
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
darkeingel said:
I can't confirm that, as I didn't try but it should be working.
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
Click to expand...
Click to collapse
Someone test it out please, that would be fantastic if it works.
Can I do this in a Telcel(Mexico) motorola g?, Someone in Canada that already did this? (telus, bell bla bla bands are compatible with Mexico)
Thunderwrath said:
Can I do this in a Telcel(Mexico) motorola g?, Someone in Canada that already did this? (telus, bell bla bla bands are compatible with Mexico)
Click to expand...
Click to collapse
I can confirm this working on a Telcel Mexico Moto G
frijolito18 said:
I can confirm this working on a Telcel Mexico Moto G
Click to expand...
Click to collapse
Did you have to unlock the bootloader?
darkeingel said:
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
Click to expand...
Click to collapse
I think it should work on all the Single sim Moto Gs (Carrier locked too) since hardware is the same al across (including bands)
Related
Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Rusty! said:
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Click to expand...
Click to collapse
Any chance for a step by step? And is this a confirmed working method?
Ydnaroo said:
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Click to expand...
Click to collapse
No. Sideload is for OTA updates. Completely different scenario.
Rusty! said:
No. Sideload is for OTA updates. Completely different scenario.
Click to expand...
Click to collapse
Ah! Of course. Brain fade here.
failed system.img when flashing unbranded stock
I have attempted to flash the stock unbranded firmware but am having no succes
The fastboot instructions given by Motorola website are as follows:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
Click to expand...
Click to collapse
Although I'm guessing that may be for the motox as the .xml included in the MotoG zip is as follows:
<?xml version="1.0"?>
-<flashing>-<header><phone_model model="QC8x26_CFC"/><software_version version="falcon_retgb-user 4.3 14.10.0Q3.X-76-LGG-8 54 release-keysMSM8626BP_1032.3051.51.00R"/><sparsing max-sparse-size="268435456" enabled="true"/>-<interfaces><interface name="AP"/></interfaces></header>-<steps interface="AP"><step MD5="173f47c2b411e291f8b0f512b8935190" filename="gpt.bin" partition="partition" operation="flash"/><step MD5="a2a1c181283543186f7ef069a9f63374" filename="motoboot.img" partition="motoboot" operation="flash"/><step MD5="187908e994f5b42710d13dbb5126d6d2" filename="logo.bin" partition="logo" operation="flash"/><step MD5="c99ebf47655a7609f10a8673ea229b72" filename="boot.img" partition="boot" operation="flash"/><step MD5="f79ca6436a8214fc7728dd927bd16898" filename="recovery.img" partition="recovery" operation="flash"/><step MD5="28ed691836a16e09be1edb7736086a49" filename="system.img_sparsechunk.0" partition="system" operation="flash"/><step MD5="9a188eb562f2abf336b66d1db53ab1f1" filename="system.img_sparsechunk.1" partition="system" operation="flash"/><step MD5="6a6ca5174610c48a855a7d16be75f948" filename="system.img_sparsechunk.2" partition="system" operation="flash"/><step MD5="b298426137783b6163fcda3621bed159" filename="NON-HLOS.bin" partition="modem" operation="flash"/><step partition="modemst1" operation="erase"/><step partition="modemst2" operation="erase"/><step MD5="73941708b28eb41f54b7c2326feec38a" filename="fsg.mbn" partition="fsg" operation="flash"/><step partition="cache" operation="erase"/><step partition="userdata" operation="erase"/></steps></flashing>
Click to expand...
Click to collapse
This seems to work via fastboot untill I get to the system.img files, they all fail when I try to flash them in order, or if I just try to flash one system.img as a whole.
I have also tried using the RSD tool, the phone is recognised when plugged in & booted up normally, after you select the .xml & click start it reboots to fastboot then can no longer see the device so the flash fails.
Unable to get the tool to see the phone if I manually reboot to fastboot first.
Any Ideas? Im guessing that manually flashing via fastboot is the only way, but cant get that 3 part system.img to install
>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
Click to expand...
Click to collapse
Have you gone through the bootloader unlock process?
Rusty! said:
Have you gone through the bootloader unlock process?
Click to expand...
Click to collapse
Yes by following the steps on the Motorola website.
I have that annoying white warning screen now every time I reboot
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Rusty! said:
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Click to expand...
Click to collapse
Yep, tried that the 1st time you posted it, still no luck.
I have noticed that after every reboot the usb debugging has switched itself off, could this be causing the permission problem?
Paul over at Modaco has created a root tool (says so on his twitter).
not sure if that will be any help in applying a stock Retrail rom on the Tesco phones. he also says RSD should work?
hope you guys can figure it out .
TeamKilo said:
Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
Click to expand...
Click to collapse
Where did you download it from?
he's in the process of uploading it. called Superboot?
The Jones said:
Where did you download it from?
Click to expand...
Click to collapse
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
seapoint said:
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
Click to expand...
Click to collapse
Code:
Motorola G (XT1032, XT1033)
Back
Size MD5 Carrier File
382.6 MiB 2E5FADFE1F8DE917AF0ABE6B9610AEC1 O2 Germany O2-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
398.7 MiB 18394D6F7268A9D489CFCFAE3B63E803 O2 Great Britain O2SL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB BD4BA4AE781BDB3DE20FD53D185E8C2C Retail Germany RETAIL-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
394.1 MiB DA99BD447878CDF35E7D2929E8E2A61E Retail French RETAIL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
397.9 MiB 2D45BDDDA22C46EF4C4023B78F9EE172 Retail British RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.zip
398.7 MiB 1B5988BD4CDB676E217F87891AB4667F Tesco Great Britain TESCOSL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB 12B83CD9B0F945C9D25881843AC50AC8 SFR France VODAFONE-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
396.7 MiB F69CE3807C2FEE310987F83144E8CABC SFR France VODAFONESL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_v2.xml.zip
409.2 MiB 9E782FA758557C526599F723E5A33F69 Claro Brazil fastboot_falcon_amxbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_43_release-keys-cid12-AmericaMovil_BR.tar.gz
409.1 MiB 3768338F742347A22DF8568B4B927449 Claro Brazil fastboot_falcon_amxbr_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-AmericaMovil_BR.tar.gz
403.4 MiB 1B4D1C455C16D2526D08D117B15C3EA6 Telcel Mexico fastboot_falcon_amxmx_user_4.3_14.10.0Q3.X-76-LCG-8-1_1_release-keys-cid12-AmericaMovil_MX.tar.gz
409.2 MiB AB46415C9D344B45F7954ADD834BC215 OI Brazil fastboot_falcon_oibr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_57_release-keys-cid12-Oi_BR.tar.gz
409.2 MiB 4C194E4FCBF508743EE7D5309281A0AE Retail Brazilian fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
409.1 MiB FA7B72E00EB3141E8B614C2022FBB9CB Retail Brazilian fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
396.6 MiB E8580CDCCB9E669D5CA1ECA8B6D4F9DF Movistar Chile fastboot_falcon_tefcl_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_CL.tar.gz
396.6 MiB 38BE1E4EAA8A938CE78DB7B2678B0481 Movistar Peru fastboot_falcon_tefpe_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_PE.tar.gz
We have 6.22 GiB of firmwares for Motorola Motorola G.
Actually, it seems the South American firmwares are pachaged , and named, differently. They're specifically labelled beginning with fastboot, and the archives let you expand to a directory giving you a single image for system.img The only one of interest to me is Brazil - I wonder will the Brazil system image work instead of the GB, FR or DE retail devices. If we get root I suppose we can edit build prop.
There has to be a way of concatenating the system images in the European retail images?
I wonder is this
jusumgeezer said:
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
Click to expand...
Click to collapse
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
The Jones said:
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
Click to expand...
Click to collapse
The Motorola version is in a "Windows" folder in the Brazil firmware download!
heres root http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Edit :Follow this thread for flashing http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Nice! Now we just need kernel source I believe then developers can get their hands dirty (well, after making a proper TWRP).
Hope so very soon
Thanks for the files.
@Devhux TWRP is already posted in original dev section.
Envoyé de mon XT1562 en utilisant Tapatalk
Fastboot Commands Full Path
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Fast link for xt1563 CA Default : https://mega.nz/#!qQZRDYAb!-W3iKudrm7xdxh2W6rdRSkDuc7142uP8zFRq8t2hPig
1st of all: thx for uploading!
secondly: the name of the original FW for the 1562 is called "XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip"
What about the "RETASIA" part, this kinda makes me wonder whether this might be intended for some kind of Asian version of the X. But I'm in Germany and also got the 1562. Will this work, regardless?
Best wishes derelektrischemoench
Which one of these is for the Wind variant XT1563?
noel_105 said:
Which one of these is for the Wind variant XT1563?
Click to expand...
Click to collapse
Flash the one i uploaded via mega works in all carriers,your in Canadian network right?
derelektrischemoench said:
1st of all: thx for uploading!
secondly: the name of the original FW for the 1562 is called "XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip"
What about the "RETASIA" part, this kinda makes me wonder whether this might be intended for some kind of Asian version of the X. But I'm in Germany and also got the 1562. Will this work, regardless?
Best wishes derelektrischemoench
Click to expand...
Click to collapse
im not 100 % sure if it will work
Hi @derelektrischemoench, I am based in France and got an X Play from retail and the original firmware does say RETASIA so I assume you should have no issue.
Full name is : 23.21.10.lux_retasia_ds.retasiaall.en.03 retfr
Build : LPD23.118-10
XMoDuLeSx said:
Flash the one i uploaded via mega works in all carriers,your in Canadian network right?
Click to expand...
Click to collapse
Thanks, yes Wind Mobile.
paugustin said:
Hi @derelektrischemoench, I am based in France and got an X Play from retail and the original firmware does say RETASIA so I assume you should have no issue.
Full name is : 23.21.10.lux_retasia_ds.retasiaall.en.03 retfr
Build : LPD23.118-10
Click to expand...
Click to collapse
Interesting, I've got my x play from retail as well here in Germany but mine says lux_reteu.reteu.en.EU reteu.
.... Whatever that means.
if you can help with stock firmware XT1563 DUAL SIM BRASIL, to with a rom stock not appear card slot !
amadeusmattos said:
if you can help with stock firmware XT1563 DUAL SIM BRASIL, to with a rom stock not appear card slot !
Click to expand...
Click to collapse
http://www.filefactory.com/file/5r5...D23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml.zip
reflash this one and if it does't work flash this :
http://www.filefactory.com/file/4bi...D23.118-6.1_cid12_subsidy-MOVSTLA_CFC.xml.zip
XMoDuLeSx said:
http://www.filefactory.com/file/5r5...D23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml.zip
reflash this one and if it does't work flash this :
http://www.filefactory.com/file/4bi...D23.118-6.1_cid12_subsidy-MOVSTLA_CFC.xml.zip
Click to expand...
Click to collapse
I tried and did not work! Does not work the slot! when I bought worked with the ORIGINAL STOCK ROM that came with unit , bought it in BRAZIL
can someone upload this to another place? i download at 24kbs from file factory.
Does anybody know why firmware for EU is missing? I guess I could use Asia one, but just in case I wanted to go back to stock.
I'm positive it was there before when thread was first posted. Maybe they were accidentally removed (just guessing)
Does anyone have a mirror for a XT1563 firmware ? Bandwith on FileFactory is horribly slow :/
vache said:
Does anyone have a mirror for a XT1563 firmware ? Bandwith on FileFactory is horribly slow :/
Click to expand...
Click to collapse
XMoDuLeSx said:
Fast link for xt1563 CA Default : https://mega.nz/#!qQZRDYAb!-W3iKudrm7xdxh2W6rdRSkDuc7142uP8zFRq8t2hPig
Click to expand...
Click to collapse
Was much faster for me. Filefactory was the worst download speed I've had since NetZero AOL dialup days.
The Eluga Switch software replaces the fsg partition to enable different LTE bands.
Mobile Q fails to replace it with a U.S. one so you get stuck with LTE band 1/3/7/etc.
Restoring LTE band 4 (from stock android 6.0.1):
1. Flash Eluga Switch to get fastboot back
2. fastboot flash fsg fsg.img
3. Flash Mobile Q
Obtain fsg.img from TWRP or root adb on a phone that never had the Eluga Switch ROM on it:
dd if=/dev/block/mmcblk0p22 of=fsg.img
Here's a diff report between Panasonic and Alcatel fsg partitions
Different Files:
Code:
/nv/item_files/conf/lte_rrc.conf
/nv/item_files/conf/mmode.conf
/nv/item_files/conf/nas_mm.conf
/nv/item_files/conf/wcdma_rrc_external.conf
/nv/item_files/modem/geran/grr/
/nv/item_files/modem/geran/vamos_support
/nv/item_files/modem/mmode/lte_bandpref
/nv/item_files/modem/uim/mmgsdi/
/nv/item_files/modem/uim/uimdrv/
/nv/item_files/rfnv/00021307
/nv/item_files/rfnv/00021308
/nv/item_files/rfnv/00021309
/nv/item_files/rfnv/00021310
/nv/item_files/rfnv/00021311
/nv/item_files/rfnv/00021312
/nv/item_files/rfnv/00021313
/nv/item_files/rfnv/00021316
/nv/item_files/rfnv/00021318
/nv/item_files/rfnv/00021321
/nv/item_files/rfnv/00021322
/nv/item_files/rfnv/00021324
/nv/item_files/rfnv/00021325
/nv/item_files/rfnv/00025028
/nv/item_files/rfnv/00025029
/nv/item_files/rfnv/00025030
/nv/item_files/rfnv/00025031
/nv/item_files/rfnv/00025478
/nv/item_files/wcdma/rrc/
/nv/item_files/wcdma/
/nv/item_files/wcdma/rrc/wcdma_rrc_feature
/nvm/num/10
/nvm/num/1877
/nvm/num/2
/nvm/num/2509
/nvm/num/2808
/nvm/num/2954
/nvm/num/4033
/nvm/num/4034
/nvm/num/4398
/nvm/num/4548
/nvm/num/5079
/nvm/num/5153
/nvm/num/5895
/nvm/num/6253
/nvm/num/6564
/nvm/num/6828
/nvm/num/911
/nvm/num/946
/tvn.txt
Alcatel Unique Files:
Code:
/nv/item_files/conf/data_config_info.conf
/nv/item_files/modem/data
/nv/item_files/modem/geran/plmn_search_freq_pruning_enabled
/nv/item_files/modem/lte/rrc
/nv/item_files/modem/lte_connection_control
/nv/item_files/modem/mmode/lte_disable_duration
/nv/item_files/modem/nas/aggression_management
/nv/item_files/modem/nas/nas_config_feature
/nv/item_files/modem/nas/nas_nv_classmark_ie
/nv/item_files/modem/nas/nas_srvcc_support
/nv/item_files/rfnv/00021323
/nv/item_files/wcdma/rrc/wcdma_rrc_disable_cpc_fdpch
/nv/item_files/wcdma/rrc/wcdma_rrc_disable_e_dpdch
/nv/item_files/wcdma/rrc/wcdma_rrc_wtol_cm_support
/nv/item_files/wcdma/rrc/wcdma_rrc_wtol_ps_ho_support
/nvm/num/3
/nvm/num/6844
/pdp_profiles
/SUPL/preprodsupl.cer
/SUPL/spirentroot.cer
/SUPL/telusslp_prod.cer
Pansonic Unique Files:
Code:
/nv/item_files/conf/cgps_sm.conf
/nv/item_files/gps/cgps/sm
/nv/item_files/modem/mmode/device_mode
/nv/item_files/modem/mmode/ue_usage_setting_Subscription01
/nvm/context1
/nvm/num/57_100
/nvm/num/57_99
/nvm/num/6792
/nvm/num/6876
/nvm/num/6907
So it looks like these two fsg files have something to do with turning LTE bands on & off
/nvm/num/6828
/nv/item_files/modem/mmode/lte_bandpref
All bands the SD615 chip or 6045/Eluga/I806 support could potentially be enabled
More info on hacking NV 6828:
Code:
usoftsmartphone.com/t264374.html
Mario223 said:
The Eluga Switch software replaces the fsg partition to enable different LTE bands.
Mobile Q fails to replace it with a U.S. one so you get stuck with LTE band 1/3/7/etc.
Restoring LTE band 4 (from stock android 6.0.1):
1. Flash Eluga Switch to get fastboot back
2. fastboot flash fsg fsg.img
3. Flash Mobile Q
Obtain fsg.img from TWRP or root adb on a phone that never had the Eluga Switch ROM on it:
dd if=/dev/block/mmcblk0p22 of=fsg.img
Click to expand...
Click to collapse
Thanks for this info!! Do you have a copy of the fsg.img from a 6045? I have a new Idol 3 coming in but my android experience is lacking here.... If you don't have a copy I can try to pull it from new device, but could you provide specific instructions on how to pull the fsg.img and then push it back to my "broken" idol?? That would save me a major headache!! Again thanks so much for providing this information!!!!
Sorry, just saw how to flash it back, how exactly do I pull it?? (Run the dd command from twrp terminal??)
And if I flash the fsg.img back, I won't have to run mobile Q, i could still just install the marionette mm rom??
---------- Post added at 03:52 AM ---------- Previous post was at 03:26 AM ----------
If anyone has a copy of the US LTE fsg partiton from a 6045 they can share, my new phone wont be in until friday, I'd like to get this fixed before then if possible thanks!!
Found it, thanks trying it now!!!
---------- Post added at 04:49 AM ---------- Previous post was at 03:52 AM ----------
Mario223 said:
The Eluga Switch software replaces the fsg partition to enable different LTE bands.
Mobile Q fails to replace it with a U.S. one so you get stuck with LTE band 1/3/7/etc.
Restoring LTE band 4 (from stock android 6.0.1):
1. Flash Eluga Switch to get fastboot back
2. fastboot flash fsg fsg.img
3. Flash Mobile Q
Obtain fsg.img from TWRP or root adb on a phone that never had the Eluga Switch ROM on it:
dd if=/dev/block/mmcblk0p22 of=fsg.img
Click to expand...
Click to collapse
The command for Idol 3 is.....
2. Fastboot -i 0x1bbb flash fsg fsg.img
Ok So I'm finally back up and running with LTE on stock MM rom 6045I. Took a few attempts but I backed up all the partitions on the new phone that came in today(a day early) it was 5.02 oob. Anyhow flashed the eluga firmware then flashed over fsg, no luck still showed hspa, but ran mobile Q anyway, still stuck on hspa and would not find any LTE mobile networks. Back to eluga, flashed modem, modemst1, modemst2 and fsg. Rebooted eluga popped up and found lte network and showed lte, flashed MM via mobile upgrade Q, and now its working like a charm, my mobile high speed data is back!! Thanks again for pointing me in the right direction @Mario223
Where did you get the fsg.img file
kal250 said:
Thanks for this info!! Do you have a copy of the fsg.img from a 6045? I have a new Idol 3 coming in but my android experience is lacking here.... If you don't have a copy I can try to pull it from new device, but could you provide specific instructions on how to pull the fsg.img and then push it back to my "broken" idol?? That would save me a major headache!! Again thanks so much for providing this information!!!!
Sorry, just saw how to flash it back, how exactly do I pull it?? (Run the dd command from twrp terminal??)
And if I flash the fsg.img back, I won't have to run mobile Q, i could still just install the marionette mm rom??
---------- Post added at 03:52 AM ---------- Previous post was at 03:26 AM ----------
If anyone has a copy of the US LTE fsg partiton from a 6045 they can share, my new phone wont be in until friday, I'd like to get this fixed before then if possible thanks!!
Found it, thanks trying it now!!!
---------- Post added at 04:49 AM ---------- Previous post was at 03:52 AM ----------
The command for Idol 3 is.....
2. Fastboot -i 0x1bbb flash fsg fsg.img
Click to expand...
Click to collapse
Where did you get the fsg.img file? I'm in the boat with no LTE after switching from Eluga. Thanks.
man0war678 said:
Where did you get the fsg.img file? I'm in the boat with no LTE after switching from Eluga. Thanks.
Click to expand...
Click to collapse
I made a backup from a brand new out of box 6045I, that I ended up buying from Amazon to fix my issue.... See here....
http://forum.xda-developers.com/idol-3/help/sim-card-unrecognized-t3452169/post68972817
Thanks!
kal250 said:
I made a backup from a brand new out of box 6045I, that I ended up buying from Amazon to fix my issue.... See here....
http://forum.xda-developers.com/idol-3/help/sim-card-unrecognized-t3452169/post68972817
Click to expand...
Click to collapse
Thanks. I might have to painfully go back to the ELUGA ROM, flash the file and hopefully get LTE back. Thanks for the files.
Can you flash just the CP file? Using the unlocked US firmware but wanted to use the T-Mobile modem. Tried to flash it and it just fails with no error. So are we not able to flash just the CP?
I wouldn't flash t-mobile modem drivers on to universal firmware. This can disable carrier aggregation permanently. Unless you want to use the phone with T-mobile only.
D1G1T4L said:
Can you flash just the CP file? Using the unlocked US firmware but wanted to use the T-Mobile modem. Tried to flash it and it just fails with no error. So are we not able to flash just the CP?
Click to expand...
Click to collapse
Normally yes... But your unlocked US Model is this exynos or snapdragon?
seemcity said:
I wouldn't flash t-mobile modem drivers on to universal firmware. This can disable carrier aggregation permanently. Unless you want to use the phone with T-mobile only.
Click to expand...
Click to collapse
Well it was originally a T-Mobile version. I flashed the unlocked US firmware on it.
maik005 said:
Normally yes... But your unlocked US Model is this exynos or snapdragon?
Click to expand...
Click to collapse
Snapdragon
Ok
I have an EA ROM on an ATT device, but we all faced on the A11 that after fixing the NT code, we are not able to use LTE and mobile data, but then we had the PDC tool where we loaded the .mbn.
Now on the A12 and A13 we don't have the ability to use PDC so I was forced to do something to get LTE & mobile data back and I made some changes to the modem .img where the problem was fixed.
Note: I read before that some people were not able to fix the fingerprint after croosflashing ROMs, now we can do it but by cross-modem images.
Current patched mods are for EA ROM. A12+ but there are one version for A11 if you do not want to use PDC tool.
Spoiler: A11 patched modem
Patched modem only for A11
in the previous modified versions, users had the problem that Netflix did not work on their A11, with V1.2 or Universal version where the mentioned problems have been fixed.
Spoiler: A12 patched modem
We have three versions of the modems
V1 is with minimal changes only for EU bands A12(outside it wil work or not)
V2 & V3 is with slightly bigger changes and can be used outsde EU,
V1-L-51A modem with a fixed fingerprint after cross-flashing the EA firmware with right signals (only docomo JP variants).
Spoiler: A13 patched modem
For A13, only versions V1 and V2 were made accordingly because previously V1 had the least number of users on A12.
V1 with fewer changes
V2 with more changes.
Spoiler: Universal patched modem
Modem_Universal fully compatible with A10+ android but there are more changes than V3 A12 modem and can be some bugs like fingerprint does not work on A13
Spoiler: Patched modem JP variant
I would also like to make JP modems for A13 (Docomo & Softbank), anyone who wants to help in making a JP patched modem should contact me on Telegram @JigsawProfile.
Note: it is always better to use a modem with fewer changes, this ensures that the updates are original and newer.
5G and VoLte working.
You can flash modems easily via Fastboot to A/B slots or you can flash via Qfill.
Flashing patched modem won"t bricked /bootlop your device.
DOWNLAOD modem.img
Note: Planned to create a magisk module, in those cases it would not be necessary to flash the Modem partition, in those cases, by removing the magisk/module or resetting the device to factory settings, we lose the modem changes.
I would also like to mention that I don't have daily access to my computer, but only a few hours a week, and that limits my possibilities.
can this modem works in docomo variant crossflashed EA south african firmware
k.syedhussain said:
can this modem works in docomo variant crossflashed EA south african firmware
Click to expand...
Click to collapse
I do not sure but you can try.
I think it doesn't matter whether it is ATAT, TMO or some other variant should work
I have locked bootloader,..can convert into bin for edl
k.syedhussain said:
I have locked bootloader,..can convert into bin for edl
Click to expand...
Click to collapse
Yout can flash .img via qfil
JigsawMobile said:
Yout can flash .img via qfil
Click to expand...
Click to collapse
Will try ,did you modified volte capabilities will it catch volte signals after flashing modified modem
k.syedhussain said:
Will try ,did you modified volte capabilities will it catch volte signals after flashing modified modem
Click to expand...
Click to collapse
tried with locked bootlloader end with bootloop
k.syedhussain said:
tried with locked bootlloader end with bootloop
Click to expand...
Click to collapse
JigsawMobile said:
Yout can flash .img via qfil
Click to expand...
Click to collapse
can you modify my modem file enable volte vowifi for indian networks
i have Japanese docomo A51L version its only work with Japanese original backup modem.
i crossflashed european za firmware south african all work perfectly.but in network setting its show only cdma roaming option.
k.syedhussain said:
can you modify my modem file enable volte vowifi for indian networks
i have Japanese docomo A51L version its only work with Japanese original backup modem.
i crossflashed european za firmware south african all work perfectly.but in network setting its show only cdma roaming option.
Click to expand...
Click to collapse
so when you flash EU modifed modems all work but you do not have volte ?
sometimes when "cdma roaming option" option shows when NT code is not corect, do you have nt coe error ?
missing oprion in networks settings it not depend of modems.
JigsawMobile said:
so when you flash EU modifed modems all work but you do not have volte ?
sometimes when "cdma roaming option" option shows when NT code is not corect, do you have nt coe error ?
missing oprion in networks settings it not depend of modems.
Click to expand...
Click to collapse
No when i flashed EU modem my phone went to bootloop....
Yes i have NT CODE ERROR
I AM USING docomo v60 with EU firmware with docomo model....
Actually you sent me bootloader flashing file...
Can you flash both modified modem in your mobile and take backup from qfil share me....
Yes i can backup modems via qfill
try this first when you flash modifed modems via fastboot than backup via qfill and that modems try to open via qfil, and tell me will it open in the .7z.
well you can flash modifed images via qfill, qfill can flash and .img files
JigsawMobile said:
Yes i can backup modems via qfill
try this first when you flash modifed modems via fastboot than backup via qfill and that modems try to open via qfil, and tell me will it open in the .7z.
well you can flash modifed images via qfill, qfill can flash and .img files
Click to expand...
Click to collapse
Ok now i can t unlock the bootloader now.
Do you have modified modem backup
Hello, should I flash the .gz file or do I need to extract it? If so, it looks like both images are 2kb bigger than the original ones.
You van flash via fastboot or via qfill, qfill can flash and .img.
Exttact from .gz you will get
Img
I don't get any .img files, only files with no extension.
Tried to flash tem via qfil and fastboot, both methods give me a kernel crash.
Also, both qfil and fasboot warned me about those files not being the exact partition size which is 361.758.720 bytes, instead, they are 361.760.256 bytes.
I tried flashing them whole and also trimmed by deleting everything post 0x158FFF0, both made me kernel crash. Restoring the backed up modem partition gets me to boot again.
edit: I'm using 7zip to extract, maybe that's the issue?
lucasdessy said:
I don't get any .img files, only files with no extension.
Tried to flash tem via qfil and fastboot, both methods give me a kernel crash.
Also, both qfil and fasboot warned me about those files not being the exact partition size which is 361.758.720 bytes, instead, they are 361.760.256 bytes.
I tried flashing them whole and also trimmed by deleting everything post 0x158FFF0, both made me kernel crash. Restoring the backed up modem partition gets me to boot again.
edit: I'm using 7zip to extract, maybe that's the issue?
Click to expand...
Click to collapse
If showing like modem_a just click one more time and you will se modem_a.img.
I will reupload in the .rar
k.syedhussain said:
Ok now i can t unlock the bootloader now.
Do you have modified modem backup
Click to expand...
Click to collapse
If showing like modem_a just click one more time and you will se modem_a.img. it imgs reatore via qfill.
To reatore do not extract only modem_a, need to be with extension .img
I will reupload in the rar compression
I would like to test the LG v60 Japanese version on a machine that has been cross-flexed to the Canadian version. Can I allow download access?
Thank you for the access.
It also doesn't work in the Japanese version -> Canadian version.
I had a question when I saw the text file in the compressed file.
Are the modified folders image\sdx55m, sdx55, modem_pr\so" and other att original modem files placed in the ea modem?
andamiro00 said:
Thank you for the access.
It also doesn't work in the Japanese version -> Canadian version.
I had a question when I saw the text file in the compressed file.
Are the modified folders image\sdx55m, sdx55, modem_pr\so" and other att original modem files placed in the ea modem?
Click to expand...
Click to collapse
All changed files EA
I did not croosflash att and ea modems but i will test it method when i having att a12 original modem, i believe that we can get to work via croisflashiig original -> EA modems.
Note: if you want to try croisflash modem you need rooted device.
Why you using canadian rom version why not EA ?