Database Users

[Q] Need some help urgently - backed into a corner while flashing a new rom

So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:

joeski27 said:
So this evening decided to go back to CM11 after using stock for a while on my N4. So I downloaded the latest CM11 nightly, along with the latest PA gapps. I did a full wipe in recovery, then flashed CM11, followed by a flash of the gapps. However, it immediately appeared that the gapps file must have been bad (gave me the red exclamation triangle android background). So rebooting leaves me in a endless bootloop. Only problem is I don't have another gapps file saved on my SDcard. And to make matters worse (yeah I know) I didn't nandroid my system prior to this, though I do have everything (apps, etc) saved on my SDcard. Now my problem is, I need to find a way of loading a new gapps file onto my phone. I have tried ADB, but I suspect that as a result of the factory reset I no longer have USB debugging on, as I can't connect to the device in ADB. I am becoming more than a little stressed right now, as I need to get this phone back up and running. Does anyone have any idea what I might do next?? I am not a total newbie to flashing roms, been at it a few years now, but this is the first time I've been stuck like this. Ugh! Please help! :crying::crying::crying:
Click to expand...
Click to collapse
Nobody has a suggestion? This isn't looking good...
What is strange to me is, even after doing another factory reset, it still boots to the same CM boot screen and is stuck in a boot loop. I have no idea what is going on here. And at the very least, at least I have everything still on my SDcard (backups of apps in TB, and all my other locally saved stuff...just that now I have no idea of how to get to any of it, or how to load on a working rom & gapps so I can have something to boot to!)

Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.

exb0 said:
Do a full wipe, flash CM11 without Gapps. It should boot but you won't be able to sign in to google and all that jazz. Just use the browser and download another gapps, then flash it.
Your computer won't detect ADB because ADB is only when android is running. If you're running a sideload-enabled recovery, you can push a zip and flash it through ADB.
Click to expand...
Click to collapse
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??

joeski27 said:
I've tried this now (wipe, and then flash of CM) and its STILL stuck at the damn CM boot animation. I just don't understand what the problem is here. I have never, ever had something like this happen before. Could it be a bad nightly? And if so, how the hell am I going to get another flashable rom onto my SDcard??
Click to expand...
Click to collapse
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.

exb0 said:
Hmmm, yeah it could be.
1 : Download a ROM. Check the MD5 checksum.
2 : Copy the ROM to your ADB folder and rename it to something easy (eg: Rom.zip)
3 : Fire up CMD, Navigate it to your ADB folder
4 : Boot your phone into recovery, find for a function called "ADB Sideload" or something along those lines.
5 : In CMD, type in "adb sideload *romname*.zip
6 : ??
7 : Enjoice.
This can be done for any type of flashable files.
or yknow. just return back to stock and do everything all again if you're uncomfortable doing this.
Click to expand...
Click to collapse
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...

joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Ah, it shouldn't matter that much. Instead of CMD just use terminal(that's what it's called in OSX right?).
didn't work? what error did you get?

joeski27 said:
So I don't know if anything is different, but I am doing this on a Mac running Mavericks. But I do have the latest SDK installed with a fresh download of tools. I am running CMW recovery 6.0.4.3, which does have sideload, and I attempted to use it a moment ago but it didn't work....will try again now...
Click to expand...
Click to collapse
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.

joeski27 said:
Yeah its not working, just brings up the splash of command prompts that comes up with you don't enter a proper adb command.
Click to expand...
Click to collapse
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?

exb0 said:
Enable sideload on your phone and then try using "adb devices", do you get anything? or random splash of commands again?
Click to expand...
Click to collapse
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?

joeski27 said:
No that's what I've been countering the whole time; I have ADB sideload set on the phone, and then after cd'ing my way to the folder with adb, I try "adb devices" and nothing, doesn't see the device at all. WTF?
Click to expand...
Click to collapse
sounds like a driver issue. You're gonna have to fix that or there's almost no way of fixing your phone :/

Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...

Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.'
By the way when a sideload is performed where is the sideloaded file saved? Just wondering where to find it when the time comes to flash.

joeski27 said:
Hang on....sideload looks like its working! But I ain't out of the woods yet, won't celebrate til it gets there, AND if it boots...
Click to expand...
Click to collapse
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
joeski27 said:
Now I guess the best bet is to try a fresh rom rather than a fresh gapps, would you say? I'm downloading both now, just wondered which would be my best bet. I mean at this point I just need something that will allow me to boot.
Click to expand...
Click to collapse
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.

exb0 said:
#prayforjoeski27 goodluck!
---------- Post added at 05:38 AM ---------- Previous post was at 05:37 AM ----------
try flashing a rom without gapps first. if the rom boots then wipe and reflash rom with gapps.
Click to expand...
Click to collapse
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....

joeski27 said:
Sounds like a plan. This time I'm loading the latest snapshot release of CM rather than the damn nightly, lol. At least we know that that version *should* reliably boot up....and we'll know shortly...going to save the rom to the appropriate folder, rename, and sideload....
Click to expand...
Click to collapse
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!

exb0 said:
I think all nightlies should boot up (i mean it IS cyanogen mod...). I think you just got a bad download. Remember to check MD5 if it's available!
Click to expand...
Click to collapse
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?

joeski27 said:
WOO HOO! Friggin thing booted, baby! Hello CM welcome screen! Never looked so beautiful!
So now I just need to 1) get a fresh gapps, 2) load it on to my SD via android file transfer, do a fresh wipe in recovery, flash CM again, followed by the fresh gapps, and I should be in business...yes?
Click to expand...
Click to collapse
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!

exb0 said:
Congrats!
You can try just flashing gapps on top of it, that's what I do. but if you're worried you can do a full wipe and flash it again. Completely up to you!
Click to expand...
Click to collapse
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:

joeski27 said:
Hey thanks a million for the help on this one! Like I said, I've done quite a bit with rom tinkering over the last few years, but sideloading was a first for me tonight. Though it is very good to know for the future! More importantly, however (and this is really not like me) in the future I either A) have to make sure I have enough SD space for nandriods, or B) keep a previous, working zip of a rom on the SD when I go to flash a new one (which is what I have always done but have not recently).
Again, thanks a bunch!!!! :highfive:
Click to expand...
Click to collapse
No problem as long as you're willing to learn I'm willing to help! if you ever run into any other problems feel free to PM me. I'll try to help as much as I can. :good:

[Q] soft bricked ls980

so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.

omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?

XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"

omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup

XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.

omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm

XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work

w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD

omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on

another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/

18 year IT vet/Total newb to rooting/rom'ing tablets

I read how there are no stupid questions, well I'm about to test that I think. I'm a complete newblet to this sort of thing but I have an N7 2012 running like a dog on 5.1.1. So like many, many other posters here I want to make her fast again but would rather not rollback to 4.4.
So I found this: http://forum.xda-developers.com/nexus-7/development/rom-6-0-android-marshmallow-pure-aosp-t3226012
I wonder firstly, I didn't see a step on backing the current environment up in case of brickage. Is that something the author thinks anyone wanting to flash their unit should know how to do already?
And if so, are there any other steps that would be beneficial to do prior to the actual flashing that any experienced ROM alterer would do that I should as well?
Thanks guys!

I'm about to go down the same route.
I have TWRP recovery installed and am using it to backup the more or less stock setup. (except for TWRP recovery, custom kernel and SuperSU.)
I'm seeing that my backup will take 2.6 gigs though, which almost runs me out of SDCard space.
But since 5.1 is pretty much unusable I probably won't keep the backup long.
As long as your bootloader is unlocked, Nexus devices tend to be hard to brick (barring any N7 2012 specific issues.)
Consider upgrading to N7 2013 running stock Android 6.0. I have 2 for app testing and they are pretty darn nice, especially for the price. Can buy for less than $150 new now, and good bargains for used.

