[Q] Flash Cognition from JH7? - Captivate General

I'm thoroughly tired of waiting for the official Froyo update from AT&T; so I'm seriously considering flashing Cognition 2.3b6...
HOWEVER I'm on JH7 - the documentation recommends downgrading to JF6, which I have no interest in doing (furthermore, I don't have easy access to a Windows machine or Odin...)
So my question is: Is it possible to go from JH7 directly to Cognition 2.3? Or am I risking bricking my phone? I haven't seen any other threads related to JH7 and Cognition.

You can flash from JH7 to Cognition 2.3b6 without incident. I've done it a few times.

Awesome. Thanks!
Hate to thread-jack my own thread, but...
Now how about downgrading? From Cognition I imagine I'll have to get back to JH7 if I want to follow AT&T's official Froyo update when it (finally) comes out. Any threads on how to go from Cognition back to a stock image?
Thanks again

tomstrummer said:
Awesome. Thanks!
Hate to thread-jack my own thread, but...
Now how about downgrading? From Cognition I imagine I'll have to get back to JH7 if I want to follow AT&T's official Froyo update when it (finally) comes out. Any threads on how to go from Cognition back to a stock image?
Thanks again
Click to expand...
Click to collapse
You won't have a reason to want the official Froyo update
But just in case http://forum.xda-developers.com/showthread.php?t=731989

It worked!
Thanks again! Everything worked fine from JH7.
I suppose if I wanted to downgrade to JH7 I could do a nandroid restore. But I have to agree, if I don't find any problems with Cognition there will be little reason to switch.

tomstrummer said:
Thanks again! Everything worked fine from JH7.
I suppose if I wanted to downgrade to JH7 I could do a nandroid restore. But I have to agree, if I don't find any problems with Cognition there will be little reason to switch.
Click to expand...
Click to collapse
Nandroid if you can otherwise one click back to JF6 and then Mini Kies to JH7. Unless Froyo is .....nm!

Related

[ROM]Fission Vanilla 2.1 Gone Gold - 11-12-2010 - True AOSP Experience

all ROM info can be found HERE
Reserved
Just holding a parking spot...
Reserved II
I am the jerk who takes two spots with his/her car...
What keyboard does this have? And does the D2 multitouch keyboard still work?
ok, let me get this straight. will i be able to SBF with the 2.2 SBF file that was leaked about 2 weeks ago?
Can I flash this over Fission 1.2.1?
Sent from my DROID2 using XDA App
firestrife23 said:
Can I flash this over Fission 1.2.1?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes, though it's still recommended that you wipe system
With rom manager or sbf? Thanks
Sent from my DROID2 using XDA App
dec11ad said:
ok, let me get this straight. will i be able to SBF with the 2.2 SBF file that was leaked about 2 weeks ago?
Click to expand...
Click to collapse
That all depends. Have you gotten the OTA yet? If you are still on baseband 01.09.05P and Version 2.2.20 from verizon then yes, you can SBF. If you have gotten the OTA and are on baseband 01.09.07P and 2.30.20 from verizon, then no, you have to wait for the new SBF. The OTA changed both the mbmloader and the bootloader and you will end up with a brick of you sbf with the 2.2.20 file after the OTA
ok, i have the BP_C_01.09.07P baseband, can i still SBF? or does it only break the ability to SBF after installing Fission 2.0?
i currently have fission 1.2.1 ROM.
dec11ad said:
ok, i have the BP_C_01.09.07P baseband, can i still SBF? or does it only break the ability to SBF after installing Fission 2.0?
i currently have fission 1.2.1 ROM.
Click to expand...
Click to collapse
you cannot SBF on that baseband
Sorry for asking:
- I'd never done an OTA upgrade, my baseband BP_C_01.09.05P
- I'd rooted my D2 with easier1-2-3 by darkonion
- Now i'm on fission 1.2.1
So, what should i do to install Fission 2.0?
Thanks in advance
a_sty2007 said:
Sorry for asking:
- I'd never done an OTA upgrade, my baseband BP_C_01.09.05P
- I'd rooted my D2 with easier1-2-3 by darkonion
- Now i'm on fission 1.2.1
So, what should i do to install Fission 2.0?
Thanks in advance
Click to expand...
Click to collapse
I was in your situation, what i've done so far is SFB'ed my DROID2 to stock and i'm currently waiting for the OTA to popup on my device and then after that installs im going to reroot with the same method you used and install fission 2.0 like i did before.
droid2andyou said:
I was in your situation, what i've done so far is SFB'ed my DROID2 to stock and i'm currently waiting for the OTA to popup on my device and then after that installs im going to reroot with the same method you used and install fission 2.0 like i did before.
Click to expand...
Click to collapse
SBF your phone before installing this.
droid2andyou said:
I was in your situation, what i've done so far is SFB'ed my DROID2 to stock and i'm currently waiting for the OTA to popup on my device and then after that installs im going to reroot with the same method you used and install fission 2.0 like i did before.
Click to expand...
Click to collapse
The instruction said that:
"If you have the latest OTA update then I suggest you do not install this ROM in the case something goes wrong you will be stuck with a brick."
So why are you waiting for the OTA and install it?
a_sty2007 said:
The instruction said that:
"If you have the latest OTA update then I suggest you do not install this ROM in the case something goes wrong you will be stuck with a brick."
So why are you waiting for the OTA and install it?
Click to expand...
Click to collapse
because nothing went wrong when i installed Fission 1.2, i want the new baseband and kernel.
droid2andyou said:
because nothing went wrong when i installed Fission 1.2, i want the new baseband and kernel.
Click to expand...
Click to collapse
So, can i SBF'ed my D2, and flashing Fission 2.0 without waiting for OTA update? (Cause maybe need a time to wait for OTA popup)
So can anybody clarify the "do i need to sbf" question?
Yes, I def read the instructions which say you should, but I have still never had to sbf my d2, and I'm just wondering what am I risking, or possible to have problems with if I don't SBF?
Just seems reeeeallly above and beyond as wiping data sucks enough already.
Anyway, thanks for the continued releases, I can't remember the last time I had the same build of a rom on my phone for more than 48 hours lol.
a_sty2007 said:
So, can i SBF'ed my D2, and flashing Fission 2.0 without waiting for OTA update? (Cause maybe need a time to wait for OTA popup)
Click to expand...
Click to collapse
angdroid said 2.0 would work with or without the new update (kernel / baseband), however if you do get the OTA update you cannot SBF if you get stuck until it is released over @ mydroidworld. As long as you have the older baseband and kernal you can SBF your D2
one. said:
So can anybody clarify the "do i need to sbf" question?
Yes, I def read the instructions which say you should, but I have still never had to sbf my d2, and I'm just wondering what am I risking, or possible to have problems with if I don't SBF?
Just seems reeeeallly above and beyond as wiping data sucks enough already.
Anyway, thanks for the continued releases, I can't remember the last time I had the same build of a rom on my phone for more than 48 hours lol.
Click to expand...
Click to collapse
As with anything, it is not required. We will not offer support for the ROM however, unless the steps listed in the first post were taken. There are many user caused issues simply because the phone has been modified and we do not know to what point it has. The steps listed for the install restore the phone to factory settings, thus giving us a starting point. This also will allow us to isolate bugs and help to eliminate user error.

Im craving froyo

