[Help] Can't flash system images to xt1031 Republic Wireless - Moto G Q&A, Help & Troubleshooting

So, last week I received the update to 4.4.4 on my Republic Wireless xt1031 (locked bootloader), then quickly realized that I preferred 4.4.2. After this, I downloaded the official republic wireless 4.4.2 firmware and attempted to flash it with fastboot, which didnt do anything but wipe my data. I then retried with mfastboot, which softbricked my phone. Whenever I try to flash any of the many stock firmwares I have found (tried Republic Wireless, Boost and a couple other firmwares, including a couple 4.4.4 firmwares), it seems that everything has been able to flash over and is working other than the system image files (system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 for the stock republic wireless firmwares). Whenever I try to flash any of the 3 over, I get an error on the phone:
hab check failed for system
Invalid PIV signed system image
and in my command prompt:
...\falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-key
s-cid6.xml>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (256840 KB)...
OKAY [ 8.056s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.464s
I've heard this can be an issue with a locked bootloader, but I've also read that people can flash stock roms with a locked bootloader as long as the firmware is specifically for your phone. Does anyone have any advice on this issue? I'm just about at my wit's end here. I have tried at least 6 different firmware, I've intentionally hardbricked it by destroying the bootloader, then reflashed it with blankflash and Motoflasher on two separate tries and still no luck. Currently, it goes through the boot process but just boots to a black screen. Any help would be greatly appreciated.

I had a nightmare with this problem, I think it is an issue with your partitions, do you have an unlocked boot loader? If so try installing twrp recovery and check the sizes of your partitions especially /system partition and post results, I never fixed the issue I eventually got it replaced by the store I bought the phone from.
PS unlocking boot loader will void your warranty so if possible try and get the store to replace device.
Sent from my XT1039 using XDA Free mobile app

jasond567 said:
I had a nightmare with this problem, I think it is an issue with your partitions, do you have an unlocked boot loader? If so try installing twrp recovery and check the sizes of your partitions especially /system partition and post results, I never fixed the issue I eventually got it replaced by the store I bought the phone from.
PS unlocking boot loader will void your warranty so if possible try and get the store to replace device.
Sent from my XT1039 using XDA Free mobile app
Click to expand...
Click to collapse
My bootloader is not unlocked and Republic Wireless does not allow the bootloader to be unlocked. One of the reasons I was trying to downgrade was because I was going to use sunshine to unlock the bootloader, but it doesn't work on 4.4.4. I got the gpt.bin from the official update for 4.4.4 on Republic Wireless that someone had posted here on xda, as it was the noly one that would flash successfully that I have found. According to the 4.4.4 debricking guide on here, you can flash the gpt.bin and motoboot.img from a 4.4.4 firmware, then after that flash the 4.4.2 files from the stock firmware of your choice.

Ahhh I see that's The same problem I had I followed most online suggestions from XDA and others and nothing worked for me so I got a replacement phone, is that possible for you to do, fingers crossed that if you do it will come with 4.4.2
Sent from my XT1039 using XDA Free mobile app

I am getting a replacement phone sent, hoping for 4.4.2!!!

Great news, I have my fingers crossed for you
Sent from my XT1039 using XDA Free mobile app

wulfep said:
I am getting a replacement phone sent, hoping for 4.4.2!!!
Click to expand...
Click to collapse
Did you get it unlocked?

wulfep, I am exactly in your situation. Were you able to find a workaround that allows you to flash the Republic Wireless Moto G 1stgen XT1031 phone with an alternate firmware, of the same Android Lollipop version but for other Spring-based MVNOs (i.e. Boost, US Cellular, Verizon etc)? And considering that the phone has the damn Motorola bootloader locked !?
Thanks.

Related

[Q] RAZR HD stuck in fastboot, cannot flash

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.

Rooting B324 on TL10?

Hello dear forum users.
I am new to Huawei but not to Android, having had (and rooted) devices since Eclair.
Yesterday, (Oct. 1st) I received my TL10 (European version). Looking through these forums I was excited to see that Lollipop had just been made officially available, so before doing anything else I upgraded. As I was on B125SP02 I had to first install B130, then B324.
Now, here's the thing. The rooting guides for Lollipop on these forums are for old stock ROMs and I don't want to risk bricking my new baby. I tried Kingroot, but it failed, so does anyone know if one of the rooting methods here will root B324?
Thanks in advance.
Install twrp recovery ..
Sent from my GT-P7320 using Tapatalk
Got it to work
paulopais said:
Install twrp recovery ..
Sent from my GT-P7320 using Tapatalk
Click to expand...
Click to collapse
Thanks.
I had to unlock first, which involved various running back and forth to find the unlock page on the HUAWEI site, then finding SN, IMEI and product ID. But I got there in the end.
:cyclops:
nope
afzal_b said:
Thanks.
I had to unlock first, which involved various running back and forth to find the unlock page on the HUAWEI site, then finding SN, IMEI and product ID. But I got there in the end.
:cyclops:
Click to expand...
Click to collapse
Well, I spoke too soon. TWRP detects that the phone isn't rooted and proposes swipe to root. I did it and there is a small screen that flashed too fast to read, then the phone reboots, but unfortunately with out being rooted.
afzal_b said:
Well, I spoke too soon. TWRP detects that the phone isn't rooted and proposes swipe to root. I did it and there is a small screen that flashed too fast to read, then the phone reboots, but unfortunately with out being rooted.
Click to expand...
Click to collapse
you have twrp installed ? if so, download https://download.chainfire.eu/supersu and install zip over twrp and its done
how did you unlock bootloader? the online tool need huawei id to register with me phone number and my country is not listed.
By email
Sent from my GT-P7320 using Tapatalk
Thanks again
Thanks - worked
You don't have to login with phone number
apopet26 said:
how did you unlock bootloader? the online tool need huawei id to register with me phone number and my country is not listed.
Click to expand...
Click to collapse
You can also login using with a Facebook login, which is how I did it.
afzal_b said:
You can also login using with a Facebook login, which is how I did it.
Click to expand...
Click to collapse
Yes I discovered that too after hours of struggling. Now I'm rooted and flashed back stock recovery. First time in these things and I feel proud I didn't brick anything [emoji13] After days of reading everything looks super clear I can root anything now [emoji41]
Still waiting for working xposed version though...
Send from Mate 7 using tapatalk
I got the Bootloader Unlock code and I unlocked my Mate 7 using the command "Fastboot oem unlock <code>" and it showed "done". I repeated the command and it showed "remote: already user unlocked", which convinces me that the bootloader is finally unlocked.
However, when I tried to flash TWRP recovery using "fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img", I still get the same error "FAILED (remote: image verification error)". I have checked the XDA pages and the TWRP version seems to be right, as I used the link (https://basketbuild.com/devs/asyan4ik/hwmt7_l09) given on this post only.
Sequence as follows:
Fastboot Flash Recovery twrp_2.8.7.0_mate7_5.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (12644 KB)...
OKAY [ 1.384s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.404s
Is there a separate TWRP version for MT7-TL10 version? If yes, can someone provide the link, please?
This is very frustrating because it's a great phone and not being able to root is very limiting!
Xposed runs but not all modules as the Huawei theming messes with it.
As for TWRP, I don't like it and only use CWM which is what I have in my Mate7.
I tried various ways including moving back to KitKat. That landed me on a bricked device.
I then went to the website of Huawei to download the rescue package. After lot of struggle, I could get the phone to boot.
The Problem: I have been thrown off to a Chinese KitKat ROM (See attached) and no matter what I do, I am unable to flash an official International Channel ROM. The flash fails every time.
I am looking for a way to move back to either KitKat 4.4.2 or 5.1.1 B324 version of Android 5.1.1 (MT7 TL10 Model). If there is no root for 5.1.1, I would prefer to stick to the latest KitKat ROM with root.
Help.
Back to Stock Lollipop with the help of @acbka
Now need to root it with a locked bootloader. No way to unlock bootloader - even though 'Phone Unlocked' is shown on bootloader screen, yet I can't flash custom recovery through Fastboot.

Signal Drops after some call time in VOLTE [Signal is dropped for both SIMs]

I have a Moto g3 XT1550 Dual sim phone, Recently I tried out Lineage OS. Later I reverted to stock by flashing stock firmware via fastboot.
Now after some call time, signal is lost for both the SIMs(I have dual SIM cards) and call is dropped. After some time signal would be back and the cycle continues.
There is one more weird thing I noticed; While flashing the stock firmware (Yes, I tried flashing a couple of times), when I try to flash
Code:
fastboot flash partition gpt.bin
It returns error as follows,
Code:
(bootloader) Preflash validation failed
FAILED (remote failure)
I have an Unlocked bootloader.
woodrez said:
I have a Moto g3 XT1550 Dual sim phone, Recently I tried out Lineage OS. Later I reverted to stock by flashing stock firmware via fastboot.
Now after some call time, signal is lost for both the SIMs(I have dual SIM cards) and call is dropped. After some time signal would be back and the cycle continues.
There is one more weird thing I noticed; While flashing the stock firmware (Yes, I tried flashing a couple of times), when I try to flash It returns error as follows,
I have an Unlocked bootloader.
Click to expand...
Click to collapse
Don't know about the signal loss but the error you're getting while flashing is because you're flashing an older firmware on a newer one. The firmware you're flashing must be the same or newer than the one on you're phone for successful flashing.
adityak1303 said:
Don't know about the signal loss but the error you're getting while flashing is because you're flashing an older firmware on a newer one. The firmware you're flashing must be the same or newer than the one on you're phone for successful flashing.
Click to expand...
Click to collapse
Thanks for your reply. I have read about this prior to flashing; However, I have read that if the bootloader is unlocked, this error shouldn't occur. Correct me if I'm wrong.
woodrez said:
Thanks for your reply. I have read about this prior to flashing; However, I have read that if the bootloader is unlocked, this error shouldn't occur. Correct me if I'm wrong.
Click to expand...
Click to collapse
The error will occur even if the bootloader is unlocked. Skip bootloader and gpt.bin files while flashing. The phone should boot up after that.

[ZIP]The Newest Firmware&Modem From MIUI 9 China Beta

This is a newest MIUI 9 China Beta "s TZ &Modem
Baseband:BO.2.6.c1.2-0818_1948_87b78d2
Link:https://yadi.sk/d/wdmLsruk3MSQJr
Flashable ZIP File
Please Use TWRP
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: DO NOT flash this on official Lineage with Lollipop bootloader, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot which is also pretty useless, since your bootloader is locked
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
PeterMarkoff said:
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: do not flash this on official Lineage, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Click to expand...
Click to collapse
kindly type, fastboot oem device-info on fastboot mode with phone pluged in,hope it didnt lock your bootloader.
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
PeterMarkoff said:
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
Click to expand...
Click to collapse
Have you unlocked your phone officially?
Because i flash this too and had no problem at all.
?
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
PeterMarkoff said:
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
Click to expand...
Click to collapse
YES,This is a Nougat Bootloader,you must unlock bootloader in official tools after you install this file in twrp
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
buktore said:
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
Click to expand...
Click to collapse
****ing ask before do something if you're not so sure about it.
Has anyone noticed any improvement with the new radio?
Hello. Has anyone got a link to the latest firmware available for a MI4C. I'm not after the official ROM, just firmware workable with ROMs. I think the last update I done was through andropax link https://androidfilehost.com/?w=files&flid=155424 is there a way I can also find out which firmware I have installed I forgot.
Is this the latest > https://androidfilehost.com/?fid=890278863836288705
fw_libra_miui_MI4c_V9.5.2.0.NXKCNFA_81f363e363_7.0
& will it run dev ROMs?

[XT1575][FIRMWARE][OFFICIAL] Moto X Pure Factory Firmware Nougat NPH25.200-22

I take no credit for this, thank the Motorola-Firmware-Team on Android File Host, and you can follow any leaked firmware on their Twitter feed.
I no longer have a Moto X Pure Edition, so I can't personally vouch for this firmware, but it seems like it is a totally legit full factory firmware image of Nougat NPH25.200-22 for flashing in fastboot.
This is the "official" full factory image of Nougat NPH25.200-22 and NOT the OTA file. It can be used for a clean flash and to relock the bootloader which is recommended to pass SafetyNet API checks if you are planning on staying stock and not rooting.
Flashfile.xml shows: version="clark_retus-user 7.0 NPH25.200-22 21 release-keysM8992_1255331.29.01.88.09R", MD5 matches, and all dates are correct.
This is ONLY for the Moto X Pure Edition, Retail US (RETUS) variant. I have no information on any other firmware or device.
Tested and verified as official Nougat factory ROM image by @Andromendous
This image is NOT flashable in TWRP, like all factory images it is flashed with fastboot in the bootloader... How to flash:
Code:
fastboot oem lock begin (if wanting to re-lock bootloader, othewise use `fastboot oem fb_mode_set`)
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock (only if you used `fastboot oem lock begin`, otherwise end with `fastboot oem fb_mode_clear`)
fastboot reboot
See https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 for detailed instructions
Downloads
Original source: https://androidfilehost.com/?fid=889964283620765304
Google Drive mirror: [removed]
@acejavelin: Since you have been one of the guru's on this phone, can this file be flashed in fastboot directly if I am on stock MM android December update rooted with Magisk and TWRP installed? I just want to make sure that when I am ready to take the plunge, I can take the minimal work procedure since I factory wipe after all major updates anyway.
Does this mean people who haven't received 7.0 OTA can flash this ROM and get Nougat without any complications such as corrupted bootloader and stuff? Also read multiple times that downgrading to 6.0 and again upgrading to 7.0 via OTA corrupts the bootloader leading to hard brick (which is now solver using external SD), will flashing this would solve this too?
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
acejavelin said:
Yes... This is the pure stock factory image for Nougat, it can be flashed, used to lock the bootloader, fix the "preflash validation" issues, etc. like any factory image.
There should be no issue applying it over a downgraded version, as long as you flash the entire image.
Click to expand...
Click to collapse
Great! I plan on holding on to this phone for about another 6 months or so and might as well get the update. Will probably go over to stock nougat in December. Custom ROMs just always seem to have at best some minor issue(s) that prevents me from sticking with them.
Dude Ace you are the f-ing man. Thanks for the find.
I flashed it manually while on Hashbangs LOS rom. I was stuck on 6.0 modem and tried to just flash the modem, which made me lose sim service. I then flashed the entire imagine manually and booted just fine.
Now I'm back to LOS with 7.0 modem and so far so good. Hashbang is doing a great job, he's already cleaned multiple bugs just today.
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
schneid said:
i am already on 7.0 but putting this away for the future. Can you flash the zipped XML or do you need to unzip and flash each piece individually? Thanks.
Click to expand...
Click to collapse
It's a factory image... Have to flash each piece manually with fastboot, this is not a flashable TWRP or other recovery image
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
We don't know that for sure... NPH25.200-22 is what has been rolling out to Sprint, T-Mobile, and AT&T devices, but it seems that Verizon users are getting NPH25.200-23 according to one verified (via screen shot) report on Lenovo's official forum.
The issue is we know the Moto OTA server keeps track of what device get's what version, if you flash this it won't know you have it so if a future OTA update comes out, you might be offered it via push and will have to wait until it's available by pull.
andromobilogy said:
So no difference between flashing this and a possible future OTA update one? I downgraded from custom 7.1 to stock 6 and now been weeks waiting for this 7 OTA update which probably wont even see the 2017.
Click to expand...
Click to collapse
Yes. There's a huge difference. With this you wont brick your phone.
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
CLETjB said:
Can we Re-lock bootloader with this version?
AND...
If you flash this version NPH25.200-23, will you still be able to install a SIM from another carrier, say Sprint, T-Mobile, or AT&T, and not be pigeon holed into a specific wireless Plan from VZW with their own Propietary APPs like VZW Cloud?
Click to expand...
Click to collapse
Yes, you can relock... unless you have already applied NPH25.200-23, otherwise you should be able to relock from ANY version out there currently.
We don't know what's up with NPH25.200-23 for sure though... recently Moto has been doing "different" versions for Verizon users that don't seem to get to anyone else, we also see it in the Moto G5+, and we don't know the differences either. Most likely it's just a minor VZW specific change and can be ignored. If the update does get pushed later, you should have no issues taking the OTA update when on this firmware, it is the official factory image.
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
ghitus said:
@ acejavelin
I know that I'm a bit OT, but I think that this thread is the most suitable for my request: do you know if there is a nougat factory image available also for the xt1572?
Thanks in advance,
Gaetano.
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
As I stated in the first post... no, I have idea or information about any other images for other variants and I suggest following MotoFirmware123 on Twitter as that is the best place to find leaked firmware. Motonovo has gotten very tight on letting firmware get out, but if it becomes available this is likely where it will come from, IF it ever gets leaked.
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Oaklands said:
Just curious. I recently moved on to a Note 8 and want to give my son my Moto X Pure. Does this file put default recovery on the phone as well? I tried to factory reset it last night (had it rooted with TWRP installed) and now it will only boot into TWRP. I just want it all stock for him.
Thanks
Click to expand...
Click to collapse
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
acejavelin said:
Yes, it is an official stock firmware image... if properly flashed with fastboot it will restore the device to 100% factory conditions, including recovery.
Click to expand...
Click to collapse
Thank you. His phone is now ready.
Finally !Thanks, man!
Now I just flash via fastboot and avoid all the OTA updates process.
you are the man!

Categories

Resources