Database Users

Phone is working fine, but Odin says "There is no PIT partition" when I try to flash.

Phone is working fine, but Odin says "There is no PIT partition" when I try to flash.
I have a GT-I9505 with the MDA version firmware, region EVR.
I've flashed it previously, successfully, to the latest ME2 firmware, but then I installed Chainfire3D which soft-bricked it.
I recovered using Kies firmware recovery, did a factory reset/cache wipe, have rooted the phone again... but now Odin won't flash the phone!
It says "There is no PIT partition", and when I try to re-partition using the PIT file from this thread, it just says "complete(write) operation failed".
I've tried Odin 1.8, 3.04, 3.07... all the same.
The phone is currently working fine and is rooted! I just want to flash to a newer firmware, is all.
Any thoughts?

Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium

samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I was doing both those things. Strangely, it worked when I used another computer! Thanks anyway.

I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Removed!!
<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> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.

0reo said:
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Removed!!
<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> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
Click to expand...
Click to collapse
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin

samersh72 said:
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
Click to expand...
Click to collapse
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?

0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
NO NEED to check it. a lot of users brick their phones and can not boot to check usb debugging. so they went directly to odin flash and it was good to go :good:

0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
Hi,
USB debugging needs to be ticked.

OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?

0reo said:
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
Click to expand...
Click to collapse
Hi,
Did you reboot your PC?

malybru said:
Hi,
Did you reboot your PC?
Click to expand...
Click to collapse
Yes, a number of times at every stage one would think it would make any difference. It didn't make any difference.
I did finally get my phone rooted. While I can't say for certain, it seems like the S4 needed to be booted normally, then connected via USB, then let Win7 auto install several drivers, then I initiated bhp090808's all-in-one root tool which rebooted the phone into ODIN mode. ODIN was then successful.
Contrast that with having the S4 disconnected from USB and manually booting into ODIN mode, then connect USB, then let Win7 install drivers, then initiate ODIN to start. That sequence gave me all the problems.
Thanks for the replies though. I do appreciate your willingness to help.

Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1

On pit partition found
samersh72 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND.
Click to expand...
Click to collapse
aa
---------- Post added at 08:53 AM ---------- Previous post was at 08:48 AM ----------
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
mpalka said:
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
Click to expand...
Click to collapse
]I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND

Sagar6699 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Click to expand...
Click to collapse
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046

Re-Partition
samersh72 said:
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Click to expand...
Click to collapse
Thanks!!
But now there is another problem........
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DDLD1_S7500ODDLD2_S7500DDLD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLZ HELP!!!!!!!!

probably solve with this
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,

Thanks for that suggestion. Switching to the back USB ports worked for me.
pisicutumic said:
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Click to expand...
Click to collapse

Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
and me as well!
thanks alot! :laugh::laugh:

yanivnn said:
and me as well!
thanks alot! :laugh::laugh:
Click to expand...
Click to collapse
And me too!

Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
For me too, you are genious!

[Q] Odin, i9505 modem flash fail

Hi,
Step one: Turn the phone on and open up the dialler.
Step two: Then type *#0011# on the keypad.
Step three: Press the menu key, then tap BACK on the screen, press the menu key again and this time select KEY INPUT.
When the box appears enter the number ‘1’ and press OK.
Step four: Once again press the menu key and then tap BACK on the screen.
You should now be in the ServiceMode main menu.
Tap on the first option – [1]UMTS,
then tap the first option again [1]DEBUG SCREEN,
then tap on [6]PHONE CONTROL,
then [6]NETWORK LOCK and finally [3]PERSO SHA256 OFF.
Step five: Head back to the UMTS menu by pressing the menu button and tapping Back on the screen.
Step six: From here tap [6]COMMON, then [6]NV REBUILD and finally [4]RESTORE BACKUP.
Step seven: Now wait for a few minutes while your Galaxy S4 reboots.
Step eight: Once it’s running again, switch it off, pop in your giffgaff SIM and power it back on.
Congratulations you’re now free to enjoy giffgaff on your newly unlock Samsung Galaxy S4.
This is my first time owning an android phone (decided to give it a go after being on iPhones for the past few years)
Bought the phone locked to 3 (Three UK), was trying to follow tutorial above but i couldnt get into service mode. after digging around for a bit, someone said that i should try flashing a different modem (I9505_XXUAME2) which should let me unlock it, and then flash back to what it is now (I9505_XXUFNC5).
So i found this tutorial on how to flash the modem, but I could not succeed. can someone point me in the right direction as to what am i doing wrong?
Thank you in advance!
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505_DXUAMDE2_MODEM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<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> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!

Almost all errors in Odin can be solved by trying the following things:
- Different usb port
- Different usb cable
- Different pc.

Lennyz1988 said:
Almost all errors in Odin can be solved by trying the following things:
- Different usb port
- Different usb cable
- Different pc.
Click to expand...
Click to collapse
so does the screenshot look right, and i dont need any additional files?

plotney said:
<OSM> I9505_DXUAMDE2_MODEM.tar.md5 is valid.
Click to expand...
Click to collapse
Odin gives a bit strange message... MDE2??? Even if it would be proper i9505XXUAME2 file, flashing could fail as the modem is from 4.2.2, not from 4.4.2 system.
If I'd be you, I'd start from digging for a PROPER modem file

spamtrash said:
Odin gives a bit strange message... MDE2??? Even if it would be proper i9505XXUAME2 file, flashing could fail as the modem is from 4.2.2, not from 4.4.2 system.
If I'd be you, I'd start from digging for a PROPER modem file
Click to expand...
Click to collapse
would it be easier to flash 4.2.2, unlock it, and flash back to 4.4.2? or would i have to root it?

plotney said:
would it be easier to flash 4.2.2, unlock it, and flash back to 4.4.2? or would i have to root it?
Click to expand...
Click to collapse
I don't see an error about MDE2. That's just a normal message in Odin. The screenshot looks alright. Try the things i said.

Lennyz1988 said:
I don't see an error about MDE2. That's just a normal message in Odin. The screenshot looks alright. Try the things i said.
Click to expand...
Click to collapse
tried all the ports on my pc - no luck
waiting for a mate to come down with another cable
and what about what spamtrash said about modem being from 4.2.2, would that be an issue? dont want to brick the phone within 24 hours of getting it

plotney said:
tried all the ports on my pc - no luck
waiting for a mate to come down with another cable
and what about what spamtrash said about modem being from 4.2.2, would that be an issue? dont want to brick the phone within 24 hours of getting it
Click to expand...
Click to collapse
You won't brick it.
Some users report that they can just flash flash the older modem, so I think you can just flash that modem on a newer bootloader. The only thing you can't downgrade is the bootloader itself.
Just to make sure, you are not running your windows on a virtual machine right?

Lennyz1988 said:
You won't brick it.
Some users report that they can just flash flash the older modem, so I think you can just flash that modem on a newer bootloader. The only thing you can't downgrade is the bootloader itself.
Just to make sure, you are not running your windows on a virtual machine right?
Click to expand...
Click to collapse
ah okay, so 4.2.2 modem on a 4.4.2 should be fine?
no-no-no

My primary concern would be that modem: I9505_DXUAMDE2_MODEM.tar.md5 - while googled it, the only source was... funny.
I'd really advise you to try find newer modem and reflash it via Odin

right.
flashing modem to I9505XXUAME2 - success
now when i try going into the *#0011# menu, it actually works, but however when i do the unlocking steps it still asks me to put a correct sim in or enter SIM network unlock pin.
any idea why its not working?

[Q] AT&T Galaxy S5 Update G900AUCU2ANG3 - Issues after update

I have tried searching and do not see anyone with a similar issue. I was previously rooted with TowelRoot, but somehow my phone not only allowed the G900AUCU2ANG3 update today to download, but also allowed it to install. I know I should have removed TR before continuing, but stupid stuff like that happens when you see the update waiting when you first wake up and don't have contacts in or glasses on...
I can fully restore my phone to normal use, other than wifi. For whatever reason, the failed update shows to have changed the baseband, but I have no ability to connect to a wifi network, and despite about 15 factory resets since this morning, my device status still shows "Custom." Here is exactly what I see when I go into Download Mode (or as close as I can replicate it):
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
At this point, I can't find anyone with an NG3 stock firmware to use with Odin, and Odin keeps failing because the old firmwares won't pass the authorization stage. I attached the Odin screenshot to this post in case someone has other ideas. I can actually use my phone (not bricked), but wifi will not connect even though it can see various open and secure networks. I get an error stating "Failed to Obtain IP" when trying to connect to networks with "Very Strong" signal strength (I can see the AP from my desk).
Thus, I really need to be able to do 1 of 2 things:
1) Restore it to stock myself so I can have wifi, or
2) Be able to get it to show "System Status: Official" so that the local AT&T Device Service Center I drive by twice a week taking my kid to hockey practice will plug it in and update it and restore it. They managed to save my wife's Note 3 from a fairly bad soft brick / boot loop issue, but I also know that the "Custom" thing will pretty much guarantee they don't work on it.
Thanks in advance.

