Related
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Some Help
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
still cannot flash
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Is your phone from Telcel Mexico originally?
I ask because on my case it is. The firmware you need to flash has to be the latest one based on your phone region, on my case I flashed the Brasil Retail. Because my phone is from Latin America. So it will depend on were your phone is from. This is all because your phone is acting up as LOCKED bootloader so flashing a version from another region is not possible.
Also because your phone got stuck on an OTA you need to make sure the version you flash is at least the same one as the OTA, newer if possible.
Rokwenelenya said:
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Click to expand...
Click to collapse
Worked but not completely
Ok, I flashed the rom that you recomended, the phone finally boots into android, but now is always on "emergency calls only" mode, with or without Sim card any suggestions?
Phone should be back as unlocked bootloader
If you flashed a version fine now, I'm sure that at least you should be able to go into fastboot and see your bootloader as unlocked.
If this is true, then you can go ahead and flash any version available, either being an older Stock version (downgrade) or any custom ROM of your liking, like CM 10.1. You should try them and see if you get a proper signal.
Also in your case, if your bootloader is unlocked again, I recommend you installing the version that you know worked fine for you. It won't matter that it's older than the one you flashed right now. It's just a matter of following the guide for unlocked bootloaders to downgrade versions.
Good luck! :fingers-crossed:
Phone almost repaired
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Honestly I have not faced this before it sounds very weird!
I can think of two possibilities, one your phone lost it's IMEI. You should check if it's still there, either by going through configuration and Phone Information or by the "secret code" on the dialer: *#*#4636#*#*
And in the following menu go into Phone Information. The first thing you should see is your IMEI. If it's not there, look for the how to restore your IMEI thread on here. I know it's there somewhere.
The second thing I can think of is to try to force your phone into your carrier, go into Cellular Networks area and manually choose your provider, this could force the registration.
Hopefully this will be of help!
Rokwenelenya said:
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Click to expand...
Click to collapse
Fastboot Error / Invalid GPT
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
adolfovm said:
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Click to expand...
Click to collapse
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
doctorwho2 said:
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
Click to expand...
Click to collapse
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Thanks
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
link
thanks
Click to expand...
Click to collapse
Thanks to you, it really work for me. My Motorola RAZR HD its now alive.
other possible solution that worked for me is
flashing this
http://sbf.droid-developers.org/download.php?device=6&file=119 (CLARO PR Jelly Bean)
Thanks!
suggestions for XT 925 please?
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
hbenz2008 said:
suggestions for XT 925 please?
Click to expand...
Click to collapse
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
unable to flash partition signed
Hi.
I downloaded the SBF from sbf.droid-developers.org/phone.php?device=6 for my region(canada).
I proceeded to try to do universal through the RSD:
Filename: UNIVERSAL.xml
Creation Date: 11/23/2014 09:11:58
File size: 1589
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
I got failed flash process 1/18 flash partition "partition_signed"
Before this, my phone was working fine. Got the kitkat update pushed to me and after update it was working fine. I was using it until my battery ran out so i turned it off. Afterwards, it just got stuck at the motorola logo. I tried to update it with xt926 didn't realize that my phone is xt925. Anyways, i got the bootloader unlocked. Tried the above but failed.
Any help is appreciated!
Thanks!
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
hbenz2008 said:
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
Click to expand...
Click to collapse
I just got help from another thread. Followed it and it worked!!
http://forum.xda-developers.com/showthread.php?t=2760840&page=72
bweN diorD said:
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
Click to expand...
Click to collapse
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
edwint290 said:
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
Click to expand...
Click to collapse
i dont really understand what you are asking.
you need to figure out which is the most recent partition table you have put on the phone successfully and flash that first. nothing will work correctly until you do. after you get a successful partition flash, you can flash whatever you want, just DO NOT flash the partition file again from any other version. old builds will work on the newer partition table.
Hello,
my Dad has a Nexus 5 from Google Play. The phone wasn't and isn't rooted/unlocked. All updates are installed when they come "over the air" to the phone. So the Lollipop OTA update comes and he let it install on the phone but the update didn't work. During the system check it says "/system/lib/libnfc_nci_jni.so has unexpected contents" and "Status 7" and "Error in /tmp/update.zip". But this could not be. It's all stock and nothing is changed on the phone (no root, unlocked).
So I tried to fastboot sideload the OTA update. But this gives me the same error.
The phone data:
Android-Version: 4.4.4
Baseband: M8974-A-2.0.50.1.16
Kernel: 3.4.0-gd59db4e
Build-Version: KTU84P
I used the "5.0 LRX21O-from-4.4.4 KTU84P" OTA file from here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
What's wrong? How can this file have been changed without root? Or is the system check wrong? Can I somehow fix this without unlocking the phone (loosing the data would be only the last option if nothing else works)?
Thanks
Hitzi
hitziflitzi said:
Hello,
my Dad has a Nexus 5 from Google Play. The phone wasn't and isn't rooted/unlocked. All updates are installed when they come "over the air" to the phone. So the Lollipop OTA update comes and he let it install on the phone but the update didn't work. During the system check it says "/system/lib/libnfc_nci_jni.so has unexpected contents" and "Status 7" and "Error in /tmp/update.zip". But this could not be. It's all stock and nothing is changed on the phone (no root, unlocked).
So I tried to fastboot sideload the OTA update. But this gives me the same error.
The phone data:
Android-Version: 4.4.4
Baseband: M8974-A-2.0.50.1.16
Kernel: 3.4.0-gd59db4e
Build-Version: KTU84P
I used the "5.0 LRX21O-from-4.4.4 KTU84P" OTA file from here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
What's wrong? How can this file have been changed without root? Or is the system check wrong? Can I somehow fix this without unlocking the phone (loosing the data would be only the last option if nothing else works)?
Thanks
Hitzi
Click to expand...
Click to collapse
As per the error, '/system/lib/libnfc_nci_jni.so' isn't the stock file so it's been changed somehow or is corrupt. That or the OTA file is corrupt so double-check the md5 and try again
Thanks for your answer. But how can a file be changed or get corrupt if there is no acccess to it for the user? But let's go this way ... the file is changed or corrupt. How can I fix this?
I read that flashing the 4.4.4 system.img could possibly fix this problem. But flashing a *.img with fastboot works only with a unlocked bootloader.
Would this way work to boot into TWRP with a locked bootloader?
fastboot boot recovery.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/help/root-unlocking-bootloader-t2820628/page2
So maybe booting into TWRP with this fastboot command and then flashing the 4.4.4 system.img. But I don't know if this will work.
Or is there a way to replace a system file with fastboot or adb when the bootloader is locked?
I won't have access to the phone until monday so I'm collecting all possible solutions.
I have 3 RAZR HD phones from Rogers in Canada that are on 4.1.2 that are Rooted but the bootloader has not been unlocked and they have chainfire SuperSU on them. My wife got the OTA update notice days ago and said yes to it. She showed me her phone yesterday with the message that the software update failed. When it failed she was told by a friend at work that it failed because she had a SU on it so she did an uninstall on SU through the playstore and tried the update again that failed. I had told them (wife and daughter) not to make changes to them until i have a look at them, but well I guess that didn't work for one anyway. I let mine download the OTA update but said install later. I have a copy of the zip file now on my PC. She then did a factory reset (work friend) and tried the OTA update again. that failed.
Coupel questions.
1: I have been trying to find out how to unroot the phones so that the OTA update works but am getting a lot of conflicting info and not sure if it applies to my Rogers phones. Do they need to be unrooted to update? Do they need the bootloader unlocked to work around the OTA update After update how do i get Root again?
2: My wifes phone now is "stuck" partially unrooted? What i mean is I tried to put chainfire SU back on but it fails saying the binary cannot install and quits. It will not accept the OTA update from Rogers also. Apps that require Root on her phone do not work properly now also.
MECH_TECH said:
I have 3 RAZR HD phones from Rogers in Canada that are on 4.1.2 that are Rooted but the bootloader has not been unlocked and they have chainfire SuperSU on them. My wife got the OTA update notice days ago and said yes to it. She showed me her phone yesterday with the message that the software update failed. When it failed she was told by a friend at work that it failed because she had a SU on it so she did an uninstall on SU through the playstore and tried the update again that failed. I had told them (wife and daughter) not to make changes to them until i have a look at them, but well I guess that didn't work for one anyway. I let mine download the OTA update but said install later. I have a copy of the zip file now on my PC. She then did a factory reset (work friend) and tried the OTA update again. that failed.
Coupel questions.
1: I have been trying to find out how to unroot the phones so that the OTA update works but am getting a lot of conflicting info and not sure if it applies to my Rogers phones. Do they need to be unrooted to update? Do they need the bootloader unlocked to work around the OTA update After update how do i get Root again?
2: My wifes phone now is "stuck" partially unrooted? What i mean is I tried to put chainfire SU back on but it fails saying the binary cannot install and quits. It will not accept the OTA update from Rogers also. Apps that require Root on her phone do not work properly now also.
Click to expand...
Click to collapse
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Your best bet is to backup your data, RSDLite back to stock 4.1.2 and take the OTA. Make sure your bootloader is unlocked. Do not root or install custom recovery before the OTA has completed.
Rogers 4.4.2 OTA file
daswunderkid said:
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Click to expand...
Click to collapse
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
link to OTA file
MECH_TECH said:
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
Click to expand...
Click to collapse
will this work with spaces in it?
h t t p: // w w w. 4shared.c o m/zip/PUw0K63Ace/Blur_Version9821122002XT925RCI.h t m l
OTA file link
MECH_TECH said:
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
Click to expand...
Click to collapse
check the post now i put in a link with spaces and it posted.
Bootloader unlocked now
I have the bootloader unlocked now from Moto website. If I boot into AP Fastboot it is confirmed "Device is UNLOCKED. Status Code: 3" I am trying to flash a cmwrecovery.img to the phone. I get the following
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6824 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 1.997s]
finished. total time: 2.527s
I am not sure that the img is working. I execute the fastboot reboot and hold volume up/down and power select recovery and it stays on the boot logo for a long time then goes black logo comes back and boots normally. Not sure why its not working and do not know what i am doing wrong.
Any advise out there on this Rogers XT926 O.T.A. update fails
Now that the bootloader is unlocked I still cannot get the Rogers OTA to work. I got the 4.1.2 rooted again now and installed chainfire SuperSU onto the phone did a full unroot with SuperSU checked with root checker and now it says it is not rooted. I did a full factory reset wipe all data and downloaded the OTA update, let the OTA update try and it got 3/4 way through and failed. it keeps saying there is a critical update to run will download it and try but fails. I even tried to use the CWM custom recovery to run the update file and it gets error messages and fails. Not sure what to change in the OTA.img file to get this to take. Did anyone else figure out how to force it to complete?
Where is the Rogers stock 4.1.2
I found lots of 4.1.2 img files but I cannot be sure that any are for Rogers. How do I know that they are really plain stock files with now changes made to them, so that I can proceed?
RSDlite problems
CWGSM3VO said:
Your best bet is to backup your data, RSDLite back to stock 4.1.2 and take the OTA. Make sure your bootloader is unlocked. Do not root or install custom recovery before the OTA has completed.
Click to expand...
Click to collapse
I found the Rogers 4.1.2 file called
9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
I installed RSDlite 6.1.5
I ran the RSDlite and it sees my phone on USB port 1 info below
MEI/ESN/MEID: N / A
Technology: UMTS
Software Version: 9.8.2Q-8-XT925_VQL-12.2
Flex Version: N / A
Bootloader Version: 109b
DRM Version: N/A
I put the above zip file in the firmware folder
I pick it screen shows
Filename: 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml
Creation Date: 12/20/2012 21:34:28
File size: 2640
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
It asks to decompress or decompress and flash.
I picked decompress and flash
It says switching device to flash mode
phone reboots to ap fastboot I see device is UNLOCKED Status Code: 3
I get an error symbol and RSDlite says
Failed flashing process. Unknow fastboot command... Result FAIL
I cannot get the 4.1.2 to flash so I can continue with the OTA update.
What am I doing wrong
daswunderkid said:
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Click to expand...
Click to collapse
Here is the Link to 4.4.2 - Rogers Rom, been using it for some time, works flawless
There is an available OTA that is only available OTA. I believe this is the update that includes VOLTE. I'm rooted and have flashed TWRP. Even when I do a factory reset my phone is still flagged as being suspected of root, therefore I can't receive the update. Does anyone know where I can either find a stock rom to flash that has no root flag or perhaps another work around.
Android version 5.0.1
Kernel 3.4.0
Build LRX21Y
Software D85020f
That's all my software info. I'd really appreciate any help and I won't forget to thank you
If you have the software update prompt you should be able to update but will lose root. For safety flash stock recovery then run the update. If you dont have an att sim you may have to borrow one or buy a prepaid.
netomel said:
If you have the software update prompt you should be able to update but will lose root. For safety flash stock recovery then run the update. If you dont have an att sim you may have to borrow one or buy a prepaid.
Click to expand...
Click to collapse
It's not a prompt but when I go to software update it says there is a new version available. It goes through the entire DL and install and at the end rejects it and says "You're device is suspected of rooting."
Even after doing the factory recovery it returned the same message. That's why I need a stock rom to flash so the system won't think it's ever been rooted.
jlgarr86 said:
It's not a prompt but when I go to software update it says there is a new version available. It goes through the entire DL and install and at the end rejects it and says "You're device is suspected of rooting."
Even after doing the factory recovery it returned the same message. That's why I need a stock rom to flash so the system won't think it's ever been rooted.
Click to expand...
Click to collapse
Some people has been able to update with the stock debloated rom from cmulk. But thats why need to remove teto by flashing stock recovery. If you are still unable to update you have no other choice but flash stock 10d via LG FLASHING TOOL.
That's what I did. There is oneclick root for lollipop now though once you're updated.
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .