Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
thats funny. i have run every froyo rom available to us, i9000 w/voodo, ulf, cognition with voodoo, and i have yet to brick my phone. i flash to stock between EVERY new rom.
there is something you are not doing right. did you disable voodoo before attempting to flash stock?
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I always flash back to JF6 via Odin 1 click before going to any new rom. It does not matter for whether voodoo is disabled or not because Odin 1 click repartitions everything to RFS. Also, the orange screen is not that big a deal. Reflashing JF6 via Odin once more is the solution.
If you continually have these problems when flashing to JF6:
1. Try re-downloading Odin 1 click.
2. Follow correct procedure for Odin flashing (Read OP's)
3. Try other USB ports
4. Uninstall and install fresh drivers that match your operating system (eg. 32bit/64bit)
Further, this post is not for the development section, but belongs in General or Q&A.
I think even without voodoo disabled, flashing back to stock will break voodoo and it wont be functional anymore. I personally never disable voodoo when flashing back to stock. You need to Master Clear after flashing back to stock.
Never bricked my phone flashing all the time.
I do it all the time! Never bricked my phone... EVER! The closest I came was when I tried flashing to another rom with CVM with voodoo still enabled. got stuck in loop, but to rectify the situation I "flashed back to stock with one click ODIN" and all was well.
i9000 is not the captivate argh different kernel
Odin gave me Blue, Light Blue, Orange, White and Black Screens of Death, no matters if i had Voodoo or not..
I think it sometimes hangs without any reason, but the drivers/program itself..
Thanks God my phone doesn't have the Bootloader's 3 Button issue..
Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
I believe he was referring to i9000 roms. I have never had any issues flashing back to stock from any rom. It has to be something you are doing. Might be the answer you want but probably going to be the most common answer you will get. Check your steps.
Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
i never said i am running an i9000 HARDWARE, i said ROMS
like everyone else has said. its something YOU are doing wrong. please dont spread FUD
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Sometimes its not the arrow....
its the Indian. The majority of the people who flash follow the same procedure with no issues. While its nice of you to try to caution folks, maybe you need to look at what you're doing instead of jumping to conclusions.
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
Agreed 10char
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
AGREED!
one person has problems with multiple devices=look for the common denominator.
if not deleted then at least OP change the title because its misleading.
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I have flashed i9000 roms, kernels, modems, themes, and anyting else imaginable, with and without voodoo, with and without master clear, and have NEVER gotten the orange death screen before, during, or after Odin flashing back to stock. I've flashed just about every iteration of the Cognition FroYo roms and have never had an issue.
Re-download odin, maybe? But it's not an issue with Cognition.
Belaflek said:
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Click to expand...
Click to collapse
Yo only need to disable voodoo when you are upgrading from one version to another but when you are flashing back to stock it will repartition everything for you back to RFS.
I've run all the Froyo kernels, ROMs, even i9000 Froyo ROMs on the Froyo reoriented kernel, with or without voodoo, it doesn't matter, and I flash back to stock all the time. Odin wipes everything out, it doesn't matter what you are running.
the "factoryfs.rfs" screen-o-death is a well known problem. fortunately, factoryfs.rfs doesn't really matter (it's only the /system partition), your phone just won't boot. Likely you'll hit the phone--!--PC screen, but as long as you have 3 button recovery working, you're safe.
this issue crops up when you have a bad USB connection to your phone. I'm willing to bet 90% of the people with this problem are running outdated hardware (made before 2006 or so) that can't keep up with ODIN's pace or are using a desktop and not plugging the USB into a port connected to the motherboard (you should be using one on the back of the tower)
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
posts like this... littering the dev forum
Related
Alright this is kind of a thread to get a discussion going. And NOO THIS IS NOT WHAT IS THE BEST ROM THREAD!
This is a thread regarding whether or not you flash back to stock when flashing new ROMs.
Personally Ive always flashed back to stock because im a Buiild 1011 and I use this thread which has worked EVERY time so if your a build 1010 this is a great way that is flawless:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
But the debate here is whether or not you flash back to stock every time and if you dont flash back to stock tell us about your experiences flashing ROMs over each other.
Im doing this because the more I read on threads of ROMs reading and reading I always see a ton of posts arguing saying that they dont even flash stock anymore and I just want to see and hear what y'all have to say.
Would love to see the return on this and since i have Download mode JIG thanks to MobileTechVideos (fantastic!) I may flash a ROM over Darkyy that Im using currently just to see how it works.
Thanks in advance
No. Never. Why would I? I do it only if I want to run stock or once or twice when my partitioning was screwed. Otherwise it's a pointless thing to do.
opcow said:
No. Never. Why would I? I do it only if I want to run stock or once or twice when my partitioning was screwed. Otherwise it's a pointless thing to do.
Click to expand...
Click to collapse
Hm, have you ever run into a problem? And I thought you have to flash back to stock or the ROM will not install if they are a different base.
I.e. Since im on Darkyy 9.3 with the JS5 base, i couldnt just go flash Perception with a JS3 base right?
Im not trying to argue Im just wondering and Im practically unbrickable so I may try that when I get home and if I get in trouble either flash back to Darkyy and finally just use the ole Jig and flash back to stock.
I stopped flashing odin after I had to bring my 1007 phone in for warranty and got a 1008 back. No way I am flashing using odin, 1008's have bad flashing mojo. I have a nandroid of the original OS and can go back to that if I need to to start over. I even bought a jig after I got this one just in case.
Stephenv1971 said:
I stopped flashing after I had to bring my 1007 phone in for warranty and got a 1008 back. No way I am flashing, 1008's have bad flashing mojo. I have a nandroid of the original OS and can go back to that if I need to to start over. I even bought a jig after I got this one just in case.
Click to expand...
Click to collapse
First of all the nandroid WILL NOT restore your old OS because it doesnt restore anything System.
Secondly the build 1008 has a problem with the 3 button fix flash this zip if your 3 button fix gets removed. It works for everyone including me when I lost 3 button combo.
And third smart choice with the Jig I bought one just in case and it has never failed me
Dlev7 said:
Hm, have you ever run into a problem? And I thought you have to flash back to stock or the ROM will not install if they are a different base.
Click to expand...
Click to collapse
No, I have done it dozens of times with many different ROMs and never had a problem.
I.e. Since im on Darkyy 9.3 with the JS5 base, i couldnt just go flash Perception with a JS3 base right?
Click to expand...
Click to collapse
Yes, you could.
Im not trying to argue Im just wondering and Im practically unbrickable so I may try that when I get home and if I get in trouble either flash back to Darkyy and finally just use the ole Jig and flash back to stock.
Click to expand...
Click to collapse
Right. I think you'll find that it works just fine and saves you same hassle and it's safer too since you won't be unnecessarily be writing a new boot.bin and sbl.bin (DG's ROMs do include sbl.bin, however).
Dlev7 said:
Hm, have you ever run into a problem? And I thought you have to flash back to stock or the ROM will not install if they are a different base.
I.e. Since im on Darkyy 9.3 with the JS5 base, i couldnt just go flash Perception with a JS3 base right?
Im not trying to argue Im just wondering and Im practically unbrickable so I may try that when I get home and if I get in trouble either flash back to Darkyy and finally just use the ole Jig and flash back to stock.
Click to expand...
Click to collapse
Just curious why you would think flashing js5 over jf6 would be any more effective than flashing over js3 or jpy. I have yet to see an explanation other than "its recommended" or "because dg said to" so I doubt you will get any real answers from the odin crowd. Personally I haven't done it in forever.
newter55 said:
Just curious why you would think flashing js5 over jf6 would be any more effective than flashing over js3 or jpy. I have yet to see an explanation other than "its recommended" or "because dg said to" so I doubt you will get any real answers from the odin crowd. Personally I haven't done it in forever.
Click to expand...
Click to collapse
Ive never thought of it that way ever before. But the only thing ive ever heard is that Odin does stuff that the install script that these ROMS dont.
Ya and its said to say but thats the only things ive ever heard that its safer and DG said so. But in my defense does the install script on these ROMs really do the same as what Odin does?
Do either of y'all know whether or not the install script on the ROMs do replace it well.
The reason ive never done this is because I always heard that only Odin can flash over things.
But Ive seen a lot of people like y'all say all you have to do is wipe data and cache, and dalvik cache, and flash away but do the instal script in these ROMs rewrite the system?
Dlev7 said:
Do either of y'all know whether or not the install script on the ROMs do replace it well.
The reason ive never done this is because I always heard that only Odin can flash over things.
Click to expand...
Click to collapse
They delete files and format partitions just fine. If they didn't then I wouldn't have been able to go for months trying almost every ROM released without ever launching Odin. I don't know what you mean by "only Odin can flash over things." If that were the case then how would CWM flashing ever work whether you flashed stock first or not? If things are getting left behind then why would having JF6 stuff left behind be preferable?
But Ive seen a lot of people like y'all say all you have to do is wipe data and cache, and dalvik cache, and flash away but do the instal script in these ROMs rewrite the system?
Click to expand...
Click to collapse
You don't have to do that either. Check out this snippit from an install script:
format SYSTEM:
format CACHE:
format DATA:
format DATADATA:
delete_recursive SDCARD:Android
delete_recursive DATADATA:databases/com.android.providers.media
delete_recursive DATADATA:databases/com.cooliris.media
delete_recursive SDCARDCIM/.thumbnailsThat takes care of deleting the cache, dalvik cache and more.
Qq
opcow said:
They delete files and format partitions just fine. If they didn't then I wouldn't have been able to go for months trying almost every ROM released without ever launching Odin. I don't know what you mean by "only Odin can flash over things." If that were the case then how would CWM flashing ever work whether you flashed stock first or not? If things are getting left behind then why would having JF6 stuff left behind be preferable?
You don't have to do that either. Check out this snippit from an install script:
format SYSTEM:
format CACHE:
format DATA:
format DATADATA:
delete_recursive SDCARD:Android
delete_recursive DATADATA:databases/com.android.providers.media
delete_recursive DATADATA:databases/com.cooliris.media
delete_recursive SDCARDCIM/.thumbnailsThat takes care of deleting the cache, dalvik cache and more.
Click to expand...
Click to collapse
So technically its Is aactually safer because you don't lose 3 buttons. And since I'm a build 1011 I have to do a 30 minute procedure just to get to JH7.
So you may be right its actually safer.
Sent from my SGH-I897 using XDA App
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
bigbyte.me said:
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
Click to expand...
Click to collapse
U got a jig?
Sent from my Captivate using XDA Premium
Zig won't help as nothing is helps only in case of Soft brick.
BTW i figured out where I went wrong, The cognition ROM contains seconday bootloader. So when I flashed it I ended up with Gingerbread primary and Froyo secondary bootloader and hence the Brick. I request all the rom dev to mention at the start of their post if their ROm contains bootloaders.
bigbyte.me said:
Flashed Cognition 4.3.2, flashed successfully.
Click to expand...
Click to collapse
^ That's where you went wrong. Cog flashes sbl. You ended up with one bootloader from 2.3, and one bootloader from 2.2.
There are videos of how to unbrick a perma-bricked phone with a riff box jtag unit on youtube. It'll require you to remove the motherboard and blow $150 or so on a riff box, though.
or you send it to someone with the equiptment, like mobiletechvideos.com and not learn about riff/boxing and spend less money... and and and...
or because it doesnt boot and they cant prove you voided your warranty send it back!
So, this could be avoided doing what?
-Going back to GB stock and from there going back to froyo stock (without 3 button fix)?
I don't think moviletech does crappys something about the solder points too close together.
Edit: but could be wrong.
Sent from my GT-I9000 using XDA Premium App
i was in a similar situation, no 3 button nothing worked my phone wouldn't even power on
but the one method that saved me was this,
Remove battery, SIM card, SD card (if present)
Connect USB cable from computer
While holding down up & down volume, re-insert battery
may be this could help you too.
mobile tech does and has been for over a month, and the first few people are free!
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
for me if i touched any buttons the jig would not work.
other methods wouldnt work either.
worth a shot.
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
1tontomato said:
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
studacris said:
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
Click to expand...
Click to collapse
Yea your right it is the sbl.bin. It was a good idea before gingerbread, but I think it's time has passed especially since it's really easy to get past not having a button combo with a jig. A bad combination of bootloaders is a "brick" for sure.
Sent from my SAMSUNG-SGH-I897
amtrakcn said:
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
Click to expand...
Click to collapse
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
bigbyte.me said:
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
Click to expand...
Click to collapse
I say none. ANYTIME you touch bootloaders there is a chance of hard bricking. If they don't have any, worst case is a "clay" (soft brick)
TRusselo said:
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
....
Click to expand...
Click to collapse
Perhaps I;m not out of the woods yet but a wrong action in ODIN had HB'd my Cappy. Your steps got me back to DL mode. Perhaps it is the 5 count. Patience not being my strong pt I had "not waited" until your recommendation.
I was trying from Continuum5.3 to get back to eclair so to carrier unlock when I made an ODIN error. Still need do that but for now I'll just be thankful that it lives, and move only forward..
its the not touching buttons that makes this trick work
if you replace the battery, what is your normal instinct?
try the power button! or try the button methods...
you are the first to confirm my trick!
congrats!
http://forum.xda-developers.com/showthread.php?t=731989
Use this to get back to stock safely!
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE
use the thanks button!
Hmm very interesting...
I thought your trick worked because it was a screw up in the param.lfs not a bootloader brick, guess not.
im surprised too...
i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.
I just use odin one click to flash back to stock then flash by froyo rom of choice.
To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy
i also use odin one-click to get back to stock
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897
heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*
This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897
Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.
Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?
FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!
No problem man.
TRUST THE ZOMBIE!!
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..
I was able to flash from the "phone ! pc" screen (kinda) May be useful for bricks?
If this post proves to be useful and would serve better in another section then please move it.
Yesterday (June.09.2011) I got a refurb replacement for my Captivate, it was actually a new phone though and as far as I can read it's an 1105 build.
It came with Froyo 2.2 and no software updates from AT$T were available when I checked from the phone.
GPS didn't seem to do so well according to My Tracks recording a 22 mile motorcycle trip home.
I was going to try Cognition (Froyo based)
I was able to use the buttons on the phone to get into recovery 3e but it checks for signatures and I couldn't figure out how to root the phone and replace recovery.
I would have used one click root from my pc but I didn't have the proper windows drivers (net framework?)
I decided to flash Odin one click to stock (Eclair 2.1)
I also have the Odin stock 2.1 with 3 button fix that I had used on my other refurb captivate successfully.
This is where things went bad for me.
I used the 3 button fix version of Odin (I don't know if my result would have been different if I had used One click Odin instead and I'd like to know for later)
After the flash the phone would only boot to the phone ! pc screen no matter how many different button, battery, power button, usb cable, jig combinations I tried (Yes I have a jig)
Anyways, I had Odin one click (not the three button fix version) open and even though I only ever saw the ! screen on the phone I noticed that Odin was showing the device connecting and disconnecting when I pulled the usb cable.
What the hell, I thought I was bricked anyways so I hit Start. The phone showed a progress bar that mirrored what Odin was showing me, right below the ! icons on the phone.
After that I was able to use the jig to enter download mode, I tried both Odin (stock 2.1) versions I had and they ran the flash but the phone boot looped when I tried to start it up.
I then tried the method to update the bootloaders and move onto Gingerbread and I was successful, Running Serendipity VII now (Thanks MikeyMike01, ChanceM)
It was a nerve racking experience and I'm nervous if I decide to try to go back to Froyo again.
Maybe this info isn't new, maybe it's helpful. I may summarize later.
Any thoughts or tips to get back to Froyo if I want to later?
not weird at all.
here's what happened:the phone...!...pc screen just signifies that a flash was incomplete, the first flash with the 3 button fixed failed before it ever loaded any firmware, therefor the image for when download mode is initiated was missing, all that is is a .png. since it was missing the incomplete flash screen was the only thing there for it to call upon when DL mode was started.
odin one click bootlooped you cause it just does that to new phones...to get back to stock bootloaders use odin one click then use this http://forum.xda-developers.com/showthread.php?t=995143... or just use that and go back to stock eclair with the GB bootloaders. DO NOT FLASH THE 3 BUTTON FIX PACKAGE WITH GB BOOTLOADERS THAT WILL BRICK YOUR PHONE.
Thanks for the explanation!
studacris said:
not weird at all.
here's what happened:the phone...!...pc screen just signifies that a flash was incomplete, the first flash with the 3 button fixed failed before it ever loaded any firmware, therefor the image for when download mode is initiated was missing, all that is is a .png. since it was missing the incomplete flash screen was the only thing there for it to call upon when DL mode was started.
odin one click bootlooped you cause it just does that to new phones...to get back to stock bootloaders use odin one click then use this http://forum.xda-developers.com/showthread.php?t=995143...or just use that and go back to stock eclair with the GB bootloaders. DO NOT FLASH THE 3 BUTTON FIX PACKAGE WITH GB BOOTLOADERS THAT WILL BRICK YOUR PHONE.
Click to expand...
Click to collapse
Is there a reason they don't just include the intended PBL with that SBL for the 3 button fix? it would solve all the problems... I'll go figure this one out.
AdamOutler said:
Is there a reason they don't just include the intended PBL with that SBL for the 3 button fix? it would solve all the problems... I'll go figure this one out.
Click to expand...
Click to collapse
they dont have the PBL file. all they have had is the SBL
A similar thing happened to me on my replacement. It came with stock 2.2 and when I tried to use Odin one click it failed. I pulled the plug and after that nothing was getting me into download mode. No button combinations or jig worked. When I was trying more combinations I had left odin open and realized it was showing as connected even though I was only getting the phone ! pc screen. So just like you I figured what the hell and went for it. 2 minutes later I was at stock 2.1.
nybmx said:
A similar thing happened to me on my replacement. It came with stock 2.2 and when I tried to use Odin one click it failed. I pulled the plug and after that nothing was getting me into download mode. No button combinations or jig worked. When I was trying more combinations I had left odin open and realized it was showing as connected even though I was only getting the phone ! pc screen. So just like you I figured what the hell and went for it. 2 minutes later I was at stock 2.1.
Click to expand...
Click to collapse
What build number on yours?
I'm still having problems, post to follow...
I just tried to go back to Froyo from Gingerbread.
I followed the instructions linked to in this thread (thanks) http://forum.xda-developers.com/showthread.php?t=995143...
The following 4 flashes just left me in a boot loop but I was able to use my jig to get into d/l mode each time.
I did get a random Odin 3 v1.3 from the net that had GT-P1000 instead of i897 or i9000 on it's title when run. I don't think it was the issue though since OneClickDownloader also failed the same way for me.
Odin 3 v1.3 JF6 Secure
Odin 3 v1.0 OneClickDownloader
Odin 3 v1.3 JF6 Secure
Odin 3 v1.7 JF6 Secure (This Odin came with the Gingerbread installation package I got from Cezar/icezar1 (I think)
Now I am running a fever and I'm generally slow but I think I'm following your suggestions.
edit; I wrote 1.2, I meant 1.3
Pirateghost said:
they dont have the PBL file. all they have had is the SBL
Click to expand...
Click to collapse
God damnit.... NEVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER flash a PBL without a matching SBL.... This is the cause of bricking for 90% of captivates.
AdamOutler said:
God damnit.... NEVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER flash a PBL without a matching SBL.... This is the cause of bricking for 90% of captivates.
Click to expand...
Click to collapse
yep. but the sbl was all that was needed when that package was created months and months ago. we didnt have any need to worry about pbls at that time...then 2.3 came along
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
daveyian said:
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
Click to expand...
Click to collapse
Well I know 4.5 and above for cognition doesn't have boatloaders in it. You might want to unzip roms and check for bootloaders just to be safe.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
daveyian said:
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
Click to expand...
Click to collapse
It will work. I am running firefly 3.0 at the moment, on GB bootloaders. I have not tried cyanogen yet. I'm sure eventually all the little bugs will get worked out of gingerbread, and I'll be back on it.
wow i posted about this MONTHS ago....
heres the link.....
http://forum.xda-developers.com/showthread.php?t=988927&highlight=flash+from+soft+brick
I got that phone ! pc last night while trying to odin back to 2.1 from stock. Odin didnt make any progress for 10 mins and I removed battery. Thought I was screwed. Removed the usb and pulled the bat. Opened odin and plugged it back in and the same screen came right up. Just held down the volume keys and power button till the screen flashed once and noticed odin recognized the com port. Then tried odin again and it worked fine... even displayed the little blue progress bar on that screen lol.
daveyian said:
What build number on yours?
I'm still having problems, post to follow...
Click to expand...
Click to collapse
A refurb 1008
true story!
happened to me 2!
Ok so I just got me a New samsung showcase. It came with 2.2 installed build number sch-i500.ee25. Ok so i find out about rooting and all this so i start researching all about it. Here is where i am. I rooted with SuperOneClick. Worked fine. I installed ROM manager to get the clockworkmod but it did not work so I used Odin to install clockworkmod. That worked fine. So at this point I decided i need to backup the stock ROM. I try this using ROM manager but no go. it reboots into clockworkmod and gives me the sd card not mounted stuff. So I read and read and read but i can't seam to find a solution to this problem. I know there other people that have had this problem. I have read through the step by step guides and i really see nothing on this. Anyone have any type of solution.
Running on stock 2.2 rom manager doesnt work. You will need to go into cwm by turning off phone, holding power,vol up and down at same time. after samsung blinks 2nd time let go of buttons and you will boot into recovery.
Thank you. I thought I tried that before but I guess i did something wrong. Worked that time. Now if my memory is correct from reading that will not back up two things. The kernel and something else. How do I back up the kernel? Or am I just not thinking correctly cause I have not had enough sleep.
Samsung Galaxy S with Cellular South
I had to have Kies Mini open and running on my computer to root my phone
First, Welcome!
Second, Download and familiarize yourself with a program called Odin. This phone is hard to brick. From nearly every situation you can flash back to stock with Odin.
Third, Showcase files are not common. Send me a PM and ill give you my email address. I can better help over email.
studdyhalllooser said:
This phone is hard to brick. From nearly every situation you can flash back to stock with Odin.
Click to expand...
Click to collapse
Not true; that's what we call a false sense of security.
add144 said:
Not true; that's what we call a false sense of security.
Click to expand...
Click to collapse
that is true. ive seen phones get restored that have been flashed with roms for other phones and wont even get past the samsung logo. he said nearly, I'm sure you can come up with some weird far out situation but don't try and scare the newbies off this early.
Sent from my MIUI SCH-i500
sageDieu said:
don't try and scare the newbies off this early.
Click to expand...
Click to collapse
What will scare newbies off is when they start flashing crazy **** for another phone in the Phone box in ODIN or something and can't fix it by just ODIN'ing like you guys are suggesting.
add144 said:
What will scare newbies off is when they start flashing crazy **** for another phone in the Phone box in ODIN or something and can't fix it by just ODIN'ing like you guys are suggesting.
Click to expand...
Click to collapse
It's ok he's the only one still here so he'll have to help them.
Sent from my SCH-I500 using XDA App
You say that but the fact that you said it means I'm not the only one.
Ooooohhhh someone's getting technicallllllllll
add144 said:
Ooooohhhh someone's getting technicallllllllll
Click to expand...
Click to collapse
dang right
Sent from my MIUI SCH-i500
Same phone
I have the exact same phone as you. I just rooted my phone for the first time yesterday and I am having trouble installing CWM. Can you explain to me how you used Odin to flash CWM. And after you flash CWM, is it possible to revert back to stock recovery? If so how?