2nd try using Custom ROMS

dancing-bass

Well-known member
Jan 3, 2011
1,022
17
0
Visit site
Gonna have a crack at a ROM. randomly flipped through a few at XDA, and saw "SlimICS 3.7" Simple, clean, fast. Some Google support already baked in. Hoping to figure out the rest myself. So I'm gonna grab the zip, throw it on, and probably go crash for the night. See if I have a phone or a smoking heap of rubble in the morning :p

(titanium backup already done, don't know if its overkill or proper proceedure but I'll back up with CWM as well, just in case...)
 

Andrew Martonik

Well-known member
Aug 12, 2011
1,610
143
0
Visit site
I wouldn't recommend just selecting a zip then walking away. The phone will finish flashing the zip but just sit at the recovery screen afterwards...

actually sit there and wait for it to finish, do your reboots, etc. and make sure it works.
 

dancing-bass

Well-known member
Jan 3, 2011
1,022
17
0
Visit site
Well I think I did something wrong.... Not sure, but either that or I got a bad copy of the ROM.

copied it to the virtual SD card in the root directory. Booted into recovery, and made a backup of my current setup (stock ICS, with 3rd party launcher). Cleared Cache, cleared Delvic and rebooted. After it came back up, I booted back into recovery. Selected the SlimICS from the SD card and installed it. (it showed it as installing). Rebooted the system.... and waited. After about 5 minutes it was still showing the animated boot screen.... so I went out for a smoke. And came back to it STILL showing boot animation.

So I pulled the battery, booted back into recovery, and restored my backup.

Any ideas folks? (I think I ran into this during my first attempt at running a ROM). Almost identical procedure I used to swap a baseband yesterday, and that went well....

**edit** the boot animation I get appears to be the stock ICS animation. I don't know if SlimICS uses the same animation or a different one. Maybe this additional info will help someone guide me?

Playing around with ROMS is just a hobby. Sounds fun anyway, if I Could get something to actually run! :-\
 
Last edited:

dmmarck

Retired Moderator
Dec 28, 2011
8,349
2,594
0
Visit site
Well I think I did something wrong.... Not sure, but either that or I got a bad copy of the ROM.

copied it to the virtual SD card in the root directory. Booted into recovery, and made a backup of my current setup (stock ICS, with 3rd party launcher). Cleared Cache, cleared Delvic and rebooted. After it came back up, I booted back into recovery. Selected the SlimICS from the SD card and installed it. (it showed it as installing). Rebooted the system.... and waited. After about 5 minutes it was still showing the animated boot screen.... so I went out for a smoke. And came back to it STILL showing boot animation.

So I pulled the battery, booted back into recovery, and restored my backup.

Any ideas folks? (I think I ran into this during my first attempt at running a ROM). Almost identical procedure I used to swap a baseband yesterday, and that went well....

**edit** the boot animation I get appears to be the stock ICS animation. I don't know if SlimICS uses the same animation or a different one. Maybe this additional info will help someone guide me?

Playing around with ROMS is just a hobby. Sounds fun anyway, if I Could get something to actually run! :-\

Did you try wiping data/factory reset? You need to do that when going from rom to different rom or even stock to different rom.

Your steps should be as follows:

[INFO]
  1. Place rom on the virtual SDcard
  2. Reboot into recovery
  3. Wipe cache/dalvik, then make a nandroid
  4. Do your wipes again, but this time with the data wipe first, then cache/dalvik
  5. Formatting system doesn't hurt either!
  6. Install the rom's zip
  7. Install the GAPPs zip, if applicable
  8. Reboot, sign in, let market restore or TiBu do its thang
[/INFO]

Note - I usually wipe cache/dalvik before making a nandroid b/c it's (1) a "cleaner" nandroid, and (2) a tad quicker.
 

dancing-bass

Well-known member
Jan 3, 2011
1,022
17
0
Visit site
Well, I managed to get a ROM running (AOKP Milestone 5). Combined with a 2000mAh battery, and things are running nice.

Social sites (Facebook, Twitter, G+) and Weather updating hourly. I use Wifi when I can (which is pretty much whenever I'm at home), and work is a steel frame, tin-sided shop in an area with weak signal -- needless to say it hurts the battery a bit.

Anyway, here's a screenshot of my battery life (which seems to have settled in with this as an average)
 

dancing-bass

Well-known member
Jan 3, 2011
1,022
17
0
Visit site
I didn't swap kernels or basebands, so whatever came packaged with the ROM is what I'm running. I may swap those out this weekend. Thanks for the heads-up about the kernel. I'll give it a shot!

Sent from my Galaxy Nexus using Android Central Forums
 

dmmarck

Retired Moderator
Dec 28, 2011
8,349
2,594
0
Visit site
Recovery = seemless. ROM Manager is still an app, so it can cause issues. I prefer doing it in recovery 100%.

As for order, you can install them in any order. I prefer going radios first, then the rom, then gapps.
 

dancing-bass

Well-known member
Jan 3, 2011
1,022
17
0
Visit site
Now I'm gonna go all in.

Latest ROM from AOKP (build 37), franco Kernel, swap basebands....
Hope I don't break anything :)

dmmark, I'm gonna follow your steps just to be sure. (After flashing the ROM, does it matter if I do the kernel first or the radio first? I would thing ROM, then Kernel, then basebands....

****edit**** is there advantages one way or the other of flashing ROMS via recovery (after reboot) vs ROM manager from the app menu? I'm a little fuzzy on this stuff in some areas, so for now I've been doing EVERYTHING (backups and all) via Recovery. Is this way "better" or is it "better" to do it from ROM Manager? (I would think Recovery is best... but I've been wrong before so I figured I'd ask!)
 
Last edited: