[Q] N900W8 Unable to downgrade to 4.3 - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello,
I recently flashed the odin file for the N900W8 (Canadian) Galaxy Note 3 to get Android 4.4 Kit Kat. The Canadian version of the phone I am using has an unlocked bootloader. I decided I want to downgrade and go back to 4.3 but whenever I try to flash the odin file for 4.3 I get this error:
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
It also says in download mode: Write Protection: Enable
Reactivation lock is also off.
I was just wondering if anyone else encountered this and found a way to downgrade successfully?
Thank you!

What was your previous os?

hey_joe said:
What was your previous os?
Click to expand...
Click to collapse
It was MJ4 android 4.3 on Bell, trying to use the odin file for it and odin will not flash it.

aly19 said:
It was MJ4 android 4.3 on Bell, trying to use the odin file for it and odin will not flash it.
Click to expand...
Click to collapse
You have to follow PART 1 of this guide to install the mexican 4.4.2 firmware. Only then will you be able to downgrade back to 4.3.

hey_joe said:
You have to follow PART 1 of this guide to install the mexican 4.4.2 firmware. Only then will you be able to downgrade back to 4.3.
Click to expand...
Click to collapse
I have tried that, unfortunately when I try to flash the bootloader portion I get the same error
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N900W8UBUCNA2_336994_REV03_user_low_noship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900W8UBUCNA2_336994_REV03_user_low_noship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

aly19 said:
I have tried that, unfortunately when I try to flash the bootloader portion I get the same error
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N900W8UBUCNA2_336994_REV03_user_low_noship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900W8UBUCNA2_336994_REV03_user_low_noship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I think because you updated directly to NB7 from 4.3, you're now stuck with the NB7 bootloader and can't downgrade to NA2 which makes you go back to 4.3. I suspect that if you had updated to 4.4.2 NA2 first then NB7, you probably will retain the NA2 bootloader which facilitates going back to 4.3. I could be wrong though.
---------- Post added at 08:53 PM ---------- Previous post was at 08:48 PM ----------
It's also possible that Samsung patched the NB7 release to prevent N900W8 from downgrading to 4.3.

hey_joe said:
You have to follow PART 1 of this guide to install the mexican 4.4.2 firmware. Only then will you be able to downgrade back to 4.3.
Click to expand...
Click to collapse
hey_joe said:
I think because you updated directly to NB7 from 4.3, you're now stuck with the NB7 bootloader and can't downgrade to NA2 which makes you go back to 4.3. I suspect that if you had updated to 4.4.2 NA2 first then NB7, you probably will retain the NA2 bootloader which facilitates going back to 4.3. I could be wrong though.
Click to expand...
Click to collapse
I suspect that is the case, thank you for your help though.
I was hoping since the Canadian version has an unlocked bootloader that the version could be downgraded at any time.

aly19 said:
I suspect that is the case, thank you for your help though.
I was hoping since the Canadian version has an unlocked bootloader that the version could be downgraded at any time.
Click to expand...
Click to collapse
I can go back to 4.3 because I'm still on NA2 bootloader but it's also possible that Samsung patched NB7 and that if I odin that on my phone it will be stuck on NB7 as well.

Related

[Q] At&t samsung galaxy s4 i337 not booting into os

