Galaxy Note II Stuck on System in Odin - AT&T Samsung Galaxy Note II

<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
My Galaxy Note II has been stuck on this for a while. I was trying to recover it via kies but it never worked so i tried out the Odin and this happened..
Please show me to any tutorial or post below a tutorial.

Katrxc said:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
My Galaxy Note II has been stuck on this for a while. I was trying to recover it via kies but it never worked so i tried out the Odin and this happened..
Please show me to any tutorial or post below a tutorial.
Click to expand...
Click to collapse
You working???
Lots of info is missing for anyone to help you....
Who is your network carrier? What did you try to flash? What version of ODIN....
If you are on ATT this may help
http://forum.xda-developers.com/showthread.php?t=2589891

Redownload the rom file. The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file.

rangercaptain said:
Redownload the rom file. The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file.
Click to expand...
Click to collapse
But he's using ODIN.... So he's flashing firmware.

Every ROM is firmware amigo. If the firmware is in a zip file set up for TWRP or CWR, good. If its in the tar format we use Odin3.
If you look inside the zip file it has a tar file in it.

rangercaptain said:
Every ROM is firmware amigo. If the firmware is in a zip file set up for TWRP or CWR, good. If its in the tar format we use Odin3.
If you look inside the zip file it has a tar file in it.
Click to expand...
Click to collapse
:
Uh yea,,,,
Senior Member
Thanks Meter 682
Posts: 1,584
Join Date: Sep 2010
I may be slightly familiar with the process and the difference.
I was pointing out the fact that it is failing while flashing with ODIN...
So your comment that
"The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file."
was probably not relevant in this case, since 99.969% of the free ROMs that devs freely build and graciously host on free sites, are not flashed in ODIN.

Only 682? Thats pretty weak amigo. Since 2010? You're so new you glow! I don't know what your malfunction is.
Samsung is a ROM/firmware developer. And Samfirmware.com (or whatever its called) is a sometimes spotty site.
The advice is still the same:
1. Redownload
2. Use the factory cable
3. Use the powered usb port
4. Use another version of Odin3.