can anyone direct me to the easiest and safest way to get froyo... I have been reading but i can't seem to find anything that isnt super complicated. all i have done to my phone is root and lagfix. just need an arrow to point me in the right direction. thanks
http://www.techpetals.com/how-to-in...d-2.2-froyo-for-samsung-captivate-leaked-2295
JagoRacing said:
can anyone direct me to the easiest and safest way to get froyo... I have been reading but i can't seem to find anything that isnt super complicated. all i have done to my phone is root and lagfix. just need an arrow to point me in the right direction. thanks
Click to expand...
Click to collapse
STEP 1: Make sure you are on 2.1 Eclair
STEP 2: Make sure you are rooted
STEP 3: Install ClockWork Recovery
STEP 4: Download either Assonance or Cognition
STEP 5: Put the ".zip" file on the root directory of your phone
STEP 6: Boot into ClockWork Recovery and flash the ROM
Check out Doc CE in the development section
Sent from my SCH-I897 using XDA App
nbs11 said:
STEP 1: Make sure you are on 2.1 Eclair
STEP 2: Make sure you are rooted
STEP 3: Install ClockWork Recovery
STEP 4: Download either Assonance or Cognition
STEP 5: Put the ".zip" file on the root directory of your phone
STEP 6: Boot into ClockWork Recovery and flash the ROM
Click to expand...
Click to collapse
And what is wrong with Axura?
adamholden85 said:
And what is wrong with Axura?
Click to expand...
Click to collapse
+1
From a phone
adamholden85 said:
And what is wrong with Axura?
Click to expand...
Click to collapse
Nothing...I just didn't want to offer a 20 page list of equally good ROMs so I used the ones I have tried.
After months of waiting and finally getting over my fears of flashing, I rooted and flashed the stock 2.2 rom to my captivate today!
my opinion, just use the stock 2.2. it's frickin amazing. I'm thrilled and can't believe it took this long for me to build up the courage to flash. from the gps working to the beautiful text to speech ( which I'm using to write this even as we speak..lol); I can't get over how much I love this.
So, use the odin flasher and have fun!
Many thanks to all the developers on XDA who worked so hard to get 2.2 out all of us!
Sent from my SAMSUNG-SGH-I897 using XDA App
How do i use odin? Do you have a link?
I can't speak in regard to other ROMs as I have only tried working with Cognition.
The thing is, if you can handle the complexities of Lagfix, installing Cognition is a piece of cake. The instructions that nbs11 posted are pretty much it, except that you should disable whatever lagfix you used before you do it, and use Android ID changer to back up your Android ID. As far as Odin goes, you only need it if:
1. You really like your phone to be clean before you upgrade
2. Something goes wrong.
I panicked the first time something went wrong. I should tell you my story. I forgot to use Android ID changer, and also forgot to copy the data from a few other things from my original Eclair build. So, I went back to one of my backups. I didn't realize that the backup didn;t include the kernel, so the rolled-back phone no longer booted. Odin to the rescue. It flashed an idiot-proof stock version, then I used ROM manager to get to my backed-up data, re-flashed with Odin, and ran the Cognition backup. It all worked fine.
TL;DR. You just need ROM Manager and a little planning, and Odin will bail you out in the off chance you screw something up.
Someone who likes setting up a phone less than I do should make a back-up checklist.
Oh, and here's a link to everything you need to know about Odin:
http://lmgtfy.com/?q=Odin+downloader+Captivate&l=1
K, I was dumb the first time around.....
RepublicanDaddy said:
After months of waiting and finally getting over my fears of flashing, I rooted and flashed the stock 2.2 rom to my captivate today!
my opinion, just use the stock 2.2. it's frickin amazing. I'm thrilled and can't believe it took this long for me to build up the courage to flash. from the gps working to the beautiful text to speech ( which I'm using to write this even as we speak..lol); I can't get over how much I love this.
So, use the odin flasher and have fun!
Many thanks to all the developers on XDA who worked so hard to get 2.2 out all of us!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm officially changing my mind. I've been using Cognition 3.04 now for about a week. I've not run into ANY issues. In the first week of using the leaked "official" 2.2 release, I'd already run into a few minor bugs, then over the course of a month, ended up with a fun that was stuck in a reboot loop...totally random issue, nothing had changed on the phone, it just went nutz on me.
I flashed to Cognition and am absolutely LOVING it!!! If you're going to flash a ROM, skip the "official" leaked 2.2 and go for Cognition. It's great! Smooth, fast, and without bloatware.
I do have to admit, yes I know I'll catch some flak for it, but I do miss the Samsung Media Hub (Cognition has it removed as Bloatware). Other than that....no issues at all!
Has anyone used these methods on a Rogers Captivate (I897)?
RepublicanDaddy said:
I flashed to Cognition and am absolutely LOVING it!!!
Click to expand...
Click to collapse
Don't try Andromeda 1.0. You would probably be so overcome with joy as to poop yourself.
opcow said:
Don't try Andromeda 1.0. You would probably be so overcome with joy as to poop yourself.
Click to expand...
Click to collapse
Does a squirt count? Cause I did that.
boborone said:
Does a squirt count? Cause I did that.
Click to expand...
Click to collapse
Lol! Well, I did pee a little...lol
Btw - I know I'll catch flak for this, but Cognition doesn't have media hub...any idea how I can install it?
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] uninstalling Froyo Beta

