Develop Bugs

[q] odin v3+1.61

I really can't get this program to work. I followed the wiki to the T. Neither of the 3 options work. The only thing i notice that is different is the 3 option
If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery
4. The process will hang while writing "factoryfs.rfs"
5. Reboot the phone and reset Odin
^^ I never get factoryfs.rfs just the same old param.lfs error
I came from EB13 & did one click root clockwork 3.0.0.5/6. After i tried to boot into recovery it coverted everything into EXT4 when the phone did not work after that i tried to use Odin to flash back to EB13. I was able to apply syndicateROM through clockwork but it still does not turn on. When i try to turn on my device I don't get the Samsung boot logo i get 2 icons. Left icon is a phone right icon is a computer...really don't know what else to do. Appreciate any help

Try using Odin without the pit file and put the tar in the PDA section. If that doesn't work try redownloading the tar file again. It might have been a bad download.
Sent From My Evo Killer!

Unfortunately I tried that already. Redownloaded and without the pit file

Try a different USB cable - the stock one sucks.

castkel said:
I really can't get this program to work. I followed the wiki to the T. Neither of the 3 options work. The only thing i notice that is different is the 3 option
If you get a FAILED error after it writes "param.lfs", try this method:
[SIZE="6" This worked for me -- disclaimer : i do not take responsibility if your car dies your phones blows up in a bundle of fire or cant work if cats fly and scratch your face if gas prices go to $5 ----- but this might help you [/SIZE][/COLOR]
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery
4. The process will hang while writing "factoryfs.rfs"
5. Reboot the phone and reset Odin
^^ I never get factoryfs.rfs just the same old param.lfs error
I came from EB13 & did one click root clockwork 3.0.0.5/6. After i tried to boot into recovery it coverted everything into EXT4 when the phone did not work after that i tried to use Odin to flash back to EB13. I was able to apply syndicateROM through clockwork but it still does not turn on. When i try to turn on my device I don't get the Samsung boot logo i get 2 icons. Left icon is a phone right icon is a computer...really don't know what else to do. Appreciate any help[/QUOTE]
youtube odin and you should get a vid help
1. restart your computer
2. take the battery out your phone wait till your computer reset
3. put the battery back into the phone WHEN COMPUTER HAS FULLY STARTED UP
4. open ODIN ... [url]http://www.mediafire.com/?5w7sb1iq7webt4l[/url] just incase u didnt have it already
5. phone in download mode the number 1 and power button
6. plug it into the computer you should see your phone in a higlight yellow code pop up in ODIN ...
7. there are 2 things checked 1 called AUTO REBOOT ( [COLOR="Red"]leave it checked )
8. UNCHECK THE F RESET TIME
9. just load the TAR into PDA . for whatever phone ur using .......... if you need to download a new tar then do so best wat to find multiple versions is usually GOOGLE IT EX: samsung epic eb13 tar
10. ONLY PDA
1.. hit start and watch the MAGIC HAPPEN
Click to expand...
Click to collapse

k0nane said:
Try a different USB cable - the stock one sucks.
Click to expand...
Click to collapse
Yeah the stock one doesn't even work for me. Windows 7 doesn't recognize it I'm actually using the HTC evo cable. This cable has flashed a Moment and Intercept several times

I seen the video as well. I wish mine worked that flawless. I even tried a different PC. Back/front usb ports. Same difference always hangs at the same error "param.lfs"

Hardware failure? Hard brick? Hope?

Hello people,
I'm actually trying to help a friend who bricked his GNex while trying to flash primela03 bootloaders.
Volume + Power combos don't work anymore, the screen doesn't turn on at all (not even the exclamation mark "soft brick" symbol)... so I figured I would try this jig that I have, which worked on pretty much every Samsung Android phone that I've flashed.
But in this case there was no effect. The screen still doesn't turn on, the battery doesn't warm up while plugged to the charger, and the phone in general does not manifest any signs of life.
The last thing he saw before the phone gave up the ghost was the following :
Code:
# fastboot flash bootloader bootloader-maguro-primela03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.398s
But I don't think this is enough to send a phone spiraling to hell like this.
I've been looking around here, but this seems to be a rather rare case. So... RMA?
Cheers,
Antonius Maximus.
--

I would try to use ODIN and bring it to complete stock everything at this point. As word of advice ODIN WILL also wipe the SD card partition so all of your friends data will be gone...

MisterEff said:
I would try to use ODIN and bring it to complete stock everything at this point. As word of advice ODIN WILL also wipe the SD card partition so all of your friends data will be gone...
Click to expand...
Click to collapse
As I implicitly stated above, the phone doesn't respond to anything, not even a USB jig. So, getting to Download mode seems impossible at this point, making Odin useless.

Does it show up in Device Manager at all when plugged into the computer?

Last option before JTAG would be attempting an OMAP Flash. As long as it recognizes without a battery while plugged into the computer.
http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/
I use it all the time. I can fix about 4/5 bricks with this - if it doesn't, the processor is fried.
Good luck!

Naezor said:
Last option before JTAG would be attempting an OMAP Flash. As long as it recognizes without a battery while plugged into the computer.
http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/
I use it all the time. I can fix about 4/5 bricks with this - if it doesn't, the processor is fried.
Good luck!
Click to expand...
Click to collapse
Exactly, this is the way to go.
If nothing else responds then this is your only option, otherwise its pretend it got fried in an ota.
And that's fraud, we wouldn't do that now would we.......

So you can't reach the boot loader??? =\
Not even get the screen to turn on???

DLD511 said:
So you can't reach the boot loader??? =\
Not even get the screen to turn on???
Click to expand...
Click to collapse
Nope, the phone is truly unresponsive. My friend is bringing the device over tomorrow, I'll attempt the OMAP Flash and post the results here.

Man what to do there.....
I have like 8 different ways to fix this if you could just get that bootloader. But if you did you'd probably fix it in no time.
Sent from my Galaxy Nexus using XDA

I have to say this phone is puzzling me more and more. I have never encountered a case like this.
So, the good news are : the OMAP flash resurrected the phone.
The bad news are : I can't get into fastboot or recovery. I get the Phone -- Triangle -- Computer symbol on the screen, which I have never seen before on a Galaxy Nexus (only on Captivates, GS1 and GS2).
So I figured I could use Odin 1.85 and flash Chainfire's stock images. But this is what I get :
Code:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> bootloader.img
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!
As soon as it tries to flash the bootloader portion of the tar file, it hangs and fails after a few seconds. Then the phone reverts to its completely unresponsive state, and I can only get it back to life with another OMAP Flash.
I've done quite a few phones before, but this one leaves me baffled.
Anybody has seen this before?

So here's the final situation...
Here's the current status :
OMAP Flash resurrected the phone
No access to bootloader, download mode or recovery
<Phone--Triangle--Computer> symbol appears regardless of Pwr/Vol key combos
USB Jig has the same effect : <Phone--Triangle--Computer>
Odin recognises the phone
Odin fails to flash anything, getting stuck at NAND Write Start, no matter which partition I try to flash
Checking Repartition and using partition-table-0915.pit on Odin has the same effect, getting stuck at NAND Write Start
To disqualify enthusiasts' advice, here's what I have done so far :
I have used every possible driver that I know of (PDAnet, Kies, GNex Toolkit), but Odin still doesn't get past NAND Write Start
I have used multiple USB cables, including the original GNex cable
I have tried to flash Chainfire's all-in-one Odin package
I have tried to flash the original firmware
I have tried to flash each partition individually (bootloader/radio/pda, etc)
TL;DR - Phone is stuck in <Phone--Triangle--Computer> no matter what I try, and Odin fails to flash.
At this point, I need some major help.

Not sure if I can be of any help, but here goes:
The <Phone--Triangle--Computer> is download mode. At least this is a start.
The only partition that you need worry about at this point is the bootloader. All the others can be flashed from that.
Given that odin is not downloading the bootloader to your device, i only see two possibilities: 1) the physical NAND is corrupt, or 2) that something is messing up when you are trying to use odin.
1) Are you using odin v1.85?
2) Did you do the following step IN ORDER?
1. Enter download mode on your device.
2. Launch ODIN software
3. Press the PDA button and select the .tar file.
4. Make sure in ODIN that "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
5. After the above, then connect your device to your computer.
6. Press the "Start" button.

efrant said:
1) Are you using odin v1.85?
2) Did you do the following step IN ORDER?
1. Enter download mode on your device.
2. Launch ODIN software
3. Press the PDA button and select the .tar file.
4. Make sure in ODIN that "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
5. After the above, then connect your device to your computer.
6. Press the "Start" button.
Click to expand...
Click to collapse
Yes to all, of course. This is far from being the first Samsung phone I flash (even though I admit I never had to use Odin for a GNex).
However, I did wipe and repartition the phone with its PIT file, and that allowed me to access Fastboot after an OMAP Flash. So, new development : I got to Fastboot!
However...
Of course it tells me that there's no bootable ROM, and that's fine. Any command, and I really mean any, crashes the phone in a rather spectacular way, heating up dramatically and progressively displaying scanlines until the screen is entirely white.
One exception : the fastboot flash command which doesn't work but displays the following -
Code:
D:\Android\platform-tools>fastboot flash bootloader bootloader-maguro-primela03.img
sending 'bootloader-maguro-primela03' (4760 KB)...
OKAY [ 0.456s]
writing 'bootloader-maguro-primela03'...
FAILED (status read failed (Too many links))
finished. total time: 0.551s
... after which the phone becomes dead an unresponsive like in my first post, and I have to defibrillate it with an OMAP flash, and so on and so forth.
So, the new status :
Harmless fastboot commands (like fastboot oem lock) crash the phone with much drama
Flash commands return "too many links" and kill the phone (OMAP Flash needed)
It's not a cable, driver, blah issue - I have another GNex phone here which I have flashed exactly the same way and all these commands worked fine.
This smells strongly of a hardware fault, so I'll be suggesting RMA tonight when I see my friend again (unless someone thinks of something else of course).
Thanks for all your help guys.

Same problem
I have the same problem here with my GNexus :/

I have the same problem with my Galaxy S1
I was flashing a new ROM on it, but Samsung Kies was running the background, process failed, (I closed Kies from task manager this time)
I tried to restart the phone in download mode but got the Phone-Triangle-PC icon.
Tried again to put the phone in download mode, then it went dead, unresponsive, absolutely silent, no lights...nara.
Let me try an OMAP flash -not sure how to yet...but google's a friend.

I got the similar situation with my GN, the phone boot into fastboot and odin mode but when I try to flash anything the screen goes black and start to show a white lines from top to bottom.
with mine I tried the OMAPFlash and it got stuck in this for hours
Code:
» Downloading complete
» Elapsed time: 0:01.445 (33680 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\tuna\MLO_4460_HS_PRO'
» Sending data (131072 bytes) ::::::::::.......... [65536]
I hope you can find a solution to it.

I have a Nexus that is bricked too. It responds to OMAPFlash but nothing else, no fastboot or download mode. I'm going to try the USB jig today, otherwise I have to sell it.

Naezor said:
Last option before JTAG would be attempting an OMAP Flash. As long as it recognizes without a battery while plugged into the computer.
http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/
I use it all the time. I can fix about 4/5 bricks with this - if it doesn't, the processor is fried.
Good luck!
Click to expand...
Click to collapse
OMG!!!! THANK YOU for the link!!! I accidentally flashed a Nexus 7 Touch recovery on my GNex, and totally killed it. I was just about to post it on eBay as a "for parts only" auction! Thank you again!

Absolutely same situation
@AntoniusMaximus: What did you finally do?
I have a colleague's Nexus which was bootlooping. I tried to install from the factory image.
$ fastboot oem unlock
worked and the phone was unlocked.
$ fastboot flash bootloader bootloader-maguro-primelc03.img
gave the same error: FAILED (status read failed (Too many links))
and the phone could not see daylight again...the phone becomes dead an unresponsive.
I have not tried OMAP Flash. And have no clue as of now how to do that.
However, the battery does warm up when plugged to the charger.
Were you able to find a solution? The phone is just a couple of months old and can be replaced by samsung if i am able to lock it back (to have the warranty). Is there a way to do that?

Garfield. said:
@AntoniusMaximus: What did you finally do?
Were you able to find a solution? The phone is just a couple of months old and can be replaced by samsung if i am able to lock it back (to have the warranty). Is there a way to do that?
Click to expand...
Click to collapse
Sorry about that, I thought this thread was dead and buried.
The conclusion to this ordeal was fairly simple : RMA. This was apparently a NAND issue, one of these very rare hardware bricks. It wasn't caused by flashing, and it happened spontaneously while the phone was operating normally. No custom kernel, no overclocking.
It came to be as the very first device that I had to return, but thankfully I wasn't the culprit. I tend to be excessively cautions.
You can lock back the phone by putting it in Fastboot mode (phone -- triangle -- computer) and issuing the command :
Code:
# fastboot oem lock
Theoretically, unless they can find evidence that you overclocked anything, you should be fine.
Cheers,
Antonius Maximus.
--

pit files for i317 and i317m

As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.

If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480

Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?

pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.

Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.

anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?

Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.

Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...

anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.

terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.

rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin

Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app

Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).

Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!

