Related
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
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.
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.
<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.
It all started when my phone got wet from me jumping into a pool and realizing my phone was in my pocket afterwards, then I put it in rice for 24 hours, battery off the phone of course, then I proceeded to open the phone, dry the motherboard, open the cards and dab them with alcohol and dry them again. THAT, gave my phone life.
THEN, it's stuck on Samsung boot screen, it does not go into recovery and it does go into download mode.
I tried a pda on odin3 v1.85 and this is what I got
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions on what I can do to solve this soft brick type of issue? I was on KitKat btw.
You have to flash a KitKat stock ROM. Can't flash earlier version like MDL.
Sent from my SGH-M919 using Tapatalk
If flashing NB4 firmware won't work, I'm afraid something may have been fried and won't be fixable by firmware flash even if it does turn on and go into download mode
Frankenscript said:
You have to flash a KitKat stock ROM. Can't flash earlier version like MDL.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I will try to do that now..
YoungCNYC said:
I will try to do that now..
Click to expand...
Click to collapse
i cant do it because my phone doesnt go into recovery, by any chance, do you know how to flash a rom through odin?
Isn't using ODIN what you posted in the first post in this thread?
If you can't get into download mode, you may have a deeper problem. Since you couldn't get into "recovery" I'm guessing one of your buttons isn't working.
If you do get it to download mode, I recommend Odin 3.07 or 3.09 (I use 3.09).
Frankenscript said:
Isn't using ODIN what you posted in the first post in this thread?
If you can't get into download mode, you may have a deeper problem. Since you couldn't get into "recovery" I'm guessing one of your buttons isn't working.
If you do get it to download mode, I recommend Odin 3.07 or 3.09 (I use 3.09).
Click to expand...
Click to collapse
yeah I use odin, but idk how to flash a ROM through it i use 1.85
I'm on my phone at work without easy access to links, but if you Google "flash phone ROM with Odin" you will get many walkthroughs.
You were probably almost there with what you did in your first post. However you used an older version of the stock firmware than was on your phone so it failed. Get the KitKat firmware (NB4) and do what you originally tried.
I also recommend using at least Odin 3.07 though I know 3.09 works because I use it.
Basically boot phone to download mode, attach USB cable, let it recognize phone, open Odin, select your proper stock firmware in I think the second of the four places where you can specify the file, press start. Reboot when done.
Sent from my SGH-M919 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
See here ... My attempt to post the link from tapatalk... Sorry if doesn't work...
http://forum.xda-developers.com/showthread.php?t=2816508
Sent from my SGH-M919 using Tapatalk
Frankenscript said:
I'm on my phone at work without easy access to links, but if you Google "flash phone ROM with Odin" you will get many walkthroughs.
You were probably almost there with what you did in your first post. However you used an older version of the stock firmware than was on your phone so it failed. Get the KitKat firmware (NB4) and do what you originally tried.
I also recommend using at least Odin 3.07 though I know 3.09 works because I use it.
Basically boot phone to download mode, attach USB cable, let it recognize phone, open Odin, select your proper stock firmware in I think the second of the four places where you can specify the file, press start. Reboot when done.
Sent from my SGH-M919 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
See here ... My attempt to post the link from tapatalk... Sorry if doesn't work...
http://forum.xda-developers.com/showthread.php?t=2816508
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
That was great but the link of the thread doesn't work
You flash firmware in Odin, not ROMs.. Don't know if you guys are getting mixed up in this.. All you do is boot to download mode, connect to PC, open Odin, go to PDA, select your firmware and click start
Frankenscript said:
I'm on my phone at work without easy access to links, but if you Google "flash phone ROM with Odin" you will get many walkthroughs.
You were probably almost there with what you did in your first post. However you used an older version of the stock firmware than was on your phone so it failed. Get the KitKat firmware (NB4) and do what you originally tried.
I also recommend using at least Odin 3.07 though I know 3.09 works because I use it.
Basically boot phone to download mode, attach USB cable, let it recognize phone, open Odin, select your proper stock firmware in I think the second of the four places where you can specify the file, press start. Reboot when done.
Sent from my SGH-M919 using Tapatalk
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
See here ... My attempt to post the link from tapatalk... Sorry if doesn't work...
http://forum.xda-developers.com/showthread.php?t=2816508
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
serio22 said:
You flash firmware in Odin, not ROMs.. Don't know if you guys are getting mixed up in this.. All you do is boot to download mode, connect to PC, open Odin, go to PDA, select your firmware and click start
Click to expand...
Click to collapse
I already did that and it doesnt go past the samsung boot screen, it doesnt go to recovery either, he might be right but the links of the mega website wont let me download the NB4
YoungCNYC said:
I already did that and it doesnt go past the samsung boot screen, it doesnt go to recovery either, he might be right but the links of the mega website wont let me download the NB4
Click to expand...
Click to collapse
Search for fenny's fixed NB4 firmware and flash that