Database Info

Thinking about unrooting Read this first!!!! ALL MODELS

**********Please Sticky**********
(MOTOROLA HAS RELEASED ALL THE IMAGES FOR ALL COUNTRY VERSIONS OF THE XOOM RECENTLY MAKING THIS A UNIVERSAL TUTORIAL AT THIS POINT)
Listen I notice recently there is a flood of issues with the xoom using different unrooting methods. I personally will say to unroot your device just bring it back to stock images. Its the safest method with the other methods if you do not know what you are doing you will find yourself sending your device to motorola for warranty repairs.
Here is a short and sweet way to unroot your xoom. by doing this you will lose your data and information so start by backing up your stuff to a computer if you have any important things on there.
if starting fastboot is on your xoom screen open up a command prompt:
0. For those who've modified their boot splash graphic with Team Eos' Splash Screen Logo Maker make sure to restore the stock Motorola boot splash FIRST as this process doesn't touch that part of the system. (Posted by Bait-Fish *Thanks for the update*)
1. Goto: http://forum.xda-developers.com/showthread.php?t=1049485 for stock USA 3G and Wifi Images
2. download the files you need
3. extract all the img's into the tools folder
4. with the command prompt open type: cd "replace with tools directory location"
5. disconnect your xoom from your computer and shut off the xoom
6. at the prompt type: fastboot oem unlock
7. it will say waiting for device
8. now plug it into your computer and reboot into fastboot by holding the down volume button and power on
9. follow the on screen instructions and agree to everything
10. your device will reboot you will get the motorola dual core window
11. force restart device by holding volume up and pressing the power button right after the device shuts off hold the down volume button and press power button
12 you should now be in fastboot mode
13. then copy each line one by one into the command window. This will allow you to go back to factory settings like you bought it from the store
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata

Good write up. +1 for sticky if there's not something already.
Sent from my SPH-D700 using XDA Premium App

whats good about this post is that it has been fully tested by me with wifi and 3G versions of the xoom with no problems reported. This method has also fixed some RSD issues. I say some because some people have flashed wrong boot images and ruined fastboot on their xooms from seeing the desktop.

wow you would think with all the issues happening with oneclick root etc you would think this would be a highly read thread. lol.

Nice guide man.

Good to have a thread like this as I was one of those one-click rooters. Unrooted, semi-bricked and learned ADB. If you're going to play with your Xoom, at least have a general idea of ADB.

Please add that this instruction (original post) is only appliable to US Xooms. Not EUs

Thanks!
Thank you so much!
I was also a clueless one-click rooter. I'd tried everything to get rooted again. This was by far the clearest and saved my hanging around waiting for a one-click unroot solution.
Cheers

your welcome enjoy your xoom.

I already upgraded to 3.1, and I unlocked it, but I can't get CWM to work, so I can't root. Can I use this method to go back to the older HC and relock, then go back to 3.1? I bricked mine before, trying to unroot and relock (I know...I know...) I've been adb'ing like crazy trying to get CWM to work, but I feel like giving up and going back to lock, stock, no barrel.

you can if you want it wont hurt the xoom which xoom do you have wifi or 3g?

I have the wifi, running 3.1, build HMJ37

if you go back to 3.0.1 you can root it, install clockwork, then upgrade to 3.1 using clockwork method. its pretty simple. within 25-30 minutes you can be running with clockwork and 3.1 rooted.

