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] Unroot Problems

Good morning all.
I am trying to get back to stock as I have to return my device. Here is what I did so far:
I ran odin with pit.charge and PDA - EE4stock_DXC.tar
I unchecked autoreboot and F.Reset Time.
Ran. According to Odin everything was successful. I have done this multiple times with battery in and out and I continue to get this when booting and it goes to stock Android System Recovery <3e>:
--bootmode=7 from cmdline...
--Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!..
# Manual Mode #
I have factory reset and wiped cache successfully.
My root was Peanut Butter Jelly time Kernel and Gummy rom.
Any help would be GREATLY appreciated.

Just found: http://forum.xda-developers.com/showthread.php?t=1111486
Not sure how I missed it previously. Will update on status.

check re-partition, reboot, and f rest time
Add pit file to pit and check pit box
add ee4 file to pda and check pda box.
then just click start, let it run and you will be good to go.

Undzis said:
check re-partition, reboot, and f rest time
Add pit file to pit and check pit box
add ee4 file to pda and check pda box.
then just click start, let it run and you will be good to go.
Click to expand...
Click to collapse
uncheck auto reboot, you're supposed to odin flash with the battery in... technically you don't need to but I wouldn't take the chance of it failing halfway through and creating a paperweight
blazing through on my 4G Droid Charge

anoninja118 said:
uncheck auto reboot, you're supposed to odin flash with the battery in... technically you don't need to but I wouldn't take the chance of it failing halfway through and creating a paperweight
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
Truth. Although the only time I've heard of someone bricking is when something happens during boot.bin being flashed.
steven8515 said:
Just found: http://forum.xda-developers.com/showthread.php?t=1111486
Not sure how I missed it previously. Will update on status.
Click to expand...
Click to collapse
Use this EE4 file HERE and the pit file from the HOW TO FIX YOUR PHONE thread.

Vibrant 4g bricked????

Okay i have a question about the T959v. Here are the facts: Phone was flashed with ODIN but the repartition box was checked. It was my fault because i didn't double check before flashing. Now the phone is in a recovery bootloop when i try to turn it on. I can reach DOWNLOAD MODE but then again if i try to flash it again same thing will happen. Is there something i can do or is the phone bricked because of that???? Thanks in advance!

What's the rom you are flashing?
Sent from my SGH-T959V using xda premium

Stock kd1 but i have some other roms like gingerbread...

Im using the .831 pit file also, but i have tried without the pit file and nothing. Also tried without repartition checked but it will do the same thing. Problem is that first time i flashed i had repartition checked

enelyam said:
Im using the .831 pit file also, but i have tried without the pit file and nothing. Also tried without repartition checked but it will do the same thing. Problem is that first time i flashed i had repartition checked
Click to expand...
Click to collapse
And your sure the rom is for the sgs4g and not the vibrant, right? Because the two are majorly different...
Sent from my SGH-T959V using XDA App

Yes i am, like i said the mistake i made was leaving the repartition option checked. For some reason the phone has a boot loop and when i hit reboot now on recovery it says failed to mount /data invalid argument. Never had something like this happened before and i have flash a ton on galaxys

enelyam said:
Im using the .831 pit file also, but i have tried without the pit file and nothing. Also tried without repartition checked but it will do the same thing. Problem is that first time i flashed i had repartition checked
Click to expand...
Click to collapse
I think Odin will auto re partition when you flash the pit. You can un check it and it should be fine either way.
enelyam said:
Yes i am, like i said the mistake i made was leaving the repartition option checked. For some reason the phone has a boot loop and when i hit reboot now on recovery it says failed to mount /data invalid argument. Never had something like this happened before and i have flash a ton on galaxys
Click to expand...
Click to collapse
I may be wrong but...
I think you need the csc. If your just flashing the pit and pda your missing the other partitions. I think when you repartitioned it wiped the partitions and you are missing one or more.

enelyam said:
Yes i am, like i said the mistake i made was leaving the repartition option checked. For some reason the phone has a boot loop and when i hit reboot now on recovery it says failed to mount /data invalid argument. Never had something like this happened before and i have flash a ton on galaxys
Click to expand...
Click to collapse
I had the same problem that you are experiencing. The fix for me was to get a full Factory load that was verified to be for the GalaxyS4G. Which is the model number that you listed. The Odin that I loaded is T595VUVKF1. This requires that you load each file in the proper Odin category. Use the Pit file, PDA, Phone and CSC files. Leave the repartition box checked and you should get your stock image back, from there you can install CWM and flash another image.

