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!
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.
Hey folks,
I'm rather embarrassed that I have to ask for help here, but here we go:
I wanted to update my Moto G (1st gen) to Lollipop 5.1 (via this thread: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) and after toying around with it for a few hours got frustrated and did some stupid things, which I'm also having a hard time to remember.
From what I recall, I managed to flash the "GPE 5.1 ROM (Optimized) v1.1" ROM via TWRP, but when booting the phone got stuck on the BOOTLOADER screen for about 1 1/2 hours, after which I decided to turn off the phone.
After that I frustratedly started fiddling around in TWRP and wiped system, cache and some more things (derp :silly: ) and well... ever since then I'm trying to get a new ROM on my SD card, but I can't push via adp because my device is not found.
Here's the facts
- When I try to regularly boot up my phone, the Warning Bootloader unlocked sign appears
- I can access the fastboot screen on my phone (AP Fastboot Flash Mode (S) 41.11), the one where it says normal powerup, recovery, factory, barcodes, bp tools and qcom. When I connect via USB it says USB connected.
- I can get access the recovery rom TWRP (v2.8.5.0)
- When I try to push a ROM to my sdcard command line tells me "error: device not found".
aaand that's it. I really hope I didn't brick my phone.
I'm on Windows 7 x64 and I would really appreciate the communities help. After that I'll show myself out and leave my phone working for a while hopefully.
edit: one more thing. my phone gets recognized as "Fastboot falcon S" in windows when I plug it in while in fastboot flash mode and as XT1032 when TWRP is booted. obviously it doesn't get recognized as a volume in Windows Explorer, or I would have already transfered another rom on the SD card by now.
edit 2: I also tried connecting the phone via another windows 7 x64 laptop now. installed motorola device manager & minimal adb and fastboot, but same thing there. :|
edit 3:ISSUE RESOLVED for now. I used this: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 and it worked like a charm. Thanks everyone.
@covecove until there is fastboot, there is hope.
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...
Hello guys..
I really have a problem right now! I appreciate everyone who tries to help me. I´ll try to expain what exactly is my problem with my Mate8.
Also I´d like to apologize for mistakes of gramatics, because im acutally from Germany..
So, my phone was working right, and actually everything was okay. With time it got so slowly, because storage was full with datas and so on. I tried to clean up some things to get it again a bit faster and so on, but that did not make it (at all). Also windows wont recognize the phone anymore. When plug in the USB it didnt even asked for data, charging or photos.. also I had problems with charging, it took toooo long for a few %.
I was on "KANGVIP" Rom (as much I know i changed stock to this custom rom) https://forum.xda-developers.com/mate-8/development/rom-kangvip-slim-t3318572
Time passed untill 3 days I decided to flash a new rom normally, like put rom on sd card, wipe dalvic and cache, and so on. I wanted this rom; Lineage OS https://forum.xda-developers.com/mate-8/development/6-0-1-cyanogenmod-13-port-t3512985
But everything came up with different errors for different actions I did like this:
"cant mound sd card"
"cant mount inernal storage"
"cant mount data"
"cant format data"
"cant mount system"
"cant mount cache"
etc. etc...
I tried to change file system to EXT3. EXT4, EXT2, FAT, and so on, for Data and System. Nothing worked correctly (but I had still on some Filestystems instead of 0MB like 2700MB). Still not working correct... On TWRP.
Then I tried to update TWRP from 3.0.1 to 3.1 (new one released). Because I saw, more precisely, I heard that an update can fix this mount issues I had.
Said and done, I updated it and instead of 3.1 I had 3.0.2 (idk why but I didnt care). But still theese problems happend.
So then I saw in a Video on youtube (which I cant find anymore) that another recovery like CWM can fix this issues. So I downloaded CWM recovery.img and installed it with TWRP an rebooted to recovery again. And now I´m in a situation, in wich I dont know what to do.
Now the phone tries to start, but no OS installed.
Try to get into Recovery, but no recovery aviable exept eRecovery which is failing with data when trying to restore.
Problem is also that Fastboot and ADB is not working. Installed HiSuite, ADB drivers, Samsung drivers (though could help).
Tried Knife Italian, but no connection to pc..
Tried different cable, no luck.
Tried windows 7, 8.1, 10 Home and now im on Win 10 Pro 64x.
All I can do is to boot into Fastmode, but cant do anything. And when I try to boot the phone normally it stucks on "Your device is booting now..." because no OS...
PLEASE HELP ME GUYS! I REALLY NEED THAT PHONE :crying::crying::crying::crying::crying:
THANK YOU !!! :good:
Hallo,
If your phone is still recognized in fastboot mode, you can try following up my tutorial here » https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I was experiencing the same problem. No OS, no recovery, no fastboot flash possibility, only fastboot booting. Keep in mind that you will need 15€ for this method to work but it is the only way to resurrect your device.
PM me if you need further assistance.
djmitza222 said:
Hallo,
If your phone is still recognized in fastboot mode, you can try following up my tutorial here » https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I was experiencing the same problem. No OS, no recovery, no fastboot flash possibility, only fastboot booting. Keep in mind that you will need 15€ for this method to work but it is the only way to resurrect your device.
PM me if you need further assistance.
Click to expand...
Click to collapse
Thank you for the reply my friend.
The problem is, that it only boots in to fastbootmode, but any pc wont recognize it. I tried even with Mac...:crying:
Greetings
DC-Phoenix should recognize the fastboot brick state even if the device doesn't show up in Minimal ADB & Fastboot. Try my method and let me know if it works.
Hi guy's.
DC Phoenix save my mate 8 with factory firmware.
I was the same problem like you and search one week a solution and after I decided to pay and try Phoenix and now I write from my mate 8
Before buy 15€ of credit you can download and try to connect your phone on DC Phoenix
does the DC phoenix method take your phone to absolute stock? ie, stock firmware +recovery + Locked + no root?
Yes. You will have the factory firmware (stock) but with unlocked bootloader.
New Problem:
i want to sell the phone and bring it back to Stock (to OxygenOS) but the problem is, that the phone won't unlock the bootloader, everytime i use "fastboote oem unlock" it boots into TWRP recovery?!?! And device status says "...locked"
Solved problem:
[problem 2]
I got my OPO back to life but i only can install CM11 on the phone, when i try to install cm12/13 it stucks at the cyanogen Logo?! Any suggestions? Is there anything i missed? I am upgrading via Fasboot.
[problem 1]
Hello,
i have a problem with a OPO, it wont start and dont give any signs when i try to charge it. When i connect it to the computer it will be recognized as "unknown usb device" (Failed to get Deviceinformation). Do someone have any solutions?
Spacket said:
Hello,
i have a problem with a OPO, it wont start and dont give any signs when i try to charge it. When i connect it to the computer it will be recognized as "unknown usb device" (Failed to get Deviceinformation). Do someone have any solutions?
Click to expand...
Click to collapse
Can you boot into fastboot mode? It doesn't take much battery to boot into fastboot mode and can might even boot if you have 0% battery.
Tried, the problem is, that the display won't get on, even when i try to charge it. It only gives some living signs when i connect it to the computer (after 18-20secs) Windows tell me, the device can't be recocnized properly
EDIT: Fixed via QFIL
New Problem:
I got my OPO back to life but i only can install CM11 on the phone, when i try to install cm12/13 it stucks at the cyanogen Logo?! Any suggestions? Is there anything i missed? I am upgrading via Fasboot.
Spacket said:
New Problem:
I got my OPO back to life but i only can install CM11 on the phone, when i try to install cm12/13 it stucks at the cyanogen Logo?! Any suggestions? Is there anything i missed? I am upgrading via Fasboot.
Click to expand...
Click to collapse
Follow this and you should be good.
If that does not work follow this and use the tools provided there instead of QFIL.
Stjinchan said:
Follow this and you should be good.
If that does not work follow this and use the tools provided there instead of QFIL.
Click to expand...
Click to collapse
Thanks for the links, i managed to Install CM13 with one code line from this thread: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
BUT, i want to sell the phone and bring it back to Stock (to OxygenOS) but the problem is, that the phone won't unlock the bootloader, everytime i use "fastboot oem unlock" it boots into TWRP recovery?!?! And device status says "...locked"
It worked some time, as you can see i installed TWRP and CM, so i dont know why it's not working now
GOOOOOD fails after fails hahaha
No one have an idea?
Spacket said:
No one have an idea?
Click to expand...
Click to collapse
Why not just flash oxygen os 3.1.4 port (its pretty much bugless) and sell? You don't need to have locked boot loader for that.