tried rooting, stuck in boot loop-HELP

[cupfulloflol]

this aokp 40 rom is pretty buggy lol. i want to try that cyanogen one

What sort of problems are you having? Perhaps there are simple fixes for the problems.

CyanogenMod Downloads <-- you can get the CM9 RC from there, the same GApps from AOKP should work with CM9. Toro = VZW Galaxy Nexus.

There are also numerous kangs of CM9 floating around with various changes to them. There are 2 here, Winner's CM9 kang (he has been away for a bit I believe as he hasn't updated in a while), then there is ParanoidAndroid which is a CM9 kang + ability to change the DPI per app making apps tablet mode. There are a few other unofficial ports out there as well.

 

[sbenson]

this aokp 40 rom is pretty buggy lol. i want to try that cyanogen one

Seriously? What bugs do you think you've found? The only serious bug for Toro is the Google Voice bug, and that will be fixed in Build 41. Other than that, this ROM is nearly flawless.

 

[GalaxyFlatulence]

Seriously? What bugs do you think you've found? The only serious bug for Toro is the Google Voice bug, and that will be fixed in Build 41. Other than that, this ROM is nearly flawless.

stock aps crashing, freezing, reboots, error mssge "aokp stopped unexpectedly", widgets in the dock disappearing then coming back, unable to move apps sometimes by holding on to them sends the phone into landscape mode, etc.


i want that cyanogen one anyway, so i guess it doesn't matter

 

[GalaxyFlatulence]

What sort of problems are you having? Perhaps there are simple fixes for the problems.

CyanogenMod Downloads <-- you can get the CM9 RC from there, the same GApps from AOKP should work with CM9. Toro = VZW Galaxy Nexus.

There are also numerous kangs of CM9 floating around with various changes to them. There are 2 here, Winner's CM9 kang (he has been away for a bit I believe as he hasn't updated in a while), then there is ParanoidAndroid which is a CM9 kang + ability to change the DPI per app making apps tablet mode. There are a few other unofficial ports out there as well.

thank you! so i download it on my phone, and boot that room through the recovery screen again? how do you change a kernel, i want that franco one

 

[syndicate0017]

thank you! so i download it on my phone, and boot that room through the recovery screen again? how do you change a kernel, i want that franco one

Yes. You flash all ROMs the same way unless specifically stated otherwise. You wipe data/cache, flash the ROM zip and then the gapps zip. You can flash a kernel without wiping anything.

Sent from my Galaxy Nexus using Tapatalk 2

 

[cupfulloflol]

stock aps crashing, freezing, reboots, error mssge "aokp stopped unexpectedly", widgets in the dock disappearing then coming back, unable to move apps sometimes by holding on to them sends the phone into landscape mode, etc.

This shouldn't happen. A few quick guesses here as to what the problem could be:
- You didn't wipe properly prior to installation.

- You restored something that you probably shouldn't have (like system data via titanium backup).

- You changed some settings that your device didn't like. For example some kernel settings, going too low with undervolting, or overclocking too high.

- Bad download, or bad install. Both of these are fairly unlikely, but I have seen reported cases of both.

- Installed something on the ROM that wasn't designed for that ROM.

Probably a few others I am not thinking of right now.

Don't misconstrue my post to make it seem like I am trying to deter you from trying other ROMs. I am all for folks experimenting and finding the ROM that works best for them, I actually encourage folks to try as many ROMs as they have time to try. I am just trying to help figure out what went wrong, as that isn't typical behavior of any ROM, much less one of the more popular ones in AOKP. It wouldn't be cool for you to have your next ROM have problems too, then you think all custom ROMs suck sorta thing.

 

[sbenson]

This shouldn't happen. A few quick guesses here as to what the problem could be:
- You didn't wipe properly prior to installation.

- You restored something that you probably shouldn't have (like system data via titanium backup).

- You changed some settings that your device didn't like. For example some kernel settings, going too low with undervolting, or overclocking too high.

- Bad download, or bad install. Both of these are fairly unlikely, but I have seen reported cases of both.

- Installed something on the ROM that wasn't designed for that ROM.

Probably a few others I am not thinking of right now.

Don't misconstrue my post to make it seem like I am trying to deter you from trying other ROMs. I am all for folks experimenting and finding the ROM that works best for them, I actually encourage folks to try as many ROMs as they have time to try. I am just trying to help figure out what went wrong, as that isn't typical behavior of any ROM, much less one of the more popular ones in AOKP. It wouldn't be cool for you to have your next ROM have problems too, then you think all custom ROMs suck sorta thing.

