Related
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 I'm in front of the weirdest thing I've ever seen in my Android life. Turns out I got my Infuse 4G and turn it back to stock AT&T Gingerbread 2.3.6 using Heimdall One-click Back-To-Stock UCLB3, and in the middle of process it seems my USB port disconnected my phone and I though I would see a brick, but thank God it was not that bad (I thought). I change the USB port and put my Infuse in download mode again, passed the tool again and everything went like heaven (again: I thought). I got my stock AT&T Gingerbread 2.3.6, but I never seen CWM anymore, I just can't because the weirdest screen I've ever seen (you'll see).
I thought my phone was unrooted, so I maded my way straight to SuperOneClick v2.3.3 and begin the simplest process. Well... it was unable to root my phone and believe me, it's not ADB problems, I know it because I can install apps through Android Commander without any problem... so that's the first weird thing I have here.
Until that moment I thought my phone was bad-flashed or something, so I tried with another tool, the mythic Odin with h8rift's [UCKD5] Odin - Stock (Root+3e) and with my device in download mode it never shown itself as COM## on Odin (required to start the process), however I clicked on PDA button, selected the .tar.md5 file and start the process that never started (logically).
So right now I have no idea what to do or where to go.
I'm apologize if I explain every little detail, the thing is that most of the time one get answers starting with "You did this?" "Have you tried that?" I all I want is to avoid that. For example, I have USB debugging, ok? Another thing someone could ask.
Please help me guys. I madded a video so you can see what happens when I try to enter CWM. Even when my phone starts, during AT&T logo screen flashes with a strange distortion. I madded this video and post it to YouTube so you can see what is hard for me to explain.
Please HELP!
I need anything that from scratch clean everything and put my phone shiny.
Best regards.
You have "rainbows" because you don't have Gingerbread bootloaders.
You need to use odin a GB leak or Heimdall a GB leak to correct the problem.
Your initial failed flash on heimdall was due to a bad connection -usb data cord or computer usb port.
qkster said:
You have "rainbows" because you don't have Gingerbread bootloaders.
You need to use odin a GB leak or Heimdall a GB leak to correct the problem.
Your initial failed flash on heimdall was due to a bad connection -usb data cord or computer usb port.
Click to expand...
Click to collapse
Man I thank you with all my heart... can you give me some resource? Sorry to bother you with that, the problem is I've been reading since yesterday and my head is about to explode.
Please I'll appreciate it.
Best regards.
Stickied "Super Thread" in Development.
Sent from my SAMSUNG-SGH-I997 using xda premium
Radiotsar said:
Stickied "Super Thread" in Development.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks, I'll check it right now
alainalemany said:
Man I thank you with all my heart... can you give me some resource? Sorry to bother you with that, the problem is I've been reading since yesterday and my head is about to explode.
Please I'll appreciate it.
Best regards.
Click to expand...
Click to collapse
There are some links on my signature line, including the superthread.
If reading right, you are on uclb3 now. Soc can't root that. I don't think anything can. You have to load another kernel. Like qkster said see his sig. I used both uclb3 packages two night ago. Both work.
(thanks qk)
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Well that is really a super thread... right now I have no idea what to do, where to go. Please can anyone tell me which option take in order to disappear this "rainbows", root my Infuse and finally can install whatever ROM I want?
Best regards.
EDIT: OK I've installed (again) Heimdall UCLB3 2.3.6 but with the Flash Bootloader box checked and everything goes like heaven, NO MORE RAINBOWS However I can't root it with SuperOneClick v2.3.3, why is that? How can I root it?
Best regards.
I see you have not read either the original post
http://forum.xda-developers.com/showthread.php?t=1524081
there clearly says that the only way to root in 2.3.6 is by flashing DD Entropy512's kernel.
kalebdevil said:
I see you have not read either the original post
http://forum.xda-developers.com/showthread.php?t=1524081
there clearly says that the only way to root in 2.3.6 is by flashing DD Entropy512's kernel.
Click to expand...
Click to collapse
OK I flashed Entropy512's kernel correctly but the problem is now I see only Samsung logo, I'm stuck there. However I can see a red CWM.
qkster said:
You have "rainbows" because you don't have Gingerbread bootloaders.
You need to use odin a GB leak or Heimdall a GB leak to correct the problem.
Your initial failed flash on heimdall was due to a bad connection -usb data cord or computer usb port.
Click to expand...
Click to collapse
Why is it that you can go from froyo stock rooted with cwm recovery straight to flashing zeus for example? What step added the gingerbread bootloaders? Just trying to learn myself!
Sent from my SAMSUNG-SGH-I997 using XDA App
SnowBeer said:
Why is it that you can go from froyo stock rooted with cwm recovery straight to flashing zeus for example? What step added the gingerbread bootloaders? Just trying to learn myself!
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
from froyo with recovery, you can flash any rom. bypassing the bootloader.
a lot of people do this w/o prob until they run into recovery issue.
i'm not sure re: the exact architecture why this occurs.
the kernel gurus can tell you more.
if you use odin, and install one the gb leaks, you will have that BL, until you do a repartition with gtg's ultimate unbrick which brings you back to froyo. I think you will lose the bl's.
In good practice, I use the 1click heimdall w/ repartition - these are packaged with "official" GB leaks. imho, i believe they are better suited for a base to get to your custom GB rom.
if you're running infused 1.6, there is no needed 'cause it's froyo.
no rainbows there
edit: to each his/her own i guess. the reason why gtg's "unbrick" seems like a life saver is due to repartition with PIT files image.
the heimdall 1 click does the same thing but takes the guess work out from the inexperience user.
Hello, I am a long-time viewer of xda but a new member, this is my first post.
(and yes, i looked for a similar theard. i could not find one.)
So, onto the problem.
I flashed Infinitum 1.1.1 to my Infuse using cwm recovery. I noticed problems right off the bat when after i had installed the zip, i rebooted into recovery then it got stuck on the samsung logo and i had to pull the battery (a normal event when flashing this rom) So when i pulled the battery and booted into recovery to try again, the cwm recovery was terribly screwed up. The top half of the screen was pixelated, and the navigation menu was off center. I was still able to use cwm to flash the rom successfully, But cwm remains srewed up.
So i tried to reflash cwm recovery using rom manager. but when i rebooted i was stuck in a recovery boot-loop that i had to get out of using odin.
I then flashed the rom again using the same procedure suggested by its developer, and it worked, but cwm is still acting as it was before. (the pixelated top half of the screen and the off center navigation menu. )
So can i get some help? i thought about removing cwm the using some other recovery. I also heard that cwm wont work on ics, but im unsure what it is.
Thanks in advance.
You don't have Gingerbread bootloaders. That's why recovery looks the way it does.
You need to Odin or Heimdall back to Gingerbread stock (I find Heimdall much easier for this) and then flash Entropy's DD kernel to get back into red recovery to flash Infinitum.
Posts 1 and 2 in this thread are what you need: http://forum.xda-developers.com/showthread.php?t=1524081
lukas_s said:
You don't have Gingerbread bootloaders. That's why recovery looks the way it does.
You need to Odin or Heimdall back to Gingerbread stock (I find Heimdall much easier for this) and then flash Entropy's DD kernel to get back into red recovery to flash Infinitum.
Posts 1 and 2 in this thread are what you need: http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
I i came from froyo, and is there a way to get the bootloaders without reverting to gingerbread stock?
Hard2thexcore said:
I i came from froyo, and is there a way to get the bootloaders without reverting to gingerbread stock?
Click to expand...
Click to collapse
Yeah, ICS recovery doesn't play nice with Froyo bootloaders.
AFAIK, there is no way to get Gingerbread bootloaders without reverting to stock. With Heimdall it's an incredibly simple, and quick process. I just had to do it myself a couple nights ago
lukas_s said:
Yeah, ICS recovery doesn't play nice with Froyo bootloaders.
AFAIK, there is no way to get Gingerbread bootloaders without reverting to stock. With Heimdall it's an incredibly simple, and quick process. I just had to do it myself a couple nights ago
Click to expand...
Click to collapse
Thank man, one more thing, will going back to gingerbread stock work if the only time i have ever used gingerbread was when i used the Zeus rom. The only other thing i have had besides zeus and this ics rom was froyo.
Hard2thexcore said:
Thank man, one more thing, will going back to gingerbread stock work if the only time i have ever used gingerbread was when i used the Zeus rom. The only other thing i have had besides zeus and this ics rom was froyo.
Click to expand...
Click to collapse
Yup, it'll work just fine
Just follow all the instructions for Heimdall to a T (there aren't many) and everything will be fine
Yeah...heimdal is the best way to get bootloaders...odin doesnt always do it and no custom rom includes them that i am aware of...
I had written detailed instructions for another person...ill try and find them and paste it here...
Also-dont use rom manager, that thing is known to cause bricks/bootloops so using it is asking for bad ju-ju lol
Sent from my SAMSUNG-SGH-I997 using XDA
mg2195 said:
Have you tried flashing boot loaders?
Here is how to do it...
1) Download uclb3 heimdal by qckster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your problems should be gone
Download mode instructions
1) pull battery
2) put battery back in
3) hold volume up + down
4) connect phone to PC with USB cable *don't let go of volume*
Just because you were on gingerbread previously does nit mean you have ginger bread boot loaders...I had ginger bread since the first leaks and did not have boot loaders until a month or two ago when I flashed them using those steps above...
Good luck!
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
There you go...follow those instructions and your cwm will be fixed!!!
Also just added it to my op of infinitum...
Sent from my SAMSUNG-SGH-I997 using XDA
Thank you for posting the guide. I literally just got done flashing GB bootloaders to my Infuse because of the rainbow Recovery when I'm on ICS. I used Odin though and used GB loader that a member posted in the AOKP Uniporn thread. I was scared but there really isn't anything to be afraid of. I tried using Heimdall but dang that was nerve racking because I was trying to use it on Mac and it wouldn't let me do the flash.
Jammol said:
Thank you for posting the guide. I literally just got done flashing GB bootloaders to my Infuse because of the rainbow Recovery when I'm on ICS. I used Odin though and used GB loader that a member posted in the AOKP Uniporn thread. I was scared but there really isn't anything to be afraid of. I tried using Heimdall but dang that was nerve racking because I was trying to use it on Mac and it wouldn't let me do the flash.
Click to expand...
Click to collapse
Good deal, glad you got it sorted out. And to clear up some confusion that is in this thread: you don't have to flash an entire Gingerbread rom to get the bootloaders. We all have our preferred ways of doing it, but you CAN flash just the bootloaders.
Here is both a Heimdall and an Odin way to get JUST the bootloaders. That's all that is necessary for someone who has rainbow distortion issues on an ICS or Gingerbread rom.:
See the third post (HERE) in Entropy512's Unofficial CM9 thread for instructions on how to flash just the bootloaders using the Heimdall command line. Or, see the answer to question 1.) in the FAQ of the rooted UCLB3 Odin thread which is HERE.
mg2195 said:
Yeah...heimdal is the best way to get bootloaders...odin doesnt always do it
Click to expand...
Click to collapse
Heimdall is one way to get the bootloaders, and here's how I did it.:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
The second part of your statement isn't true. Odin doesn't do it only when the user can't figure out how to use Odin.
thank you everyone.
Being a creature of habit i ended up flashing to rom and bootloaders using odin. that did indeed fix CWM right up.
GB loader
Jammol said:
Thank you for posting the guide. I literally just got done flashing GB bootloaders to my Infuse because of the rainbow Recovery when I'm on ICS. I used Odin though and used GB loader that a member posted in the AOKP Uniporn thread. I was scared but there really isn't anything to be afraid of. I tried using Heimdall but dang that was nerve racking because I was trying to use it on Mac and it wouldn't let me do the flash.
Click to expand...
Click to collapse
I am trying to get those GB Bootloaders. Would you be able to provide them ? or to provide the AOKP Uniport thread ?
RemiChartier said:
I am trying to get those GB Bootloaders. Would you be able to provide them ? or to provide the AOKP Uniport thread ?
Click to expand...
Click to collapse
Unfortunately I haven't had this device for over 3 years now. You'll have to do some searching for that.
Jammol said:
Unfortunately I haven't had this device for over 3 years now. You'll have to do some searching for that.
Click to expand...
Click to collapse
Thanks, I have found the GG boot.bin and sbl.bin in another thread, I will update later on this thread.
RemiChartier said:
Thanks, I have found the GG boot.bin and sbl.bin in another thread, I will update later on this thread.
Click to expand...
Click to collapse
Where did you find them? Please share...
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.
VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app