Database Info

How I recovered my i896 to (Rogers) stock

Here was my situation, and how I got out of it:
I was running the Perception build 7 ROM. It was great, no issues except that I needed to get some kernel modules for it, and was unable to get the info I needed to re-create the kernel build environment. I decided to return to stock. There were lots of threads, all going in different directions with inconsistent advice. The wiki I was looking at has what appeared to be a ClockworkMod (CWM) backup.
I had already tried to restore my own CWM backup, but (after disabling lagfix) would restore, but then seemed to loop trying to start the lock screen. Same thing with the version on the wiki. I didn't want to restore to the ATT version and I didn't have windows to run Odin...
So this should work from Windows, Linux and Mac.
get param.lfs from http://forum.xda-developers.com/showpost.php?p=9663090&postcount=58
get FIRMWARE from http://forum.xda-developers.com/showpost.php?p=9109370&postcount=697
Get Odin.rar from http://forum.xda-developers.com/showpost.php?p=8802897&postcount=1
Get Heimdall from http://www.glassechidna.com.au/products/heimdall/
Install Heimdall and any drivers it requires.
Extract the .pit file from Odin.rar. I have heard other people say don't use the pit file…I did…
Unzip the firmware
start Heimdall
FactoryFS
- factory.rfs
Kernel
- zImage
Param.lfs
- param.lfs - though I didn't use this
Primary Bootloader
- I left this blank
Secondary Bootloader
- I left this blank
Cache
- cache.rfs
Modem
- modem.bin
FactoryFS
- factory.rfs
Click Start
Phone will do it's thing. I did receive an error at the very end but all went well. I'd welcome some additional info on the Primary/Secondary Bootloader.

Curious if this restored the bootloader from at&t back to the rogers one?

Excellent! Another successful restore of Rogers stock with Heimdall. Thank you for the write up, gin032.

@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps

I had the same troubles is well.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App

I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse

gin032 said:
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
Click to expand...
Click to collapse
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App

This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
sshvetsov said:
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse

soooo why is the "start" button grayed out???

soooo why is the "start" button grayed out???

Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App

SteveCheeseman said:
soooo why is the "start" button grayed out???
Click to expand...
Click to collapse
10ee said:
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
Click to expand...
Click to collapse
sshvetsov said:
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.

Benjamin Dobell said:
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Click to expand...
Click to collapse
In my case, I did re-partition....but in the interest of fullness, where can one find such a secondary bootloader?

Bricked my rogers i896 while trying to mash up different kernels for a rom, odin didnt work so i tried heimdall with the procedures thanks to OP.
The only difference was I did not use the pit file. Everything worked flawlessly and I still managed to maintain my data on root sd although i lost root access. The ATT splash screen also was removed (thank goodness) and model number changed back to i896 in the "About". It is now back to pretty much stock, though I did lose the APN settings (can easily reenter it). Last step now is just to re-root and restore via Titanium Backup.
Thanks for the helpful information everyone!

Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.

loonieryan said:
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
Click to expand...
Click to collapse
This please!

I've tried this, but use zadig.exe my phone shows up as Gadget Serial. So I installed anyways, it says successful, but nothing happens in the frontend that shows the phone and it doesn't allow me to start anything.

ootz0rz said:
Curious if this restored the bootloader from at&t back to the rogers one?
Click to expand...
Click to collapse
+1 this is important!

Tried doing this and my phone is now a brick. It's stuck at the following image:
Phone...Yellow exclamation...PC
Edit: Just got download mode back but still not working for me
Edit: Got Odin3 to work finally. Flashing JL1. Hoping it works.

ok, I have a real challenge.
I made the derp of giving my phone temp root using Z4root, then I ran OneClickLagFix on the phone. The phone rebooted & now just goes to a black screen after the rogers logo. it is on but does not respond to anything (capacitive butons light up when pressed).
I tried the steps listed here to revert to factory but it didn't help. Any ideas?

