Develop Bugs

eastlink sghm919v Canadian s4 keeps failing when flashing stock Rom.

Hey fellow sgh-m919v owners in Canada!
Need some help here!
I am trying to Flash my eastlink wireless sigh-m919v back to stock and uproot it but it keeps failing in different times depending on the Rom I'm flashing.
On the older firmware I downloaded from sammobile.com it almost finishes then gets to modem.bin and says fail(auth) with a big red fail sign. On the phone it says secure check fail:mdm
When I try the newest one it doesn't even want to start. Odin starts then fails right away stating. Fail at sbl2.Mbn and Secure check fail: sbl2 on the phone.
Note when I go into download mode it does state that my phone is a sghm919v, current binary custom, system status custom, csb-oem_config_lbs:0x38 or 0x30. Too small to tell.
Note. I'm able to install custom roms and recoveries fine but not stock roms.
What am I doing wrong? Can someone give me step by step instructions? I'm using a Partially installed stock Rom and want it to be fully installed.
Any help is appreciated

Are you sure you are using the correct Rom...???
There is always the possibility the OS (operating system) you are attempting to install is not the correct one, and thus producing a conflict, and also a negative out come.
Can you post your Model, Make and Carrier, possibly the weblink where you are getting you update from.
Just to get a second opinion, and rule out that you are indeed getting the right download. As each Carrier is hardware sensitive, as to the type of Android OS it supports...

Well im not 100% sure im using the right one but 98% sure I am using the right one.
My phones downlosd mode says its a sgh-m919v. Canadian model of t mobile m919
I got the roms from sammobile.com
I used the firmware ending in esk thinking that meant eastlink but yesterday I doenloaded the wind, mobilicity and videotron versions of samr ftimware to see if yheres any differrnce.
Have yet to try. Will try soon

mikeogden198181 said:
Well im not 100% sure im using the right one but 98% sure I am using the right one.
My phones downlosd mode says its a sgh-m919v. Canadian model of t mobile m919
I got the roms from sammobile.com
I used the firmware ending in esk thinking that meant eastlink but yesterday I doenloaded the wind, mobilicity and videotron versions of samr ftimware to see if yheres any differrnce.
Have yet to try. Will try soon
Click to expand...
Click to collapse
Try to see if you can get your product code
http://forum.xda-developers.com/wik..._Galaxy_S_Series#How_To_Find_Product_Codes.3F

baseballfanz said:
Try to see if you can get your product code
http://forum.xda-developers.com/wik..._Galaxy_S_Series#How_To_Find_Product_Codes.3F
Click to expand...
Click to collapse
download mode states that my product code is a sgh-m919v

just tried flashing the other m919v firmwares from wind, mobilicity and videotron, no luck - fails at modem.bin. whats going on why does it keep failing. very frustrated

this is where it always fails:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919VVLUAMDJ_M919VYVLAMDJ_M919VVLUAMDJ_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> 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> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

bump! any help would be greatly appreciated guys!

Same issue
mikeogden198181 said:
bump! any help would be greatly appreciated guys!
Click to expand...
Click to collapse
I have the same issue... any resolution?... Need some help here... is our bootloader locked?

ryanmillet said:
I have the same issue... any resolution?... Need some help here... is our bootloader locked?
Click to expand...
Click to collapse
It might be all possible that you just have a simple hardware issue.
Instead of trying the latest, can you humor the conversation by trying the first update on the SamMobile site...!!!
Anything but the last or latest, try to roll back as far as you can...!!!

modem.bin is the radio file. does your phone boot into android and work fine after failing at modem.bin or it does not boot.
You can also try different version of Odin say 3.04 or a different usb port or both.
edit
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.

munchy_cool said:
modem.bin is the radio file. does your phone boot into android and work fine after failing at modem.bin or it does not boot.
You can also try different version of Odin say 3.04 or a different usb port or both.
edit
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
Click to expand...
Click to collapse
Nice reply, munchy_cool...!!!
Sent from my SGH-M919 using XDA Premium 4 mobile app

