So, I got my moto g a few days ago, and today I decided to unlock the bootloader.
The process went fine, but when it booted up to the startup screen, everything was forceclosing (systemui, etc)
I force shut it down. After that, it would show the boot animation, going to the rippling motorola logo, and then go to a black screen. I am currently flashing to stock using fastboot, I can use fastboot to flash an alternate recovery, but that seemed to do nothing. Stock recovery does not work.
I really hope there's a simple, idiot proof way to fix this.
Anyone know what it could be?
Go into bootloader, flash custom recovery and then flash a custom ROM
Sent from my XT1032 using xda app-developers app
bobcat913 said:
Go into bootloader, flash custom recovery and then flash a custom ROM
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
I flashed TWRP, twrp works fine, but I need to transfer a ROM to the phone, using TWRP's sideload feature doesn't work, as my phone does not show up as a device, once in adb. In device manager, it shows up as "Android" and has no drivers, when trying to use the adb sideload feature in recovery.
I ended up fixing it after all, installing the easy universal adb/fastboot drivers, and then adb pushing the rom, and gapps
Related
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
God I'm stupid.
So I flashed a 4.4.3 theme on a 4.4.4 ROM, and I was stuck at the boot animation.
I went to recovery, found out I don't have any ROM's on my phone, so I figured I should flash through fastboot.
I downloaded the stock 4.4.4 image, tried to do the flash-all.bat, got an error.
I extracted the RAR inside it, manually flashed recovery, system, boot etc.
I can now only enter fastboot. Whenever I try to go to recovery or start the phone the screen just goes black, and all I can do is hold down the power button and restart to fastboot.
I sure hope you guys can help me, I don't have the money to buy a new phone
Drunkbag said:
God I'm stupid.
So I flashed a 4.4.3 theme on a 4.4.4 ROM, and I was stuck at the boot animation.
I went to recovery, found out I don't have any ROM's on my phone, so I figured I should flash through fastboot.
I downloaded the stock 4.4.4 image, tried to do the flash-all.bat, got an error.
I extracted the RAR inside it, manually flashed recovery, system, boot etc.
I can now only enter fastboot. Whenever I try to go to recovery or start the phone the screen just goes black, and all I can do is hold down the power button and restart to fastboot.
I sure hope you guys can help me, I don't have the money to buy a new phone
Click to expand...
Click to collapse
Do you know what error you got when you did the flash-all?
Sent from my Nexus 5 using XDA Free mobile app
Have you tried flashing stock 4.4.3 or even 4.4.2 completely in fastboot? Including recovery again??
jd1639 said:
Do you know what error you got when you did the flash-all?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember really, something about missing .sig files I think
KJ said:
Have you tried flashing stock 4.4.3 or even 4.4.2 completely in fastboot? Including recovery again??
Click to expand...
Click to collapse
I'm trying the Nexus Root Toolkit, and before that I managed to install TWRP 2.7.1.1 and boot to recovery.
However, I can't boot to the system.
I also downloaded 4.4.3 and going to attempt to flash it.
The missing Sig error is normal and nothing to worry about
Sent from my Nexus 5 using XDA Free mobile app
It's all fine.
Luckily a friend called me on Skype and I told him about my bricked device, he suggested to use NRT.
Thanks for the help guys!
I have an unlocked bootloader, and I installed CWM recovery for the Photon q/asanti in the ROM Manager app. I want to install CM11, but when I try to go into recovery, the Motorola dual core screen comes up, and it never goes away unless I turn the phone off. What am I doing wrong? This is really frustrating because I'm so close lol
Get a recovery designed for the HD and flash that.
Sent from my HTC6525LVW using Tapatalk
It is, and I can verify that it's installed too.
If you can't get into it, it's not installed.
Sent from my HTC6525LVW using Tapatalk
Well then I guess the app I "installed" it with is wrong.
But I have a hard time believing that. I think something is preventing it from coming up, because I get stuck on the boot screen immediately after trying to open it. The boot screen shoudn't appear at all. I've also tried giving up and resetting my phone to factory, but it just reboots. I'm bummed because it is running slow and apps are stopping, and I need this phone.
That isn't my phone by the way, it's just a picture to show the screen it gets stuck on when I try to open the recovery.
Can you get into ap fastboot?
MatreyuC said:
Well then I guess the app I "installed" it with is wrong.
Click to expand...
Click to collapse
Neither CWM or TWRP are official for this phone, so you can't install them through their apps. The recovery you attempted to install is for a close relative of the HD, but it's not correct. Get a correct recovery out of the Dev section and flash with fastboot.
Sent from my HTC6525LVW using Tapatalk
Would that be why it gets stuck on the boot screen when I try to open the recovery? The only reason I used it was because it's supposed to work with my phone and some others witht the same codename. Do you know any good tutorials on how to flash a recovery with fastboot? Because I can get into fastboot.
http://forum.xda-developers.com/showthread.php?t=2232476
Sent from my HTC6525LVW using Tapatalk
Thank you
Hello...
I made a mistake and flashed my recovery with out renaming my recovery.sh file.... I am rooted and unlocked status code 3. I am also updated on stock ROM. I need to back up and switch ROM's. I original flashed recovery with ROM Manager and got no results. Then I used a flash tool but failed to read the instructions on the thread before flashing. I have since then flashed several TWRP and CWM versions, as well as stock to no avail. When I select recovery from the boot menu I see the red Motorola emblem for a few minutes then it reboots normally. Does any one have a fix and or the recovery.sh file. Thanks.
Download the latest TWRP and place in your fastboot folder. Disconnect your phone from the computer, boot into fastboot, and then plug your phone in. Wait for the phone to connect. After it's connected type "fastboot flash recovery recovery.img." Recovery.img will be the name of whatever file you downloaded. After flash is complete, unplug phone and power off. Immediately boot back into recovery. Do not boot into OS.
With this method, you don't need to rename recovery.sh. Rebooting directly into recovery allows the updater script to complete, so the stock recovery doesn't take over. If you boot right back into OS, stock recovery will override.
If you can't do fastboot, download Flashify and use that app to flash the TWRP you downloaded. TWRP for this phone is not official, so it won't show up in ROM or TWRP Manager. You'll have to DL off here.
Sent from my HTC6525LVW using Tapatalk
Thank you for your detailed reply, I will try this tonight and let you know how it goes, I suspect it will work.
Sent from my Barnes & Noble Nook Tablet using XDA Free mobile app
You're welcome, hopefully one of methods will work for you.
Sent from my HTC6525LVW using Tapatalk
Thank you! Worked like a charm. Renaming the file Recovery.IMG, disconnecting my USB cable, powering down and rebooting directly into recovery is what I did not do. Doing that has solved the problem!
Sent from my Barnes & Noble Nook Tablet using XDA Free mobile app
Custom recovery unrooted my stock updated ROM.. Be careful!
Custom recovery has an option to root or you can flash SuperSU in recovery.
Well I kinda bricked it any way lol, but I fixed it with HouseOfMoto I think. At least I see the boot screen now...
Yep seems to have booted this time I will flash TWRP instead of CWM.
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
t.holley.os said:
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
Click to expand...
Click to collapse
What do you want to do exactly? Restore stock recovery so that you can take the OTA? If you followed either one of the methods on that thread, you should already be stock, i don't get why you booted TWRP again.
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
t.holley.os said:
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
Click to expand...
Click to collapse
Just flash the stock recovery image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
t.holley.os said:
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
Click to expand...
Click to collapse
Press and hold power for 30 second, the device will try to boot but just keep holding the power. Then press and hold vol down and power. It doesn't boot into the bootloader?
Sent from my Nexus 9 using XDA Free mobile app
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
t.holley.os said:
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
Click to expand...
Click to collapse
FYI the TWRP boot loops are due to MTP bug that was never fully fixed from 2860. It's better than it used to be, but still an issue occasionally, especially if connected to power while you try to get in to TWRP.