I learned my lesson! And the forum saved me.
I did the one-click root back when I got my Xoom a couple months ago, and then when I tried un-rooting and relocking to get the 3.1 update, I bricked it (you're welcome, angel) and sent it back to Motorola. When I got it back, I tried rooting the long way, but couldn't push CWM onto it. I got lots of help and tireless support from a forum member, and finally got it unlocked, rooted, CWM'd with SD support....re-lovin' the Xoom now. And I'm glad the guy that helped me out made me re-check re-download, and redo everything just to make sure we weren't missing any steps.
I love the Xoom NOW, but when I got it back from getting fixed, I was so not happy with it being unrooted! I love to toy with stuff, and this was a real learning experience. Doing all the commands, getting the stock images, re-flashing....it was very rewarding, even though it took so long to figure out how I screwed up. (can you believe it was a usb cable that wasn't working that made it so difficult! Pushed some things, but not others....changed cables, and everything worked fine.)

Nice walk through. I don't think I'll be unrooting anytime soon but its good fyi.
Sent from my Xoom using XDA Premium App

this tutorial should be more helpful now.

dirtymindedx said:
this tutorial should be more helpful now.
Click to expand...
Click to collapse
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom

bwcorvus said:
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom
Click to expand...
Click to collapse
how do i go about doing that.

dirtymindedx said:
how do i go about doing that.
Click to expand...
Click to collapse
I would just edit line 1 to say you can get from moto at blah blah or download from blah blah so you don't have to log in.
http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom

nice set of links definitely treasure in my book. Can you post a link on there to this thread since they still haven't stickied this yet?

HELP!! No Android Recovery option

Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers

ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!

djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.

The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?

yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019

Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....

im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.

I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.

solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom

DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?

assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.

okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.

According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?

no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?

autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help

much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _

fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.

the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?

aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.

I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?

[Q] Stuck on bootscreen after using Odin

Well, here's what happened:
After flashing some different ROMs (which has been no problem in the past) my phone started acting weird...I don't really know how to describe it, it randomly crashed or didn't react, sometimes I couldn't even turn it off so I had to remove the battery and reboot it. Suddenly, the only ROM that I could flash was this one: OTA 4.04 The problem was that I got a lot of force closes so I couldn't really use it. After I spent hours on google and tried to fix the problem, I came across Odin. It seemed pretty easy and I followed a tutorial to set my Nexus back to stock Gingerbread.
Odin seemed to work perfectly and my device rebooted, but I am now stuck on the bootlogo (Google screen with the unlocked sign) and can't do anything else.
Any help, please?

Search around for "fastboot factory images" and flash one of those. Download from official google website. Note that it'll remove all apps, data, etc. Only files on the "sdcard" will be kept.

I tried to flash gingerbread and jelly bean images, following this guide. Didn't work though...it may be worth mentioning that somehow adb does not recognize my phone, fastboot however does. It says in the guide that you don't have to use adb necessarily, so I'm a bit confused that it didn't work...thanks for your reply anyways.
any more advices?

Do you actually know what you're doing? Odin socks, use Cwm recovery for flashing roms. It seems that you make flashing mistakes, dirty flashing etc. Also apps crashing is resolved with fix permissions. Read the big faq for correct flashing instructions
Sent from my Nexus S

b0ld said:
I tried to flash gingerbread and jelly bean images, following this guide. Didn't work though...it may be worth mentioning that somehow adb does not recognize my phone, fastboot however does. It says in the guide that you don't have to use adb necessarily, so I'm a bit confused that it didn't work...thanks for your reply anyways.
any more advices?
Click to expand...
Click to collapse
do this:
fastboot flash bootloader (bootloader.img)
fastboot rreboot-bootloader
fastboot flsh radio (radio.img)
fastboot reboot-bootloader
fastboot -w update (image-blabla.zip)
one more thing: ODIN ISNT NECESSARY FOR NEXUS!!

Where did you find (factory) odin images for the Nexus S, I didn't know they're available this device. In any case Odin probably aren't meant for Nexus devices.

Dont even think about using them!!! We have to stop with this! Odin was made for samsung devices but for those made by samsung not by google! Google phone use fastboot for that, odin can screw up your nexus
sent from my Nyan NeXus S
"You're either NEXUS or against us!"

Droid RAZR HD @ No Valid PIV block in Sp for system

Hi guys. First, trust me that I have looked at every post I could find regarding this issue and the reason I am starting a new thread it because the fixes are not working for me. First, my phone:
Droid Razr HD Dev Edition, I believe it's the T926, though it doesn't boot now so.....
I had rooted this phone with the Droid Razr HD Utility 1.1. I had it running on T-Mobile fine for quite some time (only HSA speed or whatever they call it, but that's fine I'm out of range for anything better anyway). I had Superuser installed and something like root keeper I think it was called. Anyway my point is everything worked great.
I started getting this popup that seemed to say Motorola wanted to do an update. Now I had ignored the update on my phone for a while as I didn't want to go through the process just yet. Finally I gave in and I let the Motorola from my Windows PC try to push an update. That was the last my phone has booted.
So now all I get is Fastboot. Now if I do the buttons and manually go to fastboot it looks normal and I connect USB and it looks fine. But if I try to run the HD Utility 1.10, 1.20 both fail, RSDLite 5.6 and 6.0 both fail. All I can come up with is No valid PIV block in sp for system. The phone does seem to respond when I try the utility but all I get is failures and it clearly says the phone is locked. RSDLite has no such luck and immediately fails.
I still have the original XT926 xml I used and I also downloaded a VZW_XT926. I'm really SOL here guys and I would so appreciate any help.
I guess the last bit of info I can think to add is that when I plug USB in fresh what looks like Motorola software (what messed me up to begin with) pops up and tells me it wants to repair the phone. Of course like an idiot I've tried that as well.

My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com

coolloser said:
My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com
Click to expand...
Click to collapse
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.

Dagroth said:
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.
Click to expand...
Click to collapse
After Jellybean there needed to be new Fastboot files because of some security change in Android, the newest utility most likely has it. I found this file
http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
in this thread:
http://www.droidrzr.com/index.php/topic/15828-rsd-lite-stock-412-firmware-restore-not-working/
If you are still stuck after that I suggest signing up on DroidRzr.com and joining the chatroom, those guys know far more than I!

Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.

Dagroth said:
Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.
Click to expand...
Click to collapse
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!

Unbricked
Dagroth said:
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!
Click to expand...
Click to collapse
I was trying to load a different ROM (running 4.4.2) so I could unlock the bootloader and root and hard bricked my phone with the same error message as a result of a failed flash. Using the fastboot command (fastboot flash system system.img) I was able to load the system.img from VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml and now am booting successfully once again.
Dagroth, you pulled my fat outta the fire! Many thanks. I hope this message helps others.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!