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

Verizon update vs Gummy - update or not?

Good to hear. Getting the Droid Eye is always a good sign, it means you're actually in the operating system as versus the Samsung Logo Screen that means it's trying to load it.
 
OK, system is updating off VZ.
Very good. You're more than half-way there.

Now, remember... this is going to take a long time to do. I'm not kidding. Some people have stated that the upgrade process can take as long as half an hour. Just keep watching the status bar go across the screen which should turn yellow as the progress continues.
 
Thanks ukfkoz for this thread and for asking those dumb questions I hate asking. I'm also running Gummycharged's Froyo, and have been pretty happy with it. Now I'm repeatedly getting this damned message about Verizon's update. On my rooted (Team Whiskey) Samsung Vibrant there was a setting I could use to turn off these updates -- apparently not for the Droid Charge from the Gummy team. Every time I've rooted a phone it's a lot of work, because I do it very seldomly.

So apparently first I have to Odin back to stock which I've never had to do before. Then I'll let Verizon dump me with their doubtlesslyloadedwithcrapware update, then I can go find a really good working Gingerbread (but not from Gummycharged as now they've dissolved). ... sigh. Nonetheless, I'm grateful for the 3rd party developers who do save us from the crapware that slows my phone to a crawl and sometimes prevents me from answering a call because the phone is so busy doing whatever else.
:(
 
Do what ukrkoz is doing. Follow the same instructions I've given to ukrkoz.

Get back to Stock EE4 which of course I've provided links to how to do so. Let it update to EP4D. Root it, which again I've provided easy to follow instructions to do so. Can download Titanium Backup to remove the apps which again, I've included a link to a list of apps you can safely remove to debloat your phone.
 
thank you for your desire to help and posts. it's downloading awright, afraid I am it'll fry the phone though, as with all I have done before, including special kernel for froyo - gummy is still there on the phone. it did not go away.
I'll let it load, I have to go away from computers for about 2 hrs. be back and report.

so, simply flashing with original stock rom via odin did not remove gummy, it's still there. oh so it appears.
 
First... follow these instructions.
http://www.toms-world.org/android/#flashStockEE4

Then follow these instructions to update to Gingerbread if your phone doesn't get the update automatically.
http://www.toms-world.org/android/#howToManuallyUpdateToGingerbread

Then, to root the phone, follow these instructions...
http://www.toms-world.org/android/#rootInstructions

And to debloat the phone...
http://www.toms-world.org/android/#safeToRemoveAppsToDebloatROM

Noticing a theme here? All of the information you need to do all of this is at one site.

trparky, I followed all of your instructions to a 'T', thanks for the info! I went back to stock EE4 unrooted, the OTA update installed and then I rooted and put Imoseyon's kernel on. I did all of the debloating and enabled lagfix again.

The only problem I'm having now is that the phone takes a lot longer to boot than before. Any ideas why?

Thanks!
 
You may have to do a factory reset once you're done loading the EE4 ROM.

The link at [ toms-world.org/android/#flashStockEE4 ]for the EE4 ROM returns an invalid link. Could you check that or perhaps identify which file on the download page would be correct?

I'm running 2.3.4 EP1F and want to get to the 2.3.6 EP4D.

Thanks
 
Yes, that's because I pulled the EE4 ODIN file. I'm only hosting the newer EP4D ODIN image, which is exactly the same version you'd get if you went back to EE4 and did the upgrade.

Essentially you'd be installing the Gingerbread version that you'd get from the upgrade but it would be a clean install. IMO, cleaner than an upgrade.
 
The only problem I'm having now is that the phone takes a lot longer to boot than before. Any ideas why?
It is said that Voodoo Kernels (such as iMoseyOn's kernel) does result in a longer boot because it's checking partition information. Nothing to be alarmed about.
 
Back
Top Bottom