Database Users

[OTA] Moto G 2014 XT1063 v22.11.6 Android Lollipop

This OTA has been copied straight from the /cache folder by @KennyWuLee.
Download Here!
Steps For Applying the Update:
Copy the ZIP to your Moto G.
Go into Recovery.
Select "apply update from sdcard"
Choose the File which you copied.
Wait till it finishes and select reboot.
This update is specifically for the XT1063 model and isn't meant for other variants.
Update Details:
Code:
v22.11.6
Android Version: 5.0
Build Number: LXB22.39-6

Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"

Any chance of this working on XT1068?

emmanuelreyes said:
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"

pleomaxell said:
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
What if i have a different version? Will it work? or i have to rename it?

emmanuelreyes said:
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
pleomaxell said:
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
@emmanuelreyes, Exactly what @pleomaxell said. Plus here's the screenshot running on my XT1063.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Is there a chance to make this file a flashable zip through TWRP? For some reason it doesn't want to install, it says "/system/lib/hw/sensort.MSM8226.so" has unexpected contents :S

Fine to XT1068
Thanks and this works fine with my XT1068, check this post http://forum.xda-developers.com/showpost.php?p=56765946&postcount=138

@Taimur Akmal why does the screenshot show an Exclamation(!) sign with the network icon?

pleomaxell said:
@Taimur Akmal why does the screenshot show an Exclamation(!) sign with the network icon?
Click to expand...
Click to collapse
It shows that I am without an Internet connection. I have Mobile Internet turned off.

Cannot lock bootloader
tbunlmtd said:
Working just fine, thanks!
Click to expand...
Click to collapse
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
mfastboot.exe oem lock begin
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 system system.img_sparsechunk.3
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 oem lock
Click to expand...
Click to collapse
getting downgrade error, PIV signed image error, sst lock fail error !
[NB: I have changed to US version (retuaws) before and flashed back to global ]

Sounds like your on a XT1063. This is what I did when I was in the same position as you. I restored my Nandroid of KK. If you have a all stock copy then you should be better then I was & about to skip a few of these steps. I found a system dump on here of the stock system & started pushing the files I knew I removed. Actually I used ES File Explorer & done a select all, copy, paste. You get prompted to ask what to do about files that are already there. Check apply to all & choose skip. This left me with a audio file that was replaced & had to be change back. You should make a new Nandroid to save your work to this point. Flash the stock recovery & run the update.zip. mine installed fine with the unlocked bootloader & root.
L is really buggy tho so be warned.

Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?

rasbin said:
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
Click to expand...
Click to collapse
I doubt it will without flashing the other firmware.

rasbin said:
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
Click to expand...
Click to collapse
You will have to flash via fastboot the XT1063 retugbl firmware in order to use this OTA file.
Check this thread, but consider making a full backup.

My md5 checksum:
2e632d07edc3c1ceb38a0ee486f12a5b

you need the bootloader unlocked?

I successfully flashed this while being fully stock/locked bootloader. Everything works except the flashlight won't turn back off after I activate it... anyone else have this issue?

patrickjaden said:
I successfully flashed this while being fully stock/locked bootloader. Everything works except the flashlight won't turn back off after I activate it... anyone else have this issue?
Click to expand...
Click to collapse
Working totally fine on my end. You are talking about the Flashlight from the Notif menu right?

Taimur Akmal said:
Working totally fine on my end. You are talking about the Flashlight from the Notif menu right?
Click to expand...
Click to collapse
Yes the bootloader needs unlocked to flash the stock firmware.

