Hi. I have been playing with a Moto G for three days now trying to get it fixed after it started booting to a black screen. Here's what I have tried so far. Hopefully somebody will be able to tell me which step I missed.
When I got into recovery on the Moto G I tried wiping the system back to factory. That didnt' work as it immediately went to do a reboot. The same thing happened when I tied wiping cash or settings. I could not boot from a new recovery because there was non on the SD card that I knew of and didn't know you could use ADB to push one there. This was a phone somebody had given me to try to fix so I didn't have any history on it.
To begin with I unlocked the boot loader because I thought if i could get an unlocked boot loader I could simply flash a new ROM. I went with TWERP. Flashing that went ok except it said something about partition size error. No biggie from what I read online. Then I selected boot from recovery. Now instead of just rebooting as it had done before I got the Android on it's back with No Command below it. I learned to hold up for 15seconds then tap Power. This got me to a recovery. Not the touchscreen recovery I had expected from TWERP but a recovery. So I went in and chose update with ADB after the other options failed to give me positive results.
After this, I had a big problem getting the Moto G listed in the ADB Devices. It jsut wasnt' there. Even after I rebooted and uninstalled drivers then reinstalled. Finally I was able to find another set of drivers and installed those. Those worked after I held Vol. Down and PWR for 2 minutes according to some instructions to reset it.
No when I try to sideload a ROM I get the ROM being pushed to the device then I get this I have tried several different ROMS
Finding update package...
Opening update package...
Verifying update package...
Installation aborted...
Could it be because I was unable to enter the device settings and switch on developer options?
What can I try next?
Did you try to get a USB otg, load a custom or stock flashable zip and install from USB otg?
BBobby said:
Did you try to get a USB otg, load a custom or stock flashable zip and install from USB otg?
Click to expand...
Click to collapse
I don't have an OTG cable. I can get or make one if needbe, but in the mean time, is there a command I can use to push the .zip file to the internal storage of the Moto G? I thought I had seen one yesterday in my searching, can't find it now.
Jonathan
I'm facing the same problem except that I haven't unlocked the bootloader. I've upgraded to 5.0.2. Is there a way I could reflash the update?
Sent from my XT1068 using XDA Free mobile app
jonawald said:
I don't have an OTG cable. I can get or make one if needbe, but in the mean time, is there a command I can use to push the .zip file to the internal storage of the Moto G? I thought I had seen one yesterday in my searching, can't find it now.
Jonathan
Click to expand...
Click to collapse
adb devices ( to see if moto g is connected)
adb push name_of_file.zip /sdcard
Good luck
Related
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
frankkienl said:
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
Click to expand...
Click to collapse
It's not bricked. It's really hard (but not impossible) to brick a Xoom. They are hardy beasts.
I do wish you hadn't tried the revert/relock thing. You just made it worse as you tried to flash a 3G image on a WiFi only device.
But don't worry, it is possible to come back from this.
Just so you know, your first mistake was using old guides (though filled with good info, but files are not necessarity right) and mixing the sources. There are much newer guides in the Development section (page 1) for non-US Xoom, and I think people have better result when they stick with one source (in this case xda Xoom forum).
Second mistake is that you used the wrong recovery image...you used the v4.0.0.4 from RomManager, which is not compatible with the external micro sd card. You need the v3.2.0.0 R4c (Tiamat version). That's still the best most current version for the Xoom.
http://forum.xda-developers.com/showthread.php?t=1074979
If you had not gotten impatient and tried to revert/relock, you could have just flashed the proper recovery image and you would be good to go.
Good luck!
You seem to know your way around adb and fastboot so I'm sure you will be able to recover. Find the proper stock images for your Euro WiFi Xoom and flash them, download and flash the correct recovery image and you can take it from there.
It works again !
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
frankkienl said:
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
Click to expand...
Click to collapse
Excellent! So glad to hear it. You have skills so I'm sure you will be coool from now on.
just an update
This is an old thread so I'm putting this here for google searchers, like me.
I had the same problem but here's what extra I found/noticed
(1) To restart the xoom when it's in this state hit power button and volume up
(2) You can see that the tablet is still responsive if you hit volume down after 2 seconds as you'll get some options
(3) For me it wouldn't work if I used the motorola cable (yes, the real one) in the front pc usb ports. I had to use the usb 3 ports at the back of my pc. Yes, it's that picky! The difference was when I used fastboot to install the system image. It took 3 minutes then gave up, stuck the cable in the back of the pc instead and it took about 10 seconds and worked first go!
(4) The pc didn't recognise the xoom and adb didn't work, i.e. it said no device attached. However fastboot did recognise it
After point (4) I realised it wasn't bricked and could move forward
thanks to the other posters here for making me realise there was hope
Okay guys, now I baught a moto g x1032 from ebay, gave it a try and It seemed laggy and buggy, went to settings and found that it was running a custom rom, so I wanted to go back to stock and I found a tutorial and I pretty much followed the tutorial, the tutorial said to download mfastboot, the firmware file, and adb fastboot as well as the drivers.
I did all of that, I installed the stock firmware and went to turn the phone on and it just shows the motorola logo then restarts.
I'm not sure what to do to get it working, I even downloaded another stock rom but it was in .zip format so I needed to transfer it to the phone and install it via cwm, I tried to install it via sideload but I kept getting the error on adb: error device not found.
I can still get into the fastboot menu by holding down the volume down + power.
I have also read that you apparantly need to have debug mode enabled, but how am I supposed to enable that when I can't get past the boot screen?
All i can think of is that maybe i was trying to downgrade the device when i shouldn't be?
If anyone can help me with this or point me in the right direction to fixing this phone back to stock that would be great.
Thank you.
What version of android did the phone come with? And what version did you try to flash?
I believe it came with 4.4 and I tried flashing 4.4 normal edition.
The phone now boots up but there is no sound or vibration or anything, tried making a call and the phone freezes, any ideas?
Which retail 4.4.4 are you needing? I can upload the UK version I use.
ramo55 said:
Okay guys, now I baught a moto g x1032 from ebay, gave it a try and It seemed laggy and buggy, went to settings and found that it was running a custom rom, so I wanted to go back to stock and I found a tutorial and I pretty much followed the tutorial, the tutorial said to download mfastboot, the firmware file, and adb fastboot as well as the drivers.
I did all of that, I installed the stock firmware and went to turn the phone on and it just shows the motorola logo then restarts.
I'm not sure what to do to get it working, I even downloaded another stock rom but it was in .zip format so I needed to transfer it to the phone and install it via cwm, I tried to install it via sideload but I kept getting the error on adb: error device not found.
I can still get into the fastboot menu by holding down the volume down + power.
I have also read that you apparantly need to have debug mode enabled, but how am I supposed to enable that when I can't get past the boot screen?
All i can think of is that maybe i was trying to downgrade the device when i shouldn't be?
If anyone can help me with this or point me in the right direction to fixing this phone back to stock that would be great.
Thank you.
Click to expand...
Click to collapse
You can flash one from here via recovery: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 then reboot.
I (assumed) bricked my Moto G LTE today and just ordered another one. How it happened was that I factory reset my phone, but the setup stopped working after I finished it so I had no launcher. I naturally panicked and booted into recovery using ClockworkMod, but it didn't work. Eventually it got to the point where it was stuck at the Motorola "M" logo, so I continued to factory reset with ClockworkMod and installed a zip hoping a stock would fix it. It did not, since I misunderstood and now my phone is currently stuck at the warning bootloader screen (replaced by "Motorola powered by Android").
So I gave up and ordered the "Motorola Moto G - Universal 4G LTE - GSM Unlocked - 8GB (Black)" from Amazon.
To prevent something like that happening again what are some things I need to do to ensure I'll always have a safe recovery? I'm also overwhelmed by how many ways there are to root a Moto G LTE and could use some direction. I'm also confused on how I can find the appropriate stock ROM of 4.4.4 for my new XT1045.
Blkdrgn415 said:
I (assumed) bricked my Moto G LTE today and just ordered another one. How it happened was that I factory reset my phone, but the setup stopped working after I finished it so I had no launcher. I naturally panicked and booted into recovery using ClockworkMod, but it didn't work. Eventually it got to the point where it was stuck at the Motorola "M" logo, so I continued to factory reset with ClockworkMod and installed a zip hoping a stock would fix it. It did not, since I misunderstood and now my phone is currently stuck at the warning bootloader screen (replaced by "Motorola powered by Android").
So I gave up and ordered the "Motorola Moto G - Universal 4G LTE - GSM Unlocked - 8GB (Black)" from Amazon.
To prevent something like that happening again what are some things I need to do to ensure I'll always have a safe recovery? I'm also overwhelmed by how many ways there are to root a Moto G LTE and could use some direction. I'm also confused on how I can find the appropriate stock ROM of 4.4.4 for my new XT1045.
Click to expand...
Click to collapse
I am in no way an expert but here is my few cents :
0) make sure your bootloader is unlocked, see motorola website
1) Install TeamWin recovery latest version. For that just use adb to connect to your phone in debug mode and flash it, read up on that. Its easy process once you know it.
2) Hold vol down and power for a bit then release power, that goes into fastboot/bootloader, in which you press down then up to get into recovery.
3) erase everything from recovery, this should destroy your OS, to start at a clean slate.
4) make sure all your drivers are install on pc, for all modes that the phone can be in, so in the recovery now you should even see ur phone using adb devices
5) do a side load using adb of the rom your want to load, should take seconds
6) restart phone, rom should work, check it all out
7, if there is no root, then go back into recovery and install Super SU zip file, you can find.
Look at this guide: http://www.swedroid.se/forum/thread...nlock-recovery-root-guide-for-windows.106595/ it has all the tools you should need.
Oh, and don't panic, its very hard to really brick your phone.
Thanks for the help. Is it OK to use the guide even though it's intended for 4.4.2? What's the difference between CWM and TWRP, which one is better? In the scenario where I need to load the stock ROM because of corrupted recovery like before, how would I do that?
Blkdrgn415 said:
Thanks for the help. Is it OK to use the guide even though it's intended for 4.4.2? What's the difference between CWM and TWRP, which one is better? In the scenario where I need to load the stock ROM because of corrupted recovery like before, how would I do that?
Click to expand...
Click to collapse
For the Moto G hands down twrp
You can even flash IMG files after 2.8( if you even need to heh)
I just got my new phone today from Amazon. Apparently it's a XT1039 rather than my old XT1045. Is there a difference? I'm in the U.S. if that matters.
Edit: While following the guide @MuhammadA linked, I can't flash any recovery for some reason. When I try to flash them, my phone says "Mismatched partition size (recovery)" and when I try to launch "Recovery" it says "Boot up failed"
Edit: Found the problem. I don't know what it was, but I used a different version of CWM called "Unofficial CWM - 6.0.5.0 - peregrine" by Shabbypenguin and the OUDHS.
Edit again: The first thing I decided to do when I installed CWM was to backup my system, the first backup to my phone which went well and finished in a minute or so. When I started another one to my external SD card, it's stuck on "Generating MD5 checksums..." for about 20 minutes. Is it safe to force restart it via the power button?
Hi, I accidentally accepted an OTA update last night without thinking. My phone rebooted and went to philz touch recovery. after much playing around i have been unable to get the phone to see my CWM backup on the external SD card. So my next plan was to flash back to the original rom. The trouble is that despite installing the correct (i think) usb adb driver the LG mobile update tool cannot detect the phone. I've tried getting the phone into download mode which for mine appears to need volume +, Volume - and usb plugging in but i just get a screen of Korean writing with 3 options. each option i choose just reboots the phone back to CWM. no matter what i have tried i cannot seem to get anything to flash on it?
Its an F350k, i'm sure it is recoverable as i can get the Lg boot logo and CWM but i simply cant get anything to install???
forgot to say i tried sideloading as well but I'm not really sure what i should sideload. i tried the stock kdz but that didnt work. my backup isnt zipped, should i zip it and try that?
any help would be really appreciated
I take it you have tried the volume up and plugging in the Usb? You can also try booting to cwm and then via ADB running adb reboot bootloader
Verstuurd vanaf mijn LG-D838 met Tapatalk
Yes, the volume up and USB doesnt work. if i press volume up, volume down and then plug the USB in I get a screen of korean writing with 3 options all of which end up taking me back to the CWM. I tried sideloading and was able to transfer files across to the phone but it wouldnt open them to flash. I've decided I am going to send it to a JTAG unbricker as its probably going to be quicker. Lesson learnt. Thanks for your help by the way
try this something happen to me before and fix my f350s , hope can help you.
http://forum.xda-developers.com/showthread.php?t=2451696
Same thing happened to me yesterday. any tips on getting this phone to work again? mydoom's solution is for twrp. unfortunately im using cwm from sphinx's app.
edit: tried adb command via adb sideload in cwm. thanks for the help mydoom!
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!