Database Info

Bricked..

My friend asked me to root his phone. When I asked him what phone he had, he told me it was a samsung vibrate.. however I found out that it is actually a sgs4g.. I flashed it with vibrant and now I have a vibrate boot loop / soft brick. I have searched around the forums and tried several jars and tars using heimdall and odin, however they all just fail. I have been trying for several hours now and am not getting any luck, especially since multiupload is dead. Does anyone know of a way to fix this? I am able to get into download mode (I have seen both variations (I.E. Digging droid and the orange triangle)). I believe it was on gingerbread.
Any help would be greatly appreciated.
Thank you.

Use the Heimdall One-Click guide in the second link of my signature. Go ahead and flash with bootloaders to be safe. And yes - that is download mode you see.
Afterwards - you can look at the guide in the first link of my signature for links to stable GB custom ROM's to flash.

I got the error "local and device PIT files don't match and repartition wasn't specified"
I remember trying this method once. However I got the same error after pushing 'ok' and flashing for a second time.
Edit -I flashed with bootloaders anyways (didnt do that step the first time). Thank you so much.

http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V

i bricked my phone installing the wrong rom and used one click unbrick. worked great!

Captivate stuck in bootloop. Help me get it back on track?

Hey everybody. I have a Samsung Captivate with CM7 installed. The other day it started bootlooping and I couldn't get it into recovery mode at all, so I ordered a Jig.
Now the Jig's here and I'm still not sure what I'm doing. I can't get into recovery with the button combos, so I'm kinda stuck. Any suggestions?

I would suggest that you use the jig to get into download mode, then do one of two things:
1. Flash a kernel that works with CM7 from Odin or Heimdall
2. Flash a stock rom from Odin or Heimdall, then reinstall CM7
You may want to try option 1 first, then option 2. If a bad kernel flash caused the issue in the first place, you might be able to save your installed programs & setup instead of having to wipe everything with a stock rom.

I've been trying unsuccessfully for the past couple of hours to flash back to stock. Odin keeps getting hung up on "Get PIT for mapping..." or the sbl.bin step. Maybe I'm doing something wrong or I have the wrong rom.
Anybody have a step-by-step? I'll owe you many thanks.
Otherwise I'll just have to go buy myself a Galaxy Note. Oh no.

See this Captivate Connection Issues and Download Mode Help
by jmtheiss
And u may need the Nexus drivers since u r on cm7 ??
ninja

Two things to try first:
1. Use a Heimdall-based one-click. There's one in my signature (if you were on Gingerbread bootloaders), or you can look in the Stock Rom collection in the Development section. Heimdall uses different drivers and interacts differently with the device.
2. Try a non one-click Odin setup. You'll need to get full Odin and then see if you can find a package to flash from inside of it. Do a little searching in the Development section and you should be able to find these items. Some newer Captivates don't respond well to the one-clicks.
If those don't work, look at the "Connection Issues" thread in my signature for more ideas (4-2ndtwin beat me to it. )

[Q] Trying to Root Infuse, odd problem.

Alright, this is just odd.
Generally, I want to get rid of the bloatware and make it so my phone doesn't run so much crap in the background, so I have turned to rooting it. However, this is more of a pain than anything.
I followed the Odin guide in order to get CWM, bloat removal, root, stock kernel, stock rom, etc, and its odd whats going on.
When I connect my phone to my computer, outside of download mode, and have it in USB debug, then it detects my phone in odin just fine. However, when I put it in download mode, it decides my phone is in a different dimension. Why is this?
When I unbricked it, I had to use heimdall. Odin detected it then, but couldn't fix, which turns out because I was using a crappy cord. I'm using the new cord now, and still getting problems with it detecting it in Odin.
Other info: I have the drivers installed from Kies Mini, I am currently trying to root with superoneclick, I have already cleared data via recovery mode, and oppan gangnam style.
Anyone able to help me understand why odin doesn't wanna detect my phone?

