Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
Related
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Early yesterday I launched Kies and hit the update firmware option from the tools menu to see if the alleged ICS update was available for my phone. It appeared it was with, a message promoting that it would clear all personal data from the phone, which I then selected cancel so I could do a backup of pictures/videos on the phones internal SD.
Without doing any sort of backup yet I shutdown the phone, only for it to freeze on the shutting down screen. After 20 mins I pulled the battery and let the phone cool down since it had gotten warm trying to shut itself down. After replacing the battery and turning on it was stuck in a bootloop with only the SGS2 logo, never reaching the ATT logo.
At that point I came to XDA, which I frequently browse but have yet to root, and began reading and searching everything I could find.
Hours later I decided to attempt to flash the stock firmware from sammobile.com using Odin. The flash took a long time and I assume never completed. I left it overnight since I didnt want to unplug it mid-flash. Checking back in the morning the phone is black, Odin says failed/disconnected, and I find the battery completely drained. I charged it for a while then tried turning it back on and got the yellow triangle "firmware upgrade encountered an issue..." screen.
Now i'm attempting once more to flash the firmware but again it has been 30 mins on Sbl.bin. I've had a hard time finding stock firmware in different varieties with working links, so to not increase the flash counter in the event I ultimately have to send it in for repair.
Any suggestions on where to go from here? I've followed every direction I can find for flashing stock firmware and nothing has been successful.
Glad to help if I can. Please tell me exactly what package you flashed from sammobile, with a link if possible.
You should change the title of the thread.... I killed my phone. LOL!
http://forum.xda-developers.com/showthread.php?t=1313659
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
Try this.....
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile. Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
SOURCE: http://forum.xda-developers.com/showthread.php?t=1311081
creepyncrawly would know better. It's his thread.
Download the file from below post to go back to stock I777UCKH7. Follow the instruction written in the post. I just had the same a while ago using the mobile odin to go back to stock. Got stuck on Samsung Galaxy SII screen. Pulled the battery and then followed the instructions from this post. I selected the one that says no BL 'I777UCKH7 OCD No BL'.
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
Once you are done with the stock restore. To upgrade to ICS LE5 follow the instructions from below post. Make sure you read and follow the instructions as mentioned in the post.
http://forum.xda-developers.com/showpost.php?p=27707563&postcount=83
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
You downloaded I777UCKH7_I777ATTKH7_ATT and extracted I777UCKH7-rev02-home-low-cl503881.tar.md5?
Flashed the .tar.md5 in the pda slot?
What version of Odin are you using?
Edit: You're getting lots of advice here. Let me know if you need me to help troubleshoot your issues.
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
nett3 said:
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
Click to expand...
Click to collapse
Try using another micro usb wire if you have one. If not then get one from radioshack or bestbuy. I had the almost similar issue on my captivate with the original USB cable. Then I got a Rocketfish one from bestbuy and it worked like a charm.
I'm sure you might have already done this. Make sure you first run the ODIN and then put your phone in download mode.
krips your a genius!
The one click is now working thanks to the suggestion to pay attention to order of operations. I must have never plugged the phone in AFTER starting the one click. This was easily overlooked when I've been switching the phone between 2 PCs and 3 micro usb cables.
I now have a progress bar and have had made more progress than in the last 24 hours. Even after searching I did not find this solution, even though it's stated in the directions and it seems trivial, maybe it should be emphasized the one click needs to phone plugged in after it's running.
Thanks again. I'll update this post when it's back to being a phone again.
PS. BROKKANIC: you were right, if I didn't kill my phone then I sure was the impeding factor in its recovery.
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Is this a bootloader problem, kernel problem, or something else?
LOL!. Glad you got it working.
nett3 said:
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Click to expand...
Click to collapse
Flash back to stock first.
BROKKANIC said:
LOL!. Glad you got it working.
Flash back to stock first.
Click to expand...
Click to collapse
I believe that what I have been doing. I ran I777UCKH7 OCD With Root.exe, which resulted in bootloop, then ran I777UCKH7-CL503881-No-BL.exe, which also resulted in bootloop. Both completed successfully, but resulted in the same bootloop.
Odin appears unable to flash anything without it being a one click. I'm trying to flash Siyah-v2.6.14-att.tar. But Odin hangs at zImage with no progress bar.
What operating system you using: if windows 7 are you running as administrator ?
hd779 said:
What operating system you using: if windows 7 are you running as administrator ?
Click to expand...
Click to collapse
I've resorted to my WinXP laptop which has been more successful than my Win7 desktop. On the Win7 attempts everything is run as admin, but has many time bluescreened and hard reset the whole PC when attempting to flash anything with Odin. Maybe a separate issue, maybe not. But the XP machine is atleast successfully flashing the Odin one clicks.
Update: Odin standalone (non-one click) appears to be unable to flash anything, it will only hang when trying to write. One click Oden packages seem to work. Is there a one click with full stock sbl, param, kernel, etc?
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
gefox4vn said:
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
Click to expand...
Click to collapse
I haven't flashed a package with a bootloader yet. The only ones that work for me are Odin one click packages, and the two I've tried do not have bootloaders. I've been looking for one WITH a bootloader but no such luck yet, since maybe that would solve the problem.
The guide/link you've suggested will not work for me at this time. I do not have the ability to boot into any andriod OS. The only capability my phone has is executing Odin one click packages for some reason, even Oden standalone firmware flashes do not work.
I had a similar issue...I eventually got mine stuck at the ATT droplets....
Finally I flashed back to 2.3.4 stock....did the ota...then upgraded to ICS.
Its all on my work laptop so I wont be able to post any specific files or their names until monday...
Good luck!
Once your phone gets to the boot screen try to get into stock 3e (both volume buttons + power till 2nd SGSII splash screen) recovery and do a factory reset. Should boot after that. Good luck.
Sent from my SAMSUNG-SGH-I777 using xda premium
Why not try a custom ics rom? What else do you have to lose? Staying stock is overrated anyways. You may also have an antivirus stopping Odin but I doubt it. Just turn off your antivirus and try.
Sent from my SGH-I777 using xda premium
I've searched for hours for different solutions and have tried them all. I'm on my last leg, and I can't wrap my head around what is going on.
I'm running an S2 with ShoStock3 rom. It's been rooted for over a year now without any major hiccups at all. Last night, it froze on me. Usually when it does this, I just force-restart by holding the power button down until it cycles. Phone usually boots right back up, and I'm all set. This time it just stayed on the boot screen. For eternity. I let it sit like that for more than 45 min, and it never budged. Turn it off from the booth screen, it'll boot right back up. I can go into download mode, but not recovery, and every little trick I've tried works.
I've tried flashing new kernels with ODIN. Tried various recoveries, like Philz and even went as far as the one touch factory ROM and using the regular method for getting the stock ROM. Nothing. Maybe I'm doing something wrong. Most people who have this problem only recently added a new ROM or modified something. I haven't touched the ROM, kernel, etc. for over a year before this happened.
ODIN never makes it far when trying to flash anything. It depends on what is being flashed. It never gets past nand read/write. It never gets past boot.bin. It never gets past factory.img. Etc. Etc. I don't know if maybe something isn't going through between computer and phone, and that's why I'm not having success or what in the world is going on. Every tutorial or help I found confidently stated that all you have to do is flash this kernel, go to recovery, clear cache, and you're all set. But I feel like I'm the odd man out.
I'm afraid that this won't see much attentions, as the S2 is far from new, but like I said I am on my last leg. I just don't understand how it stops working from cycling power. I also don't understand how every attempt doesn't even scratch the surface. Any and all help will be greatly appreciated
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
SteveMurphy said:
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
Click to expand...
Click to collapse
^^ while the device is NOT USB connected to a computer.
Actually, you're lucky. This device is so popular, even though is it getting old, that there are still a handful of knowledgeable people hanging around.
You need to get into recovery. As Steve and Cyril have said, try the correct button combination, and post back here to verify that you are using the correct combo and that it will not go into recovery.
If you do get into recovery, perform a wipe data/factory reset and see if that gets your phone to boot into the system.
If you are unable to get into the recovery with the correct combo, then you may have one of several possible issues. The first possibility to troubleshoot is nand read/write corruption. Do the following:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
creepyncrawly said:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
Click to expand...
Click to collapse
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
XxArxAngelxX said:
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
Click to expand...
Click to collapse
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
creepyncrawly said:
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
Click to expand...
Click to collapse
Tried using different computer. Brand new cord. Multiple times tried. Different ports. I dunno, it's doing the same thing. It stops whenever it gets to NAND Write Start.
EDIT: Tried something I saw in another thread. Used stock binary with pit file. Never finished, so aborted it. Now phone doesn't come on at all for any reason whatsoever. -.- Pretty sure I fried it
Hi. I have spent the past 10 hours trying to root my phone and install an XtraLite type of ROM because I am so sick of have 75% of my RAM used up when I haven't even started using the phone. I softbricked my phone, and after hours of trying to solve every minor issue that came up I finally found a solution and managed to flash a stock ROM. I have a lot of questions that I would love to get answers to because I am a little bit confused right now.
My history.
Bootloader
I spent so much time googling this and I decided to trust one site that said, if you can't find the "OEM Unlocked" option in "Developer Options" then your bootloader is probably already unlocked. This was the closest I got to an answer, along with many people with SM-G925F saying the root was successful for them without doing something to their bootloader. Can someone please clarify what I need to do with the bootloader with my EU SM-G925F?
Flashmode/Download Mode
Prior to this I spent very long trying the "adb-windows reboot bootloader/flashboot-windows oem unlock" without any results. However I somehow came to the conclusion that "Download" mode for my Samsung was no different. Any clarification on this subject please?
Rooting
The first rooting guide I trusted was the CF-Auto-Root page. This is where the bootloader question was raised but as I came to the conclusion that the bootloader already was unlocked, I decided to give it a shot. I downloaded SM-G925F file, added it to AP on Odin, and flashed my phone. Now my phone was locked in a bootloop. According to CF-Root page "A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery. For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.". As you probably guessed, my phone never booted into recovery mode, and I was never able to manually do it either since the phone was in a unstoppable bootloop. Did I do something wrong here or misunderstand anything?
ROM Instructions
My first choice was: http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
I failed the first step, never even managed to root with CF-Root. And regarding TWRP, I did download the correct version "twrp-3.0.0-0-zerolteeu" I assume. However, many descriptions say my phone needs to be rooted before I can install TWRP so I never tried to install it. Even if, I couldn't find a detailed enough description of how to install TWRP. All it says is "flash it". Problem is, I am not sure if I am supposed to be in "Download mode" and use Odin loading TWRP into "AP" or how does this work?
Never got to the ROM installing, but it would be nice to have something more detailed than "Put it on your phone, install it". Like, do I enter recovery mode and navigate to the rar file and chose to install it? Not sure how this works.
My solution to bootloop
This part took me the longest. For those stuck in a bootloop. Holding DownVolume + Power button for at least 15 sec will simulate disconnection of the battery. This helps you turn you device off. Also, if you nothing happens, make sure you unplug the USB cable as it keeps trying charge and show the status it tries to boot and keeps looping as a result. I could always manage to get into "download mode" through DownVolume + Home Button + Power Button no matter what, and I am grateful for that. I managed to find the exact build I was using on my phone "G925FXXU3COJ1_G925FOJV3COJ1_G925FXXU3COI9_HOME". But everytime I tried to flash, it always failed in the end. I spent hours on google. Someone mentioned something about it failing on a certain point of the writing, involving hidden.img. I googled for info on how to resolve this, and someone suggested to rename hidden.img to hidden.tar but it did not help. I also read some threads regarding using a matching PIT file and there were about 7 different ones to chose from. I tried them all without success. Finally I read something about removing hidden.img from the ROM. I renamed the ROM from .tar.md5 to .tar. Unpacked it, and then repacked it without hidden.img using tar-Tool from these forums. The following flash of the new created tar.md5 (without hidden.img in it) was successful.
Slave for stubborness
Unfortunately since I spent so long getting through this horrible experience, I would feel bad have wasted an entire day just to get a phone that is now reset. I could have done that in 30 seconds. However I am persistent to get this working and I am truly grateful for any help you people can supply my with. I did manage to root and ROM my old S3 but that was a while ago and I only remember a few small things about Odin and so forth. However things seem much more complicated now than before.
Thank you in advance,
Alex
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.