Database Info

[Q] (Q) NS3G - All partitions formated and cannot boot phone

Let me start off by saying that this is the worst experience I have ever had with a cell phone manufacturer.
I got the OTA update 2.3.6 and went with the install. I looked it up online and there was no information on it so I went ahead and installed it. After the install I had no cell service. This issue has been well documented but not before I tried to fix it.
So I tried to roll the update back to 2.3.4 and it seemed to be successful however the radio still did not work.
I was told by a Samsung rep that if I unlocked it, rooted it, and formatted ALL of the folders including the data, system, boot, cashe, and the entire sdcard then flashing a stock ROM would re-install everything including the radio files.
Well now all I have is a brick and I am stuck. I'm using CM5 as the recovery so I'm not completely dead. When I boot the phone up it says "no boot or recovery img" but I can select recovery and CM5 comes up.
I'm asking where to start... I want to get back to stock everything and lock it back up if my radio will not work so I can send it in for repairs. I think I'm screwed but I'm sure if anyone could fix it it must be on this developers site. I can't find documentation on it online and I know it must be out there because I can't be the only dumbarse to do this.
Respectfully,
Mike C.
Phone: Nexus S 3G AT&T

Perhaps you can mount the phone as storage, copy a rom over then flash it.

Fear not. Get everything you need here:
http://forum.xda-developers.com/showthread.php?t=878786
You need to be in the tools folder. The command you need is
fastboot flash recovery recovery.img
Get a recovery.img from the development section. I personally prefer Team Win Recovery Project (TWRP) Make sure you rename it to recovery.img if it has a different filename/or change the command above.
Once you have recovery on your phone you can access USB mode to copy a ROM to your phone, then flash it.
Since there will be no need to return your phone, no need for stock! So take your pick from what's available. I personally think brainmaster's MIUI is amazing.
Sent from the future to put right what once went wrong.

Sorry, assumed you know stuff about using commands. If you're unfamiliar with the command prompt, PM me.
Sent from the future to put right what once went wrong.

Also, if you get it all sorted but find you still get no signal, that can be resolved by flashing the right radio for your phone. Read the radio section in the development section. It's easy. If you still experience problems, let me know.
Sent from the future to put right what once went wrong.

[Q] HTC One S(ville) black screen, thats it... just a black screen, what can i do???

I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?

Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry

Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!

You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.

I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.

Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best

Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]

yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol

good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed

Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:

you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe

rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:

see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands

rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up

I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track

rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot

good luck on it

[Q] Rooting, Flashing, Upgrade services needed!

I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....

Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.

Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?

dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.

junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.

dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....

I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.

dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:

If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app

Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!

did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.

what step are you up to?

Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......

i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.

OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!

here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?

Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?

What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?

Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....

Great let us know what happens. I will be around for a while.

[Completed] HTC Vivid won't boot, possibly after build.prop change

Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.

Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.

jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.

Thread closed.

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!