Getting somewhere...
grassy-sneakers said:
It might be all possible that you just have a simple hardware issue.
Instead of trying the latest, can you humor the conversation by trying the first update on the SamMobile site...!!!
Anything but the last or latest, try to roll back as far as you can...!!!
Click to expand...
Click to collapse
OK... so Odin flashing just doesn't work...
the latest based firmware MG1 stops almost instantly with an Sb2 error....
the oldest based firmware MDJ stops at modem install "secure check fail mdm"
I am however able to flash any custom recovery and from there install anything I want via CWM
Now... I was interested in flashing an alternative modem on my M919V (as my research leads me to understand that LTE is disabled on my device) I really wanted to just flash the M919 Modem...
so I searched and searched for a way to flash the modem to another one... all of reading said not to do it... it's too risky, ect.... BUT... some said it can be done and claimed success.... so I gave it a try...
Odin flash of ANY modem gives an error... same "secure check fail mdm" No CWM modem flash exists... I did find some other devices that had CWM modems to flash but flashing them gave a Baseband "unknown" IMEI "unknown"... so that was super scary... until I repacked the CWM modem zip with my device modem and I was back in business....
Long story short... you can't flash anything Via Odin in this phone really except a recovery... everything else pretty much fails which leads me to think either it was something to do with the partition scheme or the bootloader... I'm unsure as I really am not a developer just a daring competent xda rom addict...
IF you are on M919V and wish to flash modems (granted you will want to only flash a modem specific to M919V) examples would be the MG1 or MDJ... I have found a method that works everytime... you will need to have root via CF-ROOT or a custom rom which has root (that you flashed via CMW after to odin flashed a recovery)
here is the link to the instructions...
http://www.alliance-rom.com/communi...-non-hlos-bin-temporary-flashing-method.8676/
I hope this will shed some more light on our device... I really just wish I could convert my device fully to a M919 as this device (M919V) seems to have some weird issues... OR... better yet... a 9505G :highfive:
---------- Post added at 10:07 PM ---------- Previous post was at 10:02 PM ----------
munchy_cool said:
modem.bin is the radio file. does your phone boot into android and work fine after failing at modem.bin or it does not boot.
You can also try different version of Odin say 3.04 or a different usb port or both.
edit
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
Click to expand...
Click to collapse
Tried with 3.04 (instead of 3.09) here is my log - on the device it says "secure check fail: mdm"
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

munchy_cool said:
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
Click to expand...
Click to collapse
I still want to see if it is not a software issue by trying or playing around with OFFICIAL firmware, before I assume it is just faulty hardware refusing to corporate with your attempts to restore your Canadian Phone.
Again, munchy_cool, Thank you...!!!
Also have you called Samsung, and explained to them and I quote "That your phone failed during an OS update, and you tried to roll back using a download file from SamMobile, and even then you have experienced no success...!!!", just to see if they have on record of the same issues...???
--Just a though..., as I would hate to keep beating around the bush.
---------- Post added at 09:10 PM ---------- Previous post was at 09:04 PM ----------
Also I notice you have multiple choices to download, what one do you say is your version.
-SamMobile-
SGH-M919V - Canadian Firmware

ryanmillet said:
Tried with 3.04 (instead of 3.09) here is my log - on the device it says "secure check fail: mdm"
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
means the modem is invalid for this phone, as mentioned a few posts above there are multiple firmwares for your s4 , you need to know which carrier your s4 is ..there might be checks in the firmware to stop it from being flashed onto another carriers phone even if model number is same.

munchy_cool said:
there might be checks in the firmware to stop it from being flashed onto another carriers phone even if model number is same.
Click to expand...
Click to collapse
Thus the concern of a hardware conflict/issue with being successful in your flash using Odin.
Android devices are not all the same, they change depending on what country you are in especially if you are using a STOCK ROM. Every country has a different setup requirement when it comes to establishing a valid connection, so thus the hardware/software conflict.
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:21 PM ---------- Previous post was at 12:12 PM ----------
grassy-sneakers said:
Thus the concern of a hardware conflict/issue with being successful in your flash using Odin.
Android devices are not all the same, they change depending on what country you are in especially if you are using a STOCK ROM. Every country has a different setup requirement when it comes to establishing a valid connection, so thus the hardware/software conflict.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Besides that I cannot tell which is yours (meaning Firmware - SamMobile) your post suggest EastLink...??? Is this East Canada...? In East Canada what Carriers to they provide you...?, and what Model# is your phone...?
Maybe we can help to narrow down your Firmware you need...???

If you can also provide your OS - BASEBAND version, under Settings - More - About - Baseband Version.
You should be able to get this from a Custom Rom as well...!
Sent from my SGH-M919 using XDA Premium 4 mobile app

