Database Users

[Q] CM7 Nightlies Not Flashing

There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.

hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.

Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.

Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.

Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk

ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA

ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA

Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239

hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.

janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

Issues with running any custom ROM

Hello guys,
I wonder if somebody can help me. I bought a new Nexus 7 few days ago. As usual like with any other new device, I unlocked and rooted the device with the nexus root toolkit. After that I flashed via recovery a custom ROM. Everything worked fine, but after few hours, I wanted to try another rom, so I rebooted into recovery and the mistake I made was, that i wiped the inernal storage instead of cache. I was not able to get the custom ROM to the internal storage and the ROM was deleted, so the only option to bring the tablet to work was flashing original ROM via the toolkit or fastboot. Now I'm running on the original ROM, because when I try to flash any custom ROM, the insallation finishes fine, the tablet restarts and it gets stuck on the bootanimation.
I already tried 3 different ROMs, but the problem still persists and I have always to flash back the original ROM to get the tablet working.
Does anybody know, how to solve this problem? I really want to have a custom ROM running.
I appriciate your help!
Thanks for any ideas!
Sent from my Nexus 7 using xda app-developers app

Re download the rom of your choice to the tablet. Goo manager is my preferred method Keeps from adb push to the device...
Then Boot into recovery.. TWRP is what i use..
Wipe dalvik cache and system...
you can also in twrp .. copy your rom to usb/sd media boot into twrp with a connected usb media.. do full wipe and flash the rom from usb storage.. Great for those who have issues with internal storage. This way you can wipe it as well...
Good Luck....

Hello Erica, of course iI didit this way. As I wrote, I tried 3 different ROMs and the problem is always the same. I stucks on bootanimation.
First time I flashed custom ROM without any problems, but after flashing original ROM via the root toolkit, I am not able to get any custom ROM running.
Sent from my Nexus 7 using xda app-developers app

Wipe caches and if it gets s stuck at the boot screen sometimes you just have to turn it off for a bit and try turning it on in a couple minutes

sunman277 said:
Wipe caches and if it gets s stuck at the boot screen sometimes you just have to turn it off for a bit and try turning it on in a couple minutes
Click to expand...
Click to collapse
did you flash a custom kernel? you are not suppose to before the first boot

Sunmann, I will try.
billchen, In the custom ROMs I tried was always a custom kernel. So it flashed kernel as well.
Sent from my Nexus 7 using xda app-developers app

Hello guys, I'm back again. It still doesn't work flashing any of the custom ROMs. Does anyone, please, have any other idea, what could cause the problem?
Thanks a lot!

Using TWRP to install ClockworkMod

I am using TWRP 2.3.1.0 and no matter what ROM I flash with it the system gets stuck on the Acer logo. I had ClockworkMod before and it worked fine most of the time. The reason I switched was because the latest 4.2 ROMs didn't work with ClockworkMod. I switched to TWRP using the Acer recovery installer app. Then I did a full wipe without doing a backup (the ROM that I had there before wasn't that stable so I didn't bother). Then I tried installing a couple of CM10 ROMs using TWRP. The ROMs actually went hrough the install process fine, but every single one I've tried so far with TWRP gets stuck on the Acer logo. Then I went back and tried 4.1 and even 3.x ROMs and they all install, but can't get past the Acer logo. Is there an easy way to use TWRP to go back to ClockworkMod so I can get something installed and get past the Acer logo? Thank you in advance for your help.

See this post m8 http://forum.xda-developers.com/showthread.php?p=37255618
And the following post re wiping cache, actually, try wiping cache first...may not work like we want seeing you've flashed different ROMs but u never know
Sent from my GT-I9300 using Tapatalk 2

dibb_nz said:
See this post m8 http://forum.xda-developers.com/showthread.php?p=37255618
And the following post re wiping cache, actually, try wiping cache first...may not work like we want seeing you've flashed different ROMs but u never know
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I tried doing that and it makes no difference. I am not sure why TWRP doesn't work for me, but if I could use it to get ClockWorkMod back I think I'd be ok

What ROM were you running when u changed recovery to twrp...
What do u see using pwr/vol+ buttons?
Without the unlocked bootloader v8 you won't be able to flash any ICS/Jb ROMs or change recovery...
Sent from my GT-I9300 using Tapatalk 2

[Q] Flashing gets stuck at Cyanogen boot screen, Still able to recover.

Hey folks. I'm trying to flash Cyanogenmod to my Nexus 7 running 4.2.1. I am rooted and unlocked. I downloaded the nightly 10.1 as well as the stable 10.0 along with Gapps. Flashing both with Clockworkmod recovery gets me stuck in a bootloop with both options, forcing me to restore to my backup.
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup. I'm wondering if I should restore to factory on my current first? Am I missing any steps in this process? I'd like to be able to just tap and install if possible. I had bad experiences with flashing when I had my Galaxy Captivate.
I appreciate any help with this. I have gone through several forums and threads, but none seem to be device or situation specific so I thought I would bring up this specific situation. Thanks for any help.

JavaMac said:
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup..
Click to expand...
Click to collapse
You left out the "how you flashed" part. If you were using something such as ROM Manager, it may have wiped for you. But typically, for manual flashing from the recovery you need to do a "factory reset" procedure prior to installing a new rom. (A wipe which erases everything in /data except what is /data/media)
I've used a CM10.1 nightly and sequentially flashing the gapps, no troubles. Perhaps different versions though, the devil is always in the details.

I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.

JavaMac said:
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
Click to expand...
Click to collapse
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?

JavaMac said:
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
Click to expand...
Click to collapse
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD

Pirateghost said:
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Success! TY.