Hey guys. Thank you for you time looking over this.
My brother has a Moto G (US GSM version)that he's asked me to repair for him for $50 (that I really need) and I've gone through everything my limited brain can think of.
So, here's the issue(s): When turned on, the phone immediately boots to fastboot and at the bottom has two lines saying "Invalid Boot Image" and
"Fastboot reason: Fall-through from normal boot mode"
I can get the phone into CWM recovery, and that's about it. When attached via USB, the phone doesn't show connected at all. A normal bootup just kicks me to fastboot immediately. Inside CWM, I've tried wiping and all that jazz, but it doesn't seem to do anything for me. I know there are guides and such for restoring the phone back to stock everything..but I can't get the PC to see the phone at all, so I'm not sure if I'm still able to do that or not. I've not been able to find a way.
Hopefully that's enough information. I'm not too sure what else is needed. But I could really use the help here if you guys have any ideas, because I'm totally stumped. Thanks again.
You can either use a USB OTG cable to connect it to a flash drive or micro SD card and flash a CM zip. I'm not sure if your boot loader is corrupted or not, so you might have to reflash that too.
Or you can manually reflash the stock firmware from the bootloader (again assuming your bootloader works. You might be able to sideload through CWM too), but if you're not familiar with adb it might be a pain in the ass.
If you don't have a USB otg cable and want the easiest way out, go to the original development section for the moto g and go to the "Moto tool" thread. Download the GPE firmware and use the tool to flash it (I believe this also flashes the gpe bootloader so if that's your issue that will fix it too), its very simple to use.
Sent from my XT1034 using Tapatalk
pisherthefisher said:
You can either use a USB OTG cable to connect it to a flash drive or micro SD card and flash a CM zip. I'm not sure if your boot loader is corrupted or not, so you might have to reflash that too.
Or you can manually reflash the stock firmware from the bootloader (again assuming your bootloader works. You might be able to sideload through CWM too), but if you're not familiar with adb it might be a pain in the ass.
If you don't have a USB otg cable and want the easiest way out, go to the original development section for the moto g and go to the "Moto tool" thread. Download the GPE firmware and use the tool to flash it (I believe this also flashes the gpe bootloader so if that's your issue that will fix it too), its very simple to use.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Thanks very much for your help. I'm just wondering if all the steps with the cables and all that will still work when the phone shows no connection at all? When it's hooked up to the PC, it doesn't show connected whatsoever.
Sorry, I'm not too familiar with this stuff.
BrinkBT said:
Thanks very much for your help. I'm just wondering if all the steps with the cables and all that will still work when the phone shows no connection at all? When it's hooked up to the PC, it doesn't show connected whatsoever.
Sorry, I'm not too familiar with this stuff.
Click to expand...
Click to collapse
What computer software are you using of its windows download Motorola drivers
Sent from my XT1032 using Tapatalk
Moto G boot up failed
I have a similar problem with my Moto G 2013 LTE international version. My phone boots into fastboot, but then I cannot boot into recovery. It just says boot up failed. My bootloader is unlocked and I am rooted. I have tried to install TWRP but no luck. I have tried it using TWRP manager automatically and by flashing a zip file. I have tried sideloading, but that didn't work either. Please forward any suggestions.
Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
I tried to install cyanogenmod 12 onto my Moto G (2013 XT1031), and it was stuck in boot for 10 hours, so I put it into recovery, plugged it back into my computer, followed a forum on how to fix it, and now the drivers are gone. My computer can't communicate to my phone through USB. So now when I type "adb devices" it isn't listed, so I cannot push a stock img file to my phone to fix it. I've been looking forever for a fix... Could somebody here help me if you have any idea what to do. Thx.
Add me on Facebook. I'll help you. I had the same problem. www.Facebook.Com/mykehdoom
I will post here what I did to fix it, (if I do fix it) just in case anyone else comes here to fix their problem.
You should always keep a backup or stock ROM zip on SD card or USB otg. And you shouldn't have this problem as long as you can boot to recovery. I've found the quickest way to get any Lollipop ROM to boot since the first official CM12 nightly is to install Donkey Kang kernel. Most of the time they'll stay on boot animation forever until I do. I have an XT1031 too. A Leaf micro SD card reader or a Leaf bridge are well worth the cash. They've saved me from having to use my PC to get out of a jam every time, and I've flashed almost every build of every ROM that will flash on this phone.
Bellablue2 said:
I tried to install cyanogenmod 12 onto my Moto G (2013 XT1031), and it was stuck in boot for 10 hours, so I put it into recovery, plugged it back into my computer, followed a forum on how to fix it, and now the drivers are gone. My computer can't communicate to my phone through USB. So now when I type "adb devices" it isn't listed, so I cannot push a stock img file to my phone to fix it. I've been looking forever for a fix... Could somebody here help me if you have any idea what to do. Thx.
Click to expand...
Click to collapse
Have you tried restoring stock via fastboot? http://forum.xda-developers.com/showthread.php?t=2542219
If you wish to keep the contents of the internal storage, skip the erase userdata part. At least until you can backup what you want off it.
dominati said:
Have you tried restoring stock via fastboot? http://forum.xda-developers.com/showthread.php?t=2542219
If you wish to keep the contents of the internal storage, skip the erase userdata part. At least until you can backup what you want off it.
Click to expand...
Click to collapse
No, the problem was that my computer could not do anything to the phone, they would not interact at all. ADB couldn't sense the phone. I did fix it, however. Here is what I did:
1.Open Device Manager
2.Plug in phone
3.See if a new device pops up when device is plugged in.
4.Right click the device: Properties
5.Update Driver
6.Browse Computer
7.Pick from list of Drivers
8.Uncheck "Show compatible Hardware"
9.Manufacturer: Motorola
10.Motorola USB Composite Device
11.Next
12.Follow through and wait for it to set up your driver, then device.
13.After that, adb could find my phone.
HI,
First time posting, but read a lot of great info on here in the past. just made a bit of a stupid mistake tho... I'd rooted my XT1039, and then flashed the custom recovery back as well as the stock 4.4.4 eu retail gb. I was getting the 5.1 OTA update, but the install was failing. In my eagerness, I downloaded the GPe Lollipop 5.1 update from here - http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 - and tried to flash that, missing that it is for a different phone. Now I'm stuck at the bootloader menu, with the error "fall-through from normal boot mode." Any attempt to select normal powerup, recovery, etc results in a black screen with "Google" written on it and an unlocked padlock symbol.
I was going to try and flash the stock 4.4.4 image I had, but when connecting the phone to the PC via USB, fastboot isn't recognising it as attached, even though the phone detects that USB is connected...
Any help would be seriously and massively appreciated!!
Thanks in advance!
Hey man, I have a similar problem as you. Maybe I can give you a little hand, but its better if somebody who understan everything well give you the hand, becouse I'm a "starter" with this of Moto G.
Your device is charged? With my XT1040, the bootloader didnt connect with the PC via USB if the batery was low. Other thing, which version of bootloader do you have?
Thanks! Yes, the phone is charged! Not sure what version of the bootloader it is...
Start fastboot mode with "Pwr" + "VolDwn" and in the top of the screen says:
Code:
AP Fastboot Flash Mode (S)
41.xx [COLOR="Red"]<--- version of bootloader[/COLOR]
It's 41.19...
Try flashing the CWM Recovery again ClockWorkMod Recovery by Somcom3X with fastboot.
Then mount USB storage and upload an Lollipop's backup/system for your XT1039.
Finally, try to install the Lollipop's zip. If the instalation finish succesfull, wipe data and cache. Then try to start your device normaly (first option of CWM (restart))
Anyway, yesterday I made a thread explaining what happened to me with my XT1040 and how I solve it. Read it if you have time, maybe helps with your problem XT1040 - Reviving bad Lollipop flash/downgrade/bootloader 41.18
Note: I think that XT1039 and XT1040, both can work with the same Lollipop but I'm not sure, ask arround before try with a XT1040 backup.
Hi,
Thanks for that info. Unfortunately I can't do any of that, because fastboot doesn't see the phone any more. When I plug the phone in by USB, windows recognises it, and the phone says that USB is connected, but "ADB devices" in fastboot doesn't see it... So I don't know if it is completely bricked! Selecting any option in the bootloader menu gives me a screen with "Google" on it and a padlock sign...
It has enough battery? If not, Moto G dont allow you to use ADB comands for safety. If not that, really I have no idea. Hopefully someone who knows more than me pass by your thread
Yes, the battery is fully charged... ok, thanks for your help anyway!
I unlocked my Moto G XT1040 bootloader and tried to load stock Kit Kat (because my wife didn't like Lollipop) using ADB.exe, but something went wrong. Now it boots to the "bootloader unlocked" warning screen and won't continue to boot after that. I can't run ADB commands against it because it's saying that no device was found. I assume that's because I need to turn on USB debugging, but I can't boot into the OS to do that.
I heard you could restore stock firmware using Odin, but I can't seem to find the stock XT1040 tar files that are needed to do that, and I don't know if Odin will be able to communicate with the phone, since ADB isn't recognizing any connected devices (the phone does say "USB connected" and in device manager it's recognized properly as a Motorola android device). I even tried using a different computer, but still can't send any commands to the phone.
Is it bricked beyond repair? It's fine if we have to stay with Lollipop - I'd just like to get it operational again.
Cheers
Hi
Try to flash it with fastboot... Opening your bootloader screen will put you in that mode on your phone...
Let us know
satanas17 said:
Hi
Try to flash it with fastboot... Opening your bootloader screen will put you in that mode on your phone...
Let us know
Click to expand...
Click to collapse
Thank you! I'm a newbie so I assumed that if ADB said no devices were recognized, then certainly fastboot commands wouldn't work.
I actually ended up using mfastboot to restore the stock firmware and everything is working great. Thanks so much!
micheken said:
Thank you! I'm a newbie so I assumed that if ADB said no devices were recognized, then certainly fastboot commands wouldn't work.
I actually ended up using mfastboot to restore the stock firmware and everything is working great. Thanks so much!
Click to expand...
Click to collapse
You're welcome, happy endings are always a pleasure...
Mark your topic as solved and hit the thanks button if you want...
Hi there,
Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.
I've found official ROM package on their site:
ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/
Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?
Thank you.
Hi,
I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.
Good luck!
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
denede said:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
Click to expand...
Click to collapse
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.
So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.
Have the damn files and don't know what to do with them, OMG.
I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :|
I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.
edit: 100% and no good...
edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.