Soft-Bricked? - Moto G 2015 Q&A, Help & Troubleshooting

Kinda new to this, so I apologize for any incorrect terminology. This is the second phone I've tinkered with, the first having been a LG Optimus Q which I only rooted.
So, I started off with flashing TWRP recovery and rooting my phone. Everything was fine. Decided I wanted to tinker with the status bar and other parts of the display and found CyanogenMod.
Flashed CM recovery, then installed CM from CM recovery. Booted into device to find I had lost root, and somewhere in the process of re-rooting my phone stopped booting past the "boot-loader unlocked" warning screen, but I can access recovery etc. It also boot-loops when I don't power it down from recovery.
Have attempted flashing stock, re-flashing TWRP/CM recovery, then attempted to install CM again from CM recovery only to have it fail. Could a corrupt mod cause a soft-brick?
I'm re-downloading CM now, hoping that a non-corrupt file will fix this.
Anyone have any other suggestions in case that doesn't work?
::EDIT:: It worked. Phone boots past "bootloader unlocked" warning screen, past the CM boot logo and into the phone.

Wrong place
This is Moto g3 forum!

Yousvel said:
This is Moto g3 forum!
Click to expand...
Click to collapse
This was referencing my Moto G 3, actually.

Related

[Q] Phone won't boot after changing to ART

I had really hard time naming this thread because I'm not sure anymore what's the problem.
I tried to update my Moto G (unlocked bootloader and rooted) to 4.4.2. First I unrooted the device by flashing stock rom using this guide. After I had succesfully updated to 4.4.2 I changed from dalvik to ART. When I tried to reboot, after the Motorola boot animation there was only a black screen. I tried to downgrade back to 4.3 with no success. Now when I try to boot I only get the "warning bootloader unlocked" sign over and over again. CWM recovery can't mount /sdcard/.
Have I bricked my phone or is there something I can and should do?
Thanks for the replies, I'm covered in cold sweat here.
EDIT: Seems I was too quick to make a thread. After editing the flashall.bat a little like stated in the thread I was able to flash back to stock.

Wiped system on droid maxx and can't fix it.

