yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Q&A, Help & Troubleshooting] lost101:
[MENTION=5260103]Sevael[/MENTION] - Thanks for pointing this out. The motoboot.img is now known as bootloader.img in Osprey firmware images. The motoboot partition is also different, now known as 'bootloader.'

The new command to flash Bootloader file is therefore:

mfastboot flash bootloader bootloader.img​
[Moto G 2015 Q&A, Help & Troubleshooting] nelsonw:
Will be great to add (if isn't there already) this on the OP of osprey FW post. Thanks!
[Moto G 2015 Q&A, Help & Troubleshooting] lost101:
Working on it now.
[Moto G 2015 Q&A, Help & Troubleshooting] Sevael:
I tried ADB, fastboot and mfastboot, they all return empty lists. I even tried the qboot solution for older Moto Gs. It doesn't respond to anything. I was on the internet for four hours looking up solutions and trying everything and nothing worked. Best I can tell, the bootloader is corrupted or missing. Since I can't get into the bootloader, I can't reflash anything to fix it.

According to the later pages of this thread, there are software tools out there which would fix this exact problem, but no one on XDA has been able to get their hands on them for the 3rd gen Moto G. Seems that only Motorola and perhaps some authorized repair places have access to the tools.

It wouldn't be such a big deal if this wasn't my only phone. I've previously had Samsungs and LGs and modded the hell out of them and it was always easy to recover from any type of issue via Odin or LG FlashTool. This is my first Motorola and I'm quickly learning that it's a much more fragile beast. I'm thinking that this might be my last Motorola for that very reason. I like to mod but I don't like this kind of fragility. I technically made no mistakes (just followed the guide I was directed to) and now my phone is hardbricked.

I have to go out and buy another phone this morning. The Moto G is an amazing phone for the price, but I'm not sure I want to risk it again.
[Moto G 2015 Q&A, Help & Troubleshooting] lost101:
[MENTION=5260103]Sevael[/MENTION] - Are you using Fastboot in Windows or Linux?

Edit: From what you have described, the bootloader hasn't even been touched.
[Moto G 2015 Q&A, Help & Troubleshooting] nelsonw:
I'll look into that thread and see how i can help you. But some command must be wrong to achieve that king of brick. For sure isn't Motorola issue... Give me some time and look into that.
[Moto G 2015 Q&A, Help & Troubleshooting] Sevael:
Windows.

I followed all instructions. The files were all in the same folder, I copy/pasted the commands to ensure no typos, I carefully went through line by line. But something is different about the 3rd gen that the tutorial from the first gen just doesn't seem to work.

I know that I had things setup right because I was able to get TWRP flashed no problem. Installed CM, gave it a whirl, decided to go back to stock. Went back into the bootloader (didn't re-lock it at any point, that might have been my mistake), then tried to follow the linked guide to restoring the stock firmware. I even downloaded the firmware archive twice to ensure that it was correct. I extracted it all into the folder with the ADB and mfastboot files.

That's what I thought, but the phone does not boot into the bootloader under any circumstances. I tried things like holding the power and volume down buttons for two minutes (tried both when plugged into PC and unplugged). I tried just the power button for two minutes. I tried every software solution I could find online (four hours of searching and trying). Nothing worked.

Fortunately, the store rep bought my story when I told him that the phone was like that right out of the box and he gave me a full refund. So I grabbed a different phone.

Thanks for trying to help out guys, I really appreciate it. XDA is always an awesome place. I'm not done with Motorola, but I've picked up a Moto X Play to try for now. Fingers crossed!

Thanks again.
[Moto G 2015 Q&A, Help & Troubleshooting] lost101:
[MENTION=5260103]Sevael[/MENTION] - I'm glad you got out of the situation easily.

I've added a new guide for flashing Firmware Images in 'General.'

The only significant difference is the change of name for the 'Bootloader' partition and bin file. Some people have previously posted in the Firmware Images thread that they had successfully restore Stock Firmware - following the old Moto G Tutorial. Maybe all of them skipped the 'fastboot flash motoboot motoboot.img' command.

Since the command failed for you, it doesn't make any sense that it would hard-brick the phone - unless simply by using that command a new partition was created on the phone called 'motoboot' - which conflicted with the existing 'bootloader' partition.
[Moto G 2015 Q&A, Help & Troubleshooting] scott_doyland:
It won't help you now, but technically all you needed to do to get back to stock was flash the system image files (and maybe the kernel if CM comes with its own kernel). You didn't even need to attempt to flash anything else. Its OK following guides but be aware that they aren't fool proof.
[Moto G 2015 Q&A, Help & Troubleshooting] Sevael:
I did try reflashing. As I said, the bootloader was gone. No devices detected by ADB, fastboot, mfastboot, qboot, or any other tool I tried. I put in commands and it just sat at "Waiting for device".
[Moto G 2015 Q&A, Help & Troubleshooting] nelsonw:
I'm glad that you get a Moto X. I can't understand what you did. But that is the past. Good luck and enjoy your phone! Thanks [MENTION=1006674]lost101[/MENTION] for the new guide.
[Moto G 2015 Q&A, Help & Troubleshooting] scott_doyland:
Hi,I meant for your first attempt at flashing back stock when your bootloader was OK. CM is just a new system image, you didn't need to even attempt to reflash a bootloader.

Even just using twrp to restore the system image alone would have got you back to stock.
[Moto G 2015 Q&A, Help & Troubleshooting] Sevael:
Yes, that's true. But at the time I didn't know that. There was a thread with links to the stock firmware and a guide how to flash it, so I followed it. Oh well, at least the issues I had have allowed for better information to become available for everyone.

Also true. I didn't take the time to create a backup of stock after first installing TWRP because I am used to Samsung and LG phones where you just download a single file and can restore the stock firmware image under any circumstances with no problems. It didn't dawn on me that a Motorola phone (this was my first) would be more complicated. I had (wrongfully) assumed that all Android phones were as foolproof as those two brands.

Especially Samsung. Odin plus the SamMobile website is like having an unlimited amount of get-out-of-jail-free cards. Why can't all Android phones work like that?
[Moto G 2015 Q&A, Help & Troubleshooting] scott_doyland:
I didn't know that about Samsung and LG as I have never had one. So I have also learnt something :)
[Moto G 2015 Q&A, Help & Troubleshooting] mcrammerdocdoc:
Anyone ever figure this out?

I just did basically the same thing as the OP, because I'm an idiot. If there's a way to recover (there's a fix for the 2nd gen model involving qboot, but I'm guessing the images are different) without having to hope Motorola will replace it without noticing the unlocked bootloader that would be awesome. Qboot.exe will recognize it, so if I had the right blank-flash images that would work in principle.

I still don't understand what happened. I skipped the motoboot step because I didn't want to replace the bootloader and now I can't even get the screen to turn on.
[Moto G 2015 Q&A, Help & Troubleshooting] lost101:
[MENTION=6922149]mcrammerdocdoc[/MENTION] - It would be helpful if you can provide as much detail about what you did, fastboot commands used etc. It's important to get a clear understanding as to why this is happening.

If you are not touching the Bootloader at all, then it can only be gpt.bin (Partition Table) - creating this situation - as all other fastboot files are benign. The other possibility is that it's not really hard-bricked; perhaps there is a bug suddenly dropping battery life to zero (this occurred with Moto G (1st Gen)) and letting the phone charge will resolve this.
[Moto G 2015 Q&A, Help & Troubleshooting] mcrammerdocdoc:
Yeah, sorry about that. Here's what I tried, ripped directly from Gammerson's stock-restore guide (new user, can't post the actual link apparently):

mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img # skipped; no motoboot.img in the zip
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

The only variations besides skipping the bootloader were the system.img chunks (there were 5 for my device) and the fact that I used plain old fastboot from the Android SDK vs. mfastboot. Right after that "fastboot reboot" command the screen went dead and hasn't done a thing since. Plugging it into a PC will get it listed as "Qualcomm HS-USB QDLoader 9008 (COM8)", which I'm guessing is some kind of emergency serial interface. I guess that means the battery isn't dead? Unless it's just pulling power out of the USB port. I'll try charging it for a bit and see if that helps.

Thanks! Hope some of that is useful. Seems like the thing to do would be dump a bootloader image over that serial link, but I've got no idea how to begin doing that.
[Moto G 2015 Q&A, Help & Troubleshooting] Sevael:
[MENTION=6922149]mcrammerdocdoc[/MENTION] that's exactly what happened with me.

It wasn't battery-related because it was nearly full when I did the final reboot command and it was dead immediately. I left it plugged in overnight and it didn't change anything.

The qboot thing would be the solution if we had the applicable software for the 3rd gen. There is a thread on XDA (I didn't bookmark it) where they were discussing the black-screen brick and the Qualcomm device showing up in Windows for all three gens of Moto G. The last few pages made it clear that 3rd gen owners with this issue don't yet have a solution.

I think it might have been in the 1st gen Moto G forum. The thread was over 100 pages long and involved all three gens.
[Huawei Ascend P6, Mate] :
Q&A for [Q] Enable USB Charging Only

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Q] Enable USB Charging Only. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[8125, K-JAM, P4300, MDA Vario ROM Development] boy_de_ghet:
I'm extract from Whiterat's ROM and good work on My Device

http://rapidshare.com/files/44308492/ArcSoftMMS_4.0.31.22.cab
[Samsung Gear Live] tims1710:
Hi everyone,

I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.

It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:

I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.

Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said

"Installation aborted.

OTA failed! Please power off the device to keep it in this state and file a bug report!"

I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.

Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?

Thanks,

Tim
[Samsung Gear Live] Brendo:
Did you try the live restore tool? (read the whole thread)
[Samsung Gear Live] tims1710:
I attempted to use it, however, it was unable to detect my device.

Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
[Samsung Gear Live] Brendo:
Try a different usb cable? (ie official, not a cheap one)

My watch always took a few goes to get detected by adb
[Samsung Gear Live] aligatro2010:
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.

Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.

Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
[G Pad 10.1 Q&A, Help & Troubleshooting] kutinh135:
Hi every body!

I'm looking for stock firmware for G Pad 7 V410 LTE file .kdz. I just found file kdz of V400.

Help me! Thaks!
[G Pad 10.1 Q&A, Help & Troubleshooting] rquinn19:
There isn't one that I'm aware of. Last night I was looking. If you're on a custom rom/recovery just install the stock rooted rom and install flashify and install the stock recovery which is floating around here somewhere then unroot. you'll be able to receive the update after.
[G Pad 10.1 Q&A, Help & Troubleshooting] kutinh135:
help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[G Pad 10.1 Q&A, Help & Troubleshooting] nicospanas:
I wish there was one, too. My tablet is bricked into fastboot boot loop and the LgMobile support tool does not work. Only hope is LG Flash tool. But I need the kdz.

Is there a way to convert an image (zip) into kdz?

EDIT: I found (with a lot of help) a way to unbrick it with adb.
[G Pad 10.1 Q&A, Help & Troubleshooting] jgray3493:
Please message me all the details that are needed in order to unbrick my LTE V410!!!

I have two tablets one is mine and one belongs to my son. Both are bricked!

Please H*E*L*P
[G Pad 10.1 Q&A, Help & Troubleshooting] dudedude363:
Please help me with unbricking, could you outline the process for using ADB, or maybe send me the links that helped you? if you could it would be sooo much appreciated. thank you
[G Pad 10.1 Q&A, Help & Troubleshooting] nicospanas:
This is the link with all the help and the steps I took to unbrick my tablet. Although the thread was for another model, the help I'm given is for the LG G-Pad 7.0 v410.

http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/

I basically had to flash TWRP recovery and then the stock ROM (which was rooted). Check #37 of the above link.

If you want to upgrade to lollipop you will have to flash custom recovery and unroot the tablet.

Things you may need:

TWRP recovey found here. Scroll half way down, make sure you use the right image for your model.

Stock ROM found here. Note that stock rom is rooted.

Minimal ADB and Fastboot found here. Or you can use adb.

If you need any more help, please let me know.
[G Pad 10.1 Q&A, Help & Troubleshooting] jgray3493:
HOLY SH*T!!!!

:o:D:laugh:

WOW! I followed these simple instructions and fixed the first tablet in under 5 min. My son's tablet wasn't primed and ready like mine was. I had already tried every little trick n trade I could find on the net...which consisted of "NOTHING"!!! really... Kept coming up with the same ole bricks though. Until this VITAL information surfaced!!! All I had to do on my first tablet was open up TWRP Terminal and enter the TWO codes.....rebooted.... Now enjoying!!! You got definite props from me bro! :good::good:
[G Pad 10.1 Q&A, Help & Troubleshooting] just1jonathan:
v410 kdz can be found here

achonappdotcom/downloaddotphp#
[G Pad 10.1 Q&A, Help & Troubleshooting] Mervingio:
is the test one?
[G Pad 10.1 Q&A, Help & Troubleshooting] talvigi:
I have the following links if someone in need of these

Download link for LG Gpad v410 4.4.2	http://www.mediafire.com/download/2433xqabj1k8b8d/V41007h_0.kdz

LG Flash tool http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG+Flash+Tool+2014.zip

Guide to recover the stock ROM	http://androidforums.com/threads/guide-restoring-stock-firmware.877472/

LG Mobile Drivers	https://www.androidfilehost.com/?fid=24052804347802528
[G Pad 10.1 Q&A, Help & Troubleshooting] Greydus:
Or you could follow this tutorial and thank the respective devs

xdaforums.com/g-pad-10/general/tutorial-lg-gpad-v410-5-1-to-4-4-t3232150
[G Pad 10.1 Q&A, Help & Troubleshooting] goldenfish:
https://docs.google.com/uc?id=0B7wEkGpeHpR1SVQwZTFUdkRmbjQ&export=download Google drive link for stock FW V410 4.2.2
[G Pad 10.1 Q&A, Help & Troubleshooting] stevedavid678:
Do i have to do anything else with this google drive image other than use the flash tool on a 16 GB v410?
[G Pad 10.1 Q&A, Help & Troubleshooting] baileytron:
Do you still have this stock firmware?
[XDA Assist] Special~k:
Hello geniuses, ( and I mean that literally, you guys are amazing) I have Direct TV and just got my hands on there Cinema connection kit witch allows me to connect to an internet source wireless-ly. Anywho, the error I am getting is asking for my default gateway, and my DNS, and that is way over my head. Can anyone assist? I am running a rooted Turbo. Thanks in advance!
[XDA Assist] Mike B.:
Hello and thank you for using XDA Assist.

It's unclear what Android-related specific problem you have but if by "Turbo" you mean a Verizon Motorola Droid Turbo, there is a forum specifically for questions about that device at http://xdaforums.com/droid-turbo/help where you may want to ask Turbo-related questions.

That said, if the Direct TV device simply needs information about your internet connection, you would need to know the address of your WIFI router (it'll be something like "192.168.0.1") and your default DNS server (maybe "8.8.8.8" for Google DNS?), something whoever installed your internet connection should be able to provide.

If all else fails, try posting with all relevant details in the general forum at http://xdaforums.com/general/general where someone might be familiar with your specific situation.

Good luck!
[XDA Assist] Special~k:
I appreciate your reply... and yes I was referring to the droid trubo. The internet service I am referring to, however, is my Turbos hotspot. I figured anyone running 4.4 or 5.1, no matter the device could possibly help. I know its possible, and I came very close last night to getting my Direct TV to connect to my phones hotspot. Everything else in my house is connected to my phone, not sure why this won't. I am certain its an address issue, and the default gateway and DNS is the culprit.
[XDA Assist] Mike B.:
Hello again.

If you are connecting though your phone's hotspot feature, then you have to use

its

address. That information depends on your phone, ROM and which and how many other devices are on the local network you establish, among other factors, but it's probably in the "198.162.?.?" range mentioned earlier and you can probably set "8.8.8.8" (Google) as your DNS provider. One simple way to determine your default gateway's address is to use whatever other phone, tablet, or computer you connect to that hotspot and execute a "traceroute" command. The first entry will be the gateway. I'm afraid I can't tell you how to do that specifically for your device/OS but most all operating systems have a similar command.

We cannot provide technical support nor can other members reply to your posts here on XDA Assist but, as suggested earlier, asking in the Turbos' Q&A thread at http://xdaforums.com/droid-turbo/help would be the best way to get help

This thread is now closed.

Once again, good luck!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] swordmastr54:
OK so I got at&t on my t mobile note 4 the only issue is WiFi calling it says invalid sim er05, anybody know how/if you can get it to work?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Misterjunky:
Since you are on the AT&T Network with a Tmobile phone you

will not have wifi calling.

If AT&T offers wifi calling, it will only work with an AT&T phone.

.

Good luck!

Have a great day!
[Shield Tablet Q&A, Help & Troubleshooting] bluegizmo83:
Has anyone tried using the shield TV remote with a shield tablet recently?

A few months ago nvidia said they were working on a fix to make the remotes work with the tablets and that it would be incorporated into future updates ( of which there have been a few of since then), so I'm wondering if the remotes work now before I buy one.
[AT&T Samsung Galaxy S 5] rbxrootx:
I was using safestrap to try and install a custom rom, I wiped my stock rom but my phone ended up dying (I didn't see that the charger wasn't plugged in) now I can't do anything at all. IT just gets stuck on the samsung galaxy s5 logo. I cannot flash any AP I just get an auth failed error. I tried using the G900AUCU3BOC4_OneClick but I get an error on that as well. Please help me. I figured that I don't have an OS to boot into now. And I cant downgrade from 5.0 am I screwed?
[AT&T Samsung Galaxy S 5] Sean89us:
So you can't put your phone into download mode and ODIN your old firmware back on to the phone?

Please post everything ODIN shows when you attempt so we can try and help you further. Might want to try flashing with the BL and PIT file as well.

P.S. I don't know what G900AUCU3BOC4_OneClick is, but google took me to

http://www.theandroidsoul.com/att-galaxy-s5-lollipop-update-odin-firmware-80652/

And that doesn't look legit. Make sure you get all of your firmwares from here or sammobile.com. The "Odin" on that page doesn't even look like odin.
[AT&T Samsung Galaxy S 5] squirt r6:
at&t s5 active sm-g870a

I was trying to root my phone following instructions on this site.

I installed the NE4 that was about 10+mb.

then I got stuck on the screen with red font that says "android system recovery <3E>"

I can still flash in download mode.

I attempted to install the full NE4 available from this site which is about 2.3 gig and it says FAIL! (Auth)

So then i attempted to load NG3 available from this site and it was sucessful but I'm still stuck on the "android system recovery boot.

Would anyone happen to know where I might get the "G870AUCU280F3 ROM"?

Also does anyone know what NAND erase all does when the box is checked in Odin 3.09?

Im thinking about checking that box and trying again.

for now I'm thrilled that I can still get to download mode and I don't want to mess that up.
[AT&T Samsung Galaxy S 5] FtaWolf:
In general section.