I717M stuck on I717 : wont take .pit file - AT&T Samsung Galaxy Note I717

At some point in the phones life I must have flashed a stock att because now I can't return to stock I717M. ODIN MODE say I am using a Product: SGH-I717 : Instead of the intended SGH-I717M. I am investing the time because the phone is crashing imminently and/or immediately after a odin stock flash.
Oddly enough my Product numder and SN: are coming back with an error in Kies aswell. At this point I am flashing in circles :silly: and really just want to start from the lowest common denominator for this phone as a base with proper .pit and CSC ... etc. so this is 100% official stock I717M and all the threads I read are resolved by standard flashing protocol but not mine!
Many of the automated flashes that you just drop on the PDA line cause issues in stock recovery mode by missing the CSC and I can't account for all the crashing. Perhaps SOMEHOW finding my way back to "M" will do this ? I think... : )
Thanks ahead of time everyone for your help :good:

---

Go back to Gingerbread using these files flashed through Odin:
http://forum.xda-developers.com/showthread.php?t=1657279

---

Agoattamer said:
Go back to Gingerbread using these files flashed through Odin:
http://forum.xda-developers.com/showthread.php?t=1657279
Click to expand...
Click to collapse
Thanks for the quick reply ... I have done this though and receive an error with the .pit file.
I am using ODIN 1.85 it starts the process and ends in error. The phone reads SECURE CHECK FAIL : PIT
But unlike the individual in the thread I have a more serious issue because I am using a I717M and using this method and receiving the error he had with a mismatched phone !?! This to me indicate somehow my phone thinks it's a i717( ) not a I717M. Kies sees only a I717 and when I force a "Firmware and Upgrade Initialisation" from the menu it stays exactly the same. When I use SGH-I717M and my SN to restore to factory I get : Model name: SGH-I717M : 'SGH-I717M' does not support initialising. All you can click is OK,
Now what ?
Thanks again for the help ...

---

