Related
Hello, I just recieved my new captivate, after returning old one on warranty, it came preloaded with 2.2 Froyo. My question is: can I still do a ODIN flash to get it back to 2.1? Thanks in advance for any help
Odin one-click flash to stock 2.1 worked for me after doing the official KB1 2.2 update via Mini Kies. Batch 1008 with 3-button combo download mode working.
Maybe I should have been more informative. The new phone came with 2.2 installed. I do not know if it ever had 2.1 on it. Using ODIN3 has the term "flash back to stock". Since this came with 2.2 I am assuming that 2.2 is stock. Will using ODIN3 give me a 2.1 (JF6) operating system even if it never had 2.1 installed on the phone? Also something else I am scratching my head about. The phone I am returning is an 1008 batch and the new phone is an 1007 batch. Is the new phone actually built before the phone that is being returned? Could this mean it at one time had 2.1 installed? Could it mean I recieved a refurbished phone? I was hoping for a new build thinking they fixed the problems of the old builds. Again thanks in advance for any help
there are 2 Odin3 programs, the Odin3 one click flash to stock (2.1 stock) and the odin flash anything you want Odin3 1.7 version.
yes that odin will do 2.1
what carrier are you? att or rogers? there are 2.2 flash and or upgrade packages.
Trusselo said:
there are 2 Odin3 programs, the Odin3 one click flash to stock (2.1 stock) and the odin flash anything you want Odin3 1.7 version.
yes that odin will do 2.1
what carrier are you? att or rogers? there are 2.2 flash and or upgrade packages.
Click to expand...
Click to collapse
hey bud...I have some similar problem...so I got this replacement phone after i bricked my good phone becoz of battery issue...now I was on continuum 3.1.1 but i decided to flash CM7. So I used Odin one click to stock. But I wasnt aware that my phone is one of those builds which looses 3 button combo....so i lost 3 button combo and i was frustrated I updated it to official froyo 2.2 from ATT using mini kies...now after researching a lot...I came across Odin with 3 button combo fix http://forum.xda-developers.com/showthread.php?t=818439
Now I am not sure, if I use this Odin...will i go back to stock 2.1 eclair with my 3 button fix back...as the description of this program claim that it works same as Odin one click but with 3 button como fix....
can anyone tell me if this wont brick my phone and i can go back to stock 2.1 with 3 button combo safely?
http://forum.xda-developers.com/showthread.php?t=818439
Now I am not sure, if I use this Odin...will i go back to stock 2.1 eclair with my 3 button fix back...as the description of this program claim that it works same as Odin one click but with 3 button como fix....
Click to expand...
Click to collapse
with the link you provided, please go to it and read the BIG BLUE LETTERS at the very top of post. read the rest of post for instructions,
Trusselo said:
with the link you provided, please go to it and read the BIG BLUE LETTERS at the very top of post. read the rest of post for instructions,
Click to expand...
Click to collapse
LOL i read it..but i am not sure if this will work for me..as i am on 2.2 stock...so whats stock for me...i am confused there...
it will flash you to the att stock 2.1 with 3 button fix. att stock not your stock. your stock is gone. that file is a stock rom with 3 button fix.
Well I managed to get a few questions answered both by the people responding to this post "Thank you very much" and customer services of Samsung and AT&T. Called Samsung and they confirmed that the batch # on my new phone makes it older than the phone I am returning. They also informed me that it was more than likely a refurbished model. This would take care of the question of if it ever had 2.1 installed. Called AT&T and explained my concern about recieving someone else problem phone and them sending me a model older than the one I am returning. They confirmed that it was a refurbished model. I will call warranty service again tomorrow and see what they can do. I would atleast expect a phone with newer manufacturing dates that may not have had the problems of the earlier builds to begin with.
davietr said:
Well I managed to get a few questions answered both by the people responding to this post "Thank you very much" and customer services of Samsung and AT&T. Called Samsung and they confirmed that the batch # on my new phone makes it older than the phone I am returning. They also informed me that it was more than likely a refurbished model. This would take care of the question of if it ever had 2.1 installed. Called AT&T and explained my concern about recieving someone else problem phone and them sending me a model older than the one I am returning. They confirmed that it was a refurbished model. I will call warranty service again tomorrow and see what they can do. I would atleast expect a phone with newer manufacturing dates that may not have had the problems of the earlier builds to begin with.
Click to expand...
Click to collapse
yeah u r right...I had a nice phone from new batch..which never lost 3 button combo...then becoz of my stupidity i bricked it...acted innocent infront of ATT and got replacement, but this phone is reconditioned and is from that batch which looses it 3 button combo...which I didnt know and I lost it now.,,
but this phone as awesome battery life and GPS....i am on stock 2.2...and I upgraded it myself
24hrs later and thinking I have overreacted. I returned phone because of random shutdown issues and absolutely horrible gps (even after several rom changes). The replacement phone (refurbished) has an awesome gps and no problem with the random shutdown "so far". I got a lock outdoors as soon as I turned it on not even a second of wait time. I even got a lock in my basement within 15 sec. I test drove it today. Instant lock, perfect tracking, no putting me on side roads, no going thru intersection I have stopped at, turned when I turned and no loss of signal. In other words PERFECT! I think the gps is a hardware problem that has a fix. I don't care when the phone was built as long as it works the way it is suppose to. Now I just hope that after I flash a new rom it stays that way.
viny2cool said:
yeah u r right...I had a nice phone from new batch..which never lost 3 button combo...then becoz of my stupidity i bricked it...acted innocent infront of ATT and got replacement, but this phone is reconditioned and is from that batch which looses it 3 button combo...which I didnt know and I lost it now.,,
but this phone as awesome battery life and GPS....i am on stock 2.2...and I upgraded it myself
Click to expand...
Click to collapse
Ummm... my phone is one of that batch (1008), and when I flashed with one-click I did lose 3-button. But flashing back to stock with ODIN 3 gave me 3-button back, and I' be been able to use it every since, since I'm one of those people who always flashes back to stock whenever I change or update ROMs...though honestly, I never use the 3-button option. I root, add Clockwork, and get into download mode from there. Works for me... Flashing to stock with ODIN 3 (NOT the 1-click version!) should give you back 3-click, too.
The real issue to me is AT&T giving you a used phone and calling it new. Beyond being really tacky, isn't that kind of fraudulent? Or is there something in the contract that makes lying about that okay? And if it's the latter, why don't they just tell you up front that you might get a refurb to replace your new one?
Tacky, I tell you; just tacky...
Update. Just flashed my phone back to 2.1. Flashed the "Paragon RC6" rom. Note to self: make sure you send a few donations. Everything is working great life is good. Refurbished or brand new doesn't really matter at this point. Awesome phone that works awesome. This phone is my very first cellphone. I was clueless until I found this forum. Thanks to everyone that contributes to this forum and the dev's that make having this phone worthwhile.
kevalin said:
Ummm... my phone is one of that batch (1008), and when I flashed with one-click I did lose 3-button. But flashing back to stock with ODIN 3 gave me 3-button back, and I' be been able to use it every since, since I'm one of those people who always flashes back to stock whenever I change or update ROMs...though honestly, I never use the 3-button option. I root, add Clockwork, and get into download mode from there. Works for me... Flashing to stock with ODIN 3 (NOT the 1-click version!) should give you back 3-click, too.
The real issue to me is AT&T giving you a used phone and calling it new. Beyond being really tacky, isn't that kind of fraudulent? Or is there something in the contract that makes lying about that okay? And if it's the latter, why don't they just tell you up front that you might get a refurb to replace your new one?
Tacky, I tell you; just tacky...
Click to expand...
Click to collapse
I would admit this all is easy...i got my new phone in september and had almost flashed all roms on xda for captivate...but once i didnt charge the battery full and used odin 1 click...which bricked my phone...
now i got replacement phone...which was refurb and ATT guys told me that...but as my original phone was actually bricked (means dead..no hopes) I accepted it...but ignored the fact that it can loose 3 button combo...while i was flashing it to stock (having CM7 in mind to flash next) I suddenly realized that i lost 3 button combo (which is required for CM7). I felt betrayed...so i thought to forget flashing any rom and go to stock 2.2....BIG MISTAKE....after 2.2, i was not able to flash any update.zip...i tried for root, CWM, 3 button combo...always got same error E:/signature un verified..
So in desperation I used AIO 3.0...and yes i managed to get the famous phone-!-computer screen....lol I dont have Jig...so i got it replaced again...
atleast from all this i learned how to use ADB (to get into recovery and download without 3 button combo)
Now waiting for my next refurbished phone...
Ok I have a stock KB2 Cappy. I used Odin to flash back to 2.1 KB1 JF6
Then I used Odin 3 to flash a kernel so I can put on CM7. I am now stuck in the Boot screen.
I have no 3 button, I cannot get into download mode (my jig is homemade should i order one?)
I tried to change usb and remove the sim card to try odin again to get back into stock.
Nothing seems to work the only thing is my jig is not good either for DL Mode. I want to get back to stock so any suggestions. I tried heimandall did not work either.
I am really stuck on this galaxy s I897 screen.
Is the jig soldered? If its not make sure you are connecting the correct pins and use some black tape or something to isolate your fingers from the resistors (might screw up the actual ohms making it to boot up normally and not in to dl mode.
The bootloop was expected, you are supposed to check that you have a working button combo both before you flash the kernel (because it will bootloop and you boot into recovery and flash whatever) and before you ever flash cm7 because that is the only way to get into download mode besides a jig on aosp roms.
so, fiddle around with your jig some more and if you get it in download mode just flash the captivate gingerbread bootloaders, that will fix your button combo and allow you to proceed flashing cm7.
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
This is probably the easiest guide on how to make one. Layman Jig First one I did I butchered a pare car charger to make it. You can just grab one from MobileTechVideos.com for about $8.
AlphaJ1 said:
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Click to expand...
Click to collapse
Hi guys,
Thanks for the link.
From what I understand, a jig is an improvised connection that allows your phone to go into DL mode. What if my phone is still capable of going into DL mode? My apologies, as I am at work.
Im not sure what you mean with your question. What the jig does is give the signal for it to go to download mode as was intended by samsung. Same theory on how your phone knows its connected to your computer, or the wall or the car charger. Its by manipulating the current between 2 pins. Keep in mind your phone should always be capable of going in to download mode assuming the hardware is working and your bootloaders are in working order.
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Read my post after yours...
studacris said:
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
Click to expand...
Click to collapse
^What he said. If that fails could be a faulty cable.
AlphaJ1 said:
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Click to expand...
Click to collapse
You are correct, if you can get into download mode you are not bricked. Make sure you are using the usb cord that came with your phone, plugged directly into the back of your computer. Make sure your SIM card is out, you're logged in as an administrator, and that you start odin before you plug your phone in.
If it still doesn't work, try another computer and/or another cord.
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
That is a practice from way back in the winmo days, sometimes the flash would corrupt the Sim itself. Not the case anymore for the most part. I'm with you never take mine out either.
Thanks guys, I will try this at home; hopefully it works.
prbassplayer said:
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
Click to expand...
Click to collapse
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
apbthe3 said:
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
Click to expand...
Click to collapse
Did you get a red "FAIL" message on ODIN? Because thats what I got several times. My buddy also tried and he got the same thing. The green progress bar completes up till about 80 percent and gives up on me. I'll try taking out the SD and SIM cards when I get home, hopefully it works.
Hi guys, little update:
I found this on the forums and used it:
http://forum.xda-developers.com/showthread.php?t=731989
Anyways, this worked after my second try. Interestingly enough, it worked once i removed the Sim card, which is what apbthe3 suggested..great! I'm just glad my phone is no longer bricked. Minor issue though, my phone is now an AT&T phone, but unfortunately, I am a Canadian Samsung user. New problem now. My phone is no longer rooted (never was actually, but was bricked in the process), I'm happy it works, but i need to know if there are any Canadians out there that know how to revert my device back to Rogers.
Any help would be great. Anyways, the link I provided works great, so its a great resource for our American friends.
Why don't you look at Cognition 4.x.x? Froyo stock ish looking rom tweaked out the ass very fast. Good rom.
Look in development. There are a couple of threads there just for Rogers users.
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Be in safe kernel if your on ics. You could check your device of the bug by downloading eMMC check in google play. Dont put your fate in that if your on stock ics rom not rooted you will not get the bug, be on the safe side.
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Just check the service job sheet whether they replaced the mobo or not before taking the delivery ? As simple As that.
got my gnote back with new mobo
Well, it is almost like the 'law of attraction'... I didn't want any problem and when I got my gnote today... guess what ? phone vibration didn't work. I had to go back to the SSC.
Fortunately, they responded immediately and the SSC guy fixed it on the spot without another round of formal servicing process. As explained to me, an insulation sticker of the vibrator was not removed while slipping in the new mobo. I didn't care less to understand if that is true as I was excited to get my phone with 11GB internal storage .
All seem to be working fine as of now with stock ICS 4.0.4 :good:
Today, my Note got extremely bricked, that I could not believe a phone like that could get so easily blown up.
I get this "Firmware update encountered an issue. Please select recovery in Kies and try again." message while it's rebooting every second.
I got this by making a huge mistake, using the re-partition option with the included .pit file, thinking it would factory-wipe the phone before downgrading... well, it didn't. Now, I can't barely access Download Mode or recovery because of, what I assume, low battery. It's charging now and it doesn't look like it. It reboots itself every 5 sec while it's plugged in. Before that, I used the JB leak and began to hate it because of it's damn instability. I wanted the stable, stock, ICS that came with it. I never had any problems like that on Xperia S.
Hell, even Odin can't ****ing save it because of the reboot-problem. I begin to think that, for the first time ever, I have to send this pile of **** back to Samsung and get a new one by saying, Kies ****ed up my phone.
Is there a solution that DOES NOT INVOLVE A DAMN USB JIG for this phone?
If you got the error in kies you could have followed the kies emergency firmware recovery option. Reflashing with a pit file is only for when you have triggered the emmc brick bug is my understanding. Look for the thread with the unbricking guides and hope for best. If not then it looks like service centre...........
Sent from my GT-N7000 using xda app-developers app
LinixAndroid said:
.. I could not believe a phone like that could get so easily blown up.
I got this by making a huge mistake, using the re-partition option with the included .pit file...
Click to expand...
Click to collapse
Did you really read and combine this two sentences? Sometimes people should read the warnings (here about the reasons why NOT to use a pit) and follow them.
But first of all you should recharge the battery outside your device. When you're sure it's "reloaded" try download mode again and install a prerooted Stock Rom (like GB LC1 3-part) and check if you can install and after reboot into a stable device again.
Maybe it isn't so bad forever only for a few hours.
ThaiDai said:
Did you really read and combine this two sentences? Sometimes people should read the warnings (here about the reasons why NOT to use a pit) and follow them.
But first of all you should recharge the battery outside your device. When you're sure it's "reloaded" try download mode again and install a prerooted Stock Rom (like GB LC1 3-part) and check if you can install and after reboot into a stable device again.
Maybe it isn't so bad forever only for a few hours.
Click to expand...
Click to collapse
Wait, I have to charge it outside the phone? What kind of charger only charges the battery outside the phone?
just find someone with the same phone in your neighbourhood and charge in another phone...that's the easiest way..
I have flashed my note multiple times now and it never crossed my mind to use a .Pit file..
By the way, have you thought of leaving the battery out for a few minutes? I got that Firmware issue message before because the power went out while I was flashing my phone from my PC.. Then I just left it out for a few minutes and was able to boot back into dowload mode again
After the emmc brickbug:
The custom pit file may work but trust me after a few moths you going crazy with your phone... it freezes randomly on every rom and wont charge randomly. When you wake up.. phone frozen and battery is on 0% ... i lived 2 weeks with this then i gave it to samsung and they changed the mainboard for free now im happy
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
theklxn said:
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
Click to expand...
Click to collapse
Which Odin did you use? When already on JB, you should be using Odin KK4 without bootloaders to avoid hard bricks.
If your Odin was flashing bootloaders when it got interrupted, chances are that it's hard bricked and only JTAG service will bring it back. You can contact Josh at mobiletechvideos.com for it (of course there's a fee for the service).
You can try a jig before going through JTAG service (build or buy one), maybe you'll get lucky and be able to force download mode but know that if it got interrupted while flashing the BLs, only JTAG can bring it back.
i was afriad you might say that didnt think i would have to go that far to bring it back but thank you for the swifty reponse ill get back to you when my problem has updated