Related
So I finally decided to attempt to flash my phone, but realized I have a build 1010. After reading about all the issues with flashing back with ODIN not working or disabling the 3 button download mode after using, I'm nervous now. I consider myself fairly tech savvy, but get easily frustrated. I downloaded Bay-wolf's AIO Tool and it took the phone into Download Mode without trouble, should this still work after flashing a new ROM, or will this not work just like the 3 button combo?
I really want to flash a custom ROM, but should I want to try another or flash back to stock, I would really like for it to not be a horrible or complicated process.
TIA
Seanbest said:
So I finally decided to attempt to flash my phone, but realized I have a build 1010. After reading about all the issues with flashing back with ODIN not working or disabling the 3 button download mode after using, I'm nervous now. I consider myself fairly tech savvy, but get easily frustrated. I downloaded Bay-wolf's AIO Tool and it took the phone into Download Mode without trouble, should this still work after flashing a new ROM, or will this not work just like the 3 button combo?
I really want to flash a custom ROM, but should I want to try another or flash back to stock, I would really like for it to not be a horrible or complicated process.
TIA
Click to expand...
Click to collapse
Yeah, I have build 1010. Flashed back via odin 1 click and needed a jig to get my phone working again. Then I found this post:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I've used this method several times and it's worked like a charm every time.
I have never lost three button combo from flashing a rom. I think that its more a concern for those who do not have it, which you obviously do, you got into dl mode.
There is a procedure out there for flashing stock in build 1010. It its not at easy as one click but it works
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
If your posting this you are going to flash. it is just a matter of when, tonight? ;p
Edit: beat me to it
mcord11758 said:
I have never lost three button combo from flashing a rom. I think that its more a concern for those who do not have it, which you obviously do, you got into dl mode.
There is a procedure out there for flashing stock in build 1010. It its not at easy as one click but it works
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
If your posting this you are going to flash. it is just a matter of when, tonight? ;p
Edit: beat me to it
Click to expand...
Click to collapse
bahaha XD
Just barely
I also have a build 1010 phone, and have used odin 1-click about a dozen times. Works great. I also keep a jig handy just in case, and would advise the same if you want to try odin 1-click. If it works, it's a bit easier than the other method.
Good luck!
My 3 button combo stopped working after flash, but it's no big deal, just use the android dev kit and a little command prompt. No biggie. Flash away!
Sent from my SAMSUNG-SGH-I897 using XDA App
bobtukin said:
My 3 button combo stopped working after flash, but it's no big deal, just use the android dev kit and a little command prompt. No biggie. Flash away!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
What's that?
Just got for it :]] You have a whole community to help you if you screw up. At least there's plenty of ways of flashing/reverting back to stock/and plenty froyo flavors to try. Rewind back two months ago and there were waaayy too many noobs that bricked their phones and only half the cool froyo-ness the xda developers came out with. 2.1 Eclair is too much of a kill-joy on this phone. You won't regret it.
Seanbest said:
What's that?
Click to expand...
Click to collapse
You can use the android sdk tools (ADB command prompts) (Think ms-dos) to put the phone into download/recovery mode if you lose the 3-button ability.
Just use the program in my signature to flash. Select the 3 button fix option and you're good to go. It's the AIO Captivate Toolbox in the Captivate Development section in case you can't see my signature.
I got a build 1010, must have done odin 1-click about 300 times now.
bay_wolf said:
Just use the program in my signature to flash. Select the 3 button fix option and you're good to go. It's the AIO Captivate Toolbox in the Captivate Development section in case you can't see my signature.
Click to expand...
Click to collapse
Already using it, it's how I enabled non-market apps and already tested Download Mode. Awesome app btw.
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
rufex2001 said:
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you test the phone to make sure it can accept the button combinations to go into download mode (almost all do, except for a batch of faulty ones), there is almost nothing you can do that will truly "brick" the phone. A bad or interrupted flash will result in a boot loop, which you can recover from by forcing download mode, and using Odin to reflash back to stock.
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Basically what causes a brick in any electronic equipment is from an interruption/error in any boot critical files. The item does not have the proper/complete instruction to turn on. You could say it is like starting a car being told to first put the key in
Sent from my SAMSUNG-SGH-I897 using XDA App
If you can use the 3 button combos to get into download or recovery mode, you are good to go. The only danger would be a bad Odin flash, but even so you'll have a chance to recover it by making a cheap USB jig (3 100k Ohm resistors into pins 3 and 4, I think, of the usb port) or buying one. This will boot the phone straight into Download mode.
When using Odin, there is only one stage where you can brick your phone for good, during the bootloader copy process, which probably takes less than a second.
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
rufex2001 said:
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
Click to expand...
Click to collapse
My Cappy is a 1007 build, too. I've soft bricked my phone more times than I can count, but Odin hasn't had anything to do with it. It can do it, though.
At one time in my life I flashed a new ROM every day, and I used Odin every time before I flashed.
On a side note, back when I flashed my first ROM, I pulled the battery during the first boot, dropped it, and then flashed another ROM without using Odin, and it never bricked it, so that should give you a good idea of how hard it is to brick these phones. Lol
Stupidity.
Sent from my Captivate.
opcow said:
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Click to expand...
Click to collapse
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
No odin really is not that bad just don't unplug it while it is running. You would not want to unplug your computer when flashing a new bios
Sent from my SAMSUNG-SGH-I897 using XDA App
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Sorry for any dumb or repeated question I may be asking.
Sent from my SAMSUNG-SGH-I897 using XDA App
Pierce533 said:
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
Click to expand...
Click to collapse
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
rufex2001 said:
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Click to expand...
Click to collapse
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
opcow said:
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
Click to expand...
Click to collapse
Thanks for the info. Is there a stock I897UCJF6 ROM that can be flashed with CWM? I haven't been able to find one and if there is one I would like to have one around to use. Thanks for taking the time to answer my questions.
opcow said:
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
Click to expand...
Click to collapse
That is exactly the sort of thing I had in mind! So I guess I could keep a CWM update.zip and a stock rom update.zip and some custom roms and just do everything directly from the phone and without Odin, right? Or am I missing something?
Sent from my SAMSUNG-SGH-I897 using XDA App
Guns don't kill people
opcow said:
Odin isn't bad so much as an unnecessary risk. Then there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build.
Click to expand...
Click to collapse
Yep. I have build 1008 that has always had the 3-button combo and lost it after using ODIN 1-click (I restored the combo with a later flash).
I believe opcow and others when they say that flashing back to stock is unnecessary. I just don't understand why the authors of some of these ROMs leave this as part of their installation guide.
Sent using XDA App
Pay close attention to the options in recovery when you are using a custom rom. It's part of the custom kernal, and of used properly can help you avoid odin. I avoid it because I have a mac and odin won't run on anything but windows. Custom recovery will allow you to format every part of the OS but the sbl.bin. Also in some custom recoveries there is an option to mount usb. This will allow you to format the internal sd then copy a new rom.zip and flash if you really want a clean flash. If your doing this make sure you are able to mount your sd before you format anything. Avoid stock 2.2 kernals because they have 3e recovery. There are ways around that but they have to be in play before you end up in a bootloop.
3e recovery + bootloop= odin recovery "only option".
Make sure lag fix for rom kernal A understands lag fix for rom kernal B. Also usually only a concern for stock 2.2 kernal. Other than that really hard to brick this phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
ryude said:
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
Click to expand...
Click to collapse
Could you please explain what a wipe ROM is? Thanks
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
bvsbutthd101 said:
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
Click to expand...
Click to collapse
what are the steps you're using in odin? put the battery back in to flash stuff (if you don't already have it in) if it keeps failing... also what are you trying to flash and where are you trying to end up rom/kernel wise?
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
bvsbutthd101 said:
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
Click to expand...
Click to collapse
Yeah if an odin flash fails and you unplug it and boot it up it will start the last rom you were running. You can still get it into download mode for odin right? Strange that its not flashing right... Try using a different USB port on your pc (as well as plug in your pc for good measure), disable any antivirus software you may have or run Odin as administrator, then put the battery back in for odin as always only use PDA and/or PIT sections
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
bvsbutthd101 said:
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
Click to expand...
Click to collapse
I probably would've tried a little more to fix it, its extremely hard to brick this phone or make it so you can't recover or get back to stock... anyways thats good, hope its easier to odin with the new one
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
bvsbutthd101 said:
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
Click to expand...
Click to collapse
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
anoninja118 said:
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
Click to expand...
Click to collapse
Exactly, pretty important part if I do say so myself. I'm happy though. They didn't give any problem. I didn't even ask to get a new phone. They just told me that we'll just send one out to you.
Hey well, to start things off I was trying to unlock my T-Mobile SGS4G to work with AT&T but it turns out it needs to be rooted first. I have rooted before and this is the first time I have ran into a problem.
What I did first:
I used Heimdall in an attempt to flash CWM Recovery so I can gain root access. For some reason the zImage was bad (?) and my phone could only get to the T-Mobile logo and then freeze.
Recovery and Download DID work
What I did second:
I used odin3 to flash back a stock T-Mobile rom in hope to fix things... and it did everything succesfully but now it's stuck in a real boot loop.
Can't get into Recovery, nor Download. It's really depressing to keep seeing that battery show over and over again.
Any ideas on how to get my computer to detect my phone again?
Thanks.
Edit:
I did every button combination + usb plug combination known to man. I uninstalled and installed the files again.
Did my phone brick because I ticked the partition tab on odin?
PLEASE help.
Our phone IS NOT the Vibrant. Hopefully someone can help you, but... I don't know. If you flashed OUR stock rom, with bootloaders... you're screwed. But, the fact you have images on your screen, should give you some hope.
Yea, I saw that, but the title says he has a vibrant. I don't know....
Head to the vibrant forum there are some un-brick tools over there...you need to get it in download mode use odin to flash stock froyo vibrant rom.. Should get it back up and running
Sent from my SGH-T959V using xda premium
Kingarabian said:
T-Mobile SGS4G
Click to expand...
Click to collapse
Just to verify, pull out your battery and check if you have the SGH-T959V
One of the "download jigs" may help once you are certain which phone you have and what firmware and ROM you need to flash. You can make your own with a resistor and a microUSB plug, I bought one for $8.00, delivered, (I now see they have them on Amazon for $4, Super Saver eligible) and others have had good luck with even cheaper ones on eBay.
Also: http://forum.xda-developers.com/showthread.php?p=9403915
Jigs are cheap and unless you got the right resistor lying around buy a ready made one. Also if the phone shows up in odin you can download something whatever picture shows up on the screen. Raver has a thread about using heimdall to fix the boot files but its about six months old. Worked for me once. It might even be indexed in the bible under development.
Sent from my SGH-T959V using xda premium
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