..

fffft said:
Writing a full stock firmware image, followed by a factory data reset will remove the custom status. So that would satisfy No. 2.
As to your first wish, I find it hard to believe that you couldn't find an ATT firmware image anywhere. There are dozens of firmware sites and I can only assume that you just did a short or cursory search. If you spend a few minutes with Google you can surely locate any ATT firmware version that has been release longer than one day.
Either way, use Odin to write a firmware image as the fastest way to resolve the situation. If you have difficulties, try this guide
If the problem persists, then you need to provide us with more details. Notably, the verbatim Odin error log, along with the exact file name you are trying to write and a detailed, step by step description of how you are using Odin.
.
.
Click to expand...
Click to collapse
I definitely have searched high and low for a stock version (both before the original post and just now) that will work with the failed update G900AUCU2ANG3. No one has a stock firmware I can find, and I cannot find any method by which to downgrade to an older version that I can find, such as G900AUCU1ANCE.
Here is what my phone says in Settings --> About device:
Baseband Version:
G900AUCU2ANG3
Build Version:
KOT49H.G900AUCU2AND3
File name I'm trying (but know won't work...not the newest baseband): G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar
Odin Error Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

..

fffft said:
The additional information definitely helps. But it's still a drop in the bucket. You didn't give us a detailed, step by step description of how you are using Odin e.g. what version of Odin you are using , which line you entered the firmware file line on (e.g. AP, PDA, etc) and so forth. And most importantly, did you try the procedure that I linked to in my last post?
We can't see your phone and these details are important as any one of them could cause failure. So we need to check off each item that you are doing.
Nominally the Odin error you posted says that your bootloader refused the firmware version you tried to write. More likely it is a timing error from a marginal USB cable or port. Odin is well known as tempermental with respect to USB timing. Try a different USB cable (yes, really. and yes, it is important. don't skip this step) and different USB port.
Most critically, ensure that you are entering download mode by removing the phone battery, then replacing it and using the volume down + home +power key sequence. And also important, if the first Odin write fails, do not close the Odin window. Instead remove the phone battery again, go into download mode again and then hit write again in the open Odin window. Inevitably, the second attempt will then succeed.
Try the very good procedure that is listed here <---- click on the link
Odin can be frustrating, but with a modicum of patience and attention to detail you will succeed. Good luck
.
Click to expand...
Click to collapse
I ended up going to the local AT&T Device Support Center (luckily it's about 2 miles from the ice rink at which my son practices) and they flashed it back to stock with no problems. She said I was one of 4 people that day who had issues with that particular update, and since my Knox Warranty showed 0x0, she thankfully ignored the "Custom" on device status. All is well and I have a clean backup in Kies if needed in the future and TowelRoot back on the device to kill some bloat. Thanks!

Can I get a flashable G900AUCU2ANG3? I am selling the phone and they want it stock and updated. I can't flash it back to stock. I didn't update it but it gives me the same Odin error as though I was trying to downgrade. Used to be able to downgrade it and do whatever I wanted when I was tinkering with getting SuperSU to stick after update. I've made no major changes. Did something come down from Samsung that locks Odin? I froze Knox and thought that might have something to do with it so I thawed it and factory reset after unrooting. No good.
Long story short I'd like an Odin flashable latest firmware to see if it will take. Sorry I don't have more info right now but the buyer has the phone right now.

[Q] Note 3 SM-900 Stuck on Splash Logo (Download Mode Works)

Hi Everyone,
Having a problem here with a SM-900 Note 3 sent back to the US here by a relative. A relative asked me to purchase it off Amazon with their credit card (prime shipping), so it comes from a trustworthy source. AFAIK the phone was unrooted (Knox counter 0) and apps were installed through the play store. The phone is stuck at the initial "Samsung Galaxy Note 3 SM-900" screen. The logo is not steady, instead it keeps flashing every 3 seconds. Recovery mode does not work, or at least the phone keeps flashing the logo. Download Mode, however, works and the phone stays turned on steady. Kies keeps saying connecting and Jodin3 keeps saying my phone isn't connected. I have tried all 4 ports and 3 separate usb cables. I don't have access to a Windows machine only an iMac. I'm not sure what is wrong. I'm going to try downloading odin to my mac to see if it will work. If all else fails, I plan on contacting Samsung to see if they will fix it seeing as it was purchased only 4 months ago. Any help is greatly appreciated.

Hiya Buddy said:
Hi Everyone,
Having a problem here with a SM-900 Note 3 sent back to the US here by a relative. A relative asked me to purchase it off Amazon with their credit card (prime shipping), so it comes from a trustworthy source. AFAIK the phone was unrooted (Knox counter 0) and apps were installed through the play store. The phone is stuck at the initial "Samsung Galaxy Note 3 SM-900" screen. The logo is not steady, instead it keeps flashing every 3 seconds. Recovery mode does not work, or at least the phone keeps flashing the logo. Download Mode, however, works and the phone stays turned on steady. Kies keeps saying connecting and Jodin3 keeps saying my phone isn't connected. I have tried all 4 ports and 3 separate usb cables. I don't have access to a Windows machine only an iMac. I'm not sure what is wrong. I'm going to try downloading odin to my mac to see if it will work. If all else fails, I plan on contacting Samsung to see if they will fix it seeing as it was purchased only 4 months ago. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you were using a Windows PC, install Kies 3 to get a correct driver to be installed, then download a stock firmware for your device and flash via Odin. That could help to fix the problem.
I'm not familiar with iMac so I don't know what software can be a replacement for the Odin.
You can try Heimdall.

vndnguyen said:
If you were using a Windows PC, install Kies 3 to get a correct driver to be installed, then download a stock firmware for your device and flash via Odin. That could help to fix the problem.
I'm not familiar with iMac so I don't know what software can be a replacement for the Odin.
You can try Heimdall.
Click to expand...
Click to collapse
I managed to go over a friend's house and use his windows machine. I got the correct file and used Odin and it said "PASS". Unfortunately, the Note 3 is still having the same problem with the splash logo flashing every three seconds. Not sure whats wrong. Could it be hardware related? The battery contacts on the phone are fine. I don't think there is anything wrong with the battery itself because download mode works just fine. It seems to start the phone up its having trouble getting past the initial splash screen. Safe mode is not working either. Looks like I might have to put in a call to Samsung for warranty repair.

Hiya Buddy said:
Hi Everyone,
Having a problem here with a SM-900 Note 3 sent back to the US here by a relative. A relative asked me to purchase it off Amazon with their credit card (prime shipping), so it comes from a trustworthy source. AFAIK the phone was unrooted (Knox counter 0) and apps were installed through the play store. The phone is stuck at the initial "Samsung Galaxy Note 3 SM-900" screen. The logo is not steady, instead it keeps flashing every 3 seconds. Recovery mode does not work, or at least the phone keeps flashing the logo. Download Mode, however, works and the phone stays turned on steady. Kies keeps saying connecting and Jodin3 keeps saying my phone isn't connected. I have tried all 4 ports and 3 separate usb cables. I don't have access to a Windows machine only an iMac. I'm not sure what is wrong. I'm going to try downloading odin to my mac to see if it will work. If all else fails, I plan on contacting Samsung to see if they will fix it seeing as it was purchased only 4 months ago. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. You will have to download one of the latest firmware of: HERE. I supose you don't know the CSC (country CODE) of your device. We don't know what firmware had your device either. Try to flash one of the newest for avoid active KNOX to 0x1 in future if you have to come back to one older firmware. Flash the firmware of the correct country if you know it ofc.
2. ODIN don't works in Mac.... use HEIMDALL. Lil guide: HERE

Hiya Buddy said:
I managed to go over a friend's house and use his windows machine. I got the correct file and used Odin and it said "PASS". Unfortunately, the Note 3 is still having the same problem with the splash logo flashing every three seconds. Not sure whats wrong. Could it be hardware related? The battery contacts on the phone are fine. I don't think there is anything wrong with the battery itself because download mode works just fine. It seems to start the phone up its having trouble getting past the initial splash screen. Safe mode is not working either. Looks like I might have to put in a call to Samsung for warranty repair.
Click to expand...
Click to collapse
Can you show the Odin screenshot? And also the full Odin log file?

UPDATE:
Vndnguyen; Sorry for the long wait as the past couple of weeks have been hectic with a family member in the hospital. Samsung Customer Support was obviously unhelpful but someone managed to find the true country of origin of my phone. They said (Samsung CS) based on IMEI it is from Taiwan. Now that I know the proper firmware I have downloaded the corresponding country version from Sam Mobile. Currently leaving Odin running to see if that does anything to fix it. Regardless, I will still post a screen shot and the log file.
P.S. It was confirmed the battery was not the problem, a Samsung Rep at a Best Buy store pulled out a battery from a working display Note 3 and used it in mine, but still no dice.

I tried the Taiwan firmware from Sam Mobile (N900ZSUENI3_N900OZSENI3_N900XXUENG1_HOME.tar.md5) but Odin reported fail. Even after 3 attempts it still reported fail. After contacting the third party seller via Amazon, they replied that the Note 3 was meant for Latin America. I picked one of the countries (Panama: N900UBUENJ2_N900UWAENJ2_N900UBUENG1_HOME.tar.md5) and Odin reported Pass! But it still keeps flashing at the boot screen.
This is the log for the Panama Firmware:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900UBUENJ2_N900UWAENJ2_N900UBUENG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
I'm not sure about "removed" because I left the Note 3 plugged in.
Here is the log for the Taiwan Firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUENI3_N900OZSENI3_N900XXUENG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> sboot.bin
<ID:0/004> cache.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is a screenshot of Odin. With the phone still plugged in to the computer.

Problems Flashing

T-Mo On5 Pro (I think lol
So I flashed pegasis and reborn. Turns out that they both have sound issues and the camera doesn't work on either.
So I tried to flash the recovery from one of the other threads, nothing.
Tried to reflash pagasis and reborn, nothing.
I can get to TWRP which is awesome but now even ODIN can't push anything.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At this point, I'm stuck and need a little bit of help (to at least go back to stock). Thanks!

I had this issue as well and what i did was use samsung kies to go back to stock since phone got semi-bricked and i could only enter download mode, since you have access to twrp you can try and flash the superstars rom which is stable and pretty much bug free

Echo_0408 said:
I had this issue as well and what i did was use samsung kies to go back to stock since phone got semi-bricked and i could only enter download mode, since you have access to twrp you can try and flash the superstars rom which is stable and pretty much bug free
Click to expand...
Click to collapse
Well, I guess I can grab Kies in the meantime.
Where did you grab the superstars ROM and the stock ROM? I just want to make sure camera and phone work lol.

Rom:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
Stock:
https://www.androidfilehost.com/?fid=24723757092307323
Remember that kies flashes the up to date stock rom so there's no need to download the stock one in my opinion

Echo_0408 said:
Rom:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
Stock:
https://www.androidfilehost.com/?fid=24723757092307323
Remember that kies flashes the up to date stock rom so there's no need to download the stock one in my opinion
Click to expand...
Click to collapse
Great now I have "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software" on the On5.
I have to grab that to fix it so I can use Kies? or do I just use that now? :crying:
EDIT: So I can still drop it into download mode. But Kies and Smart Switch recognize that something is getting added. What am I missing for recovery? ...
Also - SOS send halps!

I've also been there, place your On5 on download mode and go to kies, Tools, firmware upgrade and initialisation it will ask for device model and s/n (everything can be found behind the battery) oh and type everything in CAPS

Echo_0408 said:
I've also been there, place your On5 on download mode and go to kies, Tools, firmware upgrade and initialisation it will ask for device model and s/n (everything can be found behind the battery) oh and type everything in CAPS
Click to expand...
Click to collapse
Failed to run firmware update. Unknown Error Occurred. Thanks for you all your help in this matter. I think it might be dead. lol

I'm sorry friend but I have no idea to what to do next I've semi-bricked this phone more times than I can count and managed to bring it back to life every time, maybe it's the variant? I have the sm-g550t or t-mo variant..

Echo_0408 said:
I'm sorry friend but I have no idea to what to do next I've semi-bricked this phone more times than I can count and managed to bring it back to life every time, maybe it's the variant? I have the sm-g550t or t-mo variant..
Click to expand...
Click to collapse
Thanks for messaging back every time though It's the T-Mo version as well. I'm really at a loss at this point. Going to try one more time this weekend and see what I get. :cheers:
Oh man - I don't know what happened but it finally recovered. I think doing it at home made the difference. Thanks!