Thanks Mike, Question what guide did you follow to get yours rooted and the recovery stuff updated?
mikereidis said:
I'm about to go down the same route.
I have TWRP recovery installed and am using it to backup the more or less stock setup. (except for TWRP recovery, custom kernel and SuperSU.)
I'm seeing that my backup will take 2.6 gigs though, which almost runs me out of SDCard space.
But since 5.1 is pretty much unusable I probably won't keep the backup long.
As long as your bootloader is unlocked, Nexus devices tend to be hard to brick (barring any N7 2012 specific issues.)
Consider upgrading to N7 2013 running stock Android 6.0. I have 2 for app testing and they are pretty darn nice, especially for the price. Can buy for less than $150 new now, and good bargains for used.
Click to expand...
Click to collapse

Wait, I figured it out. So I've got it rooted, then pushed Cyanogenmod recovery and rebooted and got into recovery mode. First off I tried loading Cyanogenmod 12.1 which worked well. It was snappy however I could not figure how to get gapps reinstalled. Thinking maybe another rom might already have google apps I then pushed 6.0.1_r10_Grouper-MM. Booted fine but still not gapps..
So I find a website that says to push the zip to /sdcard/ then apply update from sdcard in recovery mode. However now, I'm getting errors complaining about F2FS.
E:can't open /cache/recovery/last_log
E:unknown fs_type "f2fs" for /cache
Couldn't mount /sdcard
Installation aborted
Googles not been much help yet.
7298 said:
Thanks Mike, Question what guide did you follow to get yours rooted and the recovery stuff updated?
Click to expand...
Click to collapse

7298 said:
Wait, I figured it out. So I've got it rooted, then pushed Cyanogenmod recovery and rebooted and got into recovery mode. First off I tried loading Cyanogenmod 12.1 which worked well. It was snappy however I could not figure how to get gapps reinstalled. Thinking maybe another rom might already have google apps I then pushed 6.0.1_r10_Grouper-MM. Booted fine but still not gapps..
So I find a website that says to push the zip to /sdcard/ then apply update from sdcard in recovery mode. However now, I'm getting errors complaining about F2FS.
E:can't open /cache/recovery/last_log
E:unknown fs_type "f2fs" for /cache
Couldn't mount /sdcard
Installation aborted
Googles not been much help yet.
Click to expand...
Click to collapse
I've been doing this stuff for 5 years, so I usually don't need guides, just a few hints sometimes. CM recovery these days is something I try to avoid as it mostly works only with CM. I use TWRP and flash it with adb commands like:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-grouper.img
I ended up flashing this Marshmallow ROM because it seems to be the most popular at this time: http://forum.xda-developers.com/nexus-7/development/android-6-aosp-grouper-t3268172
And I'm happy with it so far.
Strange thing though is that I had to flash it 3 times to get it to flash without any error.
Then I had to flash the Benzo Gapps 2 times to get that on with no error. Result is working OK so far.

Damn Mike, I shoulda waited another hour before settling on mine. I tried that 6.0.1 i linked earlier in the thread about 4 times. Three times it applied successfully with 1 seeming to lockup during the new user setup. But I tried at least 4 different gapps that all didnt work. The usual results was Google Play Services have stopped. So because the day was nearing an end and I needed it last night to read I dropped back to the Cyanogenmod 12.1, changed the theme and tossed in Open Gapps Nano http://opengapps.org/?api=5.1&variant=nano
Wound up having to load play books, play services, gmail, and chrome individually.
But it's snappier than ever (so far). I'll end up re-trying 6 very soon but this time I'm trying the one you found.
mikereidis said:
I've been doing this stuff for 5 years, so I usually don't need guides, just a few hints sometimes. CM recovery these days is something I try to avoid as it mostly works only with CM. I use TWRP and flash it with adb commands like:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-grouper.img
I ended up flashing this Marshmallow ROM because it seems to be the most popular at this time: http://forum.xda-developers.com/nexus-7/development/android-6-aosp-grouper-t3268172
And I'm happy with it so far.
Strange thing though is that I had to flash it 3 times to get it to flash without any error.
Then I had to flash the Benzo Gapps 2 times to get that on with no error. Result is working OK so far.
Click to expand...
Click to collapse

