I installed serendipity 7, however, it looks like I'm affected by the suspend battery drain bug: code.google.com/p/android/issue/detail?id=11126 (aka 'Android OS' process uses high percentage of battery)
So back to 2.2 it is for me .. either cognition or serendipity 6.4. I assume I'll need to downgrade the bootloaders. Which version of Odin should I use and do I need to touch the filesystem at all?
thanks!
poolemit said:
I installed serendipity 7, however, it looks like I'm affected by the suspend battery drain bug: code.google.com/p/android/issues/detail?id=11126
So back to 2.2 it is for me .. either cognition or serendipity 6.4. I assume I'll need to downgrade the bootloaders. Which version of Odin should I use and do I need to touch the filesystem at all?
thanks!
Click to expand...
Click to collapse
You can use Icezers safe method to go back to stock (search). This will let you keep the gb boot loaders and you can use the latest cog or serendipity 6.4, no problems. Or odin one click back to stock, but you lose the gb boot loaders.
Sent from my Samsung Captivate using Tapatalk
I would just flash to stock ODIN then flash your 2.2 rom of choice. That's how I did it to go to gingerbread
88EVGAFTW said:
I would just flash to stock ODIN then flash your 2.2 rom of choice. That's how I did it to go to gingerbread
Click to expand...
Click to collapse
+1
just completed process myself
So are you saying that it would be unsafe to just flash back to 6.4? Cause I have VII and I was actually thinking of downgrading before but would that be dangerous?
One general rule across most ROM threads is to flash back to stock for a cleaner install. Probably not always necessary, but recommended. Using ODIN for JF6 only takes 5-10 minutes (on my machine anyway). I'd rather do that than the alternative, spend an hour or two trying to flash the right software to get it done.
How many of these "How do I flash back from Y to X ROM?" threads do we need? There must be a couple dozen of them in here.
There are many threads that show you how to flash back to 2.2. No need for another thread.
Related
All are recommended for beginners.
Cognition, Perception, Assonance.
Also, a lot of them tell you to flash back to JF6 stock.. Mine is JL1 rogers stock 2.2. do they mean I have to switch to what seems to be an ATT firmware thats 2.1 ? then upgrade ?
I thought flash re-writes everything ground up, so why flash an older then newer ?
distortionist said:
All are recommended for beginners.
Cognition, Perception, Assonance.
Also, a lot of them tell you to flash back to JF6 stock.. Mine is JL1 rogers stock 2.2. do they mean I have to switch to what seems to be an ATT firmware thats 2.1 ? then upgrade ?
I thought flash re-writes everything ground up, so why flash an older then newer ?
Click to expand...
Click to collapse
When anyone says to go to stock, it means to go to the stock firmware that ur phone came in.
These instructions should work from almost any ROM when flashing Apex 9.x, but I felt specific instructions were needed for CM7. If coming from something other than CM7, you should make sure that your filesystems are RFS before messing around with Odin.
Here is the thread for Apex: http://forum.xda-developers.com/showthread.php?t=952588
Thanks : Watsa, DesignGears, Atinm, Cezar', Shortfuse, and anyone else.
Files you need:
--Apex_9.1_JVR.zip - http://apexromcaptivate.weebly.com/apex-9x---jvr.html
--Apex Flasher.zip - http://apexromcaptivate.weebly.com/installation-instructions2.html
--I897UCJF6-final-OCD-REV0.zip - http://forum.xda-developers.com/showthread.php?t=731989
--efs-backup.tar.gz(Optional) - this should have been created either strait out of the box, or sometime before you started flashing custom ROMs. If you've gotten this far flashing ROMs and your IMEI isn't screwed up, then you should still backup- http://forum.xda-developers.com/showthread.php?t=859914
--I897UCKF1-bootloaders.zip - http://forum.xda-developers.com/showthread.php?t=1129821
--SuperOneClickv2.1.1-ShortFuse.zip - http://forum.xda-developers.com/showthread.php?t=803682
1. Starting with CM7nightly84 (on official 2.2 boot-loaders acquired from Kies Mini (pre-CM7 install)), I used DG's OCD Odin JF6 (NOT the 3-button-fix version) to get back to stock. CLOSE the OCD window after stock flash is done. I then placed Apex_9.1_JVR.zip on my internal sd card.
2. Then, I rooted 2.1 with Super One Click and restored my /EFS folder from the backup file using ADB. After restoring /EFS, I immediately reboot in download mode and reflash to stock again using the same Odin OCD (make sure you close the one you used to flash in step one and open a new instance of it and unplug and replugin usb between every flash or you might end up a saaad panda). This makes it as close to an "Out of Box" state as possible. I'm sure this step can be skipped if a backup isn't available. This is just something I always do between flashes.
3. I downloaded Cezar's KF1 boot-loaders OCD and followed the instructions provided in the thread about how to flash them. This had me end up with KF1 boot-loaders on an otherwise completely stock, unrooted, JF6. The KF1 boot-loaders should not affect 2.1 or 2.2 normal functioning.
4. Then, I extracted the Apex pre-flash package (Apex Flasher.zip) and followed the instructions as if the boot-loaders were already flashed. This got me on Dark Core 3 - JVR_C. Watsa confirms that the KF1 boot-loaders in the Apex Flasher.zip are the same as Cezar's that are in the forum listed above. The only reason I didn't use them is because flashed them on my own.
5. Ater all that is done, reboot to the white AT&T screen. I would recommend a battery pull or recovery key combo (vol+, vol-, & power) as soon as you see it because the DC3 kernel will try to apply Voodoo ext conversions with stock 2.1 still on there. Upon arrival at the recovery screen, chose the option to install zip and find Apex_9.1_JVR.zip .
All done. When it reboots, you'll hear that beautiful robotic voice of the lady converting your partitions. Sounds almost dirty, doesn't it?
If you don't hear anything, reboot into recovery and enable the options under the "voodoo" menu.
reserved...
Try using i9000 gb bootloaders on an i9000 gb rom
Captivate 2.3.4
Thegodfather156 said:
Try using i9000 gb bootloaders on an i9000 gb rom
Captivate 2.3.4
Click to expand...
Click to collapse
I setup this guide for anyone who wanted to use the KF1 boot-loaders specifically. Starting at CM7 nightly #78, emmc is now supported on gingerbread boot-loaders for the captivate. This means that after loading these you shouldn't have to change boot-loaders again if you wanted to go back to CM7 or switch to a new ROM. All of the I9000 based GB ROMs I have seen have reported no issues using KF1 booties. Some devs even recommend them to ensure hardware compatibility. They seem to work great with Froyo as well.
i am selling my phone and want to flash back to stock for the new owner so they can get updates. Right now im running KK4. Can I Use odin One Click back to 2.1 then let Kies update to 2.2 with out bootloader problems? Will Odin or kies change my gingerbread bootloaders. I dont know much about rules of bootloaders. Any help would be greatly appreciated and repped.
Thanks
I highly doubt There will be updates...
Stick with kk4.
Or you could just flash a 2.2 package and skip the kies step. Bootloaders are backwards compatible. Ginger boots work with earlier versions of Android.
I want to make sure kies updates just in case AT&T releases gingerbread for the captivate. Also im having battery drain problems with kk4.
hardly anyone ever gets keis to work after custom roms, and if you want 2.2 the odin flash 2.2. why odin flash 2.1 then upgrade? dont make no sense!
and when gingerbread does get released, it will be ALL OVER THIS PLACE!!! new Odin flashes, new roms, new source, new kernels, new theads.... MINUTES AFTER RELEASE. Waaaayyyyyy before you would notice by randomly checking with keis....
xda.
not keis.
The point is to get this phone truly stock so who ever buys it can get ota or keis updates if there happen to be any in the future.
[email protected] said:
The point is to get this phone truly stock so who ever buys it can get ota or keis updates if there happen to be any in the future.
Click to expand...
Click to collapse
Search for Stock KB2 by Adam Outler.
I just did this when I had to replace my cappy (power button wouldn't respond half the time). I flashed back to 2.1 with the one click from DG then used kies to update to 2.2 with no problem.
I like to recommend kb2 now because a lot of refurbs and later builds came with that build. Also, trying to flash a Froyo shipped device with JF6 well cause a bootloop. So, as a blanket statement I say use KB2.
Inherited a Droid Charge running GummyCharged 2.1 from my housemate.
I want to switch to Eclipse 2.0. I know in order to run FP1 builds, you need to run stock kernel if you want wifi. Except, I also noticed that the PBJ kernel recently fixed the wifi issue.
I'm under the impression you're told to revert to stock, run OTA update, then flash your FP1 ROM so you have the latest stock kernel.
Or is there more to it than the kernel?
I'd rather skip the revert/flash/etc/etc, I updated to the latest CWM, made a backup, factory restored, wiped cache/dalvik, flashed ROM, flashed kernel, rebooted, everything seems fine (wifi working no issues). But... that doesn't mean that it is.
EDIT: Yeah, my baseband in About Phone shows i510.06 V.EE4 SCH-I510.EE1, which is what it was before. Can I get just the baseband?
Thanks!
By the way, I don't care about carrier signal at all, this phone got wet and no longer accepts SIM cards. The other functions still work, so I'm using it on wifi and I'm trying to re-purpose the device to be a portable offline GPS for hiking. But I did read that FP1 gets better GPS locks, which is part of why I want to run it.
U cant get the fp1 upgrade on a cstom rom. U have to go back to stock n get the ota upgrade. I suggest usin titanium to back up ur stuff then flash what u want. Stock fp1 or pjb 5/24 r both good, but u gta get back to factory first.
Sent from my SCH-I510 using XDA
Actually, I figured "what you do do well" and I decided to follow the suggested directions. I used ODIN, restored to stock EP4... and couldn't get past the main screen. Can't read SIM cards, so can't get past the activate screen. I then flashed back an FP1 rom, the latest PBJ kernel, and [attempted] to use the EP4 to FP1 patch, which hung and failed.
It looks like if I want to get my baseband to FP1, I'll have to jump through hoops (maybe flashing a stock EP4 pre-rooted ROM from ODIN? maybe?) Regardless, since the CDMA antenna in this thing is useless anyway, I'm just gonna skip it.
Thank you for your reply!
Well, now that you have borked your phone a bit, go and download the EP4 ODIN package and flash it (in ODIN or SamsungPST). Might not be a bad idea to flash the PIT while you're at it. You'll probably have to flash CWM, and then PBJ from within CWM (stock kernel overwrites it) Then go and try flashing your ROM of choice again (cough *tweaked* cough), either in ODIN (with the respective package) or CWM. (again with the proper package).
http://www.imnuts.org/odin-packages/
Sent from my SCH-I510 using xda premium
thanks kvswim, that's pretty much exactly what I did yesterday. I'm even running Tweaked 2.1
It's too bad, I really prefer the theme of Eclipse, but I just couldn't handle the lack of TSM Parts.
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
kintwofan said:
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Click to expand...
Click to collapse
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
xsteven77x said:
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well of course you can use it to just go back to stock, but the average user only does it when they mess up. I do agree though I personally even I find my daily driver like to start fresh then flash the keeper ROM.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Have been rooted since day of pre-order delivery. Have flashed multiple ICS/JB TW roms. I stay away from AOKP/CM roms just because of loss of features so can't report on those. I have never lost wifi or GPS. Never had sim card error. Had no problems with TWRP and haven't used CWM since worked with Koush on Tbolt problems. We worked those out and I still run CWM touch on Tbolt. Used Amon on Rezound. Recoveries are what you feel comfortable with. I use whatever works best for the device although that is irrelevant to this subject. I still use the old school clean wipe of data/cache/dalvic cache/system for all flashes on all devices and all recoveries. Ultimately have never had a reason to use Odin or go back to stock since initial root. Only bugs I have seen are rom related and nandroid back to working rom fixed it. There are differing opinions on what I have just posted but I have had no problems with flashing anything on my last 3 devices and have never bricked a phone even though I may flash 10 times a day for multiple devs on multiple devices. Maybe the old school recovery devs were on to something. Beats me.
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
takota6 said:
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
Click to expand...
Click to collapse
Yes you can but they all have killer batter life. No need to Odin you can flash it in recovery. Only have to Odin stock RUU to get firmware update. If you do it could loose root and ability to unlock boot loader. You will have it as long as you keep it. As soon as you flash another rom it will wipe that one and you will be on the base that the rom is based on. This is why the devs update to latest bases whether they be leaks or official. Best you can do is flash newer radios and kernels unless the ROM Gods tell us to update firmware and then it will be checked and deemed safe. Never Odin/flash an OTA/leak unless it has been cleared by the Android Gods. I have only used Odin once and that was because that was only way to root on original pre-order. :laugh:
be sure to back up internal sd card
takota6 said:
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
Click to expand...
Click to collapse
Don't forget to back up internal sd card. Odin will wipe it when you flash.