grassy-sneakers said:
If you can also provide your OS - BASEBAND version, under Settings - More - About - Baseband Version.
You should be able to get this from a Custom Rom as well...!
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My baseband has been flashed as I described in my earlier post... M919VVLUAMDJ.... My Carrier is unknown as I bought this phone unlocked for cheap on kijiji... but the guy said he worked for samsung and it was a spare... (Eastlink was the intended carrier...) although this model has 4 carriers it could potentially be... Eastlink, Wind mobile, ect.... The Op has the EXACT same model number and the EXACT same issue as me... he also has tried flashing literally EVERY firmware available on Sammobile website...

ryanmillet said:
My baseband has been flashed as I described in my earlier post... M919VVLUAMDJ.... My Carrier is unknown
Click to expand...
Click to collapse
(Eastlink was the intended carrier...) although this model has 4 carriers it could potentially be... Eastlink, Wind mobile, ect....
Click to expand...
Click to collapse
The Op has the EXACT same model number and the EXACT same issue as me... he also has tried flashing literally EVERY firmware available on Sammobile website...
Click to expand...
Click to collapse
I have confirmed that M919VVLUAMDJ, is the correct firmware for Canadian model phones, still at a miss, is this is a hardware description, given it is specifically found, i.e. provided visually in the OS.
and you say you have tried EVERY firmware...???
Have you read this yet...???
RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian S4 devices

grassy-sneakers said:
I have confirmed that M919VVLUAMDJ, is the correct firmware for Canadian model phones, still at a miss, is this is a hardware description, given it is specifically found, i.e. provided visually in the OS.
and you say you have tried EVERY firmware...???
Have you read this yet...???
RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian S4 devices
Click to expand...
Click to collapse
I'm downloading all the other firmware for my phone to see what one matches.... I'll let you know the results

Help with S3 Bell Bricked ?

Hi my friends Bell S3 crashed yesterday and I when it is going into recovery this is what it is displaying (see attached image) I think I need a the pit file to reflash, I tried just the md5 file but it errors out

Did you try the factory reset option ?
Nervous_Jester said:
Hi my friends Bell S3 crashed yesterday and I when it is going into recovery this is what it is displaying (see attached image) I think I need a the pit file to reflash, I tried just the md5 file but it errors out
Click to expand...
Click to collapse

the.teejster said:
Did you try the factory reset option ?
Click to expand...
Click to collapse
I wanted to try and keep the data, but at this point I will give it a try

Nervous_Jester said:
I wanted to try and keep the data, but at this point I will give it a try
Click to expand...
Click to collapse
Still having same issues does anyone have the pit file for the Canadian S3 ?

Did you try re-flashing a stock Bell ROM? If it was running stock 4.3, do not try to flash anything older than 4.3.

I'm in the same boat and require a PIT file for my Bell 16Gb S3.
When I try to flash the stock image in ODIN I get the following :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYCEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Did you try flashing a stock ROM from sammobile? You have the latest drivers installed and Odin 3.07?
I use Odin 3.07 on my i747m to flash back to stock Bell ROM all the time and haven't run into your problem.
Are you selecting only F.Reset Time?

audit13 said:
Did you try flashing a stock ROM from sammobile? You have the latest drivers installed and Odin 3.07?
I use Odin 3.07 on my i747m to flash back to stock Bell ROM all the time.
Click to expand...
Click to collapse
Yes. That's exactly what I tried to do and have done it successfully in the past without any issue.
Here is my specific post for help with details:
http://forum.xda-developers.com/showthread.php?t=2725985

the.teejster said:
Yes. That's exactly what I tried to do and have done it successfully in the past without any issue.
Here is my specific post for help with details:
http://forum.xda-developers.com/showthread.php?t=2725985
Click to expand...
Click to collapse
Are you selecting any options other than F.Reset Time?

I would download your md5 file again from sammobile sounds and looks like a bad file to me also make sure u have a good USB cable many times that can be a problem
Sent from my thl T11 using Tapatalk

