Develop Bugs

[Q] Help Flashing Note 2 N7100 through Odin3

Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
Click to expand...
Click to collapse
I believe that if it is official 4.3 you cannot downgrade.

Is it a clone?
Sent from my GT-N7105 using xda app-developers app

thedadio said:
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?

New Droid said:
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
Click to expand...
Click to collapse
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck

tonylee000 said:
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
Click to expand...
Click to collapse
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic

New Droid said:
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
Click to expand...
Click to collapse
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.

....
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader

tonylee000 said:
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
Click to expand...
Click to collapse
I've installed the latest version of CWM Recovery Touch v6.0.4.1 and try to flash the CyanogenMod 10.1.3 to see if it woks.
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Right now I'm on my mobile. Can you send me the link to one post with that please. Thanks
Enviado do meu U9200 através de Tapatalk

The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Can the mk3 bootloader be downgraded? I wss under the impression that once upgraded to a mk bootloader you were stuck with it as theyre not downgradable

New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day

exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?

sora9009 said:
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
Click to expand...
Click to collapse
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:

exceptionalkhan said:
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
Click to expand...
Click to collapse
im pretty sure bootloader cannot be downgrade.

sora9009 said:
im pretty sure bootloader cannot be downgrade.
Click to expand...
Click to collapse
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.

exceptionalkhan said:
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
Click to expand...
Click to collapse
this is really a great news.Thanks

exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
Sorry man, for me didn't work :S It keeps giving the same error :S

Hi everyone. Finally i could flash the note 2 :victory: but i still dont get it why i cant flash through odin
This is how i do it.
1. Flash the ClockworkMod Recovery through.
2. Flash the TWRP 2.6 Recovery.zip through CWM Recovery. (Don't know i i cant flash this recovery directly on odin
3. Flash a CyanogenMod Nightly ROM
4. Install Odin Mobile.
5. Flash the lastest official rom by Samsung for Europe.
6.Yeh I have a official rom on my mobile :victory:
Now I have one problem, when i try to make a call i cant hear the people on the other side and vice versa. I know the mic and speaker are working, if o try to make a call through skype it works perfectly!
Obs.On every ROM i have this problem, on Stock ROMs by Samsung, Europe and Chinese Version and also on CyanogenMod.
When i try to flash the European ROM on Odin it fails when try to write the modem.bin.
I can flash the Chinese ROM without any problems on Odin.
I'm using the lastest ROM JB 4.3 from Samsung
What is the problem now?

The MSR firmware zip link no longer exists?
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse

MadR4sta said:
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
Click to expand...
Click to collapse
Ma Bad...
Bro! the thread is closed, will update that later.
An updated link is Here:https://my.pcloud.com/#page=publink&code=XZgADZWDMzsYh1Xa8uTeOaSPsb2VAn5tb7

[Q] AT&T SGH-I747 Soft Brick Need Help!!!

I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?

FuTuRisTiC Zo3 said:
I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?
Click to expand...
Click to collapse
Ok I Installed Insecure Boot img via odin3 and my phone rebooted but now instead of it booting at the 1 second samsung screen it goes past it to the galaxy s 3 screen and just sits there. i also installed twrp, it let me mount everything but i cant u adb to push anything and it says i have no os installed. i dont know what moves to make anymore someone please help me out!!!

What version of Android did you have on your phone when it last worked, stock or custom ROM?

dawgdoc said:
What version of Android did you have on your phone when it last worked, stock or custom ROM?
Click to expand...
Click to collapse
its was a stock android rom i believe im not sure what version though.

Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time

lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
yes im able to go into download and recovery mode

lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
oops didnt fully read your 1st post

lemngo02 said:
oops didnt fully read your 1st post
Click to expand...
Click to collapse
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices

If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?

FuTuRisTiC Zo3 said:
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices
Click to expand...
Click to collapse
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.

dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
ok, not to jack his thread, but what if you are on the 4.3 bootloader? i didnt do what he did, but i am stuck in a similar situation. I am on the 4.3 bootloader, but i do have a custom recovery installed. problem is i get an error when i try to wipe. Ive tried flashing stock 4.3 rom via sideload in stock recovery, and modified rom though twrp. both roms install fine, but dont boot, but they do freeze in different points so i know something is being flashed. ive also tried wiping in cwm and stock. im bout ready to flash anything to this phone. oh and a nandroid restore fails after boot img flashes.

FuTuRisTiC Zo3 said:
its was a stock android rom i believe im not sure what version though.
Click to expand...
Click to collapse
From your message, you likely were on stock 4.3. Since you are able to get into recovery and download modes, you may try a restore via custom recovery. Please see the thread below on how to install custom recovery and do a stock restore ...
<http://forum.xda-developers.com/showthread.php?t=2658486>

fastludeh22 said:
ok, not to jack his thread, but what if you are on the 4.3 bootloader? I am on the 4.3 bootloader, but i do have a custom recovery installed.
Click to expand...
Click to collapse
I would then link you to the same thread Larry2999 provided.

dawgdoc said:
I would then link you to the same thread Larry2999 provided.
Click to expand...
Click to collapse
thanks. i had found that thread right after i posted. lets hope. its halfway downloaded. if that doesnt work,ill be posting a thread about the weird way i ended up here and detailed report of what i did and what ive tried...

dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
audit13 said:
If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?
Click to expand...
Click to collapse
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do

never mind folks i got it up and running my only option was to use the sd card so i found my adapter and fixed it. im on 4.1.2 now its updating software now im guessing to 4.3. thank you guys for all the help

FuTuRisTiC Zo3 said:
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do
Click to expand...
Click to collapse
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.

dawgdoc said:
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.
Click to expand...
Click to collapse
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else

FuTuRisTiC Zo3 said:
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else
Click to expand...
Click to collapse
There is a chance that being rooted will prevent you from using the OTA official update. I've seen reports of people being able to update to the official 4.3 while rooted, but I've also seen reports of people not being able to update.
Before you make that update, bear in mind that the official 4.3 bootloader, its name ends in MJB, is the one that will prevent you from ever going back to an older bootloader. Some of the devs and the more experienced on here have no problem with that. Others do consider it an issue. An alternative is to install the leaked 4.3 bootloader, it's name ends in MJ2. That bootloader will allow you to downgrade to the 4.1.1 or 4.1.2 bootloaders, or so I have read. There is information about this in the development and the general forums for our device.
To muddy the waters more; if you intend to sim unlock your device without gettings codes from your carrier you need to do it from the 4.1.1 official ROM. A point you can not return to from the official 4.3 ROM, or so I've read.

I am having a huge booting issue with my Samsung Galaxy S3. Its a brand new one and I tried rooting it but it gave me this error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get to download mode, but not recovery nor does it boot into the Android OS. I tried putting back the stock OS and it gave me this error:
<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> aboot.mbn
<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)
I've tried follow a bunch of these threads, but I can't seem to resolve my issue yet. I probably have that 4.3 bootloader which screwed everything up. Can someone help me resolve my issue? I literally got this phone today from AT&T. Thank you.

