so I was trying to flash the new miui 1.7.8 on my captivate and one of the step is to flash back to orig.
using odin 1.7 when I flash the phone its gone.
1- No power
2- PC doesnt recog the phone at all
3- charger not charging
so basically the phone wont come or wont charge.
tried one button to boot up in recovery but no luck...any idea?
maxximboy1 said:
so I was trying to flash the new miui 1.7.8 on my captivate and one of the step is to flash back to orig.
using odin 1.7 when I flash the phone its gone.
1- No power
2- PC doesnt recog the phone at all
3- charger not charging
so basically the phone wont come or wont charge.
tried one button to boot up in recovery but no luck...any idea?
Click to expand...
Click to collapse
What were you on before trying to flash? The newest Miui rom does not state nor is it required to flash back to stock using ODIN. What happened with ODIN when going back to stock? Did you not try using ODIN 1 click? Please give much clearer detail on your process if we want/try to help you.
i was on apex 8.x and thinking to go back to miui again. it said if you are on cm7 or miui then dont need to flash back to orig.
and since i was not, i use odin 1.7 and use cm7 initial kernel to flash my captivate. it flash successfully and when i tried to reboot phone there were no pwer and no charging.
thankx
maxximboy1 said:
i was on apex 8.x and thinking to go back to miui again. it said if you are on cm7 or miui then dont need to flash back to orig.
and since i was not, i use odin 1.7 and use cm7 initial kernel to flash my captivate. it flash successfully and when i tried to reboot phone there were no pwer and no charging.
thankx
Click to expand...
Click to collapse
Is apex 8 on 2.3 bootloaders? If so that could have been part of the issue. Miui runs 2.2 boatloaders so if you didn't flash to 2.1 or 2.2 before going back it's possibly why your phone is currently dead. Doesn't mean it's bricked. Search in the general forum for adamoutletter or someone close to that for a thread on recovering from hard bricks.
Glitch kernel let me OC to 1.4!
What .tar did you use with odin to flash back to stock? (don't say the one with the 3 button fix)
if it's a Hard brick, only option is jtag. Mobiletechvideos.com offers that service for $50 u.s. His username on here is connexion2005.
Sounds like Stud hit the nail on the head. You're not screwed, just not a happy person.
"Is apex 8 on 2.3 bootloaders? If so that could have been part of the issue. Miui runs 2.2 boatloaders so if you didn't flash to 2.1 or 2.2 before going back it's possibly why your phone is currently dead. Doesn't mean it's bricked. Search in the general forum for adamoutletter or someone close to that for a thread on recovering from hard bricks.
Glitch kernel let me OC to 1.4!"
===
tried but have no idea how to use usb or other way of jig....sorry not that technical
my phone is under warranty as of purchase date, what if i send to samsung will they know?
maxximboy1 said:
"Is apex 8 on 2.3 bootloaders? If so that could have been part of the issue. Miui runs 2.2 boatloaders so if you didn't flash to 2.1 or 2.2 before going back it's possibly why your phone is currently dead. Doesn't mean it's bricked. Search in the general forum for adamoutletter or someone close to that for a thread on recovering from hard bricks.
Glitch kernel let me OC to 1.4!"
===
tried but have no idea how to use usb or other way of jig....sorry not that technical
my phone is under warranty as of purchase date, what if i send to samsung will they know?
Click to expand...
Click to collapse
I'm not sure if Sammy'll know or not. Others maybe be able to lend you some advice as far as that goes. In all honesty, I'd avoid troubles and shoot connexion2005 a PM. I'm pretty sure he'll be able to fix it regardless of what's wrong with it. If it indeed is that you flashed over 2.3 BL, I'd say it's your best bet.
I mean Samsung might warranty, but I'm not sure, so I'm not going to say that they will or won't.
thax sending him msg
Related
Hi guys,
Can anyone tell me how to remove a bootloader or switch it to another bootloader?
I accidently flashed GT-I9000 bootloader onto my captivate and now my phone thinks that it's GT-I9000.
In bootup, a screen of "Galaxy GT-I9000 Samsung" stays on for 5 sec, and then AT&T logo&animation shows up after that.
Below is the full explanation how I ended up with this situation. It's kinda long, so if you know the solution to this problem right away, I guess you don't need to read all of it.
Anyways, thanks in advance!
So Here's what happened. I was upgrading my (rooted/froyo) captivate to gingerbread (continuum v5.4.1) In the instruction, it suggested to return to stock so I did that and my phone went back to eclair.
Then there was another optional suggestion saying that "only if you don't have bootloaders - install JVB bootloaders" and that's where my problem began.
I downloaded the 'galaxys-bootloader-JVB.tar.md5' and flashed it in Odin and my phone now thinks that it's GT-I9000. For a moment, I thought my phone was bricked, but I managed to turn it back to 2.1.
but still whenever I turn on my phone the 'Galaxy S GT-I9000 Samsung' screen shows up for like 8 seconds and then move onto AT&T screen.
Phone still operates and runs on eclair, but funny thing is every time I want to use "download mode" I have to press 'Volume down key + power, which is for Vibrant or Fascinate, instead of holding both volume up + down keys, which is for Captivate.
Same thing for "recovery mode" I have to press down VOL down + power button. This clearly shows that the phone thinks it's Vibrant, not Captivate.
Please Please Please can anybody tell me how to revert it?
samzoferrari said:
Hi guys,
Can anyone tell me how to remove a bootloader or switch it to another bootloader?
I accidently flashed GT-I9000 bootloader onto my captivate and now my phone thinks that it's GT-I9000.
In bootup, a screen of "Galaxy GT-I9000 Samsung" stays on for 5 sec, and then AT&T logo&animation shows up after that.
Below is the full explanation how I ended up with this situation. It's kinda long, so if you know the solution to this problem right away, I guess you don't need to read all of it.
Anyways, thanks in advance!
So Here's what happened. I was upgrading my (rooted/froyo) captivate to gingerbread (continuum v5.4.1) In the instruction, it suggested to return to stock so I did that and my phone went back to eclair.
Then there was another optional suggestion saying that "only if you don't have bootloaders - install JVB bootloaders" and that's where my problem began.
I downloaded the 'galaxys-bootloader-JVB.tar.md5' and flashed it in Odin and my phone now thinks that it's GT-I9000. For a moment, I thought my phone was bricked, but I managed to turn it back to 2.1.
but still whenever I turn on my phone the 'Galaxy S GT-I9000 Samsung' screen shows up for like 8 seconds and then move onto AT&T screen.
Phone still operates and runs on eclair, but funny thing is every time I want to use "download mode" I have to press 'Volume down key + power, which is for Vibrant or Fascinate, instead of holding both volume up + down keys, which is for Captivate.
Same thing for "recovery mode" I have to press down VOL down + power button. This clearly shows that the phone thinks it's Vibrant, not Captivate.
Please Please Please can anybody tell me how to revert it?
Click to expand...
Click to collapse
Odin3 one click back to stock. Your fine that's just the kernel bootloader. If you want continuum it will have the GT-I9000 bootloader, but there are other roms and kernels without it. The odd button combinations you have to use are part of the kernel as well. Flash stock then I suggest flashing Cognition after if it will not revert to stock kernel. You can flash froyo over eclair without having to update bootloaders. Also if your running a AT&T Captivate you should be having that boot animation before the GT-I9000 anyways. Sorry if this doesn't help your problem.
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
First, the new button combos are not part of the kernel. They are part if the secondary bootloader. If you think you are going to flash another gingerbread rom in the future, just leave it as is. They are compatible with 2.1/2.2 roms, with the exception of Cognition. DO NOT FLASH COGNITION UNTIL YOU ARE 150% CERTAIN YOU HAVE FROYO/ECLAIR BOOTLOADERS. The reason is, cog adds a secondary bootloader(sbl.bin) to its flash. If you try mixing aGB primary bootloader with a froyo secondary, you will have a permanent, can't recover, $500 paperweight, brick. Also, do not try to use the odin with 3 button fix, for the same reason above.
mrhaley30705 said:
First, the new button combos are not part of the kernel. They are part if the secondary bootloader. If you think you are going to flash another gingerbread rom in the future, just leave it as is. They are compatible with 2.1/2.2 roms, with the exception of Cognition. DO NOT FLASH COGNITION UNTIL YOU ARE 150% CERTAIN YOU HAVE FROYO/ECLAIR BOOTLOADERS. The reason is, cog adds a secondary bootloader(sbl.bin) to its flash. If you try mixing aGB primary bootloader with a froyo secondary, you will have a permanent, can't recover, $500 paperweight, brick. Also, do not try to use the odin with 3 button fix, for the same reason above.
Click to expand...
Click to collapse
Secondary as in the 3rd animation because I highly doubt that.You should have an AT&T screen, then your galaxy s bootloader, then your rom bootloader. the rom bootloader animation is changable and does not include the power button volume up combo. I'm not a developer, but based on my experience you CAN use odin with 3 button fix over contiuum and then flash cognition after. I highly doubt there will be a brick. For example, you want the new cm7 build. You can flash odin 3 button, flash cmw through rom manager or a zip with 2e recovery. Then flash cognition. you are at the 2.2 bootloader now. You can now begin to work towards the 2.3.4 without any issues. And there are different requirements for different gingerbread roms. some are 2.3.3 and some are 2.3.4 and you CAN NOT flash between the two.
samzoferrari said:
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
Click to expand...
Click to collapse
It's no big deal don't let this guy make you think your about to brick if your not 150% sure. There are also different bricks and this could cause a soft which is also recoverable by odin.
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
Click to expand...
Click to collapse
Just for safety's sake, though, it would probably be good to read through this before moving forward:
The Definitive Guide to Bricking
jmtheiss said:
Just for safety's sake, though, it would probably be good to read through this before moving forward:
The Definitive Guide to Bricking
Click to expand...
Click to collapse
That guide knows a lot more then I do. I suggest reading that aswell! I was speaking strictly based on experience.
If you attempt to flash the 3 button fix with gb bootloaders, you will brick. Go ask any one in gb rom forum. If you reflash froyo bootloaders, to replace gb bootloaders, before you flash 3 button, you should be ok. But if you choose to believe the other guy, and your still under warranty, tell att that your phone stopped working when you tried to update with kies.
EsotericSYN said:
Secondary as in the 3rd animation because I highly doubt that.You should have an AT&T screen, then your galaxy s bootloader, then your rom bootloader. the rom bootloader animation is changable and does not include the power button volume up combo. I'm not a developer, but based on my experience you CAN use odin with 3 button fix over contiuum and then flash cognition after. I highly doubt there will be a brick. For example, you want the new cm7 build. You can flash odin 3 button, flash cmw through rom manager or a zip with 2e recovery. Then flash cognition. you are at the 2.2 bootloader now. You can now begin to work towards the 2.3.4 without any issues. And there are different requirements for different gingerbread roms. some are 2.3.3 and some are 2.3.4 and you CAN NOT flash between the two.
Click to expand...
Click to collapse
Cm7 doesn't use gb bootloaders
Please don't double post.
Miami_Son said:
Please don't double post.
Click to expand...
Click to collapse
I apologize. The tone conveyed by the person I was responding to simply infuriated me. I do know better, just lost it for a second.
Flashing a New rom from Mosaic II
mrhaley30705 said:
Cm7 doesn't use gb bootloaders
Click to expand...
Click to collapse
So not to dig up an old post, but I guess I will...
I am running
Mosaic II
Kernel 2.6.35.7-I9000XWJVB-CL118186
2.3.3
So basically in the same boat as the OP. Running GB boot loaders for the I9000, I'm ready for a new ROM and for the first time I'm worried about a perma brick.
I am wanting to load up CyanogenMod 7
http://forum.xda-developers.com/showthread.php?t=978150
What do I need to do abt the boot loaders, can I leave them and just flash with ClockworkMod Recovery?
Thanks!
JP
Don't **** with the bootloaders. flash back and keep them stock. It's risky and unneeded. Flashing them for ANY ROM is retarded. The developers who require this are retarded. RETARDED.
The only reason to upgrade bootloaders is for the unofficial 2.3 upgrade... Which is likely laziness on Samsung's part. Do not go flashing a SBL without a PBL ever. This is bad practice and can only lead to several bricks when a SBL is released without a matching PBL. The developers who require flashing a SBL without a PBL are retarded. RETARDED.
Yep. I said it, we have retarded developers here in the forums who should be stripped of their recognized tag.
OK on the subject but not so much.... Is there a code or system manager (like sgs tools) that indicates what BL you have installed?
Or does the kernel spell that out for you? ex. Kernel version 2.6.35.7-i9000xxjvr-clCL425308 Would this indicate a i9000 BL?
I notice on the rom I use, people are asking constantly which BL is the right one!
I understand both have their + & - but there must be a way of finding which one is installed, through the phone
tomween1 said:
OK on the subject but not so much.... Is there a code or system manager (like sgs tools) that indicates what BL you have installed?
Or does the kernel spell that out for you? ex. Kernel version 2.6.35.7-i9000xxjvr-clCL425308 Would this indicate a i9000 BL?
I notice on the rom I use, people are asking constantly which BL is the right one!
I understand both have their + & - but there must be a way of finding which one is installed, through the phone
Click to expand...
Click to collapse
Hold Vol - and Power for about 10 seconds. If you reboot to download, you have the I9000 GB bootloaders. That's at least one variable eliminated.
If, after doing that, you realize you're on a Gingerbread rom without issues and the button combo does nothing, you have the i897 GB bootloaders.
jmtheiss said:
Hold Vol - and Power for about 10 seconds. If you reboot to download, you have the I9000 GB bootloaders. That's at least one variable eliminated.
If, after doing that, you realize you're on a Gingerbread rom without issues and the button combo does nothing, you have the i897 GB bootloaders.
Click to expand...
Click to collapse
Sorry should have stipulated.... other then the step you've mentioned.
I was looking to see if anyone has created a script or app that can tell you this
Hi!
I've ordered a cappy from ebay, it was listed as bricked with download mode stuck. How can i reflash it if i don't know what rom has been installed on it (froyo or gb)? I don't want to permanently brick it so i ask for your help. I don't have it yet but it's better to know the know hows. Any tips, suggestions would be greatly appreciated! Thanks!
use Odin 1 Click. It will load the bootloaders for Eclair 2.1. As far as I have read, it won't brick it. Earlier, I installed the one click Cognition Gingerbread, and I was able to go back to stock using One Click Odin.
Whatever you do, don't use the 3-button fix to go back to stock from Gingerbread - it will certainly brick it by mixing bootloaders.
Disclaimer: I am not responsible if it bricks!
Thanks, i will try that.
Beware though that My very first captivate had this problem and it wasn't software issue, I had dropped the phone and afterwards it would only boot into download mode, the only way I could get it to boot the OS was a flash, but the download mode would show back up later on. I had it replaced under warranty, that was 3 cappies ago, should be recieving the third today in the mail
so i have a captivate that ive had for a little while now. and of course ive flashed a few different gingerbread roms like usual.
anyways i wanted to try a froyo from so i used the odin 1 click stock tool to flash back to jf6,
that worked, but for some reason it wont allow me to master clear.
also my phone keeps switching between showing service, and a blue circle with a cross out sign....
(no internet access)
if i flash a rom over it, it starts acting like normal again
any idea whats wrong or whati can do?
thanks!
USB Debugging is need to do master clear. Did you turn on debugging?
speedy_11 said:
USB Debugging is need to do master clear. Did you turn on debugging?
Click to expand...
Click to collapse
yeah it was enabled.
The_Zodiac said:
so i have a captivate that ive had for a little while now. and of course ive flashed a few different gingerbread roms like usual.
anyways i wanted to try a froyo from so i used the odin 1 click stock tool to flash back to jf6,
that worked, but for some reason it wont allow me to master clear.
also my phone keeps switching between showing service, and a blue circle with a cross out sign....
(no internet access)
if i flash a rom over it, it starts acting like normal again
any idea whats wrong or whati can do?
thanks!
Click to expand...
Click to collapse
This happened on one of my old cappies that i got replaced. It was a 1008 build. It's an error in the efs folder. Did you make a backup of your efs folder before you started flashing?
If you didn't here's a method that worked for me that might get you back to normal. What i did was use Kies mini to upgrade to stock 2.2 then make sure the botton combos were working (vol up+dwn/plug usb to get to download mode, and vol up+vol dwn + power to get to recovery.) If those are working, now flash back to stock using Odin 1 click.
This wokred for me. hope it helps.
If you have your original efs folder, use Root Explorer to place the original folder ni place of the current one while on stock 2.1, then reboot to see if it worked.
What Gingerbread Roms did you "play" around with, I'm guessing you used the I9000 bootloaders also?
jack man said:
This happened on one of my old cappies that i got replaced. It was a 1008 build. It's an error in the efs folder. Did you make a backup of your efs folder before you started flashing?
If you didn't here's a method that worked for me that might get you back to normal. What i did was use Kies mini to upgrade to stock 2.2 then make sure the botton combos were working (vol up+dwn/plug usb to get to download mode, and vol up+vol dwn + power to get to recovery.) If those are working, now flash back to stock using Odin 1 click.
This wokred for me. hope it helps.
If you have your original efs folder, use Root Explorer to place the original folder ni place of the current one while on stock 2.1, then reboot to see if it worked.
Click to expand...
Click to collapse
im not sure what build because its a replacement from att and they didnt put the build number on the sticker.
i did backup the efs folder so i can try that.
melbourne408 said:
What Gingerbread Roms did you "play" around with, I'm guessing you used the I9000 bootloaders also?
Click to expand...
Click to collapse
a few apex, dvlevs, obsession. and yes i loaded gb bootloaders.
does jf6 flash you back to eclair bootloaders?
The_Zodiac said:
im not sure what build because its a replacement from att and they didnt put the build number on the sticker.
i did backup the efs folder so i can try that.
a few apex, dvlevs, obsession. and yes i loaded gb bootloaders.
does jf6 flash you back to eclair bootloaders?
Click to expand...
Click to collapse
Your going to want to flash back to eclair (imho) or froyo if you'd rather, but it will have to be done through odin without a 1 click method. If you know what I'm talking about all good. If not lemme know and I'll help ya to the links, cleaning the kitchen atm but its all good
Sent From My Swaggin 1.6 Son Of A Glitch
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
studacris said:
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
Click to expand...
Click to collapse
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
The_Zodiac said:
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
Click to expand...
Click to collapse
Couple things for the Master Clear
1. Make sure to shut down Odin then restart it without the phone connected
2. If that doesn't work restart your PC
3. If all else fails, root, install ROM Manager, get into CWM and do a factory reset
Like Studacris said, Odin to JF6 flashes the proper bootloaders, so you dont need to worry there. I've done it TONS of times
Edit** Are you using this Odin?
http://www.mediafire.com/?0w2y31maz8mdom4 If not, I would HIGHLY recommend using it
studacris said:
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
Click to expand...
Click to collapse
Dam, bad correlation on my part. Didn't want anything going wrong with bootloaders, my self learned fault on being incoherent and half asleep, just didn't want any brick brick brickety brick bricks-as my dad laughs to me all the time. Thanks for the correction.
Sent From My Swaggin 1.6 Son Of A Glitch
I'll try to follow up on what Studa was going for.
The_Zodiac said:
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
Click to expand...
Click to collapse
Ok, but that would be a good thing, you can just use the signal problem as an added reason for sending it in. If you can flash stock and it boots, all is well. Anything else just goes in your favor of why you deserve a new one.
Plus, if the phone stops working to the point it does not boot they will have no real way of telling what was running before, nor will they waste the time to find out. It will get tossed into the re-write pile, and go thru the paces for becoming a referb.
You do realize that the phone has to be regularly on to do a master clear and not be in download mode right?
dsilvan55 said:
You do realize that the phone has to be regularly on to do a master clear and not be in download mode right?
Click to expand...
Click to collapse
yes i do...
Reflash the stock jf6 with no sim card
Sent from my GT-I9000 using XDA App
Ok guys this is what i did...my friend said his phone was a samsung infuse 4g so i use the guide to root his phone..when i flash a rom on the phone come to find out it was a damn samsung captivate now it want do anything..but i can still get into the download mode..can someone guide me to the right thread
Maybe you should try with http://forum.xda-developers.com/showthread.php?t=1153310. If u can get into download mode should be easy to fix. What it's does when u turn it on?
Darkuso said:
Maybe you should try with http://forum.xda-developers.com/showthread.php?t=1153310. If u can get into download mode should be easy to fix. What it's does when u turn it on?
Click to expand...
Click to collapse
ITS DOING THIS http://www.youtube.com/watch?v=oDWmGrUPFjw
If you can get to download mode just try flashing any of Captivate ROM's (preferably stock).
gogoad said:
If you can get to download mode just try flashing any of Captivate ROM's (preferably stock).
Click to expand...
Click to collapse
As gogoad says, u can try with this http://forum.xda-developers.com/showthread.php?t=731989 that will leave the phone like new. But careful, dont unplug the phone in the process. There is http://forum.xda-developers.com/showthread.php?t=995143 too and it is safer but dosent contain bootloaders.
gogoad said:
if you can get to download mode just try flashing any of captivate rom's (preferably stock).
Click to expand...
Click to collapse
i know this is a damn question...but do i use one-click to flash a rom from download mode
thank you guys this thread can be deleted cause....ITS FIX FIX FIX FIX!!!!!!!!!!
jacsonmoore3 said:
ITS DOING THIS http://www.youtube.com/watch?v=oDWmGrUPFjw
Click to expand...
Click to collapse
I see that the issue was corrected.
For anyone else who has this issue: You will want to use a 301kohm factory mode download jig on resistor between usb pins 4 and 5. If you don't have a dongle, then just stick the leads into the usb port and fish around. This will put the device into download mode. It will work because I see that your phone is actually booting up.
Someone showed me this video last night in the Infuse4G chat room. I would have responded then, but I did not know that there was a thread. I saw that you were flashing using Infuse4G One-Click Back-To-Stock UnBrick. I took that download down because of the confusing name. I also made some changes to the wording.. Device ID is now "This package is intended for:". Infuse4G One-Click Back-To-Stock will be down until I can figure out some way of distinguishing it from One-Click UnBrick.
In the Infuse4G forums they don't have a problem with bricking, so they call flashing back to stock "unbricking"... lol.. Anyways, I figured "when in rome, do as the romans do" so I put the word UnBrick at the end. Sorry if the naming convention confused you and I am working to correct that.
Does that include bootloaders adam? Im guessing no thinking infuse bls would kill a cappy.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Does that include bootloaders adam? Im guessing no thinking infuse bls would kill a cappy.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
The infuse has locked bootloaders. This is the way it should be. We don't need to flash the bootloaders, so they are not included.
Think of the bootloaders as that which initializes the hardware and provides download mode. The kernel is what adds additional features. There is no reason to modify the bootloaders when the kernel can be changed.
The Captivate 2.3 upgrade was done improperly. Instead of changing the kernel, they went the lazy way and modified the bootloaders to use an existing kernel to save time. On HTC phones I guess the bootloader and the kernel are joined somehow so bootloader unlock is important. We don't have that problem. We have 4 stages of booting.
With this information, you should be able to see why ilI think the bootloaders should be locked on the captivate.
they should, less bricks.
Samsung fixed my captivate after the mini USB port broke and I intentionally bricked it with an Odin flash pull because they would have known it was modded/custom rommed. So they fixed it and sent it back and everything works(Thanks Samsung!) but the problem is that they flashed the new 2.3 update which is sooo slow/laggy and featureless compared to Cyanogenmod7 181 nightly that I used to have on my phone. What I want to ask is if I can Odin-one-click back to JF6 stock 2.1 from 2.3(ATT GB bootloaders I think?) and then go about rooting and such from there to get Cyanogenmod back onto my phone.
Thanks,
kind3rgarten.
Yes you can....but that's more work than it's worth.
Just flash a custom kernel with Odin...boot into recovery with button combos and flash whatever ROM you want. easy as pie
studacris said:
Yes you can....but that's more work than it's worth.
Just flash a custom kernel with Odin...boot into recovery with button combos and flash whatever ROM you want. easy as pie
Click to expand...
Click to collapse
Thank you for the answer, but I am more familiar with flashing the rom this way. Are you sure I could do it this way? There wouldn't be a problem with the bootloaders or anything?
this way == odin1click back to JF6 then root then CWM then flash CM7 and gapps
also, would there be any difference in performance/battery life or anything if I were to go your route?
If you used it before it's still ok, just like i said that's a much longer process than what's needed, and by flashing bootloaders when you don't need you're taking an unnecessary brick risk to downgrade to obsolete bootloaders. Gingerbread boots are backward compatible, so they will work with ANYTHING. so why go back and then if you wanna use a tw gingerbread ROM you'd have to update to the new ones anyway.
your process:
Flash to 2.1
Root
Get cwm
Flash ROM
And that includes bootloaders so if it disconnects you could brick.
best way
Flash kernel to get cwm
Flash ROM
2 steps and no bootloaders so at the very very worst case scenario, you get stuck in a bootloop which is much easier to fix than a hard brick.
That being said you're way will work, so whatever floats your boat...
studacris said:
If you used it before it's still ok, just like i said that's a much longer process than what's needed, and by flashing bootloaders when you don't need you're taking as brick risk.
Click to expand...
Click to collapse
Plus, if you ever decide to try a Gingerbread ROM, you'll have to reflash the bootloaders again anyway, again risking a brick.
If you really want to go back to 2.1, I would still use a bootloader free package.
^^^Lmfao... I always hit the submit post button before i finish my thought, i just added in that bit you mentioned while you were posting that lol
studacris said:
If you used it before it's still ok, just like i said that's a much longer process than what's needed, and by flashing bootloaders when you don't need you're taking an unnecessary brick risk to downgrade to obsolete bootloaders. Gingerbread boots are backward compatible, so they will work with ANYTHING. so why go back and then if you wanna use a tw gingerbread ROM you'd have to update to the new ones anyway.
your process:
Flash to 2.1
Root
Get cwm
Flash ROM
And that includes bootloaders so if it disconnects you could brick.
best way
Flash kernel to get cwm
Flash ROM
2 steps and no bootloaders so at the very very worst case scenario, you get stuck in a bootloop which is much easier to fix than a hard brick.
That being said you're way will work, so whatever floats your boat...
Click to expand...
Click to collapse
So would I just flash a kernel that already has root/CWM? Then flash CM7/gapps on top of that?
I would post a link, but I don't post here too often.
Like this?
androidforums[DOT]com/captivate-all-things-root/483646-guide-root-official-2-3-5-guide.html
apbthe3 said:
Plus, if you ever decide to try a Gingerbread ROM, you'll have to reflash the bootloaders again anyway, again risking a brick.
If you really want to go back to 2.1, I would still use a bootloader free package.
Click to expand...
Click to collapse
Yeah, I see what you mean, thanks. Can bootloaders effect battery life, because I remember that I didn't get the best battery life in CM7?
Cm7 is aosp based it doesn't have all the closed source hardware drivers of touch wiz, so the battery life will be worse.
As for the kernel, any will work. It's not a kernel you're going to be running it's just a transitory kernel used only for it's recovery. Any ROM you flash will include a compatible kernel and be rooted.
Hold on I'll find you a kk4 kernel so it won't bootloop even though you don't need it to boot all the way anyway... Brb
Edit: kk4 corn kernel grab the Odin flashable version of corse.
studacris said:
Cm7 is aosp based it doesn't have all the closed source hardware drivers of touch wiz, so the battery life will be worse.
As for the kernel, any will work. It's not a kernel you're going to be running it's just a transitory kernel used only for it's recovery. Any ROM you flash will include a compatible kernel and be rooted.
Hold on I'll find you a kk4 kernel so it won't bootloop even though you don't need it to boot all the way anyway... Brb
Edit: kk4 corn kernel grab the Odin flashable version of corse.
Click to expand...
Click to collapse
Thanks for all the help. So I just flash this and then get into CWM and flash whatever rom I want to?
Sweet!
You got it chief
kind3rgarten said:
Thanks for all the help. So I just flash this and then get into CWM and flash whatever rom I want to?
Sweet!
Click to expand...
Click to collapse
Correct. If you remember to put CM7 and GAPPS on the SD card before you flash it, you won't even have to boot it. Just flash it, three finger salute into recovery, and flash cm7.
studacris said:
You got it chief
Click to expand...
Click to collapse
Wow, I really expected someone to just call me a noob or tell me to read the FAQ or something. Thanks a lot, both of you.
I downloaded the corn kernel, but I've never really flashed a kernel through odin before, always just the method I had stated, does it go in PDA?
kind3rgarten said:
Wow, I really expected someone to just call me a noob or tell me to read the FAQ or something. Thanks a lot, both of you.
I downloaded the corn kernel, but I've never really flashed a kernel through odin before, always just the method I had stated, does it go in PDA?
Click to expand...
Click to collapse
You got it, just leave the others blank. You shouldn't have to play with the check boxes.