[ROOT] [RECOVERY] Install SuperSU and TWRP on Official Lollipop 5.0.2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[YOUR WARRANTY IS NOW VOID]
****I TESTED ONLY ON MY XT1058 MODEL I DON'T KNOW IF WORKS ON OTHER MODELS***
-First you need to unlock your bootloader [MORE INFO CLICK HERE]
-Install the motorola drivers [DOWNLOAD HERE]
1.- Activate developer settings and copy the "UPDATE-SuperSU-v2.46.zip" to the Internal Storage of the Moto X
2.- Reboot your Moto X on Fastboot Mode (Power + Volume Down Key) (at least 5 seconds)
3.- On Fastboot Mode, connect your device to the USB port of your PC
4.- Go to the downloaded folder and run the "Installer.bat" file
5.- Continue with the instructions of the program, the program will send the recovery to the Phone, now in your phone select "Recovery" option and press the Power Up Key.
6.- When you are in the TWRP recovery select "Reboot", then "System", the swype to install SuperSu.
7.- When your phone has booted normally, select "Install SuperSu" and follow the instructions that appears on phone screen
SCREENSHOTS
[DOWNLOADS]
Google Drive: https://drive.google.com/file/d/0B0yyE-L_FGXrLXpPMlZpSk05dnM/view?usp=sharing
ZippyShare: http://www30.zippyshare.com/v/ua3qv2bK/file.html
MEGA:https://mega.co.nz/#!gQpQTCAa!krYHdwWDCZSlm14PkgNombjSOB1sdfjy4SVnbqr3NnI
VIA: Moto X Brasil

Works on my xt1060 thanks

sorullo_xgrx said:
Works on my xt1060 thanks
Click to expand...
Click to collapse
Wait you Flashed the Soak Test to your XT1060? I thought 1060 was only VZW?

gchase23 said:
Wait you Flashed the Soak Test to your XT1060? I thought 1060 was only VZW?
Click to expand...
Click to collapse
It is but I switch the T-Mobile and its working great

Worked great for me. Unlocked Bootloader XT1058 AT&T US on 5.0.2

Will I be able to go back to stock after doing this? I mean there's no sbf for 5.0.2 yet, so is there anyway to revert this process?
I haven't done it yet, won't do if theres no way to go back.
Thanks

changes the stock recovery?or is only temporary

lukaop said:
Will I be able to go back to stock after doing this? I mean there's no sbf for 5.0.2 yet, so is there anyway to revert this process?
I haven't done it yet, won't do if theres no way to go back.
Thanks
Click to expand...
Click to collapse
Yeah you can always go back to stock by flashing 4.4.4 sbf file. I just flashed on my XT1053 and it works just fine.

ken1645 said:
Yeah you can always go back to stock by flashing 4.4.4 sbf file. I just flashed on my XT1053 and it works just fine.
Click to expand...
Click to collapse
Really? Thought you couldn't downgrade from 5.0 to 4.4, but I will wait for an 5.0 sbf just in case.
Anyway, thanks!

TWRP and SU included in the 5.0.2 ROM

Found out can't downgrade from 5.0 to 4.4.4 and am screwed after trying to take an OTA soak update.
edit: found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.

The stock recovery of lollipop is the same as KitKat?

ken1645 said:
Found out can't downgrade from 5.0 to 4.4.4 and an screwed after trying to take an OTA soak update.
Click to expand...
Click to collapse
I'm in a similar situation. sucks...

vikramkhalsa said:
I'm in a similar situation. sucks...
Click to expand...
Click to collapse
I found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.

ken1645 said:
I found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.
Click to expand...
Click to collapse
I saw that, but I don't want to brick my phone.. Isn't that likely using this way?

Vivjen said:
TWRP and SU included in the 5.0.2 ROM
Click to expand...
Click to collapse
What's in this? because after i flashed this the phone lost signal and even though i flash european modem won't fix it.

alexhdkn said:
What's in this? because after i flashed this the phone lost signal and even though i flash european modem won't fix it.
Click to expand...
Click to collapse
I looked at that zip. With regards to the modem, it flashes an unknown version (soak version?) of both NON-HLOS.bin AND fsg.mbn
I am running LP 5.02 (soak2) with the stock att xt1058 4.4.4 modem without issue, so it *might* work if you extract NON-HLOS.bin and fsg.mbn from your stock version of 4.4.4 and run the following from fastboot:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
Good luck.

Ctrl-Freak said:
I looked at that zip. With regards to the modem, it flashes an unknown version (soak version?) of both NON-HLOS.bin AND fsg.mbn
I am running LP 5.02 (soak2) with the stock att xt1058 4.4.4 modem without issue, so it *might* work if you extract NON-HLOS.bin and fsg.mbn from your stock version of 4.4.4 and run the following from fastboot:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
Good luck.
Click to expand...
Click to collapse
Somehow i managed to downgrade everything, even the bootloader. After the flash of your zip i tried to flash fsg and modem but it seems that i forgot to erase the two st1/2. Thanks for the interest though

