[Q] corrupt bootloaders? - Captivate Q&A, Help & Troubleshooting

all the screwing around i been doing to get the captivate to where i what it again after a soft brick. is it possible to have messed up bootloaders.
can't get into recovery
after att logo I get a screen with a pile of different colors then the phone starts up fine and works
stock uckk4 with odin flashed corn 7.06

You need to flash gingerbread bootloaders.

Check this > http://forum.xda-developers.com/showthread.php?t=1129821

that was the trick ,thanks a bunch

Related

Bell SGS bricked or saveable?

Hi,
This is my first time experimenting with flashing custom roms. I was trying to flash a custom rom onto my perfectly working newly rooted sgs (using odin), but the first rom i tried has gotten my phone to boot loop and now I don't know what to do with it. I can get to the download screen just fine and recovery mode but don't knwo what to do. Please help, I really can't afford a new phone/ don't know if samsung will let me replace it now.
Oh, the rom was the XXJVK Gingerbread which is near the top of the forums right now, if that helps at all.
I really just need my phone to be usable, I didn't expect to mess it up. Thanks again to anyone with information.
I assume you were running jl2. The problem might be because of bootloader issue.
When you were flashing gingerbread did you use pit file and repartition?
I am not a pro but If you download JL2 and flash it, should be good to go. Try not to repartition and flash without using pit file.
I did use the .pit and repartition. I'm guessing this was a no no? I'll look for jl2 and try flashing that. Might you direct me to the right download?
http://www.multiupload.com/6GRS1OWRJW
I have no idea if it will work or not. Same thing happened to me also when I was trying to flash darkys rom and I was able to open the phone after I flashed with bells original rom. Give it a try. If its a boot loop I assume its a firmware problem. You should be able to fix it. The problem might be the repartirion and pit file. I am not sure about it. Hope this helps.
Just try flashing again with boot loader update ticked in odin. I'm pretty sure that repartition and pit do nothing to the bootloader. If that doesn't work I'll add more after I shower, I stink!
Sent from my GT - I9000 running Darky's 9.5 w/ DamianGTO's Ultimate Kernel using XDA Premium App.
A bootloop = ****ed framework and/or /system/ (rom)
Flashing bootloaders will not fix the problem, they are not related at all. And if a bootloader flash fails your phone will actually be bricked.
Just flash a stock rom with odin. I recommend jl2 if you want to go official stock, js8 for fastest froyo stock or jvk for the latest leaked beta. Tick update bootloaders for jvk or jl2 flash because jvk requires jvk bootloaders and jl2 because it supposedly fixes corruption problems. Remember bootloaders are overwritten every time you flash them and us risky.
Sent from my GT-I9000 using XDA Premium App
Thanks a million guys, I did flash the stock jl2 (no .pit or partition, nor bootloader update) and the phone booted. It fed me a gajillion force closes, but i managed to connect to kies and updated it that way, so now I have a perfetly working phone again. I'll probably experiment with a few more things now that I know how to fix this.
Again, Thanks guys!

[Q] Questions about preventing a second hardbrick

