Related
Hello!
I own a FRD-L19C432 device loaded with B120 FW, TWRP flashed to erecovery, the recovery partition is stock (?) since I haven't flashed anything on it and it is also rooted.
A few days ago, I got the notification of the availability of B131 update. According to some info I've read over the web, the erecovery isn't/wasn't used for anything, so I tried my luck and proceeded with updating operation from UI. It booted to recovery, failed to install, showed some error and booted to OS, that stills on B120.
Introduction made, the question is:
I already downloaded the FRD-L19C432B131 full update zip, can I simply flash it through the dload method, or, must I first unroot and flash stock B120 recovery in order to perform the dload flash?
If so, where can I get the B120 stock recovery and erecovery? I'm not finding it while using the Firmware Finder app by Team MT.
Hope you can give some help.
Tks,
RM
you can extract the recovery.img using huawei update extractor and then flash via adb or the multitool
jkccl9 said:
you can extract the recovery.img using huawei update extractor and then flash via adb or the multitool
Click to expand...
Click to collapse
Thank you for trying to help, but that's not what I'm asking in first place:
I already downloaded the FRD-L19C432B131 full update zip, can I simply flash it through the dload method, or, must I first unroot and flash stock B120 recovery in order to perform the dload flash?
Click to expand...
Click to collapse
Thank you.
RM
omartins said:
Thank you for trying to help, but that's not what I'm asking in first place:
Thank you.
RM
Click to expand...
Click to collapse
well you have to unroot and install stock recovery before being able to update
jkccl9 said:
well you have to unroot and install stock recovery before being able to update
Click to expand...
Click to collapse
Stock recovery from B120, right? If so, where can I find this recovery since I'm not finding the full B120 FW zip?
omartins said:
Stock recovery from B120, right? If so, where can I find this recovery since I'm not finding the full B120 FW zip?
Click to expand...
Click to collapse
Try huawei firmware Updater by team mt (can't remember full name) to search for the last update and extract using tool from post 1 ^^
omartins said:
Hello!
I own a FRD-L19C432 device loaded with B120 FW, TWRP flashed to erecovery, the recovery partition is stock (?) since I haven't flashed anything on it and it is also rooted.
A few days ago, I got the notification of the availability of B131 update. According to some info I've read over the web, the erecovery isn't/wasn't used for anything, so I tried my luck and proceeded with updating operation from UI. It booted to recovery, failed to install, showed some error and booted to OS, that stills on B120.
Introduction made, the question is:
I already downloaded the FRD-L19C432B131 full update zip, can I simply flash it through the dload method, or, must I first unroot and flash stock B120 recovery in order to perform the dload flash?
If so, where can I get the B120 stock recovery and erecovery? I'm not finding it while using the Firmware Finder app by Team MT.
Hope you can give some help.
Tks,
RM
Click to expand...
Click to collapse
It's weird and sad to hear that you flashed twrp to erecovery.
Let me explain u briefly what erecovery does . when u use dload method (while flashing an update.app) , erecovery extracts all .img and .bin files and later it flashes the each file (image files) to its respective partition .
In ur case. The normal stock recovery flashed the update.zip which was included in the script . but it failed to extract update.app in the update.zip and finally output u got is error.
Solution:
The only solution for this problem is ..
Download a full update package of stock ROM...
Extract Update.app (use huawei update extractor) and then find erecovery.IMG
Install adb and fastboot drivers ..
Put your phone in fastboot mode .
Connect to PC ..
In the terminal (command prompt) , type this command and hit enter .
fastboot flash erecovery erecovery.img
(From here u can reinstall the update.zip ) if it fails .
And then try to shutdown the phone , later put full update.app in dload folder ..
Use the 3 button combination to install full package of update.app and thats it .
It reboots to stock again .besure to take a backup of your data before attempting above step . after everything done check for update from settings and install it normally
hello!
Thanks for a proper answer
At the moment I'm stuck (paused) at the TWRP backup operation, since I don't seem to be able to perform a full back to internal storage (with the previous NEXUS phones I owned it was possible...) I need first to get an USB-C adapter in order to use USB OTG to perform the safety backup.
After That I'll flash B120 stock recovery and erecovery, unroot and dload the new FW version.
Meanwhile, another question: Using the FW Finder APP from Team MT on Windows it gets a FRD-L19C432B131 result, while on the Android version of the same AP it only finds B130, not B131 (?). On the other hand, I can only find the B120 full FW over Android APP, and don't seem to find it while using Windows... Any idea why this occurs?
RM
Hello!
Task accomplished! TWRP full backup made, flashed stock recoveries from B120 and after that flashed B131 update.app though dload method.
Everything went OK except for the fact I got bootloader relocked after the second flash. I miss the simplicity of the Nexus devices...
With the TWRP backup made before I was able to restore most of the definitions though. It would be nice to digg a workaround to flash update.app without getting bootloader relocked...
I wonder if extracting boot, system and recoveries IMGs and flash all this through fastboot wouldn't work!? Did anyone tried?
RM
As the Nougat is rolling out for XT1572 devices, here's the guide for Flashing Stock Firmware using Fastboot for receiving Nougat OTA.
(Inspired by @acejavelin guide)
Prerequisites:
1) USB Drivers (Not needed for Windows 10)
2) Fastboot installed and working.
3) Stock Factory Images for Moto X Style (XT1572): https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
Procedure:
1) Open a terminal or command prompt (Shift + Right click) window into the directory that contains the firmware files you extracted above.
2) Reboot the phone in Fastboot Mode (Reboot to Bootloader) and connect the USB Cable.
3) To verify if everything is perfect type in:
Code:
fastboot devices
If it shows your device serial number then you can be sure that it's properly connected.
4) Read the 'Notes' below.
6) Before proceeding, flash this commands to clean up the previous system's mess. This will get rid of the '(bootloader) Preflash validation failed' error when flashing gpt.bin (partition table).
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
5) Here's the actual commands to Flash the Stock Image. Please Enter them One-by-one, Don't create any .bat files or copy and paste the entire section.
Code:
[STRIKE]fastboot getvar max-sparse-size[/STRIKE]
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 modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
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 fb_mode_clear
Make sure you read whatever is happening on the prompt, do not miss any errors. (Scroll up the prompt and re-check everything before booting)
Notes:
1) This won't Lock your bootloader but you will be able to get OTA's.
2) For receiving Nougat on RETASIA Dual Sim, download: XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
There will be a 44mb update already queued when you boot the device. It will update the device to December 2016 Security Patch.
Reboot and you will be able to get Nougat OTA (911mb), if eligible.
3) If you didn't get the OTA Update, Flash this Nougat OTA after updating to December 2016 security patch: https://forum.xda-developers.com/moto-x-style/general/ota-nph25-200-15-retasiads-t3636765 (Credits: @Sagar_1401)
4) Different firmwares may contain a different number of system.img_sparsechunk.X files, you must flash the number you have in your firmware image in order. From what I have seen, most 5.1.1 firmwares have nine, 6.0 has eight, and 6.0.1 has eleven sparsechunks.
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
There is no need to do fastboot getvar max-sparse-size, that is just for RSD Lite to check your maximum system chunk size, when doing it manually it does nothing.
Not really sure why this guide is needed, there are already a few out there that are basically identical.
Nice guide @antariksh thanks for this.
i will be flashing from my current version 6.0.1_MPH24.107-58 (seemingly higher version) tomorrow.
will update once i attempt this.
Quick tip if you can't get SafetyNet passed with Magisk V13.1 or V13.2
For Stock Nougat as we don't have boot.img
1) Backup boot with TWRP
2) Restore boot with TWRP
3) Flash Magisk zip
4) Reboot and Install Magisk Manager v5+
This won't get your SafetyNet passed.
5) Open Magisk Manager and once again press 'Download and Install'
This will automatically download and install the latest Magisk and after a reboot your SafetyNet will be passed.
antariksh said:
5) You must use a factory firmware image that is the same version as what you have installed or newer to successfully relock the bootloader, you cannot just grab the old (shipped) version from Moto's site. If you attempt to use a firmware image that is older than what you have installed currently, you will receive a Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
Click to expand...
Click to collapse
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
trannamcloud said:
I got 6.0.1 ROM, how do i downgrade to 6.0? I try to flash to 6.0, it's shown message like above
Click to expand...
Click to collapse
titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update
So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
trannamcloud said:
Thanks a lot!
I go back to 6.0.1 Retapac, with security pack 1-Mar-2016, an now waiting for official Nougat OTA update
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
pradeepvizz said:
So I was on 6.0.1 as well and used the 18-8 firmware to downgrade to 6.0. had the same preflash validation error, i flashed gpt the second time after the error occurred and completed the flash like normal. Everything just worked perfectly fine after that. Got the security update to December and nought!
Edit : I did all of this keeping my bootloader unlocked.
Sent from my HTC 10 using Tapatalk
---------- Post added at 08:05 AM ---------- Previous post was at 08:01 AM ----------
You need to go to 6.0 and not 6.0.1.. The firmware to download is XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs
titanworm said:
hi guys,
My XT1572, previous rom version 6.0.1_MPH24.107-58-5 and I reflashed to 6.0 MPHS 24.49-18-8 successfully but I can not update December patch security 2016. I attempted to flash Nougat on RETASIA Dual Sim in Recovery but error FingerPrinter. Do I need any tricky ? Thank
Click to expand...
Click to collapse
Last week I flashed the MPH24.107-58-5 (6.0.1) thinking that this was the latest version. But then I TWRP restored back to my Custom ROM as there was no Nougat OTA.
On this Saturday I was able to flash the MPHS 24.49-18-8 without any issues.
Try flashing the gpt.bin twice and don't try to lock your bootloader.
trannamcloud said:
So have you upgrade to Nougat yet?
I unlocked bootloader already, so could i bypass preflash validatation error as your guide? My phone said "downgrade failured " in bootloader screen logs
Click to expand...
Click to collapse
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
Click to expand...
Click to collapse
I have upgraded to Nougat successfully with no problems.
pradeepvizz said:
i didn't see what the bootloader screen logs said, but when you get the error, you have to reflash the same thing again.
I have upgraded to Nougat successfully with no problems.
Click to expand...
Click to collapse
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
acejavelin said:
You can't go from 6.0.1 to 6.0 completely... Your bootloader and partition table cannot be downgraded and are actually different than on 6.0, they work (meaning 6.0 will boot} but it isn't a match. You cannot take an OTA to 18-16 or any other version because of the mismatch.
The only way to upgrade is go back to 6.0.1 then take the OTA to Nougat.
Click to expand...
Click to collapse
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
Same me, the only way is back to 6.0.1 now
titanworm said:
yep, I had to return to XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml although I reflashed XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml completely on my devices and I was not able to upgrade to December patch. Now, my Android security patch level is September 1,2016. Did we have December 2016 patch for this MPHS24.107-58-5 and Asia DS? @acejavelin
Click to expand...
Click to collapse
trannamcloud said:
Att image for your ref, i got preflash error when trying to flash gpt.bin. And i found problem as Mr @acejavenlin said below, saidly i have to go back 6.0.1 again
Click to expand...
Click to collapse
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?
hi, guys
What is your Bootloader version, mine is BL: A0.4C for 6.0 Retasia DS. I see 6.0.1 Retasia DS has BL: A0.4A. Which versions is higher? With BL: A0.4C for 6.0 Retasia DS, I cannot flash to 6.0.1 with GPT.bin and Boot.img.
I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.
duttandy said:
I'm currently on xt 1572 retasia ds MPHS24.49-18-16 but with bootloader unlocked and twrp installed. Can someone guide me to the December 2016 file so that I can restore to stock or the nougat file so that I can directly update my phone through fastboot method. Thanks in advance.
Click to expand...
Click to collapse
We don't have either... The best you can do is hope someone can do a TWRP backup of recovery you can restore, it needs to be the same variant and version.
pradeepvizz said:
i am not expert in Moto flashing, don't honestly have the patience to wait for the OTA from 6.0.1 to 7.
Was the build MPHS24.107-58 official for ASIA DS in the first place? i see posts on the lenovo forums asking 6.0.1 for Asian version which makes me think there was no official release. i wouldn't expect a OTA update if there was no official release of the 107-58 build in Asia. mine is a Asain version, what version is yours?
Click to expand...
Click to collapse
Confuse now. As you said, 6.0.1 build 107-58 is not official release, so maybe not receive OTA Nougat?
My version is Asian - retapac, 6.0.1 - build 107-58 with security patch 1-Mar-2016. It's unable to downgrade to any stock 6.0, as preflash error.
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!
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1572/EU
and also you can find other's firmware in it.
Good new for XT 1572 users!
Many thanks!
Okay. This looks really good.
A couple of noobish questions. This phones modem/OS version/Country/Pure-style mallarky is damaging my brain, compared to my old Samsungs..
I assume that this file needs to be extracted and each file installed via Fastboot. If so, how many of the files need to be installed. (Do I need Recovery.img, if I would rather not have to reinstall TWRP)
Even better, is it possible to flash this via TWRP ? (asking just in case...)
Can I flash this on top of my RessurectionRom 7.0.. Which was probably based on a MM modem ? Is everything needed in this package, or will the old modem result in no connection ?
Thank you in advance.
Great, thanks a lot! A small question, is there a difference between the NPH and NPHS versions of the firmware? I guess N stands for Nougat (since there's also L and M versions), but what does the S mean?
timmtn said:
I assume that this file needs to be extracted and each file installed via Fastboot. If so, how many of the files need to be installed. (Do I need Recovery.img, if I would rather not have to reinstall TWRP)
Even better, is it possible to flash this via TWRP ? (asking just in case...)
Can I flash this on top of my RessurectionRom 7.0.. Which was probably based on a MM modem ? Is everything needed in this package, or will the old modem result in no connection ?
Click to expand...
Click to collapse
extracted and flashed via fasboot or rsd
it can be flashed on any custom roms
it is not recommended to flash the file bootloader.img and gpt.bin
janpascal said:
Great, thanks a lot! A small question, is there a difference between the NPH and NPHS versions of the firmware? I guess N stands for Nougat (since there's also L and M versions), but what does the S mean?
Click to expand...
Click to collapse
it means that the version of this firmware is higher and newer,and the firmware has packed the latest security patch.
zi_mo said:
extracted and flashed via fasboot or rsd
it can be flashed on any custom roms
it is not recommended to flash the file bootloader.img and gpt.bin
Click to expand...
Click to collapse
Just what I was looking for. Thank you.
http://bigota.d.miui.com/V10.0.9.0....0.PDHMIXM_20190514.0000.00_9.0_3ded3e7b82.tgz
Is this final release? how did you find it?
http://en.miui.com/download-333.html
alienspl said:
http://en.miui.com/download-333.html
Click to expand...
Click to collapse
This is developer rom right? This is for test?
This oficial ROm MIA1 ,OTA
alienspl said:
This oficial ROm MIA1 ,OTA
Click to expand...
Click to collapse
How i can flash this? I have unlocked but i have still 8.0 with root. I can do this without clean personal data?
All you need to do is update in your phone's settings. Or in this way. http://en.miui.com/thread-807252-1-1.html
https://www.youtube.com/watch?v=z3ByqpYquQY&t=232s
Easiest way to upgrade without losing data is to reboot to bootloader, then use ADB tools and run the below commands:
Fastboot flash system system.img
Fastboot flash boot boot.img
(Copy system.img and boot.img from .tgz file)
Upgrade worked perfectly for me.
rambojambo21 said:
Easiest way to upgrade without losing data is to reboot to bootloader, then use ADB tools and run the below commands:
Fastboot flash system system.img
Fastboot flash boot boot.img
(Copy system.img and boot.img from .tgz file)
Upgrade worked perfectly for me.
Click to expand...
Click to collapse
And realy better is this pie than oreo?