ken1645 said:
Found out can't downgrade from 5.0 to 4.4.4 and am screwed after trying to take an OTA soak update.
edit: found a way how... it's sneaky though. Use the stock 4.4.4 recovery files, but for the gpt.bin file, replace it using a gpt.bin file from one of the leaked 5.0.2 recovery files and flash as normal to get back to 4.4.4. I had a 1% battery stuck bug though after doing this and discovered by killing the phone all the way to 0% shut down and then recharge the battery meter fixed itself again. Got all the way back to stock 5.0.2 soak test once again after doing this.
Click to expand...
Click to collapse
I did the same but just deleted the gpt.bin reference line in the xml to skip over flashing it. I'm not now .38 soak test

So it is safe to downgrade? I would like come back to stock 4.4.4 and then install CM12, my question is because of the bootloader version I read a downgrade may cause brick
Sent from my XT1058 using XDA Free mobile app

[HELP] Problem flashing TWRP recovery on ZUI

Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)

Unlock your bootloader and retry.

Already retried to unlock the bootloader.. But no luck.. Thanks for the tips btw

I have found the solution.. I will post it in the weekend

luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
when u post please tell my in the praivte
[email protected]

Kingroot worked for me bit only after the second try

Tengo10 said:
Kingroot worked for me bit only after the second try
Click to expand...
Click to collapse
can u explain me please how u do it with king root??

eyalyagel said:
can u explain me please how u do it with king root??
Click to expand...
Click to collapse
I coud've offered more direct support if you messaged me or replied to my thread.

Have you found any solution?

Breadcrust said:
I coud've offered more direct support if you messaged me or replied to my thread.
Click to expand...
Click to collapse
can u give me please the link or explain may the way????
thank u very much

eyalyagel said:
can u give me please the link or explain may the way????
thank u very much
Click to expand...
Click to collapse
Did you do fastboot -i ox2b4c oem unlock?

Breadcrust said:
Did you do fastboot -i ox2b4c oem unlock?
Click to expand...
Click to collapse
yes,
FAILED (remote: Oem unlock is not support)
finished. total time: 0.008s
and i allow the oem in the developer option....
also i have the same phone in my home but the difrrent bitween them:
1. have only home press in the bottom
the ather phone have home, back,manu, bottom this phone can be unlocked and i sucsses to instal twrp

I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.

xnoobx said:
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
Click to expand...
Click to collapse
I'm also facing the same problem with my ZUK Z1

ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.

hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
Dear
I was using CM12 new version till last week and i have lots of problems, specially with mobile signal during the calls voice is dropping signal is too week as well. So i have decided to move to ZUI version and it's perfect so far i'm not facing any problem. Only the vulnerable is there some kind of malware and GPS having some bugs i have checked with bbs.zuk forms and they are suppose to fix it with next update. so i was trying to install the stagefright fix via recovery.remaining everything is smooth and faster than CM12.

hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
I also tried to boot. But it also denies this action :/.
So with the latest version my boot loader is locked. Sounds wonderful.

luqmanhans said:
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Click to expand...
Click to collapse
In this case, you need flash fw Z1_CN_OPEN_USER_Q4275715.1_L_ZUI_1.0.050_ST_150910 via sd card ( root internal memory/creat sdfuse folder), after turn off fone and boot phone via factory mode recovery ( voulme down + power ). If phone flash ok, version is 1.0.050. So, phone can flash twrp recovery and rom CyanogenMod 12.1 .
Goodluck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:

hristos13gr said:
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
Click to expand...
Click to collapse
First you must downgrade the ZUI from 1.2.040, just search this topic in this forum: how-to-flash-zuk-z1-zui-version-t3265741
After that you can boot with TWRP recovery. But if you failed to flash Cyanogen, use Modaco steps: 375804-convert-z1-from-zukui-to-cyanogen-os/
When your ZUK Z1 already use Cyanogen, you can flash to other recovery or ROMs easier .

New firmware

