Related
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
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?
I am running cm12 nightly of 3rd April and I am using cyandelta to update so that I
Don't have to download 200mb everyday. It was working great until today .
I am unable to flash the latest nightly and it shows error . I even update twrp and tired
Everything please guys help.
CyanDelta is unofficial.
Maybe try flashing the regular zip, it'll probably work.
Elluel said:
CyanDelta is unofficial.
Maybe try flashing the regular zip, it'll probably work.
Click to expand...
Click to collapse
solved it . i just copied the update script from older version of nightly and placed it in the downloaded one
I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on sd card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
chairshot215 said:
I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on sd card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0_r3 for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59913506&postcount=3
beekay201 said:
http://forum.xda-developers.com/showpost.php?p=59913506&postcount=3
Click to expand...
Click to collapse
Thanks but the thread is the issue with the bootloader version in the updater script like the op had experienced I am not having an issue at this point but after rebooting into system. At first I thought maybe Kernel as am using my own kernel but same with Stock CM Kernel. Also Nandroids restore and boot without issue so have been using my Nandroid backed up just before installing 5.1 and have flashed test versions of my Kernel just fine. Its just weird that the issue is when booting after a fresh Rom install. Can flash a new boot.img without causing the issue and have done a diff between update scripts just in case something else funny in my update script other than the bootloader version line ans they come back the same.
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).