Hello there! I recently had purchased a Samsung Galaxy s4. I did not really enjoy touchwiz. I really wanted Google Play Edition. Anyways, my phone is stuck in ODIN mode with a message saying "Downloading... Do not turn off target!" I know that you can enter download mode and hit cancel to boot. But, my issue is different. Listen. I got safestrap on my s4, and it worked perfectly. I backed up my phone and installed Google Play Edition on the STOCK slot. Turned out, Google Play Edition would not boot up so I went back into safestrap and added a new rom slot. Then I restored my firmware on that slot. I left the stock slot not working... Then I uninstalled safestrap at boot up, not thinking about the stock rom. THIS IS THE BIG MISTAKE. I then rebooted my phone, and I get odin with the error message. I can't get into recovery settings or safestrap of course. I am now stuck with no options on my phone. I try to go to download mode and hit cancel. This did not boot up my phone, only my Google Play Edition which was not working. Now I can't change my rom slot. All I want to do now is go back to touchwiz. I want to restore my phone, but how? I would really appreciate your help!
I was running android 4.3 jellybean on MF3 so I can't load TWRP.
AlwaysBeen said:
Hello there! I recently had purchased a Samsung Galaxy s4. I did not really enjoy touchwiz. I really wanted Google Play Edition. Anyways, my phone is stuck in ODIN mode with a message saying "Downloading... Do not turn off target!" I know that you can enter download mode and hit cancel to boot. But, my issue is different. Listen. I got safestrap on my s4, and it worked perfectly. I backed up my phone and installed Google Play Edition on the STOCK slot. Turned out, Google Play Edition would not boot up so I went back into safestrap and added a new rom slot. Then I restored my firmware on that slot. I left the stock slot not working... Then I uninstalled safestrap at boot up, not thinking about the stock rom. THIS IS THE BIG MISTAKE. I then rebooted my phone, and I get odin with the error message. I can't get into recovery settings or safestrap of course. I am now stuck with no options on my phone. I try to go to download mode and hit cancel. This did not boot up my phone, only my Google Play Edition which was not working. Now I can't change my rom slot. All I want to do now is go back to touchwiz. I want to restore my phone, but how? I would really appreciate your help!
I was running android 4.3 jellybean on MF3 so I can't load TWRP.
Click to expand...
Click to collapse
Download mf3 tar file http://forum.xda-developers.com/showthread.php?t=2504311
Run in odin, your phone should be back up and running.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Download mf3 tar file http://forum.xda-developers.com/showthread.php?t=2504311
Run in odin, your phone should be back up and running.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know why it is failing
AlwaysBeen said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I dont know why it is failing
Click to expand...
Click to collapse
I think you've got an incomplete flash somewhere. I don't know if this will work but try the mf3 emergency files then flash the tar file again. http://forum.xda-developers.com/showthread.php?t=2526964
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
I think you've got an incomplete flash somewhere. I don't know if this will work but try the mf3 emergency files then flash the tar file again. http://forum.xda-developers.com/showthread.php?t=2526964
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Which file do I exactly download from this link?
AlwaysBeen said:
Which file do I exactly download from this link?
Click to expand...
Click to collapse
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
bobbigbuns said:
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
Click to expand...
Click to collapse
I really appreciate the registering just to help me out! Do i load the pit file with the MF3 tars? Or before?
bobbigbuns said:
You need SGS-I337_16GB.pit. Run this in Odin and it will fix your issue.
And yes I registered just to answer your question.
http://forum.xda-developers.com/showthread.php?t=2404970
Click to expand...
Click to collapse
<ID:0/003> Removed!!
<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> 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)
It failed =( What can I do? My phone is showing in red text: SECURE CHECK FAIL : PIT
MY BOOTLOADER IS LOCKED, IT SAYS MY WRITE PROTECTION IS ENABLED
AlwaysBeen said:
<ID:0/003> Removed!!
<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> 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)
It failed =( What can I do? My phone is showing in red text: SECURE CHECK FAIL : PIT
MY BOOTLOADER IS LOCKED, IT SAYS MY WRITE PROTECTION IS ENABLED
Click to expand...
Click to collapse
Do you remember what bootloader you were on?
If you were on anything higher than MF3 you are wasting your time, as you cannot downgrade this far.
MK2 and up requires those specific Odin tars. Since the original post was in January I will assume you were on MK2 at that time.
See here: http://forum.xda-developers.com/showthread.php?t=2663545
Personally, I would just go with the NB1, since root is now out for us. Once you odin the NB1 file, grab the files needed to towelroot, root, install superuser.apk, install safestrap 3.72 and you will probably be back in business
Now... thus all said, I am having a nightmare myself... last night I was listening to music on my I337 NC1 stockly rooted, when all of a sudden it froze... so I pulled the battery (which was fully charged), put it back in, and now my phone won't power up.
Being the geek I am, I grabbed my original samsung udb cable and plugged it into my windows machine... lo-and-behold windows recognized it, but as a completely different device... Qualcom USB or something...
How can I get back to download mode? Or do I need a JTAG? :crying:
kevp75 said:
Do you remember what bootloader you were on?
If you were on anything higher than MF3 you are wasting your time, as you cannot downgrade this far.
MK2 and up requires those specific Odin tars. Since the original post was in January I will assume you were on MK2 at that time.
See here: http://forum.xda-developers.com/showthread.php?t=2663545
Personally, I would just go with the NB1, since root is now out for us. Once you odin the NB1 file, grab the files needed to towelroot, root, install superuser.apk, install safestrap 3.72 and you will probably be back in business
Now... thus all said, I am having a nightmare myself... last night I was listening to music on my I337 NC1 stockly rooted, when all of a sudden it froze... so I pulled the battery (which was fully charged), put it back in, and now my phone won't power up.
Being the geek I am, I grabbed my original samsung udb cable and plugged it into my windows machine... lo-and-behold windows recognized it, but as a completely different device... Qualcom USB or something...
How can I get back to download mode? Or do I need a JTAG? :crying:
Click to expand...
Click to collapse
Sorry to hear about your dilemma. I probably cant help, but why not try.
Question, what do you mean by stockly rooted NC1? Are using the NC1 stock rom but rooted, or are you using another rom? Did you root using the download method or the towel root? Just curious.
I take you have tried to get to download mode using these steps?
Power off the phone completely by removing its battery for 5 seconds.
Re-insert the battery back into its place.
Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.
MatthewPresley said:
Sorry to hear about your dilemma. I probably cant help, but why not try.
Question, what do you mean by stockly rooted NC1? Are using the NC1 stock rom but rooted, or are you using another rom? Did you root using the download method or the towel root? Just curious.
I take you have tried to get to download mode using these steps?
Power off the phone completely by removing its battery for 5 seconds.
Re-insert the battery back into its place.
Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.
Click to expand...
Click to collapse
yeah... tried all that.
Stock Rooted NC1 ROM
Sent from my A110 using Tapatalk

I9505 soft-bricked odin fails flashing roms

I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english
C4scade said:
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english
Click to expand...
Click to collapse
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Sorry for my bad english but
i also got the same error with odin :
aboot.mbn
FAIL! (Auth)
got no sound and got a black screen when calling mic also not working
flashing custom roms wont fix it any way to install stock i9505 rom without odin or kies ?
's it fixable any ideas ??
Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Man, i don't think that a nandroid backup can solve a binary error.. and yes, i checked the firmware md5, it's ok, it is from sammobile.com
I'd say if you've got aboot fail then your trying to flash older rom on a phone that's had newer rom on it aka Knox already.
Sent from my GT-I9505 using xda app-developers app
Flash the ''i9505 pit'' file on odin in pda. That will fix
DONE!!!
mr.biceps said:
Flash the ''i9505 pit'' file on odin in pda. That will fix
Click to expand...
Click to collapse
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
mgolejnik said:
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
Click to expand...
Click to collapse
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?
CarlM34 said:
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?
Click to expand...
Click to collapse
But I never wrote that I had installed version 4.3 / 4. This is the version which is installed this time: I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar after this I flash CF-Auto-Root-jflte-jfltexx-gti9505.tar and now it is rooted and it is KNOX (but not for long)
Maybe I made a mistake. If so, sorry
...
I MADE MISTAKE!!! I am so sorry for that!!!
I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar it is newest version it's 4.4.2!!! I am sorry again.
I'm Also Having a problem with my samsung s4 gt-i9505 (INS)
i was trying to flash my phone with 4 files of firmware with Odin3 v3.10.6
and while flashing i got this problem
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9500DDUHPE1_REV01_CL1856465_SIGNED.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ODD_I9500ODDHOJ1_CL5979820_QB6580299_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if you have any solution please reply

[ROM,TW] Darklord v2.2 Need XSE CSC

Hello,
I have SCL22 KDDI AU From Japan. Status of my phone is rooted and DarkLord V2.2 Rom installed noe.
My SIM Card not detected because when I install the ROM there is no XSE CSC. I try CSC Changer, Region Lock Away,
and others apk but none of it working.
Yesterday I try to flash SCL22KDUBND3_SCL22KDIBND3_KDI from odin 3.07 & 3.09, but FAIL.
<ID:0/024> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCL22KDUBND3_SCL22KDIBND3_SCL22KDUBND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/024> Odin v.3 engine (ID:24)..
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> sbl1.mbn
<ID:0/024> NAND Write Start!!
<ID:0/024> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Any idea friends? please help me...

Samsung Galaxy SM J727 perx [BOOST]

SAMSUNG GALAXY SM J727P - (BOOST MOBILE)
This thread is for the SM-J727P Boost Mobile is my carrier.
Update: 3/2018 (STILL UNDER CONSTRUCTION)
The new RA1 is just a security patch. I myself have already got root so no worries....
GET NEWEST ODIN RELEASE
Get yourself the latest version of Odin. (Head to odins page for best downloads)
Head over to TWRP'S HOME PAGE and download the latest version for your device. Also get MAGISK. I believe the latest is Magisk v16 is now the latest. Also will need the MAGISK LATEST APP (5.6.0 I think) -
(Put magisk on external sd)
HOW TO ROOT:
1. Download ODIN, TWRP, AND MAGISK.
2. FLASH LATEST TWRP RECOVERY WITH ODIN. MAKE SURE AUTO REBOOT, IS NOT CHECK.
3. Pull battery and boot into recovery.
4. Wipe cashe/dalvik and Flash Magisk.
5. CLICK DONT INSTALL if prompted AND reboot
I have downloaded a few magisk modules and to my surprise, they work pretty good so far....
Just got the RA1 update and I wanted to grab the update file and upload it here and make a backup but I'm not currently rooted. A little insight would be greatly appreciated. What's the easiest and best way to do this???

			
				
Please dont delete these spots. This is a spot for a future solution. Ty
Does anyone have the QI3 update they could post on here? Please help!!1
lancez666 said:
Does anyone have the QI3 update they could post on here? Please help!!1
Click to expand...
Click to collapse
If you didn't find it yet it's in guides news an Discussions in the thread galaxy J727P stock update you will find it there !
I found the J727PVPU2AQI3 update and am uploading it now
virgin mobile galaxy J727P
TeknoGodz said:
I found the J727PVPU2AQI3 update and am uploading it now
Click to expand...
Click to collapse
thank you ! an very cool !
peter couniaz said:
thank you ! an very cool !
Click to expand...
Click to collapse
J727PVPU2AQI3.rar
https://drive.google.com/open?id=0B0pnxQY-SNGETUdNcjhGT3REcGc
TeknoGodz said:
J727PVPU2AQI3.rar
Click to expand...
Click to collapse
ayy!! Just what I needed! Thank you sooo much! You're a life saver!
No problem man you're very welcome I needed it to get my phone out of boot loop so I paid for it from one those firmware sites, glad it was able to help you as well.
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
ashx's old root still works on the new AQI3 firmware by the way
Thank you a million for these links! I updated the thread!
TeknoGodz said:
J727PVPU2AQI3.rar
https://drive.google.com/open?id=0B0pnxQY-SNGETUdNcjhGT3REcGc
Click to expand...
Click to collapse
Thank you Thank you Thank you!!! Odin'ed it and worked first time. You saved my phone! You're the man! I am eternally grateful!
lancez666 said:
Thank you Thank you Thank you!!! Odin'ed it and worked first time. You saved my phone! You're the man! I am eternally grateful!
Click to expand...
Click to collapse
Np at ALL! I hope to start seeing more development. I have taken a break for a while. I can't wait to find a rooted QI3 stock deodexed for this device. I don't know how but I got Ubuntu and Virtual Box set up just can't figure it out..... anyone find a stock rooted QI3 that boots and works yet???
TeknoGodz said:
No problem man you're very welcome I needed it to get my phone out of boot loop so I paid for it from one those firmware sites, glad it was able to help you as well.
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
ashx's old root still works on the new AQI3 firmware by the way
Click to expand...
Click to collapse
You are the greatest bro!!!! Thank you s ooo much!!!! I really appreciate your willingness to help and share. I love this site. The developers to noobs...... everyone's here to help one another! Couldn't have a better group of people!
virgin j727p stuck in flashing stock rom
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<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!!
getting this error also saying #SW REV CHECK FAIL : [aboot] Fused 2 Binary 1
Plz help me anyone knock me fb.com/sahapartha15
parthaxda007 said:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<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!!
getting this error also saying #SW REV CHECK FAIL : [aboot] Fused 2 Binary 1
Plz help me anyone knock me fb.com/sahapartha15
Click to expand...
Click to collapse
I've had this happen to me and it ended up being the cord... Make sure you are using a genuine Samsung cord and if that's not available us one that is thick and has good connections and make sure its a data cable no just charging... this gave me hell for days until I randomly tried it again with a new cord. If the files your using are correct then restart your computer and change to a better cord and it should work. It did for me... if you need anything else or any other files let me know... I have almost everything for this phone since it came out and development started.
---------- Post added at 04:10 AM ---------- Previous post was at 04:09 AM ----------
TeknoGodz said:
No problem man you're very welcome I needed it to get my phone out of boot loop so I paid for it from one those firmware sites, glad it was able to help you as well.
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
ashx's old root still works on the new AQI3 firmware by the way
Click to expand...
Click to collapse
I have that old root process and files to btw if anyone needs em
Help pls
JeepinxJosh said:
I've had this happen to me and it ended up being the cord... Make sure you are using a genuine Samsung cord and if that's not available us one that is thick and has good connections and make sure its a data cable no just charging... this gave me hell for days until I randomly tried it again with a new cord. If the files your using are correct then restart your computer and change to a better cord and it should work. It did for me... if you need anything else or any other files let me know... I have almost everything for this phone since it came out and development started.
---------- Post added at 04:10 AM ---------- Previous post was at 04:09 AM ----------
I have that old root process and files to btw if anyone needs em
Click to expand...
Click to collapse
Im using a Samsung Original Cord and the same result as above, idk what to do...
<ID:0/010> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/010> Odin engine v(ID:3.1203)..
<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> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> aboot.mbn
<ID:0/010> sbl1.mbn
<ID:0/010> rpm.mbn
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Boost Mobile J727perx
and in the phone its says
SW REV CHECK FAIL: [about] Fused 3 > Binary 1
[1| eMMC write fail : ABOUT
before this i installed TWRP and lineage OS port for that phone.
RSDoTTo said:
Im using a Samsung Original Cord and the same result as above, idk what to do...
<ID:0/010> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/010> Odin engine v(ID:3.1203)..
<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> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> aboot.mbn
<ID:0/010> sbl1.mbn
<ID:0/010> rpm.mbn
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Boost Mobile J727perx
and in the phone its says
SW REV CHECK FAIL: [about] Fused 3 > Binary 1
[1| eMMC write fail : ABOUT
before this i installed TWRP and lineage OS port for that phone.
Click to expand...
Click to collapse
Try getting a different download of the firmware.... also your not using the pit file right? Your using the newest odin to? And are you running o din by shift clicking it and run as administrator?
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:35 AM ---------- Previous post was at 06:33 AM ----------
I can upload the files I used if that would help
Sent from my [device_name] using XDA-Developers Legacy app

Galaxy S7 FLAT Oreo firmware DOWNLOAD

Sammobile released S7 Flat 930F oreo firmware to DOWNLOAD Pls see here
https://www.sammobile.com/2018/05/03/you-can-now-download-the-first-galaxy-s7-oreo-firmware/
The lattest G930FXXU2ERE8 BTU firmware download
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU2ERE8/219215/
G930FXXU2ERD5 - Galaxy S7 SM-G930F BTU United Kingdom firmware Download here
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU2ERD5/217727/
ATTENTION: You need the latest version of Odin3 3.13.1. PLS see attachent
Reason: Samsung implemented lz4 compression on partition images and older versions do not support that. Thanks to mentioning. @LGaljo
I just uploaded it in google drive
https://forum.xda-developers.com/showpost.php?p=76408523&postcount=1365
Will this work for s7 flat dual sim?
nikkilku26 said:
Will this work for s7 flat dual sim?
Click to expand...
Click to collapse
yes!
Thank you!
I can't flash it via Odin, i select all the files, it starts but my phone reboots in 1 second and nothing happens, here is my log:
<ID:0/010> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/010> Odin engine v(ID:3.1101)..
<ID:0/010> File analysis..
<ID:0/010> skip file list for home binary
<ID:0/010> sboot.bin.lz4
<ID:0/010> param.bin.lz4
<ID:0/010> cm.bin.lz4
<ID:0/010> boot.img.lz4
<ID:0/010> recovery.img.lz4
<ID:0/010> system.img.lz4
<ID:0/010> modem.bin.lz4
<ID:0/010> modem_debug.bin.lz4
<ID:0/010> cache.img.lz4
<ID:0/010> hidden.img.lz4
<ID:0/010> Home Binary Download
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Added!!
alcides2 said:
I can't flash it via Odin, i select all the files, it starts but my phone reboots in 1 second and nothing happens, here is my log:
<ID:0/010> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/010> Odin engine v(ID:3.1101)..
<ID:0/010> File analysis..
<ID:0/010> skip file list for home binary
<ID:0/010> sboot.bin.lz4
<ID:0/010> param.bin.lz4
<ID:0/010> cm.bin.lz4
<ID:0/010> boot.img.lz4
<ID:0/010> recovery.img.lz4
<ID:0/010> system.img.lz4
<ID:0/010> modem.bin.lz4
<ID:0/010> modem_debug.bin.lz4
<ID:0/010> cache.img.lz4
<ID:0/010> hidden.img.lz4
<ID:0/010> Home Binary Download
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Added!!
Click to expand...
Click to collapse
Make sure you're using the latest version of ODIN, which is 3.13.1 and updated for the Oreo 8.0 firmware
Dashkaa said:
Sammobile released S7 Flat 930F oreo firmware to DOWNLOAD Pls see here
https://www.sammobile.com/2018/05/03/you-can-now-download-the-first-galaxy-s7-oreo-firmware/
G930FXXU2ERD5 - Galaxy S7 SM-G930F BTU United Kingdom firmware Download here
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXU2ERD5/217727/
Click to expand...
Click to collapse
Please mention that you need latest version of Odin3 3.13.1. Thanks
Reason: Samsung implemented lz4 compression on partition images and older versions do not support that.
The old SamFirm downloader (v. 0.3.6) is still working.
It's much faster than sammobile without premium account and you can even download as binary...
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
I have few stupid questions? Noob
1. Will I trigger knox after installing this?
2. Will I lose all my data ?
3. I'm on AUT csc? What happens when I switch to BTU csc ?
h4xx0rr said:
I have few stupid questions? Noob
1. Will I trigger knox after installing this?
2. Will I lose all my data ?
3. I'm on AUT csc? What happens when I switch to BTU csc ?
Click to expand...
Click to collapse
1. No, you won't, if you install an official ROM.
2. No, but I propose to make a clean install and wipe. (sava data before)
3. CSC is OXA, not BTU. OXA is an international CSC.
Athanatos81 said:
1. No, you won't, if you install an official ROM.
2. No, but I propose to make a clean install and wipe. (sava data before)
3. CSC is OXA, not BTU. OXA is an international CSC.
Click to expand...
Click to collapse
OXA is not a CSC, CSC is BTU but also a Multi-CSC so includes many other CSCs, if your phone was originally one of them, such as XEU, it will default to that CSC, otherwise it should flash BTU
h4xx0rr said:
I have few stupid questions? Noob
1. Will I trigger knox after installing this?
2. Will I lose all my data ?
3. I'm on AUT csc? What happens when I switch to BTU csc ?
Click to expand...
Click to collapse
1) No
2) No but make a backup of the content of the internal memory just in case anything goes south.
3) If AUT is not in the list of BTU (which is a MULTI-CSC) then you should flash using the BL+AP+CP+CSC (instead of HOME_CSC) and that will factory reset your phone. If AUT is included in the BTU csc list then use the HOME_CSC file instead.
Sent from my SM-G930F using Tapatalk
Before flashing, do we have to ACTIVATE PIN in "Secure startup" ???
Flashing with latest odin 3.13.1 I end up stuck on the S7 bootscreen (not even the bootloop). First boot gets into samsung recovery, second reboot just gets stuck on the flash screen.
Also, if I try this and want to return to Android 7, its it possible to downgrade?
Is this global version? i mean if this unlock one? I am from Israel if i am will install it, This will work fine?
forcedv said:
Before flashing, do we have to ACTIVATE PIN in "Secure startup" ???
Click to expand...
Click to collapse
I didn't, but I had PIN & Fingerprint set for lockscreen
Worked on my SM-G930F ZTO - Brazilian using Odin3 v3.13.1
Previous version:
G930FXXU1DQE5
Android 7.0
Odin log:
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> modem_debug.bin
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4065 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
Updating with Odin don't affected my files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone in North America tried this firmware?
I am having the worst luck as of late- any firmware I have tried to flash since I reverted to vanilla N refused to flash. (vanilla AT&T BRA1 was successful). I am trying to either revert to my normal home ROM (T-M BRA1 or later) or (if possible) the UK Oreo. I am trying to find out why the spate of failures is happening.
Hence my questions.
1. Is this indeed for S7 Snapdragon (as opposed to Exnyos)?
2. If it is for Snapdragon, has anyone been successful?
3. Has there been a problem specifically with T-M N firmware as of late?

Categories

Resources