This is how the story goes, bear with me.
I had an ATT Captivate 1012 running on S7 but it was rebooting on me during phone calls. I decided to go back to stock with odin oneclick as I had read it works with 1012s but the process hung. I managed to recover and flashed back to stock JH2 with the non-one-click version.
I followed this guide by Breakin' Ranh
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I had used it successfully to get to stock before many times.
This is where I think I screwed up, please correct me if im wrong.
I thought that taking me back to JH2 would restore my bootloaders and allow me to install the 3buttonFix.zip via CWM over stock JH2, but after installing that zip my phone didnt boot up since.
The 3ButtonFix.zip I used was from this thread http://forum.xda-developers.com/showthread.php?t=1134443 . Via CWM, not Odin.
My battery was not at 100% (checked with a friend's phone and it was at about 24% so I'm not sure if that was the issue.
The question is, wouldnt have flashing to JH2 wipe out the bootloaders S7 installed (i9000 GB loaders if im correct)
I can only think of few things and would appreciate, if possible, your thoughts about these, all in an effort to learn more about the process and to reduce my chances of hardbricking again (Got a new captivate, 1010 this time)
1) JH2 bootloaders are clearly not compatible with that 3ButtonFix.zip because it perhaps assumes an underlying JF6 base? I was on JH2 when i flashed the 3ButtonFix.zip linked above
For future reference, should i then go JH2->JH7
This is the JH7 i have used before the 'accident'
(it is linked in the thread above)
I897UCJH7 Firmware
http://www.ponack.net/designgears/JH7_OTA.zip
2) The JH2 .tar provided in that thread did not /*correctly*/ install all? captivate bootloaders?
3) The flash to stock with the above guide didnt clear out my bootloaders successfully. The first time i tried to flash with odin oneclick it failed so i had to start over with the non-oneclick, that's how i managed to successfully get into JH2.
4) Perhaps flashing with a low battery (30% or so) ruined the install of 3buttonFix.zip?
Maybe I botched my flash via odin only to ruin it further with 3buttonFix.zip via CWM.
Would you recommend heimdall for all my (new) flashing endeavours? I _reaally_ don't want to go through the jtagging/phone replacement experience again.
Would have flashing the Odin version of 3buttonFix have prevented this? or maybe using heimdall to get back to stock?
What do you recommend i do to avoid these problems in the future? Stay away from 3ButtonFix.zip and just use a usb jig (finally got one *AFTER* hardbricking).
TL;DR
I read on the forums that people have bricked by ruining their sbl.bin by coming from a gb bootloader. But I was under the impression (apparently incorrect) that flashing to stock (Any stock froyo/eclair?) would prevent such issues. What do you think went wrong?
Sorry for the 20 questions :|
Thanks!
-XercesBlue
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Did you even try the button combos BEFORE you flashed the fix? You shouldn't have needed it at all...
Just forget that the 3 button "fix" even exists.
studacris said:
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Click to expand...
Click to collapse
Thank you for your reply studacris.
So the I897UCJH2.tar package I linked to does not contain bootloaders? If so this makes muuuuch more sense now. Should I find a package that contains those "stock" bootloaders to restore the phone into a stock state then ?
Will the packages linked at the bottom of this thread work then?
http://forum.xda-developers.com/showthread.php?t=731989
The "The internal beta's are NOT one-click, please read the linked threads
UPDATE: I897UCJH2 (Internal BETA)" ?
Do you have any ideas how that one is different from the I897UCJH2.tar I flashed following Breakin' Rahn's. If you follow the link you will see they link to the same files I had used during my first hardbrick.
Reading some more I stumbled upon your old reply,
http://forum.xda-developers.com/showpost.php?p=13581072&postcount=1798
So, If i get this right and to reiterate
For 1010s to get back to stock+bootloaders
1) OneClick (http://forum.xda-developers.com/showthread.php?t=731989)
OR
Use the internal betas "I897UCJH2 (Internal BETA)" linked at the bottom of the same thread ??
2) Do this http://forum.xda-developers.com/showthread.php?t=995143
If you run into a bootloop
OR this
http://forum.xda-developers.com/showthread.php?t=963403
?
I hope you understand how I can be a bit confused here.
I had no luck previously with OneClick on my 1012. Maybe the 1010 is different but i doubt it. The process hung at some point and had to start over with Breakin'Rahn's guide. Finally got to stock by perhaps without bootloaders.
---
As for the combos, when on s7 the combos worked. Volume down+power worked as expected for dl mode volume up + power for recovery. Upon flashing the new package I lost them leading me to assume incorrectly I was at a new factory mode.
The power down, remove battery, hold power, put battery, plug usb did not work either when on JH2. Of course, me being new at this I might have missed something.
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
studacris said:
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
Click to expand...
Click to collapse
Great, thank you for taking the time to read/reply!
Yes, I am definitely staying away from 3buttonfix.
XercesBlue said:
Yes, I am definitely staying away from 3buttonfix.
Click to expand...
Click to collapse
BUT, Im on a 1010 and the vol up + vol down and power buttons wont get me into recovery.
What method should I use to get into recovery?
If you have the gingerbread bootloaders the combo will work. The combo is in the secondary bootloader...