Can't return back to stock ROM

Hello, could please someone help me with this terrible problem? I have Galaxy S4 mini (i9195 LTE version). I flashed clockwork recovery, make a root and install CyanogenMod 11 (everything works fine). But I need to complaint this device back to the shop, because it has problems with random restarts (and I was thinking than maybe a flashing of custom ROM can help, but no). But when I connect device to the PC with Odin (3.09, but I tried 3.07 and others), select original ROM (which I downloaded from sammobile) and click Start, process fails after few seconds (I tried all of USB ports on my laptop and I tried same steps on my second PC), but with no success
Here is the log from ODIN:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUBML4_I9195TMZBML1_I9195XXUBML4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the screen of my phone I see this:
ODIN MODE
Model: gt-i9195
Current binary: custom
System status: official
Knox kernel lock: 0x0
Know warranty void: 0x1
CSB-config-LSB: 0x30
Bootloader ap swrev: 2
Write protection: enable
SW REV CHECK FAIL: Fused 2 > Binary 1
And I am trying to flash this ROM:
Model: GT-I9195
Model name: GALAXY S4 mini LTE
Country: Germany (T-Mobile)
Version: Android 4.2.2
Changelist: 2340422
Build date: Fri, 20 Dec 2013 16:46:00 +0000
Product Code: TMZ
PDA: I9195XXUBML4
CSC: I9195TMZBML1
MODEM: I9195XXUBML4
Can someone tell me why I can't return back to stock ROM?

jerrry said:
[SNIP]
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)[/CODE]
[SNIP]
Click to expand...
Click to collapse
See that "Auth" there? Have you allowed access to your phone via USB? First thing that comes to mind for me.