jimchee said:
I would download your md5 file again from sammobile sounds and looks like a bad file to me also make sure u have a good USB cable many times that can be a problem
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse
I appreciate the replies but the file is good as i used it before, so is the cable as I use it all the time.
Something bad has happened with my phone as it's now it's actually hard bricked (won't power on or go into download mode. indicator light is red when plugged in w/o battery) and it might be the result of internal memory failure.
I'm trying the debrick process now as a lost option for me. If that doesn't work I may tried to get it jtagged.

When mine did that I was able to recover with sdcard method but it took me many many tries to get it to write correctly. If that doesn't work then JTAG is next option
Sent from my thl T11 using Tapatalk

jimchee said:
When mine did that I was able to recover with sdcard method but it took me many many tries to get it to write correctly. If that doesn't work then JTAG is next option
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse
I just finished my 3rd try to get the debrick img to write. Very frustrating as it take an hour to write and say successful in the end.
But the contents on the card so change or get overridden. I'm going to try on a different computer tonight. I'm determined to get the card written with the img and if that doesn't work then it's jtag.

You just have to keep trying, it took me hundreds of tries to get it to finally write it correctly, when I finally got it correct I couldn't read it on my computer, before that it was showing as a series of folders.
Sent from my thl T11 using Tapatalk

jimchee said:
You just have to keep trying, it took me hundreds of tries to get it to finally write it correctly, when I finally got it correct I couldn't read it on my computer, before that it was showing as a series of folders.
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse
I got the Debrick image written and my phone boots from it into download mode. Unfortunately I still cannot write the stock image. It fails to write because of the missing PIT file. So I am at a loss.

Galaxy S3 Major Root Confusion Update!

Hello Please if possible be very Noob friendly with your instructions, thanks
Ok I have a rooted Samsung Galaxy S3 AT&T on Firmware 4.3
So I noticed the 4.4.2 Update came out and i really want to update to it but I couldn't OTA because it would say update failed later discovered this is because my S3 is rooted
Now I am in the middle of trying to unroot my galaxy s3 and am very confused i tried doing backup and reset obviously that didnt work i am very confused on how this Odin software works so if you someone could give me very noob specific directions it would be greatly appreciated!
Thanks in Advance

Just open the SuperSU app and select Full Unroot. Let it do its thing and you're unrooted.
Or follow enewman17's thread for how to update.

I believe unrooting will only be successful if none of the AT&T apps were removed from the device. I forgot about that point and I had to flash the 4.3 stock image in order to successfully install the OTA update to 4.4.2. The OTA will try to patch all that ATT bloat during installation; if its not there it will fail.

DocHoliday77 said:
Just open the SuperSU app and select Full Unroot. Let it do its thing and you're unrooted.
Or follow enewman17's thread for how to update.
Click to expand...
Click to collapse
Yah i already did that but it would still fail the update at 24%

mwrobe1 said:
I believe unrooting will only be successful if none of the AT&T apps were removed from the device. I forgot about that point and I had to flash the 4.3 stock image in order to successfully install the OTA update to 4.4.2. The OTA will try to patch all that ATT bloat during installation; if its not there it will fail.
Click to expand...
Click to collapse
Could you please give me a download link or something to the 4.3 stock image for odin?
Everytime i download one it always some weird files that i do not know how to utilize through odin
So if you could give me a stock 4.3 that would be great thanks

nkhaira said:
Could you please give me a download link or something to the 4.3 stock image for odin?
Everytime i download one it always some weird files that i do not know how to utilize through odin
So if you could give me a stock 4.3 that would be great thanks
Click to expand...
Click to collapse
I used this method in post #1 to go back to stock 4.3: http://forum.xda-developers.com/showthread.php?t=2565972
Contrary to other posts...I only had Auto Reboot checked and that worked for me.
This will also wipe all data from your device...make sure you backup pics/vids/contacts/etc. before you do this.
After you take the OTA update, I can also confirm that TowelRoot will successfully root the ATT GS3 running KitKat. Although the documentation says no reboot is required...I needed a reboot after rooting with towelroot.

mwrobe1 said:
I used this method in post #1 to go back to stock 4.3: http://forum.xda-developers.com/showthread.php?t=2565972
Contrary to other posts...I only had Auto Reboot checked and that worked for me.
This will also wipe all data from your device...make sure you backup pics/vids/contacts/etc. before you do this.
After you take the OTA update, I can also confirm that TowelRoot will successfully root the ATT GS3 running KitKat. Although the documentation says no reboot is required...I needed a reboot after rooting with towelroot.
Click to expand...
Click to collapse
But isnt that for the Sprint Galaxy s3
I have the SGH-i747 AT&T LTE USA Version?

nkhaira said:
But isnt that for the Sprint Galaxy s3
I have the SGH-i747 AT&T LTE USA Version?
Click to expand...
Click to collapse
My sincerest apologies. Correct. I used that link for you because the instructions were clear and concise. The firmware download should be good from here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip

mwrobe1 said:
My sincerest apologies. Correct. I used that link for you because the instructions were clear and concise. The firmware download should be good from here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip
Click to expand...
Click to collapse
Just to make sure this is the file i put in odin so i can go back to stock 4.3 update (non rooted) and update OTA to 4.4.2 right?

nkhaira said:
Just to make sure this is the file i put in odin so i can go back to stock 4.3 update (non rooted) and update OTA to 4.4.2 right?
Click to expand...
Click to collapse
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)

