Related
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south.
Could I be flashing a bad file? Is the CWM.tar.md5 not the correct file to flash?
I've tried several different versions of both Odin and CWM. Is there something else that I have to do before this step? I've read a lot about the S4 being a pain to load custom roms onto.
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!
Your boot loader is locked. So, no custom recovery and kernel. The only working recovery we have is safestrap.
More info - http://forum.xda-developers.com/showthread.php?t=2616221
misterbreadcrum said:
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2!
Click to expand...
Click to collapse
I see this above but need more info... Are you completely stock right now?
You will NOT be able to Odin any CWM to this phone. See below for other brief info for you to look into for CWM/TWRPand how to install IF on MDB or MDL firmware. Or if MF3 Your ONLY OPTION is Safestrap and limited to TouchWiz based Roms.
If you are then when you go to Settings/More/About Phone what does your Baseband say? Does it end with MDB, MDL, MF3?
IF it ends with MDB or MDL the look up Casual Root with TWRP. This will allow you to flash ANY Roms.
IF it ends with MF3 Then look up Safestrap for MF3. This will allow you to flash Safestrap versions of Roms.
ALSO IF it is MF3 you might as well update to MK2 or NB1 then use their safestrap version for root
Sent fron I337 Red BadAss Themed ShoStock 7.0
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
DarkVamprism said:
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
Click to expand...
Click to collapse
just look for stock lollipop rom for your phone ( sammobile)/and flash with odin, just make sure to do a full wipe before flashing the stock rom
Thanks for the quick reply, will this allow me to get future updates? like hotfixes released and stuff? I saw somewhere that once you flash it does something to the kernal which makes updates possibly brick the phone.
Just factory reset the custom, then use ODIN to flash the Stock ROM
Flashing the stock ROM will allow OTA updates so long as you don't root or flash anything else custom like recovery - it needs to stay 100% stock for OTA
But you can still root, and each time an OTA arrives, grab the new ROM from sammobile dot com and use ODIN to flash it, that will update your phone, leaving everything in tact, all your data and images etc will be fine, only thing you'll need to do after updating is root the phone again
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
DarkVamprism said:
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
Click to expand...
Click to collapse
Try a UK firmware, the latest version BOE5 is in my sig link on MEGA, much faster than Sammobile
There is also samsung-updates dot com you can check out
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
DarkVamprism said:
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
Click to expand...
Click to collapse
Are you sure you had the phone in Download Mode?
Volume DOWN & HOME & POWER (Then volume up when asked)
And yes, disable Reactivation lock before flashing anything or you'll end up with major problems requiring a massive mess on to fix
Using ODIN 3.10.6 ?
think you need pitfiles with the rom
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
ad0dh67 said:
think you need pitfiles with the rom
Click to expand...
Click to collapse
Yea I was wondering the same
Try this OP
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Load it into the PIT section along with the ROM in the AP section together and try again
---------- Post added at 19:14 ---------- Previous post was at 19:12 ----------
DarkVamprism said:
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
Click to expand...
Click to collapse
Here's the latest ODIN
https://mega.co.nz/#!Exo3yADS!y7pFS5-9RVhp4vDxTRAQARAwkjyQAB_9mDZWfXkLqko
There is no pit section inside of Odin 3.10?
Edit: Nevermind I found it but it says not to use it unless im an engineer, how badly will this screw me up =\ Im kind of scared to.
DarkVamprism said:
There is no pit section inside of Odin 3.10?
Click to expand...
Click to collapse
There is on the lower left log / options / PIT section, although clicking that says to load it into the CSC section
Try using the PIT file with your 3.09 version of ODIN first as Im not sure where 3.10.6 wants the PIT file loaded into, it's not very clear
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
DarkVamprism said:
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
Click to expand...
Click to collapse
Put it in the PIT section
I'm just reading up on what 3.10.6 means with that engineer warning
Make sure you load the stock ROM into AP together with the PIT file in the PIT section before flashing
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
DarkVamprism said:
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
Click to expand...
Click to collapse
Are you running ODIN as Admin? (Right click > Run as Administrator)
Using a native PC running Windows? All Samsung drivers installed?
It almost sounds as if your bootloader is locked, but you managed to flash custom recovery and root right?
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
DarkVamprism said:
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
Click to expand...
Click to collapse
Looks like you need to grab the G900I ROM and PIT
I'd try with just the ROM first, hopefully ODIN saved you from bricking when it realised it was for the wrong model phone
Get the G900I ROM, stick it into ODIN like you originally tried, see how you go from there
EDIT - Now it makes sense why there was no Australian ROM for your G900F, there is for the G900I
Okay, good news is sam mobile had the correct firmware now that im using the correct model number(doh) and the phone still boots fine, will update when I have downloaded and tried it, thanks for sticking with me.
HI, when I try to install new firmware on my galaxy j5 with odin with pda and file pit for repartition, I got this errors:
<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> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010>
<ID:0/010>Re-Partition operazioni failed.
<OSM>All threads completed. (succeed 0 / fail 1)
Please, help me.
Seconded. Does anyone have a solution for this issue?
@Vincenzolt98 @Dionisis89
It's a custom PIT or stock one? From where you downloaded stock ROM?
When I flashed stock ROM I only had to put it at PDA ( AP for newer Odin versions). I think the repartition should be done automatically when is flashed stock ROM.
Try latest Odin version and also make sure that the PIT file is the correct one (can be for 8gb, 16gb for example).
I recommend you to use SamFirm program for downloading stock ROMs faster.
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 . Even if it's deprecated, it still works fine. The program is attached at attachments in that thread.
#Henkate said:
@Vincenzolt98 @Dionisis89
It's a custom PIT or stock one? From where you downloaded stock ROM?
When I flashed stock ROM I only had to put it at PDA ( AP for newer Odin versions). I think the repartition should be done automatically when is flashed stock ROM.
Try latest Odin version and also make sure that the PIT file is the correct one (can be for 8gb, 16gb for example).
I recommend you to use SamFirm program for downloading stock ROMs faster.
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 . Even if it's deprecated, it still works fine. The program is attached at attachments in that thread.
Click to expand...
Click to collapse
It should be the stock PIT. I don't remember where I downloaded it from but it appears to be the correct one. I don't know where the problem is.
The firmware corresponding to my J500FN's CSC is Austrian (ATO), so I downloaded it from that updato site.
The reason I went to find the PIT file in the first place is because flashing stock ROM via Odin failed. It showed this code (last 2 lines):
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
It had failed at this point, and I've tried flashing the 6.0.1 and 5.1.1 stock image, to no avail. Perhaps you have a solution for that instead?
Dionisis89 said:
It should be the stock PIT. I don't remember where I downloaded it from but it appears to be the correct one. I don't know where the problem is.
The firmware corresponding to my J500FN's CSC is Austrian (ATO), so I downloaded it from that updato site.
The reason I went to find the PIT file in the first place is because flashing stock ROM via Odin failed. It showed this code (last 2 lines):
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
It had failed at this point, and I've tried flashing the 6.0.1 and 5.1.1 stock image, to no avail. Perhaps you have a solution for that instead?
Click to expand...
Click to collapse
Regsrding hidden.img.ext4 error, try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
People confirmed that this video works, but here is a post/tip regarding that video: http://forum.xda-developers.com/showpost.php?p=69673728&postcount=10 .
#Henkate said:
Regsrding hidden.img.ext4 error, try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
People confirmed that this video works, but here is a post/tip regarding that video: http://forum.xda-developers.com/showpost.php?p=69673728&postcount=10 .
Click to expand...
Click to collapse
I've tried this method, but Odin shows me another error: MD5 error! binary is invalid .
And yes, I've tried removing the .md5 from the file name, but then Odin is stuck on file analysis forever. That happens on Odin v3.12. At version 3.11, it simply hangs after choosing that file. At version 3.09 (which also has the option of flashing a PIT file) it shows this:
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea of what I could do? Maybe the PIT file I used isn't correct, after all? Where should I download it from?
---------- Post added at 01:43 PM ---------- Previous post was at 01:28 PM ----------
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Dionisis89 said:
I've tried this method, but Odin shows me another error: MD5 error! binary is invalid .
And yes, I've tried removing the .md5 from the file name, but then Odin is stuck on file analysis forever. That happens on Odin v3.12. At version 3.11, it simply hangs after choosing that file. At version 3.09 (which also has the option of flashing a PIT file) it shows this:
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea of what I could do? Maybe the PIT file I used isn't correct, after all? Where should I download it from?
---------- Post added at 01:43 PM ---------- Previous post was at 01:28 PM ----------
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Click to expand...
Click to collapse
Did you try to flash it without PIT file?
Also, if you flashed TWRP before, then try to flash TWRP, then boot in TWRP recovery and wipe /system, /data, /cache and dalvik-cache. Then power off the phone, boot in download mode and try to flash again through Odin.
If you didn't flash TWRP before and you don't wanna lose warranty, then boot in stock recovery and wipe, but your internal memory will be wiped too.
I never used a PIT file when I flashed stock ROM.
EDIT:
Dionisis89 said:
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Click to expand...
Click to collapse
Oh. Nice
I'm glad I helped you.
#Henkate said:
Did you try to flash it without PIT file?
Also, if you flashed TWRP before, then try to flash TWRP, then boot in TWRP recovery and wipe /system, /data, /cache and dalvik-cache. Then power off the phone, boot in download mode and try to flash again through Odin.
If you didn't flash TWRP before and you don't wanna lose warranty, then boot in stock recovery and wipe, but your internal memory will be wiped too.
I never used a PIT file when I flashed stock ROM.
EDIT:
Oh. Nice
I'm glad I helped you.
Click to expand...
Click to collapse
I'm sorry I didn't try flashing the firmware you provided me with in the first place, thereby "making you" type more on an answer that has been answered (by my flashing the correct firmware). There is something else you might help me with, if you have the time. Why did you provide me with a link to the German firmware? I told you it had Austrian CSC. And yet the German firmware was the one that actually worked. How so? And something else. Which is the website that you sent that firmware from? You edited your post soon after you had posted the link.
Dionisis89 said:
I'm sorry I didn't try flashing the firmware you provided me with in the first place, thereby "making you" type more on an answer that has been answered (by my flashing the correct firmware). There is something else you might help me with, if you have the time. Why did you provide me with a link to the German firmware? I told you it had Austrian CSC. And yet the German firmware was the one that actually worked. How so? And something else. Which is the website that you sent that firmware from? You edited your post soon after you had posted the link.
Click to expand...
Click to collapse
Huh? I only gave you links with the YouTube video and SamFirm.
Oh wait, I think that maybe SamFirm downloaded latest available update. In SamFirm you can switch to manual mode and type there the region, PDA and CSC and you can download the firmware which you want.
#Henkate said:
Huh? I only gave you links with the YouTube video and SamFirm.
Oh wait, I think that maybe SamFirm downloaded latest available update. In SamFirm you can switch to manual mode and type there the region, PDA and CSC and you can download the firmware which you want.
Click to expand...
Click to collapse
I didn't use SamFirm to download the firmware file, of that I'm sure. Mostly because upon attempting, I failed. I had put SM-J500FN in model name and ATO in CSC, but SamFirm found nothing.
I think you had a link from Mediafire in your response to me and that's how I downloaded the firmware. Hell, I might be mistaken, since I searched through a ton of threads, including some at XDA, in order to find a solution. It's possible I saw the link at another user's post.
In any case, thank you very much, once again. You saved my phone from becoming a paperweight.
Dionisis89 said:
I didn't use SamFirm to download the firmware file, of that I'm sure. Mostly because upon attempting, I failed. I had put SM-J500FN in model name and ATO in CSC, but SamFirm found nothing.
I think you had a link from Mediafire in your response to me and that's how I downloaded the firmware. Hell, I might be mistaken, since I searched through a ton of threads, including some at XDA, in order to find a solution. It's possible I saw the link at another user's post.
In any case, thank you very much, once again. You saved my phone from becoming a paperweight.
Click to expand...
Click to collapse
Is this the link you talk about? http://www.mediafire.com/download/skldahurz12dick/DBT-J500FNXXU1AOI1-20151006173751.zip . If yes, it's the German stock ROM I've uploaded andmentioned it in my ROM thread at installation instructions I posted it only there. It's kinda old firmware, but always worked fine for me, didn't have any issues (it's the firmware which my phone came with).
You welcome! I'm glad I helped you!
Maybe the OP (first post) has same problem like you. He'll have to read
#Henkate said:
Is this the link you talk about? http://www.mediafire.com/download/skldahurz12dick/DBT-J500FNXXU1AOI1-20151006173751.zip . If yes, it's the German stock ROM I've uploaded andmentioned it in my ROM thread at installation instructions I posted it only there. It's kinda old firmware, but always worked fine for me, didn't have any issues (it's the firmware which my phone came with).
You welcome! I'm glad I helped you!
Maybe the OP (first post) has same problem like you. He'll have to read
Click to expand...
Click to collapse
Yes, yes, that's the one!
I doubt he still has the problem though, since the thread was created at the end of August. Nonetheless, other people who might face the same issue will be able to read this thread and extract useful information.
Hello, I have Canadian version of S7E which should be compatible with G935F but I'm getting pit error
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OEM/USB are both on in developer options, any ideas what's causing this or should I try a different firmware?
re: firmware flashing
HeavenlyFall said:
Hello, I have Canadian version of S7E which should be compatible with G935F but I'm getting pit error
OEM/USB are both on in developer options, any ideas what's causing this or should I try a different firmware?
Click to expand...
Click to collapse
When flashing any firmware in Odin do NOT checkmark the PIT option.
Make sure that the PIT option in Odin is NOT checked before flashing!
Good luck, have a great day!
Misterjunky said:
When flashing any firmware in Odin do NOT checkmark the PIT option.
Make sure that the PIT option in Odin is NOT checked before flashing!
Good luck, have a great day!
Click to expand...
Click to collapse
The only options checked is auto reboot and reset time tho
Since this is not working, is it possible to flash directly to a nougat rom if I'm on MM + rooted with TWRP?
re: flashing
HeavenlyFall said:
The only options checked is auto reboot and reset time tho
Since this is not working, is it possible to flash directly to a nougat rom if I'm on MM + rooted with TWRP?
Click to expand...
Click to collapse
Yes, if you are rooted and have twrp both sucessfully installed
simply go to: https://forum.xda-developers.com/s7-edge/development
There you will find many Nougat 7 custom roms.
I would suggest not to flash any of the unofficial
nougat 7 roms though, they are not complete and
have many bugs and other issues.
There are about 3-4 really good Nougat 7 roms in the above link
to choose from.
You won't need Odin to flash any of the custom roms and it's a lot
easier to flash. All the zip file custom roms are flashed via twrp.
Good luck, have a great day!
Hi, so i'd like to upgrade my AT&T GS7 G930A to the latest available version of android that's released, as i'm still on the nougat beta update from earlier this year that wasn't officially released(meaning i'm still only at security update's from january 2017), however, none of the odin files i've tried have worked (links will be below) it keeps getting stuck at "Initializing" and on my phone it keeps saying "Odin Protocol version error", so i was hoping you guys would be able to help me
https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168 (was going to OTA update after downgrading)
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930aucu4bqd4-5-18-2017-t3608909
and https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-android-n-offical-odin-package-t3567801
the version currently installed on my phone is G930AUCU4BQA4
You need to go completely back to stock in order to get back on nougat latest I suggest that you flash back to the pk1 marshmallow 6.0 and use the odin provided by Sam mobile
logoster said:
Hi, so i'd like to upgrade my AT&T GS7 G930A to the latest available version of android that's released, as i'm still on the nougat beta update from earlier this year that wasn't officially released(meaning i'm still only at security update's from january 2017), however, none of the odin files i've tried have worked (links will be below) it keeps getting stuck at "Initializing" and on my phone it keeps saying "Odin Protocol version error", so i was hoping you guys would be able to help me
https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168 (was going to OTA update after downgrading)
https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930aucu4bqd4-5-18-2017-t3608909
and https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-android-n-offical-odin-package-t3567801
the version currently installed on my phone is G930AUCU4BQA4
Click to expand...
Click to collapse
Just flash this firmware using Odin3_v3.12_PrinceComsy
muniz_ri said:
Just flash this firmware using Odin3_v3.12_PrinceComsy
Click to expand...
Click to collapse
Nope, now i get
Code:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
tlopez1973 said:
You need to go completely back to stock in order to get back on nougat latest I suggest that you flash back to the pk1 marshmallow 6.0 and use the odin provided by Sam mobile
Click to expand...
Click to collapse
how would i go about finding these files? as you can see by one of the links in my post, i already tried the PK1 firmware from here
From what I learned it always ends up being an Odin problem not going back just try different versions of Odin make sure your restart your phone when putting it in download mode
logoster said:
Nope, now i get
Code:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try just flashing the CSC file with that Odin version. It contains the .pit file to format your partitions. If that works you should then be able to flash all 4 files.
muniz_ri said:
Try just flashing the CSC file with that Odin version. It contains the .pit file to format your partitions. If that works you should then be able to flash all 4 files.
Click to expand...
Click to collapse
nope, same error, <ID:0/004> FAIL! Model dismatch fail
logoster said:
nope, same error, <ID:0/004> FAIL! Model dismatch fail
Click to expand...
Click to collapse
Try the reverse for kicks and giggles meaning try all other files except CSC.
muniz_ri said:
Try the reverse for kicks and giggles meaning try all other files except CSC.
Click to expand...
Click to collapse
<ID:0/004> FAIL! Model dismatch fail
tlopez1973 said:
From what I learned it always ends up being an Odin problem not going back just try different versions of Odin make sure your restart your phone when putting it in download mode
Click to expand...
Click to collapse
so do you have any links to both the PK1 files and odin that you know work? because i still have this problem, and everything i've tried just keeps giving me the same errors, either that odin protocol mismatch, or the model dismatch failure (and you also said try sammobile odin? i can't find it, and their website seems to insist that the G930A doesn't exist)
Sorry for bumping, but I'd really like to fix this