Because you have latest knox bootloader. Do you see that line ""bootloader ap swrev : 2"" in your download mode.....that indicates it.
So this means you cannot downgrade to jellybean roms. Do not try to downgrade because repeated failures of odin might brick your device.
The mbn files odin flashes are all related to bootloader and corrupted bootloader = hard brick.
If you are desperate for jellybean flash the brazil ububne2 for I9195. Only that JB works. Good luck.

ericlnu: Thank you for reply. Did you mean USB debugging in phone settings menu? But I can't boot into system because the last flash causes FAIL message and I can only access to bootloader or download mode.
sasank360: Thank you very much for your support. I didn't know that. So you mean than I need to download Brazil ROM for i9195 (ububne2), which will only works? (and after that I can update to 4.4.2)? Or what Can I do after flashing ububne2 ROM if I need back original stock ROM from my operator?

jerrry said:
ericlnu: Thank you for reply. Did you mean USB debugging in phone settings menu? But I can't boot into system because the last flash causes FAIL message and I can only access to bootloader or download mode.
sasank360: Thank you very much for your support. I didn't know that. So you mean than I need to download Brazil ROM for i9195 (ububne2), which will only works? (and after that I can update to 4.4.2)? Or what Can I do after flashing ububne2 ROM if I need back original stock ROM from my operator?
Click to expand...
Click to collapse
You cannot go back any further. Jellybean ububne2 is the latest jb rom and only that works. Ofcourse you can flash any stock kitkat firmware if you wish. Good luck.

Thank you. I flashed ububne2 ROM to my Galaxy S4 mini and finally, ODIN didn't fails (and phone si working). But when I try to flash latest KitKat ROM (from my operator or any Jelly Bean ROM for my region), ODIN again fails with flashing. Ububne2 is right now the one and only ROM which I can flash to my device.

jerrry said:
Thank you. I flashed ububne2 ROM to my Galaxy S4 mini and finally, ODIN didn't fails (and phone si working). But when I try to flash latest KitKat ROM (from my operator or any Jelly Bean ROM for my region), ODIN again fails with flashing. Ububne2 is right now the one and only ROM which I can flash to my device.
Click to expand...
Click to collapse
Try the knox free kk rom. worked fine for me. knox tripped and running cm11.

kev23m: You mean any unnoficial ROM? This is not sollution for me (I already tried CM11 ROM), but due to random restarts (which is probably hw problem) I need return back stock ROM and complaint device with my seller/shop (as a part of warranty issue).

jerrry said:
kev23m: You mean any unnoficial ROM? This is not sollution for me (I already tried CM11 ROM), but due to random restarts (which is probably hw problem) I need return back stock ROM and complaint device with my seller/shop (as a part of warranty issue).
Click to expand...
Click to collapse
It is the stock rom , knox bootloader removed so people can update without knox. Thanks to SilviuMik
Click Here

oh, I see. But this ROM is only for Galaxy S4 Mini Duos, I have classic LTE version (i9195).

jerrry said:
oh, I see. But this ROM is only for Galaxy S4 Mini Duos, I have classic LTE version (i9195).
Click to expand...
Click to collapse
oops. I think i read somewhere he got a request for 9195 too, maybe he has prepared it. Just do a search and see.
See this

need to reprogram as the phone stuck at Samsung Galaxy S III

My phone got crashed which can't bootup. The phone always stayed with Official release, never rooted. I am not sure which version has been upgraded to, now it stuck with Galaxy S 3 screen, only thing I know it has the SecureLinux enabled, so it must be either 4.3 or 4.4. I wanted to reprogram to the official firmware, but not sure if I reprogram to the wrong version, would that causes any problem?
Please help.

additional infomation:
at download mode:
PRODUCT nAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE

Does this download menu look like 4.2?
Or it is 4.3 , I dont see warrenty flag.
Thanks.

No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.

audit13 said:
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
Click to expand...
Click to collapse
The phone is T999 for T-mobile, but seems there is one time only that it had official release of 4.2.1 or 4.2.2 available. I am not sure if I should flash the 4.1.2 or 4.2.1 back. But I seem can't find the 4.2.1 or 4.2.2 firmware on line anymore.
Question is that if I try to flash 4.1.2 to the phone, would it cause any problem if it was in 4.2.1?
Thanks all, I know this probably an old issue.

Flashing 4.1.1 or 4.1.2 should be fine.