GB bootloaders with root

What Odin/One click package should i download to get root with GB bootloaders with CWM and flash zip file roms only? So i can flash roms like Fasty III and others? Which one is suggested for great battery life? Experts please
First off you don't need root to flash a rom. as for bootloaders use either a leak 2.3.5 i897 rom with bootloader or just the bootloader package. They are stickied in Dev section.
Can you please send me a link im new at all this but im learning i have Odin 3 v 1.81 and Odin v 1.81 ATT GB bootloaders extracted. I just want to be able to use download mode jig and plug in USB and go.
I have UCK H3 one click is that good enough to get started? Could i flash a rom in rom manager like fasty III im looking for fast and grt battery life.
KH3 1 click should be good. Don't use Rom Manager. Here you can find everything you will need. Just flash KH3 or any other GB leak, let it boot up normally, flash (with ODIN or SGS kernel flasher(app)) the boog's kernel that has CWM, let it boot up normally. Boot up in recovery and flash the rom.
Yea ive seen this which one should i pick and with or w/o bootloaders. 2.3 or 2.4.5 not sure? Just want the best one for speed and battery life and i like launcher pro.
I don't use launcher pro so can't say. But IMO KH3 or KJ3 would be my best (I still use KH3 modem). You need bootloaders so you can flash one with bootloaders.
prbassplayer said:
KH3 1 click should be good. Don't use Rom Manager. Here you can find everything you will need. Just flash KH3 or any other GB leak, let it boot up normally, flash (with ODIN or SGS kernel flasher(app)) the boog's kernel that has CWM, let it boot up normally. Boot up in recovery and flash the rom.
Click to expand...
Click to collapse
SGS kernel flasher requires root. Which rooting involves a kernel swap with Odin anyway, so for this purpose its pretty useless.
I just flashed UCK H3 and while in process i checked flash bootloaders now im soft bricked. Will the download mode jig help? I have one i dont know what to do. It doesnt work. What can i do am i screwed? I have the soft brick symbols on my phone now.
Reboot pc, swap usb Ports (make sure its one on the back of the PC), right click Odin and ruin as admin, put .tar in pda slot, Pull battery, replace, use jig, ignore screen that appears, connect to PC if Odin recognizes it hit start.
Grt thanks ok i got the fish now what do i reboot or what and add kernel next? I still have Odin opened and USB plugged in
Disconnect, close Odin. Pull battery, replace, use jig, flash boog's kernel the same edu you flashed the fugu kernel.
Im getting a screen that looks like a TV screen all lines what the heck is that? Its boots to ATT logo then TV screen all colors and lines. I did the kernel it passed but not sure whats going on now. It keeps rebooting ATT screen and TV looking screen
... That sounds like you didn't flash correct bootloaders. Correct me if Im wrong. On a side note ya Studa I had a brain fart on SGS kernel flasher.
I can still get in download mod with jig. Cant i try a diffrent package in Odin?
Did you use KH3 with bootloaders?
Not sure what to do im trying the AIO toolbar and im enabled for root phone but seems like nothing is happeneing im still in download mode
that is froyo boots on a gingerbread ROM.
op flash this package
That will flash the gingerbread bootloaders which will get rid of those lines and make it possible to boot into recovery.
DO NOT USE AIO TOOLBOX AFTER THIS PACKAGE IT WILL BRICK YOUR PHONE. might as well just delete that for safe measure.
Ok i was in recovery in rebooted phone now im at ATT screen logo no lines now. What do i do now is there a rom to flash or am i even rooted? Can i go into download mode and flash a kernel
Im staying at recovery till i hear back from someone lol. Where do i go from here?

Confused about firmware versions