mwrobe1 said:
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
Click to expand...
Click to collapse
Thank you for being responsive and helpful
I have started the file download i have slow internet speed at my house but it should download in 30 minutes and in a hour i will update this thread if it worked thanks!

mwrobe1 said:
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
Click to expand...
Click to collapse
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is the error message i am getting.. when i am trying this

nkhaira said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is the error message i am getting.. when i am trying this
Click to expand...
Click to collapse
I'll try to locate the exact MD5 I used and give you a link later today/this week. Sorry for the trouble.

mwrobe1 said:
I'll try to locate the exact MD5 I used and give you a link later today/this week. Sorry for the trouble.
Click to expand...
Click to collapse
Ok As soon as possible would be appreciated currently this is my only phone and i need to use it and I factory reset it yesterday thinking it would get rid of the root i would like to install all my apps and everything as soon as possible thanks

Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.

DocHoliday77 said:
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
Click to expand...
Click to collapse
Thanks for your reply So since this in too many different files what do i do to combine them (noob)? i know its something to the extent of extracting them into one folder?
Could you give me instructions on that

DocHoliday77 said:
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
Click to expand...
Click to collapse
Ok i got all the files combined now i see a csc a AP file and alot of the file catergories from Odin do i only need the AP file for PDA or do i need to insert each corresponding file into each corresponding category in Odin?

I don't have this device so its apparently a little different than I'm used to in this regard. Check post 13 of that thread to see if that helps. Otherwise someone more familiar with that particular process will need to chime in.

DocHoliday77 said:
I don't have this device so its apparently a little different than I'm used to in this regard. Check post 13 of that thread to see if that helps. Otherwise someone more familiar with that particular process will need to chime in.
Click to expand...
Click to collapse
Thank You So much!!
Sorry for late reply but the download you sent me worked and after 10 minutes i was on stock 4.3 upgraded to 4.4.2 without any problems!!!
THANKS!!!

[Q] Where do I download Rescue Firmware?

I would like to download Rescue Firmware because "Firmware Upgrade encountered an issue" message pops up
Unfortunately links on this thread: http://forum.xda-developers.com/showpost.php?p=32273406
are dead
Any other alternative links?
EDIT: As I have read with 4.4.2 firmware, bootloader is also upgraded and I cannot downgrade which means I have to find a 4.4.2 firmware which has 4 files and pit in order to restore my phone
Can someone help?

