New update for Moto G4/4+ started rolling (NPJS25.93-14-8). It has 56MB and it contains the 1st June 2017 security patch.
You can download it from here and install it by flashing it from SD card or sideloading it.
https://drive.google.com/file/d/0B_CvjgZQDGNDNFNIME5XNjRubFE/view
thanks a lot, here in my country barely i received nougat.
Would it make any issue if I have my device with a different kernel than the stock one? For rooting it I had to flash Elemental-X kernel (Moto G4 Plus).
Thanks.
cesardemi said:
Would it make any issue if I have my device with a different kernel than the stock one? For rooting it I had to flash Elemental-X kernel (Moto G4 Plus).
Thanks.
Click to expand...
Click to collapse
For flashing the OTA, you must flash to stock Nougat rom (including kernel), otherwise the phone will enter in bootloop. After you install the OTA, you can flash the EX kernel and root it again.
A few other things to note about this update:
Looks to require NPJS25.93-14-4 (the March 2017 v7.0 update) to install from (that fastboot update is here if you need it: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )
Bootloader updated to B1.06 (March 2017 had B1.05) - I imagine this fixes the critical security vulnerability as noted in the May 2017 security update (CVE-2016-10277 https://source.android.com/security/bulletin/2017-05-01#eop-in-motorola-bootloader ) EDIT - it seems that once this patch is flashed, downgrading your device (especially when flashing the GPT/bootloader from an older stock ROM) may well risk bricking your device! This brick may also occur if you downgrade from this build without flashing GPT/bootloader and then install an OTA. Be aware.
Boot animation now has 'Motorola, a Lenovo company' at the bottom (not sure if that was there previously) when the logo flips from Lenovo to the M symbol.
IMEI SV seems to be changed to 9 (think it used to be 8).
New logo seems to appear when charging with the device off (before the battery gauge appears)?
Also, if your OTA download is in your Download folder, when you're in stock recovery, I had issues trying to 'apply update via SD card'. Seems that 'mount /system' allowed me to navigate to the Download directory (don't know if that applies to everyone).
I was previously rooted on the March update with magisk v13 and ElementalX. I attempted to revert back to stock by:
Booting back into TWRP
Using the magisk uninstaller (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot to bootloader
Then using the following commands in adb to flash a stock NPJS25.93-14-4 boot and recovery image.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
However, upon trying to flash the OTA in the stock recovery, I encountered an error 7 (I think it was failing to load or verify system).
Flashing the following partitions from the NPJS25.93-14-4 stock ROM allowed me to flash the OTA in the stock recovery without erasing my data (bear in mind I was already fully updated to NPJS25.93-14-4 before rooting. I've also got a TWRP backup and Titanium backups to fall back to.) This should not affect your data, but ensure you have your data backed up regardless (always good practice when flashing anything that touches your system). I am not sure if all these partitions are required to flash the OTA if you were previously rooted. As always, if you're using these commands to roll back to stock from a rooted stock system, be prepared to factory reset if your system is not stable.
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Now I'm on the June 1 2017 update on a retgb XT1642 Thanks @georgeiulian89
Now to try and root this build
Flashed the zip from stock recovery. No issues
Thanks
Sent from my Moto G (4) using XDA-Developers Legacy app
Flashed on my XT1622. Can't say any good or bad about it.
Edit: The battery statistics seem to be more detailed now, first time ever that I have seen Firefox in it.
I tried to sideload the zip from my recovery. When I select Apply update from SD Card, the screen turns blank except for the
ge 0/0
Supported API: 0
None other keys are working.
I tried many times and still has no improvement. I am on Stock NPJS25.93-14-4
arunzone said:
I tried to sideload the zip from my recovery. When I select Apply update from SD Card, the screen turns blank except for the
ge 0/0
Supported API: 0
None other keys are working.
I tried many times and still has no improvement. I am on Stock NPJS25.93-14-4
Click to expand...
Click to collapse
Sideload it from the PC.
Just need to put it out there - Do not try to downgrade after you have upgraded to the latest OTA. I did. Hard bricked my phone.
georgeiulian89 said:
Sideload it from the PC.
Click to expand...
Click to collapse
I had sideloaded it via ADB but was curious to know about the issue. Do you have any idea about how to sort this issue?
arunzone said:
I had sideloaded it via ADB but was curious to know about the issue. Do you have any idea about how to sort this issue?
Click to expand...
Click to collapse
Do you have an SD card, and if so, what card is it? Just wondering if having an SD card might allow the recovery down as it reads?
echo92 said:
Do you have an SD card, and if so, what card is it? Just wondering if having an SD card might allow the recovery down as it reads?
Click to expand...
Click to collapse
Yes. I have Samsung Evo Plus 64 GB MicroSDXC Card. I tried place the zip file in internal memory and sd card. Still no improvement.
I also tried after removing the SD Card.
Can i flash it on my Indian version of moto g4 plus build no. Is NPJS25.93-14-4
VivekBhagat said:
Can i flash it on my Indian version of moto g4 plus build no. Is NPJS25.93-14-4
Click to expand...
Click to collapse
yes, you can.
arunzone said:
yes, you can.
Click to expand...
Click to collapse
Okk thanx
echo92 said:
Now to try and root this build
Click to expand...
Click to collapse
Did you succeed?
anirudh.m said:
Did you succeed?
Click to expand...
Click to collapse
Just install Vegito 6.6/EX kernel and flash superuser 2.79SR3.
Adb sidelined update worked thanks
i flashed 93-14-4 then this ota,rooted and working fine thanks
Related
Hi,
Current Configuration
1. Recovery : CWM Recovery
2. Device: XT1033 Indian Variant
3. Android Version: 4.4.4
4. ROM: Stock
5. Root Status: Rooted
I'm trying to install OTA vai cwm recovery but it's giving me following error.
Code:
Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.0.2/LXB22.46-28/30:user/release-keys; this device has motorola/falcon_retbr_ds/falcon_umtsds:4.4
E:Error in /cache/Blur_Version.210.12.40.falcon_umtsds.AsiaRetail.en.03.zip
(Status 7)
Installation aborted.
I'm stuck here since last 3-4 hours
Today Issue got resolved.
Steps I Followed.
Flashed Stock Firmware and all
Use this
If you want to preserve your Media and settings
Don't execute this
mfastboot.exe erase userdata
Click to expand...
Click to collapse
Then simply put your OTA in SD Card and install it from stock recovery.
ant24x7 said:
Hi,
Current Configuration
1. Recovery : CWM Recovery
2. Device: XT1033 Indian Variant
3. Android Version: 4.4.4
4. ROM: Stock
5. Root Status: Rooted
I'm trying to install OTA vai cwm recovery but it's giving me following error.
Code:
Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.0.2/LXB22.46-28/30:user/release-keys; this device has motorola/falcon_retbr_ds/falcon_umtsds:4.4
E:Error in /cache/Blur_Version.210.12.40.falcon_umtsds.AsiaRetail.en.03.zip
(Status 7)
Installation aborted.
I'm stuck here since last 3-4 hours
Click to expand...
Click to collapse
you must using stock recovery
indrasatrya said:
you must using stock recovery
Click to expand...
Click to collapse
So is there any other way that i can install this OTA. Without messing above configuration ?
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
today i downloaded the ota and while it was being insatalled about 25 % the screen displayed "error" and the device booted up and it said update unsuccessful....
what to do.......... unlocked bootloader + UNrooted moto g xt1033....
anooj21m said:
today i downloaded the ota and while it was being insatalled about 25 % the screen displayed "error" and the device booted up and it said update unsuccessful....
what to do.......... unlocked bootloader + UNrooted moto g xt1033....
Click to expand...
Click to collapse
Reflash the ASian XT1033 4.4.4 firmware and try again. There are numerous guides regarding this OTA flashing business in the general section. You might want to check them out.
pfufle said:
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
Click to expand...
Click to collapse
Thanks for reply! I'll try this today.
Meanwhile I tried following and installed cm12 it worked.
1. format all partitions except /sd/media
2. Flashed cm11 with gapps
3. Faced Boot animation loop (Please some explain why ? )
4.Flashed CM12 (It Worked using it now)
pfufle said:
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
Click to expand...
Click to collapse
Okay I tried these steps.
First Flashed Stock Recovery
Unroot from Supersu
Tried flashing OTA update through recovery but same error.
Any suggestion!
ant24x7 said:
Okay I tried these steps.
First Flashed Stock Recovery
Unroot from Supersu
Tried flashing OTA update through recovery but same error.
Any suggestion!
Click to expand...
Click to collapse
flash the stock firmware with stock recovery, stock 4.4.4 dual sim asia retail
pfufle said:
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
Click to expand...
Click to collapse
woozie.2007 said:
flash the stock firmware with stock recovery
Click to expand...
Click to collapse
After flashing Firmware is there any chances of data loss ?
ant24x7 said:
After flashing Firmware is there any chances of data loss ?
Click to expand...
Click to collapse
yes, the phone will be like new
woozie.2007 said:
yes, the phone will be like new
Click to expand...
Click to collapse
Wait I know i'm asking questions like a noob. But data loss means
/data/media This partition will also get affected
ant24x7 said:
Wait I know i'm asking questions like a noob. But data loss means
/data/media This partition will also get affected
Click to expand...
Click to collapse
why you dont save all on your pc? after that flash a clean stock 4.4.4
woozie.2007 said:
why you dont save all on your pc? after that flash a clean stock 4.4.4
Click to expand...
Click to collapse
But Already I'm on Stock ROM with Stock Recovery and Device is unrooted.
Do I still need to flash KitKat Firmware ?
ant24x7 said:
But Already I'm on Stock ROM with Stock Recovery and Device is unrooted.
Do I still need to flash KitKat Firmware ?
Click to expand...
Click to collapse
is recomended to do a factory reset before a clean install, if you dont want to do this, you can try to flash without factory reset, but if the flash fail, you must do a factory reset....when you root the phone some libs files is modified
woozie.2007 said:
is recomended to do a factory reset before a clean install, if you dont want to do this, you can try to flash without factory reset, but if the flash fail, you must do a factory reset....when you root the phone some libs files is modified
Click to expand...
Click to collapse
Found these steps on other thread to Flash Stock 4.4.4
My Doubt is second last step where it says erase userdata. Does it wipe out my media partition too ?
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
ant24x7 said:
Found these steps on other thread to Flash Stock 4.4.4
My Doubt is second last step where it says erase userdata. Does it wipe out my media partition too ?
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
Click to expand...
Click to collapse
yes, will erase all
woozie.2007 said:
yes, will erase all
Click to expand...
Click to collapse
Thanks! Backing up Entire phone. Will update here after flashing.
ant24x7 said:
Thanks! Backing up Entire phone. Will update here after flashing.
Click to expand...
Click to collapse
Skip the second last step if you don't want to bother backing your phone up.
pfufle said:
Skip the second last step if you don't want to bother backing your phone up.
Click to expand...
Click to collapse
You saved my lots of time!
I flashed stock firmware without erasing userdata. And it worked. Now successfully updated to 5.0.2. With my all Media and settings preserved.:laugh::laugh:
Thanks a ton!
Hello guys, I need urgent help
I've upgraded my moto G 2013 to Lollipop retail UE a couple of days ago, everything was working perfect, I have it only rooted and few apps installed, nothing weird (no xposed). I wanted to install a new bootlogo but just in case I did a backup with the TWRP recovery.
I got a bootloop after flashing that, and when I wanted to restore my backup, it was not there! The ''restore'' tab in TWRP is empty, but I see the backup in my sdcard with the file manager of TWRP, it was done just 2 min before but it's just like if the recovery doesn't see it.
What can I do? I've tried with a factory reset but still in bootloop. Can I flash a Kitkat stock rom via fastboot? Because I've seen in some places that it can brick my phone... I was thinking, maybe I can flash the logo of the Lollipop UE rom?
Thanks in advance, I need your help
matapr0 said:
Hello guys, I need urgent help
I've upgraded my moto G 2013 to Lollipop retail UE a couple of days ago, everything was working perfect, I have it only rooted and few apps installed, nothing weird (no xposed). I wanted to install a new bootlogo but just in case I did a backup with the TWRP recovery.
I got a bootloop after flashing that, and when I wanted to restore my backup, it was not there! The ''restore'' tab in TWRP is empty, but I see the backup in my sdcard with the file manager of TWRP, it was done just 2 min before but it's just like if the recovery doesn't see it.
What can I do? I've tried with a factory reset but still in bootloop. Can I flash a Kitkat stock rom via fastboot? Because I've seen in some places that it can brick my phone... I was thinking, maybe I can flash the logo of the Lollipop UE rom?
Thanks in advance, I need your help
Click to expand...
Click to collapse
yes u can flash the kitkat stock rom but follow these steps carefully......
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
note:
u will receive some errors but no problem continue
after flashing kitkat will see flashing line on ur device every time u reboot ur device
just on and off ur screen and that would do it(fix the problem).
upgrade to lollipop to get rid of that flashing lines problem.
Thank you very much! any help to try to install the backup I have but isn't detected by TWRP recovery? Because I wouldn't like to lose all my data
Did you store it to an external SD card using a OTG device? Did you try changing the location for the restore file in TWRP?
If anyone can advise me on the solution to get upgrade to latest Android System version would be grateful.
Currently I am on India Stock 6.0.1 rooted and TWRP installed (System Version : 24.66.2.quark_reteu.reteuall.en.EU retin). I am getting system update notification to 24.201.2 version. However after download install/update, its failing. It gets restart to TWRP and had manually reboot back to System. And then system detect already downloaded update and starts auto restart. Is there solution to fix this issue....
Thanks
mohangj said:
Currently I am on India Stock 6.0.1 rooted and TWRP installed (System Version : 24.66.2.quark_reteu.reteuall.en.EU retin). I am getting system update notification to 24.201.2 version. However after download install/update, its failing. It gets restart to TWRP and had manually reboot back to System. And then system detect already downloaded update and starts auto restart. Is there solution to fix this issue....
Thanks
Click to expand...
Click to collapse
Your TWRP reference is the clue.
You need to be on pure stock to get any OTA updates. Your TWRP recovery is blocking that, since you don't have stock recovery. It will continue to fail.
You can either flash back to 100% pure stock (including recovery), take the OTA, then re-flash TWRP.
Or you can wait until the full firmware of that update is posted -- not just the OTA, which is not the full version -- and flash that full firmware version manually with ADB or RSD.
If you choose the latter method, until that full firmware is posted you can disable the OTA notification if it bothers you.
(Be aware that some minor OTA updates never have the full firmware version posted.)
ChazzMatt said:
Your TWRP reference is the clue.
You need to be on pure stock to get any OTA updates. Your TWRP recovery is blocking that, since you don't have stock recovery. It will continue to fail.
You can either flash back to 100% pure stock (including recovery), take the OTA, then re-flash TWRP.
Or you can wait until the full firmware of that update is posted -- not just the OTA, which is not the full version -- and flash that full firmware version manually with ADB or RSD.
If you choose the latter method, until that full firmware is posted you can disable the OTA notification if it bothers you.
(Be aware that some minor OTA updates never have the full firmware version posted.)
Click to expand...
Click to collapse
Thanks !!
First method is only the right approach as of now if decide to go for update. Second method won't be possible in near future as Moto Maxx won't be getting Nougat :crying:
Hi ChazzMatt,
I decided to upgrade to 24.201.2 version, had successfully installed stock rom and got OTA update to 24.201.2. Installed TWRP and SuperSu.
Everything is working fine except, it directly booting to TWRP, what could be the issue....any fix.
mohangj said:
Everything is working fine except, it directly booting to TWRP, what could be the issue....any fix.
Click to expand...
Click to collapse
There were other reports about people booting directly to TWRP recovery a few weeks ago, instead of to their system. Sorry, I can't remember the reason or the fix... But there were at least two other people who had that issue. I'll try to research and see if I can find it.
What version of TWRP are you using? Do you have the most recent?
bhb27 said:
TWRP update
twrp-3.0.3-0_MOD_3-quark.img
Download
===================
Feb-17-2016
===================
* All the previously TWRP Mod + the below
* Included the latest TWRP updates to this date
* Kernel Improves
* Latest updates and bugs Fix to the date of TWRP
* Most notable is the fix for Nougat Setting configurations be lost after the wipe of cache or a restore of the ROM Data, only new backups made on the latest MOD TWRP will have this featuring.
Click to expand...
Click to collapse
also, what version of SuperSu are you using? Once rooted with the older version, you can update to newest.
SuperSU v2.79 SR3
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
After flashing the newest TWRP and SuperSu, clear all caches in recovery and reboot. See if that fixes the issue?
OK, I found one of the incidents and I gave him the same advice, but never heard back about results.
However the issue was his phone was booting to the bootloader, not to his TWRP recovery. Is yours actually booting to the TWRP screen or to your bootloader?
Here's his incident, and there was also another I can't find right now. One was going to recovery, but this guy below was going to bootloader.
___
zeeshan.siddique4779 said:
I have isntall this rom every thing is fine , but when ever i restat my phone it goes straight in to bootloader , then i have to press enter to go to the system andriod ? Why it is so ?
Click to expand...
Click to collapse
ChazzMatt said:
Is it going to your TWRP recovery or actually your bootloader screen? Someone else reported this on another ROM and they were mistaken -- it was going to recovery, not the bootloader. I don't remember why. I'll look around and see if I can find the comment.
But try reflashing the latest version of TWRP for Quark by our Quark TWRP maintainer, found here:
twrp-3.0.2-0-Mod_04-quark.img (updated September 2016)
https://www.androidfilehost.com/?fid=529141701856462150
Can't hurt and may help.
You may not have the latest version of TWRP for our Quark, which was released in September 2016. Our Quark maintainer (who has official status) has newer modded versions on Android Host Files the official TWRP website has not yet integrated. It's their fault, not his. So, he provides the newest stuff to us in spite of their neglect.
Once you re-flash that TWRP, then reflash latest SuperSu and clear caches (it's an option you will see after your install something).
Reinstalling SuperSu can't hurt and also may help. Then, let it reboot.
[2017.01.03] SuperSU v2.79 SR2
https://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
When you initially rooted this ROM you had to use beta 2.62 SuperSu, but now you can update to newest if you haven't already.
Click to expand...
Click to collapse
zeeshan.siddique4779 said:
Yes it goes in bootloader screen not in recovery . Then i have to press power button to start phone .
What do you recomenr ? Any solution ?
Click to expand...
Click to collapse
ChazzMatt said:
Have you tried the the three things I suggested?
Install latest TWRP
Install latest SuperSu
Clear all caches in TWRP
In the meanwhile, I'll keep researching -- but any of those may somehow fix your issue.
Click to expand...
Click to collapse
zeeshan.siddique4779 said:
ok i will try and report you back . Thanks for help brother
Click to expand...
Click to collapse
ChazzMatt said:
Also try dirty flashing the ROM again. Boot into TWRP, flash the ROM, clear caches, reboot.
Click to expand...
Click to collapse
My issue is also exactly same what zeeshan.siddique4779 explained. Let me correct what I mentioned TWRP, its bootloader. When I boot/reboot it directly goes to Bootloader (-->START) there I have to press power button to boot system Android. I installed twrp-3.0.3-0_MOD_3-quark.img and cleared all cache, still issue persists.
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
mohangj said:
My issue is also exactly same what zeeshan.siddique4779 explained. Let me correct what I mentioned TWRP, its bootloader. When I boot/reboot it directly goes to Bootloader (-->START) there I have to press power button to boot system Android. I installed twrp-3.0.3-0_MOD_3-quark.img and cleared all cache, still issue persists.
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
Click to expand...
Click to collapse
He was on modified stock ROM for the Droid Turbo XT1254 -- a tweaked, debloated ROM by Computerfreek274 over in the other Quark forum. But same issue...
mohangj said:
I tried to go back to stock bootloader and install stock 6.0.1, but install is failing 3/22 error gbt.bin. I searched fix to this...didn't get. Currently I am running LOS 14.1 (root inbuilt in Developer option) with rebooting to bootloader issue
Click to expand...
Click to collapse
I think this is because with the OTA you took you installed a new bootloader. You can only downgrade to earlier firmware, even with an unlocked bootloader, if you omit gpt.bin from flashing. If you omit gpt.bin from the flash commands you can even downgrade back to Lollipop or Kitkat.
Thanks and I think you are correct. I tried to take stock update and bootloader broke.
How do I omit gbt.bin while flashing. So far I only flashed to stock with RSD. Please refer links, I will give a try.
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
mohangj said:
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
can u give me the link tostock rom? unable to find one i bricked my xt1225
jigar003 said:
can u give me the link to stock rom? unable to find one i bricked my xt1225
Click to expand...
Click to collapse
EVERY QUARK FIRMWARE EVER RELEASED
http://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
Well, almost the every Quark firmware. See, Motorola has released a few OTAs with security fixes and has not posted the full firmware yet. What @mohangj was able to do was DOWNGRADE to the last full firmware posted. And he was able to do that by having an UNLOCKED bootloader.
If your bootloader is still locked, you will only be able to flash the firmware you are bricked on (or higher), you will not be able to downgrade. And if Motorola has not yet publicly released the full firmware version, you have to send it to a repair center or something. Or wait until they release the full firmware publicly.
This is why having an UNLOCKED bootloader is so helpful sometimes!
If your bootloader is unlocked you can flash any XT1225 firmware listed at that link, just omit the GPT.bin file when flashing.
thanks my bootloader is unlocked
jigar003 said:
thanks my bootloader is unlocked
Click to expand...
Click to collapse
Then you're very smart!
jigar003 said:
can u give me the link tostock rom? unable to find one i bricked my xt1225
Click to expand...
Click to collapse
I am using https://forum.xda-developers.com/moto-maxx/general/moto-turbo-indian-variant-marshmallow-t3422783
mohangj said:
It worked Thanks brother !!!!
Here what I executed on bootloader
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin (didn't execute this command)
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
mohangj said:
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
Click to expand...
Click to collapse
Since all you replaced with @bhb27's kernel was the the kernel, you wouldn't have to re-flash the entire stock image. All you needed to re-flash -- I think -- would be the boot.img. That would have overwritten the custom kernel...
But at this point, since you have re-flashed the entire image andnow the phone won't boot, I'm not sure what is wrong.
You can always try to flash a custom ROM? I know people use Viper on custom ROMs and I believe even with @bhb27 kernel. So, not sure why your Viper didn't work any more. But you need to get your phone up and working again.
Try this Marshmallow ROM for starters:
[ROM][All Quark][6.x.x]Resurrection Remix
https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232
mohangj said:
**********************************
ChazzMatt,
I am facing another kind of problem again, I had flashed custom Kernel BHB27 (https://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526) on stock 6.0.1, It was successfully installed and but I lost Devinebeats Viper4Android effect. I tried to reinstall driver/relash zip file. It didn't work. So I wanted to reflash to Stock. This time I followed same steps as above. But not able to successfully flash, after executing all commands, device reboots to Motorola Android boot screen and then goes off, its getting switched off in some 15-20 secs. Not able to boot completely back to stock. what am I upto now
Click to expand...
Click to collapse
Here's a "custom" ROM based on XT1225 stock Marshmallow. It's just stock Brazilian Quark Marshmallow but modified to run on ALL Quarks (including Droid Turbo XT1254) by @iiWoodstocK. Try flashing that?
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
ChazzMatt said:
Here's a "custom" ROM based on XT1225 stock Marshmallow. It's just stock Brazilian Quark Marshmallow but modified to run on ALL Quarks (including Droid Turbo XT1254) by @iiWoodstocK. Try flashing that?
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Thanks for the update. It worked by removing gbt.bin entry line from flash file and flashed it by RSD. No issues now
Need help I'm getting this annoying notification to update to 24.201.2 every now and then hence I final tried to install it failed.
Please check the screens for more.
And recovery also does not open says "no command " error I'm not sure whether I had installed or not. How to fix this? And remove that annoying updated notifications without root.
TRY THIS AT YOUR OWN RISK! MAKE A NANDROID BACKUP BEFORE MAKING ANY CHANGES!
So, you have rooted The phone flashed EX kernel and then Rooted via SuperSU/Phh's Superuser/Magisk v 12.0
Find the stock Kernel of the version you are on, since this OTA needs you to be on 25.93-14, therefore, you can find the boot.img of the stock kernel. here and stock recovery here
Next would be to un-root the phone,
ANY FLASHING HERE NEEDS TO BE DONE IN CUSTOM RECOVERY. ( I know you know it, but Just a reminder)
1. SuperSU - use the un-root option,
2. Phh's Superuser - just uninstall the apk and then flash the stock boot.img
3. MagiskSU - Use the magisk uninstaller here
3 simple Steps to follow: (Please follow the order, as flashing the stock boot.img on the rooted phone can bootloop it! And nothing will help then except flashing the stock ROM.)
1. Make sure you redo any changes done to the System. (cannot guarantee if the OTA will succeed after this). The changes done by Magisk will be reverted as soon as you flash the uninstaller, so nothing to worry about that.
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important) IGNORE IF ROOTED BY SUPERSU. USE APP UNROOT OR RESTORE THE NANDROID MADE BEFORE ROOTING
3. Connect the phone Via PC and then in bootloader mode flash the stock boot.img and recovery.img
Take the OTA of approx 40MB and then u can root the phone again!
Done!
I have also replaced the boot warning picture with a custom one. Wonder if I need to reverse this... I don't have the stock warning pic.
Maybe I should flash the system and logo completely, keeping the user data.
SoNic67 said:
I have also replaced the boot warning picture with a custom one. Wonder if I need to reverse this... I don't have the stock warning pic.
Maybe I should flash the system and logo completely, keeping the user data.
Click to expand...
Click to collapse
Yess, that needs to be brought back to stock... flashing the logo file in the stock firmware should do the trick... I have never tried it though!
I have re-flashed the 93-14.4 with the file that I have received. Well... it seems that the retention is gone. Again.
I uninstalled the root, flashed the stock recovery and removed any root apps on the phone. Still the update wouldn't work and I won't go as far as re-locking my bootloader in order to install a update that only patches some vulnerabilities that this device has been vulnerable to for at least 6 months. When I tried to install the update it would fail every time.
I did use the fastboot to re-flash the system and logo, keeping my data untouched. The "noerase.bat" file contains:
Code:
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 oem oem.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 erase cache
fastboot reboot
j0nas_ said:
I uninstalled the root, flashed the stock recovery and removed any root apps on the phone. Still the update wouldn't work and I won't go as far as re-locking my bootloader in order to install a update that only patches some vulnerabilities that this device has been vulnerable to for at least 6 months. When I tried to install the update it would fail every time.
Click to expand...
Click to collapse
How did u root the phone?? SuperSU? U don't really need to uninstall the the root apps as after unroot they do not function!!
Did u alter the system? Like made any user app as system app??
SoNic67 said:
I did use the fastboot to re-flash the system and logo, keeping my data untouched. The "noerase.bat" file contains:
Code:
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 oem oem.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 erase cache
fastboot reboot
Click to expand...
Click to collapse
What's the error that u are getting after this??
Ideally, u should flash only system file!! Recovery and System 1-7!
abhi212b said:
How did u root the phone?? SuperSU? U don't really need to uninstall the the root apps as after unroot they do not function!!
Did u alter the system? Like made any user app as system app??
Click to expand...
Click to collapse
I rooted with superuser.zip with phh's superuser app. Got it somewhere here on xda and it has worked fine. Some root apps caused a bootloop, either gnuroot or root essentials or both. I just remove most root apps that may interfere with the bootup when I unroot even if they can't do anything after the unroot.
j0nas_ said:
I rooted with superuser.zip with phh's superuser app. Got it somewhere here on xda and it has worked fine. Some root apps caused a bootloop, either gnuroot or root essentials or both. I just remove most root apps that may interfere with the bootup when I unroot even if they can't do anything after the unroot.
Click to expand...
Click to collapse
Ohkay! did u flash EX kernel? Did u bring back that to stock??
abhi212b said:
Ohkay! did u flash EX kernel? Did u bring back that to stock??
Click to expand...
Click to collapse
Yes, I backed up the stock one before I flashed it for the first time.
j0nas_ said:
Yes, I backed up the stock one before I flashed it for the first time.
Click to expand...
Click to collapse
If everything's stock, there should not be any problems in taking an OTA!
You can go here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
And download the stock rom and flash only system files, just in case any messing up to the system was done.
Make a nandroid 1st.
Just flash systemsparse 0-7..
If that doesn't help...Flash all of these!
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
This should do the trick.
abhi212b said:
If everything's stock, there should not be any problems in taking an OTA!
You can go here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
And download the stock rom and flash only system files, just in case any messing up to the system was done.
Make a nandroid 1st.
Just flash systemsparse 1-7..
If that doesn't help...Flash all of these!
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
This should do the trick.
Click to expand...
Click to collapse
Do I need to re-lock the bootloader? Because that was the only thing missing from complete unroot. When I tried to install the update it got to like 40% before crashing or something, don't know what causes that.
j0nas_ said:
Do I need to re-lock the bootloader? Because that was the only thing missing from complete unroot. When I tried to install the update it got to like 40% before crashing or something, don't know what causes that.
Click to expand...
Click to collapse
Nope, relocking is not mandatory to take the OTA! It fails because the device doesn't look like stock! if u uninstalled any system app, or removed the bootloader unlocked warning message or used any custom logo, or even added any folder to the system folder, it fails!
abhi212b said:
Nope, relocking is not mandatory to take the OTA! It fails because the device doesn't look like stock! if u uninstalled any system app, or removed the bootloader unlocked warning message or used any custom logo, or even added any folder to the system folder, it fails!
Click to expand...
Click to collapse
It still fails and it's as a clean install as it can be apart frombeing connected to my wifi and my google account, nothing else is installed. When I try to install the update this time it got to ~30% and then displayed a dead android and "Error!" below it.
j0nas_ said:
It still fails and it's as a clean install as it can be apart frombeing connected to my wifi and my google account, nothing else is installed. When I try to install the update this time it got to ~30% and then displayed a dead android and "Error!" below it.
Click to expand...
Click to collapse
I have no idea if everything is stock why is it failing OTA! Then you will have to install stock rom again.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Go here and follow the instructions! If u are rooted then make a titanium backup of all the apps and user data and then do this function! That way after taking the OTA u can root again and use the titanium backup app to get all the data back!
Newbie here. I hope to receive my Moto G4 Plus (xt1644) tomorrow! I don't understand this step:
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important)
When rooting my G4 Plus, I will be using SuperSU. It seems that to unroot this app it's not done within custom recovery, which step 2 seems to require? Am I misunderstanding something?
Also, you speak of a 40MB OTA update. Does this change the Android version or is it just some type of security patch? Thanks
flroots said:
Newbie here. I hope to receive my Moto G4 Plus (xt1644) tomorrow! I don't understand this step:
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important)
When rooting my G4 Plus, I will be using SuperSU. It seems that to unroot this app it's not done within custom recovery, which step 2 seems to require? Am I misunderstanding something?
Also, you speak of a 40MB OTA update. Does this change the Android version or is it just some type of security patch? Thanks
Click to expand...
Click to collapse
You use custom recovery to recover your bootloader and system before making any changes.
---------- Post added at 11:23 AM ---------- Previous post was at 11:18 AM ----------
abhi212b said:
I have no idea if everything is stock why is it failing OTA! Then you will have to install stock rom again.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Go here and follow the instructions! If u are rooted then make a titanium backup of all the apps and user data and then do this function! That way after taking the OTA u can root again and use the titanium backup app to get all the data back!
Click to expand...
Click to collapse
I used titanium backup to restore my apps after installing linage os. I felt the trouble of installing linage is less than acquiring that security update. So far so good Except all sms are lost and a few games lost their saves.
abhi212b said:
What's the error that u are getting after this??
Ideally, u should flash only system file!! Recovery and System 1-7!
Click to expand...
Click to collapse
I guess the bootloader didn't want to be re-written, but the logo also needed to be reverted (I had a custom one).
However, the above procedure worked fine for me, the installed applications where maintained.
j0nas_ said:
You use custom recovery to recover your bootloader and system before making any changes..
Click to expand...
Click to collapse
Sorry, I don't know what that has to do with step 2 which refers to unrooting SuperSU. As near as I can tell, one does the uninstall of SuperSU within the SuperSU app on Android, not custom recovery. Hope you can elaborate. Thanks
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
1. Get your bootloader unlocked as we will require it once, to take a nandroid backup for safety.
2. Install TWRP 3.1.1.0 to make a nandroid backup on phone.
3. Once backup is done copy it from phone to PC to make it safe. It will take some time as mine was 6GB in size.
4. Before rebooting into fastboot select "Do not install TWRP" in recovery.
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
6. Reboot into recovery and clear cache and userdata partitions. Reboot normal now.
7. Phone will start the setup like after factory reset. Just skip restoring your personal data by answering No to save time. But let it complete whatever else it do. Now "About phone" will say device is Moto X Style and build is MM 6.0.1 RETEU.en. This is just fine. Phone converted (No GSM signal is no worry at this time).
8. Try System Update. If update is available fine, otherwise we do it manually to take it to MPHS24.107-58-13 (required as Nougat pre-requisite).
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
10. Again boot and skip Android setup. About phone will say your current build version.
11. Now download and copy Blur_Version.24.231.13.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
12. Boot into recovery and choose Apply the file from SDCard. WOW this is Nougat update. It will successfully complete the update.
13 Download Last official Clark MM stock ROM from Motorola website and open the zip file to extract NON-HLOS.bin and fsk.mbn and flash it from fastboot in the standard way.
14. Go into recovery and clean cache and userdata partitions
15. Boot normally to be greeted by Nougat firsttime setup.
16. Congratulations. You have Nougat and Moto X Style.
No links to files?
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
What about ota?
Bart_UA said:
What about ota?
Click to expand...
Click to collapse
There are two files I mentioned that starts with the name "Blur_Version". These are always OTAs!!! You apply through Wifi or SDCard, what is the difference?
This is my About Phone screen after the update.
jaffers said:
This is my About Phone screen after the update.
Click to expand...
Click to collapse
You can do backup with twrp and upload it for them.
Boot(before root)+system only.
Root is not required in my steps and TWRP not installed permanently (See my steps).
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Very simple. people like me don't want to loose Moto Action, Moto Display and Moto Voice. You loose all that in custom roms. I tried Lineage in my wife's Moto X 2014 a month ago. Frequent reboots, crash and reboot during video recording etc. This after several months of constant updates. Stock ROM do not have this type of issues. Atleast in the last decade not once any of my phone ever rebooted on its own. So I don't approve custom roms. If you don't mind, go ahead.
dzidexx said:
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Click to expand...
Click to collapse
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
jaffers said:
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
Click to expand...
Click to collapse
Yes. Now you shouldn't.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Stock Nougat is getting August security patch rigth now!
Dual sim
Is it dual sim supportable after updating?
NahuelMS said:
Stock Nougat is getting August security patch rigth now!
Click to expand...
Click to collapse
Blueborne is fixed in September security fix.
jaffers said:
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
11. Now download and copy Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
Click to expand...
Click to collapse
Hi, downloading the necessary files to upgrade my phone and I see you show the same file to download in steps 9 and 11. Is this file being installed twice?
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
Click to expand...
Click to collapse
I completed the steps up to this one. I want to make sure I don't accidentally flash everything.
So noob question, what files do I not fastboot? I know boot and recovery. Appreciate the help.
NON-HLOS.bin
fsg.mbn
BTFM.bin
flashfile.xml
servicefile.xml
slcf_ref_d_default_v.1.0.nvm
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
any possibility to flash custom recorvery/root on android 7? When im flashing recorvery via fastboot it says "permission deined"
nvm im dumb, misswrite a single letter in fastboot
I find this post a bit hard to read.
1). You are not really clear on exactly what to flash. You are close but not precise. If you are going to provide instruction like this you might need to be a bit more granular.
2). You mention the same file twice for both the pre-requisite patch and the nougat update. Are then both one in the same? This doesn't make sense.
I followed these instructions up to step #7. I flashed the following files:
logo.bin
BTFM.bin
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
I left out the following:
boot.img
fsg.mbn
gpt.bin
NON-HLOS.bin
recovery.img
My phone is showing Moto X Style however my build # is MPHS24.107-58-5 and not MM 6.0.1 RETEU.en
System version is reporting 24.221.5.clark_reteu.reteu.en.EU retus
If I try to move forward with the MPHS24.107-58-13 update I get a digital signature error.
jaffers said:
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
Click to expand...
Click to collapse