Database Develop

[Q] Odin

I was just wondering I just recently bricked my last Captivate luckily At&t replaced it for free but im not sure how many more times thats going to work. My idea was that the brick occured from a suspicious looking 2.3 odin file but im not sure if that bricked it. Should I try flashing with the same computer but with a diferent 2.3 odin? I got a new one heres the link.
http://forum.xda-developers.com/showthread.php?t=1129821
Edit: forgot original package that bricked my phone.
http://forum.xda-developers.com/showthread.php?t=1232703

voldomart13 said:
I was just wondering I just recently bricked my last Captivate luckily At&t replaced it for free but im not sure how many more times thats going to work. My idea was that the brick occured from a suspicious looking 2.3 odin file but im not sure if that bricked it. Should I try flashing with the same computer but with a diferent 2.3 odin? I got a new one heres the link.
http://forum.xda-developers.com/showthread.php?t=1129821
Edit: forgot original package that bricked my phone.
http://forum.xda-developers.com/showthread.php?t=1232703
Click to expand...
Click to collapse
A hard brick occurs when you flash incompatible bootloaders. Make sure you flash the gingerbread bootloaders first (either the i9000 bootloaders or 2.3 captivate bootloaders) with odin then flash your gingerbread rom. There are odin packages that include just the bootloaders. Hope that helps.
Sent from my SGH-I897 using xda premium

Yeah it kinda helps im gonna wait though and buy a usb jig just so im ready if anything does manage to go wrong. Thanks though i didnt know that.

See with the package i used that bricked my phone it got stuck in a certain stage and wouldnt go anywhere so i tryed unpluging it and try to go back to 2.1 but after that attempted 2.3 flash it wouldnt accept any odins.

A hard brick not only happens with incompatible bootloaders, but with an incomplete bootloader flash, which is what happened, you say it stopped at a certain point, that is more than likely where it bricked. That package isn't "suspicious", if it were there would be a lot of reports about it.
The first link you posted is bootloaders only. It will not flash 2.3 firmware at all. Just the boots.
To make sure odin doesn't stall out, use a port on the back of the pc, right click odin and run as admin.

What studacris said. Keep in mind there is always a small risk on flashing that Odin fails. So once you flash Gingerbread bootloaders just don't flash any bootloaders again unless you really need to. OR Look in to the Unbrickable mod if you want that.

Just askin how long would ikt take to flash just the gb bootloaders?

Less than a second. Its a very small risk to begging with BUT a risk none the less.

ANother question is there any danger in downgrading bootloaders?

Same as upgrading. No reason to Downgrade except maybe AOSP specific kernels or warranty.

I had to right now because of a bootloop and a failed custom rom install and none of my backups worked and i couldnt install anything else. It said on clockworkmod that it couldnt read my cache folders. Did i have to go back to 2.1? Because thats what i did. Also thank you guys for answering my questions the captivate is so much more complex that the droid when it comes to custom roms and stuff like that.

voldomart13 said:
I had to right now because of a bootloop and a failed custom rom install and none of my backups worked and i couldnt install anything else. It said on clockworkmod that it couldnt read my cache folders. Did i have to go back to 2.1? Because thats what i did. Also thank you guys for answering my questions the captivate is so much more complex that the droid when it comes to custom roms and stuff like that.
Click to expand...
Click to collapse
No there are Odin packages that Do not include bootloaders, just saying. Same as there is GB packages without bootloaders as well (this goes for KF1 and KH3 to my knowledge). Once you flash GB bootloaders there is no reason to reflash bootloaders except for AOSP specific kernels and Warranty.

[Q]help !bricked my captivate

I was trying to root my stock froyo. But somehow I was getting bootloop. Then I tried installing some stock rom through odin. But my bad day, it failed and now I have [phone...+..!...+..computer]. I couldn't go into normal yellow triangular download mode. Searched thru net and found out that this IS a download mode and I need to flash some good ROM/Bootloader/Kernel and I will be fine.
However, I have tried a lot of different odin flashable ROM?bootloaders, etc nothing works.
I saw a lot of ppl refering to this link.
http://forum.xda-developers.com/showthread.php?t=731989
However I have some question here, first it says open and then click start.. what will that do, we generally put some file in PDA or PHONE section and then we click start. I dont see any such file link there.
can someone help, please. Atleast take me to stock somehow. Now I dont want to root.

Use Heimdall One-Click. download it here. http://files.teamkomin.com/files.php?dir=Captivate/ get the KB2-Rooted version to save yourself some time.

Thank you. without that rooted rom, I was planning not to try rooting again. Thanks, it saved my captivate and rooted too

[Q] T599N PRoblems

I have been having an issue of getting my phone to do anything from hemidall frontend or odin various verisons of. I installed a rom and accidentally hit re partition when i did but didnt have any problems for a week or two tunred it on one day and it just went to download mode. I have tried flashing various pit files and roms and recovery. I literally have tried various samsung drivers roms other phone roms fixes and they all fail. or lag out while trying to flash. I am all but at my wits end with said phone. anyone have any ideas. IF you say JTag if first post i shall just take it out back and shoot it... Any help would be appreciated
The repartition was checked after i did tysons pre-rooted for 599n

joshjonte said:
I have been having an issue of getting my phone to do anything from hemidall frontend or odin various verisons of. I installed a rom and accidentally hit re partition when i did but didnt have any problems for a week or two tunred it on one day and it just went to download mode. I have tried flashing various pit files and roms and recovery. I literally have tried various samsung drivers roms other phone roms fixes and they all fail. or lag out while trying to flash. I am all but at my wits end with said phone. anyone have any ideas. IF you say JTag if first post i shall just take it out back and shoot it... Any help would be appreciated
The repartition was checked after i did tysons pre-rooted for 599n
Click to expand...
Click to collapse
T599 has borrowed a lil space from the galaxy s3 mini general forum, thats where tysons thread is also located. You will have better luck posting this in t599 general thread

Trouble Rooting my Metro PCS Galaxy Exhibit T599N..
I need root for the galaxy exhibit 4G Metro Pcs.. I think it's a app on the phone that's blocking the root.. Called (Perizinan Rumah Tangga) this app is on my phone it's not letting root the phone.. I think once I remove it I'll work.. I'm on jelly bean 4.1.2 .. It's not letting root on Kingo a Root either.. Help anyone.. Thanks

go here
http://forum.xda-developers.com/galaxy-s3-mini/general
look for t599 in the thread title

(Q) I527 stuck in Download

(RESOLVED)
Alright so in order to not bore you all, ill get to the point. I messed up trying to do impossible things with my I537 because I didn't read any forums before trying... stupid I know. That being said I now have a "soft bricked" phone stuck in download mode. I have been looking around (I assume not hard enough) for the right file to flash with ODIN to get me back up and running so I can actually do my research this time before playing with different stock roms.
Can anyone point me in the right direction to get the right files to unbrick this thing?

First things first: this forum is for the SGH-I537 AT&T Galaxy S4 Active, not the I527 Galaxy Mega. I just want to make sure you have the right device. If you have the Mega (I527), you want this forum, and ignore the rest of this post.
If you do in fact have the Galaxy S4 Active (I537), then check out this thread, it has all the official firmware files that have been released for this device. I would recommend using the firmware files for NE3 (KitKat) to flash in Odin. The NE3 build is the easiest to root, and you can always use the keep-root method to upgrade to lollipop if you so desire.

Oh yes sorry that was a mistype. I did indeed mean to type I537. Ok Ill give this a shot and update on how it goes.

Ok so Im currently downloading the Full Odin package, but I have already rooted the phone with towelroot. Is that going to be an issue?

Nah it won't be a problem. Flashing firmware files with Odin will unroot your phone (it resets everything to original factory settings). You can always reroot with towel root again

Ok new problem though, I was able to get everything flashed through ODIN, it restarts; then I get the Samsung boot screen, att boot screen and then it just goes black. I put it back into download mode and tried to re-flash it a couple times but it keeps doing the same thing. Thoughts? This Is the section I got the file from;
I537UCUCNE3 (4.4.2) Released 2014-06-06 - OFFICIAL

Issue has been solved, I just had a battery issue but after changing that and letting the phone charge up it started up great. Thanks for all your help "thisisapoorusernamechoice"

Cant Downgrade to 4.1.1 from 4.4.4. on i9305

i9305 Imei shows null/null after flashing I9305XXUFNL1_DBTFNL1 which was a stock rom
Also no signal as you would guess
Now I cant even downgrade to any roms apart from 4.4.4.
Phoen is rooted and tried 4.1.1. I9305XXALI5_I9305EVRALI5_I9305BVALI5 through Odin and Mobile ODIN
On Mobile odin phone looks like its working then stays on the SAMSUNG Logo for ages and nothing, just stays there
I have a Back up of an efs which I done through Rom Manager but not sure if its corrupted or how to restore it
If someone coud give me a walkthrough :highfive:

EwOkie said:
i9305 Imei shows null/null after flashing I9305XXUFNL1_DBTFNL1 which was a stock rom
Also no signal as you would guess
Now I cant even downgrade to any roms apart from 4.4.4.
Phoen is rooted and tried 4.1.1. I9305XXALI5_I9305EVRALI5_I9305BVALI5 through Odin and Mobile ODIN
On Mobile odin phone looks like its working then stays on the SAMSUNG Logo for ages and nothing, just stays there
I have a Back up of an efs which I done through Rom Manager but not sure if its corrupted or how to restore it
If someone coud give me a walkthrough :highfive:
Click to expand...
Click to collapse
Hi,
About IMEI null/null with 4.4.4 firmware, you should search in this Q/A forum, there a lot of threads asking for this issue. Maybe you should get an answer yourself
However, you should try again to do a clean flash of latest official 4.4.4 firmware with ODIN v3.09 by following this GUIDE HERE from @MaHo_66.
AFAIK, it's impossible to downgrade from 4.4.4 because of KNOX bootloader. It has been said many times in this Q/A forum. Maybe it exists somewhere a tricky trick to do it but I'm not aware of this.

