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...
Related
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.
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!
Hi guys,
Before i start, just be informed that i have tried google all possible solutions and tried them but to no avail. I know its a long shot but perhaps someone may be able to help however small the chances are.
My phone is a Xiaomi Redmi Note 3 Snapdragon variant and is rooted.
What happened was, i tried installing TWRP (kenzo version) on my phone and so following the "instructions" in the downloaded file.
I used Flashify to flash the boot.img and then redmi_note_3_Twrp.img then the phone prompted me to reboot.
Now my phone is stuck in bootloop. The only thing i can do is to boot into Fastboot. So i tried accessing fastboot via ADB hoping to be able to some how flash the original boot.img back.
The problem i have now is that i am unable to access the phone at all even though i can go into fastboot. It wont be detected by my PC. I tried Minimal ADB and Fastboot and PdaNet.
Is there any other way for me to detect my phone and run some form of command to get it started again? Any help at all is appreciated. The phone is fairly new and i'm regretting trying to get the latest ROM for it.
I'm hoping i'll have some luck in a helpful community such as this.
Thanks guys.
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Marticco said:
Omg!! someone with the same problem as me. The same happened to me. Flashed a CWM file now am stuck in a Bootloop and ADB wont find my device either
Click to expand...
Click to collapse
Fret not my friend. For i have found the solution and managed to unbrick my phone. Thank the good guys at MIUI for this.
Head over to the MIUI forum and search unbrick under the Redmi Note 3 forums. I can't post the link here unfortunately
You can also thank me after you unbrick your phone.
This only applies if you are uaing the Redmi Note 3 Pro
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Marticco said:
yea unfortunately i dont use that phone. I have a Lava Iris x1 Grand (Lollipop). I am still trying to get ADB find my device
Click to expand...
Click to collapse
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
willetan said:
Well if that's the case i suggest googling how to get into EDM mode for ur phone and using your phone brand's flash tool to flash a new ROM onto your phone. This means you will not be able to save your phone's memory. Is your phone's bootloader unlocked?
Click to expand...
Click to collapse
yes it is unlocked,
i think? When i entered fastboot mode. One of my apps says bootloader enabled and when i typed 'fastboot devices' in the Minimal ADB and Fastboot its shows:
0123456789ABCDEF devices
whereas if I type 'adb devices' i just shows:
List of devices attached
The main problem is the driver, i cant get adb to find my device. I have tried the universal usb drivers like Kouch but no success. My device is listed in the Unspecified section in my computer
It's a stock phone, unrooted bootloader locked. The phone was updated to the latest firmware a few days ago and was working well since.
Today I left the phone on the desk for a while. When I came back, the phone had rebooted and was in the fastboot mode screen.
I tried to restart but it just loops back to same screen. Does not even go into recovery!!
What snapped it, cant understand!
Is it bricked? How do I revive the phone now?
Please help!
Thanks
Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/
sms2000 said:
Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/
Click to expand...
Click to collapse
Do I also need to flash stock recovery from fastboot?
Thanks again.
observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
No, recovery is part of the ROM, so not needed.
If it's a completely stock device, why not contact OnePlus and get a replacement?
Are you guys suggesting ADB sideload command? My USB debugging seems to be off, returns empty on "adb devices"
I am unaware of fastboot command to flash the stock rom, googled it but could not figure out the right command.
Thanks
maigre said:
If it's a completely stock device, why not contact OnePlus and get a replacement?
Click to expand...
Click to collapse
That's right.
If am not able to fix it myself with members help, I'll have to go through customer support drill.
observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
jerrywmilton said:
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
Fingers crossed mate! Hope you get it right!
observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
yeah, I was gonna say....just follow directions carefully....it works....same set up has been working for years for each different model.
Thanks to each one of you.
The issue is resolved
I used the unbrick tool i.e. MSMDownloadTool to fix the problem. Hope it does hot happen again!
Thanks
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/