[Q] got my broken captivate replaced lost 3 button combo - Captivate General

The power lock button broke on my cappy. So i took it back to AT&T and got a new one. At first the 3 button combo worked, I went to flash to complete stock 2.1 because i was about to go to GB. Well then i lost the three button combo and cant get it back. Should i try to take the phone back saying it wont go into recovery and try to get a new one. Idk if having to get into recovery is a must to them or if they'll say you dont need it. What should i do I got it back to stock 2.2 using kies from 2.1.
I really dont want to put up with a non 3 combo phone. What should I do? Get a JIG or go back to AT&T?

chrisd000111 said:
The power lock button broke on my cappy. So i took it back to AT&T and got a new one. At first the 3 button combo worked, I went to flash to complete stock 2.1 because i was about to go to GB. Well then i lost the three button combo and cant get it back. Should i try to take the phone back saying it wont go into recovery and try to get a new one. Idk if having to get into recovery is a must to them or if they'll say you dont need it. What should i do I got it back to stock 2.2 using kies from 2.1.
I really dont want to put up with a non 3 combo phone. What should I do? Get a JIG or go back to AT&T?
Click to expand...
Click to collapse
Rooting and changing roms voids your warranty, so if you tell them what your up to not only will they not help you, but they may void your warranty. Try a jig, or if you really want to take it back, return the phone to stock and tell them the gps still sux. Good luck
This is my signature, this is my gun. One is for posting, one is for fun.

Im all the way back to stock, Im still showing the correct product code and everything so that shouldnt be a problem. Im just thinking how i can get them to give me a different one. I guess i can say i use recovery to wipe my phone clean every once in a while to speed the phone up. Oh and you need recovery if you get ota updates right

Not a big deal in the least.
If you were going to gingerbread anyway all you need is that first boot into download because once you flash gingerbread bootloaders you will have a working combo.
Its software not hardware, button combo is contained in the secondary bootloader, no reason to replace a phone because of slightly faulty software.

Ok so i guess ill work on getting the three button to work tomorrow then go to gb, cause the three button fix by design gears wasnt taking, thats why i got a little scared, and i guess i better order a JIG. Ive been without one for 10 months but now im a little nervous lol

and i guess once i get a JIG it will completely eliminate the use of the three button combo anyway. Cause im one of those people that goes back to stock on every flash and it would be a pain to have to do the three button fix. So i guess ill order a JIG from mobiletechvideos.com
Though it wouldnt help recovery as much but rom manager will take care of that.

Didn't they have a three button combo fix a while back? I haven't been on here in a while since my captivate is broken but i seem to remember something like that...

Yea i have the zip file to fix it but now my phone wont go into clockwork at all to even install it. It keeps saying signature failed

Did you apply the 3e fix?
Sent from my GT-I9000 using XDA App

chrisd000111 said:
Yea i have the zip file to fix it but now my phone wont go into clockwork at all to even install it. It keeps saying signature failed
Click to expand...
Click to collapse
There's a .zip for that, too. Somewhere in the threads you can find the zip that will get you to recovery. Look for 3e recovery without signatures.

The 3e sticky is at the top of the page...i thought you flashed 2.1, you shouldn't have 3e that is a stock froyo recovery, what did you do?

i had 3 button when i got the phone and then i went back to 2.1 cause i was gonna flash gb. so once i went to 2.1 i was mad that i lost it and updated it to 2.2 through kies thinking i would just take it back to att and thats when all this start happening.
So i got clockwork to work and the three button combo is now working also, so ill just flash gb straight from 2.2. That is fine right its still a stock rom with root but thats it. or should i now go back to 2.1 then get three button and then flash.
I hate that i have to add all these steps compared to before which was so easy and fast.

You can flash gb over whatever. I went from firefly to stock gb.

Thanks alot i should be good to go now, Im never going to go to stock 2.2 unless im taking it back again.
I guess I'm gonna definitely order my JIG today too.

Related

I think I am in trouble

