I tried unlocking the bootloader and it said unlocked, but when it booted back up it did the whole system update thing, and then it kept force closing the phone app. Well, I held down the power button for ~15 seconds, and now when it boots back up, it gets to the brown part of the boot animation, (farm type motorola) and goes to a black screen.
Going into the bootloader and selecting factory does the same thing.
Please help?
(US GSM 16GB version XT1034)
Flashed CWM, wiped data/cache and it got past the screen with the brown, but now it just boots to the black screen after the water drop part.
Try to restore stock firmware...look here: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=failed
Pablitooos said:
Try to restore stock firmware...look here: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=failed
Click to expand...
Click to collapse
Thank you so much. It's working. At first I flashed the XT1032 because I thought AWS was the Global version, but I flashed the correct firmware just now. Again, thanks.
landonh12 said:
I tried unlocking the bootloader and it said unlocked, but when it booted back up it did the whole system update thing, and then it kept force closing the phone app. Well, I held down the power button for ~15 seconds, and now when it boots back up, it gets to the brown part of the boot animation, (farm type motorola) and goes to a black screen.
Going into the bootloader and selecting factory does the same thing.
Please help?
(US GSM 16GB version XT1034)
Flashed CWM, wiped data/cache and it got past the screen with the brown, but now it just boots to the black screen after the water drop part.
Click to expand...
Click to collapse
If you don't find a solution, you could try doing the same to about 2,000 more moto G's and build a small house..
Related
I recently installed this ROM and I thought it was working fine. I did a restart of the device and now I seem stuck at a android screen that it doesn't see to be going pass. The android word just display as a light goes across the screen and then it seems to cycle again.
I can't seem to boot into recovery either to put restore the back up I made, because when I get to the white fast boot screen the selection won't scroll down to recovery when I hit the down volume button. It just stays there and then tries to install a patch for a radio I believe.
Any thoughts on why this is stuck at the android word screen or how I can get back to my back up and restore that. Thanks
verseman said:
I recently installed this ROM and I thought it was working fine. I did a restart of the device and now I seem stuck at a android screen that it doesn't see to be going pass. The android word just display as a light goes across the screen and then it seems to cycle again.
I can't seem to boot into recovery either to put restore the back up I made, because when I get to the white fast boot screen the selection won't scroll down to recovery when I hit the down volume button. It just stays there and then tries to install a patch for a radio I believe.
Any thoughts on why this is stuck at the android word screen or how I can get back to my back up and restore that. Thanks
Click to expand...
Click to collapse
Try removing your sd card and then vol down and power. Then once you're past fastboot white page pop it back in in time for recovery, and do your thing. Try clearing caches first. If not then restore a backup.
Sent from my Inspire 4G using Tapatalk
Yup I think I seen that in another forum to a similar type problem, I removed the SD card and was able to get back into clockwork recovery. I wipes all data/settings, cache partition and then loaded the rom again.
First thing I did was do a reboot so. So far it didn't get stuck and booted back up. Will do another reboot later tonight to see if it holds. Thanks for the tip
I'd reccomenf going to the dhd forum and getting the latest version (new one coming out soon)
Sent from my Desire HD using XDA App
I have a bit of a problem. I am on a moto g sold in the UK with Vodafone. I followed all the steps posted by root junkie on his youtube video in an attempt to install cyanogen, however cyanogen was taking a long time to load(30 mins without loading). So i went back into cwm to wipe data, this process stalled, so i pressed volume down and power to to go back to fast boot mode.Now when i go to recovery instead of loading into cwm my phone stalls at the white screen which says "warning bootloader unlocked". I have tried reinstalling cwm which seems to install fine, however when i click recovery it goes back to the warning screen. I have also tried reinstalling the stock firmware, however the same problem occurs.
Do you have any suggestions?
Thanks
andy07070 said:
I have a bit of a problem. I am on a moto g sold in the UK with Vodafone. I followed all the steps posted by root junkie on his youtube video in an attempt to install cyanogen, however cyanogen was taking a long time to load(30 mins without loading). So i went back into cwm to wipe data, this process stalled, so i pressed volume down and power to to go back to fast boot mode.Now when i go to recovery instead of loading into cwm my phone stalls at the white screen which says "warning bootloader unlocked". I have tried reinstalling cwm which seems to install fine, however when i click recovery it goes back to the warning screen. I have also tried reinstalling the stock firmware, however the same problem occurs.
Do you have any suggestions?
Thanks
Click to expand...
Click to collapse
I have sorted this now.
How did you solve it, I have the exact same problem except I was reinstalling the stock android.
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
Hey everyone
My Nexus 5 White suddenly reboots and shows up and stuck at Google Logo startup. It drained battery very quick and turned off while i was going back to home. At home I entered to Bootloader (Vol Down + Power) and then Power+Vol Up for additional menu to Clear cache. It worked and appears it cleared cache and rebooted but it stuck at the logo again.
So I decided to follow guides to Flash everything again. But when I try to flash Cache, Bootloader and System error msg shows up "FAILED (remote: flash write failure)" .
Some guides claim memory is dead? Anyone experienced this situation?
PS: Yes I unlocked the bootloader and I tried 6.0 and 5.X
Does the bootloader remain unlocked?
The bootloader in mine would unlock then re-lock at reboot. Also, mine would be stuck at the screen with the spinning balloons. Tried latest 5.1 and 6 too.
Wound up getting a used N5 with smashed screen and swapped motherboards.
audit13 said:
Does the bootloader remain unlocked?
The bootloader in mine would unlock then re-lock at reboot. Also, mine would be stuck at the screen with the spinning balloons. Tried latest 5.1 and 6 too.
Wound up getting a used N5 with smashed screen and swapped motherboards.
Click to expand...
Click to collapse
Yep it remains unlocked. Can't even see the balloons. Now it starts directly to Bootloader. Anyone have this issue fixed?
Nope , it's dead Jim. eMMC is fried.
audit13 said:
Does the bootloader remain unlocked?
The bootloader in mine would unlock then re-lock at reboot. Also, mine would be stuck at the screen with the spinning balloons. Tried latest 5.1 and 6 too.
Wound up getting a used N5 with smashed screen and swapped motherboards.
Click to expand...
Click to collapse
I am having same problem, after I try to reset NExus 5 stuck at 'erasing', I tried to unlock bootloader but as soon the Phone reboots bootloader gets locks again, I tried nexus toolkit to flash stock rom, I tried flashing custom recovery but phone wont boot in custom recovery, Please tell whats wrong, should I give up on this phone??
Thank you
The emmc is damaged and cannot be replaced. A motherboard swap was required to fix mine.
audit13 said:
The emmc is damaged and cannot be replaced. A motherboard swap was required to fix mine.
Click to expand...
Click to collapse
Can confirm, had the same. Emmc fried, could not be repaired, fix: replace mainbord
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Just ran into the same issue with a friend's Nexus 5... Gone for good sadly, time to get a Nexus 5X.
A relatively cheap fix would be to find a used N5 with a smashed screen and working motherboard. I picked up phones between $30 and $50 CAD on Kijiji.
Turuunen said:
Yep it remains unlocked. Can't even see the balloons. Now it starts directly to Bootloader. Anyone have this issue fixed?
Click to expand...
Click to collapse
Same as Turrunen. Maybe this symptom can't be referred to the EMMC bridge...Still seeking for solutions...
Or maybe even though we don't get the point, we still need to swap a main board or buy a new one...
With a unlocked bootloader, failure to flash a stock ROM to the phone, especially, anything above 4.2.2, is also an indicator that something is wrong with the emmc.
Turuunen said:
Hey everyone
My Nexus 5 White suddenly reboots and shows up and stuck at Google Logo startup. It drained battery very quick and turned off while i was going back to home. At home I entered to Bootloader (Vol Down + Power) and then Power+Vol Up for additional menu to Clear cache. It worked and appears it cleared cache and rebooted but it stuck at the logo again.
So I decided to follow guides to Flash everything again. But when I try to flash Cache, Bootloader and System error msg shows up "FAILED (remote: flash write failure)" .
Some guides claim memory is dead? Anyone experienced this situation?
PS: Yes I unlocked the bootloader and I tried 6.0 and 5.X
Click to expand...
Click to collapse
Weired but worked for my sis nexus 5
boot ur phone into bootloader
flash stock 6.0 thru Wug fresh's tool but while flash when it comes in downloading boot or what ever in your phone restart it in middle of flashing ! and then again flash! if this dosent work them Emmc id fried for sure
So recently for some reason my Nexus 5 gets stuck on the booting animation. I think it was updating to 6.0.1 or something but I'm not sure, because I just woke up one day and the phone wouldn't boot, and when it finally did it just gets stuck on the boot animation. I've tried to flash stock images and etc but I need an unlocked boot loader and for some reason if the phone doesn't boot completely after unlocking the bootloader, then it gets re-locked. So now my last option is to use the stock recovery to wipe data or something but when I go to the screen with the dead android guy, no combination of buttons seem to make the recovery options show up. If anyone could help that would be great, even if it doesn't involve the stock recovery!
unlock
shylittlezerg said:
So recently for some reason my Nexus 5 gets stuck on the booting animation. I think it was updating to 6.0.1 or something but I'm not sure, because I just woke up one day and the phone wouldn't boot, and when it finally did it just gets stuck on the boot animation. I've tried to flash stock images and etc but I need an unlocked boot loader and for some reason if the phone doesn't boot completely after unlocking the bootloader, then it gets re-locked. So now my last option is to use the stock recovery to wipe data or something but when I go to the screen with the dead android guy, no combination of buttons seem to make the recovery options show up. If anyone could help that would be great, even if it doesn't involve the stock recovery!
Click to expand...
Click to collapse
You only need to go back to the bootloader to unlock and then flash factory images, why do you need recovery?
If the bootloader is relocking itself after a reboot, the emmc has probably gone bad and can only be fixed with a motherboard swap.
audit13 said:
If the bootloader is relocking itself after a reboot, the emmc has probably gone bad and can only be fixed with a motherboard swap.
Click to expand...
Click to collapse
aw that's unfortunate. thanks anyway
I had two Nexus 5 phones that would bootloop and, eventually, the bootloader would keep relocking each time I rebooted.
I bought a couple of used N5s with busted screens, swapped motherboards, and everything went back to normal. A new motherboard is way too expensive.