Database Info

unrecoverable soft brick even with USB JIG

so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.

muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?

Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG

donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.

Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps

muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.

Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App

will do thanks guys, ill try it tonight and let ya know how it goes for me.

i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now

krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much

muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.

I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??

amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...

Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.

That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.

That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!

Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App

Woops ahahahha. Was talkin to my friend. SOrry!

fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/

Messed up flashing

I was attempting to flash back to stock (2.2) using odin3 1.85 but I messed up and now my phone goes to the phone yield PC screen.
I can get into download mode, but odin one click doesn't do anything besides "<OSM> All threads completed. (succeed 0 / failed 0)" after clicking start. All the boxes are blank though..
Am I completely screwed here?

As long as you can get into download mode, you are not completely screwed. Open up odin 1 click first and then plug it in. I would use a different USB port. I screwed up once by placing and flashing an infuse rom on a captivate but odin 1 click to jf6 worked for me. Another time I got that phone yield computer screen too, created a jig and flashed to jf6, master clear and reflashed.

Ok, I've been reading over various threads and a lot of them say they have to keep trying to get it to work so I guess I'll keep doing that.
Thanks for the reply, makes me feel better
And I fixed it

RandomZero said:
Ok, I've been reading over various threads and a lot of them say they have to keep trying to get it to work so I guess I'll keep doing that.
Thanks for the reply, makes me feel better
And I fixed it
Click to expand...
Click to collapse
once upon a time I flashed t mobile vibrant firmware onto a bell vibrant. instant gg, cst me 100$ at the local phone store to fix. ha ha