Hi All!
I just receive a new firmware MPN24.104-44.
Anybody else?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes, me too. UK, unlocked. It was a big download, still going. Not Nougat, which is what I first thought. No idea yet what it fixes.

I have been on this version on the US unlocked version (screenshot) I wish we would get nougat already.

mrbracht said:
I have been on this version on the US unlocked version (screenshot) I wish we would get nougat already.
Click to expand...
Click to collapse
So, it's the August security update? That's it?

Yeah, I'm guessing so. Kind of disappointed with the dev work and software updates for this phone. Still one of the best phones I have ever had. Just wish it would take off on here.

mrbracht said:
I have been on this version on the US unlocked version (screenshot) I wish we would get nougat already.
Click to expand...
Click to collapse
Unrelated to updates, how did you get the black/dark theme?

which firmware are you in , I wnt the dsds modem firmware lol

Any ideas on how to flash it on an unlocked device; I couldn't even with the stock recovery.
TWRP gets far into the update but ends with ERROR: 7 (the system partition has unexpected contents.)

Yeah, I'm having the same issue. It's getting on my nerves...

Even when trimming the updater-script file, I still end up with asset errors. I went so far I now get Error: 6 and now I can't be bothered to find the missing semicolon...

Stuck during update
Sebastiann70 said:
Hi All!
I just receive a new firmware MPN24.104-44.
Anybody else?
Click to expand...
Click to collapse
I did, but my phone keeps hanging during the update. I need to reset it at the boot menu. Else its stuck in a loop trying to install the update, then reboots and starts over again. I dont know what i should do.

LloydGSR said:
Unrelated to updates, how did you get the black/dark theme?
Click to expand...
Click to collapse
Just use substratum and download the "A swift dark theme" from the store.

mrbracht said:
Just use substratum and download the "A swift dark theme" from the store.
Click to expand...
Click to collapse
How did you get Substratum to work? None of the themes I've tried are working, keeps saying exception in trying to install.

EpsiMaxx said:
I did, but my phone keeps hanging during the update. I need to reset it at the boot menu. Else its stuck in a loop trying to install the update, then reboots and starts over again. I dont know what i should do.
Click to expand...
Click to collapse
Scrap my past post, I think I know what it is (and not the same as yours). We'll see.

Hey guys, just curious do we need to un-root our device before updating via OTA or can we keep our device rooted and apply update without any issues? Also does root survive after updating to a new version via OTA? I havent got my phone yet, still shipping..

mhp1995 said:
Hey guys, just curious do we need to un-root our device before updating via OTA or can we keep our device rooted and apply update without any issues? Also does root survive after updating to a new version via OTA? I havent got my phone yet, still shipping..
Click to expand...
Click to collapse
You can try to install SuperSU survival script but I haven't tried it, I'm rooted , running xposed and ultered some system files so the ota will not flash on my system.
You'll definitely have to flash stock recovery and uninstall any customizations you have made to your system.
I tried flashfire myself and it wouldn't flash the ota for me.
Sent from my XT1635-02 using XDA-Developers Legacy app