So... I heard that AT&t will be updating phones to Froyo tomorrow Feb 24th. How would I go about removing the beta samsung rom I installed back in October? or should I just wait till the new rom hits the web and apply that?
Obviously I'm pretty new to all this.
Someone will package it into a cwm .zip for people who love bloat and such.
Sent from my Captivate.
That was not a beta. It was a leaked ROM that devs in here used as a base. You will need to Odin back to stock, but there's some confusion right now as to whether the Froyo release tomorrow will be OTA or via Kies. If it is OTA and you do an Odin you will not be able to get it. I would wait right now and start reading up on the process before you do something that might brick your phone. Start with the tutorials in the Stickies at the top of this forum.
MikeyMike01 said:
Someone will package it into a cwm .zip for people who love bloat and such.
Sent from my Captivate.
Click to expand...
Click to collapse
Haha, so true. Some are so eager to use this bloat and gimped ATT rom...
iwantatransam said:
So... I heard that AT&t will be updating phones to Froyo tomorrow Feb 24th. How would I go about removing the beta samsung rom I installed back in October? or should I just wait till the new rom hits the web and apply that?
Obviously I'm pretty new to all this.
Click to expand...
Click to collapse
ROMs can not be uninstalled. You have to flash a new ROM. You have two choices:
1. Use the leaked UCKB1, by all means this seems to be the official release tomorrow, and flash it using ODIN3. Make sure you do a factory reset afterwards.
2. Use the ODIN OneClick to flash back to orginal JF6 stock firmware and wait for official release to upgrade.

Odin One Click for Official Froyo KB1?

Any word on if there will be an Odin One Click for the official Froyo 2.2 KB1? If so, will it be able to incorporate the ability to recieve OTA updates? I've looked in many obvious threads including, the development section as well as the Odin One Click thread.
Doesn't KB1 come with a newer recovery that needs to be downgraded regardless? So why not just flash back to JF6?
cavsoldier19d said:
Any word on if there will be an Odin One Click for the official Froyo 2.2 KB1? If so, will it be able to incorporate the ability to recieve OTA updates? I've looked in many obvious threads including, the development section as well as the Odin One Click thread.
Click to expand...
Click to collapse
Any more updates, I wouldn't hold my breath, won't be OTA. AT&T learned it's lesson with the JH7 fiasco.
You can just use Odin3 to get back to JF6, then reinstall the Froyo update via Kies. Done it a half dozen times already.
I am aware that I could flash back to jf6 and go from there. Just curious if odin would make a kb1 is all. I agree, hopefully att learned from ota update fiasco. When I first got my captivate, I was shocked to see that samsung didn't provide a desktop software cd that would allow your pc to download and push updates similarly with blackberrys and the blackberry manager software or iphone with itunes. For that reason alone is why i found myself on xda trying to find out how to update. I now know that is what the samsung lies is for. But that could still be provided with the phone for the average end users who don't rom their phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
ODIN ONE CLICK (and ODIN3) are utilities made by Samsung, and how it was compiled is unknown, SO.. it cannot be "torn apart" and redone with froyo.
however there are some automated systems out, HEIMDALL and the new Captivate toolbox using HEIMDALL, may come out with easy froyo flashes,
and dont forget about froyo's 3e recovery, updated rooting, updated unlock, ect... it just adds more things to do to load a new custom rom..
so unless you want to flash froyo stock and leave it there, there isnt much point.
I am keeping a copy of the stock froyo firmware in this post http://forum.xda-developers.com/showthread.php?t=963403 Just in case I need to send it back. I have used Heimdall to flash it a couple of times so far.
pietro_spina said:
I am keeping a copy of the stock froyo firmware in this post http://forum.xda-developers.com/showthread.php?t=963403 Just in case I need to send it back. I have used Heimdall to flash it a couple of times so far.
Click to expand...
Click to collapse
Wait, so I can just flash that prior to sending my phone to ATT as opposed to odin to JF6 then Kies to KB1?
Something like this would definitely be handy.
+2 a Odin kb1 would make life easyer
Sent from my SAMSUNG-SGH-I897 using XDA App
qwertyaas said:
Wait, so I can just flash that prior to sending my phone to ATT as opposed to odin to JF6 then Kies to KB1?
Click to expand...
Click to collapse
Maybe, :-/
It depends on what you end up with when you flash it... as there are only the four (cache.rfs, factoryfs.rfs, modem.bin and zImage) files in there. if the rom you flashed has other stuff that won't get over written I guess you might ind up with some sort of Franken ROM and worst case a brick. If you arn't sure what you have done to or have on your phone then I guess you ask in your roms help thread what is the approved method of returning to stock from their rom... some have various lagfixes and such that can require a specific procedure.
Even Odin leaves behind remnants of things from your previous usage. I just sent two phones back and had to Odin both. I then did master clear and still there was some stuff left that I had to delete manually. I doubt AT$T has the manpower or time to go through every returned phone looking for custom ROM remnants. To insulate them from any claims of having access to a customer's private information that may have been left on the phone by a less tech savvy user, they probably just wipe them when they get them or toss them in a bin to be used as repair parts.

