Database Users

[OTA ZIP] Pure Edition XT1095 Lollipop 5.0 22.11.6 & 22.21.11

NEW 22.21.11 OTA Zip posted on the site 12/1/14
YOU MUST BE ON 22.11.6 TO UPDATE
NEW 22.11.6 OTA Zip posted on the site 11/11/14
http://www.graffixnyc.com/motox.php
OTA is there!
Instructions:
This is ONLY for the XT1095 Pure edition.. Support priority will be given to those with a XT1095. If you have another model number you will have to figure out how/if you can run this OTA. It's not up to this thread to support devices the OTA was not meant for.
IF YOU ARE ON THE FIRST SOAK TEST OTA .5 YOU CANNOT UPDATE TO .6. IT WILL FAIL! YOU WILL HAVE TO DOWNGRADE TO 4.4.4 THEN APPLY THE .6 OTA
Follow @SolarTrans Guide found here: http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Be unaltered unrooted system. The device cannot be rooted and then unrooted.. it must be a never rooted system or the update will fail. It seems it's failing on devices that were rooted and then unrooted. On devices that were never rooted or where the user had stock back up they made prior to rooting the ota will update fine
Boot into Stock Recovery
ADB Sideload the zip
For people getting the modem error. Make sure you back up your current modem using the DD command (google if you don't know how)
After that download the AT&T modem from my website, flash it, then take the OTA. You MAY lose LTE after the update. If you do just reflash your old modem and you'll be good to go. It's also been confirmed if you reflash the AT&T modem after the update you will get LTE back.
Download Links can be found on my website: http://www.graffixnyc.com/motox.php
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....

This is going to sound really nooby but do i just flash this in recovery? Or in the bootloader?
Sorry, this is my first Moto device, have had Nexus and HTC phones before this

Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks

jellydroid13 said:
Use ADB sideload to flash on a stock unrooted system. Went through perfectly for me and currently optimizing apps. Thanks
Click to expand...
Click to collapse
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?

THEindian said:
So, unroot, flash stock recovery, then go to the bootloader and adb sideload?
Click to expand...
Click to collapse
yeah but go to recovery and sideload

I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.

dmbfan13 said:
I'm rooted, but still stock recovery. Can I still boot to stock recovery and sideload?
Also, how do I adb sideload? Can someone explain? I have somewhat of an idea, but want to make sure before I go ahead and do so.
Click to expand...
Click to collapse
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!

Can be root achieved?
sent from my Nexus 7

THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
<snip snip>
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
Same thing happened to me. I suppose we'll have to flash stock back?

THEindian said:
Yeah, so i just got it to start flashing. Yes, you have to be unrooted but this is pretty simple, to unroot:
Go to the SuperSU app, go into the 3rd tab with all the settings, in there, there should be an option, something along the lines of "clean unroot", hit that, it should only take a minute or so
If you still see the SuperSU app once thats done, go into the play store and uninstall it
You are unrooted
To flash, plug in your phone and type in "adb reboot recovery"
You'll the that little android, once you see this, press the UP volume button, then power button, then release
Scroll down to where it says apply update from adb
type in "adb sideload BLAH BLAH BLAH.zip"
It should start applying. Hope this helps!
CRAP. I got an error in the installation and now it won't boot. It was something along the lines of how it didn't have the intall-recovery.sh file. Someone please help!
Click to expand...
Click to collapse
It seems like either the install-recovery.sh file was removed when you unrooted (SuperSU uses that file) or it detects it has been modified and is failing. You will have to ask someone to pull it from a non rooted device

I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.

Is there a guide to re-root?

will I get the next OTA if I sideload the soak test?
just wondering.

Mine is also bricked due to using unroot in supersu....

THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
I am in the same boat as you.

edwardgtxy said:
Mine is also bricked due to using unroot in supersu....
Click to expand...
Click to collapse
Yeah... mine's in a bootloop that I can't seem to stop. Holding the power button doesn't actually seem to turn it off. The screen goes black... and then eventually it just starts up again.

Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?

matt99017d said:
Im getting an error that says /modem/image/modem.b00 has unexpected contents.
any clues?
Click to expand...
Click to collapse
Same here.

THEindian said:
I assume so, trying to do this but i have yet to find a stock image, the only is the one OP has his website is almost down. Do you know where else i could get an image?
---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------
Could you mirror your system.img to dropbox or mega or something? The download for the system.img is taking 1 day.
Click to expand...
Click to collapse
No, do not mirror my files. I like to keep count of my downloads. Get a better internet connection. I downloaded the file in less than 5 minutes as others did.
It appears you need a non-rooted system image that's never been rooted. You need to be fully stock. Not rooted and then un rooted. I believe the unrooting process still leaves files in an altered state than their original. If there is a single extra character in a file, if it's the slightest smallest difference the file is considered altered and will fail OTA checks.
Quite a few people have tried this and it has worked. It seems the ones it's failing on are ones that were rooted then unrooted. Derek Ross just told me it worked like a charm for him.

any tips to stop the boot loop? I am parking mine in recovery now to drain the battery.
Btw, it seems the OTA modified modem, system and boot. So theoretically, we can just use fastboot to go back to the your imgs, and the phone should still work right?

Disable security warning at boot for MHC191

It seems to be from searching you can use a custom vendor image? I'm on stock with root. Everything went smooth as butter but i'm still unclear on this as i know custom roms dont have it i believe. Is there a thread i'm missing where these are listed or is there anything i can flash? It's not a big deal whatsoever but the ocd in me felt compelled to figure it out lol.

Download factory image for what build your on, unzip and flash vendor.img in twrp 3001 done.
Sent from my Nexus 6P using Tapatalk

SM210 said:
Download factory image for what build your on, unzip and flash vendor.img in twrp 3001 done.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks. I didn't realize that's all i had to do. I spent half the day setting everything up how i wanted and didn't want to mess it all up. Thank goodness for backups now.
Update: I flashed the vendor image in twrp in vendor and the corrupt message at boot is still there. Maybe i wasn't clear. I'm talking about the locked boot loader message

If you're running stock you have to re-lock the bootloader to get rid of that message on power on.

Zaphon said:
If you're running stock you have to re-lock the bootloader to get rid of that message on power on.
Click to expand...
Click to collapse
Ok. There seems to be a workaround for everything once your rooted so i thought maybe there was something for this also.

bckrupps said:
Thanks. I didn't realize that's all i had to do. I spent half the day setting everything up how i wanted and didn't want to mess it all up. Thank goodness for backups now.
Update: I flashed the vendor image in twrp in vendor and the corrupt message at boot is still there. Maybe i wasn't clear. I'm talking about the locked boot loader message
Click to expand...
Click to collapse
Are you talking about the orange "your device can't be checked for corruption" message or the red "your device is corrupt message"? The orange one is standard if you have an unlocked bootloader, there's nothing you can do about it apart from locking the bootloader. I'd advise dealing with it though, it's better to deal with that orange message than to deal with the potential consequences of having as locked bootloader when something goes wrong.

Heisenberg said:
Are you talking about the orange "your device can't be checked for corruption" message or the red "your device is corrupt message"? The orange one is standard if you have an unlocked bootloader, there's nothing you can do about it apart from locking the bootloader. I'd advise dealing with it though, it's better to deal with that orange message than to deal with the potential consequences of having as locked bootloader when something goes wrong.
Click to expand...
Click to collapse
yeah that's what i was talking about and i agree. i just thought maybe there was a work around i may be missing. Thanks everyone for the help. Been flashing for years. This one had me lost. Nexus 6p is one incredible phone. I always loaded custom roms right away on Samsung devices but with xposed and root this is more than enough running stock. I even skipped a toolkit for the first time and battled windows running on my mac. not fun lol.

All customs Roms also have this. Dirty unicorns, resurrection remix and cm. I understood in op what you meant. That message can also alert to if someone messed with your phone, it'll change to red and say your device is corrupt. I think when /system is modified. I got that once or so.

Axon 7 brick

I've spent the whole night trying to figure this out, but to no avail. Here goes...
Hey guys, so I was innocently playing around with GravityBox when I restarted my phone so some new settings would kick in, and it sends me into a bootloop. I went into TWRP Recovery, and at first factory reset my phone, hoping it would solve the problem, but it didn't, so I ended up "Formatting Data", which still didn't work. I'm kind of new to this whole flashing/rooting/ business, and I was wondering how I could fix my phone. If turned on, it stays in the booting process with the golden "Axon" letters forever. The model is the US variant, it's bootloader is unlocked via the ZTE Request Form, and it currently has TWRP as it's custom recovery. Help will be much appreciated. Also, it's on OTA B20
Edit: Alright so I've tried to flash to boot.img as well as recovery.img in twrp, but both give me an error. Strangely enough, if I wait out the Axon logo for about 5 minutes, it actually boots up, but as if it was the first time turning it on (asks you to sign in to google, wi-fi setup, fingerpring setup, etc). Another thing I noticed was that it says I only have 4gb of storage, instead of the 64 it originally came with. Every time I reset it/turn it off, it makes me set up the phone again.
Edit #2: Fixed with the help of this thread http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895 Only problem seems to be that Wi-Fi does not work. /:

I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk

raber111 said:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
Click to expand...
Click to collapse
I don't have a TWRP backup to restore to ): if that's what you mean, any other solutions?

I didn't have to but I found a backup on XDA . And I don't really know if you should use it or you should wait till full stock image will release.
Отправлено с моего HTC One M8 через Tapatalk

Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895

reddrago said:
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
Click to expand...
Click to collapse
I'm in the process of doing this as of right now, thank you. Will update.

It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!

Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.

Barsky said:
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Click to expand...
Click to collapse
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk

flyer_andy said:
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Click to expand...
Click to collapse
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.

bricky23 said:
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,

Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
I'm in the exact same boat. Did you ever figure out how to get wifi back?

Pollito788 said:
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Click to expand...
Click to collapse
Am I missing something. that dev-host site sends me exploit installers. good thing I do nightly acronis images.

Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
Flapjack said:
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Click to expand...
Click to collapse
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one

peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.

peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Would not mind fixing this rather than shipping my packed up axon7 to newegg. Think I have a few days before it has to ship, so I am open to working on it some more.
Thanks.
---------- Post added 08-29-2016 at 12:00 AM ---------- Previous post was 08-28-2016 at 11:51 PM ----------
Flapjack said:
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
Click to expand...
Click to collapse
Try flashing the 2.65 ver over it

peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .

Barsky said:
Try flashing the 2.65 ver over it
Click to expand...
Click to collapse
That's the thing.... I've restored it repeatedly. All traces of 2.67 should be gone. I've completely restored it three times now.
I'm honestly thinking I'm better off returning this phone while it's still working. I wonder if something is wrong with it.

DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
tysm bro <3

DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
Brings DrakenFX some coffee and nudges him awake. :cyclops:

Phone will only boot into TWRP

So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.

hegro said:
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
Click to expand...
Click to collapse
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.

GtrCraft said:
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
Click to expand...
Click to collapse
Pretty sure I was just stock rooted. How would I go about doing that? Like I said, I have a stock rom downloaded on my PC. Tried to flash it but all I get is 'waiting for device' in the cmd window after directing it towards the zip file.
Also as I said, trying to learn and absorb as much info as I can here, never done this before so I am a little slow. =/

just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?

hegro said:
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
Click to expand...
Click to collapse
Boot to twrp and flash a custom rom zip like lineage os. Or a modified stock rom like stoneware

Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.

hegro said:
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
Click to expand...
Click to collapse
I had this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig

Go into fastboot and just type fastboot continue
fixed

alevity said:
I has this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Click to expand...
Click to collapse
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.

hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash

power off your phone then volume down and power together until bootloader screen appearing than select factory mode and then press power button to select factory mode

hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bornlivedie said:
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
Click to expand...
Click to collapse
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.

pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.

hegro said:
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
Click to expand...
Click to collapse
That's stock recovery

alevity said:
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
Click to expand...
Click to collapse
I wouldn't know about "perfectly ok" but I had that bad key thing before, and read the rebooting into TWRP fixes the "issue". It's true, it works. I have N/A now and not "bad key".

corrupted boot img(Qualcomm)[boost]

I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.

Thexmastermind said:
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.
Click to expand...
Click to collapse
Your not going to get a signal with Boost or any other CDMA carrier with custom ROMs right now. They work for GSM models but need to be fixed for CDMA.
Sent from my Moto E (4) using XDA Labs

Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.

Thexmastermind said:
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Click to expand...
Click to collapse
If you don't already have it, the Boost stock firmware is here: https://firmware.center/firmware/Motorola/Moto E4/Stock/
Download this one:
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
If you can't get RSDlite to recognize your device, you'll have to use adb/fastboot to flash the firmware manually piece by piece.
Sent from my Moto E (4) using XDA Labs

RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.

Thexmastermind said:
RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Click to expand...
Click to collapse
I'm not sure what your problem could be other than not having the correct firmware. I haven't used RSD with this device (maybe someone who has will chime in) because it wouldn't recognize it so I've just been flashing it with fastboot on Windows with a script to flash everything automatically, so it's just as easy. It's the only time I really ever use Windows. You shouldn't need to erase anything before flashing. I've never had to. Be careful using the erase command, I've seen users screw up partitions using it and ending up with a brick. I only use it erase modem st1 and st2 and to wipe data.
Sent from my Moto E (4) using XDA Labs

I only have Linux ATM. My machine had XP on it till it crashed setting up eclipse lol rsd communicates with the device fine, so I'm assuming it's the firmware. Like I said I'm at family's for the holiday, but I'll keep you posted when I get home.

Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.

Thexmastermind said:
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Click to expand...
Click to collapse
Pretty sure no verity zip or magisk takes care of that (though you get n/a in the corner)

I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?

Quick question: when I flash twrp, leave it as read only, correct? Then flash verity, then su?

Thexmastermind said:
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Click to expand...
Click to collapse
No, don't leave it read only.

So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.

Thexmastermind said:
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
Click to expand...
Click to collapse
Yes

Alright, so I got an error message about a bad key when I tried flashing twrp. I booted into twrp from fastboot via command line, flashed verity, flashed su "successfully" just waiting on partition details to be updated....
But it feels like it's been a good ten minutes of nothing happening. I ran the following from desktop:
adb shell whoami
Return was:
root
But I'm still waiting for it to update the partition details...

GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.

Thexmastermind said:
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Click to expand...
Click to collapse
You don't delete it. Be careful debloating.

Yeah I noticed there were a handful of apps that don't want be uninstalled. I saw a thread about it so I'll probably do a little more research.

how recovery?
pretty much same deal... how did you recovery to work