Database Users

6.0.1 - How to flash?

I am looking for a clear explanation of how to flash Android 6.0.1 with root and encryption disabled without wiping data. With all the explanations through the forum, all the "if's" and "but's" get confusing and can be clear as mud. Thanks for your help.

i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I

nextelbuddy said:
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
Click to expand...
Click to collapse
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.

how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img

ShaunWinSC said:
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
Click to expand...
Click to collapse
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ovrclck said:
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
Click to expand...
Click to collapse
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.

nextelbuddy said:
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
Click to expand...
Click to collapse
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?

ShaunWinSC said:
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
Click to expand...
Click to collapse
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.

nextelbuddy said:
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
Click to expand...
Click to collapse
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.

I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
ShaunWinSC said:
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
Click to expand...
Click to collapse
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.

nextelbuddy said:
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
Click to expand...
Click to collapse
Have u flashed vendor.img ???
That's probably the problem :silly:

kauemelhado said:
Have u flashed vendor.img ???
That's probably the problem :silly:
Click to expand...
Click to collapse
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol

nextelbuddy said:
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
Click to expand...
Click to collapse
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message

kauemelhado said:
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
Click to expand...
Click to collapse
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!

I have flashed these three Files via the readme commands(fastboot flashing) and did not have my data partition wiped. and now FC's on ubermallow custom rom.

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
Some people are having this problem with EX kernel. But I guess the kernel is not the problem.
I'll flash the update later on today, then i'll tell you how that work for me hehe

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61

kauemelhado said:
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
Click to expand...
Click to collapse
Nice, how did you made it? Did you leave the recovery.img?

Martini3001 said:
Nice, how did you made it? Did you leave the recovery.img?
Click to expand...
Click to collapse
I flashed stock recovery and later on flashed twrp.
I was getting the android of death when booting into TWRP.
So, I did this:
-fasboot flash recovery *twrp*
-fastboot reboot-bootloader
*on your fone* using the volume buttons search for "RECOVERY"
-boot into recovery
-thank me!
lololol

I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?

MPAI said:
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
Click to expand...
Click to collapse
after you flash TWRP, if you reboot, the system will flash the stock recovery back if its not the original
after u flash TWRP, u need to boot into recovery, and then flash the expected SuperSU.zip
the supersu zip script will edit the system and disable the flashing of stock recovery

Going back to stock: no Wi-Fi

Hi everybody.
I'm very upset with my Moto X Style (XT1572, retail EU, bought in Italy though I live in South America).
Some days ago I received Android 7.0 OTA. Everything was fine until I had some problems with file management, which I had some months ago. So, I did a factory reset. Nothing improved, though I tried many times, so today I tried to flash a factory image of 6.0.1 using this image:
XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5
I did it multiple times, with different guides, because everytime I turn on the phone (no problem with that) to set it up, I can't detect any Wi-Fi access. If I skip the initial set up and go to Configuration/Wi-Fi, if i turn it on it automatically turns off after one or two seconds, never listing any access.
Most guides I followed where amost identical, maybe changing one or two fastboot cmd lines. What I can tell you is that with "fastboot flash partition gpt.bin" I get a failure, which I've been told happens because I want to flash an older system number. I get the same failure when doing "fastboot flash modem NON-HLOS.bin".
I really need to make it work, guys. The help I'm asking for is for:
1) Which image should I go for? I repeat, my last official system was 7.0, after unlocking went for a 6.0.1.
2) Idiot-proof fastboot cmd line in order (maybe I'm doing it wrong).
3) If you can tell me how to relock after it, I'd be very grateful.
4) Anything else is appreciated.
Finally, one thing I forgot: the first time I flashed it I forgot the eleventh system chunk and got on a bootloop, but I could start again.
Thank you!

Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 @FernandoAmado
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
Relock is impossible so far.