I tried that MM ROM it worked fine for first week, then it started to act the same as it was on 5.1.1. I used Nexus Root Toolkit to flash my nexus to stock and then flash the rom with just few clicks

Grouper needs a total do-over. Problems with complete flash.

Hey folks. I recently revived my 2012 Nexus 7 wifi. I thought it was toast, but I guess it just needed a nap. It was having Gapps problems last time I tried to flash, and this time around, I'm having the same issues. I've attempted to flash a few versions as well as flashing a few different roms. The roms flash fine, and they run very smooth, but Gapps constantly either fails to flash due to space concerns or even though it claims success, it doesn't load the services and I end up with a ton of errors and can't really work with the tablet. The computer itself obviously runs great, but I'm missing something, or need to take it back a step or something.
I was hoping someone could explain to me how to purge everything and install the most appropriate Rom & Gapps pairing. I'm using CWM, btw.

JavaMac said:
Hey folks. I recently revived my 2012 Nexus 7 wifi. I thought it was toast, but I guess it just needed a nap. It was having Gapps problems last time I tried to flash, and this time around, I'm having the same issues. I've attempted to flash a few versions as well as flashing a few different roms. The roms flash fine, and they run very smooth, but Gapps constantly either fails to flash due to space concerns or even though it claims success, it doesn't load the services and I end up with a ton of errors and can't really work with the tablet. The computer itself obviously runs great, but I'm missing something, or need to take it back a step or something.
I was hoping someone could explain to me how to purge everything and install the most appropriate Rom & Gapps pairing. I'm using CWM, btw.
Click to expand...
Click to collapse
First of all CWM is ancient...
I do this when I feel like starting over.
(First flash TWRP, via fastboot if possible)
Format the partition /system, /data, /cache and Internal Storage (yes even that)
Then connect it to the computer, get on XDA and download CM13 or a ROM you like (I like CM13) and flash opengapps (pico, just google it)
I would suggest following the suggestions that the developer of the CM13 port to the Nexus 7 gave to fix the eMMC speed.
Installing Trimmer and setting it to daily is enough.
Good luck!

Can't get any version of CM to load

I am unlocked (it yells at me every time I power on...)
Flashed twrp-2.8.6.0-xt907, everything went fine
But after flashing any version of CM it either doesn't get past the unlocked bootloader warning (when I use cm-10.1.3-xt907 cm-11-20140104-SNAPSHOT-M2-xt907 or cm-10.2-20131102-SNAPSHOT-M1-xt907)
or it just shows the CM face with the white circle growing out over and over (if I use cm-12.1-20160523-NIGHTLY-xt907 or cm-12.1-20160530-NIGHTLY-xt907)
I've done the factory wipe a dozen times, even tried formatting at the partitions before installing. Wiping cache/davlik...nothing seems to help. Any advice?

bassgoonist said:
I am unlocked (it yells at me every time I power on...)
Flashed twrp-2.8.6.0-xt907, everything went fine
But after flashing any version of CM it either doesn't get past the unlocked bootloader warning (when I use cm-10.1.3-xt907 cm-11-20140104-SNAPSHOT-M2-xt907 or cm-10.2-20131102-SNAPSHOT-M1-xt907)
or it just shows the CM face with the white circle growing out over and over (if I use cm-12.1-20160523-NIGHTLY-xt907 or cm-12.1-20160530-NIGHTLY-xt907)
I've done the factory wipe a dozen times, even tried formatting at the partitions before installing. Wiping cache/davlik...nothing seems to help. Any advice?
Click to expand...
Click to collapse
I believe those are all built for the jellybean bootloader, did you downgrade, or still on KitKat?
Sent from my KFFOWI using XDA Labs

I must've missed that, thanks

sd_shadow said:
I believe those are all built for the jellybean bootloader, did you downgrade, or still on KitKat?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Hmm, the CM wiki is confusing me on this
https://wiki.cyanogenmod.org/w/Install_CM_for_xt907
Your device must be bootloader unlocked.
For CM 11.0, the device builds have been unified. Get the latest CM 11.0 build for KitKat bootloader updated devices here and for devices still on JellyBean bootloader here.
For CM 12.0 and newer, KitKat bootloader is required and builds were de-unified again. Get them under the usual xt907 builds.
Click to expand...
Click to collapse

