Ok this morning i found out the official Froyo OTA was just released. I was running 2.1 EA28. I attempted the official OTA manual update, but kept on getting that stupid message, so I reflashed my phone to dl01 via Odin so i could do the OTA but failed, Then i reflashed my phone again to a newer build the dl09 and attempted the OTA and still failed. So i attempted the sd card method in safe mode, first using the ea28 update zip file, couldn't even do that. On all the methods i get stuck on my unpacking screen on my phone about 30% on "updating modem". Now im stuck on the dl09. If anyone has any suggestions please let me know, i've been at this, this whole morning and mid afternoon and losing my patience! All i want is to run Froyo on this stupid phone, but there are so many freakin problems!
try files from here, sometimes these phones are picky.
http://http://forum.xda-developers.com/showthread.php?t=1026746
Related
So...
Let me start off by saying I've been doing a lot of searching and reading already and pretty confused.
I've been playing around with my Vbirant trying to install the Voodoo Lag fix. Currently I'm running stock rooted JI6. Every time I install the voodoo lag fix, I get stuck at the Vibrant screen. Had to odin Eugene's Froyo that doesn't brick then odin back to stock. Tried this multiple times and kept getting stuck at the Vibrant screen.
Finally, tonight I tried going back to the original JFD and was able to apply the voodoo lag fix.
What I'm trying to figure out is how to apply the voodoo lag fix specificially to a stock JI6 build. Can someone tell me what the heck I'm doing wrong? I've verified that I don't have the larger NAND.
Below are some of the links that I've used for reference. Thanks for your help!
http://forum.xda-developers.com/showthread.php?t=791478
http://forum.xda-developers.com/showpost.php?p=8322865&postcount=131
http://androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/
Are you actually applying the correct voodoo.zip file for your phone version? Try renaming it update.zip and reinstalling packages in recovery, that might work.
Thanks Bobbbb. I've tried both 3.0 and beta4 specifically for the Vibrant. Renamed both to update.zip and put it on root of the internal SD, rebooted into recovery and did a re-install packages. Get "Linda's" voice, all 3 steps, and then it's just stuck at the vibrant screen. Let it sit there for 20-30 minutes and finally gave up. This was all for stock JI6.
For stock JFD, it only took maybe 10 minutes for the whole process.
Woke up this morning to a new update, and hit install. My phone is now stuck on the screen with Andy and the caution sign. What do? I was running Gingerblur v2.something, which after doing some Googling, sounds like I should have removed before updating. Whoops.
You can do a battery pull to abort the installation, won't harm anything. But you are right, you will not be able to update to 1.83 with and mods on the phone. Being rooted won't stop the update, but changes beyond that will cause it to fail. You will need to flash either the 1.26 sbf, or possibly the 1.57 but I don't really know as I haven't used it, to restore the needed system files before updating to 1.83. Browse the forums as there are many posts already detailing how to get the update if you have mods installed.
So i tried updating to the latest update ED04 and once it downloaded and restarted and installed it got caught in a loop where it would not get past the Samsung logo. ODINed back to DL09 and now trying to update to EA28 to get back to the update before ED04 but it keeps hanging up at updating modem and restarts and says "UPDATE FAILED or INCOMPLETE. reason: IP_PREVIOUS_UPDATE_FAILED." anyway of getting it to update.
Follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1097355
After Odin-ing to DL09, flash the EA28 modem delta in CWM, not Odin.
Another Fascinating post by my XDA app...
Will that screw up any future OTA updates.
Which DL09 file did you use when you ODIN'd? Make sure you use this one:
http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
Changing your modems should not affect your ability to receive OTAs unless you change to a non official modem like EB01 or EC01. Missing verizon and samsung apps and programs will affect your ability to receive OTAs
Keep in mind it is only the modem so I would think OTAs may get screwy if the build isn't the same (ex DL09 with ED04 Modem) and it tries to update both. If you flash a stock build that is the same as the modem I would expect it to work fine. If you are going to end up using a non stock ROM then it won't really matter anyways.
Well what happened is i had this problem a few months ago trying to go from DL09 to EA28 and verizon sent me a phone with EA28 on it well OTA'ed up to the ED01 Froyo update and rooted but forgot to unroot before update and got caught in a reboot loop. now im trying to get back to froyo. is the EA28 modem screwing it up if i go back to CI500_VZW_DL09_ECLAIR and try to update back to EA28.
I would think you could just OTA all of them after flashing DL09.
Or you could follow this link to do the modems-Modems, and flash which ever rom you want ED01, ComRom, Evil Fascination, etc.
Guys I'm new to the forum but have been messing around with custom pseudo-roms for the Atrix for a little while now. I was running Adeo, then Gingerblur, then Greyblur all without a hitch when I heard about the new OTA update coming to the phone and Gingerbread coming up, so I wanted to go back to any build that would allow me to get the HSUPA update as well as the gingerbread update, but when I went to flash my phone to sbf using rsdlite, it said internal programming fail and nothing else happened. I installed gingerblur over greyblur in an attempt to see if it would flash, but nothing. Have done a factory data wipe, still can't flash. I can't even get into the stock Android Recovery, all that comes up is a triangle and exclamation point. Could someone please help me out here, I'm running gingerblur on a rooted Atrix on 1.5.7 and cannot get it to flash sbf, all I want to do is go back to stock att rom for the coming updates.
Thanks,
BK
Hey,
I have the same exact set up as you. It seems vague in your post if you re-flashed back to 1.26, and that may be why you're getting errors? Every time I update roms, I re-flash to 1.26 using the method in the link below.
http://forum.xda-developers.com/showthread.php?t=991072
Then I ran Gladroot to unlock, enable sideloading, etc.
http://forum.xda-developers.com/showthread.php?t=1016060
Downloaded and install the 1.83 update online (not on-air because I didn't get prompted)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I ran the 'afterupdate.bat' on Gladroot after installing the update.
And I now have 2.2.2 / 1.8.3
Thanks bud, what I ended up doing was trying to manually uninstall gingerblur and greyblur and the adeo rom by using scripts etc but it never worked. My phone started acting weird, the home button stopped working, no 3g connectivity, it would say I have superuser but it wouldn't be rooted... something was seriously messed up. I tried to get into the stock android recovery but it wouldn't boot, I think something was corrupted. I knew sbf files rewrite system and boot data, so I went into tenfar's custom recovery (after rooting for the 10th time) and deleted system and boot data, system data was deleted, but boot data had an error. I wiped the caches and all and I tried to sbf flash to 1.8.3 but nothing and the phone bricked. I then tried it on another computer with more memory than mine (mine was running kind of low because of a linux partition) and the flash worked and I'm on 1.8.3. I think I'll wait for official gingerbread and unlocked bootloader in July before I mess with my phone again.
I have the AT&T SGS2. I had installed a few custom software a few months ago, but then I installed a stock 2.3.4 for the AT&T phone. The custom binary count is 1 on the recovery screen.
To upgrade to the official ICS from AT&T, I installed the latest KIES. It successfully detects the firmware update for the device. KIES starts installing and everything goes fine until almost very end. At 91%, installation fails giving the error message something like "Unexpected error. Firmware upgrade encountered an issue. please select recovery mode in kies & try again". I tried several times and same thing happens again. I also tried downloading the stock ICS and install it via ODIN, but same thing happened. It failed at the very end.
What could be happening here? Any advice? Can it be anything to do with the custom binary count? Thanks in advance...
Not sure what might be intefering with kies or Odin. Where did you get the tar that you flashed that failed?
You might try again, with the UCLE5 Stock ICS plus Root tar from the Development forum.