MariosFFX said:
I would like to download Rescue Firmware because "Firmware Upgrade encountered an issue" message pops up
Unfortunately links on this thread: http://forum.xda-developers.com/showpost.php?p=32273406
are dead
Any other alternative links?
EDIT: As I have read with 4.4.2 firmware, bootloader is also upgraded and I cannot downgrade which means I have to find a 4.4.2 firmware which has 4 files and pit in order to restore my phone
Can someone help?
Click to expand...
Click to collapse
You can flash normal firmware via odin in your situation, if you have this message fw upgrade..... etc your phone is in download mode connect to pc and flash, prefer older odin, v3 1.87 is the best for this. Another way to restore your phone is with kies (if you don't know how there is a thread in forum search it for instructions) . There is not any rescue fw 4.4.2 only pit file you can find but is not necessary.
Send from my phone

vagsvag said:
You can flash normal firmware via odin in your situation, if you have this message fw upgrade..... etc your phone is in download mode connect to pc and flash, prefer older odin, v3 1.87 is the best for this. Another way to restore your phone is with kies (if you don't know how there is a thread in forum search it for instructions) . There is not any rescue fw 4.4.2 only pit file you can find but is not necessary.
Send from my phone
Click to expand...
Click to collapse
Καλησπέρα
I have re-flashed the firmware with Odin countless times and the message re-appears, it won't boot and neither booting to recovery works.

MariosFFX said:
Καλησπέρα
I have re-flashed the firmware with Odin countless times and the message re-appears, it won't boot and neither booting to recovery works.
Click to expand...
Click to collapse
Γειά χαρά
I think it is failing to flash. Check at odin at left side if the flash finished well, it must say succeeded 1fail 0 and after removed at 2 last lines. The normal flash time is about 5 minutes for N7100.
Send from my phone
---------- Post added at 07:47 PM ---------- Previous post was at 07:18 PM ----------
Also here is an old guide how to restore with kies. The guide writes that you have to enter at download mod, you are already don't worry, the message fw encounter a pro..... etc is download mod
http://forum.xda-developers.com/showthread.php?t=2261153
Send from my phone

vagsvag said:
Γειά χαρά
I think it is failing to flash. Check at odin at left side if the flash finished well, it must say succeeded 1fail 0 and after removed at 2 last lines. The normal flash time is about 5 minutes for N7100.
Send from my phone
---------- Post added at 07:47 PM ---------- Previous post was at 07:18 PM ----------
Also here is an old guide how to restore with kies. The guide writes that you have to enter at download mod, you are already don't worry, the message fw encounter a pro..... etc is download mod
http://forum.xda-developers.com/showthread.php?t=2261153
Send from my phone
Click to expand...
Click to collapse
There are no errors.
Kies Emergency firmware recovery does not work, my device is not listed.

MariosFFX said:
There are no errors.
Kies Emergency firmware recovery does not work, my device is not listed.
Click to expand...
Click to collapse
There is no error at odin and device don't boot this is strange, Kies can't recognize your device try to put at kies first model and after serial number as saying this guide and after connect your phone to see if like this is possible.
http://forum.xda-developers.com/showthread.php?t=2697238
Send from my phone
---------- Post added at 08:50 PM ---------- Previous post was at 08:45 PM ----------
You are sure that you put the correct firmware at odin n7100 has different firmware than n7105 or n7102 etc etc. Each one has it's own
Send from my phone
---------- Post added at 09:01 PM ---------- Previous post was at 08:50 PM ----------
Model and serial you can find at a white stick down of battery when you take out battery.
Send from my phone

vagsvag said:
There is no error at odin and device don't boot this is strange, Kies can't recognize your device try to put at kies first model and after serial number as saying this guide and after connect your phone to see if like this is possible.
http://forum.xda-developers.com/showthread.php?t=2697238
Send from my phone
---------- Post added at 08:50 PM ---------- Previous post was at 08:45 PM ----------
You are sure that you put the correct firmware at odin n7100 has different firmware than n7105 or n7102 etc etc. Each one has it's own
Send from my phone
---------- Post added at 09:01 PM ---------- Previous post was at 08:50 PM ----------
Model and serial you can find at a white stick down of battery when you take out battery.
Send from my phone
Click to expand...
Click to collapse
Here's Odin Log:
Code:
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB2_N7100DBTDMA1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> sboot.bin
<ID:0/018> NAND Write Start!!
<ID:0/018> tz.img
<ID:0/018> system.img
<ID:0/018> boot.img
<ID:0/018> cache.img
<ID:0/018> hidden.img
<ID:0/018> recovery.img
<ID:0/018> modem.bin
<ID:0/018> RQT_CLOSE !!
<ID:0/018> RES OK !!
<ID:0/018> Removed!!
I tried updating my phone using KIES and the message "phone not recognized" pops up.
Here's a screenshot as well on ODIN
capture
any ideas?
I need a firmware which will let me FLASH EVERYTHING including the latest bootloader and re-partition
However I am limited to 4.3 and 4.4 firmwares because I tried installing 4.4.2 like in this image
http://forum.xda-developers.com/attachment.php?attachmentid=1503343&d=1353616564

MariosFFX said:
Here's Odin Log:.......
Click to expand...
Click to collapse
The firmware you mounted at odin xxdmb2 as I saw at your screenshot is 4.1.2 firmware
Latest Samsung 4.4.2 original firmware you can find here
http://live.samsung-updates.com/index.php?device=GT-N7100
Send from my phone

vagsvag said:
The firmware you mounted at odin xxdmb2 as I saw at your screenshot is 4.1.2 firmware
Latest Samsung 4.4.2 original firmware you can find here
http://live.samsung-updates.com/index.php?device=GT-N7100
Send from my phone
Click to expand...
Click to collapse
The same thing happens with the latest Germany 4.4.2 firmware.
I have noticed that my Bootloader has not been updated because I haven't seen anywhere saying anything about Knox in Download Mode
How can I update my bootloader?
The firmware I tried to flash is: N7100XXUFNE1_N7100DBTFNE1_N7100XXUFND3_HOME.tar
N7100XXUFNE1_N7100DBTFNE1_DBT

MariosFFX said:
The same thing happens with the latest Germany 4.4.2 firmware.
I have noticed that my Bootloader has not been updated because I haven't seen anywhere saying anything about Knox in Download Mode
How can I update my bootloader?
The firmware I tried to flash is: N7100XXUFNE1_N7100DBTFNE1_N7100XXUFND3_HOME.tar
N7100XXUFNE1_N7100DBTFNE1_DBT
Click to expand...
Click to collapse
fne1 you tried if I remember well is updating bootloader only you have to check at odin with reset time and auto reboot also phone bootloader update. Notice if bootloader update fails and phone can't go to download mod you have after serious problem.
Send from my phone

My Samsung S3 I747 is stuck on the logo when booting onto phone, tried using Odin..

I got my S3 from my brother since my Nexus 5 is currently broken, and with the S3 he installed CyanogenMod though it doesn't have root. So I decided to try and root it, but probably messed something up and now I'm stuck on the Cyanogen loadup screen, been waiting there for a solid 3 hours, and finally decided to try to fix it. I've tried using Odin3 3.0.7, trying to flash stock rom but I'm currently getting this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does anyone know what to do at this point? I've tried multiple different stock roms in case one of the stock roms had a problem. However, I flashed TWRP no problem, and I have that working for my recovery. What should I do at this point to get my phone back to Stock ROM?

Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.

The error happens when trying to flash aboot.mbn because, as @DocHoliday77 noted, LK3 cannot be flashed if the phone is running a 4.3 or newer bootloader.
I advise flashing TWRP and a custom ROM. This will allow you to boot the phone and determine the phone's bootloader version.

Flinze said:
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.
Click to expand...
Click to collapse
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes, I am able to access recovery with TWRP working, I just don't know where the terminal emulator is. (sorry i'm not very experienced w/ TWRP)

Also one thing to note, I can't install any sort of ROMS or can't flash anything through TWRM for some reason. When I swipe to flash a rom, what happens is that it just automatically goes back to the TeamWin logo page thing, and then I'm back on the home screen of TWRM (which shows all the buttons like install, wipe, backup, restore, mount, etc.) So I can't flash through TWRM, and if possible can someone link me a custom rom that supports md5, .tar, with those file extensions since the roms I've tried all are zips of .img files. (unless there is a way to convert it to md5, .tar, etc. extentions so that I can use ODIN on my computer to flash it)
edit: what I mean by md5, .tar is a PDA file so that I can use ODIN. if possible I just want my phone to run again w/ any roms... I've been phoneless for a few days now

You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Okay, when I typed the command getprop ro.bootloader what is get is:
I747MVLDLK4
I've tried flashing the stock recovery through TWRP, but it just again doesn't work as I explained in the previous post. So I tried using ODIN to flash it after converting it into a md5 file so that ODIN can read it and now when I try to enter recovery my screen is just black.

Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/

audit13 said:
Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/
Click to expand...
Click to collapse
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!

Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.

Flinze said:
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!
Click to expand...
Click to collapse
Glad to hear you got it going!
audit13 said:
Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.
Click to expand...
Click to collapse
Don't even worry about cred on this stuff man! You do plenty enough to be just as deserving! @dawgdoc too!
And tbh, I'm really glad you chimed in on that one! Since I'm not as familiar with which variant has which build number for the I747/I747M, (and since I'm usually used to just glancing at the last 3 characters), it probably would've taken me another 2 or 3 posts to have realized that was the problem. I Definately didn't catch it that first time!
So in the spirit of giving credit where it's due, you do deserve it here and in many, many other threads! Thanks!
Sent from my SGH-T999 using Tapatalk