dzidexx said:
Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 @FernandoAmado
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
Relock is impossible so far.
Click to expand...
Click to collapse
I really want to thank you for your help. With your comment and the guide you gave me, I was able to flash that image, update to the next and last 6.0.1 and I'm downloading OTA 7.0 right now.
I have two questions I hope you (or anybody else) could help me with:
1) When I finally get back to 7.0, will that partition file which gave me trouble coincide with the system number? So I can forget about that issue?
2) Are you sure there isn't a way to relock it and bring it to status 2? I know it's not a problem, leaving it unlocked, but I'd like to relock it anyway, and then flash a fresh logo that doesn't point out it was unlocked.
Again, I'm very grateful for your help. You have no idea the stress I've got with this issue. I'm never going to unlock a phone, ever again.
The funny thing is, I did all this mess because Android stopped reading a particular selection of my music's metadata. Some Beach Boys album (it even left some BB albums untouched) and I couldn't sort it out doing a hard reset nor formatting the SD card. Funny and painful experience.

1. You will see.
2. There isn't the newest 6.0.x and 7.0 roms for fastboot. BL cannot be locked after update to it.
Users on Lolipop or early 6.0 can relock.
You can flash modified logo.bin, is what to choose:
https://forum.xda-developers.com/moto-x-style/themes-apps

" Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin "
Yes Yes
I had the same problem with same Build and your turtorial helps me !
Now everithing is OKAY
Thanks @dzidexx !

Factory Reset with TWRP and Magisk Boot loops back to TWRP

I tried to do a Factory Reset from within Nougat 7.0 under Settings, Backup & reset "Factory data reset" but after a reboot, my MXPE entered TWRP, so I tried doing another System reboot, but kept booting to TWRP, I eventually had to Re-Flash step by step , but I do know what could have caused it, I tried it 3 times and each time, same result. I have TWRP 3.1.1-0, Magisk 14.0 installed with Xposed Framework 88.2 SDK-24 (Systemless by topjohnwu) installed, and followed these steps https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268. After installing TWRP Recovery, I made sure to choose to leave the System Partition READ ONLY.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Then after a complete setup
fastboot flash recovery twrp-3.1.1-0-clark.img
fastboot flash logo logo.bin (Custom Logo) (to wipe that stupid Unlocked Bootloader Warning logo)
fastboot reboot (back into Recovery) (2x)
Any help would be most appreciated..

Boot into twrp and do "format data/factory reset".
Reflash magisk if you want root.
Reset from settings works only with stock recovery.
---------- Post added at 06:16 AM ---------- Previous post was at 06:16 AM ----------
@CLETjB

Thank you, I'll try it.

dzidexx said:
Boot into twrp and do "format data/factory reset".
Reflash magisk if you want root.
Reset from settings works only with srock recovery.
---------- Post added at 06:16 AM ---------- Previous post was at 06:16 AM ----------
@CLETjB
Click to expand...
Click to collapse
^^^ This.
When you choose to do a factory reset, the phone attempts to boot to recovery and perform that action.
When you have a custom recovery on the device, the action cannot be completed and the phone retains a 'flag' within one of the partitions to continually boot to recovery.
This partition has been identified on most phones that have been around for while and rooted, however, the method of removing this flag is usually performed in an 'unchecked' state, and therefore, any mistyping can potentially brick the phone for good. Hence these methods are not generally publicised.
I remember back in the days of Gingerbread and Ice Cream Sandwich, these methods were shared more openly, however, in those days, I think the community both here, and on other forums, was a little more savvy in terms of technical ability and awareness of potential issues.
Regardless, if you have twrp installed, do not attempt to perform a factory reset from within the settings of android, you can only perform it from within twrp.
I hope that this sheds a little light on the issue.

Yes it does, Thank you.
I only wish the Carriers and MFGs would openly be more friendly with Development/Rooting since it would help Enhance the products openness and compatibility after the initial Warranty period of 2 years. Google Pixel devices welcome Rooting and Bootloader unlocking without void the warranty, plus there is a lot of more customization out there with a rooted device and bland UI and backup options, than one that is so locked down you practically can't do squat with it. I like the MXPE and the MOTO Actions / Voice have a lot to do why the MXPE STOCK image is a sought after device as well the 21 Mega Pixel Camera and the storage options, to name a few. The Craftsmanship of this device from China is pretty good compared to other devices, and it feels like its built strong and not too fragile, I only wish it was 100% waterproof and virtually indestructible like the Droid Turbo II.
I know security has a lot to do with the reluctancy to openly unlock a device, but that would put some more pressure and creativity on some developer like TWRP to help protect the device they are running on.

removed

Can't get RSD Lite to detect my Moto X (pure)