Exactly, this. I would assume that since you're essentially flying by the seat of your pants with rooting and romming, you probably botched something along the way.

Sent from my Xoom using Tapatalk 2

 

[rjcapp]

Is this for real? I mean come on this seems way too bazaar to be true........

 

[sbenson]

Is this for real? I mean come on this seems way too bazaar to be true........

I know right?

Sent from my Galaxy Nexus using Tapatalk 2

 

[GalaxyFlatulence]

This shouldn't happen. A few quick guesses here as to what the problem could be:
- You didn't wipe properly prior to installation.

- You restored something that you probably shouldn't have (like system data via titanium backup).

- You changed some settings that your device didn't like. For example some kernel settings, going too low with undervolting, or overclocking too high.

- Bad download, or bad install. Both of these are fairly unlikely, but I have seen reported cases of both.

- Installed something on the ROM that wasn't designed for that ROM.

Probably a few others I am not thinking of right now.

Don't misconstrue my post to make it seem like I am trying to deter you from trying other ROMs. I am all for folks experimenting and finding the ROM that works best for them, I actually encourage folks to try as many ROMs as they have time to try. I am just trying to help figure out what went wrong, as that isn't typical behavior of any ROM, much less one of the more popular ones in AOKP. It wouldn't be cool for you to have your next ROM have problems too, then you think all custom ROMs suck sorta thing.

Exactly, this. I would assume that since you're essentially flying by the seat of your pants with rooting and romming, you probably botched something along the way.

Sent from my Xoom using Tapatalk 2

hmm out of those, i think not wiping properly prior to installation is the one. i didn't install anything on the rom, or change any processor/volt settings.

 

[GalaxyFlatulence]

wow, cyanogen rom is far less buggy. i tried both again (wiping data&cache), the aokp 40 has far more features, but is way too buggy (even aafter a proper wipe).. maybe it's a bad download

 

[cupfulloflol]

hmm out of those, i think not wiping properly prior to installation is the one. i didn't install anything on the rom, or change any processor/volt settings.

Yeah that would do it. Not wiping can cause some wacky things to happen, especially when changing between two different ROMs. Minor updates, perhaps going from AOKP 40 to AOKP 41 for example, you may be ok with not wiping (wiping would still be recommended). But going from stock to AOKP would almost certainly require a wipe. And going from AOKP to CM9 would require a wipe as well.

There are many different things you can backup and restore, to make wiping a little less painless. Especially if this is something that you plan on doing often.

Titanium backup - Backup and restores apps, among many other things. Don't restore anything system though. There are alternative apps for TiBu, but to be honest it is the only one I have any experience with.

Alternative homes - Like Nova, Apex, ADW, GO.... many others offer options to save your screen setup and restore.

SMS backup - You can back up your text messages with various apps, some of the alternative SMS clients even allow this if you are user of one of those.

ROM settings backup - There are some ROMs with built in backup options, for their ROM Control settings. AOKP has an app on the market ( https://play.google.com/store/apps/details?id=com.aokp.backup ). Kernel side there are some options here as well (not backing up the kernel, but the kernel settings).

Probably missed quite a few other things that can help backup/restore. All of this is in excess to the Nandroid backup you make in recovery, it is still recommended you do that....then these are the less necessary ones.

 

[syndicate0017]

wow, cyanogen rom is far less buggy. i tried both again (wiping data&cache), the aokp has far more features, but is way too buggy (even aafter a proper wipe).. maybe it's a bad download

The ROM isn't buggy, it may just not play nice on your phone. I could never run DroidTheory's ROMs. Lag central. Everyone else loved them. Just like kernels, ROMs are very phone-dependent.

 

[GalaxyFlatulence]

how do i delete extra roms that i don't want? they no longer show up under downloads after the factory wipe, and i can't figure out how to do it in the recovery screen thans

i have a gummy one i want to get rid of, doesn't work

 

[tgyberg]

how do i delete extra roms that i don't want? they no longer show up under downloads after the factory wipe, and i can't figure out how to do it in the recovery screen thans

i have a gummy one i want to get rid of, doesn't work

You can just leave those rom zips or grab root explorer and delete them from your sd card.