Database Users

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

[Q] please help with my nexus....

I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:

Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck

Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app

olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)

bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you

[Q] Droid Razr M not fully booting: Help Please

Hello,
Problem:
factory reset my Droid RAZR M with the hope to resolve in-call audio problems (very low ear piece volume at full). When I rebooted the phone the Welcome screen appeared asking for a language choice. Chose english US. The Message: "Please wait, This may take a few minutes" appeared with a spinning icon. But nothing else ever happens. The phone never moves beyond this selection.
I have android-sdk (Linux setup) installed on my computer in order to use the suite of tools like fastboot and adb. The tools work, in that I can see the phone, pull data, upload to the phone and even get a command shell on the phone. However in order for adb to recognize the phone I have to put the phone in "BT Tools" mode. In "AP fastboot" mode fastboot sees the phone. As far as I remember USB debugging was turned on.
I do not have a recovery image installed.
The phone has Kitkat 4.4.2 ver 183.46.10 and is rooted with TowelRoot. I just unlocked the bootloader today via motoapocalypse package. Status of the phone is unlocked Code 3
I also removed some unused apps - like NFL and a few other space and bandwidth consuming apps that I will never use.
I'd like to get this phone to work again. Is there any hope?
Please advise and thanks for reading.

You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More

Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Klen2 said:
You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More
Click to expand...
Click to collapse

diordnAMRZAR said:
Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Click to expand...
Click to collapse
You can try using SBF_FLASH or mFastboot-v2 (which has a linux version) to flash the system.img .

SOLVED: [Q] Droid Razr M not fully booting: Help Please
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!

diordnAMRZAR said:
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!
Click to expand...
Click to collapse
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.

ATTACK said:
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.
Click to expand...
Click to collapse
Well I'm happy to have the utility that works. Can thank you enough -- or the creators. Found it also on goggle code after a properly crafted search string. All this for an in-call audio problem that only worsened after I took the phone apart. Still works on speaker mode though so that's good enough -- at low volume. And I learned a few things. One interesting thing: The shell prompt got rewritten to say ${USER}@scorpion_mini/ after flashing the system.img. Pretty sure it only said android prior to re-flashing . And the getprop helper app is a new thing for me.
Feel like a kid all over again exploring this little device.

Just need someone to confirm that I'm SCREWED

I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.

6.0 is the current update...
Flash twrp then try flashing a custom ROM. Honestly it sounds like you might be doing something wrong, or maybe a bad USB cable? Keep trying I don't think you're screwed

Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Do you still have an custom recovery installed? TWRP?

Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.

acejavelin said:
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
Click to expand...
Click to collapse
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.

Steeleio said:
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Click to expand...
Click to collapse
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk

acejavelin said:
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Pure. I figured if I start all the way over from the beginning it would work out. Like I said, even one of the OTA's failed. I tried flashing the BTFM.bin file but that didn't work either. I will try some other stuff when I get off work today.

So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?

Steeleio said:
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Click to expand...
Click to collapse
No, in fact it is quite common to get that message with the partition information... Ignore it, if everything else went fine and you having no more problems, your good to go.

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