Messed up flashing .. cannot get to download
I have a similar and may be a worse problem.
I started out with a perfectly fine factory installed Captivate Froyo 2.2 UCKB2.
I tried flashing using Adam Outler's Heimdal install for Gingerbread 2.3.4.(UCKH3).
(http://forum.xda-developers.com/showthread.php?t=1238093)
Everything was fine until I actually started the flash .. it went on to copy the pit file but spat out an error Loading the Kernel. And now I have a Phone--!--PC no matter what I do.
I tried the button combo, the button+USB combo, the button+usb+battery combo, the adb reboot download thing, but to no avail.
Have not tried any of the "Jigs" yet. Nor have tried the Unbrickable Mod (skilled soldering on the board is a little too much for me). Don't want to deal in hardware unless absolutely necessary.
Any help in getting me to download mode is really appreciated.
EDIT:
WOW ... I was never able to get into a download mode, I connected the phone to the PC with the right drivers, ODIN3 was able to detect the device, Hiemdall was also able to detect the device connected, so I went on to flash the phone with Hiemdall (even though it was not in the download mode [still showed phone--!--pc] ) AND IT WORKED ... I WAS ABLE TO FLASH SUCCESSFULLY .. I am on Gingerbread 2.3.4 now ... !! Flashed without the bootloaders ! Thought I should share it with all ... !!

ptera said:
I have a similar and may be a worse problem.
I started out with a perfectly fine factory installed Captivate Froyo 2.2 UCKB2.
I tried flashing using Adam Outler's Heimdal install for Gingerbread 2.3.4.(UCKH3).
(http://forum.xda-developers.com/showthread.php?t=1238093)
Everything was fine until I actually started the flash .. it went on to copy the pit file but spat out an error Loading the Kernel. And now I have a Phone--!--PC no matter what I do.
I tried the button combo, the button+USB combo, the button+usb+battery combo, the adb reboot download thing, but to no avail.
Have not tried any of the "Jigs" yet. Nor have tried the Unbrickable Mod (skilled soldering on the board is a little too much for me). Don't want to deal in hardware unless absolutely necessary.
Any help in getting me to download mode is really appreciated.
Click to expand...
Click to collapse
The phone--!--PC screen is (in a sense) download mode. Just try flashing again from that screen.

Thank you JMTheiss
jmtheiss said:
The phone--!--PC screen is (in a sense) download mode. Just try flashing again from that screen.
Click to expand...
Click to collapse
I did just that and it worked great... Thanks .. although I did it before I saw your post.. I tried it out since ODIN3 and Hiemdall were both "seeing" the device connected and I thought it was worth a shot.
Thank you for the comment though, I would have definitely returned here had it not occurred to me.

May have killed wife's phone, please help!

Hey all,
I've been flashing ROMs since the old Windows Mobile days and recently have run into a problem that has me stumped and I haven't been able to fix it. I beg you experts for help, I'm not sure what else to do.
My wife had some complaints that her Infuse was acting slow so I thought a new flash of something might help. I attempted to flash CatyRom but was stuck at the rainbow loading animation for over an hour. At this point I was getting nervous so I figured I would go back to stock. I used the link http://forum.xda-developers.com/showthread.php?t=1331381 for Heimdall One-Click Back to Stock. After doing that the phone just froze on the Samsun logo and after retrying it twice and restarting I was making no progress. I've tried some other back to stock threads and the latest was I loaded the ultimate unbrick from http://forum.xda-developers.com/showthread.php?t=1367099 and now the phone is stuck in a red Clockwork Recovery v2.5.1.3 - Voodoo Lagfix. When I try rebooting it sits at the Samsung logo, when I try to flash the one thing on the phone(CatyRom) it says:
E:Can't mount /dev/block/stl11(file exists)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl11(file exists)
E:Can't mount /dev/block/stl9(file exists)
Error mounting SYSTEM:!
At this point I'm not sure what else to do/try. I can get into this version of Clockwork which I suppose is kind of good, but all that's on the phone is CatyRom and that won't install. If anyone can help I'd truly appreciate it.

Try flashing the community gingerbread kernel with Odin to reset your recovery and do a complete wipe and fix permissions...that happened to me once and that fixed it for me....after that you should be able to flash caty
Sent from my SAMSUNG-SGH-I997 using xda premium

For some unknown reason Odin isn't seeing the phone. Heimdall detects it in Download Mode fine, but it never shows up in Odin.
Also, when I tried one of the GTG back to stock Heimdall repackages everything goes fine and then at the end when it says Ending session.. it then says:
ERROR: Failed to send end session packet! Heimdall crashed!
The phone just sits in download mode, if I pull the battery and restart it's like nothing was done.

I'm not too experienced on hemidal but I believe there is a way to flash that same kernel I mentioned thru hemidal...but I don't use it so I would ask Dani897 he knows hemidal very well...hope that helps..
Sent from my SAMSUNG-SGH-I997 using xda premium

On heimdal or however you spell it click flash boot loaders ive used it many times it should work
Sent from my SGH-I997 using XDA App

Hemidall & Odin use different drivers. After using Hemidall, you have to reinstall the samsung usb drivers again for Odin to see your phone.

Truckerglenn said:
Hemidall & Odin use different drivers. After using Hemidall, you have to reinstall the samsung usb drivers again for Odin to see your phone.
Click to expand...
Click to collapse
What he said. Uninstall the driver in device manager. For me, it shows up under a main section called libusb.
Did you use the straight up repackage link or the one with the community v8 kernel in it? Since you have red CWM recovery, it would seem that you either used the community v8 which has voodoo lagfix enabled by default or you had a bad flash with the straight up repackage. I think I have a heimdall package that has all the gtg unbrick files in it. I'll post it up here if I find it.
EDIT: I threw a heimdall package together based on gtg's unbrick and just flashed it to my phone as a test. Yes, it worked just fine.
heimdall package back to uckd5 stock using gtg's unbrick files - http://www.multiupload.com/QL5BCRG1CI

the exact same thing happened to me... try different usb ports ..try different usb cables.. i didnt believe my usb cable was bad....it was. i used gtgs unbrick once i got odin to see the phone!!! im back to normal!!

Thanks for the help guys, I got the phone visible in Odin after reinstalling new drivers but it just sits there at:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I've been looking at "Get PIT for mapping.." for over an hour now, it doesn't seem to be doing anything. I've tried 2 different back to stock options through Odin and they both say the same thing.
Also, I'm not sure what my battery level is or if it will even charge, since trying Odin I haven't been able to get back into recovery, just download mode. Any suggestions?

Try a fresh download of the file your flashing in Odin and restart Odin before hand
Sent from my SAMSUNG-SGH-I997 using xda premium

Griffon23 said:
Thanks for the help guys, I got the phone visible in Odin after reinstalling new drivers but it just sits there at:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
I've been looking at "Get PIT for mapping.." for over an hour now, it doesn't seem to be doing anything. I've tried 2 different back to stock options through Odin and they both say the same thing.
Also, I'm not sure what my battery level is or if it will even charge, since trying Odin I haven't been able to get back into recovery, just download mode. Any suggestions?
Click to expand...
Click to collapse
Are you trying to use gtg's ultimate unbrick?
Sent from my SGH-I997

jayson94538 said:
Are you trying to use gtg's ultimate unbrick?
Sent from my SGH-I997
Click to expand...
Click to collapse
Yes, that was the one I was attempting to use, but I've tried one or two others since then. I've also tried redownloading afew of them. I was excited when I got Odin to see the phone, but it hasn't done anything yet.
So far with all of them it will freeze at a certain step, either "Get PIT for mapping..." or "ID:0/003> Firmware update start..<ID:0/003> factoryfs.rfs" and it will never continue. I know this things can take some time, but I've given them almost an hour each.
I'm also concerned that the battery may be running low, is there any way to charge it when I can only get into download mode? Any other suggestions are welcome.

Griffon23 said:
Yes, that was the one I was attempting to use, but I've tried one or two others since then. I've also tried redownloading afew of them. I was excited when I got Odin to see the phone, but it hasn't done anything yet.
So far with all of them it will freeze at a certain step, either "Get PIT for mapping..." or "ID:0/003> Firmware update start..<ID:0/003> factoryfs.rfs" and it will never continue. I know this things can take some time, but I've given them almost an hour each.
I'm also concerned that the battery may be running low, is there any way to charge it when I can only get into download mode? Any other suggestions are welcome.
Click to expand...
Click to collapse
Some people got it to work by switching to a different usb chord, or trying on a different computer.
Sent from my SGH-I997

Try this: Download mode using Odin. Uncheck the reboot box. Flash Enthroy's kernel dated 11/02.
If it flashes, boot into recovery, it should be Red. Scroll down and disable Voodoo lagfix or enable it if it's disabled.
Rebooting should put you in a loop after the kernel fixes the partitions. Good.
If you disabled lagfix, boot to download mode and use the latest stock GB leak or Ultimate Unbrick.
If you enabled it, boot to recovery, but this time disable it. Rebooting should put you in a loop after the kernel fixes the partitions. Good. Boot to download mode and use the latest stock GB leak or Ultimate Unbrick.
The loop should only occur if the rom is messed up.
Booting after flashing shouldn't take more the 5-10 minutes. At least from what I've seen on my phone.

Truckerglenn said:
Try this: Download mode using Odin. Uncheck the reboot box. Flash Enthroy's kernel dated 11/02.
Click to expand...
Click to collapse
Thanks, I'll give this a shot, but I'm not finding anything called Enthroy's kernal, I've tried searching for it but no luck, I may be missing it.

Go into the infuse super thread and look under kernels for the download. If nothung works, contact me because my phone (im sending it from) was rezurected with mobile videos jtag repair. Turns out my phone wont connect to computers even with a new usb slot installed. Anyway its forty bucks but its well worth it . If you still have warranty go ahead and use that up if you do not care about the info on your phone.

dude..try a different usb!!!!!! i kept getting the same errors.. it would get 1/4 way throught the process and get stuck... i used my sons usb cable from his HTC inspire and it worked perfectly!!!! USB CABLE !!! TRY IT!!!
i used gtgs very carefully ..step by step !!!
once i did it with a new usb, it downloaded in 3 minutes!!!!
good luck!!!!
oh and happy new year everyone!!!

did you get it working?? just curious

mejori said:
did you get it working?? just curious
Click to expand...
Click to collapse
Hey guys, unfortunately I've been out of town and just got back yesterday to continue work on the phone. I've actually had quite abit of success. I decided to try GTG one more time just to see, this time I used both a different USB cable and USB port and it worked! The flash completed without any problems and the phone booted up like stock in just afew minutes.
I am having one slight issue though. Everything was working fine after the reflash but my wife noticed today that her data stopped working. She's not able to connect to either her 4g/3g connection or WiFi. When she tries to go to any websites it says "Web page not available." in the browser. Her phone service is fine, but data both on and off WiFi give that message. I've tried turning on Airplane mode, restoring default APN settings, and restarting the phone afew times.
The only thing I haven't tried yet is a factory restore, I'd like to avoid it since she just set everything back up but I'll probably have to do one and hope the problem doesn't come back.
Thanks everyone for all the help!

Griffon23 said:
Hey guys, unfortunately I've been out of town and just got back yesterday to continue work on the phone. I've actually had quite abit of success. I decided to try GTG one more time just to see, this time I used both a different USB cable and USB port and it worked! The flash completed without any problems and the phone booted up like stock in just afew minutes.
I am having one slight issue though. Everything was working fine after the reflash but my wife noticed today that her data stopped working. She's not able to connect to either her 4g/3g connection or WiFi. When she tries to go to any websites it says "Web page not available." in the browser. Her phone service is fine, but data both on and off WiFi give that message. I've tried turning on Airplane mode, restoring default APN settings, and restarting the phone afew times.
The only thing I haven't tried yet is a factory restore, I'd like to avoid it since she just set everything back up but I'll probably have to do one and hope the problem doesn't come back.
Thanks everyone for all the help!
Click to expand...
Click to collapse
That's the first thing I do after I Odin back to stock. Do a hard reset to erase what ever was left behind, or else you will keep having problems. GL

[Q] download mode keeping rebooting?!

My sidekick was soft bricked so i used odin to recover it. now when i plug it in it goes immediately to the download mode screen and is recognized by odin. problem is is it restarts after min or so. odin starts flash modem passes, kernel passes, but while flashing the factoryFs, it gets to 53% and the phone restarts and it fails. it does this in oneclick odin and also in odin3. any help would be much appreciated. the phone wont work unless plugged in and it restarts every min.

Have you used Odin before?
If not, try downloading a new recovery image for your device.
You'll have to use the ability to search the interweb to get yourself one. Go get it.

Try reinstalling drivers for your phone on your OS. Reinstalling JRE (Java Realtime Enviroment) backup and clear your sdcard, then do as you have been doing before and let me know if you can get somewhere, thanks!
Sent from my SGH-T839 using XDA

yes, ive used orin before with no problem. my little girl plugged my phone while it was flashing and causing it go to the phone-!-computer screen. I was able get it out of that but now its doing what i stated earlier. i been lookin for the image you mentioned but it seems all the links but so far all the link are bad or have the fbi warning on it. imma keep trying to look for it though.
Ive reinstalled the drivers several times, changed usb ports, i only have one usb cord that i could get to work so im stuck s far as that goes. not sure how to do the jre but ill google it, in all the threads i read on here your the first to mention jre. i havent had a sd card in the phone since it messed up, should there be? i let you know if it works. thanks

Did I brick my phone?

I have 4.1.1 on the phone and I was doing the Odin method. I ran the valrec file and it worked quickly. I closed Odin and then went to do the recovery. It didn't work (found out because my usb crashed...odd) but eventually I got it working again. Since I thought I wasn't supposed to close Odin I redid the valrec file and it was super slow/stuck on sbl2.mbn so I pulled the cable, stupid I know. I tried turning on the phone and obviously it gave me an error and wouldn't boot. I went to do it again and now it's on sbl3.mbn but it has been there for awhile. I don't know why it's so slow this time around but I'm really worried that I just screwed up my new phone that I got yesterday. Does anyone have any suggestions or advice? I'm kind of freaking out now.

Issue resolved, someone on reddit suggested I reboot my computer. I did that, and also turn the phone off and back into download mode, and that worked. That was a harrowing experience...