[Q] 4g reboots in download mode unless connected to power.

I bought a second hand galaxy s 4g that had a problem. When the phone gets rebooted, such as a battery change, it only restarts in download mode. I tried flashing a new rom in odin hoping it would set right whatever is wrong in there but no good. When the phone is connected to a power source it restarts normally. I know there is a fix for this but I can't find it. Seems most people can't get into download mode but I can't get out! Thanks in advance for whoever can help. How can I fix this?

robthorn2010 said:
I bought a second hand galaxy s 4g that had a problem. When the phone gets rebooted, such as a battery change, it only restarts in download mode. I tried flashing a new rom in odin hoping it would set right whatever is wrong in there but no good. When the phone is connected to a power source it restarts normally. I know there is a fix for this but I can't find it. Seems most people can't get into download mode but I can't get out! Thanks in advance for whoever can help. How can I fix this?
Click to expand...
Click to collapse
Interesting problem. What ROM is it currently running? Have you tried a factory reset, cache wipe, etc?

I did. I just got it yesterday and immediately did a cache wipe and reinstall packages. It has froyo.vuvkb5 kernel 2.6.32.9. I installed the krylon360 stock+rom via odin with no change. I was going to try flashing a team whiskey rom onto it when I have time but wanted to check if this had been a problem for anyone else. I found one post somewhere that may point to a missing .dll but everything is fine when its plugged into power. I am lost.

robthorn2010 said:
I did. I just got it yesterday and immediately did a cache wipe and reinstall packages. It has froyo.vuvkb5 kernel 2.6.32.9. I installed the krylon360 stock+rom via odin with no change. I was going to try flashing a team whiskey rom onto it when I have time but wanted to check if this had been a problem for anyone else. I found one post somewhere that may point to a missing .dll but everything is fine when its plugged into power. I am lost.
Click to expand...
Click to collapse
The phone runs on Android which does not utilize .dlls (dynamic link libraries; that's a Windows thing). KB5 is an old ROM. If you're trying to stay on Froyo right now, why not flash KD1 (http://forum.xda-developers.com/showthread.php?t=1063696), then do a factory data reset. See if that helps. If you plan on going to Gingerbread then we need to insure you flash a ROM with the correct boot loaders else you could get into the "rainbow screen", soft brick, bootloop, or something of the sort.

I am definitely going to upgrade the phone. I found another thread that had a problem that I also have but didn't mention the download mode problem. When I try to reinstall package I get the same message as this thread
http://forum.xda-developers.com/showthread.php?t=800614
It ends with this message
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
I'm guessing the original owner of the phone boned something up and gave up on fixing it. I'm just getting back into android after a year trying to like the windows phone which is now my nemesis. I don't remember many of the lessons I learned from my Vibrant so any help getting this guy here on point would be much appreciated.

robthorn2010 said:
I am definitely going to upgrade the phone. I found another thread that had a problem that I also have but didn't mention the download mode problem. When I try to reinstall package I get the same message as this thread
http://forum.xda-developers.com/showthread.php?t=800614
It ends with this message
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
I'm guessing the original owner of the phone boned something up and gave up on fixing it. I'm just getting back into android after a year trying to like the windows phone which is now my nemesis. I don't remember many of the lessons I learned from my Vibrant so any help getting this guy here on point would be much appreciated.
Click to expand...
Click to collapse
Yeah, I don't recall that mount point on my phone. I think /sdcard is mounted to /mnt/sdcard. Did you try flashing the KD1 ROM I listed above? You'd have to do it from ODIN.
If you want to get on the latest, RaverX3X did a great favor to many and created an ODIN version of the latest release from Samsung (KJ6). It's found here: http://forum.xda-developers.com/showthread.php?t=1353176

I just finished downloading the above file and will flash as soon as i get home. Thanks for all the help. I'm most def going to use the raver file.

robthorn2010 said:
I just finished downloading the above file and will flash as soon as i get home. Thanks for all the help. I'm most def going to use the raver file.
Click to expand...
Click to collapse
Good luck. Let me know how it goes.

No change. I tried both roms and same result except for gingerbread being much faster. I am not rooted right now so I suppose I will try rooting and looking around my folders for anomolies? Could this be a hardware problem?

robthorn2010 said:
No change. I tried both roms and same result except for gingerbread being much faster. I am not rooted right now so I suppose I will try rooting and looking around my folders for anomolies? Could this be a hardware problem?
Click to expand...
Click to collapse
Hard to say, though it seems odd that it reboots fine when plugged in. Aside from rooting & poking around maybe try installing chadster's KG4 ROM (http://forum.xda-developers.com/showthread.php?t=1183413). Instead of just the PDA file, it has the partition information file (.pit), the PDA, CSC, & phone files. I wonder if flashing that might help? If you try it, just:
Put CODE_T959VUVKG4_CL1385158_REV00_user_low_noship.ta r.md5 in PDA
Put Hawk_Sidekick_VibrantPlus_831.pit in PIT
Put SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 in CSC
Put T959VUVKG4-Phone-CL1037720.tar.md5 in PHONE
Let ODIN decide what needs to be checked & flash.
That backs you off of the latest version of GB, but if it works, you can reflash the KJ6 version afterward.

That sounds like a step in the right direction. I get the feeling something was missing in the phone file wise and needed a full redo to the most deep level. I have to wait til I get home to try. I am very anxious.

robthorn2010 said:
That sounds like a step in the right direction. I get the feeling something was missing in the phone file wise and needed a full redo to the most deep level. I have to wait til I get home to try. I am very anxious.
Click to expand...
Click to collapse
I totally understand. I hope this works!

Nothing. Same result. Also now the gps has stopped working.

robthorn2010 said:
Nothing. Same result. Also now the gps has stopped working.
Click to expand...
Click to collapse
Dang, we made it worse. Sorry about that. I'd definitely push KJ6 back onto it and factory data reset.
I'm wondering whether it would be worth a shot to flash one of drhonk's kernels (http://forum.xda-developers.com/showthread.php?t=1194032) on it with CWM/Root/and voodoo. That way you can go into CWM recovery, wipe the cache, davlik cache, and fix the permissions.
IF you want to try it and see what happens before, download drhonk's KG4 kernel, put it in the PDA section of ODIN, and flash it. If you flash KJ6 first, you can ODIN his KJ1 ROM.
After doing it, boot the phone into recovery mode (you might have to use an app like quick boot), go to advanced, and fix permissions.

Op, you seem to be getting a lot of great help from Stephen, but did you get this working? if not follow the gb guide to flash both sets of bootloaders. wipe you're sd card. Now go back and return to froyo kd1 and use the official upgrade through kies. If that doesn't fix it, you have a hardware problem. After the upgrade to kj6 official, take it to a store and say it started happening once you upgraded
Sent from my T959 using xda premium

My GT7Plus bricked itself again... Help! *** Edit: Fixed!!! See page 6 for details!!

So, this happened recently, and I fixed it. Link: http://forum.xda-developers.com/showthread.php?t=1735119
Well, outta no where, same basic issue, but with a twist.
This afternoon while I was asleep my GTab rebooted. It came back to the "Samsung Galaxy Tab 7.0 Plus" splash screen and is stuck. I *can* get into download mode, and I can almost get into recovery. When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
Twist:
So, knowing what I did last time, I installed Odin and the Samsung drivers on my POS computer at home, booted into Download Mode, and did the "PDA" option with the correct FW (same as I used last time for the T869 from SamMobile, I saved all the files). It runs through just fine, gets to the end and the Tab reboots. It then goes into recovery and and does a few things (I believe it said it was deleting the cache and a few other processes). Then, lastly, it again says:
"# Manual Mode #
-- Updating Application
... followed by a reboot, and back to hanging on the boot logo.
Any ideas?!? Ironically, I put it on CL today to see if I can sell it for enough to cover a Nexus7. I woke up to an offer, and a bricked Tab. Figures.
Any thoughts/help are greatly appreciated. The sooner the better. lol

Is it possible that I need to flash a good recovery in Odin? If so, what's the procedure. and can someone link me to the one I would need for the US TMobile 4G version of the GT7+?

Also, since flashing the stock FW isn't fixing anything, and it seems like a possible Recovery issue, a friend at work is suggesting I choose the option in Odin to delete the partitions.
Thoughts??? (quickly)

Damn dude, again?
I think there is 3 or 4 threads about this on this forum and same amount on 7.7 forum. None come to a cause our solution, seems like people repeats some procedures and out of nothing it works again.
When it happened to me a let its battery drain fully to the point it won't turn on anymore let it this way for some time. Then fully charged, this is a little harmful to your bat, for the record. Then try to turn on, it will take some time but eventually it could enter on the system.
I think the data partition got corrupted.
Sent from my GT-P6210 using Tapatalk 2

Yup.
So, I tried the option in Odin to re0make the partition, and every time I try it fails with an error of "Can't Open Package" (or something along those lines).
I have reinstalled the FW through Odin no less than 10 times, nogo. The first time I open recovery after flashing, It says it is installing a package, clearing cache, etc, and the last line always says "-- Updating Application". After 10-15 seconds, that goes away and it reboots only to hang on the GT7Plus splash screen again. Then, any time I go into recovery after that first post-Odin instance, if says:
"# Manual Mode #
-- Updating Application
Should I be trying to reinstall Recovery? If so, what do I use (link)? Also, how do I do that in Odin...

I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2

leodfs said:
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Where was that tip? Link?
Also, any one have that .pit file I can try with?

http://forum.xda-developers.com/showthread.php?p=28574760
Sent from my MB525 using Tapatalk 2

Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app

statuzz said:
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which file it is that I'm using, I'll have to look at home in a couple of hours. This happened to me a few weeks ago (link in original post), and I flashed this FW with Odin and it recovered, and has been fine since (till now), so I know it's at least a usable FW. I'll try to find the other one today.
I just tried finding the stock pit file for the TMo SGH-T869, but I can't find it. Anyone have a link to it by chance? Also, once I get it, what do I do (options to choose) in Odin to flash it?... and do I do it at the same time as the FW?
Thanks for any help! I was really hoping to sell it in the next day or two to fund the Nexus7, so now I'm really frustrated.
ETA: Also, I let it completely die, to the point it wouldn't boot. Then charged it for a bit and booted. Same issue.

I think that if u find the pit file they should be flash at the same time...fw in pda and pit in phone...(this need to be check to confirm) after flashing.. reboot into factory recovery wipe everything and try to boot
Hopefully u fix that today
Sent from my Galaxy Nexus

When it happened to me, i flashed the pit first and at the same with stock with re partition checked, didnt help. I did everything that I could find and I feel like it only worked again by itself
You can look every single thread of this exact problem, the ones that got it back working can't really say how, they flash everything many times and it suddenly works.
The good things are that flash the stock ones don't increase you flash count, and as long as you can enter download mode you are not really s#%
Sent from my MB525 using Tapatalk 2

Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:

VisualOddity said:
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
Click to expand...
Click to collapse
The problem is that there's is not development for t869 so there's not much to look for...just factory images and root method
Sent from my Galaxy Nexus

Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?

VisualOddity said:
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
Click to expand...
Click to collapse
i think u should forget about the pit file, couz the firmware have the pit repackage with the tar, im gussing u will only need the pit file in case u want to change the phone partitions, try to get those 2 fw and try them :good:

That's why I'd like the pit file, so I can check the option in Odin to re-partition.
So, I have internet at home now. I have now tried again letting it completely die, then completely charge, same issue. I have also tried 2 different versions of the SGH-T869 firmware.
Any thoughts?
Also, given what I have done so far, I posted this yesterday, any thoughts?
"Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad? "

Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.

chrisrotolo said:
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
Click to expand...
Click to collapse
Thank You. A few questions:
Would that stock recovery.img have to be model specific. i.e. for the SGH-T869, or could it be from any GT 7 Plus (or is it generic on all devices with HoneyComb)? I *think* from experience it has to be T869 specific, but it's worth asking.
Also, about Heimdall, where do I get that, and how do I use it to flash? I've heard of it, but never used it.
Lastly, about the CSC files. That makes sense seeing as what it's doing, so that *could* be the whole issue. How can I overcome that? Can I download and flash those files somehow? Do you have a link to them?
Thanks for the help everyone. I'm hoping that in doing all this, maybe whatever ends up fixing this will be a guide for everyone else having the issue...

OK, I saw a couple of you guys mention the 7.7 people having this issue, so I went there to research. If I am reading right, it *sounds* like this could be a solid mix of a data system being corrupted, and the stock recovery (Samsung e3?) being bad.
Someone mentioned that you can pull the stock recovery.img from a the firmware, make a .tar with only that, then flash that. Once that's done you can do a full wipe in recovery, flash the full FW, and hopefully be back in business.
I want to try this, and if it works, maybe we will have a proven solution for the people getting this issue. However, not only have I never created a .tar, I have especially never created a flashable .tar, so...
What do I do? Other than pulling the recovery.img from the FW, how do I do this?

How to make volume button not activate screen

So I have a question......My husband loves his phone except for one thing, when the volumn rocker is pressed it activates the screen. So after doing some research it seems the only way to change this is to root it. True or not???? Here is the information from his about phone screen:
samsung sgh-i727
android version 4.0.3
baseband version 1727ucld2
kernal version 3.0.8
bild iml74k.ucld2
If there is a way to deactivate this without rooting that is preferable but I have been unable to find any answers to that.
Where do I start and what do I need if so? Thank you.

ARGETIM said:
So I have a question......My husband loves his phone except for one thing, when the volumn rocker is pressed it activates the screen. So after doing some research it seems the only way to change this is to root it. True or not???? Here is the information from his about phone screen:
samsung sgh-i727
android version 4.0.3
baseband version 1727ucld2
kernal version 3.0.8
bild iml74k.ucld2
If there is a way to deactivate this without rooting that is preferable but I have been unable to find any answers to that.
Where do I start and what do I need if so? Thank you.
Click to expand...
Click to collapse
Your on a leaked incomplete firmware go to official ICS
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I am totally new at this....how and what do i need to do?
We are also AT&T so Im not sure if this matters or not.

ARGETIM said:
I am totally new at this....how and what do i need to do?
We are also AT&T so Im not sure if this matters or not.
Click to expand...
Click to collapse
If, in fact you are on a leaked version of the firmware, you need to go into your apps drawer and see if the Kies app is installed. If it is, you can try to use it to update to the official release of the ICS firmware.
But before you do the above, just for giggles, look in your apps drawer and see if Superuser and Rom Manager are installed. If they are there then chances are the device is already rooted. If it is, let me know and we will work forward from there. If it is rooted you can install a kernel that does not have volume rocker wake feature to solve your problem.
Sent via Tapatalk 2

Ok. So there is no rom manager or sies installed.......
hitekredneck said:
If, in fact you are on a leaked version of the firmware, you need to go into your apps drawer and see if the Kies app is installed. If it is, you can try to use it to update to the official release of the ICS firmware.
But before you do the above, just for giggles, look in your apps drawer and see if Superuser and Rom Manager are installed. If they are there then chances are the device is already rooted. If it is, let me know and we will work forward from there. If it is rooted you can install a kernel that does not have volume rocker wake feature to solve your problem.
Sent via Tapatalk 2
Click to expand...
Click to collapse

hitekredneck said:
Looks like someone has messed around with that phone and only half baked a firmware install. Give me a few minutes and I will round up some links with information on what you need to do to get back to official AT&T Icecream Sandwich firmware.
Sent via Tapatalk 2
Click to expand...
Click to collapse
OK, here are a couple of links. One is to a tutorial here on XDA that will walk you through using Odin to flash stock ICS firmware from AT&T.
But first, here is the link to download the firmware (ROM) that you will need -> http://www.hotfile.com/dl/162779401/27c699c/I727UCLF6_I727ATTLF6_ATT.zip.html. Just choose "Regular Download" from the page that shows up. I know this is a very large download and will take quite some time to download from Hotfile servers.
And here is the link to download Odin, the program that you will use to flash the stock firmware to the phone. -> http://forum.xda-developers.com/attachment.php?attachmentid=925569&d=1330549534
Download both of these packages to your computer, not your phone. And be sure you have an archive extracting program such as 7zip installed on your computer. It is free software and you can download the 32bit or 64bit version, whichever you need, from the following link. -> http://www.7-zip.org/.
Next, here is the link to the tutorial for flashing this firmware with Odin -> http://forum.xda-developers.com/showthread.php?t=1652398
Scroll down until you find section #1 that is titled "1. HOW TO RESTORE STOCK FIRMWARES".
Follow the instructions to the letter, other than the file downloads, as those I have previously provided above in this post. I am assuming that you have already downloaded these prior to implementing the following tutorial. Once you have gone through this procedure and you have a fully functional Skyrocket, please hit the thanks button for Vincom as he is the one that took the time to work up this tutorial for anyone that may need it.
Happy flashing ..... HTR
The following is only copy/pasted from the tutorial link above. Please use the instructions from that thread only. I only posted an example below so you would know where to start in that thread.
DO NOT! CHECK "REPARTITION" IN ODIN! YOU HAVE BEEN WARNED!!
1. Download Odin 1.85
2. Download the stock TAR for your device - see section below.
3. Extract(with 7-ZIP) the contents of odin-185.zip to a folder.
4. Extract(with 7-ZIP) the contents of the stock firmware file to a folder, do not change the name of the extracted MD5 file.
5. Run Odin 1.85.exe from the folder you extracted it to.
6. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS.
7. Only Click "PDA" and select the firmware file you extracted, it will have a md5 extension.
8. How To Put your device into Download Mode: (download mode is NOT the same as recovery mode)
a. Connect the USB cable to your PC, but NOT your device.
b. Remove the battery.
c. Reinsert the battery.
d. Press and keep down both Volume Up and Volume Down keys then insert the USB cable into your device. (On Rogers phones It's just Vol Down.) DO NOT RELEASE THE VOLUME BUTTONS UNTIL INSTRUCTED
e. When You see the screen warning you about installing a rom w/a yellow triangle RELEASE the volume key(s)
f. Now press and release the volume "up" key, you should now be at the Download Mode screen w/odin recognising your phone. -See Pics Below-.
9. Click Start in Odin, it will flash the firmware, give it approx. 10mins. When its done flashing it will autoreboot the phone. Thats it, you're done.

THank you. I will try this tonight when I get home and let you know how it goes.....

Well finally got around to trying this.....phone is recognized by computer but Odin does not see it? Now what?

Leave odin for now, it seems you have at&t phone, so you should try this method: http://forum.xda-developers.com/showthread.php?t=1749021
should be easier.

[Q] Phone Bricked Please Help

Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.

Read the second link in my signature and see if it helps you with Heimdal.

lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?

JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.

Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.

bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?

bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.

JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...

bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.

JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.

When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....

bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.

JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:

Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.

bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol

JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.

JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.

hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?

champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.

JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).