its a first gen US boost mobile moto g xt1031. it is boot-loader unlocked and rooted. currently has twrp recovery and had cwm. i have never been able to flash any rom either from side-load or from internal or external sd. about a month ago i started having trouble restoring backups and now a few days ago it wont let me make a backup either. it gets stuck when it comes to restoring or backing up the data partition. beforehand i had no problems with backups. when i got the phone almost a year ago i didn't have any trouble boot-loader unlocking and rooting it. i am currently using lubuntu with the android sdk installed and my phone is recognized in adb and fastboot. i have been rooting and flashing android since my hd2 days and i never had this problem. i have tried several different boost moto g roms and none of them will boot. i just get boot loops. i have tried 4.4.2 4.4.4 and 5.0 roms. none will boot up. can anyone help me out with any ideas of whats wrong? debugging is on and again it is rooted boot-loader unlocked running twrp and recognized on my computer with adb and fastboot. thanks.
I am having the exact same issue. I first flashed BlissPop onto the device, and immediately ran into boot loops. I flashed a CM nightly for the 1031, same issue, and now even a stock rom does nothing but boot loops.
i have been trying to run cm since last july. im almost to the point that i dont even want this phone anymore. ive never had this problem with any other phone. i hope someone can help us. the only thing i can flash is recovery. but thats pretty much pointless since i can flash a rom or create or restore a backup. the old backup i have fails when it comes to date but it will boot. i just have to start from the beginning every time.
Yeah man, I've been through everything I typically do for rescues like this one, nothing has worked. Stock ROMs bootloop as well, which is just strange. I'm starting to think I killed the parition table on the phone itself.
davenull said:
I am having the exact same issue. I first flashed BlissPop onto the device, and immediately ran into boot loops. I flashed a CM nightly for the 1031, same issue, and now even a stock rom does nothing but boot loops.
Click to expand...
Click to collapse
good news that might help you. i had to reformat my whole system and change it to f2fs using twrp. installed cm 11 and it booted up just fine. im gonna try to install cm 12 now. finally after nearly a year... oh and no thanks to anyone else on this thread. (you not included in that).
Related
I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?
Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.
Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on
TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
ilinimud said:
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
Click to expand...
Click to collapse
You have to ensure the ROM you are using is built for the KK kernel. Not all ROMs work with the KK kernel.
Here is a list of ROMs that work with KK:
http://www.droidrzr.com/index.php/topic/48909-kitkat-roms-list/
Anything else will result in what you are experiencing - bootloops.
Hi,
I'm getting killed with this device. I have a VZW XT926 Stock from reverting back to VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml this twice tonight:
I'll begin with how I started, I unlocked the SIM and threw a T-Mobile in there. No problems, so I rooted with Towelunlock, installed SuperSU and updated the Binary. Then I installed TWRP2710-RAZR-HD_M-KITKAT through Fastboot. I could get into TWRP and all was right with the world. Then I tried to install cm-11-20140708-SNAPSHOT-M8-moto_msm8960 and I'd get stuck at the Moto dual core logo. No progressing. So I thought maybe the Factory reset wipe wasn't enough in TWRP so back to recovery and wipe everything, and flash again and reboot and same result. So now I can only boot to recovery I didn't backup my current rom, cause, ya know I'm a stoopid, and I have to factory reset to 4.4.2, and re root, and re unlock sim. Frustrated right now to the point of entertaining the idea of using this Verizon bloat rom rooted and not going for CM11.
I'm sure I'm too tired to keep this up tonight, and I'll probably really brick my phone if I keep at it without any sleep. My question for you is:
What am I doing wrong, what simple instruction am I missing when reading that is screwing me up? Because I'm too dumb/tired/whatever to figure it out without your help.
The snapshot is for the old kernel. Download the newest nightly. I ran into the same issue not knowing. Its that easy!
You need to start over jethro....back to HoM And this time make a backup of Stock before flashing a custom rom
j37hr0 said:
Hi,
I'm getting killed with this device. I have a VZW XT926 Stock from reverting back to VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml this twice tonight:
I'll begin with how I started, I unlocked the SIM and threw a T-Mobile in there. No problems, so I rooted with Towelunlock, installed SuperSU and updated the Binary. Then I installed TWRP2710-RAZR-HD_M-KITKAT through Fastboot. I could get into TWRP and all was right with the world. Then I tried to install cm-11-20140708-SNAPSHOT-M8-moto_msm8960 and I'd get stuck at the Moto dual core logo. No progressing. So I thought maybe the Factory reset wipe wasn't enough in TWRP so back to recovery and wipe everything, and flash again and reboot and same result. So now I can only boot to recovery I didn't backup my current rom, cause, ya know I'm a stoopid, and I have to factory reset to 4.4.2, and re root, and re unlock sim. Frustrated right now to the point of entertaining the idea of using this Verizon bloat rom rooted and not going for CM11.
I'm sure I'm too tired to keep this up tonight, and I'll probably really brick my phone if I keep at it without any sleep. My question for you is:
What am I doing wrong, what simple instruction am I missing when reading that is screwing me up? Because I'm too dumb/tired/whatever to figure it out without your help.
Click to expand...
Click to collapse
ESCollins90 said:
The snapshot is for the old kernel. Download the newest nightly. I ran into the same issue not knowing. Its that easy!
Click to expand...
Click to collapse
Yup, this worked. Now to delete that backup
Sent from my Amazon Jem using XDA Free mobile app
Alright, so it has been a while since I last tried custom roms only to go back to official EUI, so bear with me as this is probably a basic dumb question.
So I had TWRP and the official EUI. I saw that there was an OTA update and normally used the update app on the phone. It downloaded the rom, and booted into twrp which started flashing the rom. So far so good. I let it do its thing as it took some minutes... once it was ready it showed a dialog asking if I wanted the flashing process to rewrite the boot partition or let TWRP own it. I wasn't really sure which one to pick, but as I "swipes to unlock", the phone restarted anyway without letting me pick any of the two.
Now It only boots into recovery mode (TWRP). This is probably easy to fix in TWRP, but I am not sure how. Can anyone help?
Thank you.