You can't keep root to accept the OTA. If anything in the /system, /oem, /boot, /recovery partitions are different from what it expects, it'll fail with error 7.
To revert to a state where you can accept the OTA, go get the correct stock image file for your variant. In my case, it was XT1635-02_ADDISON_RETUS_MPN24.104-49_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (you can download stock images from https://mirrors.lolinet.com/firmware/moto/addison/official/).
In the zip file will be boot.img, oem.img, recovery.img, and system.img_sparsechunk.0 (all the way through system.img_sparsechunk.10). You need to flash all 13 of those files from the bootloader:
Code:
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 flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
From there, boot into the OS and check for update, it'll go through the process, reboot into the stock recovery and go through the OTA update.

Wife's unlocked/GSM MZP got the November Security patch a couple days ago. I would think Moto would be trying to update this phone to Nougat soon after the Z and Z Force got it last month, but that doesn't seem to be the case. Even the Moto G got updated before this phone.
Oh well, Nougat doesn't really bring much to the phone anyways, I've had it on my 6P since its release. It will be interesting to see if this phone gets even better battery life after the update though. 10+ hours of SoT in a charge is already insane.

Brick moto g4 xt1622

Hi, yesterday i have unlock bootloader of my moto g4, xt 1622 , i have flashed twrp and this is perfect, but after i have flashed zip of magisk.zip for root permission, when i reboot i obtain only black screen and led white ( intermittence led) .
The device is recognize by windows 10 (in test mode and no signature driver verify ) but not in tray bar..
Mode recognized by pc are:
in fast boot like " fastboot athene_13mp S " in "other device"
In adb mode " sideload" ( from stock recovery) like "Moto g4 plus " in device manager/usb devices"
I have stock recovery and can't start blank flash because the device isn t recognized by pc like qualcomm device..
What can i do??? Thanks a lot my friends!!

The problem is that magisk is not compatible with the Stock kernel, so if you want magisk you need to flash a custom kernel, i recomend this: https://elementalx.org/devices/moto-g4/ you need to flash the kernel and after this flash magisk.
Regards

Wow! So the phone is save? ?
And what can i flash pther kernel, can i have a guide plz? Can i flash with sideload? Thanks!

Yes, you need to enter un recovery, conect your phone to pc and with adb put in the cmd adb sideload nameofyourzip.zip and then flash magisk with sideload if hoy wanr

Unfortunately i recive this error.. what can i do? Thanks!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ok, first you need to install twrp: https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Then you need to go in twrp to avanced and adb sideload and flash it.

Hmm, can you confirm if you have stock Marshmallow (6.0.1) or Nougat (7.0) on your device? I see from the stock recovery version that it's 6.0.1/MPJ24.139-23-4 (a really old build of Marshmallow).

Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David

scossa1994 said:
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
Click to expand...
Click to collapse
Thanks, as Ismael034202 pointed out above, if you were on stock Nougat, then you will need to flash a custom kernel, as rooting on the stock Motorola Nougat kernel will cause a boot failure. If you were still on Nougat, then you could have followed this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 with flashing magisk instead of SuperSU.
As you've re-flashed the old Marshmallow stock ROM, then you do not need a custom kernel (Marshmallow stock ROM kernels are less strict about rooting), flashing TWRP and then flashing magisk should work on Marshmallow.
However, you need to be very careful if you revert back to full stock - as you've appeared to have downgraded from Nougat, taking OTA updates may hard brick your device. If you can remember what Nougat stock ROM you had before unlocking your device, I would recommend downloading a copy of that stock ROM and using the stock ROM to update. Try not to use stock OTA updates.

Very well explained echo92. +1 ?

what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks

scossa1994 said:
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
Click to expand...
Click to collapse
Hmm, in that case, the easiest way may be to flash the latest stock ROM to your device and start over again. As an alternative, do you have a TWRP backup of your device?
For XT1622, you'll likely want NPJS25.93-14-13 (Nougat, 7.0 stock, December 2017 security patch) firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Download and extract as directed in the post, and to flash to repair your device, use the following flashing commands:
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 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 userdata
fastboot reboot
Click to expand...
Click to collapse
This should not re-lock your bootloader. Next, download TWRP, ElementalX and magisk and flash as I suggested in the guide above. The basic guide for rooting on Nougat is:
a)Flash/boot TWRP. Backup your device.
b)Flash ElementalX.
c)Flash magisk or SuperSU.
d)Wipe cache/Dalvik in TWRP.
e)Reboot and wait for boot.
f)Any issues, revert to your backup made in a)

Can i use fastboot within debug usb off? Because i recive an error, i m tryng and post a pic.
Thanks
This is my situation after try to use fastboot

Hace you installed Motorola drivers for pc, you can use fastboot without USB debugging
https://mobilesupport.lenovo.com/rola/es/solution/MS89882 This os the link for the fastboot drivers

Thanks guys!! I had write the stock 7.0!! Now the phone is perfect!! Thanks!!
I had wrong driver and pc not recognized the phone!! Now yes ??

Now install twrp, elementalX Kernel, magisk and enjoy

Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.

Moto Singh said:
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Click to expand...
Click to collapse
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.

scossa1994 said:
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
Click to expand...
Click to collapse
No nothing is working.

Moto Singh said:
No nothing is working.
Click to expand...
Click to collapse
I don t know.. the problem is the corrupted bootloader ( i think..)