Spectre370 said:
Alright, this is just odd.
Generally, I want to get rid of the bloatware and make it so my phone doesn't run so much crap in the background, so I have turned to rooting it. However, this is more of a pain than anything.
I followed the Odin guide in order to get CWM, bloat removal, root, stock kernel, stock rom, etc, and its odd whats going on.
When I connect my phone to my computer, outside of download mode, and have it in USB debug, then it detects my phone in odin just fine. However, when I put it in download mode, it decides my phone is in a different dimension. Why is this?
When I unbricked it, I had to use heimdall. Odin detected it then, but couldn't fix, which turns out because I was using a crappy cord. I'm using the new cord now, and still getting problems with it detecting it in Odin.
Other info: I have the drivers installed from Kies Mini, I am currently trying to root with superoneclick, I have already cleared data via recovery mode, and oppan gangnam style.
Anyone able to help me understand why odin doesn't wanna detect my phone?
Click to expand...
Click to collapse
bleh windows and odin problems. it might be a usb controller problem. or a driver problem... the usb chord should always be plugged directly into the back of the computer into the ports on the motherboard preferably. no hubs or anything. also the heimdall driver might be messing with the samsung download mode driver. there is actually different drivers for download mode and normal connections from samsung. it looks to the computer like different devices. for odin to work you need to connect in download mode and wait for windows to install the drivers or download the drivers from the samsung support website and install them manually. this might require removing all existing samsung drivers and the heimdall driver and starting over.
i have to ask though, if you unbricked the phone with heimdall why not use heimdall to flash the cwm kernel? all you have to do is extract the zImage from the .tar and flash it to the kernel partition.
also fyi super one click can not work on official gingerbread. the att official gingerbread is apparently very secure. or the real hackers never paid it any mind because it is so easy to work around that limitation with odin or heimdall.

Well, I can try digging through and see if the heimdall driver might still be there, idk if it is or not. Also, when I plug it in in download mode, it installs a driver, but when I look through device manager, it says the device isn't there.
Also, I read somewhere you couldn't root the phone with heimdall using the same method I was trying to get ahold of, so thats why I didnt use heimdall. But in that case, any chance you could link me to a guide on how to do that? The main thing I want is to get rid of this bloatware and crap.

Spectre370 said:
Well, I can try digging through and see if the heimdall driver might still be there, idk if it is or not. Also, when I plug it in in download mode, it installs a driver, but when I look through device manager, it says the device isn't there.
Also, I read somewhere you couldn't root the phone with heimdall using the same method I was trying to get ahold of, so thats why I didnt use heimdall. But in that case, any chance you could link me to a guide on how to do that? The main thing I want is to get rid of this bloatware and crap.
Click to expand...
Click to collapse
what link were you following? so i can see what you are working with..
the only ways to root is to flash a pre-rooted /system image(but i haven't seen one, i've been too lazy to make one myself) or flash a cwm kernel and use it to flash an su and superuser package. some of the older kernels had a rooting script but it sometimes borks su if you update it and will downgrade su when you reboot so the devs took the rooting feature out of the kernels. both the /system image and the kernel method need heimdall or odin. anything that odin does heimdall does but heimdall uses different packages or no "package" at all.
heimdall can be done in command line and it's easier to explain that way than the ui. are you comfortable with command line?

THis is the link to the guide i was using. http://forum.xda-developers.com/showthread.php?t=1613523
And I'm not too great with command lines. I have next to no experience with linux os, and though I've tried to learn some, it just doesn't seem to stick.
Hell, most of what you said doesn't entirely make sense to me.

New info. Computer detects it in download mode, but odin doesnt. Grr to this stuff.

I think I found the main problem.
When I unbricked my phone, I upgraded to GB. Now I'm at GB, and according to what I read, thats where all the problems are stemming from. Is there a way to root when you are on GB? Or do I need to downgrade to Froyo, root, then go back to GB?
If I have to do the latter, then I'll just skip GB and figure out the CM9 stuff.

you should still be able to use heimdall, and i think it can work with the samsung drivers, the open source driver heimdall uses may help in some situations but i dont think it's needed. odin can be weird. i never use it.
you have 2 options asuming heimdall works(i think it will). you can use option a from that thread but flash it through heimdall, or you can go to the thread for entropy's kernel and download the zImage and flash that through heimdall.
for heimdall download this and extract it to a folder somewhere. https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
you may also need this but it may already be on your system http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en
download the rom .tar file (or kernel zImage if you want cwm) that you choose and extract the contents to the folder that contains the heimdall files.
if you are using the rooted rom, stock kernel no cwm package it is in .rar and there is a .tar or .tar.md5 inside of that. remember to extract the .tar and not just the .rar.
now if you are already on the att release if gingerbread uclb3 you will only need the factoryfs.rfs remeber that it should be in the same folder as the heimdall.exe file
put the phone in download mode and connect the usb cable then open a command prompt and navigate to the folder with heimdall and the factoryfs.rfs (c:\users\<login name>\<whatever folder you made or chose>\ ) and type
Code:
heimdall flash --factoryfs factoryfs.rfs
if you chose to use a kernel with cwm instead then you will use the zImage file. download the kernel you want and extract the zImage file into the heimdall folder or what ever you called it. go into a command prompt and type
Code:
heimdall flash --kernel zImage
after you have cwm you can download this http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip for root, move it to the sdcard and reboot to recovery and flash it in cwm
if you are not comfortable with command line you can use the frontend but it requires the pit file which you need to get from the unbrick packages.

