I was previously running MIUI (not sure which version) and something went wrong with it. Random processes just kept "unexpectedly stopping." I found the Heimdall One-Click and tried it. The process never finished (failed to upload FACTORYFS everytime :/). I tried checking the Flash Bootloaders option. It got the FACTORYFS upload percent a bit further along, but still failed. Opened up Odin, and it wouldn't find any device plugged in.
After a couple more tries at this, suddenly, no matter which USB port I plug in to, my computer fails to recognize the device when previously it would on a couple specific ports. Odin will not recognize it, either.
Am I screwed?
Edit:
I've gotten the USB to recognize. I'm scared to do anything now, for fear I won't get it to recognize again. Odin still does not see the device. What other tools can I use to unbrick this?
I believe the driver for heimdall "takes over" the port. You have to use a different port or uninstall the driver to use Odin on it again. Also it seems when the upload won't complete most have success with another cable....nothing wrong with qksters uclb3 return to stock. I've used it several times.
Sent from my SGH-I897 using Tapatalk
I had the same issue a few days ago. SCARED me to...
Powered the phone off.
Unpluged USB
Rebooted Windows PC
Rebooted phone
Started at step one again
This time try another USB Port on computer
This time everything worked
I've had this happen before. After much panicking, I used GTG unbrick.
Thread located here → http://forum.xda-developers.com/showthread.php?t=1116251
download is here → http://www.mediafire.com/?i57410xodydx5l1
Follow it verbatim. Worked like a charm!
unistall
i had the same thing happen the other day i opened device manager and unistalled the driver for the phone then pluged the phone back in let it reistall and away i went may have to reistall drivers from kies
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
AdamOutler said:
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
Click to expand...
Click to collapse
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
cobraa783 said:
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
Click to expand...
Click to collapse
No. The device is controlled by windows in a virtual machine.
AdamOutler said:
No. The device is controlled by windows in a virtual machine.
Click to expand...
Click to collapse
Actually ur windows didn't even need drivers for the device ur using in a vm
cobraa783 said:
Actually ur windows didn't even need drivers for the device ur using in a vm
Click to expand...
Click to collapse
It does. Otherwise it will be an unrecognized device and you can't connect it to the VM.
just wanted to chime in here and verify. had a similar problem with odin not working after using heimdall.. used another usb port and odin now sees my infuse.. no problems. thanks guys
Also, wanna say that, for some reason, I had better luck using different version of Odin. Can't remember exactly but I think 1.7 worked & 1.8 didn't - not at PC right now to verify.
Sent from my SAMSUNG-SGH-I997 using XDA
once you install zadig...driver installation for heimdall, it takes over that 1 port.
you can always go back to that 1 port or designate it for heimdall.
odin will not be usable for that port unless you re install samsung drivers again.
I have an (old -6yrs) pc with 1 usb same cord ($1) and 1 usb back port...same 1 for 6 months with heimdall - never had to mess with anything else...successful restore everytime...
use what you're comfortable with.
save that 1 configuration as your rescue if possible.
This topic was as close as I could find to my issue... Heimdall One-Click Kernel...
First of all, let me say that I appreciate all the work everyone has done on the Infuse forums. It has expanded my knowledge by leaps and bounds just by reading for about 5 hours today. I know this will be a long post, and I apologize. I am just trying to show that I have done everything (so far) that is within my ability to try.
I inherited a "mostly working" (sound doesn't work at all) AT&T Infuse 4G, and am trying to install CWM and root the bugger in order to use it on WiFi as a mini tablet. I Do Not have a SIM card for it (I am on SIMple Mobile, not AT&T), and do not plan to use it for calls (already have a phone for that). It was already running UCLB3, but I wasn't sure if that was how the phone came, or if it had been upgraded from Froyo at some point with or without the bootloaders. I had planned to play with this phone some and maybe try out some Jelly Bean since my T-Mobile G2x has lost most of the wonderful devs that it had.
First, I used the Settings>Privacy>Factory Data Reset to clear all the information on my phone and my internal SD card. I made sure that Java was the latest version on my laptop and DL'd qkster's [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3. I spent the next 2 hours reading and re-reading the OP and all the resulting posts to make sure I had a firm grasp on how to do everything. I first booted into stock Recovery and did another Factory Reset from there and also cleared Cache. I booted into Download mode on the Infuse 4G and ran Heimdall One-Click. Installed the Heimdall driver, closed all programs, rebooted the computer, went back into Heimdall One-Click, put the phone back into Download mode, clicked Flash, waited for phone to reboot, turned phone off, went back into Download mode and flashed again, this time with BL checked.
This entire process went off without a hitch. Phone boots into GB and all is glittery gold. It's when I come to the next step in the thread that I started having the issue. Again, from an overabundance of caution, I made sure that I read the thread again, absorbing all the information pertinent to loading the Kernels from One-Click. Deciding to try InfuZen-A16 Kernel, I downloaded it and ran it just as I had the previous One-Click. Opened the .jar, booted the phone to Download mode, clicked Flash, and let the phone reboot. Uh oh. Samsung splash screen is staying on my screen now...
Maybe it just needs a while to process. Left the phone plugged in so it wouldn't lose too much battery life and went and did some more reading on the forums. 5 minutes, still Samsung screen. 10 minutes, still Samsung... No biggie, I'll just read some more. Maybe this is just a longer process than I thought. 30 minutes later, still Samsung. Okay, something must be wrong... Hold down power button to shut it off. 3 minutes holding button, still on. Battery pull...
3-button workout for recovery... Nope, no such luck, still showing the persistent Samsung screen. Back to Heimdall One-Click for recovery to UCBL3. That works. Back into stock recovery. Again, Factory Reset, clear Cache. Download mode, try again. Flash InfuZen-A16 Kernel a couple more times (flashing back to Stock between attempts), using a different USB cable and different USB ports, but still same thing each time, leaving the phone for at least 15 minutes on the Samsung splash screen to see if it moves anywhere. I then tried the ENTROPY512's 4.4.2012 kernel, hoping for different results. Same thing. Tried it 2 more times with different cables and different ports. Each time that I flashed back to Stock, it worked on each USB port and cable I was trying, so I don't "think" it could be the cables or the ports that are causing the issue.
Any help is greatly appreciated. It is my understanding that to get root on UCLB3 and above, I need to have CWM installed, but other than Heimdall One-Click Kernels, the only way to get CWM on a phone is by having it already Rooted. If I am erroneous in this understanding, please point it out and I will happily do my due diligence to fix my own problem.
Thanks in advance for any help anyone gives me.
The custom GB kernels for infuse start a file system conversion immediately upon reboot (from rfs to ext4). If your sound was working, you would hear a robotic female voice providing status updates. This process typically takes no more than 20 minutes to complete, usually less.
If the phone is just sitting there at a samsung logo, try leaving it longer to see if it completes and boots the phone OS.
If it still doesn't work, try the jscott30 Odin package instead:
http://forum.xda-developers.com/showthread.php?p=27286083
Here are the custom kernels in Odin packages:
http://forum.xda-developers.com/showthread.php?t=1698367
IMPORTANT: If you try Odin, use a different USB port than the one you set up for Heimdall. Reserve the Heimdall port for only Heimdall flashing.
For Heimdall, make sure you are using this one (kernels in posts 2 & 3):
http://forum.xda-developers.com/showthread.php?t=1524081
(looks like you are based on the files you referenced above)
Regardless, make sure your USB connection is 100% reliable and you do not interrupt the flashing process - otherwise you may brick the phone.
Thanks for the reply, Zen. I'll try it again when I get home and just let it run for at least an hour.
I have a minor aversion to using Odin, just because it is closed source as opposed to open source for Heimdall. I will take it under advisement, though.
Thanks for all the words of wisdom you give to all the members of xda. :thumbup:
*edit* - Well, decided to just let it ride for over an hour. Took an extended nap after I got home, so after flashing, the phone has been on the Samsung screen for well over 3 hours. I am going to presume that the Heimdall kernel install packages are a no go for me. I will read up on Odin and give it a shot. Thanks again. - *edit*
Sent from my LG-P999 using xda app-developers app
Related
HELP! I was trying to frehsly install a rom..
so i used odin to "master clear" everything
it deleted everything!
hoping that in recovery mode, it'll let me "mount storage" so i can transfer my new rom into the phone, that didnt happen!!!
so, then i tried to go with odin 1 click to install i896 stock...
and it doesnt work , so i unplugged phone, and now i get that mobile phone error..
please help, the only thing i can do successfully do is put my phone in download mode! D:
PLEASE! PLEASE!
THANK YOU!
Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Sent from my SAMSUNG-SGH-I897 using XDA App
Read carefully.....
ags on board said:
Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Click to expand...
Click to collapse
+1
Go into the ODIN thread and read extensively. Since you can get into download mode, make sure that once you connect your phone you get the COM notification in ODIN. Mine always appears in the small box in the upper left portion of ODIN one-click (if you don't get this, reinstall the samsung drivers found in the ODIN thread and reboot. If you're running Win7, make sure you run ODIN as admin).
Master Clear does exactly what it says...it wipes all of your data. MC is only supposed to be used when your phone is on and fully booted up with USB debugging on.
Flashing back to stock should only take ~5 minutes max - if it halts unplug, pull your battery, wait a few seconds, and restart. If it continues to fail, try a different USB port. If using a PC, use the back USB ports. If it still fails, try a different system. (I had this issue this weekend and finally got it on the first run on my friend's laptop - not sure what happened, had flashed 5-6 times on mine previously).
Hope this helps. Once you're back to stock, be sure to thank designgears for his killer dev work!
EDIT:
PS It's pretty tough to brick a cappy - read extensively in the ODIN thread and you'll see what I mean.
Its always good practice to back everything up and know the step by step procedures before you ever do anything. Good luck!
Connexxions "how to" videos are VERY detailed and shows you step by step how to do just about everything on this phone. I highly recommend them.
don't panic, ur lucky that u can still get into download mode. that is just soft brick I think..
Sent from my SAMSUNG-SGH-I897 using XDA App
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
Hello all, any help would be greatly appreciated.
My wife's phone has been rather buggy so I decided to root and rom it. Rooted the phone with the oneclick method. Moved on to getting CWM up and running (it is what I'm familiar with from my G2x). I liked what I was seeing with the Valhalla Final rom OP and decided to give it a try. Read the instructions to install but things have steadily gone down hill.
I am comming from stock. I did a NANDROID backup. Wiped, wiped, wiped and then flashed the ROM. I do believe that I just didn't read carefully enough where it says I "must have pre-installed kernel" . When I rebooted I got a pixelated screen unreadable screen. There was a voice in the background describing what was going on but I plugged along and waited the 5-7 minutes. Figured if it didn't work correctly I would just go back into CWM and restore my nandroid backup. However I can no longer get back into CWM or the recovery prompt that comes before CWM. I just get the Galaxy S 4g screen which then goes to the weird pixelated screen and then it continues in a boot loop.
I tried to follow this debricking thread but got stuck a couple of times. First, that I can't find the boot.bin and sbl.bin files. I google around and found this but the download link no longer works. Does anyone have the boot.bin and sbl.bin files handy?
Also, the Zadig program to install the Heimdall driver doesn't show me any driver options. I suspect that this is because Heimdall or Zadig had not run on the computer before I had the phone properly connected. I saw that it was the Samsung Composite driver that was being asked for. Not sure if I found the correct one but either way it didn't work. I was unable to get the computer to recognize the phone (also phone would continue on its boot loop, also it doesn't change anything whether I am holding down the volume buttons when I turn the phone on or not).
I have stayed up half the night looking for something but am wondering if I just straight up bricked the phone and need to send it to someone with JTAG experience. Let me know if there is something I am missing or some suggestions you have.
Go here:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
The problem is that you tried flashing a gingerbread rom even though your phone still had Froyo bootloaders. If you flash a gingerbread rom using one of the one click files mentioned in the guide, you'll be able to flash more GB custom roms.
Don't worry your phone is fine, you just need to read a little more and you'll be good to go.
Thank you very much for the link, the post is very through. I am getting stuck because my phone appears to not want to go into "Download Mode." Every time I press the up + down vol buttons and plug in the usb I just get the attached images and they go in an infinite boot loop.
I have tried every usb port on the computer and followed the instructions near the first of the post and uninstalled all ports which had Android or Samsung associated with them. I also tried all the different ways I could to get into download mode based on this link.
I am currently in the process of uploading a clip of the infinite boot loop I am in on Youtube and will post it if it helps.
Again thank you all for your help. The XDA community is the best!
That is the rainbow screen indicating you need GB bootloaders. Just pull your battery. You need to flash twice - second time checking the 'flash bootloaders'.
For the driver issue/phone not recognized by the computer - There is a tool in the guide called USBDeview (in the notes). Use it to make sure you have uninstalled all android related/unknown drivers. Go into uninstall programs and make sure you uninstall Samsung drivers. Restart your computer. I also run the CCleanner reg cleaner. Then restart computer again.
For Download Mode - Pull battery. Plug your USB into your computer only. Make sure you are pushing both the volume up and down buttons simultaneously. Without putting battery back in, plug your USB cable into your phone while continuing to hold volume up and volume down buttons. Keep holding volume buttons with USB plugged into phone and computer and put the battery back in.
Start guide over and read thoroughly.
Fb that's the screen I got coming back from nand back up!!! I had to flash a diff kernel with Odin to fix it
Thanks for all your help. Ironically I was doing everything correctly, but my usb cable had gone bad on me the night that it all happened. So thanks all, espicially lumin30 for the excellent guide and for FBis251 pointing me to it. After switching to a working cable and completing lumin30's guide all is now working great!
As a random side note the driver section showed up slightly differently for me (the device I had to pick was [usb composite] but once I figured that out everything went well).
Glad you figured it out
Hey guys, names Michael, new to the forum. Lately my SGS4G wouldn't be recognized by my PC. It charges and I can access the SD Card (Mass Storage). However when I put my phone through download mode it would not be recognized at all. This ultimately keeps my phone from getting rooted, flashing etc. It's a real pain. I tried other PCs, and still wouldn't get recognized. I previously rooted, flashed the kernel and rom. But about a week ago my phone was bricked while attempting to flash another rom. I recovered my phone through Heimdall One-Click. The flashed kernel is still the same but everything else was reset. No root, stock Gingerbread. I have Samsung drivers installed on both my PCs. Still not getting recognized. Some help would be very appreciated.
The Heimdall One-Click is stock kernel. You need to go to the second post of the One-Click thread to flash the custom kernel with the One-Click.
lumin30 said:
The Heimdall One-Click is stock kernel. You need to go to the second post of the One-Click thread to flash the custom kernel with the One-Click.
Click to expand...
Click to collapse
Yes, but the thing is my phone is not recognized anymore when I put it into Download Mode.
Anyone? Should I factory reset my phone?
Factory reset didn't help. Tried a new cord, still didn't work. I'm on my last nerve, the SGS4G has been nothing but a bitter disappointment. Help would yet again be GREATLY appreciated.
don't know man, have you tried re-installing the drivers?
This happened to me, do you have a diff computer you can use? One day mine just stopped working on the PC I used all the time and I tried my gf's PC and it worked I'm not sure what happened.
Every once in a while I have to switch PC's.
Sent from my cm_tenderloin using xda premium
I tried reinstalling Samsung drivers, tried other PCs. Still not working.
Try a different USB cable.
I used two other USB cables, I believe the problem persist with my phone.
I wouldn't say that right away. Just keep screwing around with stuff. One time, I had been using the same chord, and usb slot on the same computer for a long time, and one day it just wouldn't respond to my phone. I tried tons of stuff, but couldn't get it going. Anyways, it just magically started working again after a computer reboot. I took the cord out of the computer, and rebooted it, and after it was fully booted, plugged it back in, and it worked. So keep messing around. Put it in d/l mode, then plug it in with Odin or Heimdall open, and see if they recognize it.
Let's see, where shall I begin?
Got my phone back from my girlfriend since she bought the Nexus 4. Battery was extremely swollen and because of that, the phone basically didn't work. Constantly restarting, couldn't use data, etc... Bought a new battery and decided that I would get a nice fresh ROM installed to get this thing running nice again. It has been on Valhalla for about a year now, and I tried to jump straight to the ICS milestone ROM that I saw in Development. Unfortunately, I didn't know of the new CWM that I was supposed to have, which results in a nice little brick. Frozen at the Boot screen. I was able to get it back into download mode with the volume buttons+cable method and luckily Odin recognized it. I installed a really old KD1 Rom that I had which appears to be all the way back to Froyo.
Now that you are up to speed, the phone boots up fine and seems to be working, but nothing in CWM works at all. Everything fails to mount, which means I can't flash any zips to get off this ROM. To top that off, Odin stopped recognizing it in download mode after I installed that other ROM.
It's been too long since I have been on this phone, and within a couple hours of messing with it again, I can see that I have obviously fallen behind on the development. Any suggestions as to what I should do next? My goal is the get it up to the newest ROMs and see how well it runs. I have the Basic with a twist kernel and ICS milestone ROM ready to go, but no way to flash them.
Thank you to anyone who took the time to read this.
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
th3controller said:
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
Click to expand...
Click to collapse
I didn't even realize it was a Froyo rom, to be honest. I would go and search for a Gingerbread Rom, but the "All roms/rooting/FAQS....." sticky in the development section has been updated in such a long time. I decided to take my chances on that one instead of looking through tons of threads. Froyo was the only one I had for Odin at the moment unfortunately, and Odin was all that I could use.
Thank you so much for the help! This phone should be up and running again in no time!
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
th3controller said:
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
Click to expand...
Click to collapse
Just the Samsung Drivers? I'll try to find them all.
Well, looks like the guide isn't going to work very well for me. I got all the way up to installing drivers with zadig. Heimdall opened automatically like I installed it before ( I may have, it has been forever), but zadig never did. I had to trick it into opening. Once it did open, my phone never shows up in the list of devices as a Samsung device. It only shows up as "Unknown device" and there are no drivers for it to install.
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
TwitchyEye said:
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
Click to expand...
Click to collapse
Finally got around to working on my phone again. Unfortunately, I am unable to follow the guide how I was supposed to. Fortunately, on the other hand, it appears that I successfully got it to flash gingerbread.
Here were my steps to get it work if you want a laugh. My computer didn't like the procedure that the guide had.
1. Update Java, download file, place file into C drive, etc... Everything up to this point worked fine.
2. Open command prompt and execute command. (This is where it all went crazy)
3. Command says false. (instead of opening Zadig, my computer immediately opened Heimdall. So how do I install drivers?)
4. Went to Heimdall help menu and selected install, which froze heimdall completely. Upon Heimdall crashing, Zadig opens.
5. Open Zadig. All drivers are uninstalled, but my device can't be found in the list. (Right after here is where to told me to reboot.)
6. Reboot. Windows keeps automatically installing drivers and I can't do anything about it, so I just uninstall them and try again.
7. Same process. Command prompt, heimdall opens early, crash heimdall, open Zadig, SUCCESSFULLY install drivers.
8. Command prompt again, because that is my only way of getting heimdall open
9. Heimdall finds device, try to flash, but it fails.
10. Unplug phone, and plug in again. Heimdall finds it again.
11. Try to flash again, and success.
It was kind of a nightmare getting it to work, but it looks like it will fix it finally. Thanks for the help everyone!
Double-flashing with Heimdall seems fairly standard. When that happens, sometimes you don't actually have to unplug the phone again, just repeat the same flash-command and it should work the second time. If that doesn't work, reboot the phone, it should go to panic-download mode where it doesn't boot to launcher anymore, just shows the yellow exclamation mark screen, and there the flash should work.
Both my SGS4G and my wife's have done this since we first got them. Sometimes.