My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks

Works fine on i317m

anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593

qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.

Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE

kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged

[Q] Please Help! Flashing errors

Samsung Galaxy s3 T-mobile SGH-T999 4.3 jellybean
I have been trying for a few days to flash my phone but no luck. All I want is to get cyangenmod but I encounter errors everywhere I go. I have tried the simple method provided by cyanogenmod themselves but at the end of the process it boots me up into recovery mode telling me that I might lose root and asking that if I want to fix it. No matter what I choose it decides to boot up into regular touchwiz with no apparent changes. I have tried the mobile odin method but it comes up with an error and boots up yet again. It came up with an error but the screen turned off before I could read any further. I have tried flashing the rom via rom manager but everytime I do it boots me up into recovery mode with an error and eventually asks me that same question regarding root just before returning me back to touchwiz. I have even tried using odin307(which I used to root my phone) but it no longer recognizes my phone. I have no idea what to do. My phone still works fine although I get more errors concerning google application after a factory reset but I can still use it no problem. Also, whenever I try to boot up into recovery mode it just shows up with that cyanogenmod icon and then it dissapears just before having it boot up normally so i can no longer boot up into recovery mode. I have downloaded clockworkmod recovery but no luck. I have done so many things that I wouldn't be surprised if my phone turned out to be broken now. whenever I boot up into download mode it now tells me that everything is custom. I have heard of problems concerning knox but when I rooted my phone it didn't it didn't seem to get rid of it. This is really driving me nuts and I now hate samsung for having it made so hard to tweak anything in this phone. Does anyone know of a way get passed all of this stuff and flashing the rom? is my phone broken now? Any help would be greatly appreciated.

It helps a lot if you included exactly what errors you saw. A recovery log, what exactly you're trying to flash, and any other related details goes a long way.
If odin doesn't see your phone its probably a driver issue. What does it say in device manager?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
It helps a lot if you included exactly what errors you saw. A recovery log, what exactly you're trying to flash, and any other related details goes a long way.
If odin doesn't see your phone its probably a driver issue. What does it say in device manager?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
As you can see, I am a complete noob when it comes to this stuff so I apologize in advance if I don't answer your questions in the correct manner.
If you are talking about the phone drivers, I had already installed them some time ago. I have even installed kies and kies3. Odin recognized my phone before I did all of this since it was what I used to root my phone. I am still able to access the phone's files through my computer.
when I used rom manager it would give me an error right after the whole backup process and show me recovery mode. I would try to look up the same rom via the recovery directory but it would give me the same error message. If i clicked on the reboot option, it would boot me up to stock. If I clicked on the **go back** option a couple of times it would give me this message.
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
*Go back*
no matter what I clicked on, it would boot me up into stock yet again.
I tried doing this again just now and it turned off. it then showed that small strip of blue at the top left that it usually shows before booting up into recovery mode and the screen turned off shortly after. at this point I was unable to turn on the phone even with the charger on. I was only able to turn it on after booting it up into download mode.
This same root message appeared when I tried to flash using the cyanogenmod website method. the only difference was that it only showed this message and not the whole recovery menu.
The device manager reads it as "Samsung device"

