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.
Related
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk
ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.
LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >
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!
Code:
Boot failed. Press POWER KEY to retry.
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care for furthur assistant.
AP Flashboot Flash Mode ( Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Hi everyone,
I've wanted to root my Android phone for a while now, so I decided to do it these holidays, following instructions on getdroidtips ( How to Install Lineage OS 17.1 for Moto G8 Plus | Android 10 [GSI treble] (getdroidtips.com) ). I couldn't boot into TWRP recovery mode for some reason, (maybe it didn't install properly) so I tried to install Havoc OS using ADB. My phone then rebooted several times and then gave an error message, saying I could either try rebooting again or factory reset. I chose factory reset and went through the whole process again twice, the third time with Lineage OS. It then gave a different error message (in the code block). I can use the volume keys like in the bootloader, but couldn't get it to boot. I also can't access the phone over ADB.
This was my first time messing with Android beyond basic ADB commands, so I didn't really know what I was doing. I might have messed up the instructions or made some other mistake. All of my data is backed up, so all I'm hoping for is to either boot Lineage OS or somehow flash the stock ROM again.
Does anyone know how to solve this issue?
BTW I am not on Verizon.
I've run into a few of these situations. I also tried this version of Android as a Custom Rom and got a Boot Loop
I had to use TWRP to reinstall my TWRP backup.
Just in case you don't have TWRP or TWRP access for some strange reason you could try this:
I have a moto g8 plus xt2019-2
Motorola_Moto_G8_Plus_XT2019-2_DOHA_RETBR_9.0_PPI29.65-43_(MobileGuru4.com)
Motorola Flash File For All Model (Stock ROM) - Mobile Guru4
Download Motorola Flash File for all Motorola models. Here all Stock ROM and firmware files given for Motorola phones are official original files
www.mobileguru4.com
Search for this on google, when you find it download it. Then inside the zip file once you unzip it find the directory that is labeled - firmware
Inside that directory there's a file labeled "flashfile.bat" This setup uses ADB with ADB Fastboot on the phone. I assume you know how to get ADB Fastboot on your phone. When you execute the above file you will see it working in the command prompt on your computer. Let it run. It will not show anything on your phone until your phone reboots. This is what I use as a DISASTER BACKUP in case TWRP is unusable or in any way I'm unable to get to it.
I hope this helps you, it worked on my phone.
Thanks for the reply. Unfortunately, I can't try it because I've already sent the phone away to be repaired. The repair company said they would have to send it away when I originally emailed them. The repair company had a no fix no fee arrangement, so if they can't do it I'll try using fastboot. Hopefully that will happen and I won't have to pay $200.
sorry my english, i have the same problem and already try everything, rsa always fails and rsd lite does not recognize my device in windows 10, i tried to short the motherboard and it didn't work, i am seriously thinking about changing the motherboard or sell the parts
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.