My brother gave me a rooted phone, so to unroot it I got a .bat off of a site to flash the stock firmware, but now the wifi doesn't work on it, so I think the firmware I used had the wrong radio firmware. I ended up getting the flashfile off of the motorola dev site and made sure it was the right one. I then got RSD Lite and it's not detecting my phone when I plug it in. I made sure I got adb and fastboot, I installed the motorola usb drivers, I put my phone into Fastboot flash mode, I have my phone in debugging mode, I've tried different USB Cables, different USB ports, I've ran it in administator and I still can't get it to detect my phone. Does anybody know a fix for this, or a different way I could flash my xml file onto my phone?
When I downloaded RSD, there was another link for the drivers. When I downloaded it, it had 5 different files (pic attached). This may or may not be the issue, but I couldn't figure out what to do with these files.
Thanks!

Simplier is harder sometimes - i've never used .bat or rsd - only fastboot, keyboard and fingers.
Thera are two good tutorials fot it.
Wifi - sometimes it is needed to repeat few commands: from modem... to... bt,
Drivers - Motorola Device Managers installs all,
Unroot - "unroot & restore boot" iwith supersu/magisk manager app.
You flashed something - there isn't flashable Nougat for all models - give us more info - xt15??, DSim/SSim, last android ver....
https://forum.xda-developers.com/moto-x-style/general
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
@lisc89d

dzidexx said:
Simplier is harder sometimes - i've never used .bat or rsd - only fastboot, keyboard and fingers.
Thera are two good tutorials fot it.
Wifi - sometimes it is needed to repeat few commands: from modem... to... bt,
Drivers - Motorola Device Managers installs all,
Unroot - "unroot & restore boot" iwith supersu/magisk manager app.
You flashed something - there isn't flashable Nougat for all models - give us more info - xt15??, DSim/SSim, last android ver....
https://forum.xda-developers.com/moto-x-style/general
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
@lisc89d
Click to expand...
Click to collapse
Sorry for the late reply. The hardware SKU is XT1575 and the android version is 5.1.1
I just barely followed this tutorial https://www.youtube.com/watch?v=njXQYn53SPc, and I still wasn't able to get it to work.
I also got my firmware off of this site https://androidfilehost.com/?w=files&flid=44735, to my knowledge, I flashed it with the correct firmware. I downloaded and flashed from this download - CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml.zip
Also I'm a noob when it comes to phones, so I'm not sure what DSim/SSim means.
Thank you!

Sorry, I can't tell anything about RSD.
If you want more help you should flash 6.0. or 7.0(your link AFH) with this tutorial:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 @lisc89d
Upload here screenshots from pc.
---------- Post added at 06:19 AM ---------- Previous post was at 06:18 AM ----------
Ps.
Did RSD show something like that?
fastboot flash modem NON-HLOS.bin
...OK
fastboot erase modemst1
...OK
fastboot erase modemst2
...OK
fastboot flash fsg fsg.mbn
...OK
fastboot flash bluetooth BTFM.bin
...OK