futiless said:
Thanks for the quick reply ... I have done this though and receive an error with the .pit file.
I am using ODIN 1.85 it starts the process and ends in error. The phone reads SECURE CHECK FAIL : PIT
But unlike the individual in the thread I have a more serious issue because I am using a I717M and using this method and receiving the error he had with a mismatched phone !?! This to me indicate somehow my phone thinks it's a i717( ) not a I717M. Kies sees only a I717 and when I force a "Firmware and Upgrade Initialisation" from the menu it stays exactly the same. When I use SGH-I717M and my SN to restore to factory I get : Model name: SGH-I717M : 'SGH-I717M' does not support initialising. All you can click is OK,
Now what ?
Thanks again for the help ...
Click to expand...
Click to collapse
not that I am a brainchild in this department, or any other for that fact, but I read a lot and have not heard of this one.
I sometimes think if I ask questions, would or could this inspire others to come up with the solution.
have you called your carrier? can they not help you?
have you tried uninstalling drivers and re-installing for Kies purposes? to try an "emergency firmware recovery" (I think that's what it was referred to as)
what modem shows on phone? and can you flash appropriate modem to carrier?
you mentioned PIT file in PDA slot? I have always used .TAR files (maybe same thing, different terminology?)
as I said, just questions that come into my mind. maybe help troubleshoot?
good luck my friend
one more***********************
I just went to link recommended by the GOAT guy ( sorry for raping your name).
noticed post #1 was titled for BELL and listed files. then I went down and saw post #4 were files for ROGERS. did you notice that?
you didn't say which was your carrier

---

The only thing I can think of is I had a brick at one point and me and a service tech JTAG'd in the files : could this explain why my phone thinks it isn't a I717M?
I using Mobilicity and a AWS modem/hack
Thanks for advice everyone this is quite the problem and is clearly unresolved as it just wont take the .pit file and if I use the pda/phone part only only the pda will even flash from that post. So no CSC, graveyard, pit... all of which I need.
:crying::crying:
I think this phone is a mess.
Sean

---

Not sure of it make any difference at all.....but I used Odin the other day and it was version 3.0.7 located in this post:
http://forum.xda-developers.com/showthread.php?p=42806745

---

Bubbajoe40356 said:
Not sure of it make any difference at all.....but I used Odin the other day and it was version 3.0.7 located in this post:
http://forum.xda-developers.com/showthread.php?p=42806745
Click to expand...
Click to collapse
I used it and it proceeded unlike 1.85 but I still have a fail on the PIT : and when I reset and go into download mode it says SGH-I717 and Secure Check Fail: PIT at the bottom: in recovery mode i get a smashed android and a error about a genaric CSC and that it is still using ATT CSC !?!? Also a very concerning error regarding sdcard E: cannot be found ?!? this is new...
Yes and it WILL NOT BOOT '.':crying:
Can anyone confirm too if I should be seeing I717M in odin and recovery modes

---

At one point I worked with a service tech at the local JTAG shop took us all afternoon but we got it to boot out of a hard brick loopback dongle wasn't working. I THINK he put the ATT kit on my phone from JTAG and that is the problem now ...
Does anyone with a good handle on this stuff know if I can use the feared "NAND ERASE ALL"I am scared but it seems to make sense that is what it is ...
Anyone care to say they agree I have no right to hold anyone accountable and at this point I am running out of optinos ... it would semm..
Sincerely S:silly:

---

Does not matter what region phone you have. Whether it is att or a Canadian carrier this ROM should install. Did you follow directions in that thread fully? Since you are using a pit you have to select repartition in the check boxes.
Sent from my SAMSUNG-SGH-I497 using xda premium

---

Couldn't be more straight forward and I followed the instructions exactly. There were frankly no more than 2 sentences of instructions. Which I followed, regarding the check box for repartition it got selected automatically when you put something on the .pit line. I have not tried without repartition checked. I figure this might be a case for NAND ERASE ALL

---

See If it takes the csc..and firmware
the partition table shouldn't need flashed, all variants are partitioned the same.

---

What is up with these canadian variants? There are so many posts about not being able to flash, superuser not taking, modem having to be reflashed. Just don't see this with the ATT version. I wonder if there is another script causing all this....

---

studacris said:
See If it takes the csc..and firmware
the partition table shouldn't need flashed, all variants are partitioned the same.
Click to expand...
Click to collapse
Here is the log from Odin 3 3.07 : (1.85 just crashes with a PIT error as specified before) However Odin 3 proceeds as follows for those who can shed more insight I will be grateful to no end:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ABOOT_SGH-I717M_I717MUGLA2_user_CL875155_REV00.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_KERNEL_AMSS_SGH-I717M_I717MUGLA2_user_CL875155_REV00.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I717MUGLA2_phone_secure_Q1_BMC_REV_00_CL870799.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-I717M-CSC-BMCLA2.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> rpm.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> cache.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> tomb.img.ext4
<ID:0/006> userdata.img.ext4
<ID:0/006> amss.bin
<ID:0/006> mdm.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
-----------------------------------------
here we can see odin blazing through without an issue but !! the same .pit error occurs and after reset the system boots to TWRP recovery instead of stock !?!?!! A huge log of errors also occur regarding not being able to find internal storage the TWRP directory and EMMC not formatted or mounted ?!?
When I boot to ODIN it says current binary : CUSTOM ?!
I am really confused now..

---

I need a couple things answered :
1) does I717(M) varient display the (M) in ODIN when on the proper download mode or do they all say I717 ?
2)When Odin mode says stock binary : Yes (for all intents and purposes is it a mirror copy (modem,boot,recovery,pit etc.) ?
3) If not what is likely different ? (ie how could I send it back for stock repair or resell as the original)
4) Now everything seems to be worse in the sense that every rom is locking and freezing after you click android to start setup after a long wait possibly the second screen it reboots ?
5) in stock recovery I get a Update from RB fota mode now ? how does that work from recovery ? I thought it would need internet access at least.
THANKS EVERYONE :good::good::good::good::good::good::good:

---

A couple questions for you..... You mention in stock recovery you get "Update from RB fota mode now" but you said earlier that after you install and it reboots you back to TWRP? Now which is it?
Are you installing the stock gingerbread ROM with ODIN when in "Download Mode" on the phone? Hold "Power" and "Volume Down" down. Can you get the phone to boot enough to format the internal (usb) memory? I don't know if that option is available in stock recovery or if it functions correctly in TWRP. This is not the same as a full wipe. I know stud will say it has nothing to do with installing ROMs. But I know 2 people that had a similar issue as you ( 1 being me) and the only way the write would take is if the internal (usb) memory was formatted. This leads me to believe there is some kind of script stored there on Canadian variants.

---