If you have problem reverting from 2.3.6 to stock 2.3.5, this might help

NOTE: this is from 2.3.6 to stock 2.3.5. NOTHING RELATED TO ICS DOWNGRADE.
I hope my experience on reverting back to stock 2.3.5/2.3.6 can help other people with similar problem.
I was running Romulus V2.0 (Android 2.3.6). I wanted to update to Leaked ICS or prepare for future ICS official update. So I need to revert back to stock 2.3.6.
The method Jim suggested is (1) FXZ to 2.3.5. (2) OTA to 2.3.6. But when I use RSD to flash 2.3.5 FXZ (precisely following the beginner's guide, download InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip and replace files in "replace.zip"), I get "Invalid CG version". My next try is to follow the guide in http://forum.xda-developers.com/showthread.php?t=1493386, and my phone is alive again. However, I cannot do a factory reset, so I still cannot go back to stock 2.3.6.
After a lot of searching, I was able to find another "replacement package". Its linke is http://www.mediafire.com/?3bs8ovqteawab02, named "replaceFilesInFXZ.zip". I replaced files in InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip with files in this package. My phone boots without problem and is on stock 2.3.5. I also have OTAed to 2.3.6.
I think this could be helpful for those that want to revert back to stock 2.3.5/2.3.6, and be able to update to ICS. If you are on 2.3.6, I think it is safe to take a try, since there is no hard brick problem as long as you do not flash ICS leak.
---------------------------
I was thinking why some people can FXZ 2.3.5 following the beginner's guide but some people cannot. One possible case could be (please correct me if I am wrong):
I was on stock 2.3.5, but has never OTAed to 2.3.6. I was always using bootstrap recovery to flash other's customized 2.3.6 rom. Therefore, some files such as CDT.bin, boot.img, recovery.img, device_tree.bin and lbl was never updated to 2.3.6 version.
When I follow the beginner's guide, I think this guide assumes that everyone has ever OTAed to 2.3.6 before. So some inconsistency happens.
jerrycrystal said:
I hope my experience on reverting back to stock 2.3.5/2.3.6 can help other people with similar problem.
I was running Romulus V2.0 (Android 2.3.6). I wanted to update to Leaked ICS or prepare for future ICS official update. So I need to revert back to stock 2.3.6.
The method Jim suggested is (1) FXZ to 2.3.5. (2) OTA to 2.3.6. But when I use RSD to flash 2.3.5 FXZ (precisely following the beginner's guide, download InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip and replace files in "replace.zip"), I get "Invalid CG version". My next try is to follow the guide in http://forum.xda-developers.com/showthread.php?t=1493386, and my phone is alive again. However, I cannot do a factory reset, so I still cannot go back to stock 2.3.6.
After a lot of searching, I was able to find another "replacement package". Its linke is http://www.mediafire.com/?3bs8ovqteawab02, named "replaceFilesInFXZ.zip". I replaced files in InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip with files in this package. My phone boots without problem and is on stock 2.3.5. I also have OTAed to 2.3.6.
I think this could be helpful for those that want to revert back to stock 2.3.5/2.3.6, and be able to update to ICS. If you are on 2.3.6, I think it is safe to take a try, since there is no hard brick problem as long as you do not flash ICS leak.
---------------------------
I was thinking why some people can FXZ 2.3.5 following the beginner's guide but some people cannot. One possible case could be (please correct me if I am wrong):
I was on stock 2.3.5, but has never OTAed to 2.3.6. I was always using bootstrap recovery to flash other's customized 2.3.6 rom. Therefore, some files such as CDT.bin, boot.img, recovery.img, device_tree.bin and lbl was never updated to 2.3.6 version.
When I follow the beginner's guide, I think this guide assumes that everyone has ever OTAed to 2.3.6 before. So some inconsistency happens.
Click to expand...
Click to collapse
Did you update to ICS or not? That does not appear to mentioned at all in your post... It just says that you are on 2.3.6 and not ICS... that really does not help all here if that is the case... those bricking have ALL installed the AT&T ICS leak, and tried to fxz back to 2.3.5...
So.... I am sure that what you mention does not really do any good since you appear to NEVER have installed the OTA ICS leak for AT&T, this really does not help...
jimbridgman said:
Did you update to ICS or not? That does not appear to mentioned at all in your post... It just says that you are on 2.3.6 and not ICS... that really does not help all here if that is the case... those bricking have ALL installed the AT&T ICS leak, and tried to fxz back to 2.3.5...
So.... I am sure that what you mention does not really do any good since you appear to NEVER have installed the OTA ICS leak for AT&T, this really does not help...
Click to expand...
Click to collapse
+1
Sent from my MB865 using xda's premium carrier pigeon service
It is from 2.3.6 to 2.3.5, not from ICS
jimbridgman said:
Did you update to ICS or not? That does not appear to mentioned at all in your post... It just says that you are on 2.3.6 and not ICS... that really does not help all here if that is the case... those bricking have ALL installed the AT&T ICS leak, and tried to fxz back to 2.3.5...
So.... I am sure that what you mention does not really do any good since you appear to NEVER have installed the OTA ICS leak for AT&T, this really does not help...
Click to expand...
Click to collapse
No, I was just to help people that running 2.3.6 to go back to stock 2.3.5 (There are people that have the same issue as mine). Nothing related to currently leaked ICS.
jerrycrystal said:
No, I was just to help people that running 2.3.6 to go back to stock 2.3.5 (There are people that have the same issue as mine). Nothing related to currently leaked ICS.
Click to expand...
Click to collapse
There is already a sticky on this... please search next time...
UGGGGGGHHHHHHH!!!!!
I am getting so tired of repeating myself:
http://forum.xda-developers.com/showthread.php?t=1778853
jerrycrystal said:
...After a lot of searching, I was able to find another "replacement package". Its linke is http://www.mediafire.com/?3bs8ovqteawab02, named "replaceFilesInFXZ.zip". I replaced files in InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip with files in this package.
Click to expand...
Click to collapse
^^^This guy even shot himself in the foot right here^^^
Seriously, what do you consider "a lot of searching"?
Sent from my MB865 using xda's premium carrier pigeon service
jimbridgman said:
There is already a sticky on this... please search next time...
UGGGGGGHHHHHHH!!!!!
I am getting so tired of repeating myself:
http://forum.xda-developers.com/showthread.php?t=1778853
Click to expand...
Click to collapse
In fact, this is REALLY not the same thing as the sticky one!!!!! Especially the beginner's guide.
People have problem reverting back, that's why there is a post also sticked "2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX"
But these people will want to go back to full stock 2.3.5 with the ability to do OTA and recovery.
That's the reason I post this.
jerrycrystal said:
In fact, this is REALLY not the same thing as the sticky one!!!!! Especially the beginner's guide.
People have problem reverting back, that's why there is a post also sticked "2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX"
But these people will want to go back to full stock 2.3.5 with the ability to do OTA and recovery.
That's the reason I post this.
Click to expand...
Click to collapse
Dude, The invalid cg fix is the sticky, and it works perfect for this issue. Again this phone has been out over 10 months now, and we have seen it all. Please just sit back and watch things around here for a while before you jump in and just muddy the waters... it is already hard enough to keep people from doing stupid things, that we are expected to fix.
Apex_Strider said:
^^^This guy even shot himself in the foot right here^^^
Seriously, what do you consider "a lot of searching"?
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
I read all posts in this forum related to atrix2 about from 2.3.6 to 2.3.5. And the attachment I give is NOT the "replace.zip" in the beginner's guide, I found it in another forum.
jimbridgman said:
Dude, The invalid cg fix is the sticky, and it works perfect for this issue. Again this phone has been out over 10 months now, and we have seen it all. Please just sit back and watch things around here for a while before you jump in and just muddy the waters... it is already hard enough to keep people from doing stupid things, that we are expected to fix.
Click to expand...
Click to collapse
Sorry if I muddy the waters... and I appreciate what you have done for us, really.
But the method in sticky posts really does not help me to revert back to stock 2.3.5, I INDEED have read all posts/replies one by one. The method I posted actually worked for me to go back to stock 2.3.5, so I wanted to share it.

Categories

Resources