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.
Does the phone ! computer graphic mean I'm bricked?
Was attempting to root the phone via Odin/ED1. Pressed start... got a few messages that looked ok, immediately followed (1-2 sec) by:
<OSM> All thread completed. (suceed 0 / failed 1)
Put battery back in, powered up and get the phone ! computer icon.
Went back to Odin and tried loading the stockrootedID1 tar again and nothing... just displays the message:
<OSM> All thread completed. (suceed 0 / failed 1)
Am I perma-bricked?
Thanks.
Not really .....have you tried flashing a different kernel? put phone on download mode by turning off....insert us cable while holding the volume button down and download mode should be there flash kernel and should be ok there
BTW...that's the phone I own and that has happened to me several times .
Thanks M_T_M, that's good to know.
I just got the phone last week and want to root it to run a wifi hotspot app.
I've only found a couple of sources with a root procedure for this phone post patch (verizon charge 2.2.1). They both pointed to the same stock rooted image.
I'll see what kernels are available and how to go about flashing them (odin, i guess).
LTE/4G coverage pretty good in my area as much as 30 down and 6 up... not too shabby for a phone.
I had been running Synergy R72 (with the bootloader unlocked).
Today I tried to flash CM-10 Milestone using Rom Manager. It failed. No biggy right?
The research I did suggested using Odin to flash a couple of files (VRALEC, VRAFL2, Root66). Those processes caused Odin errors too and did not complete and Odin finally got stock at "CS."
After trying to restart Odin a few times (another suggestion) I did a battery pull and restarted the phone (into DL mode) and got the dreaded "System Software not authorized by Verizon has bee found on your phone." (I was searching for the 16GB .pit file in hopes of pushing that to the phone)
Some posts suggest using Odin to get around this but I can't get Odin to even recognize the phone. I tried to use the Galaxy Tool Kit to connect to the phone but it never found it although I didn't exhaust every option on the Took Kit menu).
I think I now have a very personal relationship with the word "Bricked ."
What are my options/solutions?
So you can't put your phone into download mode at this point?
that is correct. Only lights up with the "Unauthorized" screen.
One caveat. This phone is often hard to get into that mode (half the time it boots into "normal") But I've tried to get to the DL mode more times than I care to think about. And will try some more.
Aargh.
I'd keep trying, see if ADB recognizes it and put in "adb reboot download" without the quotes. If that doesn't work, invest in or build a USB jig to force it into download mode. You're SOL without download mode.
mustbepbs said:
I'd keep trying, see if ADB recognizes it and put in "adb reboot download" without the quotes. If that doesn't work, invest in or build a USB jig to force it into download mode. You're SOL without download mode.
Click to expand...
Click to collapse
thanks for that advice. A couple of notes:
- When I do try to boot into DL I do see that tiny blue text top left as if it wants to go into DL mode.
- when you say "see if ADB recognizes it" I'm not at all sure what you refer to? I have ADB drivers on my PC. Is there something to do with those?
- I'm happy to build or buy a USB jig. what the hell is that?
Hmm. What happens if you do take it to Verizon?
mustbepbs said:
I'd keep trying, see if ADB recognizes it and put in "adb reboot download" without the quotes. If that doesn't work, invest in or build a USB jig to force it into download mode. You're SOL without download mode.
Click to expand...
Click to collapse
(I should think a bit more before typing).
I DL'd ADB and Fastboot.
Please provide the exact command strings etc.
I assume that I connect the phone via USB and turn it on. (It will display the "Unauthorized" screen.
Then do I open a command prompt and type "USB reboot download"
If that's correct I get an "error: device not found"
Running "SDK Manager" in the \lib directory returns this error:
FAILED TO EXECUTE tools\android.bat error 2
The system cannot find the file specified.
This actually gives me hope that perhaps ADB isn't correctly installed (not that I know why or how to repair).
When you get to the Unauthorized screen, did you pull the battery and then reinsert, then hold power+home+volume down? This should put it into download mode
yosterwp said:
When you get to the Unauthorized screen, did you pull the battery and then reinsert, then hold power+home+volume down? This should put it into download mode
Click to expand...
Click to collapse
Thanks for your help.
Yes, I've done that many times.
I do briefly see the phone display the tiny blue text top left that evidently presages the DL mode but it just goes "Unauthorized"
maplewood said:
Thanks for your help.
Yes, I've done that many times.
I do briefly see the phone display the tiny blue text top left that evidently presages the DL mode but it just goes "Unauthorized"
Click to expand...
Click to collapse
You can buy a usb jig from mobile tech videos, Google it. Also look up the tons of guides for adb. You get the sdk and android platform tools, from there you open a command prompt in the folder containing adb-windows.exe (I don't think they renamed it yet, you can for ease of use though to just adb.exe), put the command in adb reboot download and you should be set. Make sure your phone is connected and turned on.
Tl;Dr just look it up lol
Recovering from soft brick
yosterwp said:
When you get to the Unauthorized screen, did you pull the battery and then reinsert, then hold power+home+volume down? This should put it into download mode
Click to expand...
Click to collapse
Well the stars must have re-aligned. I can finally get into DL mode.
But I'm not sure what is on the phone so am quite clueless as to what to start rebuilding. I had been following this thread http://forum.xda-developers.com/showthread.php?t=1840030&page=5 when things went pear shaped.
I'm gonna follow the measure twice, cut once methodology next but don't know what files to try to flash to the phone. (that thread recommended VRALEC, VFRALF2 and Root66. It believe things crapped out with Root66)
<<TIME PASSES>>
Flashing VRALEC.bootchain.tar.7z worked fine.
However trying to add . BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar (or more precisely the MD5 version thereof) fails because every copy of the file I find evidently is "invalid"
Odin says:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 is invalid.
<OSM> End...
As I've tried to download that file from different sources I'm starting to think that the problem is not in the file but in something I'm doing. ??
BTW: the phone displays the following:
Odin Mode
Product Name I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
I've read the other threads and used Google before I started this thread.
Before the phone changed hands, and I wanted to connect it to Kies, I did a factory reset. The phone is on firmware 2.1
After wipe data/factory reset and wipe cache partition were performed rebooting the system resulted in the phone going black, showing the GT-I5800 screen and returning to the recovery screen as shown. I removed the battery multiple times, long and short. Sometimes after rebooting it showed the green android with an exclamation mark. I then left it like that for the night but then the recovery returned. I installed the program Odin via Parallels on my Mac. But the USB connection is only long enough to ask to connect to Parallels and when the phone boots to recovery it never shows up in Odin3.07. I am from the Netherlands, concerning the firmware version. At the moment I'm looking for a possibility to revive the phone via the SD card or, of course, any other way. Is there a way to show the phone on the computer again?
try with windows environment and boot device into download mode and try to re-install sammys drivers to of....then perform flash with odin....
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
OK, sammys drivers are re-installed. Phone in download mode. Now I've ODIN 3.07 and ODIN I5800 multidownloader v4.252. Which one to use? I've I5800XWJPI.tar, size 229MB. The ID;COM still fails to show the phone. Pressing start in v3.07 and the tar file at the PDA line gives the following message:<OSM> All threads completed. (succeed 0 / failed 0).
After a while the phone drops out of the download mode. With the ODIN Multi downloader it just mentions please connect phone when I press start.
Mike_2200 said:
OK, sammys drivers are re-installed. Phone in download mode. Now I've ODIN 3.07 and ODIN I5800 multidownloader v4.252. Which one to use? I've I5800XWJPI.tar, size 229MB. The ID;COM still fails to show the phone. Pressing start in v3.07 and the tar file at the PDA line gives the following message:<OSM> All threads completed. (succeed 0 / failed 0).
After a while the phone drops out of the download mode. With the ODIN Multi downloader it just mentions please connect phone when I press start.
Click to expand...
Click to collapse
try to explore op of this http://forum.xda-developers.com/showthread.php?t=1478503 wonderful thread by @PersianSphinx
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
Mike_2200 said:
OK, sammys drivers are re-installed. Phone in download mode. Now I've ODIN 3.07 and ODIN I5800 multidownloader v4.252. Which one to use? I've I5800XWJPI.tar, size 229MB. The ID;COM still fails to show the phone. Pressing start in v3.07 and the tar file at the PDA line gives the following message:<OSM> All threads completed. (succeed 0 / failed 0).
After a while the phone drops out of the download mode. With the ODIN Multi downloader it just mentions please connect phone when I press start.
Click to expand...
Click to collapse
Oh dear, looks like you're having a bad time :-/ Check my thread out, go to my profile and find my threads to find it. You see, l had this same problem a while back using my brother's laptop instead of my own Seems like an uncommon Android thing; some phones go faulty like this. Besides, why are you wanting to flash Samsung firmware? Use costum ROMs, they are so much better(er). Ok, I actually went ahead and read this thread. I tried to do a similar thing from boot-camp and didn't work. Put Odin on a stick along with your firmware and use a friend's/family member's Windows pc. You will have to put the phone on recovery and connect to Kies (or you know, any other way you know of that installs your drivers), let's cross our fingers that this works.
Thanks for all the replies. :good: Since it was consuming too much time, there is a new Samsung Advance in the house. I will definitely give it try on a windows computer. Somehow I want it to work. If I find the answer in the near future I'll see if the thread is still open and post the solution.
And why I don't install the custom ROM's is that I otherwise have to familiarize myself with those too. Even more time consuming.
Mike_2200 said:
Thanks for all the replies. :good: Since it was consuming too much time, there is a new Samsung Advance in the house. I will definitely give it try on a windows computer. Somehow I want it to work. If I find the answer in the near future I'll see if the thread is still open and post the solution.
And why I don't install the custom ROM's is that I otherwise have to familiarize myself with those too. Even more time consuming.
Click to expand...
Click to collapse
You really love time no custom roms based on stock function almost exactly the same as far as the ui goes but they are better and faster. Do update this thread though
Sent from my Xperia Miro using xda premium