Hey everyone. So I have an SGS2 rooted and running a custom rom and now am doing the same with a bell i9000m.
I used Kies to update to 2.3.3.
However, no matter what kernel I flash, I always have a boot loop. I have NO CWM and I would like to get that for the ability to hard reset...
I can only really access Download mode. Tried flashing back to stock 2.3.3 KG3 rooted kernel and still no luck. Tried CF Root JVP 3.7 (to get CWM) and still no cwm and a boot loop.
If I have updated to 2.3.3 doesn't that mean I have the gingerbread bootloader now? No matter what kernel I flash, I always seem to be getting a freaking boot loop, but it should be working....
Am I flashing the wrong firmware version or something? Or just getting unlucky with boot loops (Seeing as how CF root won't even boot)
Just kinda confused because for CF root you are supposed to install a version with a similar version model (JVP,ect) but the i9000m had JL2 (for froyo), and KG3 (for gingerbread) which are not options for CF-root

Simpilicity crashed, stuck at bootloop, nothing works

Hi everyone,
First time posting, I was on Simplicity rom 2.2.1, playing tiny tower while my alarms were going off. Next thing I know, the whole phone (GT-i9000) crashes and its stuck in an infinite bootloop. I can get into download mode easy enough and I tried flashing to a heap of stock roms: JVT, JVU, JVH and JVN. Nothing worked. I couldn't get into recovery mode, but after flashing the original CWM7 kernel I could.
Tried wiping everything in recovery, including dalvik cache, then flashing back to Simplicity in CWM. Again, nothing working, in fact nothing at all. Tried stock again, not working. Tried flashing some other kernels, didn't work either. Curiously I tried flashing darkys rom RE 10.5 in ODIN and it failed at repartitioning. Not sure if there's anything behind that. Anyway, I don't really know what to do next, so I'm here.
i tried without repartition with repartition etc and it would always fail.. but then i tried again put repartition set pit file and now..its flashing it! so trying more might help you. btw im using darky resurrection
That didn't work, it only lets me attempt one ODIN flash per entry into download, then I have to reset the phone to try again.
Make sure flashing a rom with bootloader.
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
I've always been cautious about bootloaders, I read somewhere that if you do it wrong it will completely brick your phone. Can you tell me how to do this safely?
you need to flash stock rom 2.1 with three parts and pit 512 and repartition checked, if didnt work try with out repatition
Can you provide a link for stock 2.1? I can't find one.
Found one with a bootloader, used ODIN, and it worked! Then went to stock JVU, updated to speedmod kernel (still working) but then I tried to update to SURFACE rom and I'm back to square one. Bootloops.
Tried more stocks roms with bootloaders, none of them working. I can get to recovery again if I flash CWM7 kernel like before.
lankks said:
I've always been cautious about bootloaders, I read somewhere that if you do it wrong it will completely brick your phone. Can you tell me how to do this safely?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=14273101
Sorry when I say bootloaders I mean they are built into the rom. I never flash them separately. The above link is a great resource to firmware with bootloaders. The newest gingerbread firmware is JW6... Try that or one of the others. I'm currently on JW5, with semaphore 2.7.4 kernel and DMore 3.3 Rom, it's rock solid. Hope you get it sorted.
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
vanisleryan said:
http://forum.xda-developers.com/showthread.php?p=14273101
Sorry when I say bootloaders I mean they are built into the rom. I never flash them separately. The above link is a great resource to firmware with bootloaders. The newest gingerbread firmware is JW6... Try that or one of the others. I'm currently on JW5, with semaphore 2.7.4 kernel and DMore 3.3 Rom, it's rock solid. Hope you get it sorted.
Sent from my I9000 running JW5 with Dmore3.3 and Semaphore 2.7.4
Click to expand...
Click to collapse
Yeah I found this thread earlier, I did flash with JW6, doesn't work.
So instead I just accidentally flashed a ROM for the Galaxy Tab, now my phone won't turn on at all, I'm afraid I just bricked it for reals. Can't enter download mode, completely dead boot.
http://www.teamovercome.net/p1000/?page_id=17

Categories

Resources