Agoattamer said:
A couple questions for you..... You mention in stock recovery you get "Update from RB fota mode now" but you said earlier that after you install and it reboots you back to TWRP? Now which is it?
Are you installing the stock gingerbread ROM with ODIN when in "Download Mode" on the phone? Hold "Power" and "Volume Down" down. Can you get the phone to boot enough to format the internal (usb) memory? I don't know if that option is available in stock recovery or if it functions correctly in TWRP. This is not the same as a full wipe. I know stud will say it has nothing to do with installing ROMs. But I know 2 people that had a similar issue as you ( 1 being me) and the only way the write would take is if the internal (usb) memory was formatted. This leads me to believe there is some kind of script stored there on Canadian variants.
Click to expand...
Click to collapse
That is a very intelligent perspective; presently I can say that I got the stock recovery in but only with ODIN 1.85 with phone boot-loader update checked off (gret in the new 3.x versions of ODIN). So I could never get the phone to format without error when using all 5 items
For the record THE ONLY WORKING STOCK SO FAR is :
[Stock ODIN] AT&T Jelly Bean Download
http://forum.xda-developers.com/showthread.php?t=2261598
I found a Stock ODIN JB Bell Download from another site but it froze at every screen during setup until it would just reboot itself (seems like Kernel might be wrong though)
None the less me and all other (1717M)'s are in fact isolated in this condition to ATT stock roms and honestly; to be frank it could explain why I have been frustrated with the blaze modems on this thing since last July when I got it. I have spent days at a time trying to find a modem that wont drop and require a power cycle + 10 minutes to come back online.
Maybe Mr. Goat you are right, maybe me and a bunch of others are literally stuck with a I717 because of lingering scripts, wouldn't surprise me because TWRP was sticking around for a long time until I checked the bootloader format and only in 1.85 oddly enough.
WHAT I think the rational ones reading this should be questioning is why does my Download Mode ODIN read I717 no (M) after all these attempts to wipe and format and when using (M) varient stock roms the phone wont boot and crash like it has the wrong kernel (or modem) fixed with a ATT stock rom (on the surface anyhow). This would be fine if I didn't have a BELL serial number and clearly its something else.
For the extremely advanced I once found a thread (can't for the life of me find it again) where someone managed to change the model of the phone because it got changed I think during a JTAG. This would make sense as I had to do this too. I downloaded an app on the play store which used root and I allowed it to adjust SD-EXT for SD caching (BIG MIS-TAKE) Hard brick was the result. While I was getting help the app would auto execute on startup and time was running short so I imagine he pushed me to ATT stock. I want to make it bell again as my phone crashes a lot and I am not sure if this can even relate to it or not.
THANK YOU EVERYONE I AM VERY GRATEFUL

---

Did you even try the Odin version for Bell Jellybean?
http://www.hotfile.com/dl/213003896/d4f7f24/I717MUGMD1_I717MBMCMD1_BMC.zip.html
Or how about Bell ICS version for odin?
http://www.hotfile.com/dl/163095548/c1447e9/I717MUGLF4_I717MBMCLF4_BMC.zip.html
If you install a stock ATT ROM, the phone will report back as an I717. It has nothing to do with serial number. It has to do with software.
If you can install a stock ROM and it works then immediately format that USB memory and then do a factory reset.
And if your phone crashes alot, try a new battery. You might think it is good but it could be giving an incorrect voltage.

---

wish i could say this worked as it didn't still stuck without the (m) : using those downloads it loads to black screen have to hold power 15 seconds and it vibrates and back to the black screen...

---

Hello every one ... I know as a fact that I717M could be hard on patience .. as Bell uses HSPA and LTE instead of 2G and the others .. hard to find the right modem and others.
When i had that problem to revert to stock ... I got the full file for Stock Bell Jellybean (around 700 meg file zip) ... unzipped .. used odin 3.07 (recently seen 3.09 really good too) and placed the .MD5.TAR file into the PDA (called AP in odin 3.09) section .. had just the auto reboot checked and flashed good with it (important that it is the in second line option (the PDA one or AP in odin 3.09)
PS: I had my phone in download mode when flashing as it should ... (reboot holding volume down)
For the customer rom or counter that says you have been a bad boy .. I had to go on the thread for counter reset and that did it ....
hope it will help .. (recently had to do that often as I am trying tons of ROMs)
Cheers
---------- Post added at 11:39 AM ---------- Previous post was at 11:38 AM ----------