I flashed the boot.img from VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip, but that didn't seem to help any.

bassgoonist said:
I flashed the boot.img from VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip, but that didn't seem to help any.
Click to expand...
Click to collapse
I didn't remember correctly,
cm11 and cm12 require the kitkat bootloader
where did you find the recovery?
should be a cm recovery on their site, could try that
Sent from my XT1060 using XDA Labs

bassgoonist said:
I am unlocked (it yells at me every time I power on...)
Flashed twrp-2.8.6.0-xt907, everything went fine
But after flashing any version of CM it either doesn't get past the unlocked bootloader warning (when I use cm-10.1.3-xt907 cm-11-20140104-SNAPSHOT-M2-xt907 or cm-10.2-20131102-SNAPSHOT-M1-xt907)
or it just shows the CM face with the white circle growing out over and over (if I use cm-12.1-20160523-NIGHTLY-xt907 or cm-12.1-20160530-NIGHTLY-xt907)
I've done the factory wipe a dozen times, even tried formatting at the partitions before installing. Wiping cache/davlik...nothing seems to help. Any advice?
Click to expand...
Click to collapse
Try This One
https://download.cyanogenmod.org/get/jenkins/90471/cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip

Any resolution?
I have the same problem as Bassgoonist. Wondering if you ever got it resolved?
I have xt907, rooted, unlocked via sunshine, KK bootloader. Installed twrp-2.8.6.0-xt907. Flashed cm-12.1-20160822-NIGHTLY-xt907 and it never gets past initial boot animation. I also tried the CM recovery which installed fine, but exhibited the same symptoms.
So, did msm8960.zip work? Should I just keep trying different nightlies?
Has anyone had this problem and gotten past it?

s1gma40 said:
I have the same problem as Bassgoonist. Wondering if you ever got it resolved?
I have xt907, rooted, unlocked via sunshine, KK bootloader. Installed twrp-2.8.6.0-xt907. Flashed cm-12.1-20160822-NIGHTLY-xt907 and it never gets past initial boot animation. I also tried the CM recovery which installed fine, but exhibited the same symptoms.
So, did msm8960.zip work? Should I just keep trying different nightlies?
Has anyone had this problem and gotten past it?
Click to expand...
Click to collapse
im having the same issue

Finally got it.
HideTheCookies said:
im having the same issue
Click to expand...
Click to collapse
((Sorry for the lack of links, I'm new here and the links aren't yet allowed for me. Hopefully you can cut and paste them.))
I was so close for so long. You know how you start going around in circles, and you think you've done everything, but maybe you forget a step? Yea.
I won't repeat everything I did, but here's the links I followed, they have explained it pretty good:
1st: forum.cyanogenmod.org/topic/117181-any-dev-is-intrested-in-unlocking-latest-kernel-of-razr-m
2nd: Well, I had to pay the 25$ for sunshine. But it was worth it: theroot.ninja
3rd: Follow this, but skip the first section on rooting, you've already done that: wiki.cyanogenmod.org/w/Install_CM_for_xt907
The thing that is missing in the last step, that I thought I had done, but not completely apparently, is this:
Just before you install the CM21 mod, you are in twrp and you've done your backup. The directions say "7.Select Wipe and then Factory Reset." Well that's not quite enough. INSTEAD you need to choose wipe, then choose the advanced option, and wipe every single thing except the sdcard. (Do it twice, why not? We'll teach those partitions to mess with us!)
Finish up with the install as the directions suggest and that should work. It worked for me on an xt907, starting from the 182.46.15 firmware version. The first boot does take several minutes.
Thanks to Cube Computer Channel on YouTube for having a great, long video that was full of information, of which I ultimately only needed the three second reminder/kick in the head that I need to wipe all partitions.
Good luck all!
S1gma40 out.