[Q] Black screen after Heimdall One-click with bootloader, Download mode works

First, I tried searching for hours, and I haven't been able to find this same issue anywhere on the forums yet. If I missed it, sorry, and thanks.
I downloaded the stock 2.3.6 firmware from the Hiemdall One-touch thread here, and ran it on my phone (SGH-T959V Galaxy S 4G, and I made sure the firmware was for that specific model and not the Vibrant). It ran through the first time just fine, and then I went to do the bootloader (which I gather I probably shouldn't have done and didn't need to do maybe). Heimdall One-Click started running, then gave me this message and restarted the phone to a black screen:
Code:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Now, I can pull the battery and get the phone into Download Mode just fine, and I've tried running the same firmware as well as several others (AntonX-Basic_with_a_twist, Stock KJ6 + root-One-Click, hampsterblade-Basic_MIUI_Kernel_r2_OC_UV, at least), but while they all do the first restore fine, none will load the bootloader and I get the same results every time. The phone is obviously not 100% bricked since I can get into Download Mode, but all I get is a black screen, no lights under the buttons and nothing on screen, not even the rainbow pattern or the Samsung logo. It's as if the phone isn't doing anything at all, and it doesn't change if I just pull the battery and leave it (tried for 15-20 minutes a little while ago). The only thing I can do is put it back into Download Mode, but none of the firmwares I've found have worked to restore the bootloader.
I am using a Mac with 10.8 and Java 1.7, and if it's necessary I can get access to Windows, but that will take me some time and effort, so if there's any way to resolve it using just the Mac that'd be best.
jW

When you flash the Heimdall package, does the phone boot fine?

It should have work with Mac, can you double check things?
If possible can you try re-downloading the .jar package.
And in the terminal run the .jar package (sorry I don't know OS X commands).

Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW

jondesu said:
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
Click to expand...
Click to collapse
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.

th3controller said:
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
Click to expand...
Click to collapse
Thanks, I've got a Linux distro downloading and I'm looking into whether I could get a copy of Windows or borrow a PC easily.
jW

You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.

FBis251 said:
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
Click to expand...
Click to collapse
Thanks, I'll give that a try (still trying to get Linux installed here to try that as well). The first one I tried, and the one I think I'd prefer to use is the T959VUVKJ6 Stock UVKJ6 from the Heimdall One-Click thread in the forums here. I tried some of the others when that one failed. It downloaded fine, and I tried downloading it again with no change in the results.
I should clarify, btw, that I have been trying flashing it without the bootloader, but when I do that, it still sits on the black screen. The very first time I did it and one other time later, I did get the rainbow screen (and the first time, but never again, it did boot up to the stock OS and home screen), but now if I flash with or without the bootloader, I get nothing, probably because the bootloader got screwed up by the first bad flash.
My first step today will be using another cable (there's one handy, I just didn't think about it), and then I'll move on to trying Linux/Windows.
jW

S8 bootloop, ODIN fails at write, finally asking for help

So the past couple days I've been learning what I can about rooting. Finally decided to give it a shot and well I can't seem to get ODIN to work correctly. It seems to always end with abl.elf and then failing at write. I've tried Comsy and a few versions of ODIN including the latest version.
I'm currently downloading the latest firmware for my phone which is what I was updated to.
I have the Galaxy s8+ SM-G955U originally through VZW. I remember the ending of my firmware was CRE9 so I found this version off of Samsclub: G955USQU4CRE9_G955UOYN4CRE9. I downloaded some stock files for my device because I wanted to reset my bootloader version so I could root and use PARTCYBORG's rom. That's when it seemed to start looping.
I have access to download and recovery if you need that information. I also have downloaded the latest samsung drivers for Odin. I'm pretty sure if I could get it to write I could fix this issue but I've gone through a hundred threads on this forum and I'm pretty much a bit overwhelmed now. Please help
EDIT: I think I've nearly gotten it, but I'm stuck now. Odin 3.12 and Comsy 3.12 seemed to get me close. I've ran into missing Home Binary and Fail! Model Mismatch. Trying a 3.13 version of ODIN and then calling it.

One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.

JeffDC said:
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
Click to expand...
Click to collapse
hi I installed the image twrp 3.2.2.0 but by mistake on boot. how can I restore the boot? thank you