[AT&T Samsung Galaxy Note I717] gregsarg:
folks,

With the recent number of AT$T note users having Odin troubles, I decided to post up a few of the "known" problems that jam up the device. They are Brick level issues, and I decided to share them with you in a new thread.

The information is likely already out there, but spread far, and over many threads, so this will offer you a one stop fix you "NEED" to have, in the event you are restoring the SGH-I717 device to a factory state, and you find yourself seeing the download mode "limp mode" screen.

( this screen makes you think that download mode is gone, and no longer functions, but it does)...

Many users have the desire to return to stock, and in doing so, have encountered Severe Odin issues. This particular one, has caught several users in the last month, myself as well, and can catch even the seasoned Odin user by surprise.

Follow the steps below, and you will be okay....(I hope.)

(First) : When flashing a stock Odin .tar back to the SGH-I717, you "MUST" first go into your recovery...(CWM/TWRP) and factory reset the device. This will remove the data remnants that are often staying on the device.

(this can cause an immediate force close when the device boots from a good flash restore, and can corrupt your new shiney restored rom on pre-boot)

(Second): When pushing the stock rom .tar through Odin, "DO NOT" uncheck the "reset" toggle in ODIN !!!

this bypasses a critical write step in the restore process, and forces the device into download "limp" mode. Basically asking you to emergency restore using kies.

This is because the recovery is still being written to the device, even though Odin confirms the write step as a "PASSED". and the boot must occur to finish the process.

(Third): and possibly the most important step:

"DO NOT" attempt to multi-push Odin files back to back, by turning off the reset toggle in Odin.

You "MUST" ALLOW THE DEVICE TO BOOT, between .tar flashes. Again, the reset is a feature that finalizes the writing of the files to the device, and must remain "ON"...

Now, I realize that many PC environments are different, and each device also. Not to mention user skill levels, and what is being accomplished. But with the number of folks having flash issues using Odin lately, I simply wanted you to be aware of a few things that "WILL" jam you up.

And I'm certain that a few of these "bricks", needing a JTAG repair, were not true bricks. Instead, the download mode was still there, but was asking for a Kies emergency restore in the "limp mode" screen instead.

The screen is much different, showing a picture of a device, with an "X" between it, and a computer icon. Basically telling you that your flash failed, even though Odin shows a "PASSED" in the dialogue box.

Edit:

In the event of the download mode "limp", you will see an error screen asking you to go into kies for an emergency restore.

The kies restore is not needed. As you can start Odin again, and push the rom.tar to the device from this screen. (but you "MUST" remove the cable, then open Odin and load the .tar, then plug in the device and wait for the "COM" connection to show.

If Odin fails to push the .tar, "Then" go to Kies, and emergency restore the device using the super secret code.

Standard disclaimers apply, and mileage may vary...so do your homework.

hope this helps a few of you out......g