Related
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line
UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:
Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
How is that going to take away the udc start?
I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.
Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:
Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.
ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.
re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.
I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick
Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...
Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.
Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?
For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.
sm-n900
sm-900 and pit
I've had many phones in the past and never had a problem flashing stock and custom on any of them, but i've run into a issue with my sisters J5 2016 that i cant sort out.
As far as i understand she did an OTA update, but it failed halfway. The phone turned off, then wouldn't reboot......thats when she gave to me.
I first tried to access recovery mode, but this was not working.
If you just try to power up normally, then you get the samsung screen, but with the error message in corner.
View attachment 4231349
Only mode working is download mode, but this has an error in the first line that i have never seen before (it actually starts my worry that the internal memory is damaged somehow)
View attachment 4231345
I tried a firmware (single file in the AP box), but failed on pit.
So tried a version of firmware with the 4 separate files, but same error messages, so retried with the separate .pit file included in the flash.....still no joy, same error messages.
View attachment 4231346 View attachment 4231347
I have searched Internet and xda, but can not find this fail, so hoping someone might have a solution, or a way i can prove the internal memory is damaged (maybe theres another piece of software that i can use)
meerameer said:
I've had many phones in the past and never had a problem flashing stock and custom on any of them, but i've run into a issue with my sisters J5 2016 that i cant sort out.
As far as i understand she did an OTA update, but it failed halfway. The phone turned off, then wouldn't reboot......thats when she gave to me.
I first tried to access recovery mode, but this was not working.
If you just try to power up normally, then you get the samsung screen, but with the error message in corner.
Only mode working is download mode, but this has an error in the first line that i have never seen before (it actually starts my worry that the internal memory is damaged somehow)
I tried a firmware (single file in the AP box), but failed on pit.
So tried a version of firmware with the 4 separate files, but same error messages, so retried with the separate .pit file included in the flash.....still no joy, same error messages.
I have searched Internet and xda, but can not find this fail, so hoping someone might have a solution, or a way i can prove the internal memory is damaged (maybe theres another piece of software that i can use)
Click to expand...
Click to collapse
Use Smart Switch. It will automatically download and restore anything needed even if that means a pit file. Give it a try using thr Emergency Recovery option.
Amarius1 said:
Use Smart Switch. It will automatically download and restore anything needed even if that means a pit file. Give it a try using thr Emergency Recovery option.
Click to expand...
Click to collapse
Thank you for trying to help, that is much appreciate, but maybe i didn't make it clear.
The only working option is the Download mode, the Recovery mode doesn't work, so Smart Switch cant connect/see the phone
meerameer said:
Thank you for trying to help, that is much appreciate, but maybe i didn't make it clear.
The only working option is the Download mode, the Recovery mode doesn't work, so Smart Switch cant connect/see the phone
Click to expand...
Click to collapse
Doesn't matter. Just enter your s/n of the phone found behind the battery in the Smart Switch menu saying "Emergency Recovery"
It doesn't specifically need to recognise it or show as connected. Just make sure ur in download mode with cable in and enter the emergency data in the bokes so Smart Switch can force download the stock firmware for your phone
Amarius1 said:
Doesn't matter. Just enter your s/n of the phone found behind the battery in the Smart Switch menu saying "Emergency Recovery"
It doesn't specifically need to recognise it or show as connected. Just make sure ur in download mode with cable in and enter the emergency data in the bokes so Smart Switch can force download the stock firmware for your phone
Click to expand...
Click to collapse
Unfortuantly it was a fail.
Smart Switch downloaded the firmware, but could not install it and displayed a user friendly "Unknown Mode" message (i did check by plugging into odin without switching the phone off and odin showed it was in download mode).
The last message on phone screen reads "mmc: mmc_read fail" (this appeared when Switch came up with its fail message)
Just for clarity I tried all the above multiple times with different leads, and even different laptops and have upgraded my own phone without issues earlier .....so i am near admitting defeat with this J5 6
I do have to say again, thanks for suggesting and helping
meerameer said:
Unfortuantly it was a fail.
Smart Switch downloaded the firmware, but could not install it and displayed a user friendly "Unknown Mode" message (i did check by plugging into odin without switching the phone off and odin showed it was in download mode).
The last message on phone screen reads "mmc: mmc_read fail" (this appeared when Switch came up with its fail message)
Just for clarity I tried all the above multiple times with different leads, and even different laptops and have upgraded my own phone without issues earlier .....so i am near admitting defeat with this J5 6
I do have to say again, thanks for suggesting and helping
Click to expand...
Click to collapse
i dont know my answer will help or not. but i have met some older samsung phones with error in mmc. mmc is a hardware, so if you want to fix you have to change the mmc. maybe you can search for information about mmc on google to make sure.
by the way, why dont you go to service center? your waranty still 0x0
yea like mfmuam mentioned, take it to service centre and most likely they will change your motherboard. If your warranty is unexpired it will be totally free.
mfmuam said:
i dont know my answer will help or not. but i have met some older samsung phones with error in mmc. mmc is a hardware, so if you want to fix you have to change the mmc. maybe you can search for information about mmc on google to make sure.
by the way, why dont you go to service center? your waranty still 0x0
Click to expand...
Click to collapse
Unfortuantly her warrenty expired about 3 weeks ago (almost like the phone knew it had to break away that date ), but yes i have considered hitting ebay and getting her another board. Shes on holiday at moment, so will have to wait to see what she wants to do....... Thanks for advise though :good:
check your android security patch level ( im now in may 1 2017 region XID ) and than you download stok rom same like security patch level in your phone and than flash with odin put in pda.
---------- Post added at 11:44 PM ---------- Previous post was at 11:29 PM ----------
now i've 3 stok rom with different sec patch lvel,if i flash the first stokrom odin says fail like your ss,and then i flash the second stokrom odin says fail too,now im flash the third stokrom and tarraaa its work,because what?the third stokrom i have sec patch lvel in May 1 2017 same like im using my phone now.
pls correct if i wrong
check patch lvl - setting - about device - softwre info
Doni Artjoe said:
check patch lvl - setting - about device - softwre info
Click to expand...
Click to collapse
LOL, how could he check it when there is no system
installed on the phone and the phone cant boot up?
@meerameer
Hello,
please dont give up.
But also please dont be a fool and try repair change motherboard
by yourself.
You could try to re-flash with Heimdall program at Linux-System.
But before you can try to flash in Windows with Odin 3.12 program again.
download the very first firmware rom from samdownloads (they have 4-part rom with pit file)
make sure your battery is at 80% minimum
take out the battery
wait 30 sec
press and hold only power button for 10 sec
put back battery
start phone in download mode with no keys but only usb jig insert
start odin 3.12 and prepare all files but take CSC_(your-code) (do not use the csc_home!), take option with reboot, and also re-partition
connect phone with pc and start odin flash
Another idea would be to flash some custom recovery only and do full wipe
there, and then let Smart Switch emergency repair the phone.
You also have still a chance to get it repaired by the Samsung Service,
for maybe just a small fee. Just write them some short lovely email.
franticfreddy said:
LOL, how could he check it when there is no system
installed on the phone and the phone cant boot up?
@meerameer
Hello,
please dont give up.
But also please dont be a fool and try repair change motherboard
by yourself.
You could try to re-flash with Heimdall program at Linux-System.
But before you can try to flash in Windows with Odin 3.12 program again.
download the very first firmware rom from samdownloads (they have 4-part rom with pit file)
make sure your battery is at 80% minimum
take out the battery
wait 30 sec
press and hold only power button for 10 sec
put back battery
start phone in download mode with no keys but only usb jig insert
start odin 3.12 and prepare all files but take CSC_(your-code) (do not use the csc_home!), take option with reboot, and also re-partition
connect phone with pc and start odin flash
Another idea would be to flash some custom recovery only and do full wipe
there, and then let Smart Switch emergency repair the phone.
You also have still a chance to get it repaired by the Samsung Service,
for maybe just a small fee. Just write them some short lovely email.
Click to expand...
Click to collapse
Thank you Mr Frantic for the nice clear instructions :good:
I actually spend all day fixing hardware on phones and laptops, but thats hardly the rocket science of software like you developers get into. I have done flashing etc since the days of my beloved ACE.
I followed you so far down to 7, as i don't have a separate csc, apart from the csc_home file and for all my searching for a UK separated file firmware i had no luck, only got the combined one
I have tried what you suggested, but am going to try again following you to the letter :highfive:
PS Custom Recovery wouldn't go on, failed on odin at the .pit and theres no recovery (as far as i can tell) on the phone, just displays the J5 6 first screen, with the addition of the info text you get when in Download Mode.
@meerameer
Hello,
you could also try firmware for another country like germany, as the chance is good
that there it will be possible to choose english language in setup.
Maybe you can try this german firmware with csc_dbt.
But you need to be registered to samdownloads and firmware zip has password for encrypt
but its written on the download site (its mostly samdownloads.de)
The csc_home will not erase the internal storage since there is normally no pit file in it.
Because you need to re-pit and format the phone completely, you must use any
csc_(any country) but not csc_home.
Maybe thats why Odin fail for you so many times, because you never got any csc part
with the pit file in it?
You can check the csc part file if there is a pit file in it, you can open csc file with 7-zip.
EDIT:
Anyways, i have attach now the single pit-file for the j5-2016 european version.
So now you can try flash your 4 firmware in Odin with this additional pit file.
In Odin you got the menu for repit, where you can select the pit-file
manually (there is a warning that pit from csc will be used, but since you dont
have any csc file with pit in it, you can give a try.)
Else you still have the option to use SamFirm download program, where
you can download the newest firmware with option in binary nature (that means 4-parts)
and there will be csc file with the pit file already in it,
so you can flash like you already did.
I hope that helps..
franticfreddy said:
@meerameer
Hello,
you could also try firmware for another country like germany, as the chance is good
that there it will be possible to choose english language in setup.
Maybe you can try this german firmware with csc_dbt.
But you need to be registered to samdownloads and firmware zip has password for encrypt
but its written on the download site (its mostly samdownloads.de)
The csc_home will not erase the internal storage since there is normally no pit file in it.
Because you need to re-pit and format the phone completely, you must use any
csc_(any country) but not csc_home.
Maybe thats why Odin fail for you so many times, because you never got any csc part
with the pit file in it?
You can check the csc part file if there is a pit file in it, you can open csc file with 7-zip.
EDIT:
Anyways, i have attach now the single pit-file for the j5-2016 european version.
So now you can try flash your 4 firmware in Odin with this additional pit file.
In Odin you got the menu for repit, where you can select the pit-file
manually (there is a warning that pit from csc will be used, but since you dont
have any csc file with pit in it, you can give a try.)
Else you still have the option to use SamFirm download program, where
you can download the newest firmware with option in binary nature (that means 4-parts)
and there will be csc file with the pit file already in it,
so you can flash like you already did.
I hope that helps..
Click to expand...
Click to collapse
Seems I was having a dumb moment earlier. :silly:
Yes I checked before and the csc contained "J5XNLTE_EUR_OPEN_HIDDEN220M.pit". Thanks for the pit file also, I have checked on file size and they are exactly the same .
I have been questioning myself wondering if had right pit for my model, but screen and sticker (under battery) all say J510FN and all the .pit files i have found are all exactly same file size.
In total I've tried two 4 file firmwares, and 3 single file ones from different regions and release dates. All stop on that pit error before it even gets into the essence of the firmware.
Can you think of any software that can test the mmc , something that might give a bigger hint to whether its a hardware issue?
Hello,
well there is the option to test the mmc with special equipment for experts.
But its difficult and requires knowledge.
Did you try another Odin version?
Maybe Odin 3.09 or 3.10.7 can flash the firmware.
In older version of Odin, only check option for re-pit.
Do not make auto-reboot.
Only check re-partition and f.reset-time.
Do not use BL.
Only use AP+CP+CSC+pit file
When flash is finished, take out battery and put back in,
and restart manually into download mode and flash again the single firmware file
in AP.
I think you have flashed a different firmware version which is not suitable for your pit file
with the 220M addition.
It is very important to use the corresponding firmware files.
Maybe you only use the provided pit file for flash (do not select anything in BL, etc),
just select the pit file in re-pit menu.
franticfreddy said:
Hello,
well there is the option to test the mmc with special equipment for experts.
But its difficult and requires knowledge.
Did you try another Odin version?
Maybe Odin 3.09 or 3.10.7 can flash the firmware.
In older version of Odin, only check option for re-pit.
Do not make auto-reboot.
Only check re-partition and f.reset-time.
Do not use BL.
Only use AP+CP+CSC+pit file
When flash is finished, take out battery and put back in,
and restart manually into download mode and flash again the single firmware file
in AP.
I think you have flashed a different firmware version which is not suitable for your pit file
with the 220M addition.
It is very important to use the corresponding firmware files.
Maybe you only use the provided pit file for flash (do not select anything in BL, etc),
just select the pit file in re-pit menu.
Click to expand...
Click to collapse
Ok tried this, but still no joy.
I think you are certainly correct about what you were saying about the 220m pit file, as that one on the phone screen gives the message "ERROR There is no pit binary".
The pit file you posted gives the error "SECURE CHECK FAIL : PIT"
But the only time i have seen a SECURE CHECK FAIL message before is when i have accidentally in past tried putting completely wrong firmware on a phone , does that fit with what you know ?
ADDITIONAL INFO
My sister told me last night she had in fact taken it to her local indepentant phone shop to see if they could repair, they had no luck.
So i dont know what they did to it in their attempts. I do now have to wonder if they badly failed and now the phone is confused to what pit it should have, hence errors on software that should have fixed it
I've checked with the imei and the serial to make sure I'm defiantly looking for right files (J510FN), also my sister had from new and its never had a replacement board etc.......so im sort of hitting a brick wall.
Seems only option is to drive the 50 miles to the city, where i know there is an authentic Samsung repair store and hand over my life saving for them to look at it and tell me what we already know
Hello,
its really weird, its hard to find out what went wrong with your phone..
Maybe the guys at the generic repair center did the final brick of it.
As you said with the pit file i provided you got another kind of error.
I think there was some mix in bootloader and pit files which were used
at begin error stage 1.
I seen some kind similar problem when people was cross-mixing the 4-part
firmware files (they wanted use older bootloader but newer modem and system
or vice versa).
As there is still shown the samsung official binary but custom system, it is
possible the guys at generic repair center did use Odin and checked the
nand erase all option which is never, never, never a good idea.
Try to flash with this Odin v3.10.7 version
I strongly recommend you get your firmware file with
the SamFirm downloader ,
where you can search for your model SM-J510FN with countrycode BTU,
and check option to download in binary nature , so you will get the 4 parts.
The program requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
Here and here.
If you have the firmware there is no need to extra select the pit file for
flashing since its in csc_btu integrated. Just check option repartition, f.reset time.
These files also get checksum, then the secure fail *should* not happen...
If not fail then after finish flash take out battery, wait, put back,
goto recovery and do factory reset..
Im running out of ideas.. , anyways good Luck .
franticfreddy said:
Hello,
its really weird, its hard to find out what went wrong with your phone..
Maybe the guys at the generic repair center did the final brick of it.
As you said with the pit file i provided you got another kind of error.
I think there was some mix in bootloader and pit files which were used
at begin error stage 1.
I seen some kind similar problem when people was cross-mixing the 4-part
firmware files (they wanted use older bootloader but newer modem and system
or vice versa).
As there is still shown the samsung official binary but custom system, it is
possible the guys at generic repair center did use Odin and checked the
nand erase all option which is never, never, never a good idea.
Try to flash with this Odin v3.10.7 version
I strongly recommend you get your firmware file with
the SamFirm downloader ,
where you can search for your model SM-J510FN with countrycode BTU,
and check option to download in binary nature , so you will get the 4 parts.
The program requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
Hereand here.
If you have the firmware there is no need to extra select the pit file for
flashing since its in csc_btu integrated. Just check option repartition, f.reset time.
These files also get checksum, then the secure fail *should* not happen...
If not fail then after finish flash take out battery, wait, put back,
goto recovery and do factory reset..
Im running out of ideas.. , anyways good Luck .
Click to expand...
Click to collapse
OK, I have a couple of hours free now, so will try this.
Just like to say again, thanks for all your suggestions, you have been more than helpful :fingers-crossed:
UPDATE
Tried what you suggested, but still no joy.
Tomorrow i need to go near the city, so going to take a detour and take phone to the Samsung Shop. I'll update you on what they have to say about it .
Thanks again
Sad to hear it didnt work
I just was about to say, try what I said but also select the same separate pit file in the pit menu.
Im pretty sure the "right" mix of the right pit file and the corresponding firmware files could
help. But theres so many versions to try and its hard to find especially older firmwares..
Best regards.
franticfreddy said:
Sad to hear it didnt work
I just was about to say, try what I said but also select the same separate pit file in the pit menu.
Im pretty sure the "right" mix of the right pit file and the corresponding firmware files could
help. But theres so many versions to try and its hard to find especially older firmwares..
Best regards.
Click to expand...
Click to collapse
***Final Update***
I managed to get the logic board checked by Samsung and the emmc was corrupted. They wanted £124 to fix it.... Which I declined, as I can a replacement board on ebay for around. £60.
Chances are that the fault was caused by when my sister took it to a local generic repair shop, and might have been ok if she has gone to a more reputable repair shop.
So my note to all is research your repair stores when you have a fault, as the cheapest doesn't always mean the best.
Hi guys,
As the title suggest i'm having trouble updating my phone & can't find threads directly relating to the issue i seem to be having.
When i try to update through the phone i get a message that states "The operating system on your device has been modified in an unauthorized way."
I do as the message suggest which asks me to update through kies but then kies makes me download the new app which says my phone is up to date even though i'm on 4.4.4.
As for the state of my phone, i bought it about a month ago sealed new, it's still stock & I've done nothing to it & tested to see if it's routed just in case & it seems not to be.
i'll list all the details to help any kind soul who wishes to help:
Model number - SM-G900f
Baseband version - G900FXXU1ANK3
Kernel version - 3.10.0-2413392 - [email protected] #1 - Fri Nov 14 22:19:34 KST 2014
Build number - KTU84P.G900FXXU1ANK3
Thanks for any help in adavance, if you need more information from me please let me know!
Drakmon said:
Hi guys,
As the title suggest i'm having trouble updating my phone & can't find threads directly relating to the issue i seem to be having.
When i try to update through the phone i get a message that states "The operating system on your device has been modified in an unauthorized way."
I do as the message suggest which asks me to update through kies but then kies makes me download the new app which says my phone is up to date even though i'm on 4.4.4.
As for the state of my phone, i bought it about a month ago sealed new, it's still stock & I've done nothing to it & tested to see if it's routed just in case & it seems not to be.
i'll list all the details to help any kind soul who wishes to help:
Model number - SM-G900f
Baseband version - G900FXXU1ANK3
Kernel version - 3.10.0-2413392 - [email protected] #1 - Fri Nov 14 22:19:34 KST 2014
Build number - KTU84P.G900FXXU1ANK3
Thanks for any help in adavance, if you need more information from me please let me know!
Click to expand...
Click to collapse
Download the latest version of the firmware for your device
Here's the UK version
https://rapidgator.net/file/2220550....galaxys5update.com/galaxy-s5-stock-firmware/
Download odin
https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Download and install the Samsung USB drivers if you haven't already done so
Put your phone into download mode (hold power button Vol down & home button)
Connect phone to PC via USB
Press Vol up to start connection
Open odin
In the AP section add the firmware tar (Unzip download to get tar image)
Press start
Once it's flashed & your phone has restarted (it may not fully boot but it doesn't matter) go to recovery mode (hold power button Vol up & home button) and do a data wipe/factory reset
Now your phone will fully boot
TheFixItMan said:
Download the latest version of the firmware for your device
Here's the UK version
https://rapidgator.net/file/2220550....galaxys5update.com/galaxy-s5-stock-firmware/
Download odin
https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Download and install the Samsung USB drivers if you haven't already done so
Put your phone into download mode (hold power button Vol down & home button)
Connect phone to PC via USB
Press Vol up to start connection
Open odin
In the AP section add the firmware tar (Unzip download to get tar image)
Press start
Once it's flashed & your phone has restarted (it may not fully boot but it doesn't matter) go to recovery mode (hold power button Vol up & home button) and do a data wipe/factory reset
Now your phone will fully boot
Click to expand...
Click to collapse
Thanks for the help!
do you know why it has to be done through Odin & it won't download by itself?
also do you have another link, this one is supremely slow & is there any way to keep the data that's currently on my phone?
Thanks again btw!
Drakmon said:
Thanks for the help!
do you know why it has to be done through Odin & it won't download by itself?
also do you have another link, this one is supremely slow & is there any way to keep the data that's currently on my phone?
Thanks again btw!
Click to expand...
Click to collapse
Most of the links you will find are really slow unless someone has uploaded it to their personal file storage & shared link
I would always advise to factory reset/wipe data after flashing firmware through odin
If you are rooted you can use titanium backup to backup app data but really most apps you don't need to
Things like contacts should be synced to your Gmail account but you can use an app to backup contacts & sms messages - just make sure you save the file to your pc or first & transfer it back & restore it after wipe
WhatsApp has its own backup via Google drive if you enable it
Anything else on internal storage (pictures music documents etc) just copy to pc
TheFixItMan said:
Most of the links you will find are really slow unless someone has uploaded it to their personal file storage & shared link
I would always advise to factory reset/wipe data after flashing firmware through odin
If you are rooted you can use titanium backup to backup app data but really most apps you don't need to
Things like contacts should be synced to your Gmail account but you can use an app to backup contacts & sms messages - just make sure you save the file to your pc or first & transfer it back & restore it after wipe
WhatsApp has its own backup via Google drive if you enable it
Anything else on internal storage (pictures music documents etc) just copy to pc
Click to expand...
Click to collapse
Hey there, quick update!
When i try & parse the update through Odin the process fails?
I noticed in download mode the "system status" is set to "custom" & when i checked into this, when my phone is on in the settings option in about phone my system status is "official".
could this be why it's failing? if so, any ideas how to fix this?
other maybe useful info is when it fails it says "system check fail : aboot" not sure if that gives any more info?
Also in download mode my phone thinks it's a SM-G901F?
Thanks in advance!
Drakmon said:
Hey there, quick update!
When i try & parse the update through Odin the process fails?
I noticed in download mode the "system status" is set to "custom" & when i checked into this, when my phone is on in the settings option in about phone my system status is "official".
could this be why it's failing? if so, any ideas how to fix this?
other maybe useful info is when it fails it says "system check fail : aboot" not sure if that gives any more info?
Also in download mode my phone thinks it's a SM-G901F?
Thanks in advance!
Click to expand...
Click to collapse
The system check will fail if you are trying to flash the wrong firmware
The sm g901f is the galaxy s5 plus so get that firmware for your country
If your device is actually something different get the correct firmware & the correct corresponding pit file & flash both with reparation device ticked
TheFixItMan said:
The system check will fail if you are trying to flash the wrong firmware
The sm g901f is the galaxy s5 plus so get that firmware for your country
If your device is actually something different get the correct firmware & the correct corresponding pit file & flash both with reparation device ticked
Click to expand...
Click to collapse
on my phone it's listed as a SM-G900F, this is the first reference I've ever seen to SM-G901F.
Is this not rather odd that my phone thinks it's an SM-G900F?
Drakmon said:
on my phone it's listed as a SM-G900F, this is the first reference I've ever seen to SM-G901F.
Is this not rather odd that my phone thinks it's an SM-G900F?
Click to expand...
Click to collapse
Not if you flashed a custom rom for a different variant
Anything displayed in about phone is mainly just displaying what is written in the build.prop of the rom/kernel/baseband you are using
Look in the area under where the battery sits - it will tell you what your device is
My guess is that if download mode displays your device as a g901f then that is what it is
TheFixItMan said:
Not if you flashed a custom rom for a different variant
Anything displayed in about phone is mainly just displaying what is written in the build.prop of the rom/kernel/baseband you are using
Look in the area under where the battery sits - it will tell you what your device is
My guess is that if download mode displays your device as a g901f then that is what it is
Click to expand...
Click to collapse
Sticker under the battery lists it as a SM-G900F, mobile is stock new & i bought it about a month or two ago. Not rooted or modified in anyway (at least by me).
I bought it thinking it was an SM-G900f, interesting that it may not be....
Drakmon said:
Sticker under the battery lists it as a SM-G900F, mobile is stock new & i bought it about a month or two ago. Not rooted or modified in anyway (at least by me).
I bought it thinking it was an SM-G900f, interesting that it may not be....
Click to expand...
Click to collapse
It's more likely then that incorrect firmware was flashed on it in the past
Find the correct 900f firmware with pit file & flash it with reparation ticked
TheFixItMan said:
It's more likely then that incorrect firmware was flashed on it in the past
Find the correct 900f firmware with pit file & flash it with reparation ticked
Click to expand...
Click to collapse
so is the sticker on the back the correct Model i should be targeting or is the download mode version my actual model?
Drakmon said:
so is the sticker on the back the correct Model i should be targeting or is the download mode version my actual model?
Click to expand...
Click to collapse
Highly unlikely the sticker has been altered
More likely someone flashed incorrect firmware on device
Find correct firmware (what the device actually is) and pit file (pit file must correspond to firmware) & tick reparation device
TheFixItMan said:
Highly unlikely the sticker has been altered
More likely someone flashed incorrect firmware on device
Find correct firmware (what the device actually is) and pit file (pit file must correspond to firmware) & tick reparation device
Click to expand...
Click to collapse
Thanks for all the help you're giving,
Is there any diagnostic programs that can tell me 100% what model my phone is actually supposed to be?
Half the stuff online says the download mode version is correct but there is this whole thread dedicated to someone in a very similar issue to that i'd like to avoid as it looks like it takes ages to fix: https://forum.xda-developers.com/galaxy-s5/help/samsung-galaxy-s5-sm-g900f-sm-g901f-t3400692/page4
Drakmon said:
Thanks for all the help you're giving,
Is there any diagnostic programs that can tell me 100% what model my phone is actually supposed to be?
Half the stuff online says the download mode version is correct but there is this whole thread dedicated to someone in a very similar issue to that i'd like to avoid as it looks like it takes ages to fix: https://forum.xda-developers.com/galaxy-s5/help/samsung-galaxy-s5-sm-g900f-sm-g901f-t3400692/page4
Click to expand...
Click to collapse
What country is the device from
Is it network locked? And what network is it on
I can give you a quick suggestion of firmware to try
TheFixItMan said:
What country is the device from
Is it network locked? And what network is it on
I can give you a quick suggestion of firmware to try
Click to expand...
Click to collapse
Here is a link to where i bought it from, just as an extra reference as they may have more info than what just i can tell you https://www.ebay.co.uk/itm/New-Factory-Unlocked-SAMSUNG-Galaxy-S5-G900F-Black-White-Blue-16GB-Android-Phone/253356954657?_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20160727114228%26meid%3D6f58bd4f7d0347f1b86e571ca200abc0%26pid%3D100290%26rk%3D1%26rkt%3D2%26mehot%3Dpp%26sd%3D253356954657%26itm%3D253356954657&_trksid=p2060778.c100290.m3507
It's an unlocked phone for us within the UK but it was shipped from Hong Kong if i remember correctly.
on a side note, i was looking into firmware versions, my phone is currently on 4.4.4 but there seems to be no version listed for that on SM-900F PDA lists but there is on SM-901F & one of the firmware updates is listed as G901FXXU1ANK3 & my PDA is G900FXXU1ANK3
Drakmon said:
Here is a link to where i bought it from, just as an extra reference as they may have more info than what just i can tell you https://www.ebay.co.uk/itm/New-Factory-Unlocked-SAMSUNG-Galaxy-S5-G900F-Black-White-Blue-16GB-Android-Phone/253356954657?_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20160727114228%26meid%3D6f58bd4f7d0347f1b86e571ca200abc0%26pid%3D100290%26rk%3D1%26rkt%3D2%26mehot%3Dpp%26sd%3D253356954657%26itm%3D253356954657&_trksid=p2060778.c100290.m3507
It's an unlocked phone for us within the UK but it was shipped from Hong Kong if i remember correctly.
on a side note, i was looking into firmware versions, my phone is currently on 4.4.4 but there seems to be no version listed for that on SM-900F PDA lists but there is on SM-901F & one of the firmware updates is listed as G901FXXU1ANK3 & my PDA is G900FXXU1ANK3
Click to expand...
Click to collapse
After g900f on the sticker does it have three letters after it?
---------- Post added at 06:15 PM ---------- Previous post was at 05:59 PM ----------
Drakmon said:
Here is a link to where i bought it from, just as an extra reference as they may have more info than what just i can tell you https://www.ebay.co.uk/itm/New-Factory-Unlocked-SAMSUNG-Galaxy-S5-G900F-Black-White-Blue-16GB-Android-Phone/253356954657?_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20160727114228%26meid%3D6f58bd4f7d0347f1b86e571ca200abc0%26pid%3D100290%26rk%3D1%26rkt%3D2%26mehot%3Dpp%26sd%3D253356954657%26itm%3D253356954657&_trksid=p2060778.c100290.m3507
It's an unlocked phone for us within the UK but it was shipped from Hong Kong if i remember correctly.
on a side note, i was looking into firmware versions, my phone is currently on 4.4.4 but there seems to be no version listed for that on SM-900F PDA lists but there is on SM-901F & one of the firmware updates is listed as G901FXXU1ANK3 & my PDA is G900FXXU1ANK3
Click to expand...
Click to collapse
Try this firmware
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/BTU/download/G900FXXU1CRA2/206701/
With this pit file tick reparation
https://drive.google.com/file/d/0BzyeAt2hy6XeM3g4SWhUaWtoVWM/view
TheFixItMan said:
After g900f on the sticker does it have three letters after it?
---------- Post added at 06:15 PM ---------- Previous post was at 05:59 PM ----------
Try this firmware
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/BTU/download/G900FXXU1CRA2/206701/
With this pit file tick reparation
https://drive.google.com/file/d/0BzyeAt2hy6XeM3g4SWhUaWtoVWM/view
Click to expand...
Click to collapse
I'll write out the whole thing:
Model: SM-G900F
SSN: -G900FGSMH
FCC ID: A3LSMG900F
Also on the case of the pit file - is that kind of interaction super advance? Odin gives me a warning when i go into that setting lol
Drakmon said:
I'll write out the whole thing:
Model: SM-G900F
SSN: -G900FGSMH
FCC ID: A3LSMG900F
Also on the case of the pit file - is that kind of interaction super advance? Odin gives me a warning when i go into that setting lol
Click to expand...
Click to collapse
Flashing pit files will reparation your device - although odin shouldn't do if it is the wrong files as with anything there's always a risk
Usually you wouldn't flash pit files as there's no need but as your phone isn't accepting firmware you may have to
If the above firmware doesn't work you can always try the 901f firmware (without the pit & don't tick repartition) it will only flash it if it passes verification test so no harm in trying
TheFixItMan said:
Flashing pit files will reparation your device - although odin shouldn't do if it is the wrong files as with anything there's always a risk
Usually you wouldn't flash pit files as there's no need but as your phone isn't accepting firmware you may have to
If the above firmware doesn't work you can always try the 901f firmware (without the pit & don't tick repartition) it will only flash it if it passes verification test so no harm in trying
Click to expand...
Click to collapse
The firmware listed above is the same as the original one we downloaded, i'll try it again with the pit file in place & let you know how it goes this time.
Drakmon said:
The firmware listed above is the same as the original one we downloaded, i'll try it again with the pit file in place & let you know how it goes this time.
Click to expand...
Click to collapse
it failed again.
Just for good measure, here are the odin logs:
<ID:0/004> 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/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2484 M
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thought they don't seem to say much
Though on the phone it listed the reason for failure due to PIT
This difficulty is noted specifically on the Galaxy Tab A6 10.1 (SM-T580 and the SM-T585)
After searching through XDA Forums for a solution, I, along with others are at a loss. This Custom binary blocked by frp lock is rather difficult and exibits 4 different ways of showing itself. All but one has basically the same symptoms, which are:
1. Startup goes to bootloop. One version displays Custom binary blocked by frp lock on the Logo Screen.
2. Download Mode is accessible, but not usable. Not accepting of official stock firmware. Also Custom binary blocked by frp lock shown here in another version.
3. Recovery mode inaccessable. Redirects to a screen similar to Download Mode. In upper left, Custom binary blocked by frp lock is displayed. (This one was my device. I solved issue by flashing "Binary 4 FRP Unlock" via Odin. Others could not solve issue).
4. Same symptoms as 1 and 2. However Recovery mode was accessable, not usable. Custom binary blocked by frp lock also present.
I've tried everything I can find on it. Downgrade, flash Binaries 3 and Binaries 4. Flash TWRP, Flash stock firmware. OEM Unlock, 3 files, 4 files, repair files. Nothing seems to work.
Does anyone familiar with this have any good ideas that I haven't used or thought of? This ones got me baffled!
Solution for some, not all.
Casper Young said:
This difficulty is noted specifically on the Galaxy Tab A6 10.1 (SM-T580 and the SM-T585)
However I'm beginning to hear of it on other varients of the Tab A.
Here's the files most people that have a Galaxy Tab A SM-T580 or SM-T585. will need'
SM-T580 Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
SM-T580 U4 Binaries (this is a two pack. Flash 1 then flash 2 in the AP section)
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2.https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
For anyone that has symptoms 1,2 and 3. either one of the files I put here may work. After that you can flash the official firmware to your device. Flashing the binary files often reset the device. I have the 4 file for the T580 if anyone needs it.
Click to expand...
Click to collapse
I realize this is a bit old but I am at a loss with a t580.. I think I am confused at this point..I have odin and have replaced the .ini file with one you have listed. what happens next? I think I need a bit more instructions.. the other two files give a bad binary code...also you mention the 4 file for the t580.. nothing I find has 4 files.. only 3 ... no CP file. Thanks for any info..
cnicely said:
I realize this is a bit old but I am at a loss with a t580.. I think I am confused at this point..I have odin and have replaced the .ini file with one you have listed. what happens next? I think I need a bit more instructions.. the other two files give a bad binary code...also you mention the 4 file for the t580.. nothing I find has 4 files.. only 3 ... no CP file. Thanks for any info..
Click to expand...
Click to collapse
It may seem old but people are still having this difficulty and I seem to be the only one who bothers to investigate as well as try to help.
Tablets normally do not use the CP file which is for phone operations.
Here's my copy of the current 4file software. You'll notice it has two CSC files one labled HOME. You put one of in the CSC section of Odin3 when flashing. Which one depends on if you want to keep your application data or not. If you wish to keep your application data use the one labled "HOME"
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
Okay so you're stuck in some kind of Custom Binary FRP lock, can you define which of the 4 scenarios you are having?
Slightly of track, it seems this issue may come up with other and newer devices, so I'll tell you where the binary identifier of your device can be found. Our device currently has the firmware listed as T580UEU4CSC1. The U4 is the binary level of the bootloader I don't know what the U is for but the 4 represents the binary structure that has to be matched. Whatever binary number that may change to, it will always be in the same place.
The following two files are flashed one at a time. They are labeled somewhat use the one with a 1 first. Place it in the AP section on Odin3 and flash. You can either uncheck the reboot option or be prepared to go to download mode while the device reboots. by holding Power+Volume Down+ Home Button. Once back in Download mode place the second file in the AP section and flash. Be aware this method was used on another device than mine. It is one that came up during research and worked for someone I was assisting after the first method failed.
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
I can't currently locate my Combination or Repair files. It may be the first link I sent you. They should be listed with BL, AP and the two CSC files you only use one of. They go in their respective spaces and there isn't a CP file.
The file you mentioned as ini was not that when I first uploaded it and has somehow changed. It was a patched Odin3 that worked better for this issue so it looks like I have two files to locate in my vast file system that I'll put up here by tomorrow. The patched Odin3 and the U4 Binary Unlock. Meanwhile...
This is the file that got me out of Custom Binary FRP Lock. Place it in the AP section of Odin3 and flash. Right after that, reboot to Download Mode and flash in the 4 file.
https://drive.google.com/file/d/1Rip0qIGo-GbzFdH55s1vIpe6f1aqYKbD/view
Hopefully that works for you.
Hi, thanks for your post. Does it work also for the T585? It's exactly T585XXU2BQK5
ParadiseEagle87 said:
Hi, thanks for your post. Does it work also for the T585? It's exactly T585XXU2BQK5
Click to expand...
Click to collapse
The method works but the files here will not work for you because your device is using a binary 2. Although the T580 and the T585 are essentialy the same device yours can access the network and uses the CP file. I'll save you some time with this link. https://combinationfirmware.com/downloads/t585xxu2apl1/
Casper Young said:
The method works but the files here will not work for you because your device is using a binary 2. Although the T580 and the T585 are essentialy the same device yours can access the network and uses the CP file. I'll save you some time with this link. https://combinationfirmware.com/downloads/t585xxu2apl1/
Click to expand...
Click to collapse
Hi, thanks for the link but there is now "Download" button except for other versions like T585XXU2ARC2 and T585XXU2AQC1 but no download button for T585XXU2APL1
Thank you
Thank you for the reply. I will work on this early next week. Hopefully I can follow everything..from what I read I think I understand a bit more than I did. Thank you again for the effort you put in to help out those of us who are not "into" this on a regular basis.
Thank you
WHOHOO!!! I did it...not sure what I did but I did it. I tried both unlock files and the combination put me in factory binary mode.. I could check and test everything but didn't know what else to do.. If I remember correctly I then did the 4 files (again) and when it rebooted it came up without the FRP. but It appears to be running fine. Thanks to Casper Young for the time taken to help out...can't express enough my appreciation for the time and effort you gave.
ParadiseEagle87 said:
Hi, thanks for the link but there is now "Download" button except for other versions like T585XXU2ARC2 and T585XXU2AQC1 but no download button for T585XXU2APL1
Click to expand...
Click to collapse
Are you still having difficulties? Sorry I didn't respond sooner, I was on vacation. Let me know if you still need assisstance.
Thank Casper for this interesting post.
Do I understand you correctly, that this solution only helps to recover from a FRP lock situation and flash back the original firmware, but does not allow you to install a custom rom on the device?
Bass3rr said:
Thank Casper for this interesting post.
Do I understand you correctly, that this solution only helps to recover from a FRP lock situation
Click to expand...
Click to collapse
Maybe you do, maybe you don't. You would have to clarify what type of FRP you are experiencing. There are two types. The most commonly known FRP situation has to do with the Google Account Sign in. This is the one where the device can somewhat be accessed but only goes as far as the Google sign in page and you're stuck there because you don't have the proper password to get past it and into the device to use it.
No, this is not that kind of FRP!
This one has to do with when someone roots and/or flashes a corrupt or bad file into their Android and overloads the binaries (the operating system) and you can get stuck at various places but cannot use the device, flash a custom Rom or the Official software into the device and therefore it's rendered useless for the time being. It does not let you get to the sign in page. It does not let you use Recovery. It only seems to bootloop then shut down or stay on or locked on that screen. It does not seem to let you use Odin3 to flash files to return it to normal. And you'll get a red letter notice at the top of the screen saying "Custom Binaries Blocked by FRP Lock.".
Is that discriptive enough to answer your question?
Thanks for your reply Casper.
I was experiencing the second type (red letter notice).
After an earlier failed attempt and reading on this forum, I was aware of the requirement to delete the Google account prior to flashing. After ODIN flashing TWRP, custom Rom and no verity, i used my own Google account for testing . Everything seemed to work just fine. After I deleted my own Google account and installed my daughter's, I got the FRP lock upon the next reboot.
Am I still doing something wrong?
Hello, i have a T-585 in my hands, that has no recovery, no nothing. The only way i can boot up device is in Download mode, and in a blank blue screen ( i guess it is the same download mode, but without any text on screen, the background color is the same though). The problem is, i can't flash any rom on it, even stock rom, i get an error everytime. Newest rom won't flash through Odin (tried different versions), gives me error, if i try older rom, i get an error, it seems i need binary 6 to flash something. It has a FRP lock too. Don't really know what to do. If anyone has any ideas how to fix this, please help. I have been searching an trying to fix this 5 nights in a row, but no luck and no success.
Re-emrgence
mezablusa said:
Hello, i have a T-585 in my hands, that has no recovery, no nothing. The only way i can boot up device is in Download mode, and in a blank blue screen ( i guess it is the same download mode, but without any text on screen, the background color is the same though). The problem is, i can't flash any rom on it, even stock rom.
Click to expand...
Click to collapse
With the exception of the words written in red letters it sounds like you may have come to the right place. Well let's find out if you're somehow in Binary FRP Lock. Did you recently try to flash in a cutom ROM or Root firmware? As far as I'm aware the T580 and the T585 can use the same files but it's been a while and I'd have to check. Here's what it sounds like you're dealing with. Are you being redirected to a blue screen with nothing on it? Now that's odd because on mine I tried to go to Recovery Mode and got redirected to the Download mode screen which is light blue, however, mine had the words "Custom Binaries Blocked by FRP Lock" You not having it there is a first that I've heard. But so far I've noticed 5 or 6 different versions of this and only half have managed to correct the matter. Let's see. First your going to need the Odin3.13B Patched Downlader and let me see if I can find the files you may need, or at least lead you to them.
Odin3.13.1B,
https://drive.google.com/drive/folders/1YCiv190uj7Cu_Yu_2onmYe3kbaDduhbl
The current firmware for the T585 should be,
Build No. T585XXU6CSK1
So yes this would indicate your device is running the U6 Binaries. Here's a combination file you should be able to use.
https://drive.google.com/file/d/1cpWRqDUQZmUhE5xoKuyc4BptCWT7X9DQ/view
And then flash in the official stock firmware.
Casper Young said:
With the exception of the words written in red letters it sounds like you may have come to the right place. Well let's find out if you're somehow in Binary FRP Lock. Did you recently try to flash in a cutom ROM or Root firmware? As far as I'm aware the T580 and the T585 can use the same files but it's been a while and I'd have to check. Here's what it sounds like you're dealing with. Are you being redirected to a blue screen with nothing on it? Now that's odd because on mine I tried to go to Recovery Mode and got redirected to the Download mode screen which is light blue, however, mine had the words "Custom Binaries Blocked by FRP Lock" You not having it there is a first that I've heard. But so far I've noticed 5 or 6 different versions of this and only half have managed to correct the matter. Let's see. First your going to need the Odin3.13B Patched Downlader and let me see if I can find the files you may need, or at least lead you to them.
Odin3.13.1B,
https://drive.google.com/drive/folders/1YCiv190uj7Cu_Yu_2onmYe3kbaDduhbl
The current firmware for the T585 should be,
Build No. T585XXU6CSK1
So yes this would indicate your device is running the U6 Binaries. Here's a combination file you should be able to use.
https://drive.google.com/file/d/1cpWRqDUQZmUhE5xoKuyc4BptCWT7X9DQ/view
And then flash in the official stock firmware.
Click to expand...
Click to collapse
Hello, i've been away for a few days, thank you for the reply, i'll try to use files that You put out tomorow, and give You an update. If this works, You're a magician.
I didn't try to Root or flash custom rom on this tablet. A friend gave it to me because it had a cracked screen, so i could change it. Also it was left for sometime and wasn't used, so was completely discharged. I changed the screen and charged it, but it wouldn't boot up, so i thought it maybe had failed to update or something, tried to flash a Stock rom, but it wouldn't flash through Odin. Older ones give the binary error so i need a U6, tried different of those, but still no luck. At the end I even thought maybe that there may be some physical damage ( friends kid steped on it, that's how the screen got cracked), but doesn't look like it.
I have a minor problem downloading frp unlock. Google doesn't let me download it. Sorry, you can't view or download this file at this time. I guess i have to wait some time....
Ok, so i managed to download the zip file from GDrive, but there is a password on the archive. I can't extract files from the archive, it has a password.
Found the password under some Youtube video. Tried to flash the Combination with Odin, it failed. Here's the log from Odin.
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1366 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried adding a PIT file while flashing too, but i had the same result.
mezablusa said:
I have a minor problem downloading frp unlock. Google doesn't let me download it. Sorry, you can't view or download this file at this time. I guess i have to wait some time....
Ok, so i managed to download the zip file from GDrive, but there is a password on the archive. I can't extract files from the archive, it has a password.
Found the password under some Youtube video. Tried to flash the Combination with Odin, it failed. Here's the log from Odin.
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1366 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried adding a PIT file while flashing too, but i had the same result.
Click to expand...
Click to collapse
Are you certain that the firmware you are trying to flash is for your specific model number?
When you flash via Odin, disable the "re-partition" option in Odin.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Are you certain that the firmware you are trying to flash is for your specific model number?
When you flash via Odin, disable the "re-partition" option in Odin.
Click to expand...
Click to collapse
Yes, i'm certain. What other firmware could I flash on sm-t585? The only other firmware i could think of flashing would be for t580, but i didn't try to do that. I tried older version roms for t585, but i got an error on tablet screen because of binary 6.
So the only rom i can try to flash is the newest with U6, at least i don't get an error on tablet screen, but Odin still fails.
When I flash i have enabled only auto reboot and F.reset time. Re-partition option is disabled.
I'm kind of lost at this point...
mezablusa said:
Yes, i'm certain. What other firmware could I flash on sm-t585? The only other firmware i could think of flashing would be for t580, but i didn't try to do that. I tried older version roms for t585, but i got an error on tablet screen because of binary 6.
So the only rom i can try to flash is the newest with U6, at least i don't get an error on tablet screen, but Odin still fails.
When I flash i have enabled only auto reboot and F.reset time. Re-partition option is disabled.
I'm kind of lost at this point...
Click to expand...
Click to collapse
When you flash the U6 firmware and it fails, can you tell me if it gives you any specific errors ?
Can you tell me at which step in the flashing process it fails?
Have you tried using different versions of Odin?
Have you tried using a different PC?
Sent from my SM-S767VL using Tapatalk