FLooDW said:
Hi,
About IMEI null/null with 4.4.4 firmware, you should search in this Q/A forum, there a lot of threads asking for this issue. Maybe you should get an answer yourself
However, you should try again to do a clean flash of latest official 4.4.4 firmware with ODIN v3.09 by following this GUIDE HERE from @MaHo_66.
AFAIK, it's impossible to downgrade from 4.4.4 because of KNOX bootloader. It has been said many times in this Q/A forum. Maybe it exists somewhere a tricky trick to do it but I'm not aware of this.
Click to expand...
Click to collapse
In Addition to @FLooDW 's answer:
Try to use Philz 6.48.4 or 6.59.0 as your recovery rather then TWRP or the old CWM (6.0.4.7), especially DON'T use the latest TWRP from their official website, its a broken build and its known to mess up the partitions! That could be your problem if you have done that before...
Any recovery you want to use, download from my RECOVERY/GUIDE thread that FLooDW linked to you, use those they work fine.
PS. before flashing official firmware with ODIN, make sure you have a custom recovery installed, then boot into recovery, wipe system/data/cache/dalvik-cache/internalSD/boot/modem etc. this is to ensure when you have flashed the firmware, there is nothing left from the previous firmware that was installed.
Note: when explaining your issue, try to do that by providing as much as possible info about your actions before and after the problem occured, that way anyone who wants to help can help you the best way possible.

MaHo_66 said:
In Addition to @FLooDW 's answer:
Try to use Philz 6.48.4 or 6.59.0 as your recovery rather then TWRP or the old CWM (6.0.4.7), especially DON'T use the latest TWRP from their official website, its a broken build and its known to mess up the partitions! That could be your problem if you have done that before...
Any recovery you want to use, download from my RECOVERY/GUIDE thread that FLooDW linked to you, use those they work fine.
PS. before flashing official firmware with ODIN, make sure you have a custom recovery installed, then boot into recovery, wipe system/data/cache/dalvik-cache/internalSD/boot/modem etc. this is to ensure when you have flashed the firmware, there is nothing left from the previous firmware that was installed.
Note: when explaining your issue, try to do that by providing as much as possible info about your actions before and after the problem occured, that way anyone who wants to help can help you the best way possible.
Click to expand...
Click to collapse
Really helpful addition !

Trying what you guys have mentioned just now, let you know as soon as :good:
What 4.4.4. om do you suggest?
Also the efs I backed up (not sure if its working or not as it was with Rom Manager)
How do I restore, can it be done with root explorer?
Tried the [ROM][i9305][18.10.15]>>>4.4.4<<<[KK][STOCK][TW][STABLE][+AROMA] S5 Elite Lite v4.0
which I posted a few days ago, left a post with no reply and thats when I started getting the null/null

PSN_AGNi_pureSTOCK-v5.9.5-4.4.x_I9305_AROMA
Currently trying this rom.. watching the installation set up and says so far that set_perm: some changes failed
used philz_touch_6.59.0-i9305
Rebooting and stays on Samsung Galaxy boot screen ??

EwOkie said:
PSN_AGNi_pureSTOCK-v5.9.5-4.4.x_I9305_AROMA
Currently trying this rom.. watching the installation set up and says so far that set_perm: some changes failed
used philz_touch_6.59.0-i9305
Rebooting and stays on Samsung Galaxy boot screen ??
Click to expand...
Click to collapse
AGNi is not a ROM, this is a kernel. Did you flash AGNi kernel over official Samsung firmware ?
As MaHo_66 said, you have to explain more what you have done and what you need if you want us to help you.

Steps :
reflashed a Stock Rom then Rooted it then added Philz Recovery
Then Tried this rom : I9305XXUFNL1_O2UFOB1_4.4.4_KK.zip
Currently trying various modems to see what this gives me
Failing this will need to try QPTS or EFS Professional again.
* I know how to flash and root roms if you look at my signature along with kernels I am basically telling you what I have tried to get
this null/null away as I think its a baseband/modem issue somewhere as I have read various posts and some people agree.
Cant even do the *#197328640# or *#*#197328640#*#* to get into certain modes
Thinking it maybe the sim card slot now .......... I am losing my mind now!

EwOkie said:
Steps :
reflashed a Stock Rom then Rooted it then added Philz Recovery
Then Tried this rom : I9305XXUFNL1_O2UFOB1_4.4.4_KK.zip
Currently trying various modems to see what this gives me
Failing this will need to try QPTS or EFS Professional again.
* I know how to flash and root roms if you look at my signature along with kernels I am basically telling you what I have tried to get
this null/null away as I think its a baseband/modem issue somewhere as I have read various posts and some people agree.
Cant even do the *#197328640# or *#*#197328640#*#* to get into certain modes
Thinking it maybe the sim card slot now .......... I am losing my mind now!
Click to expand...
Click to collapse
There are few other possible solutions you could try:
- try this, it shows you how to get in service mode and the restoring of the golden efs backup, that should be present if its good.
If above doesnt work, then try the one below.
- have you tried to flash the param_bin file? if not try that with ODIN, it might work.. file attached.
Let us know how it goes.

H yes tied that file and didnt work
will the imei work from another phone or efs?
isnt that link just gps?