I updated to Whitehawkx's Valhalla, and flashed successfully, although when booting I would get a fuzzy/snowy screen.
After reasearching, I found that I needed the GB bootloaders. So, I went to the Bible post, found the "updated bootloader" GB ROM, and attempted to flash it via odin.
Here's where I think I went wrong. I put the phone in download mode. In Odin, which I've used extensively in the past, I checked the "Phone Bootloader Update" checkbox, then attempted to load the PIT, Phone, and CSC files from that GB ROM linked in the Bible post.
It hung.. I let it sit for well over an hour, and it was just stuck on zImage, in the "Message" area of Odin, where it shows progress.
I unplugged the usb, replugged, tried again.. same thing.
I rebooted phone, and it no longer goes into bootmode. I get an active screen, that displays a small handset icon connected to a PC icon, with an orange warning triangle between..
Again, cannot get into download mode, even with every method posted. It always just displays this same graphic.
Since the display is functioning, I assume it is not hard bricked.. but hoping for something to help!
Thanks mucho in advance. I have many hours into trying to recover, before coming to the community with tail between legs.
hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
I wonder if you might need a jig to be able to get it into DL mode again? There is a post about that somewhere, but I can't seem to find it at the moment.
mike-y said:
hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
Click to expand...
Click to collapse
Yeah, as I mentioned, that's where I think I went awry as well. Figured that since I was primarily wanting to replace the bootloader, I should check it. Probably my big downfall though.
Odin should still be able to pick up your phone with that screen. It might take a bunch of tries as well as switching between 1.7 and 1.85. Just keep trying. Flash kg4 then Honks kernel. Should give you cwm access then reflash valhalla
You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App
CozzaFrenzyy said:
You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.
Bimboy said:
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.
Click to expand...
Click to collapse
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App
farwek said:
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Excellent help, that allowed me to get the phone connected. Appreciate it.
However, I can get Odin to see the device, but do nothing with it. I've tried flashing the KG4 as recommended, then I tried a few others, including going back to KC1.
I can never get past "Setup Connection" in the log, which looks like this:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> pda.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
So, I'm connecting, starting the process, getting MD5 validation, and then not connecting. So, I think I am VERY close, but I can't get past this.
Greatly appreciate more thoughts, even if it's unrecoverable. You guys have got me this far, and I appreciate it.
I had this happen the other day and had to go back to KC1 "fix", found here.
That link 3/4 of the way down on the first post will give you like 3 or 4 files to put in odin. Before you try it restart your comp and phone. Good luck!
Hey golmar.... ... Did you use your own bible thread to find that link?
FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
List of dangerous ODIN stuffs.
1. Repartion with wrong pit(wrong means never able to boot again even with bootloader fix)
2. Check "bootloader update"
3. "EFS clear"
4. Put a file with bootloaders in the "bootloader" section. You have to put it in PDA.
5. flash wrong bootloaders. ( you can unbrick using a few methods)
6. flash the wrong rom.
airfluip1 said:
FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
Click to expand...
Click to collapse
Yes, I knew it, as soon as I did it, as I stated.
I got it to start to flash, and then hang.. for hours. I saw probably 5mm of a progress bar on the phone. From there, I can now go into download mode via battery pull/usb/volumes/battery insert. However, I can never get past "Setup Connection.." in ODIN.
Luckily, I have had a work holiday to day to "labor" over this less-then-optimal situation. Still nada though. I continue to get messed up drivers, and when I get the correct ones loaded, I only get to "Setup Connection..." on the ODIN flash.
Over the years, I've gotten into many "close to paperweight" situations, when cooking early WM ROMs. I've never been this deep in time to recover.. without results.
You must use heimdall to insure optimum results, also there is a different driver. Just follow my post on heimdall. It is in the development section. Also, I would suggest using version 1.1.1 instead of 1.3.x or whatever. It should be on the heimdall site. Just google it. All the archived versions are still there. 1.1.1 is easier, as it has a more easy to use GUI for some people and you don't need to use a pit file. Primary boot loader is boot.bin and secondary boot loader is sbl.bin. Make sure you have C++ 2010 redistributables on your computer and navigate to the "drivers" section in the folder you download. Open zadig, and then go to options and list all devices, you should then see Samsung composite USB or something like that, click install driver, when it is done, just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.
Thanks airfluip1! I'll give it a shot tonight. I already had tried Heindall, from you post, so I have it all downloaded already (1.1.1), along w/C++.
airfluip1 said:
... just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.
Click to expand...
Click to collapse
Well, with Heimdall, I get consistent, replicatable failures. I can flash the primary bootloader, but it always fails at 20% on the secondary bootloader (even tried the "backup secondary bootloader" flash with the same result:
Code:
c:\heimdall>heimdall flash --primary-boot boot.bin --secondary-boot-backup sbl.b
in
Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading backup secondary bootloader
20%
Failed to send file part packet!
Backup secondary bootloader upload failed!
For some reason, it will not let me flash it.. So close, I can taste it. FWIW, MD5 checks fine on the SBL file. Also, I started with the heimdall_frontend, but prefer the feedback the commandline offers.
Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App
Light-라이트 said:
Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thanks! That was something I tried immediately. I may be looking at something I need a jig for. I wonder if partitioning got hosed, and it is not allowing me to write to disk, where it thinks it should be. Also, not sure if it is worth my time, compared to buying the next latest and greatest. Kind of a good news/bad news scenario.
Just wanted to thank everyone for this thread... I ran into the same problem as the OP did when I tried flashing Valhalla.... Somehow I manged to completely overlook the giant red bold message about needing the GB bootloader. So, I got the boot loop and the fuzzy screen mentioned, but what I did was go into download mode and Odin flashed Krylon's stock+root per this extremely detailed tutorial.
Tomorrow I'll probably entertain flashing up to GB, but for now I'm just glad not to be bricked....
Try this DL mode method
Get the KG4 leak and load it into Odin.
Leave everything as-is (including re-partition).
Pull the battery from your phone.
Plug the phone into the PC.
Hold Vol+Up and VOL+Down while connecting the battery.
Once Odin picks your phone up, hit start.
You *really* shouldn't have any problems at that point. I've encountered the exact same issue, and entering DL mode using this method worked for me.
Once your phone is up and going on KG4, use Odin again to flash Valhalla, and you're good to go
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
Thank you! This thread saved my bacon. I had the snow after a failed Heimdall. Odin 1.7 and a different USB port enabled me to get back.
Related
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.
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
Phone (Droid Charge) is completely unresponsive after I tried flashing to the factory ROM using Odin per this link: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11. (Two attempts to flash to this ROM aborted in CWM.)
When I used Odin, I got only <OSM> messages in the message box, ending with this one:
<OSM> All threads completed. (succeed 0 / failed 0)
The green status bar never appeared, and the "Start" button reactivated. I did this twice with repeatable results - nothing flashed. I then made the (apparently) huge mistake of removing the USB cable from the phone. It is now a paperweight. No response to power button, no response to plugging phone into wall outlet for charging (battery symbol doesn't appear).
Any ideas, or am I totally screwed?
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
My experience is nothing compared to others but I had a situation similar but for some reason I ended up using the Samsung Flash program instead of Odin and after hours of screwing around it worked.
imnuts said:
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
Click to expand...
Click to collapse
I have tried to do this. Nothing appears on the screen when I connect the phone with the volume-down button depressed.
By the way, before I flashed the ROM (or tried to) I first did the PIT thing per the following thread: [HOW-TO]Fix your phone
Additional info: here is the log of ODIN messages.
<ID:0/003> Added!!
<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..
<ID:0/003> Firmware update start..
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
Did you check "re-partition" in Odin before you flash?
If your phone doesn't display logo "Samsung" then your bootloader is shot. The phone is brick for good. Only by miracle it may come back to life. Just let it rest for a day then retry....it's in coma...sorry.
buhohitr said:
Did you check "re-partition" in Odin before you flash?
Click to expand...
Click to collapse
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Look, guys, I think it's clear that I'm hosed. But don't hesitate to ask for more details so that fixes can be developed to help prevent the next guy from suffering the same fate. Rooting has been an expensive, time-wasting exercise for me, and I'd rather it not be for anyone else, if possible.
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
buhohitr said:
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
Click to expand...
Click to collapse
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
The only time removing the USB cable during a flash can result in a brick is while it is flashing sbl.bin AFAIK because that is what contains the "download mode". You can usually recover it without too much trouble otherwise. I don't think that was the root cause.
Sent from my SCH-I510 using Tapatalk
MaxBuck said:
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
Click to expand...
Click to collapse
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable) you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
If I read it right you flashed just the rom with repartition selected one of those times?
Sent from my SCH-I510 using xda premium
Hindle1225 said:
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable)
Click to expand...
Click to collapse
That is correct - I can get no response whatever from my phone whether I attempt any of the following:
- going into download mode with battery removed OR installed, using the USB port directly on my computer.
- turning on the phone normally
- turning on the phone with the home button depressed
Hindle1225 said:
you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
Click to expand...
Click to collapse
Correct.
Hindle1225 said:
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
Click to expand...
Click to collapse
PIT file came from here: [HOW-TO]Fix your phone
ROM installed at the outset of this process came from here: [12-14-11][ROM][EP4D] InfinityROM
ROM I was trying to flash to came from here: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11
Hindle1225 said:
If I read it right you flashed just the rom with repartition selected one of those times?
Click to expand...
Click to collapse
Not sure what you're asking here.
Again my knowledge is very limited but all of what you described I went through and eventually recovered. I pulled the cable out while installing. It didnt see it in Odin. Says it installed but didnt. And Im sure several other things. In my mind this thing is really hard to totally brick. I reinstalled all samsung drivers, downloaded the files again but used the Samsung Flash program to get back up.I tried different ports, cables etc.I went through the stuff you are for almost 8 hours lol before I finally got it running but it did. Cant hurt to try everything one more time. If you feel it is a paper weight then and have no recourse such as warranty sell it.Crap I might buy it cheap to waste a couple of hours(lol) just to see what I could do.
MaxBuck said:
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Click to expand...
Click to collapse
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
MaxBuck said:
Not sure what you're asking here.
Click to expand...
Click to collapse
I was making sure I knew the steps you went through. If you really can't get into download mode, thats bad news.
imnuts said:
There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time.
Click to expand...
Click to collapse
This is what I was getting at.
Sent from my SCH-I510 using xda premium
imnuts said:
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
Click to expand...
Click to collapse
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
imnuts said:
...
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
...
7. Press "Start" and flash the package.
Click to expand...
Click to collapse
It seems that step 2 is what you were confused on - while I can't speak to how others interpret this my interpretation is that there is something in both PDA and PIT before pressing start. I seem to remember something about folks that "unbricked" phones for something like $40 - mobiltech video or unbrickable mod are terms that come to mind. In the same How-To thread the above instructions are quoted from are folks mentioning such things at least.
Just get your phone unbricked for 40 bucks. then I would either get a new comp to flash with or borrow a friends comp. I suggest using spc latency checker on your comp to see if you have latency issues. Also, try a new cable. I have found that many cables don't work well.
Sent from my SCH-I510 using XDA App
MaxBuck said:
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
Click to expand...
Click to collapse
I'm pretty sure you did it wrongly.
Like others comment, you only need press START button once, AFTER you select PIT file and ROM file (in PDA section), tick the Re-partition (and leave the other unchanged). No need to press START button twice (it seems you press it twice? based on your explanation) ...
If you still able to enter DOWNLOADING MODE, maybe better if you try to reinstall your samsung driver and maybe change the usb port used to flash, or if needed restart your computer ... and after it is detected by ODIN, do it again in the correct way ...
Hope you can unbrick your phone ...
For what it's worth, I've flashed the PIT file by itself in Odin with no problem. Completely acceptable but like was mentioned, you shouldn't really need it in most cases, even situations like this. But I wonder if somehow Odin attempted to flash sbl.bin and failed. That has the potential to hard brick the phone for sure since that file contains download mode. Does anyone know of another way to push the bootloader files to the phone?
Sent from my SCH-I510 using Tapatalk
Did you ever get this phone recovered and/or try one of those $40 programs someone mentioned? I am in the same boat it seems. =(
Hello everyone, before I start, I want to let everyone know I have searched endlessly for a fix, etc.
I have a SideKick 4G that I purchased maybe a month ago, and yesterday I went ahead and tried to flash a custom ROM on it. Now my issue is, I was hap-hazardly strolling through the menus and doing the procedure so I didn't back anything up or check the mounts etc.
My issue is, I have Odin and the sk4g.pit file, but I can't find the KD1OdinSTOCK.tar or KG2OdinSTOCK.tar files, because the file hosts are down... permanently.
I also do not know if I have the KD1 or KG2 firmware, what the difference is, and if any problems could be caused by flashing one or the other onto my device. I'm pretty new to the whole process and I was only looking to make my phone faster and less clunky.
If I get the files, a quick walk-through for my specific situation would be very highly appreciated.
Thanks in advance!
EDIT: I found a newer firmware for the SideKick 4G, called KH1, Not KD1, KG2, or KJ1.
To get the file:
1) Go to SamFirmWare.com and make an account
2) Search T839UVKH1
3) Make sure you find the firmware for this model. "SGH-T839"
4) Download it
5) Make sure to look for what password you'll need to open the file (This one is marked with "##")
6) Input password when extracting the file to wherever you want to put it (The password for this one is samfirmware.com)
That should be it.
My issue now is that Odin isn't recognizing my device. It's in download mode and I have the factory cable but I must be doing something wrong as I can set the PIT file and the PDA file, tick boxes etc. but I can not for the life of me get my device detected.
Alright, later update.
I got Odin to recognize my phone, and now I'm trying to flash it.
I don't seem to be having any negative impact with my firmware (KH1) and sk4g.pit, however it always fails at write boot.sbl OR, it gets stuck at Set PIT file.
My phone changed from the Downloading... mode to the Phone - ! - PC picture, however, I was told I can still flash from this mode. I've been continuing to flash with different settings in hopes of reaching recovery, and so far what has NOT worked:
Auto Reboot
Auto Reboot + Re-Partition
Auto Reboot + Re-Partition + F. Reset Time
I don't believe I've tried Auto Reboot + F. Reset Time without Re-Partition, or Re-Partition with F. Reset Time.
Any advice or comments?
Update #2.
http://forum.xda-developers.com/showthread.php?t=1350060&page=6
This thread seems to have a link to a oneclick stock recovery as well as KG2 firmware, judging by the 254 MB download (THAT WORKS BY THE WAY.)
Hopefully after I download this, I can get the phone running. Will post later to inform a yay or nay.
Edit: I almost successfully flashed to stock KG2 Firmware. All went well (Kernal, Recovery, etc) Except it failed at the modem.
It rebooted after failing modem and now I'm stuck at sidekick boot logo. It's better than having Phone - ! - PC though.
EDIT 2: Seems that it keeps failing at Modem, part 3 of 6. along with that, it does restore the phone to Download mode rather then the broken sync picture. Odin now does not recognize the phone, but I think that's due to the other drivers the oneclick method prompted me to install. I'm going to try to disable those drivers temporarily and see what odin thinks about it.
Update #3.
I discovered the drivers downloaded to run the oneclick as provided by the link in the previous update did infact block connection to odin with the same device.
Uninstalling the driver got the connection going again. Every time in Odin, I fail at writing either boot.sbl or cache.rfs.
I took the files from the KG2 firmware and compiled my own .tar out of them and when I flashed using my compiled tar, that's when I got the cache.rfs write error. Phone has shown no signs of improving or deteriorating. I can go back to oneclick recovery and get the phone out of broken sync picture mode, and back into Download mode. However, here are my 2 issues flashing.
In Odin:
I either have no connection, or
I can't write boot.sbl or cache.rfs and fail.
In Heimdall One-Click KG2:
I need the driver Odin doesn't like, and
I flash almost all the way through, but fail halfway through uploading MODEM.bin.
It's giving me the opportunity to flash Boot Loaders along with KG2 kernal, recovery, modem, etc. It's the only thing I haven't tried yet.
Update #4.
I'm about to flash bootloaders. Wish me luck
EDIT: I'm about to cry :') I THINK IT WORKED. I'm loading boot screen.. got animation and now got samsung screen, waiting for the phone to boot. got a fully successful oneclick and it's looking well at the moment
YEAH!!!!!!!!!!!!!!!!!!!! HOME SCREEN!!!!!
Nice monologue.
Thank you sir. What do you think of the things I did to get my phone working again? Anything you think I shouldn't have done? o_o''
Hi everyone. I've been reading these forums for quite some time and I have been flashing some of the custom roms that the developers have made (I think they're all awesome). I thought that I was confident enough with flashing to give the CM7 rom a try. I followed FBis directions (not the one click but the slighter harder version) and upon flashing using heimdall I had an error saying that the PIT was flashed but the Kernel wasn't (unfortunately I was too stupid to write down the exact error).
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue but another problem exists, my computer (win 7) upon plugging in the phone only sees it as a unknown device. I tried changing the driver manually to Samsung USB composite but it gives an error saying device is not working properly. Is there anything I can do to fix this brick? I just can't get my computer to recognize that my phone is connected so it's not possible to heimdall since it also thinks no device is connected.
Any help is greatly appreciated it. I have searched the forums for a similar situation but I think mine is unique so I made a new post, I know people don't like to repeat what is widely available.
Whenever i had that happen trying to install cm7 i just used the 1 click gremlin remover and it flashed back to stock for me.
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my SGH-T959V using XDA
Hi, nvm I fixed my issue
Yes I've tried to heimdall back to stock (or rather the new AntonX one-click that Bryan had made) but my phone was unrecognized. Instead of trying to update the driver manually through Device Manager I downloaded the Samsung 64bit drivers for our phones and ran the setup.exe. That seemed to overwrite the drivers and next time I put my phone into download mode it was recognized and all was well.
Sorry for taking up your time.
Turns out I haven't fixed my problem. My computer is able to recognize my phone now and so I've tried One-click heimdall back to Stock UVKJ6 under Bryan's thread. I flash it, however, I get the Samsung splash screen and nothing else happens. I go into recovery and it is still the blue CWM and it gives me errores that it cannot mount or open /cache/recovery/log. If a try a nandroid restore it cannot format volume and says make_extf4fs failed on /dev/block/stl10
I tried the one-click again, I flash once, let it restart, the flash again with bootloaders but still get blue CWM. Even if I try to flash bryan's SMSKJ6bml-rc2 kernel, I still end up with the blue CWM.
Anyone have ideas on what can be wrong?
http://sourceforge.net/projects/tea...T959VUVKJ6_STOCK-UVKJ6-One-Click.jar/download
oh wow, I was just flashing the one-click kernel, I'm a noob.
Thanks a lot FBis, I should have known better.
How did you solve it, now?
johndeere5 said:
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue
Click to expand...
Click to collapse
Hi! I'm having a similar problem with that "firmware upgrade encountered an issue" message, driving me crazy. I gather you fixed the issue? Maybe I'm dense, but I can't figure out exactly how you did it. What exactly is Heimdall? Is that what you used? Other posts in this thread mention Gremlin Remover, did you use that? Where can I get Heimdall, and how do I use it if I do get it? I'm definitely a noob, but my need is real, any help will be appreciated. Thanks! R
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Why Not ODIN?
lumin30 said:
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Click to expand...
Click to collapse
Thanks, a few things I want to clear up though? I've heard that Heimdall doesn't work with Galaxy S2. Is that correct? In any case, isn't it just the same kind of program that ODIN is? I've been trying to use ODIN to flash a file called
recovery-cmw-hercules.tar
but it always fails. What will Heimdall do differently?
You can tell I'm pretty new to this, have patience with me please.
Incidentally, when I try to run ODIN, on the assumption that I'm seeing a download mode screen, I can get ODIN to detect the phone and I see COM(6) usually in the yellow-highlighted screen. I check only "auto reboot" and "PDA," and in the PDA field I insert the location of the tar file (above). Here's the result:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Every single time.
Kindly, R
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Make sure you're using a samsung galaxy s 4g sgh-t959v. If that is not your phone stop flashing, look up the correct forums and only flash files from THAT forum, not from any other one.
lumin30 said:
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Click to expand...
Click to collapse
Oops! Where should I go then? Thanks, R
The T-Mobile galaxy s2 forums would be my first guess