I accidentally (don't ask) wiped my system while trying to install cyanogenmod. After doing that CM seemed to finally successfully install but it was stuck at a bootloop. I went back into recovery to restore my backup but it resulted in an error the first time. I tried it again and it said it was successful. I tried booting that up but the boot logo looked different than before and it wouldn't boot. It wasn't a bootloop but it was stuck on the boot logo. After trying a few more different things nothing worked and I decided to flash the stock firmware back. When I tried RSDlite failed the flashing process. Maybe I don't have the right firmware for my phone or something. I can't figure it out. I'd really appreciate anyone input on this. I need to get my phone up and going again as soon as possible. It's a Droid Maxx. It's not the Dev Edition but it does have an unlocked bootloader.
Thanks
EDIT:
I tried flashing that firmware again and for some reason it worked the second time. This thread can be deleted.
If you find it wont boot past the CM bootanimation, go back to recovery and Factory Reset - that normally will get it to complete the boot process. Make a backup first so you can easily restore back if you choose. Beats RSD back to stock and starting over...
I also run an unlocked Droid Maxx, non dev, currently on AICP ROM or CM, whatever flavor I feel like and who is updating their ROM the most often.

[Q] Help! My moto g is hard bricked after flashing CM12

I rooted my phone by unlocking my bootloader, putting philz touch recovery, and flashing superSU.zip. After using my phone with root for a while, i noticed that some things were really unstable and buggy, such as it wouldn't charge, so i decided that i might as well flash cyanogenmod 12 since i have a recovery. This was my first mistake, as flashing cyanogenmod put my phone into an infinite boot animation screen. I then used adb to sideload the official Motorola 5.1 update. But this also gave me an infinite bootloop. I tried flashing cyanogenmod 12.1, that also didnt work. I tried flashing stock android 5.1, also bootlooping. I did some searching and i found that my bootloader was not recent enough to flash lollipop roms. So i tried again after updating my bootloader, and now its even worse. It doesn't even attempt to start up, it just goes straight into recovery mode as soon as i boot it up. It also has this strange screen flickering/glitching going on, like this. I don't even know where to go from here so any help would be greatly appreciated.
Some extra info:
I did clear all cache before flashing.
Model number is XT1032
Bootloader version is 4118, before it was 4113.
I recommend flashing a stock 4.4.4 ROM to your phone using fastboot commands. Do no flash anything older than 4.4.4.
Flash cm11 first. I had the stuck at bootanimation. On cm 12.1 flashed 11 then wiped and flashed 12.1 and all is Good

Majorly screwed up my Moto G [URGENT HELP NEEDED]

Alright so I have a Moto G original version, currently running 4.4.4. I previously rooted it and stuck TWRP on it, but then when it became available to update to Lollipop on the Moto G I tried to get stock recovery on it. I used "MotoToolAIOV3" to put "Kitkat Stock Recovery" on it. This seemed to work fine, until it came to update, which then it errored every time I tried. I then realised the stock recovery that "MotoToolAIOV3" must be faulty or something, so I tried reputting TWRP on my Moto G by flashing it from an app called "Rashr". This seemed to be successful, HOWEVER I went to reboot my phone to check if it had worked, put it into bootloader, then went into recovery and it still came up with the stock recovery "MotoToolAIOV3" had given me. I was confused, so I tried "normal powerup", which THEN sent me into TWRP, however this time, when the bootloader unlocked warning came up, a weird blurry line went through my screen every so often, and then it went into TWRP, with the line going across the screen in TWRP as well. I've tried to boot into normal powerup through TWRP, Bootloader, normal powerup, holding down power button but every time I try, it goes into TWRP with a dodgy line going across my screen. I'm currently doing exams and I really need my phone as I have revision notes on apps that I can only access on that phone, and things such as exam timetable saved in the actual phone.
Please, somebody help ):
Again my phone is a Moto G Original Gen running 4.4.4 stock android, on a tesco thing (cant remember what its called might be kernel).
Thank you.
bump
bump
bump2
bump2
Arcenum said:
bump2
Click to expand...
Click to collapse
Seems like you have flashed TWRP into the kernel partition. Seem like the "Rashr" app or whatever flashed it there by mistake. I recommend that you install TWRP via a more standard procedure, such as using fastboot(if bootloader unlocked) or using the instructions given where ever you downloaded TWRP. Your situation is not serious as long as you are careful....
1. Install recovery to correct partition
2. Boot to that recovery and wipe/factory reset etc...
3. Install an new ROM.

Unknown model stuck on fastboot, can't flash Stock Image

About a year ago, a friend gave me his Moto G so that I rooted it for him. On the system settings it showed as "falcon", XT1032. Everything was working fine. Then, he got a Moto G3, and gave his old Moto G to his young brother. After about two months, my friend told me that the old Moto G was in a bootloop, so I fixed it. Two weeks later, he told me the phone was no longer booting (it could barely boot into fastboot) and gave it to me again. Obviously, his young brother did something, but I don't know what, oh and also both times the battery was completely discharged when I received it.
So, I thought "Easy, just flash stock image and it will boot again". So I downloaded XT1032's stock image (5.1, as that was the version installed) and tried to flash it. Got many errors, both on PC fastboot/mfastboot and phone's fastboot. Also I couldn't boot or flash TWRP recovery, everything was broken. So I checked the model number on the battery, and it said it was XT1039, the 4G, peregrine version. So I downloaded peregrine's stock, and tried to flash it. Still got lots of errors (image size is too large, boot hab failed or something like that, I can't remember it clearly) but at least now I was able to boot TWRP recovery, but I still couldn't permanently flash it. There I checked the partitions, and they were corrupted, so I fixed them. Tried to flash again with no luck. Booted TWRP, tried to flash LineageOS, and got an error saying that the phone is the Falcon version! So, downloaded Falcon's Lineage, flashed it successfully, but the system won't boot, instead it will default to stock recovery (which was previously not working). AGAIN tried to flash Falcon's stock, now I'm back to the begining...
A solution I thought was intentionally bricking the phone completely and blank flash it, but I'm unsure how to do it, and I don't think is the best option...
BTW if someone could tell me how every partition is originally formatted so I can be sure all of them are fine, thanks.

Categories

Resources