Hello Everyone,
I have a rogers captivate. I was trying to update to 2.3 android using Odin . I followed the whole process as stated. After rebooting, I got AT&T logo??? and the phone will not boot, go into recovery mode, or connect to my computer. Have I messed up my phone. Please advice.
how did you get an AT&T logo if it doesnt boot?
also what part of the process were you at? gingerbread shouldnt give the white ATT screen
it should give the "i9000" screen with gingerbread.
or were you flashing stock ATT first?
there is nothing wrong with having the wrong boot screen AND A FIX WAS RELEASED LAST NIGHT FOR GB
the fix for stock ATT has been out for a while. AND MY STOCK ROM FIXES IT TOO!
did you read the part about the button combos changing with gingerbread? or if you are on the ATT stock, use old button combos. Also you should have found my stock rom link before flashing, info there too!, its in my sig,
you have to give us more information to help you.
I beleive I was installing it to stock ATT first. That is when this happened. I was on Odin one click install. I remember the phone saying "do not disconnect the target". then all the installation was done from odin. This phone had 2.2 from samsung.Right now all that happens is that the phone starts and a flashing att logo on white background stays..
please let me know what other info is needed. i will post it all to the best possible
boot into download mode and flash ATT stock again. something messed up
are you using the "one click odin" or the other odin?
and what gingerbread are you trying after?
how do i do that. i have tried vol up+down+power combo. still the same flashing logo with no menus. i was using one click odin. and i was still on installing stock android. never got the chance to go to 2.3
If you can't get into download mode through the 3 button way you might need the jig. You got lucky since you're still able to boot up some have perma brick so try the jig and flash back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App
HOLD VOL UP + DOWN
the plug in USB to PC.
keep buttons held until screen comes on!
i asked which gingerbread you were going to do AFTER
What is the build number on your phone, 4 numbers printed under the battery, mine is a 1010 for example, which mean oct. Of 2010 is when it was built. Some phones 1010 and after will not accept the one click odin rom and cause a bootloop like you are having, Try an odin package from TRusselo's sig instead.
my packages dont have the bootloaders. that might be whats screwed up with blinking att boot.
need download first before anything. i do have a GB bootloader package separately
something else:
try removing battery,
plug in USB to PC and Phone
Hold both Volume buttons
put battery back in.
should get you download mode
I really have noidea about what gingerbread i was after, i guess i wanted just the stock android without any custom software from samsung. I am total noob here as far as androids go.
the number on the battery say 2010.12.20 and the last forr nos under the battery at s/n are 11.02.
what is a jig. how do i use it. My phone cannot connect to the computer.
When I try to reset my device by any method, whether usb or power combos, it goes into either a. ATT logo flashing every few secs. or b. battery charging logo with nothing happeining.
Also my phone cannot be seen on my computer
gingerbread isnt for noobs
NOT THE DATE ON the battery
UNDER the battery ON THE PHONE
4 digit number
if you dont know what a jig or gingerbread or any of this stuff is,
you shouldnt have touched your friggin phone!
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
GO GOOGLE A CAPTIVATE JIG AND BUY ONE
you wont be able to make one if you cant follow instructions.
that is your only hope. if not your phone is F'ed up perminantly.
your ONLY HOPE AFTER, is if your phone *somehow stops* turning on *forever*
and you send it back for warranty, and play dumb! ..... ..... ... .. .
PROGRAMMING a phone cant be learned it 5 minutes.
HELL you cant even read the friggin instructions (written for experienced users) in 5 minutes
this was an expensive lesson on researching and learning before doing
hitechchef said:
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
Click to expand...
Click to collapse
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Thanks I will try this method
BWolf56 said:
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Click to expand...
Click to collapse
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Oh right.. Wow..
Yep, go read about a JIG (it's pretty simple to use). You can either build it or buy one from mobiletechvideo or ebay.
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Lol That kind of subtly is lost here... noone is picking up on your suggestion...
and thats how its going to stay,
ive said it before with almost the same words.
ive laid out all the tools....
correction of the original problem is necessary,
research is salvation,
resistance is futile.
there it is... i laughed... all is good again...

How I hard bricked my Captivate (FYI)

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...

[Q] Something Wrong With New Captivates?

I just got a Samsung Captivate two days ago, and while trying to root it, I seem to have bricked it. When trying to flash initial root zip in stock recovery, the install always failed because it failed to verify the signature. Then I got the bright idea of ODIN one clicking back to stock, thinking maybe that'd help. Now, if the phone is unplugged, I get a boot loop with the white at&t screen, and if I try to plug it in to get into download mode, it just blinks the battery status screen, showing an empty battery. I tried replacing the battery with a fresh one, but no change. Any help would be greatly appreciated.
should have just ran a search for " captivate signature verification ".. million threads... and fix in my signature...
so you odin flashed to stock then flashed the root kernel?
or just flashed to stock? What stock? there are many. theres 3 odin packages and 4 one clicks just for ROGERS.. there are even more for att. some even ACTUALLY BRICK YOUR PHONE.
having the WRONG kernel for wrong rom causes bootloops.
you are not bricked. bricked your screen doesnt come on.
you really need to research.
Sounds like you flashed jf6 on a froyo shipped phone, losing your 3 button ability in the process.
shagdaddy said:
I just got a Samsung Captivate two days ago, and while trying to root it, I seem to have bricked it. When trying to flash initial root zip in stock recovery, the install always failed because it failed to verify the signature. Then I got the bright idea of ODIN one clicking back to stock, thinking maybe that'd help. Now, if the phone is unplugged, I get a boot loop with the white at&t screen, and if I try to plug it in to get into download mode, it just blinks the battery status screen, showing an empty battery. I tried replacing the battery with a fresh one, but no change. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Please, you have gotto give us a step-by-step on what you did.......especially on what you did !!!!
mrhaley30705 said:
Sounds like you flashed jf6 on a froyo shipped phone, losing your 3 button ability in the process.
Click to expand...
Click to collapse
we have a winner!!
op search usb download mode jig...easy to amke cheap to buy. it eill force dl mode and from there you can flash ANY other stock firmware than JF6...
One click root is much easier than whatever you tried doing
Sent from my SAMSUNG-SGH-I897 using XDA App
I did the same thing. You will have to get the USB jig to reflash it. Get the stock 2.2 ROM and use super one click. Odin can get you back the clock work mod.
Sent from my SGH-I897 using Tapatalk
studacris said:
we have a winner!!
op search usb download mode jig...easy to amke cheap to buy. it eill force dl mode and from there you can flash ANY other stock firmware than JF6...
Click to expand...
Click to collapse
I won! Ok, where's the bacon for winner?

Did I hard brick my infuse?

Sadly I think I hard bricked my phone. Have been waiting patiently for working bluetooth on ICS and once I saw that the awesome Devs here figured it out... needless to say I downloaded CM 9 immediately. So went to flash from Red recovery... got the bootloop on first flash. Did the 3 finger salute to reflash from blue recovery and immediately noticed rainbows. Expecting it, I didnt sweat it. However to my chagrin, I soon found out that the zip file was too far down on the list to be able to see with the glitched rainbow recovery. Bottom line... it ended up with me somehow stuck back in red recovery and unable to install any zip files.
Got home to odin back to stock and it just gets to cache.rfs and does nothing more. Now it will not even boot up. All I can do is get into download mode but hiemdall doesn't recognize it and Odin doesnt get any farther than the cache.rfs step. Went to warrantee it and was told that when they added the iphone to the list of insurable phones that they upped the deductable from 125 to 199 for smartphones. Spending 200 on a infuse is idiocy when for 550 i can get a galaxy S III, (which I already had preordered). Thanks Apple for screwing up the insurance!
So being that I can still get into download mode, is there any way to get this operational again? I was jumping ship to the S III anyways but wanted to give the Infuse to the GF since it was way better than her phone. Any help would be appreciated. Thanks!:highfive:
chipstien said:
Sadly I think I hard bricked my phone. Have been waiting patiently for working bluetooth on ICS and once I saw that the awesome Devs here figured it out... needless to say I downloaded CM 9 immediately. So went to flash from Red recovery... got the bootloop on first flash. Did the 3 finger salute to reflash from blue recovery and immediately noticed rainbows. Expecting it, I didnt sweat it. However to my chagrin, I soon found out that the zip file was too far down on the list to be able to see with the glitched rainbow recovery. Bottom line... it ended up with me somehow stuck back in red recovery and unable to install any zip files.
Got home to odin back to stock and it just gets to cache.rfs and does nothing more. Now it will not even boot up. All I can do is get into download mode but hiemdall doesn't recognize it and Odin doesnt get any farther than the cache.rfs step. Went to warrantee it and was told that when they added the iphone to the list of insurable phones that they upped the deductable from 125 to 199 for smartphones. Spending 200 on a infuse is idiocy when for 550 i can get a galaxy S III, (which I already had preordered). Thanks Apple for screwing up the insurance!
So being that I can still get into download mode, is there any way to get this operational again? I was jumping ship to the S III anyways but wanted to give the Infuse to the GF since it was way better than her phone. Any help would be appreciated. Thanks!:highfive:
Click to expand...
Click to collapse
You need to reboot your computer or something and get into download mode. Odin WILL flash it. Or use one of the one click kernel/recovery downloads and flash it.
You can get it working, it will just take some time and tricks.
I wish everyone was local so I could drive over and save the day!
chipstien said:
Sadly I think I hard bricked my phone. Have been waiting patiently for working bluetooth on ICS and once I saw that the awesome Devs here figured it out... needless to say I downloaded CM 9 immediately. So went to flash from Red recovery... got the bootloop on first flash. Did the 3 finger salute to reflash from blue recovery and immediately noticed rainbows. Expecting it, I didnt sweat it. However to my chagrin, I soon found out that the zip file was too far down on the list to be able to see with the glitched rainbow recovery. Bottom line... it ended up with me somehow stuck back in red recovery and unable to install any zip files.
Got home to odin back to stock and it just gets to cache.rfs and does nothing more. Now it will not even boot up. All I can do is get into download mode but hiemdall doesn't recognize it and Odin doesnt get any farther than the cache.rfs step. Went to warrantee it and was told that when they added the iphone to the list of insurable phones that they upped the deductable from 125 to 199 for smartphones. Spending 200 on a infuse is idiocy when for 550 i can get a galaxy S III, (which I already had preordered). Thanks Apple for screwing up the insurance!
So being that I can still get into download mode, is there any way to get this operational again? I was jumping ship to the S III anyways but wanted to give the Infuse to the GF since it was way better than her phone. Any help would be appreciated. Thanks!:highfive:
Click to expand...
Click to collapse
Yes you did...you hard brick it...
Naa if you have download mod your golden....i say use the one click method to get gb back on and you can put gb bootloader on also...run this twice, just don't close the program heimdall after the first boot, second time check the bootloader box...run it again...
http://forum.xda-developers.com/showthread.php?t=1524081
scottx . said:
You need to reboot your computer or something and get into download mode. Odin WILL flash it. Or use one of the one click kernel/recovery downloads and flash it.
You can get it working, it will just take some time and tricks.
I wish everyone was local so I could drive over and save the day!
Click to expand...
Click to collapse
I would do the same exact same thing. I LOVE helping with stuff like this. I always rooted/jailbroke
my friends phones at no charge when other people on Craiglist or friends would charge to use the SAME exact software
:good:.
I have the same problem as the OP. both Odin and heimdall seem to freeze midway through the flashing process. My phone has been out of commission since yesterday and I can't figure out the fix yet. I've tried bootloaders with heimdall one click, still no go.
nickg2027 said:
I have the same problem as the OP. both Odin and heimdall seem to freeze midway through the flashing process. My phone has been out of commission since yesterday and I can't figure out the fix yet. I've tried bootloaders with heimdall one click, still no go.
Click to expand...
Click to collapse
Let it get a charge and try again...
Try using another computer...
Sent from my SAMSUNG-SGH-I997 using xda premium

[Q] Clockworkmod Recovery updated, can't enter recovery mode

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

Categories

Resources