Develop Bugs

[Q] Failed attempted update to 4.0.4 - stuck (FIXED)

See my reply to this thread on page 2 for the resolution.
---
So I unlocked and rooted my VZW LTE galaxy nexus a couple months ago, no problems with the process.
I looked into updating from 4.0.2 to 4.0.4 and found this walkthrough for YAKJU IMM76D:
androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2/
Page 1 goes through checking USB debugging, what to back up first, etc. USB debugging was enabled already.
Page 2 (link above) provides the instructions on what to download, how to run it, etc. I followed the steps there. It went through:
---
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> bootloader.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> radio.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---
As it stands, if I put the battery in the phone, the screen will turn on and display an icon of a mobile device, two dots, a warning ! triangle, two dots, and a PC monitor.
Pressing the power button "reboots" back to this screen - it just turns off, then turns back on.
Vol up and power does the same thing - does not go into recovery
vol down and power does the same thing
vol up, vol down, and power does the same thing
pulling/replacing the battery does the same thing
I am able to re-run Odin3 v1.85 with the PDA download option checked, specifying that same .tar. It will still go through 95% of the process and end the same way, with "FAIL!" shown in Odin and an almost-complete blue progress bar on the phone below that other error image described above.
So, I *think* this should be salvageable, but I don't know how or what/where to find the file(s) that I should be using to fix this.
THANK YOU for reading and any advice you have, and let me know if anything needs clarification. Screenshot of Odin results attached (seems to not be working... imgbucket link alternative: imgbucket.info/photo/ggnkdlyyu/Odin3_v1_failed.jpg)

Youre phone has nothing to boot from. That's what that means... (Check my signature) use that, reflash stock 4.0.2, try again... And do a backup, first!!
If you're very unlucky, you buggered up the whole memory unit. That means, loss of EVERYTHING...
Oh, and: Stop being a whimp Be a man. Stand above it. Think: "I can do it!!"...
It may sound harsh, at first. But, if you would know, how many times, that has happend, with a Samsung Phone, to me... And if I would have given up, I wouldn't have gotten me a developers phone
So, be strong, (Use my root helper) And tell that phone, who's boss!

Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.

trevordyck said:
Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.
Click to expand...
Click to collapse
I like your way, of thinking
Like a man!

The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app

El Daddy said:
The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
OH, well that explains everything! Thanks for that clarification... now back to trying to un-bork my handiwork.

Time to try to get into Odin mode.
Sent from my Galaxy Nexus

Time to "stay" in Odin mode... playing with Odin (ignorantly, a bit) is what got me here...
axne1 said:
Time to try to get into Odin mode.
Click to expand...
Click to collapse

Well I haven't made any progress on the phone, but I've done a few things to try familyguy's stuff. I think I have the latest version of that, and the 4.0.2 downloaded via the program, but I get this error message every time I try to flash a stock LTE ROM with it. Do I need to do this with Odin, this program, or something else?

I think you should read this
http://forum.xda-developers.com/showthread.php?t=1600203
Sent from my Galaxy Nexus

Aha! Thank you much for that. Following a few links I think I can fix it just by specifying a suitable firmware, because Odin does actually run the "PDA" flash until the end (progress bar still shows up on my "soft bricked" display and Odin indicates it's copying stuff). So, when I land later tonight I'll download and give this a try:
dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I guess I'm not really asking any useful question here so much as tracking my attempts... hope I get this sorted before work in the AM!

Awesome!!!
Keep us updated!
Sent from my Galaxy Nexus

No luck yet. I can still run the GSM "Phone" flash in Odin until 95% complete when it fails, but all of my attempts at using Google's archived 4.0.2 for CDMA are stopping at about 15%, and I have to R&R battery to restart it. This is as far as I can get:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!! (*sits here indefinitely)
Any pointers on what is required for the various fields to flash a stock setup to this thing using Odin?

It sounds like it's looking for some type of backup like a nandroid
Sent from my Galaxy Nexus

There is a tool on amazon.com that should help it's called a jig or something like that.
Sent from my Galaxy Nexus

AHHHH! FIXED!
Things I learned:
- Odin is a Samsung product and needs special samsung-y .tar files to flash the phone. Regular ROM stuff doesn't work. (pardon the ignorance in terminology)
- "mysid" specifies a VzW compatible build for the GNEX
- If you accidentally flash a GSM tar to your VzW phone using Odin, Odin is the only thing that will get you out of your sitch (of the things I could figure out how to try. I didn't try any command line stuff. That's last ditch for me - takes more time for me to learn, and a busy Monday morning at work wasn't helping me)
- I found the resolution here: http://forum.xda-developers.com/showthread.php?t=1426207&page=5 - a factory Odin pair of files for CDMA/VzW, one for PHONE and one for PDA. Saved. My. Bacon.
- The $10 wifi on Alaska Airlines is slow as junk.
- Starting this whilst abroad is a bad idea. (HAHA!)
Regarding the walkthrough I followed that got me in this mess - nowhere that I saw did the author (or readers) specify that the flash I was about to try was GSM only. Maybe I missed that detail, but if not it would make sense to me that someone reading a tutorial on how to flash their phone probably would have NO IDEA that yukjiwhatever is GSM and mysid was for CDMA. That would have been good to read, like, in the first paragraph of the article. Anyways...
I have a working phone and somewhere unicorns are grazing in a field. I hope this helps some other equally poor sap recover his phone.

Flashing stop at data.img D710

Flashing stop at data.img in my galaxy s ii sprint
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> Sbl.bin
<ID:0/013> param.lfs
<ID:0/013> zImage
<ID:0/013> factoryfs.img
<ID:0/013> data.img
than stop
I have try with SPH-D710_FI27 and SPH-D710_FL24 and same problem

apas100 said:
Flashing stop at data.img in my galaxy s ii sprint
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> Sbl.bin
<ID:0/013> param.lfs
<ID:0/013> zImage
<ID:0/013> factoryfs.img
<ID:0/013> data.img
than stop
I have try with SPH-D710_FI27 and SPH-D710_FL24 and same problem
Click to expand...
Click to collapse
Hi apas100,
So it never fails, it just stops?
My first suggestion - Using PC Odin, I would flash the FL24 low ship tar. You can find this in RWilco's Rom Repo. Use the FL24 Original Tar. (Place in PDA slot in Odin)
Let's see if that works for you.

Hi MoHoGalore
Yes , just stops not fails
I will try with this Rom

I did with this rom but same thine
It's stops at data

Did anything happen before that that caused you to flash a one click?
And what happens if you flash a nodata version?

apas100 said:
I did with this rom but same thine
It's stops at data
Click to expand...
Click to collapse
Can you take a screen shot of the progress?
Also, do you know where to get the pit file and how to add that to that Odin flash? If not, I can link and write the steps but it'll be a few hours.

garwynn said:
Did anything happen before that that caused you to flash a one click?
And what happens if you flash a nodata version?
Click to expand...
Click to collapse
I got this phone with this message "Firmware upgrade encoutered and issue. Please select recovery mode in Kies & try again."
When I flash a nodata it will flash but the phone dosen't start , It stops with loge samsong
MoHoGalore said:
Can you take a screen shot of the progress?
Also, do you know where to get the pit file and how to add that to that Odin flash? If not, I can link and write the steps but it'll be a few hours.
Click to expand...
Click to collapse
Yes I know , Copy of screen in attach files
.

android+slp? What are you flashing? I'm seriously drawing a blank on me, Garwynn or anyone else packing something named like that..
Link to that please?

MoHoGalore said:
android+slp? What are you flashing? I'm seriously drawing a blank on me, Garwynn or anyone else packing something named like that..
Link to that please?
Click to expand...
Click to collapse
Looks like he might have yanked odin from another package similar to CF autoroot by chainfire.
☆SoA: Son's of Android™☆
I like to break stuff!

-EViL-KoNCEPTz- said:
Looks like he might have yanked odin from another package similar to CF autoroot by chainfire.
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
The black title bar populates from the title when created. Must be old if it's pertaining to our device. I just don't remember seeing it..

Ignore the title. It's plain Odin 1.85 and not the problem here.
Back to this:
I got this phone with this message "Firmware upgrade encoutered and issue. Please select recovery mode in Kies & try again."
Click to expand...
Click to collapse
Who did you get the phone from? Go ask that person what they flashed before that. Then go tear them a new one for not telling you in advance that they triggered the eMMC bug.
The telltale signs are there that it's this. Odin issues, stuck on data (which the phone locks up and freezes, requires a battery pull, right?) It sounds almost like a dead ringer for the eMMC bug. And if you didn't know it when you got the phone (and especially if you paid for it) you got a bad shake on it.
If you have Sprint, get TEP on it ASAP and get it swapped out. If you can't I can get you going again but you're going to lose part of your internal memory. Let me know which way you want to go.

MoHoGalore said:
The black title bar populates from the title when created. Must be old if it's pertaining to our device. I just don't remember seeing it..
Click to expand...
Click to collapse
I never pay attention to it lmao. I don't use Odin much anymore anyways unless it's an emergency like these last 5x I've borked my IMEI/MEID and had to Odin a modem to fix it >_<
☆SoA: Son's of Android™☆
I like to break stuff!

-EViL-KoNCEPTz- said:
I never pay attention to it lmao. I don't use Odin much anymore anyways unless it's an emergency like these last 5x I've borked my IMEI/MEID and had to Odin a modem to fix it >_<
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
You can also make it say whatever you want by putting a Odin3.ini file in the Odin folder and saying
[Option]
Title= I am the best

I did it with Odin3 v3.04 and same thing
Now when I turn it on I get "Firmware upgrade encoutered and issue Please select recovery mode in Kies & try again"
I got it from ebay so I don't know history of it , I just want to make it working

Let's assume the emmc bug is triggered.
You need to do a few things:
1. Get a MicroSD card if you don't have one already.
2. Put on the MicroSD card:
HG42's Find Brick (Beginning to End) CWM App.zip
HG42's Find Brick (End to Beginning) CWM App.zip
Source: hg42's Partition Scanner Thread
(A big shout out to Hg42 for his efforts here and here on this project!)
3. Download and flash via Odin:
FL24 Kernel with Agat's tRec 0.2.2 (v0.4.0, FL24 based)
4. Reboot to recovery by holding vol. up and power until you see Agat's recovery.
You now have to verify where the emmc bug trigger starts and stops to work around it.
So keep the battery cover off for the next few steps.
5. In recovery run the find_brick_start zip.
Wait until it freezes - if it's the eMMC bug it should.
hg42 said:
If it freezes, the block shown last with "..." at end of line is the first bricked block in that direction.
The line before with "-> ok" is the first usable block before/after the brick.
Click to expand...
Click to collapse
You'll know because you'll see it moving at a pretty steady clip and then just stop dead in its tracks.
If it somehow goes through the entire script and doesn't hang, stop here and let us know.
6. Assuming you were hung up on Step 5, note where it bricked. (the ... block)
Now pull the battery, put it back in, boot to recovery and do the other zip.
Wait until it hangs and note it.
You know know where it bricks. This is important because that part of memory is now unusable.
Step 7
Now go to the OP of this thread and download pits-Epic4GT.zip.
Unzip it, look inside the pits-patched folder.
Inside you're only going to care about the files with DATAFS in the name. Ignore the rest.
Now, look for the pit file that patches between your start (Step 5) and end (Step 6)
It should always start at 00922 and normally ends 2 GB later. (ex. 3070MB)
Your start and stop must be within the range of the pit fix or it will lock up again later.
Hold on to this pit file. You will need it for every Odin flash you do.
Step 8
Using Odin, flash any full restore (rooted/unrooted), include the pit and check "repartition".
This will repartition and format your phone to "work around" the black hole that is the eMMC bug.
This is a lengthy process but should get you in the game.
I caution against flashing custom ROMs though because if anything touches that bad area it will lock up your phone and require a battery pull.
Lastly - if you are on Sprint, still consider taking it to a store, requesting TEP and then asking them to look at and/or replace it. This is just a workaround and the wear leveling could slip back in and start trying to use that block eventually.
Can you PM me the details when you can including the ebay item #? (link okay) If they didn't add this to the description you should file a dispute immediately on it and honestly try to recover some/all of what you paid for the phone IMHO - especially if in the past 30 days.

I have nothing else to add to this thread other than a standing ovation for your help. Well done!
Hope the OP gets this resolved!
Sent from my SPH-D710 using XDA

Photos will talk , to know what is happen exactly
Photos in ATTACH FILES

apas100 said:
Photos will talk , to know what is happen exactly
Photos in ATTACH FILES
Click to expand...
Click to collapse
In first one you didn't add the pit file and check re-partition. What was the result of that one?
If it I rebooted on its own we can immediately rule out the eMMC bug. Good news but still need to fix your partitions.
Sent from my SPH-L900 using Tapatalk 2

garwynn said:
In first one you didn't add the pit file and check re-partition. What was the result of that one?
If it I rebooted on its own we can immediately rule out the eMMC bug. Good news but still need to fix your partitions.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Do u mean I have to check re-partition and add the pit file , Ok I will do that but which file there many files in pits-patched

apas100 said:
Do u mean I have to check re-partition and add the pit file , Ok I will do that but which file there many files in pits-patched
Click to expand...
Click to collapse
Try just the regular pit file.
Sent from my SPH-L900 using Tapatalk 2

[Q] Issues installing 4.2.2 Update with Odin

Hello,
I've just acquired a GT-5120 and am trying to install the 4.2.2 update using Odin.
I downloaded the update zip for my device (1.4GB), unzipped it to see a .tar.md5 file. Opened up Odin, checked PDA, selected the .tar.md5 file. Pressed start and got a failed message.
Here's the log
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I thought there was an issue with my connection / Odin, but I was able to successfully flash a custom recovery and root the device.
Any pointers to get the flashing working?
Thanks!

Somethings to check
1) What is the version of the ODIN you used? I suggest Odin3 3.07.
2) When you try to flash, did the ODIN complete md5 check of the file you added to PDA? (Because it's note in the log you provided or it's different).
3) From where did you download the .tar.md5? "www.Sammobile.com/firmwares" is the best.
4) Did you rename the .tar.md5 file, probably a silly question, but sometimes funny things happen.

AkiOrpheus said:
1) What is the version of the ODIN you used? I suggest Odin3 3.07.
2) When you try to flash, did the ODIN complete md5 check of the file you added to PDA? (Because it's note in the log you provided or it's different).
3) From where did you download the .tar.md5? "www.Sammobile.com/firmwares" is the best.
4) Did you rename the .tar.md5 file, probably a silly question, but sometimes funny things happen.
Click to expand...
Click to collapse
Thanks for the reply, Aki!
I'm using Odin 3.07
The log may have not reflected it since I've tried removing the .md5 extension and flashing with just the tar (same extension as the recovery that successfully flashed). After selecting the file, it takes a few minutes before I'm able to do anything (md5 check?).
I downloaded the file from a thread in this forum with a bunch of mirrors. I'll check out sammobile and report back after testing the file downloaded from there.
I tried leaving the .tar.md5 and renaming it to just .tar (since I successfully flashed a .tar file).
Thanks for the help!
AGH Disregard
I was trying to flash an 5120 ROM on my I467M :crying:

danada said:
Thanks for the reply, Aki!
I'm using Odin 3.07
The log may have not reflected it since I've tried removing the .md5 extension and flashing with just the tar (same extension as the recovery that successfully flashed). After selecting the file, it takes a few minutes before I'm able to do anything (md5 check?).
I downloaded the file from a thread in this forum with a bunch of mirrors. I'll check out sammobile and report back after testing the file downloaded from there.
I tried leaving the .tar.md5 and renaming it to just .tar (since I successfully flashed a .tar file).
Thanks for the help!
AGH Disregard
I was trying to flash an 5120 ROM on my I467M :crying:
Click to expand...
Click to collapse
I think u should be glad that u didn't sucsess
coz I think success will be a bricked phone

[Q] XAC Firmware flash issues

I am trying to get back to the XAC version (Canadian version) of the firmware and had previously tested the CleanRom and the MK1 (these work fine but all miss the English(Canadian) language). I have two P600UEUAMJ4 (which is the right and original firmware it came with) and am not able to run it through ODIN. I am not going to make this the weekend of recovery as it is easy enough to send over the right stock firmware. I did contact Samsung and asked for a technician as I want to know if I can access the system through ADB and see if I can somehow convince the system to accept the firmware.
This is the ODIN output, which really only tells me it is failed....
<OSM> Please wait..
<OSM> P600UEUAMJ4_P600XACAMJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Turning it off and on shows that the firmware failed, Kies has no way to figure out what the heck happened and goes into panic mode and stops at 96% (around the same as where ODIN stops...)

Go into Kies 3, Reinstall USB drivers under the Tools menu. Reboot. Try Odin again.
Sent from my SM-P900 using Tapatalk

dodo99x said:
Go into Kies 3, Reinstall USB drivers under the Tools menu. Reboot. Try Odin again.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
That did not work either -
The device is properly recognized and I have learned an important lesson.
What I should have done is the following: create a backup before rooting the device with ADB - note to self
That way, even when **** hits the fan, I could have extracted what I needed with the ADB tool.
I wonder if the there is a fastboot image kicking around on the internet - googling.
Thanks for the reply.
Al

If you're using a windows 8/8.1 machine, try Odin again on a Win7 pc.
Sent from my SM-P900 using Tapatalk

dodo99x said:
If you're using a windows 8/8.1 machine, try Odin again on a Win7 pc.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I will fire one up, you think it might have to do with drivers? Luckily I have a W7 kicking around.
Will let you know when...
Sent from my SM-N900W8 using XDA Premium 4 mobile app

dodo99x said:
Go into Kies 3, Reinstall USB drivers under the Tools menu. Reboot. Try Odin again.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
aelaan said:
I will fire one up, you think it might have to do with drivers? Luckily I have a W7 kicking around.
Will let you know when...
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope that did not do the trick, I even freshly installed a laptop with W7 - pretty much stuck with the MK1 firmware - it keeps failing at the same point over and over again.
Oh and yes I downloaded the firmware from three different spots and also Kies or Kies3 have no clue how to handle it.
Going for a walk - need to clear my head.
:cyclops:

aelaan said:
Nope that did not do the trick, I even freshly installed a laptop with W7 - pretty much stuck with the MK1 firmware - it keeps failing at the same point over and over again.
Oh and yes I downloaded the firmware from three different spots and also Kies or Kies3 have no clue how to handle it.
Going for a walk - need to clear my head.
:cyclops:
Click to expand...
Click to collapse
Try the latest firmware P600ZHUANC3 and odin 3.09 (latest)
I did mirrors a while ago here:
http://forum.xda-developers.com/showpost.php?p=51308363&postcount=23

Anything but the XAC flashes, I am back on stock mk1, still baffled.
Sent from my SM-P600 using XDA Premium 4 mobile app

Bell SGH-I747M - There is no PIT Partition

I was running PAC-ROM and updating regularly to the latest version. Last version was April 16th.
The phone was working fine but all of a sudden for no reason it rebooted and was stuck at the PAC Loading screen.
I realized something weird was going on so I went into TWRP to reflash but it wasn't able to mount any of the partitions... NOT GOOD @#$# so all writes failed.
So then I decided to ODIN back the 4.3 stock rom (from sammobile).
If wrote for about 15 minutes and then FAILED.
Odin V3.07 now gets stuck at initialization.
Odin V1.85 shows more useful information (color of ID:COM box is yellow when) :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYCEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Device shows the following :
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER RP SREV: 1
Can anyone provide me with a Bell S3 16G PIT file ??
I was able to find the AT&T version but couldn't find anywhere if this will work on my phone.. I did read that it didn't work on a TELUS phone so I'm reluctant to try it.
Any help would be appreciated or is there is anywhere in the Toronto area I could bring the phone to be fixed, that would also help !
Thanks in advance.

After deciding to try the ATT PIT file I got the following in ODIN (see image):
Sadly,
The device won't even turn on now... Looks like a hard brick.... sigh..

Any sounds when you connect the phone to your computer? Any lights with or without the battery installed?

audit13 said:
Any sounds when you connect the phone to your computer? Any lights with or without the battery installed?
Click to expand...
Click to collapse
The red light comes on the phone when I connect it to the PC without a battery.
The computers recognizes "QHUSB_DLOAD" but fails with "no driver found".

I think you need to go through the de-brick procedure. If that doesn't work, you may have to have it JTAG'd.

audit13 said:
I think you need to go through the de-brick procedure. If that doesn't work, you may have to have it JTAG'd.
Click to expand...
Click to collapse
Thanks,
I'm trying this debrick method now :
http://forum.xda-developers.com/showthread.php?t=2549068
debrick img didn't seem to write to the SD card the 1st time so I'm still working on it.

the.teejster said:
Thanks,
I'm trying this debrick method now :
http://forum.xda-developers.com/showthread.php?t=2549068
debrick img didn't seem to write to the SD card the 1st time so I'm still working on it.
Click to expand...
Click to collapse
I got the Debrick image to work so my phone now boots into download mode again via the ext SD card. Unfortunately I still can't write the stock image as it still complains of a missing PIT file.
I tried the att file but it show Auth failed on the phone so I'm at a loss... Sigh..
Any ideas on how to get a flashable PIT file for Bell?

The out file is in the tar file I still think it may have been corrupted, the first thing I would do is download a new file from SamMobile or samsung-updates
Sent from my thl T11 using Tapatalk
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
SORRY PIT file not out file
Sent from my thl T11 using Tapatalk
---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------
I would also easy nand before flashing and if it flashes then it will usually bootloop and I have to go into recovery and format data and cache, but that is what has worked for me in the past
Sent from my thl T11 using Tapatalk
---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------
Erase nand
Sent from my thl T11 using Tapatalk

Not quite sure I understand all your feedback but I'll try to respond.
- Corrupted tar file : The file I have is good as I have used it before. I downloaded again to err on the side of caution and MD5 was the same for both so I know the file is fine.
- Easy Nand : I assume you mean "Nand Erase All".
From what I read this is only useful if the partitions are stuck in read only mode :
Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results.
In my case, when I started out, TWRP couldn't even mount ANY partition which tells me the PIT is corrupt or missing.I think I'm back to requesting a BELL SGH-I747M PIT file... sigh...
Thanks for taking the time to reply and for any additional insight you can offer.
I'm starting to think that my internal memory is simply toast but will continue to try.
jimchee said:
The out file is in the tar file I still think it may have been corrupted, the first thing I would do is download a new file from SamMobile or samsung-updates
Sent from my thl T11 using Tapatalk
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
SORRY PIT file not out file
Sent from my thl T11 using Tapatalk
---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------
I would also easy nand before flashing and if it flashes then it will usually bootloop and I have to go into recovery and format data and cache, but that is what has worked for me in the past
Sent from my thl T11 using Tapatalk
---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------
Erase nand
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse

Folks,
Apparently the PIT file can be generated on a rooted device by running the following command in the terminal emulator :
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
This should generate a file named "out.pit" in the /sdcard folder.
Can anyone with a Bell 16G S3 run this command and upload the out.pit file here please ?

This is NOT GOING TO BE AN EASY FIND ..
I just got a valid PIT file dumped from a working Bell S3 16Gb phone using EFS professional and unfortunately still get the authentication error message.
Here is a screenshot of my phone when trying to flash..
I think the only possible way to move forward with an S3 PIT file is to "find" an official Samsung file that has the correct signature embedded.

the.teejster said:
This is NOT GOING TO BE AN EASY FIND ..
I just got a valid PIT file dumped from a working Bell S3 16Gb phone using EFS professional and unfortunately still get the authentication error message.
Here is a screenshot of my phone when trying to flash..
I think the only possible way to move forward with an S3 PIT file is to "find" an official Samsung file that has the correct signature embedded.
Click to expand...
Click to collapse
Try this to extract PIT file of your device and post it. I will check if there is a problem.
http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html

patate331 said:
Try this to extract PIT file of your device and post it. I will check if there is a problem.
http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html
Click to expand...
Click to collapse
An extracted pit file is NOT signed and therefore cannot be flashed.

the.teejster said:
An extracted pit file is NOT signed and therefore cannot be flashed.
Click to expand...
Click to collapse
Okay... I wanted to check the file generated by your phone...
Try this one.
Replace extention by .pit

the.teejster said:
The red light comes on the phone when I connect it to the PC without a battery.
The computers recognizes "QHUSB_DLOAD" but fails with "no driver found".
Click to expand...
Click to collapse
I've had that same error before on a Galaxy S 2 or t959, I forget which. Windows would constantly fail using odin. What i did to fix it was install ubuntu using Wubi on windows and then I used Heimdall to flash back to stock. Worked a miracle on my phone and everything was fine and dandy!
Hope that helps and let me know if that works!

patate331 said:
Okay... I wanted to check the file generated by your phone...
Try this one.
Replace extention by .pit
Click to expand...
Click to collapse
If you don't mind me asking.... Where did this one came from.? Is it signed?
Thanks.

the.teejster said:
If you don't mind me asking.... Where did this one came from.? Is it signed?
Thanks.
Click to expand...
Click to collapse
Come from here: http://www.phonandroid.com/forum/pr...ossible-sur-sgh-i747m-canada-t58048.html#null
It should be signed. Let me know, I cannot test it.

It failed the authorization check so it looks like it's not signed.
Thanks for trying.
patate331 said:
Come from here: http://www.phonandroid.com/forum/pr...ossible-sur-sgh-i747m-canada-t58048.html#null
It should be signed. Let me know, I cannot test it.
Click to expand...
Click to collapse

Well,
I received confirmation from 2 different repair shops that, based on the information I supplied and what my phone is displaying, that the internal memory is dead.... Memory hardware failure and not related to rooting or using custom roms.
Time to give up and move on.
Thanks for trying to help out !

the.teejster said:
This is NOT GOING TO BE AN EASY FIND ..
I just got a valid PIT file dumped from a working Bell S3 16Gb phone using EFS professional and unfortunately still get the authentication error message.
Here is a screenshot of my phone when trying to flash..
I think the only possible way to move forward with an S3 PIT file is to "find" an official Samsung file that has the correct signature embedded.
Click to expand...
Click to collapse
same problem cant find pit and iv searched 1000s sites pages getting tired looking
wish could just make my own custom but dont no enough yet