Related
Hi everybody,
I have an canadian Rogers Moto X 1058 which I use here in Europe. To get european languages & the 4.4.4 Update I went back to Stock Recovery & French 4.4.2 (RETAIL-FR_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml.zip).
Then I wanted to update via OTA to 4.4.4 but it failed. Doing this via adb sideload it also fails with this error:
"/modem/image/dsps.b00" has unexpected contents"
What I did by flashing the french 4.4.2 was replacing the NON-HLOS.bin and fsg.mbn with the ones from the Rogers 4.4.2 to have Radio / Modem working with the Hardware.
What can I do now to get 4.4.4, please?
a) Flashing the Verizon 4.4.4 over my 4.4.2 like mentioned here http://forum.xda-developers.com/moto-x/general/update-moto-x-mexico-to-4-4-4-vzn-firm-t2828190 and using the Rogers Modem Files again
or
b) should I flash the french 4.4.2 again with the french Modem Files for the 1052, then update to french 4.4.4 via adb side load & then flash the Rogers 4.4.2 Modem Files via adb afterwards before rebooting?
Any help about this riddle would be appreciated
yeticomes said:
Hi everybody,
I have an canadian Rogers Moto X 1058 which I use here in Europe. To get european languages & the 4.4.4 Update I went back to Stock Recovery & French 4.4.2 (RETAIL-FR_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml.zip).
Then I wanted to update via OTA to 4.4.4 but it failed. Doing this via adb sideload it also fails with this error:
"/modem/image/dsps.b00" has unexpected contents"
What I did by flashing the french 4.4.2 was replacing the NON-HLOS.bin and fsg.mbn with the ones from the Rogers 4.4.2 to have Radio / Modem working with the Hardware.
What can I do now to get 4.4.4, please?
a) Flashing the Verizon 4.4.4 over my 4.4.2 like mentioned here http://forum.xda-developers.com/moto-x/general/update-moto-x-mexico-to-4-4-4-vzn-firm-t2828190 and using the Rogers Modem Files again
or
b) should I flash the french 4.4.2 again with the french Modem Files for the 1052, then update to french 4.4.4 via adb side load & then flash the Rogers 4.4.2 Modem Files via adb afterwards before rebooting?
Any help about this riddle would be appreciated
Click to expand...
Click to collapse
Since you have already changed ROMs (I normally don't suggest doing this), here is my recommendation:
You can flash the entire French 4.4.2 again (baseband and all) and then accept the OTA to 4.4.4.
Keep in mind that you can omit the "erase userdata" command and it will preserve your data and apps.
Also note that we have received reports that using a 4.4.2 modem with a 4.4.4 ROM has resulted in issues for some. This includes no signal, or even missing IMEI. So I really would not suggest flashing a 4.4.2 baseband after you accept the OTA. If you really want to be on the Rogers baseband (keeping in mind that there is no need to do so - the FR baseband should work fine for you...), you will need to wait until the 4.4.4 full SBF for Rogers is released.
Good Luck.
samwathegreat said:
Since you have already changed ROMs (I normally don't suggest doing this), here is my recommendation:
You can flash the entire French 4.4.2 again (baseband and all) and then accept the OTA to 4.4.4.
Keep in mind that you can omit the "erase userdata" command and it will preserve your data and apps.
Also note that we have received reports that using a 4.4.2 modem with a 4.4.4 ROM has resulted in issues for some. This includes no signal, or even missing IMEI. So I really would not suggest flashing a 4.4.2 baseband after you accept the OTA. If you really want to be on the Rogers baseband (keeping in mind that there is no need to do so - the FR baseband should work fine for you...), you will need to wait until the 4.4.4 full SBF for Rogers is released.
Good Luck.
Click to expand...
Click to collapse
Thank you Sam, seems that there is hope
Regarding the use of the 1052 ROM - it was only because of the languages :-/ Didn't know that I can use the european Modem Files with the canadian Hardware - so for now I'll take the ones from the french 4.4.4 OTA.
Before I'll re (m)fast boot the french 4.4.2 again - which steps should I leave out, to keep my user data, please?
Code:
sudo fastboot oem fb_mode_set
sudo mfastboot flash partition gpt.bin
sudo mfastboot flash motoboot motoboot.img
sudo mfastboot flash logo logo.bin
sudo mfastboot flash boot boot.img
sudo mfastboot flash recovery recovery.img
sudo mfastboot flash system system.img
sudo mfastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo mfastboot flash fsg fsg.mbn
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase customize
sudo fastboot erase clogo
sudo fastboot oem fb_mode_clear
Only this ones are to delete or all the stuff which is not an .img?
Code:
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase customize
sudo fastboot erase clogo
You helped me very much! Thank you! Maybe you can agai just help me with these fast boot questions, please?
yeticomes said:
Thank you Sam, seems that there is hope
Regarding the use of the 1052 ROM - it was only because of the languages :-/ Didn't know that I can use the european Modem Files with the canadian Hardware - so for now I'll take the ones from the french 4.4.4 OTA.
Before I'll re (m)fast boot the french 4.4.2 again - which steps should I leave out, to keep my user data, please?
Code:
sudo fastboot oem fb_mode_set
sudo mfastboot flash partition gpt.bin
sudo mfastboot flash motoboot motoboot.img
sudo mfastboot flash logo logo.bin
sudo mfastboot flash boot boot.img
sudo mfastboot flash recovery recovery.img
sudo mfastboot flash system system.img
sudo mfastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo mfastboot flash fsg fsg.mbn
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase customize
sudo fastboot erase clogo
sudo fastboot oem fb_mode_clear
Only this ones are to delete or all the stuff which is not an .img?
Code:
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase customize
sudo fastboot erase clogo
You helped me very much! Thank you! Maybe you can agai just help me with these fast boot questions, please?
Click to expand...
Click to collapse
Glad to help. The only line that is necessary to leave out is "fastboot erase userdata".
samwathegreat said:
Glad to help. The only line that is necessary to leave out is "fastboot erase userdata".
Click to expand...
Click to collapse
Cool, your support is a dream! Will try it immediately & post when its done!
samwathegreat said:
Glad to help. The only line that is necessary to leave out is "fastboot erase userdata".
Click to expand...
Click to collapse
Hmm, did so & now my Moto X has no longer a Mobile Network connection?! I am on 4.4.2 and only Wifi is working - what can I do?
Should I reflash the Rogers 4.4.2 Modem files? Should I re-do all commands & just exchange the files?
or is it possible to use only these commands to update the Modem?
Code:
sudo fastboot oem fb_mode_set
sudo mfastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo mfastboot flash fsg fsg.mbn
sudo fastboot oem fb_mode_clear
Or any other solution, please?
http://d.pr/i/woyv
Ufff ... seems that below worked for me :good:
yeticomes said:
Hmm, did so & now my Moto X has no longer a Mobile Network connection?! I am on 4.4.2 and only Wifi is working - what can I do?
Should I reflash the Rogers 4.4.2 Modem files? Should I re-do all commands & just exchange the files?
or is it possible to use only these commands to update the Modem?
Code:
sudo mfastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo mfastboot flash fsg fsg.mbn
Or any other solution, please?
http://d.pr/i/woyv
Click to expand...
Click to collapse
yeticomes said:
Ufff ... seems that below worked for me :good:
Click to expand...
Click to collapse
Excellent. I was just getting ready to reply that you did a great job with those commands (that's EXACTLY the commands needed to change basebands).
Great Job. Glad everything worked out. :good:
samwathegreat said:
Excellent. I was just getting ready to reply that you did a great job with those commands (that's EXACTLY the commands needed to change basebands).
Great Job. Glad everything worked out. :good:
Click to expand...
Click to collapse
Thanks a lot - was a little bit in a hurry because I had to leave home for some hours and the Mobile Network was gone
I got missing IMEI.
Himanshudud said:
I got missing IMEI.
Click to expand...
Click to collapse
Is this directly related to this thread subject?
If not... I suggest searching for a similar thread issue, or starting a new one.... Otherwise this is called thread hijacking. ?
If it is related to the info on this thread... Can you be more specific? What you did before that happened, what model and firmware you are on... Etc.
KJ said:
Is this directly related to this thread subject?
If not... I suggest searching for a similar thread issue, or starting a new one.... Otherwise this is called thread hijacking. ?
If it is related to the info on this thread... Can you be more specific? What you did before that happened, what model and firmware you are on... Etc.
Click to expand...
Click to collapse
I am new to talpatalk. I was trying to reply to previous comment.
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
samwathegreat said:
Since you have already changed ROMs (I normally don't suggest doing this), here is my recommendation:
You can flash the entire French 4.4.2 again (baseband and all) and then accept the OTA to 4.4.4.
Keep in mind that you can omit the "erase userdata" command and it will preserve your data and apps.
Also note that we have received reports that using a 4.4.2 modem with a 4.4.4 ROM has resulted in issues for some. This includes no signal, or even missing IMEI. So I really would not suggest flashing a 4.4.2 baseband after you accept the OTA. If you really want to be on the Rogers baseband (keeping in mind that there is no need to do so - the FR baseband should work fine for you...), you will need to wait until the 4.4.4 full SBF for Rogers is released.
Good Luck.
Click to expand...
Click to collapse
Exactly when I changed the firmware version I got missing IMEI error. Mobile fails to detect network.
Himanshudud said:
I am new to talpatalk. I was trying to reply to previous comment.
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Exactly when I changed the firmware version I got missing IMEI error. Mobile fails to detect network.
Click to expand...
Click to collapse
Well, ideally, having a nandroid backup of your EFS is ALWAYS a good idea.
But without that, you can try to restore the stock firmware for your model/carrier and same android version. Do not downgrade! Like so many have done.... If you flashed a different carriers firmware, and a higher version that your carrier has available....then have big issues, You may be putting the phone away and waiting for files you can flash for your model... On the same version of android you are now on.
I flashed 4.4.3 and got no IMEI. While downgrading with 4.4.2 got gpt.bin error. And again no IMEI. Then I flashed every other file of 4.4.2 except gpt.bin and now on 4.4.2 with IMEI back. But afraid to take ota update. And now waiting for full firmware file to leak.
Himanshudud said:
I flashed 4.4.3 and got no IMEI. While downgrading with 4.4.2 got gpt.bin error. And again no IMEI. Then I flashed every other file of 4.4.2 except gpt.bin and now on 4.4.2 with IMEI back. But afraid to take ota update. And now waiting for full firmware file to leak.
Click to expand...
Click to collapse
Glad it's back.... And no.... I would never take an OTA again.... To be safe.
You're not missing anything special... And I'm sure flashable files won't take too long.
KJ said:
Glad it's back.... And no.... I would never take an OTA again.... To be safe.
You're not missing anything special... And I'm sure flashable files won't take too long.
Click to expand...
Click to collapse
i know just some minor update to camera and dial pad.
Soooo i was a big dumby and i wrote over the modem in order to get the update.
Now i have no signal/service available , or compatible baseband flashed.
Wifi works, everything else is amazing !!
Currently
Android 5.0
Baseband: Unknown <------
System version: 22.11.6.victara_tmo.tmo.en.US tkpca
Build Number: LXE22.39-6
If any one successfully backs up the telus baseband could you please post it ?!!?
So screwed at the moment
If you can tell me how to do so I would be happy to.
---------- Post added at 03:32 PM ---------- Previous post was at 02:51 PM ----------
pipesdl said:
If you can tell me how to do so I would be happy to.
Click to expand...
Click to collapse
I might have figured it out, use at your own risk.
https://drive.google.com/file/d/0B5ErTnQGFRMaVjRaWDV2dFlqMzg/view?usp=sharing
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Ah, didn't realize two files were needed. Links below.
FSG
https://drive.google.com/file/d/0B5ErTnQGFRMaN0JjLUx1RDVZakk/view?usp=sharing
NON-HLOS
https://drive.google.com/file/d/0B5ErTnQGFRMaWHVXZEhwS2UwU2M/view?usp=sharing
pipesdl said:
Ah, didn't realize two files were needed. Links below.
FSG
NON-HLOS
[
Click to expand...
Click to collapse
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
I think I did extract it with an mbn extension, don't know if it will make a difference but I'll upload shortly.
Let me know if it works.
https://drive.google.com/file/d/0B5ErTnQGFRMaQk9fcC05amJvTDg/view?usp=sharing
OscarAlert said:
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
Click to expand...
Click to collapse
You need the following commands. Just keep your mbn file.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I would love to know if those modem files work for the Telus phone after flashing, as the only thing holding me back is that it currently won't let me back up my own. If it does then lollipop here I come!
Those two files worked! Thanks so much to everyone who helped out in this thread. Successfully running Lollipop on my Telus Moto X now!
Awesome, can you let me know what steps you followed in addition to the steps above?
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Kodiak1 said:
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Click to expand...
Click to collapse
I'm pretty sure that in order to make an image of your baseband files, you need to be rooted. Root access is granted by SuperSU. As for the extensions on the fsg file, it doesn't matter what you call it. You just have to be consistent when copying it or applying it back to your device. I think someone posted on the forum using mbn and then used bin for applying it, which for obvious reasons wouldn't work.
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Take pity on me
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Update on xt1092 worked! I did this:
1. Downloaded the 4.4.4 system image from xt1905 (first post for download link)
2. Extracted the zip
3. flashed over mfastboot.exe
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
4. sideloaded the OTA update from first post
5. reboot
6. flashed back the original modem and fsg from xt1902, without erasing modemst1 and modemst2 -> https://www.androidfilehost.com/?fid=95784891001608300
Click to expand...
Click to collapse
Then realising I had no signal I followed this post:
YES!
I finally have Lollipop on my XT1092!!
I followed steff999's guide but encountered several problems with the modem and data connections etc.
I just couldn't figure out why flashing the XT1092 modem files didn't work.
Then I went back to my original firmware and did the procedure again.
But now I did not let it boot after the OTA Update and directly booted into fastboot mode and flashed the modem and fsg files.
Then after reboot I immediately had mobile service. IMEI and Baseband is back again.
I use Linux and it is very easy with Linux.
In a terminal just go to the folder with the files (no matter where they are!!).
After getting Android SDK I did:
Code:
$ sudo apt-get install android-tools-fastboot <<-- to install fastboot
$ cd /directory with your files...<<--- choose your folder
$ fastboot flash logo logo.bin
etc
after flashing the files put OTA.zip on phone. Go in recovery mode and apply update.
Then when it reboots directly go in fastboot mode and type:
$ cd /directory with your XT1092 modem files/
$ fastboot flash modem NON-HLOS.bin
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
now it boots into lollipop and it should recognize your sim card.
This is how it worked for me with Linux. Should be similar with Windows but I think the files for flashing have to be in fastboot directory then.
I did not use erase modem commands
I hope this will give hope back to people who encountered similar problems with the modem. I was about to give up but decided to give it a last try.
Click to expand...
Click to collapse
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
THE-M1GHTY-BUKO said:
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Then realising I had no signal I followed this post:
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
Click to expand...
Click to collapse
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
drolgnir said:
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
Click to expand...
Click to collapse
My problem is now fixed, thankyou.
For future reference for others, how did you fix the problem?
Sent from my XT1095 using Tapatalk
halfez said:
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Click to expand...
Click to collapse
Any chance you have a copy of the modem files for your moto x 2014 (XT1097 ) on Wind? I flashed the T-Mobile 5.0 xt1095, and don't think I properly backed up my files.
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
halfez said:
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
Click to expand...
Click to collapse
Come on, just do it!
I have read the threads on the latest OTA update for the Pure Edition and I am confused on how to proceed. I am running System Version 22.11.6 Build Number LXE22.39.-6 and have got an OTA for 22.21.11.en.US, but it has failed of course. I am rooted with CF-Auto Root, the version from the middle of November, and have stock recovery.
What I am seeking to do is update to 22.21.11.en.US and not lose my apps or data.
What is the correct procedure for updating? Thanks Guys!!
I was on the first soak test build for lollipop and when the .6 build came out (the one that your on) I couldn't update unless I downgraded to 4.4.4 then re upgraded to lollipop OTA but it took a day for the OTA to show on my phone .....im pretty sure you have to do the same from .6 to .11 so https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images follow the steps on Motorola's website here really simple process just a few commands, but it will wipe your device
Since you're rooted, just run Titanium backup, return to 4.4.4, then apply .6 update and .11 update. (The .11 we have so far is only a delta from .6 -- not the full OTA)
edit: Apparently the full kitkat->lollipop .11 OTA is out there... hooray!
Do not use the instructions on Motorola factory images website
That website is missing a subtle command, that will make your OTA fail. I had that problem.
This line is missing.
fastboot flash modem NON-HLOS.bin
The OTA checks for the integrity of the modem and fails otherwise.
---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------
Matthewlawson3 said:
What I am seeking to do is update to 22.21.11.en.US and not lose my apps or data.
Click to expand...
Click to collapse
You can try ADB backup for backing up all your apps and restore after OTA. This way the restore process works even after unrooting.
nimper said:
Since you're rooted, just run Titanium backup, return to 4.4.4, then apply .6 update and .11 update. (The .11 we have so far is only a delta from .6 -- not the full OTA)
edit: Apparently the full kitkat->lollipop .11 OTA is out there... hooray!
Click to expand...
Click to collapse
Android.is.better94 said:
I was on the first soak test build for lollipop and when the .6 build came out (the one that your on) I couldn't update unless I downgraded to 4.4.4 then re upgraded to lollipop OTA but it took a day for the OTA to show on my phone .....im pretty sure you have to do the same from .6 to .11 so https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images follow the steps on Motorola's website here really simple process just a few commands, but it will wipe your device
Click to expand...
Click to collapse
I was rooted on .6 and had to go to 4.4.4. I received the OTA to .11. It was a 576 MB or so update. So there are 2 update OTA depending on what version you are running.
Questions and Requests
bradley26 said:
I was rooted on .6 and had to go to 4.4.4. I received the OTA to .11. It was a 576 MB or so update. So there are 2 update OTA depending on what version you are running.
Click to expand...
Click to collapse
Ok. I have a few questions and requests.
First, this would be my first downgrade I have ever done, do I have to relock the bootloader and/or unroot first?
Second, what are the exact steps and commands in order to downgrade. I know you said they are Motorola's website, but just to be safe, and with the modem command added in, I would feel much better and be appreciative if someone provided that for me.
Third, I am on the US pure edition, which version of 4.4.4. would I need to download from Motorola's website? I've forgotten which version it came with.
Fourth, I was never a soak tester and I am on .6. Why can't I do a direct upgrade to .11 such as what is discussed here?
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Another Approach?
And what about this approach to upgrading from .6. to .11? Could this work?
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Matthewlawson3 said:
Ok. I have a few questions and requests.
First, this would be my first downgrade I have ever done, do I have to relock the bootloader and/or unroot first?
Second, what are the exact steps and commands in order to downgrade. I know you said they are Motorola's website, but just to be safe, and with the modem command added in, I would feel much better and be appreciative if someone provided that for me.
Third, I am on the US pure edition, which version of 4.4.4. would I need to download from Motorola's website? I've forgotten which version it came with.
Fourth, I was never a soak tester and I am on .6. Why can't I do a direct upgrade to .11 such as what is discussed here?
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
For whatever reason you can never have been rooted to update your ROM. So i followed the steps below to get back to stock for the update.
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ 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
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
bradley26 said:
For whatever reason you can never have been rooted to update your ROM. So i followed the steps below to get back to stock for the update.
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ 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
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
Click to expand...
Click to collapse
@Matthewlawson3
you can't downgrade the bootloader so omit that step. it won't make the OTA fail.
i'd recommend erasing userdata and cache.
once you do this, you should get the official full OTA that you can check for in the settings menu and apply. good luck.
mrvirginia said:
@Matthewlawson3
you can't downgrade the bootloader so omit that step. it won't make the OTA fail.
i'd recommend erasing userdata and cache.
once you do this, you should get the official full OTA that you can check for in the settings menu and apply. good luck.
Click to expand...
Click to collapse
So motoboot.img is the bootloader? That is the command you don't want me to enter?
I need to type in all the commands in that exact sequence, correct? Where does one enter the fastboot flash modem NON-HLOS.bin in the sequence of commands?
I would prefer not to lose my apps and data if it can be avoided. I do have Titanium Backup and could if need be, but what are the downsides to not erasing usercache and cache?
Thanks for your help on this!!!
Motorola Fastboot
I've never used the Motorola Fastboot utility. How does one acquire it and how do you set it up? I've only use the Android fastboot in the platform-tools folder.
Also, which build of 4.4.4. do I choose from on graffinxnyc's website? 4.4.4 Build: KXE21.187-42 Full Restore Images?
Matthewlawson3 said:
I've never used the Motorola Fastboot utility. How does one acquire it and how do you set it up? I've only use the Android fastboot in the platform-tools folder.
Also, which build of 4.4.4. do I choose from on graffinxnyc's website? 4.4.4 Build: KXE21.187-42 Full Restore Images?
Click to expand...
Click to collapse
fastboot flash partition gpt.bin
fastboot reboot-bootloader
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 flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
I got the images from motos site. had everything I needed.
not sure what, if any, errors you'd see due to not erasing userdata/cache
mrvirginia said:
fastboot flash partition gpt.bin
fastboot reboot-bootloader
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 flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
I got the images from motos site. had everything I needed.
not sure what, if any, errors you'd see due to not erasing userdata/cache
Click to expand...
Click to collapse
I have got the image for 4.4.4 (TMO_21.21.42.victara_tmo.tmo.en.US) from Motorola for the US Pure Edition, through the request process. Can I run these commands using regular fastboot from the android SDK platform-tools folder or must I use fastboot found in the Motorola 4.4.4 image? If I must use Motorola fastboot, what is the process for getting that setup before I go into a command prompt and enter the commands?
If I use the Motorola fastboot can I just copy the needed files into the Windows folder found in the Motorola image folder and then open a command prompt there to enter the commands? Is it that easy? I do not have a mfastboot file in the Windows folder in the image.
Matthewlawson3 said:
I have got the image for 4.4.4 (TMO_21.21.42.victara_tmo.tmo.en.US) from Motorola for the US Pure Edition, through the request process. Can I run these commands using regular fastboot from the android SDK platform-tools folder or must I use fastboot found in the Motorola 4.4.4 image? If I must use Motorola fastboot, what is the process for getting that setup before I go into a command prompt and enter the commands?
If I use the Motorola fastboot can I just copy the needed files into the Windows folder found in the Motorola image folder and then open a command prompt there to enter the commands? Is it that easy? I do not have a mfastboot file in the Windows folder in the image.
Click to expand...
Click to collapse
After doing some research, I have placed the fastboot.exe from the Motorola image in the Android-SDK platform-tools folder, but before I placed it in there, I renamed it mfastboot.exe, so as not to clash with the android fastboot.exe. When I type in the command prompt "mfastboot," I get a list of commands. Does this indicate everything is working correctly? And if so, when I type in the commands to perform the downgrade will I type in "mfastboot" instead of "fastboot" with every command?
Matthewlawson3 said:
After doing some research, I have placed the fastboot.exe from the Motorola image in the Android-SDK platform-tools folder, but before I placed it in there, I renamed it mfastboot.exe, so as not to clash with the android fastboot.exe. When I type in the command prompt "mfastboot," I get a list of commands. Does this indicate everything is working correctly? And if so, when I type in the commands to perform the downgrade will I type in "mfastboot" instead of "fastboot" with every command?
Click to expand...
Click to collapse
yes and yes
Ok. Thanks! One last question regarding the commands. After I flash partition gpt.bin, I am suppose to reboot from fastboot back to fastboot (reboot-bootloader) before continuing the commands..correct?
Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi
Hi All!
Here is my situation, I have a moto g xt1072 (Jan 2016) which came with a faulty problem, no sound after 5 seconds of been started. I checked everything (Factory reset via recovery), including both speakers, (both working at 7.5 ohms). Do you think a firmware change or a different ROM can help or it's time to let it go?
Base band: M8926_309101.02.03.19R THEA_EMEA_CUST
Kernel: 3.4.42-gef77327 [email protected] #1
System Version: 24.41.34.thea_retes.retesall.en.EU retes
Complation numer: MPB24.65-34
Everything is stock, no changes were made.
Thanks in advance!!!
@lost101
did you look here
http://forum.xda-developers.com/moto-g-lte
sd_shadow said:
did you look here
http://forum.xda-developers.com/moto-g-lte
Click to expand...
Click to collapse
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
murrayhawk said:
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Click to expand...
Click to collapse
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
lost101 said:
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
ora69 said:
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
Click to expand...
Click to collapse
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
murrayhawk said:
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
Click to expand...
Click to collapse
please, if anything gives a fail, post it on the thread! I myself have hard bricked this device, and now im trying to find the testpoint for it, ive already invested hours into this.. and i have no progress!, its worth it to post it on a thread
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
The guide I linked to is not about downgrading. Ignore references to Android 4.3 - it still applies to Android 6.0. It sounds like you have not installed the usb drivers for your phone in Windows. This is a prerequisite. These Moto G drivers will also work for your phone:
Moto G USB Drivers (WinXP/7/8/10 32Bit-64Bit)
Test Fastboot is working by typing: fastboot devices
You may also be able to use RSD Lite - but this again will require you have installed USB drivers for your phone.
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
sd_shadow said:
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
i think the tip you gave to avoid usb 3.0 ports will really help, didnt realize i was using the usb 3.0 port
Ok, this is what I did so far: (I'm running Windows 7 64b).
1. RSD Lite 6.2.4: Installed
2. Motorola Mobile Drivers Installation 6.4.0: Installed
3. Motorola Device Manager: Installed
1. I started the mobile into the recovery mode
2. Connected the moto cable to the pc
3. Opened RSD Lite, loaded the new firmware and hit start boton
4. The process reached a "please reboot manually...."
5. The phone starts but with the old firmware in it.
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
murrayhawk said:
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
Click to expand...
Click to collapse
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Ok, please check the attachment.
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Can you explain why does it retain the original firmware after mfastboot commandas ran well?
Just a quick reminder. This moto g XT1702 Jan2016, is not rooted, bootloader is locked and has everything stock, it came with Android 6.0 installed.
murrayhawk said:
Can you explain why does it retain the original firmware after mfastboot command as ran well?
Click to expand...
Click to collapse
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
lost101 said:
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
Click to expand...
Click to collapse
What I have right now is : System Version: 24.41.34.thea_retes.retesall.en.EU retes and after flashing to XT1072_THEA_RETES_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml. I'm still having 24.41.34.thea_retes.retesall.en.EU retes.