My moto g XT1033 was running fine on CM13 nightly. Since i had few bugs i tried to flash PA 5.1 which is based on CM12. And my phone is stuck in bootscreen. Not able to enter recovery also. Only the bootloader is accessible.
Pls help.
jayabharath2612 said:
My moto g XT1033 was running fine on CM13 nightly. Since i had few bugs i tried to flash PA 5.1 which is based on CM12. And my phone is stuck in bootscreen. Not able to enter recovery also. Only the bootloader is accessible.
Pls help.
Click to expand...
Click to collapse
Did you try to flash recovery by fastboot ?
ssinghebay said:
Did you try to flash recovery by fastboot ?
Click to expand...
Click to collapse
yes i tried it, But cant flash recovery, and i cant access recovery also.
jayabharath2612 said:
yes i tried it, But cant flash recovery, and i cant access recovery also.
Click to expand...
Click to collapse
better wipe and reflash stock rom 5.1.1 through fastboot.
I owned same 1033. almost everyday I flash any custom rom with twrp. and yah switching 5.1/6 doestnt matter to me when I flash or restore or wip. no problem here.
Mine also stuck once, I let the stay as for some hours than try to go to recovery, wiped everything including internal, than flashed new cm. No problem after that
Related
So i decided to install the CM 12 on my MotoG.I downloaded the files and followed the instructions.I wiped cache,dalvik,data and did Format System but the installation failed.So I reboot my phone only to see that it was stuck at a bootloop.I get back to TWRP and I see that there was no OS installed.I decided then to flash 4.4.4 which worked,but after rebooting i was in a bootloop with no OS once again.I installed PhilZ Touch to see what's wrong.It says that I can't mount the system and the sdcard.I've tried Sideloading,adb pushing but everything fails...Is there anything i can do?Help is much appreciated
Have you tried to flash a stock ROM via fastboot commands?
Yes nothing happened..still stuck at bootloop...
nikoschasapis said:
Yes nothing happened..still stuck at bootloop...
Click to expand...
Click to collapse
which stock rom did you try to flash using fastboot?
if it's the stock 4.4.4 it's probably going to fail, you need certain things to do (you can search around here) if you're using xt1033, you can search for (xt1033 stock) there's a guide that will get you up and going. On my moto g that has flashed stock 5.0.2 and cm12, i found out that i can't use the normal method to flash the stock 4.4.4 rom, rather i was forced to flash the 5.0.2 rom, since the fastboot command fails at almost everything, which would leave the phone unusable
oh yeah, here's the guideRESTORE TO STOCK
Nevermind.I formatted the data and it let me adb push the stock 4.4.4
ROM
I recently upgraded from stock opo cyanogen to the cyanogen nightlies. now whenever i go back to TWRP to make a backup, it breaks my os and i get stuck in a bootloop. i have to factory reset my phone and set everything up again, and all of the backups are just bootloops. i already tried re-flashing TWRP and cyanogen, both through the TWRP manager and through the fastboot flash recovery command. if anyone has a solution it would be much appreciated.
ItsDeadEnd said:
I recently upgraded from stock opo cyanogen to the cyanogen nightlies. now whenever i go back to TWRP to make a backup, it breaks my os and i get stuck in a bootloop. i have to factory reset my phone and set everything up again, and all of the backups are just bootloops. i already tried re-flashing TWRP and cyanogen, both through the TWRP manager and through the fastboot flash recovery command. if anyone has a solution it would be much appreciated.
Click to expand...
Click to collapse
Are you using the latest version of TWRP?
fixed it
Shankar9822 said:
Are you using the latest version of TWRP?
Click to expand...
Click to collapse
it turns out it had nothing to do with twrp, it was a corrupted verion of gapps.
i just reflashed everything. (cm12, new gapps download, and supersu)
Hi.
Today I wanted to upgrade from CM11 to CM12.1, but I had to upgrade the bootloader first. It all worked and I'm now on bootloader version 41.18.
When I flashed the ROM it flashed in 20 seconds from an USB stick. It seemed a little to fast. When I rebooted it worked fine and I was on Android 5.1.1, but after installing SuperSU and rebooting I stuck into a bootloop.
I'm now in a bootloop and when I try to enter the recovery the TWRP splash screen comes up, but then it goes into the bootloop again.
I have the XT1032 and my TWRP version is 2.8.6.0 and I have a TWRP backup from CM11
If someone could push me in the right direction how I can access TWRP then that would be great.
Thanks in advance.
Quick update
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
zomgwalrus said:
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
Click to expand...
Click to collapse
I have the same issue, cannot get into twrp, how did you managed to boot into TWRP?
i had same issues in my moto g xt1032 i tried below CM12.1 works without issues.
go recovery --- wipe---- format data
and try step install steps like install rom zip & gapps
Ok, first what do you use to flash recovery, can you reflash recovery with the lastest TWRP version (2.8.7.0) and post back the logs here? Then tell me if you can get into recovery
Its common place that twrp cause bootloop with backups.
No problem try to
Install new twrp using fastboot mode it will be work fine
Hi,
This is a new Mi4w Global and I got tired of waiting to Marshmallow to come OTA so decided to try CM13 and seem to have bricked it. Please help!
I flashed latest TWRP (also tried CyanogenMod recovery), then I did the factory reset, wipe cache, flashed the CM13 ROM but it won't boot. Always flashes the Mi logo and then straight into Fastboot. I can still access recovery by holding volume up and power, but no amount of flashing the ROM seems to work. I've tried latest Stable and Nightly CyanogenMod ROMs.
Did I miss a step? One thing I remember doing which might have been the problem is while I still had the original Xiaomi recovery I opted to boot onto System 2 or whatever. I think I flashed recovery straight afterwards. I wonder if that is the cause?
Anyway, please help me! Many thanks if you can help me get my phone working again.
Update: In case this helps anyone else, I did manage to find an original Mi4 recovery so I flashed it and the I also flashed the official MIUI developer build of Marshmallow. Now my phone is unbricked. I would still like to figure out how to root it and install CM13 sometime, but at least I have a working phone for now.
It's simple, you selected system 2 before installing cm13, and two installed rom in system 1. Be on system 1 and try again.
Prashanth Meesara: said:
It's simple, you selected system 2 before installing cm13, and two installed rom in system 1. Be on system 1 and try again.
Click to expand...
Click to collapse
OK thanks. What is system 2 then, is that the "sdcard" partition? I had looked in both TWRP and Cyan recovery for an option to change the boot partition but couldn't find it.
I own a moto g xt 1033 and installed cyaonogem mod 13, I used to recovery twrp,but he did not quit the cyaonogemmod robot image, then restarted and tried to reinstall the android back , but when the device will start it appears the image of the unlocked bootloader and restarts and it becomes infinite.
when I try to clear system cache, the TWRP error , it seems the TWRP is corrupted , what can be ?
If anyone can help me I can post a video on youtube showing defects
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Professor Gibbins said:
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Click to expand...
Click to collapse
Sorry for the delay....i using twrp 2.8.5.0, I stored in the internal storage to cyanogemcm12, It was executed wipes, install cyanogemmod, but got stuck in logo cyanogem,
I returned the recovery was made and wipes again, and install Rom XT1033 Android 4.4.4 KitKat Dual Chip, unfortunately now he does not leave the image "boot loader" unlocked).
*I have access to fastboot via adb!
*I have access to recovery!
*however after all these errors, the TWRP does not allow Wipes, and also appears error installing rom.
*When I install a rom stock fastboot , this does not seem a mistake, but goes into bootloader and is restarting without stopping
help you if I put a video on youtube?
I will record a video and share tomorrow.
Thanks
Sorry my english
Professor Gibbins said:
What TWRP version are you using? What were the steps you took to install CM and the stock ROM? What was the error that TWRP gave you?
Click to expand...
Click to collapse
i using twrp 2.8.5.0, I stored in the internal storage to cyanogemcm12, It was executed wipes, install cyanogemmod, but got stuck in logo cyanogem,
I returned the recovery was made and wipes again, and install Rom XT1033 Android 4.4.4 KitKat Dual Chip, unfortunately now he does not leave the image "boot loader" unlocked).
*I have access to fastboot via adb!
*I have access to recovery!
*however after all these errors, the TWRP does not allow Wipes, and also appears error installing rom.
*When I install a rom stock fastboot , this does not seem a mistake, but goes into bootloader and is restarting without stopping
i have link youtube
Thanks
Sorry my english
To get the phone working again, I would suggest flashing latest 5.1 version of these factory firmware images (for your exact device model) through fastboot.
To flash CM13, try using TWRP 3.0.2-0, and the latest CM13 snapshot. Note that the first boot of Cyanogenmod can take a long time (20+ minutes).
Professor Gibbins said:
To get the phone working again, I would suggest flashing latest 5.1 version of these factory firmware images (for your exact device model) through fastboot.
To flash CM13, try using TWRP 3.0.2-0, and the latest CM13 snapshot. Note that the first boot of Cyanogenmod can take a long time (20+ minutes).
Click to expand...
Click to collapse
I tried all these Step
I think TWRP is corrupt, or the fast i dont know , it installs the features, but not fixed
link my video youtube.com/watch?v=ZGgpL_JCQSY