Develop Bugs

[Q] victory_8G_100528.pit vs. s1_odin_20100512.pit

What is the difference between victory_8G_100528.pit (which is in the Odin Stock Flashing section of the WIKI) and s1_odin_20100512.pit (which I've seen other posts recommend for flashing back to stock)? Are they interchangeable or should one be used over the other?

In reality you don't need to use a .pit file to flash back to stock, assuming you are flashing a tarball that includes the modem. The only times you need to use a .pit are a) re-partitioning, b) flashing a modem alone, or c) flashing a kernel.
But to answer your question, _100528.pit was supposed to be the newest leaked .pit from Samsung. You can use either, whichever works.

^what he said.
Victory is the newest. It shifted the partitioning slightly, but I don't remember what got bigger and what got smaller. There's a thread about it here somewhere, but it'll take some searching.

Uh, I think I screwed up. I used Odin to flash the EF02 modem, but I manually set the PIT to victory_8G_100528.pit and now the phone won't even turn on...what can I do now?
EDIT: Of course, after I post that, it DID turn back on...phew.

1.) Kudos to you for searching this and not starting a new thread
2.) The pit they are talking about are ooollllllddddd
3.) I would ask this question in the thread you got the modem or pit file from
Good luck sorry I wasn't of that much help

leatherneck6017 said:
In reality you don't need to use a .pit file to flash back to stock, assuming you are flashing a tarball that includes the modem. The only times you need to use a .pit are a) re-partitioning, b) flashing a modem alone, or c) flashing a kernel.
But to answer your question, _100528.pit was supposed to be the newest leaked .pit from Samsung. You can use either, whichever works.
Click to expand...
Click to collapse
i thought if flashing a modem you do not need the pit file.
i thought the pit was only for if you are repartitioning the file system.
this video from acs team does not say to use pit for the modem update only.
http://www.youtube.com/watch?v=5V6rASKU23Q

What Partitions? Are we talking /Data and /System?

[QUOTE=Original Android
Sent from my SPH-D700 using XDA Premium App
What ever partions the thing redoes when checking repartion.
I always check all three when doing a new rom.

pit.usefullness
I have found repeatedly the case, from dealing with many software locked Epics, that when I get continued failures [whether they are failures at modem.bin or recovery.bin] (which I come across most with people who are not even sure of what chaotic kinds of up/down-grading they have done) the only thing that puts "the life back in the zombie" is:
:Flash pit only. Check> Re-partition ONLY.
The flash will be fast and you will get a
RESET/PASS.
Remove battery. Replace and boot to DL Mode.
Reset Odin and flash tar of choice. You should
get a pass/reset flashing a complete tar.
:::::::: I take no credit it for this, I have had a hard time tracking down where I heard of flashing the pit here on XDA. I just felt that it was high time I posted and I have not seen this CRITICAL "Escape Hatch" life saving technique mentioned anywhere. I wish I could give proper credit where it is so obviously due. This software unbrick method has been the one thing to save at least a dozen or more Epics that were right on the brink. Some of them that had just slowly lost power and died with a full battery during a modem flash, then only powered to a black glowing screen. Plugged in, Odin said Bing-Bongk, and I did the pit only>>>>>RESET. Then flash tar (NOT checking repartition) and Voila.
I am will be posting a link all the goodies needed just as soon as the uploads complete. Hopefully I can return the favor by getting some of the other fine folks here out of a jam.
Thanks to everyone here at XDA that makes the world of Development a more accessible and free-source experience.
And everyone here at .:android monsters:. would also like to give a HUGE round of thanks to IAP {the Independent Android Project} for their overwhelming contribution to Epic Development with the v15/Honeycomb Dreams release of the "Paranoid Android" ROM, and the recent release of the IAP App available for download on their homepage. The Fastest-Slickest/Sickest-Most Overall Stable ROM available for the Epic.
TRY IT, YOU WILL BE GLAD
Anyone with any questions or requests, feel free to pm me.
Tanx........

[Q] Buggy screen on any DK28 rom

any time i try to flash to anything dk28 based, i get the same result. the touch screen (almost) randomly stops responding to input. seems to be related to keyboard opening, but not always. example: from sleep, wake > slide unlock > slide notification bar > tap... "damn it..." can't open the notification unless i sleep it and start over. this is not a hardware problem so far as i can tell as it works fine when flashed to stock. it's less than 2 weeks old and no, i did not spill anything on it. am i alone here?
not new to android, nor am i new to flashing roms, hacking portable devices / electronics in general or using forums. i did search and nothing matched my issue. please don't treat me like a noob just bc my account is new.

As of this morning my phone seems to have developed this kind of behavior, out of the blue. I have no idea what caused it, just that it is exceptionally frustrating.

further info:
...this was all using cwm3 one click with conversion to ext4. just installed cwm 2.5 and flashed the zip version of dk28 (from here) and got the same result again... damn it... back to the beginning again...

Flashed Nebula (seven sisters) and got the same... I mean, if it did this on stock fw I would obviously exchange it... but its only when I flash. So either I'm doing something wrong, there is something wrong with my handset or there's something with cwm or dk28 causing this. Not outside the thought of me doing something wrong, but I've tried so many different things at this point... the only thing I have left I think is flashing dk28 as an update. Is there one around?
Sent from my SPH-D700 using XDA App

my epic was doing the same thing after i flashed midnight but then just a soon as it started it stopped and hasnt happened since. ive tried to recreate to solve it but to no avail if you figure anything out please let me know

Odin back to stock = fine.
flash update.zip for here = intermittently unresponsive again.
seriously... no one else is getting this continuously? i mean it's pretty unusable...

I'm still getting it pretty consistently, I haven't flashed back to DI18 to see if that fixes it. (Odin and I have a bitter history) I suppose if I'm going to take it back I need to flash it back though.

yeah, i did something wrong the first time with Odin but i'm pretty comfortable now. don't know what i did before, but it failed and nearly bricked. as i understand it now:
1. remove sd card (i just go ahead and pop out the battery while i'm at it)
2. boot into download mode (boot while holding "1")
3. select victory PIT and DI18 in PDA
4. uncheck everything but restart
5. connect handset and verify that it is seen
6. go.
have done this about 10 times now and haven't had a problem... until i try to do go to DK28...
I think i'm going to have to wait for official FROYO... it's killing me but i don't want to try to walk into sprint like "hey, my rooted phone doesn't work right...". if it still happens on official 2.2, i will swap.

Mine does the exact same thing. I asked about it yesterday because I couldn't find anyone with a similar issue but the only answer I received was to go back to stock and try it again. I did that and I got the same result.

I ended up just taking the phone into a Sprint repair center, they replaced the screen and didn't even mention the DK28 Bonsai 2.0.1. For free, in less than three hours.

I'm a little confused, are u flashing DK28 with Odin?

It doesn't seem to matter how I flash:
tried flashing just DK28 in Odin
tried flashing modem/pit in Odin and ROM in CWM3
tried the same with CWM2.?
tried update.zip from stock recovery
all get the same result. Behavior seems to actually be time based - like when wake from sleep, it responds for a few seconds and then stops. it doesn't come back until i sleep/wake again, then it's fine.

UPDATE
EB13 is out, installed and still causing an issue. I will be going to the Sprint store later. Still don't know why this didn't happen on DI18, but whatever - happens on official release now so a replacement is justified.

using odin,stuck 1/2 way downloading on phone

ok so I had to try the 2.2 out and the bugs are killing my experience. i am trying to revert back to stock .downloaded the pit and tar and am trying to use odin. my phone is stuck at 1/2 way mark after 20 min so far on downloading screen. since all the links are 404 ed i downloaded odin 1.7. the stock pit and stock tar. it takes 2 hours for me to download the big one. what can i do now?stuck in factory yfs?

Just do a battery pull and resart odin
odin is sensitive but just keep trying should take about 5 mins
and please post in correct section

what is the corect section and retried what you said 3 times. trying the 64 bit computer now, and man are you fast.

Should've been posted in the Q&A section
Here's some more info...
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
i Recommend you do this if you can get into recovery b/c it's flashable (no need to use odin)...
http://forum.xda-developers.com/showthread.php?t=786266

Moved to Q&A, please post in the correct section.

i looked and double checked and found out I was trying to flash dg 27. to get the stock one i guess its going to be 4.5 hours unless anyone knows where else to download it faster if i dont find one

is rapidshare good and how much do they soak you?

yea it'll take awhile to download lol just be patient its a huge file

Well I. Can say its a learning curve. I have finaly odined the stock flash(I think) and ended up with a broken gps so I installed clockwork 2.5 and downloaded the stock rom flashable from cwm. That fixed the gps and I backed it up. Next I tried flashing another 2.2 rom, broke the gps again and tried restoring to the backup but it failed. Reflashed the stock d17 again that got me back working from the 2.1 to 2.2 to 2.1 again but the android market didn't work so I. Reinstalled again and no gps again and soomehow I think thbis is the rom that doesn't alow kme to shut the phone off, just restarts. I want to go back to stock working everything again. Is that possible? What cwm flash rom will get me there again. That 2.2 just screws me every time.

[HOW TO] Unbrick a failed odin back-to-stock E4G (and some stuff about MMS)

Issue: Flashing back to stock on odin fails, with solid color phone screen.. (help the search engines out a little bit here)
I bricked my E4G while trying to odin back to BML stock FC09 gingerbread. I searched the threads for help, and got sparse information like "after failed odin, wouldn't go back to download mode so I left it overnight"
I don't have that kind of time.
Here's how it all began, with maybe more backstory than you wanted, and what I did to fix it. This solution may be no great revelation to the pros around here, but I'm a 45 year old IT manager that just started playing with android phones and admit to being a rank amateur so I'm proud of myself today
H/W version: SPD-700.0.5
Carrier: Boost
A couple months ago I bought an E4G for $40 off of CL. It was a good ESN sprint phone. I Boosted it using the Incognito method since I was already down to the $35/month shrinkage. Flashing it to Boost left me on the vanilla stock FC09 Gingerbread ROM so it was easy to get mms working using the dialer codes and my spl to edit the settings and change the URL from sprint to boost.
Then I got really bored with Gingerbread so I rooted with the deodexed pre-rooted BML version of GB that's floating around here, flashed CWM 5 recovery and stepped up to the April 23rd Carbon JB rom because I thought it looked cool. I was very pleased with it except that after fiddling for a long time, I could never get the MMS to work right. Every time I would enter DATA code in the dialer and then my SPL, I'd get that damned MODEM EXCEPTION error when I tried to edit the MMSC URL. A little more research led me to believe this was an android permissions issue new to ICS and JB. I gave up because I didn't really use MMS that much and everything else was working great.
THen... All of a sudden I needed to use MMS for work, so my interest in fixing it was renewed. I noticed that after I flashed the (mtd) Carbon ROM over my stock FC09, the MMSC URL changed from boost to another carrier (not even Sprint! Something like mobipcs.com, I dont' remember). I'm just smart enough to figure out that the change came over with whatever configuration was in the phone used to build that release of Carbon, but that's really irrelevant; I discovered this same phenomenon (with variations on the carrier) with every ICS or JB rom I've tried on the E4G. Sorry, I'm getting off topic. Only tweak was that I switched from CWM to TW for recovery.
Anyway, not having the time to fiddle with this MMS issue any more right now, I needed to odin back to stock. SO... I found my trusty copies of SPH-D700-FC09-8Gb-REL.tar.md5 and the victory_8G_100528,pit (since I was on an MTD rom, I knew I'd have to repartition)
I wasn't concerned because I feel pretty comfortable with Odin so I make the appropriate selections (leave repartition, uncheck everything else, pick the right files, blah blah), put my phone in download mode and connect. I hit start.
Looks like things are going swimmingly until I look down at my phone, which is blazing a full-screen bright magenta back at me, instead of the download progress bar I expected. No errors in Odin, just hanging there. CRAP! Softbricked.
I disconnect, try to boot the phone, NOTHING. No power. So I pop the battery, push buttons, wait about a minute, try again. Nothing. Lather.Rinse. Repeat, finally it comes back to life in download mode. I retry everything, double checking all odin choices. Looks good, hit start -- Same thing (now it's lime green - a little less traumatic). Just to be to object lesson in insanity, I retry three more times, all the same result where odin hangs on flashing factoryfs,
So I go for broke, what the hell, it's only $40, right? This time, I reset everything, restart odin, and this time I leave out the pit file and just flash the ROM (remember, the reason for the pit was to repartition from mtd for a BML stock rom and I didn't know how far the flash had gotten before it bricked).
It went a lot slower than I'm used to, but...SUCCESS. I'm back on FC09. Flashed CWM 5, boot into recovery, flash the deodexed pre-rooted BML fc09, and I'm back in action. Change the MMSC url and everything's happy again.
Except me.
I wish I could figure out how to get Boost MMS working on a JB rom. I love Carbon and Slimbean, but I gotta have MMS now.
Anyway, hope this helps someone who gets the same error.

Problem with Flashing Almost Everything!

I am posting this as a new topic because I don't have enough posts to post my concern in the thread of the ROM I use.
I have been using PATB ROM for a while now without any issues. Since updating to the newest version I have run into severe issues trying to flash anything besides doing Restores. Every time I try to flash something new it fails immediately and this includes trying to flash a new recovery. I did some reading and thought I had found the answer in restoring the system to stock firmware via Odin. However after trying this a short while ago the process failed as well as soon as Odin showed Recovery in the process bar. This screwed my phone pretty bad, but I was able to Odin a new Recovery on to the phone which seems to have taken it back to functioning normally. I am still unable to flash anything and the only stuff I can do inside Odin is to put different Recovery zips on the device. But even after doing that I am unable to flash anything, and it jumps to Failed right away.
I am not much more then slightly experienced when it comes to rooting and flashing but I have never come across anything like this before. I was using Xposed Framework and I unistalled it because I thought it might be causing the issue. But still no luck. This is driving me crazy. Any help with this would be greatly appreciated because I would like to try out some new ROMs. By the way my flash count reads as only 4 when taken into download mode even though I am pretty sure I have flashed more then that; unless it only trips when completely changing ROMs which would make it a correct count. So I am hoping somebody out there has seen this before and knows how to help me get past this. Thanks to those who are able to help.

Have you tried flashing the full MK4 firmware? IIRC you can't go backwards. Try this out: http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
Use Odin 3.07. If it fails go with 3.09. Please let me know if it works or not. Your partitions may be corrupt but that's a LONG shot. Let's just stick with you're trying to downgrade and the bootloader isn't letting you
Sent from my SPH-L900 using xda app-developers app

After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.

dragonrider6218 said:
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
Click to expand...
Click to collapse
If you decide to go to MK4 be sure to install Philz Cwm Recovery or your problems will start all over again