Allright thanks a lot! I knew something like that was happening but i have not been able to find a firmware with those files divided i mean the csc,pda, and phone files separated. Everything i found has been the package that you just file in pda... If anybody know where to find that i appreciate the link.

enelyam said:
Allright thanks a lot! I knew something like that was happening but i have not been able to find a firmware with those files divided i mean the csc,pda, and phone files separated. Everything i found has been the package that you just file in pda... If anybody know where to find that i appreciate the link.
Click to expand...
Click to collapse
I think this package should help you out...
http://forum.xda-developers.com/showthread.php?t=1183413&highlight=odin+kg4
If not, I have one that has all 3 necessary files that (just not the pit which you already have anyways) I can upload and share that will get you going again...

enelyam said:
Allright thanks a lot! I knew something like that was happening but i have not been able to find a firmware with those files divided i mean the csc,pda, and phone files separated. Everything i found has been the package that you just file in pda... If anybody know where to find that i appreciate the link.
Click to expand...
Click to collapse
Just get a heimdall one click. It has everything you need in one tiny easy to use package.

It's ok guys! And thanks for the inputs. I found what i was looking for and flashed the phone. It working like a charm! with KF1 thanks a lot

enelyam said:
It's ok guys! And thanks for the inputs. I found what i was looking for and flashed the phone. It working like a charm! with KF1 thanks a lot
Click to expand...
Click to collapse
Sweet, glad you got it working but i recommend you do it again with kj6 official GB. kf1 was the first GB leak we got. It has a borked boot loader file so good luck with recovery and download mode

Bassmanjames said:
Sweet, glad you got it working but i recommend you do it again with kj6 official GB. kf1 was the first GB leak we got. It has a borked boot loader file so good luck with recovery and download mode
Click to expand...
Click to collapse
Congrats man...
+1 on the KJ6...

How to unroot

I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?

There is nothing that can set the custom binary to 0.
jc1337 said:
I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
Click to expand...
Click to collapse

appdroid said:
There is nothing that can set the custom binary to 0.
Click to expand...
Click to collapse
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?

jc1337 said:
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
Click to expand...
Click to collapse
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....

Pirateghost said:
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Click to expand...
Click to collapse
\
do you have any idea why it might not be working then? I'm using the .tar from that post about unroot i727 and it's not working. What I'm doing is
1. running odin as admin
2. selecting pda (the SGH-I727-UCKJ2-k0nane.tar)
3. while phone is off pressing both volume buttons and then plugging in usb (putting it into download mode)
4. making sure odin sees my phone
5. clicking start
and this is what it does and it won't go any further
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
I've let it sit there for about 30 minutes without it moving any further?

do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?

Pirateghost said:
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Click to expand...
Click to collapse
I'm needing to return the phone to AT&T. Yes, I do comprehend what root is. And yes, I had a custom ROM on it before this.

sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try

Pirateghost said:
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Click to expand...
Click to collapse
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!

jc1337 said:
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
Click to expand...
Click to collapse
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.

Pirateghost said:
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Click to expand...
Click to collapse
I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?

jc1337 said:
So, should I just try to find the stock rom online?
Click to expand...
Click to collapse
that k0nane.tar IS the stock rom.....

Pirateghost said:
that k0nane.tar IS the stock rom.....
Click to expand...
Click to collapse
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?

jc1337 said:
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
Click to expand...
Click to collapse
with that exact file.
it will however, probably trip the download counter

Pirateghost said:
with that exact file.
it will however, probably trip the download counter
Click to expand...
Click to collapse
It is, I've gone from YES(4 counts) to YES(15 counts) I honestly have no idea what I'm doing wrong and why it won't go past NAND Write. I've been working on this for the past three hours though and they close in an hour an 15 minutes so I guess I may not make it tonight...

at this point I would be okay with just getting this phone working again.... I have to be up in a few hours and need to get to sleep

If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed

You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium

r3dp0is0n2012 said:
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
Click to expand...
Click to collapse
I am under 30 days, but I don't think that'll work if I can't get past the screen that says "Firmware upgrade encountered an issue. Please selecdt recovery mode in Kies & try again." and says I have a custom binary download of 16

hcyplr29 said:
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah I did. I'm trying to flash the .tar not the whole zip

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?