• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [ROM][4.0.4] AOKP ICS B40/M6/Mods (7/8)

Well I'm going to do it from 23 to 24 then 24 to 25

According to the b25 release notes:

Wipe shouldn't be neccesary coming from build 23 or 24.

From:

Build 25

So flashing from 23 -> 25 should be fine, just wipe cache and dalvik only (I do those anytime I flash something since it only takes an extra minute or two to boot up and avoids some strange issues).
 
Other than the weird reboot when tapping accept for super user and droidsshd after the first boot of b25, it's been great since!

I broke down and bought TB pro, which made things much faster and smoother to upgrade which required a full wipe. :)
 
So a dirty flash looks like this:

Wipe Cache
Wipe data
Wipe davlik
Install Rom
Install Gapps
Install Kernal
Install theme (if you use one)

???

When I flash from compatible (in the sense a full wipe is not required), I have always done the following:

1. boot to CWM (or whatever custom recovery you use, which could change the wording of the rest of the steps, but it's the same idea)

2. wipe cache (this just formats the cache partition in cwm)

3. wipe dalvik (advanced -> wipe dalvik cache)

4. flash ROM

5. flash gapps

6. optionally flash a kernel or theme, etc

7. reboot and enjoy

No need to touch the data partition at all if you're going between compatible ROMs (e.g. AOKP b23 -> b25).
 
When I flash from compatible (in the sense a full wipe is not required), I have always done the following:

1. boot to CWM (or whatever custom recovery you use, which could change the wording of the rest of the steps, but it's the same idea)

2. wipe cache (this just formats the cache partition in cwm)

3. wipe dalvik (advanced -> wipe dalvik cache)

4. flash ROM

5. flash gapps

6. optionally flash a kernel or theme, etc

7. reboot and enjoy

No need to touch the data partition at all if you're going between compatible ROMs (e.g. AOKP b23 -> b25).


Correct except after you wipe Dalvik Cache go in to Mounts and Storage--> Format System. And some people precaution against flashing a kernel during the same reboot as when you flash the ROM. I do it every time. But people say you shouldn't, all up to you. Most people also say don't dirty flash, but we all do that don't we? :P

So step 4 is Format System (Mounts and Storage --> Format System) and then the rest is as you said.

You just have to decide whether you want to break up the other flashes in separate reboots.
 
Correct except after you wipe Dalvik Cache go in to Mounts and Storage--> Format System. And some people precaution against flashing a kernel during the same reboot as when you flash the ROM. I do it every time. But people say you shouldn't, all up to you. Most people also say don't dirty flash, but we all do that don't we? :P

So step 4 is Format System (Mounts and Storage --> Format System) and then the rest is as you said.

You just have to decide whether you want to break up the other flashes in separate reboots.

I don't think I have ever used format system. I think I remember seeing cwm automatically do that when flashing a ROM anyway. Maybe it used to be a necessary step, but perhaps not anymore.

As for flashing a kernel, yeah I've had no trouble doing it in the same session, but if you're paranoid, might be worth flashing the kernel in a separate reboot into recovery.
 
But that's like a factory reset, no?

No, it literally means it will format the /system partition, not the "entire system" :) So it's just an extra precautionary step to avoid stale files from a previous ROM.

E.g. suppose you had a ROM first with some file in /system/xbin, but flashed a new ROM and the file was left there and caused problems. Formatting the system partition would avoid that happening.

I'm fairly sure CWM does this implicitly, but I'll confirm with koush.

*edit* Ok, what I remembered was partially correct. The ROM's update script often formats system automatically (which is probably why I saw the message when flashing AOKP). Not all ROMs, do, though, so if the one you're flashing doesn't it's a good thing to remember to do (and can't hurt doing manually to be safe). :)
 
something is up with my phone. it was working fine yesterday and i let the battery die and now i cant get it to turn on. the phone is charged and it shows the charged button but i cant get it to boot in recovery or boot the phone up. not sure what to do as i am traveling right now. but boy im not happy.
 
something is up with my phone. it was working fine yesterday and i let the battery die and now i cant get it to turn on. the phone is charged and it shows the charged button but i cant get it to boot in recovery or boot the phone up. not sure what to do as i am traveling right now. but boy im not happy.

I've seen a few reports of that and what seems to be the best solution is to battery pull for 5-10 minutes.
 
I just did that and its still not working.

How is this possible? The state of the phone hasn't changed unless its hardware failure internally?

Could I take it back to verizon and swap it for a refurbished if they don't notice the root since they won't be able to boot it up either?
 
I just did that and its still not working.

How is this possible? The state of the phone hasn't changed unless its hardware failure internally?

Could I take it back to verizon and swap it for a refurbished if they don't notice the root since they won't be able to boot it up either?

So...you can't boot into recovery either with the volume buttons down along with the power button?

Have you tried it booting into recovery with the phone plugged in?
 
Yeah what happens is that the phones charged icon comes up and then it flashes to the battery full icon and then it doesn't do anything. This is with it plugged in. I remember last night having a few instances where my battery button wasn't working properly but other then that it was good and it kept working.

Really weird. What should I do?
 
Yeah what happens is that the phones charged icon comes up and then it flashes to the battery full icon and then it doesn't do anything. This is with it plugged in. I remember last night having a few instances where my battery button wasn't working properly but other then that it was good and it kept working.

Really weird. What should I do?


Certified Like New phone are shipped. I'm pretty sure they don't stock them in there store (or so I was told by VZW).

So you could call them, and have them ship you a replacement. They wouldn't be able to trouble-shoot it over the phone.



They'll send you a replacement, but I don't know if there are consequences when the phone get back to Samsung, and they are somehow able to determine the root status. VERY UNLIKELY.

But I would try this first...

How to unbrick your phone.

http://androidforums.com/verizon-galaxy-nexus-all-things-root/474570-how-all-things-root-samsung-galaxy-nexus.html#post3957198
 
So.....no wipe coming from 25?

So make a Nandroid, Flash 26, Flash new Gapps, Reboot..

That's it?

Will my settings and home screen layouts change?
 
So.....no wipe coming from 25?

So make a Nandroid, Flash 26, Flash new Gapps, Reboot..

That's it?

Will my settings and home screen layouts change?

Make nandroid, wipe cache, wipe dalvik, flash B26 & gapps then reboot.
You shouldn't lose anything in a dirty wipe. No guarantees but most of the time its ok
 
Back
Top Bottom