Ok, first thing you should do is uninstall kies. Odin usually wont work if its installed. If it still fails to see it in odin, uninstall your drivers through device manager, then install the stand alone driver pkg from my sig. (Use the second or third newest to start, the latest should work, but its had a lot more changes for the S5 and Note3.)
Once you get Odin working, download TWRP and flash. (Put the file in PDA if using Odin v3.07, or put it in AP if v3.09). See my sig for everything you need. (Get the .tar or .tar.md5 file for flashing in Odin btw.)
Next boot recovery and flash your rom. A factory reset would probably a good idea at this point, but you can try without first if you want.
If you have any questions or problems feel free to ask. Most of us dont mind helping at all, so long as you are willing to make an effort to help yourself first.
Good luck!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Oh, and Sammys devices wont turn on when plugged in. This is perfectly normal.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Ok, first thing you should do is uninstall kies. Odin usually wont work if its installed. If it still fails to see it in odin, uninstall your drivers through device manager, then install the stand alone driver pkg from my sig. (Use the second or third newest to start, the latest should work, but its had a lot more changes for the S5 and Note3.)
Once you get Odin working, download TWRP and flash. (Put the file in PDA if using Odin v3.07, or put it in AP if v3.09). See my sig for everything you need. (Get the .tar or .tar.md5 file for flashing in Odin btw.)
Next boot recovery and flash your rom. A factory reset would probably a good idea at this point, but you can try without first if you want.
If you have any questions or problems feel free to ask. Most of us dont mind helping at all, so long as you are willing to make an effort to help yourself first.
Good luck!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Oh, and Sammys devices wont turn on when plugged in. This is perfectly normal.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you for the timely and thorough responses.
Okay so odin is now reading my device. It just isn't reading my device while on download mode though.
I tried the .tar version first and this is what came up:
C:\Users\Jerry\Desktop\openrecovery-twrp-2.4.0.0-d2tmo.tar
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I attempted this four times and they all ended with "fail" at the top
I then attempted the .tar.md5 and I received this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> openrecovery-twrp-2.3.1.0-d2tmo.tar.md5 is invalid.
<OSM> End...
It seems like it is not even reading this file. This came up before even connecting my device. I tried a couple versions of this but they all had the same result.
My phone then asked to update clockworkmodrecovery and I did.( I actually installed the rom installer version) After doing so, I decided to try my luck and boot up into recovery mode. This time I was successful in booting up into recovery mode although it still showed me that cyanogenmod icon right before getting there. I then went on to install a zip from sd card only to receive the same message I have been receiving since the very beginning:
Installing: /sdcard/0/cm-11-20140217-NIGHTLY-d2tmo.zip
Finding update package...
Finding update package...
Opening update package...
Installing update...
assert failed: THEN A BUNCH OF THESE getprop(" ro.bootloader") =="T999VVLUVUBMK4" (WITH VARIATIONS AFTER T999)
E: Error in /data/media/0/cm-11-20140217-NIGHTLY-d2tmo.zip
(status 7)
Installation aborted.
After error I clicked on the "reboot now" option, only to come up with this message again:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
This message is what seems(at least to me) to be the main problem. It has appeared after a successful cyanogenmod standard installation (the one from their website) only to restore everything to default after I click on it. Instead of rebooting normally like cyanogenmod said, it would bring me up to this screen. so it seems that even if i were to have a successful installation, this would keep it from going through
I also tried mobile odin but, once again, showed an error that disappeared before I could remember anything.
Thanks your help is really appreciated.

If odin isnt seeing it in download mode try reinstalling your drivers, maybe a different version. Also, check what version of odin you are using. If 3.07, try 3.09. If using 3.09, try 3.07.
Another thing I noticed is the twrp you were trying to use is quite old. Try 2.7.0.0. If you still cant do this from Odin, use the Goo Manager app from the store. (Press menu, then install openrecovery script)
Also, install Terminal Emulator, and enter this:
getprop ro.bootloader
Tell me what it returns. Finally, if you want, open the rom zip file and find the updater script. Open with Notepad++ and delete the assert lines at the top. Save then delete the sig files from the rom, rezip and flash. (There are 3 signature files, cert, manifest, and another. If found, delete, if not, ignore)
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
If odin isnt seeing it in download mode try reinstalling your drivers, maybe a different version. Also, check what version of odin you are using. If 3.07, try 3.09. If using 3.09, try 3.07.
Another thing I noticed is the twrp you were trying to use is quite old. Try 2.7.0.0. If you still cant do this from Odin, use the Goo Manager app from the store. (Press menu, then install openrecovery script)
Also, install Terminal Emulator, and enter this:
getprop ro.bootloader
Tell me what it returns. Finally, if you want, open the rom zip file and find the updater script. Open with Notepad++ and delete the assert lines at the top. Save then delete the sig files from the rom, rezip and flash. (There are 3 signature files, cert, manifest, and another. If found, delete, if not, ignore)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Hey man I was finally able to flash my rom! I updated both the drivers and odin and was able to successfully install the recovery file. It still did not install cyanogenmod reading an md5 error and "error executing updater binary in zip" though. anyway I installed AOKP instead and it finally worked. I think the cyanogenmod files that I downloaded were just incompatible with my device or faulty (even though i tried like 10. maybe something wrong with my phone?). Anyway I am really grateful for all of your help. I was so happy after I was finally getting it. It seriously frustrated the heck out of me. I no longer hate my samsung and am quite liking this new rom. Thanks again!

Glad I could help and that you seem to be happy with it so far!
Sent from my SGH-T999 using Tapatalk

Phone Stuck on Dowloading (Do not turn off target)

Hi,
Phone; SM-AF520F
My phone has been restarting on its own from the past month and I ignored it. It showed me occasionally Google services failed or system UI is not responding.
I factory resetted the phone as any noob would do and the restart occurrence went to only at night, which I was unbothered with. A little time passed and the phone went to the downloading sky blue screen.
I'm aware with flashing roms and stuff but I never really tried it. I tried everything;
i) Used Odin, three different versions
ii) Used Stock firmware, three different versions
iii) Used Smart switch
The phone only went in download phase and than in the phase where you press home button, volume and power and it shows fonts in the left hand corner. Odin always giving me errors, sometimes stucking on setting up connection.
Two errors:
i) There is no PIT partition
ii) Write operation failed
There are always these things happening.
When I restarted with volume down and power key, the system showed, there was an error and try smart switch, updated my drivers but when I go in the settings to emergency recover my phone, it does not show my phone.
After restarting the phone couple of time, Im in downloading mode again, in between the screen also turns full sky blue with no text.
I tried installing custom recovery but the image didn't load, ( I dont know what i am doing at this point, even if this was a good idea).
I have scavanged every forum, every post, everything on the internet but I just can't seem to fix it, I tried every possible thing and it just dosent work. I know it can be fixed but I don't know how. I know I'm doing something stupidly wrong but I can't seem to figure it out.
This is an old phone, I'm going to buy another one soon but I just hope it works for another week? Can I wipe the whole system and start from scratch (Which i dont know how to do).
Any type of help would be greatly appreciated, or just tell me to give up hope on it so I can just throw it away and move on.

1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!

matkali said:
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
Click to expand...
Click to collapse
Thank you for your response.
I did what you exactly said, previously it failed at the instant, now it moved one tab and than failed.
I tried the provided Odin, than tried two roms with, with the pit filed extracted and enabled re partition.
The error occurred: Complete(write) operation failed.
The error occurred every time I tried to flash, it never worked.
Do you think there is anything else to do?

Try this way to go download mode:
Press vol-down + power until phone restart
Then instantly press vol-up + Home + Power to going to download mode!
If it not works for you! You can use (eMMC programmer or easy JTAG) to writing rom on your phone memory (Last Option)!

I gave up on it and asked for professional help. Idk what he did, but he fixed the phone. It was sluggish at first but it works like a charm now.
It took 7 minutes to turn it on, than It said, there was an authorized user who tried to access your phone, use your previous email password to access your phone. I put it on my previous details and the works okay after some updates.
I wonder what he did? And i never knew android has a feature where if somone tries to reset your phone, google account locks it? Wow.
Is flashing a custom os a good idea? I'm afraid I'll brick it or something or just keep running one ui and wait for it to die again.
Thank you for your help btw, made me learn alot.

matkali said:
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
Click to expand...
Click to collapse
im having the exact same problem this guy has, installing a pit file will erase my data? if i use HOME_CSC will the pictures stay? i only care about the photos.