rangercaptain said:
Only 682? Thats pretty weak amigo. Since 2010? You're so new you glow! I don't know what your malfunction is.
Samsung is a ROM/firmware developer. And Samfirmware.com (or whatever its called) is a sometimes spotty site.
The advice is still the same:
1. Redownload
2. Use the factory cable
3. Use the powered usb port
4. Use another version of Odin3.
Click to expand...
Click to collapse
No problem here slick. Yep having a life is rough.
I guess I would have to agree that a download of the stock ROM firmware from sammobile.com (which is not actually associated with the ROM/firmware developer Samsung) (http://www.sammobile.com/about-us/) would be a good idea, and then flash via ODIN.
Vice a download of a Dev ROM that perhaps an XDA developer posted on a cheesy site, which I mistaken thought you were implying.
That is why I posted the simple glowing statement, but it's an ODIN flash. Didn't expect a ROM flash 101 class.

Attack the OP's problem, not members who contribute solutions.
All you have done here was try to show everyone you're the smartest guy in the room.
Run along now.

rangercaptain said:
Attack the OP's problem, not members who contribute solutions.
All you have done here was try to show everyone you're the smartest guy in the room.
Run along now.
Click to expand...
Click to collapse
Respectfully, that's what I was trying to do, by asking questions. Like what were they trying to flash.
Then you jumped in and suggested to redownload, Without ensuring they were even flashing the right thing.
I have seen you give out great advice. That's why this seemed odd.

99% of the times a flash fails in Odin3 or recovery its because of a file error. If it was the wrong file for the phone it would flash and brick or it would stop immediately. But since he got most of the way through the process, I concluded correct file but likely corrupt download.
But you already know this.
---------- Post added at 01:49 PM ---------- Previous post was at 01:44 PM ----------
I actually made up the 99%, but its most of the time.

Related

[RECOVERY] Odin Flashable ClockworkMod Recovery Images

I am a MadTeam developer and I recently acquired this phone. I noticed that there weren't any Odin flashable ClockworkMod recoveries of the latest versions for this device, so I made my own and decided to share with you guys. This possibly may be helpful for new comers and also for people who may want to update their recoveries to touch recoveries without having to purchase the pro version of ROM Manager. I'll be sure to keep this thread up-to-date.
These are based off of the official ClockworkMod recovery images available at http://www.clockworkmod.com with no changes whatsoever.
ClockworkMod Recovery v6.0.1.5: http://www.mediafire.com/?wjm90gwjcvg4ccc
ClockworkMod Touch Recovery v6.0.1.5: http://www.mediafire.com/?bpr3dd11747zgcc
Flashing Instructions:
1. Open up Odin3 v1.85. Make sure only the "Auto Reboot" and "F. Reset Time" boxes are checked and nothing else.
2. Connect your phone to the computer in Download Mode. Odin should now detect your phone.
3. Select the PDA button and navigate to the desired recovery tar.
4. Press the "Start" button. It will now flash the updated recovery to your device. Your device will reboot upon completion.
Reserved.
Thanks, now when we say, Odin flash CWM, we can speak of flashing the latest one instead of the old 5.xx!
Thank you for doing this. I'm sure it will help some people out.
F. Reset Time
What does "F. Reset Time" do and is this required?
racer321 said:
What does "F. Reset Time" do and is this required?
Click to expand...
Click to collapse
Honestly not sure if needed but I've always had it checked and nothing bad had happened.
I stall out on flashing recovery image. Here's what I get. I'm using a tar where I manually swapped in the recovery image on my own.
<ID:0/004> Added!!
<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> recovery.img
Click to expand...
Click to collapse
And it just stalls. The screen of the phone appears as if nothing happened. I don't see the progress bar or anything.
Odin shows the first blue bar of the progress bar but it never goes beyond that.
Any help?
EDIT - it worked fine using one of the tars from this thread. So what am I doing wrong when substituting a recovery image on my own?
Hey thanks mate.
I tried flashing the latest TCWM via Rom Manager, and I guess the download got interrupted and it had a bad flash.
Ah well, not a big deal, but you saved me from having to go back to stock to unbrick it.
thanks for this its awesome to be updated and when i need it i will report lol
Is anyone making these for twrp?
Phateless said:
Is anyone making these for twrp?
Click to expand...
Click to collapse
TWRP already releases Odin flashables on the website.
http://techerrata.com/browse/twrp2/hercules
meekrawb said:
TWRP already releases Odin flashables on the website.
http://techerrata.com/browse/twrp2/hercules
Click to expand...
Click to collapse
I had no idea, but that's pretty awesome.

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

[UPDATED 9/27] [ODIN] MetroPCS - M919N (UVUAMF2) STOCK ODIN Flashable

Hey there,
I know some people have been requesting this for quite some time! This couldn't have been possible without @techguy1214 so a huge thanks goes out to him!
This is the absolute STOCK M919N Firmware. (THIS IS NOT ROOTED!)
EXPERIMENTAL: This is UNTESTED by me, I compiled this ODIN tar file using the same structure the T-Mobile ODIN File has. I do not have the MetroPCS version of this phone, I have the T-Mobile version. But I figured enough people wanted it so I would try to make it happen.
CONFIRMED WORKING!
I will not be help responsible if you brick your device or flash this incorrectly and your phone ends up blowing up. You have been warned.
Click to expand...
Click to collapse
NOTE: Because this is not officially signed by Samsung, I believe your flash counter will go up, use Triangle Away to reset your counter!
Huge thanks goes out to @danyvw for picking up my slack, new instructions posted.
Link: https://docs.google.com/file/d/0BxJFwkvU-C2McW5zU0RWQ01hM2s/edit?usp=sharing
1. Download the above .zip file and extract the .tar file in the archive and save it somewhere
2. Reboot your phone to download mode.
To get download mode shut down the device. After it shuts off completely simultaneously press the Down volume key+ Home button + press the power button .
3. Start Odin
4. Click on the PDA button and browse to the .tar file that you extracted in step 1 and select it
5. DO NOT PUT .PIT FILE AND DO NOT TICK REPARTITION
6. Connect the USB cable and wait for the ID:COM section to turn blue
7. Click start to flash
8. Do not disconnect the cable or turn off the device once the flash has started, it’s going to take some time to flash, when finish exit Odin and disconnect USB.
9. Let the phone start and Voila!!!!!!
theexel said:
Hey there,
I know some people have been requesting this for quite some time! This couldn't have been possible without @techguy1214 so a huge thanks goes out to him!
This is the absolute STOCK M919N Firmware. (THIS IS NOT ROOTED!)
EXPERIMENTAL: This is UNTESTED by me, I compiled this ODIN tar file using the same structure the T-Mobile ODIN File has. I do not have the MetroPCS version of this phone, I have the T-Mobile version. But I figured enough people wanted it so I would try to make it happen.
AGAIN.. THIS MAY NOT WORK.
If it doesn't use the T-Mobile ODIN, it will work, but of course, you will have the T-Mobile Baseband and whatnot, but if it does not work, I will try to work on it again soon!
NOTE: Because this is not officially signed by Samsung, I believe your flash counter will go up, use Triangle Away to reset your counter!
Download the TAR file: https://copy.com/lyMNNbzjaNYm
Click to expand...
Click to collapse
i tired it it worked 100% thanks
techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
No, thank you @techguy1214.
Without you, we wouldn't have these files! :highfive:
What is STOCK M919N ?
Can you elaborate more about the different between this M919N & M919V (as an example):
Can we flash without root ?
Compatibility with what ROM or firmware ?
Report log or advantages...etc.?
Anything more...?
itzik_man said:
Can you elaborate more about the different between this M919N & M919V (as an example):
Can we flash without root ?
Compatibility with what ROM or firmware ?
Report log or advantages...etc.?
Anything more...?
Click to expand...
Click to collapse
M919N is the MetroPCS variant of the Galaxy S4.
M919V is the Wind / Mobilicity / Videotron variant of the Galaxy S4, I believe.
This is for people that maybe messed up flashing a ROM or simply want to go back to barebone OFFICIAL MetroPCS stock firmware due to any reason. (Most likely they broke something and want to send it to warranty, lol.)
techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
any 1 else confirm this....??
djlucklu said:
any 1 else confirm this....??
Click to expand...
Click to collapse
Seems not...
arocker said:
Seems not...
Click to expand...
Click to collapse
Did not work for me. I jumped the gun and flashed a tmo stock rom to see if I could unlock my phone for free. I am unable to flash back to this rom now and can't unlock using a tmo rom.
Can anyone confirm that the pit files are different between the M919 and M919N? I tried a lot of different things last night and I think I flashed the M919 pit file as well as the rom, which is most likely my problem. Odin fails as soon as it tries to write.
Doesn't work
I tried to flash many times with different downloads and always get the same flash error:
<ID:0/004> Added!!
<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> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I get the exact same error.
downloading now ill let you know
fatalfury said:
downloading now ill let you know
Click to expand...
Click to collapse
Any update fatalfury?
people with errors making sure kies is not open right ? also try the USB port on back of computer and test again
krazierokz said:
people with errors making sure kies is not open right ? also try the USB port on back of computer and test again
Click to expand...
Click to collapse
Is not with Kies, its with Odin. Kies does not have firmware support for the SGH-M91N.
Understood just stating that Odin and kies open together conflicts and Odin won't run right that's all I'm saying
sent from my t mobile S4
Fixing Issues an PLEAS!!!
zbennett15 said:
I get the exact same error.
Click to expand...
Click to collapse
For this you are going to need mobile Odin To Flash an you will need to flash twice after you flash it the first time!:laugh::fingers-crossed:
techguy1214 said:
For this you are going to need mobile Odin To Flash an you will need to flash twice after you flash it the first time!:laugh::fingers-crossed:
Click to expand...
Click to collapse
Same error with PC odin, and when trying to open with mobile odin - partition could not be found.
---------- Post added at 07:20 PM ---------- Previous post was at 06:50 PM ----------
techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
Hey! how you flashed it? Thanks in advance.
I made some changes to techguy file.Is Working flawlessly with Odin, posted on androidforums:
http://androidforums.com/metropcs-g...t/773372-unofficial-m919nuvuamf2-working.html
danyvw said:
I made some changes to techguy file.Is Working flawlessly with Odin, posted on androidforums:
http://androidforums.com/metropcs-g...t/773372-unofficial-m919nuvuamf2-working.html
Click to expand...
Click to collapse
Updated OP, thank you.
Exel said:
Updated OP, thank you.
Click to expand...
Click to collapse
Thank you! Without your file I wouldn't have done anything. :good:

Cannot odin flash

I am getting an error flashing to 4.0.4 stock odin flash. I am pretty sure that the phone is not on 4.3 (I bought it thinking i could fix it) as it doesn't have the warrenty bit on the downloading screen.
this is my odin log:
ID:0/062> Added!!
<ID:0/062> Odin v.3 engine (ID:62)..
<ID:0/062> File analysis..
<ID:0/062> SetupConnection..
<ID:0/062> Initialzation..
<ID:0/062> Get PIT for mapping..
<ID:0/062> Firmware update start..
<ID:0/062> recovery.img
<ID:0/062> NAND Write Start!!
<ID:0/062> rpm.mbn
<ID:0/062> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Could you possibly boot into the phone and see if it is on Android 4.3?
codemonkey98 said:
Could you possibly boot into the phone and see if it is on Android 4.3?
Click to expand...
Click to collapse
The phone does not boot. It turns on then resets into recovery mode with a bunch of cannot mount error messages.
wireless_planets said:
The phone does not boot. It turns on then resets into recovery mode with a bunch of cannot mount error messages.
Click to expand...
Click to collapse
You wouldn't mind posting the errors, or taking a picture of the errors?
codemonkey98 said:
You wouldn't mind posting the errors, or taking a picture of the errors?
Click to expand...
Click to collapse
Here is the errors
Your phone has gone completely insane. The file systems, the NAND, etc are all messed up. When you cannot write to the NAND or the system, you got much of a problem.
Have you tried to see if you can flash a .PIT with Odin?
codemonkey98 said:
Your phone has gone completely insane. The file systems, the NAND, etc are all messed up. When you cannot write to the NAND or the system, you got much of a problem.
Have you tried to see if you can flash a .PIT with Odin?
Click to expand...
Click to collapse
I tried flashing the pit of i747 and it was successful, but still could not flash pda afterwards.
wireless_planets said:
I tried flashing the pit of i747 and it was successful, but still could not flash pda afterwards.
Click to expand...
Click to collapse
What were the errors that Odin gave you?
codemonkey98 said:
What were the errors that Odin gave you?
Click to expand...
Click to collapse
The odin errors are on the first post
wireless_planets said:
The odin errors are on the first post
Click to expand...
Click to collapse
My mistake. I'd really be interested in how this device became like this.
I would assume by now you'll need a new motherboard because the NAND isn't writing properly.
codemonkey98 said:
My mistake. I'd really be interested in how this device became like this.
I would assume by now you'll need a new motherboard because the NAND isn't writing properly.
Click to expand...
Click to collapse
I bought it from a customer. They took it to a guy was suppose to unlock it and he broke it. They wanted to sell it and I bought it for 50$ I figured I could fix it.
Would jtag be able to fix it? I have riff box that I rarely use, so I could order the connection for it.
wireless_planets said:
I bought it from a customer. They took it to a guy was suppose to unlock it and he broke it. They wanted to sell it and I bought it for 50$ I figured I could fix it.
Would jtag be able to fix it? I have riff box that I rarely use, so I could order the connection for it.
Click to expand...
Click to collapse
It's worth a shot but I do not think so at this point. I would believe a motherboard would be the only fix.

[Q] Can Anyone Send me a Legit SM-900T PIT file ???

Hi peoples of XDA I am in need of an authentic SM-900T 32GB PIT so I can revive my bricked note. I
Have unsuccessfully tried various sources but all of them seam to stem from the same sm9005 version and when I use odin the note rejects
the file and displays a Secure Check Fail in red letters on screen. This makes me believe a t-mobile pit will aid me in my mission of ressurrection.
Thanks to you all.
jub2k3 said:
Hi peoples of XDA I am in need of an authentic SM-900T 32GB PIT so I can revive my bricked note. I
Have unsuccessfully tried various sources but all of them seam to stem from the same sm9005 version and when I use odin the note rejects
the file and displays a Secure Check Fail in red letters on screen. This makes me believe a t-mobile pit will aid me in my mission of ressurrection.
Thanks to you all.
Click to expand...
Click to collapse
Have you tried just flashing the 4.3 or 4.4 tarball?
dragonstalker said:
Have you tried just flashing the 4.3 or 4.4 tarball?
Click to expand...
Click to collapse
Yeah I get a wierd error.
jub2k3 said:
Yeah I get a wierd error.
Click to expand...
Click to collapse
what version of odin are you using, what version of android and filename are you trying to odin, and what is the error?
dragonstalker said:
what version of odin are you using, what version of android and filename are you trying to odin, and what is the error?
Click to expand...
Click to collapse
I used V3 .04 and .07, and both of them give me a Secure Check Failed error in big red bold letters on screen.
I tried 2 seperate files . My_9005.pit & 9005.pit
An image of the error.
Error.
You need to use Odin v9 and the file is about 2.1 GB. Do a google search for the stock firmware and download that (sometimes it comes with Odin automatically) then hit the AP option and find your file.
---------- Post added at 07:41 AM ---------- Previous post was at 07:40 AM ----------
jub2k3 said:
Error.
Click to expand...
Click to collapse
I didn't look at your screen shot, I would first try flashing twrp recovery
Results= No Joy
This is the results of using v3.09 and flashing TWRP.
<ID:0/088> Added!!
<ID:0/088> Removed!!
<ID:0/051> Added!!
<ID:0/051> Odin v.3 engine (ID:51)..
<ID:0/051> File analysis..
<ID:0/051> SetupConnection..
<ID:0/051> Initialzation..
<ID:0/051> Get PIT for mapping..
<ID:0/051>
<ID:0/051> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Noobtoob posted a full how to, with pit included for both heimdall and odin. Check out his post and download from there. I don't want to post his work somewhere else.
http://forum.xda-developers.com/showthread.php?p=47887501 <<<< Original Thread

Categories

Resources