audit13 said:
Flashing 4.1.1 or 4.1.2 should be fine.
Click to expand...
Click to collapse
###Right now I can't go to recovery mode, so I am trying to program the stock recovery, but failed. When I tried to odin the stock 4.1.2 it failed too. Here is the error during flashing stock recovery.
<ID:0/008> Added!!
<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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried different USB cables? Different USB ports? The rom cam from sammobile.com?

audit13 said:
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
Click to expand...
Click to collapse
Here is the error msg:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)

It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.

audit13 said:
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
Click to expand...
Click to collapse
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3?

You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.

thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3? All I want is just get the phone back. I tried to load 4.3 bootloader, but it failed.

audit13 said:
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
There is possibility that the pit is wrong, I tried to load the downloaded T999-16Gb pit from download site, maybe that file is not right? Since I can flash the stock boot.img by using Odin for version 4.1.2, the bootloader must be right???, Don't know what aboot.mbn would be affected by anything else.
I am wondering if someone can provide the T999 regular 16GB pit file, the early version of T999, Thanks.

A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.

audit13 said:
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
Click to expand...
Click to collapse
is it possible that the phone is upgrading from 4.1.2 to 4.3 and got crashed. but the bootloader is still showing 4.1.2?
what other possible reason that I can't flash aboot.mbn?

Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.

audit13 said:
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
Click to expand...
Click to collapse
Reboot to download mode, it is saying the same.
I am trying to flash stock recovery, modem, bootloader, all stock version 4.1.2 Only it can flash 4.1.2 bootloader, the recovery and modem always fails. Also the stock rom got failed.
With the same setting I can flash my other S3 recovery without problem, so the Odin, USB cable should not be an issue.
Thanks.

Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.

audit13 said:
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
Click to expand...
Click to collapse
the only problem is that my other working phone is running 4.3. I don't know what is the procedure to program it to 4.3 if my crashed one is in 4.1.2

[HELP] how to fix SGN8.0 always failed while flashing

ODIN MODE
PRODUCT NAME: GT-N5110
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 1
RP SWREV: A1
can any body know how to remove these line?
KNOX WARRANTY VOID: 1
RP SWREV: A1
i google it and i see that any off that two line are the cause why i can flash my official firmware..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i try all of andoid version of GT-n5110 its always fail..
BTW the samsung galaxy NOTE 8.0 have a gyroscope sensor for pokemon go?

can any body fix diss?

Elesio badiable said:
KNOX WARRANTY VOID: 1
RP SWREV: A1
can any body know how to remove these line?
Click to expand...
Click to collapse
Once you tripped the KNOX counter, you can't reset it. But, it will not block you from flashing via ODIN.
Elesio badiable said:
BTW the samsung galaxy NOTE 8.0 have a gyroscope sensor for pokemon go?
Click to expand...
Click to collapse
It does have a gyroscope (read under the "Sensors" here), but have no idea about "pokemon go" compatibility. :silly:

Stillness said:
Once you tripped the KNOX counter, you can't reset it. But, it will not block you from flashing via ODIN.
It does have a gyroscope (read under the "Sensors" here), but have no idea about "pokemon go" compatibility. :silly:
Click to expand...
Click to collapse
But how to fixx that can you pls help me ? i want to flash stock firmware Pls?

Elesio badiable said:
But how to fixx that can you pls help me ? i want to flash stock firmware Pls?
Click to expand...
Click to collapse
Why not try flashing the correct firmware for your device?
Your device is the wi-fi version (GT-N5110), but you are flashing a ROM for the 3G version (GT-N5100). Details from your OP proves that:
Elesio badiable said:
PRODUCT NAME: GT-N5110
...
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
Click to expand...
Click to collapse

Stillness said:
Why not try flashing the correct firmware for your device?
Your device is the wi-fi version (GT-N5110), but you are flashing a ROM for the 3G version (GT-N5100). Details from your OP proves that:
Click to expand...
Click to collapse
sorry i try it but it failed so i try GT-N5100 because i want to try if it gonna success but it failed so pls!! helpp
BTW you have a back up or stock rom of GT-N5110 not custom rom!! that i can flash it by TWRP i want to try the stock rom of thiss phone so pls? thks 4 help by the way ...

seems like your phucked it up dude! You can try COI3 firmware, as it flashes the latest bootloader over what 4.4.2 had installed originally. If it fails, you probably flashed a custom Note 2 Verizon firmware that ruined your bootloader info. Once you flash a higher revision bootloader, you cannot downgrade, unless someone developes a fix like Dr Ketan did for the Note 2 guys.