dzidexx said:
Sorry, I can't tell anything about RSD.
If you want more help you should flash 6.0. or 7.0(your link AFH) with this tutorial:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 @lisc89d
Upload here screenshots from pc.
---------- Post added at 06:19 AM ---------- Previous post was at 06:18 AM ----------
Ps.
Did RSD show something like that?
fastboot flash modem NON-HLOS.bin
...OK
fastboot erase modemst1
...OK
fastboot erase modemst2
...OK
fastboot flash fsg fsg.mbn
...OK
fastboot flash bluetooth BTFM.bin
...OK
Click to expand...
Click to collapse
I've just given up on RSD Lite, because what happens is it is supposed to detect my phone when I plug it in it doesn't. I have a new problem, though. I followed this guide - https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110.
He said that it would be safe to flash a new version (I've been flashing 5.1.1, and I tried flashing 6.0 this time). Now my phone is stuck on the "Warning Bootloader Unlocked" screen.

Wait, maybe will boot...?
Why do you quote me if you aren't doing what I suggest?
Ask in thread you linked.

All right, I finally fixed both issues. I just flashed 7.0 on there and it unbricked it and I guess fixed the radio firmware.
Thanks for help leading me in the right direction and sorry if I was a pain in the rear to help.

[Q] Boot looping into TWRP, XT1768 Qualcomm, can boot via "factory mode"

Hello all! Been a member for years but haven't had to post anything for a very very long time. Having a very strange compound set of issues with an XT1768 Moto E4. I bought this phone about two years ago but only used it for a couple of months. I did unlock the bootloader and install TWRP back then but don't remember what else, not sure if it was a custom ROM or not.
It's sat in a drawer for over a year, and I decided to let my kid have it for Christmas. It booted up fine and had 80% battery, all my apps etc. Every thing worked. Then I did a factory reset. After doing the reset, the phone booted into TWRP and would only boot into TWRP after a couple more reboot attempts.
So I downloaded and installed the Stock Plus ROM from XDA, following the instructions to wipe system, data, dalvik and cache first. After flashing, the phone would still only reboot into TWRP. On a whim, I rebooted to bootloader, then selected "factory mode", which then booted normally. The phone worked fine for about a day, but would occasionally reboot on its own and boot into TWRP. Now, the phone does not want to charge,and will reboot into TWRP when disconnecting the USB cable.
I really just want to flash the phone back to 100% stock, factory image. No TWRP, locked bootloader. My kid doesn't need any of it, just a reliable stock phone. I've been googling and searching XDA but information I'm finding is very confusing since there seem to be several e4 models. This one is an unlocked, Qualcomm variant as far as I know. I can't find a 100% stock image to flash or clear instructions to restore back to 100% stock, locked.
Can anyone point me in the right direction? Is Stock Plus good for the XT1768? Is there a way to go back 100% stock with clear instructions? Or to fix the issues with charging and being stuck rebooting into TWRP? Do I need to flash "no verity", whatever that is? I have not done any rooting or unlocking or flashing of Android for quite a while and am a bit Rusty, but I know my way around TWRP and ADB, etc. Any help would be immensely appreciated!

bast525 said:
Hello all! Been a member for years but haven't had to post anything for a very very long time. Having a very strange compound set of issues with an XT1768 Moto E4. I bought this phone about two years ago but only used it for a couple of months. I did unlock the bootloader and install TWRP back then but don't remember what else, not sure if it was a custom ROM or not.
It's sat in a drawer for over a year, and I decided to let my kid have it for Christmas. It booted up fine and had 80% battery, all my apps etc. Every thing worked. Then I did a factory reset. After doing the reset, the phone booted into TWRP and would only boot into TWRP after a couple more reboot attempts.
So I downloaded and installed the Stock Plus ROM from XDA, following the instructions to wipe system, data, dalvik and cache first. After flashing, the phone would still only reboot into TWRP. On a whim, I rebooted to bootloader, then selected "factory mode", which then booted normally. The phone worked fine for about a day, but would occasionally reboot on its own and boot into TWRP. Now, the phone does not want to charge,and will reboot into TWRP when disconnecting the USB cable.
I really just want to flash the phone back to 100% stock, factory image. No TWRP, locked bootloader. My kid doesn't need any of it, just a reliable stock phone. I've been googling and searching XDA but information I'm finding is very confusing since there seem to be several e4 models. This one is an unlocked, Qualcomm variant as far as I know. I can't find a 100% stock image to flash or clear instructions to restore back to 100% stock, locked.
Can anyone point me in the right direction? Is Stock Plus good for the XT1768? Is there a way to go back 100% stock with clear instructions? Or to fix the issues with charging and being stuck rebooting into TWRP? Do I need to flash "no verity", whatever that is? I have not done any rooting or unlocking or flashing of Android for quite a while and am a bit Rusty, but I know my way around TWRP and ADB, etc. Any help would be immensely appreciated!
Click to expand...
Click to collapse
Good source for firmware
https://mirrors.lolinet.com/firmware/moto/perry/official/
Probably use Retus software channel
Sent from my mata using XDA Labs
---------- Post added at 04:06 AM ---------- Previous post was at 04:00 AM ----------
The XT1768 is Qualcomm
Flash command s should be
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
Sent from my mata using XDA Labs
---------- Post added at 04:08 AM ---------- Previous post was at 04:06 AM ----------
Some good instructions in
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
Or my
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
Sent from my mata using XDA Labs

Many thanks! I will try the most recent image in the Retus folder using those commands you posted! Thanks!