Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<ID:0/006> Added!!
<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> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<ID:0/006> Added!!
<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> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?
It sounds like you have done a lot of research and educated yourself prior to attempting your first flash. Major props to you for that as most people don't.
My $0.02 about your issues...I had something similar happen once when I forgot to uncheck "F. Reset Time" before starting the flash. If that's not the problem then I'd try a different cable. Next step would be to try a different version of Odin, there are plenty floating around these forums.
Good luck!
hongseong said:
Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<ID:0/006> Added!!
<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> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<ID:0/006> Added!!
<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> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?
Click to expand...
Click to collapse
put it in the phone slot not the pda slot to bypass the pda bug
Oooh, thanks for the replies! I don't think I can get a micro USB cable right at this moment, but...
I did try the Phone method, and at first it seemed to actually start flashing, but it got stuck at factoryfs.rfs for quite a while, so I restarted the process and now it will just fail like it did before in about three seconds. Not sure what's gong on here, but it was nice to see it exhibiting some semblance of working up until it began hanging at factoryfs.rfs!
More helpful tips would be greatly appreciated!
Are you exiting Odin, disconnecting the phone, rebooting the phone into DL mode BEFORE trying to flash again? Odin will fail forever if you simply try to restart the process without the steps above.
I sure am!
I also think it has to do something with the param.lfs file since Odin always seems to fail once it encounters it (and it does so early on!).
Thanks again ^^
Ok have you tried to redownload the tar file it could be corrupted.You should be putting the whole tar file unopened in PDA leaving all the other slots empty and using the correct pit file that comes with odin.It is ok to leave the reset time option set it will not hurt anything.
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App
hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Was Re-Partition checked during any of your attempts?
For the longest time no, but then I talked to noobnl and he asked me to try to put it into both re-partition mode and phone bootloader update mode. It just hung at "DO NOT TURN OF TARGET" and that was it. He warned me that it could brick it, but I guess I got lucky and it didn't.
So yes, I did check re-partition mode, but not until I tried all aforementioned tips in every combination possible.
bubby323 said:
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oh, I was trying to flash DI18 the entire time (I gave up trying to flash DK17 last night, haha ^^ But I'll try your DK05 extended tip right now! Sorry I missed this ><
Okay, so using artemis' DK05 extended package and older Odin, I get a different readout
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
But it just stalls at boot.bin forever, and I've tried this several times, so...
I think the moral of the story here is that I'm unlucky
But yeah, that's what's happened so far. Thanks for the continued help, everyone!
Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck
marsknight said:
Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck
Click to expand...
Click to collapse
I tried to do it on another laptop in the house, but I ran into the same errors, but I'll try the microSD card trick soon
Thanks for the words of encouragement! I'm continuing to work on this problem, though I am a bit anxious to see how I can live without a cell phone...
im stuck with the same problem... and the messed up thing is i used odin before on this phone with win7 64bit... now i wish i never try updating to the new modem...
spent sooo much time on this and nothing im just gonna put it away b4 i smash it with a hammer... back to win mo...
Eeek, well, I think I'm going to scale back my attempts at fixing this for the moment. I'd be flat out lying if I said this wasn't a little bit frustrating, so I'm going to just relax before I make this fiasco ruin my Thanksgiving break for me. I'm most likely going to just purchase a cheap used flip phone and see through the rest of my contract with Sprint after changing my plan accordingly (no need for a data plan with a cheapo flip phone, and CERTAINLY no need for the 10USD WiMax surcharge, ^^; ).
That isn't to say that I'm not very thankful for all y'alls help, because I am, and this forum is awesome (along with the IRC chat!). Plus, not everything is *that* bleak; I mean, now I have a device that can charge batteries AND a 16GB microSD card freed up for other uses. So, thank you for all the help, and I hope y'all have a nice day!
Odin always seems to work for me windows 7 64bit and I have the 32bit drivers for the phone maybe try to deletethe old ones and install the 32bit drivers
Sent from my SPH-D700 using XDA App
Couple of questions and suggestions. Have you tried flashing just the modem in the proper slot(phone) with the proper pit file. I WOULD SUGGEST YOU TRY IT WITH THE OLDER ODIN(not 1.6) and the older pit. Then I would suggest you try to flash the full tar for DI18 with the older odin and no pit file. I have flashed my phone dozens of times with no pit as long as its the full tar. I could be wrong but I believe the pit is for partial system flashing. The only option I have checked on the left hand side of odin is reboot fwiw. Lastly, others have hinted at it too, odin is very finicky, try and try again. Always close down odin and restart it between attempts, and rebooting the computer seems to help others, and pull the phone battery and re-enter download mode each time too. Good luck, don't give up, if you can get into download mode all is not lost.
sent from an Epic4g through the cosmos
Related
Ok, going to try to cover all my bases up front. Here's the whole story.
I rooted my phone and loaded CyanogenMod about 2 days ago. It's way too easy, vastly improved the operation of my phone, so why not? Went off without a hitch. I've been informed that I should have done a NAND Backup, but I had no idea at the time.
About 4 hours ago my wife changed our phone numbers to a local area code after putting it off for the last year. I call Sprint because we're getting Error 16 Switch 386. Turns out you can just update the System Profile on the stock software, but after looking around for a while, turns out you can't in CyanogenMod. I'm like, "Ok, well I'll just put the stock software back on."
So, I try and I try and I try, but it keeps failing. I can still get back in to CyanogenMod, but ODIN won't let me flash any sofware onto my device. Well, one of the times I go to try to make it work I accidentally hit NAND Erase All. Now I'm stuck in a boot loop. I can boot in to recovery and download, but when I try to mount /data to do a factory reset, it can't. Cannot mount /data. Awesome. Now I'm getting into Re-partitioning this piece, which I seem to have successfully done once, but now I still can't flash any software to the phone because this:
<ID:0/006> Added!!
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
And here we are. I've tried using different cords, different USB ports, restarting the phone and my computer, different versions of ODIN.
My .pit is CSB_signed_Fusion3_EUR_0325_V2.pit, and my .md5 is \L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5
I'm not trying to go crazy, I just wanted the bloatware and background bull off of my phone. Now I probably have a brick in my pocket.
What firmware were you running when you rooted?? 4.2 or 4.3? If it was 4.3 you need to make sure that the file your trying to flash is a 4.3 (mja or mk2) file!
The tar you posted is MDC if you were on mja or higher this is your problem and you have go back to that!
Here's a link to the tar files I mentioned!
http://forum.xda-developers.com/showthread.php?t=2509605 Sent from my SCH-R970 using Tapatalk
bignick1215 said:
What firmware were you running when you rooted?? 4.2 or 4.3? If it was 4.3 you need to make sure that the file your trying to flash is a 4.3 (mja or mk2) file!
The tar you posted is MDC if you were on mja or higher this is your problem and you have go back to that!
Here's a link to the tar files I mentioned!
http://forum.xda-developers.com/showthread.php?t=2509605 Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
It was definitely on 4.3. I just started a download for the MJA. Is that the one I need, then?
Should work! If not try the mk2 but I think this will fix ya!
Sent from my SCH-R970 using Tapatalk
bignick1215 said:
Should work! If not try the mk2 but I think this will fix ya!
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Good news and bad news. The new process/files worked, but now I'm stuck on the Sprint boot screen. I'm going to keep poking around because this is much better than where I was at an hour and a half ago, but I've still got a ways to go.
So I did a factory reset, still got the Error mounting /data! message. Pulled the battery, did it again, successfully reset, phone is back to normal. Thanks a ton, homie.
No problem!!
Sent from my SCH-R970 using Tapatalk
I'm trying to go from MF9 -> MK2 (though this should be noted that the same error occurs trying to go to MJA). When I hook the phone up via my USB 3 ports, Odin starts to flash, but the phone won't budge it's progress bar.
Code:
<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> NON-HLOS.bin
If I try the exact same process on a USB 2 port, my phone gets stuck at the same point, but Odin only gets as far as the PIT.
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
I've verified the MD5s are correct. Thankfully, in both cases, it hasn't actually bricked the phone. Any suggestions?
Use a different version of odin. I've been using odin v3 3.09 and it works great with MJA and MK2. I would say it is a cable problem and not a port problem if the newer odin doesn't fix it.
I've tried both 3.07 and 3.09. No change in the results.
Edit: Additionally, no change with a brand new cable.
Hssarth said:
I'm trying to go from MF9 -> MK2 (though this should be noted that the same error occurs trying to go to MJA). When I hook the phone up via my USB 3 ports, Odin starts to flash, but the phone won't budge it's progress bar.
Code:
<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> NON-HLOS.bin
If I try the exact same process on a USB 2 port, my phone gets stuck at the same point, but Odin only gets as far as the PIT.
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
I've verified the MD5s are correct. Thankfully, in both cases, it hasn't actually bricked the phone. Any suggestions?
Click to expand...
Click to collapse
Are you running Odin 'as administrator'?
Is the cable BRAND NEW?
Yes, Odin is running as Administrator. As for the cable, it's the first time it's ever been used. Fresh out of the packaging.
That is strange, I would still recommend trying another cable just to be safe. Also, you are extracting the tar file from the original zip that is downloaded right? Next, are you loading it in the PDA slot on odin 3.07 or the AP slot on 3.09? What OS is your computer running? Don't use front usb slots on the PC if it is a desktop, they are often faulty, use the ones on the back of the PC. Your situation is not normal so just trying to narrow down the variables.
Yes, the file was extracted and loaded into those slots. I'm running on Windows 8.1, but experienced the same issue on a Windows 7 system. As for front vs back, the USB 3 ports that had slightly more success were located on the front, whereas the 2s were located on the back. (And before you ask, the motherboard is less than a month old. I doubt it's the ports. >.>)
Are you opening the file in the pda section of odin then flashing?
Sent from my SPH-L720 using XDA Premium 4 mobile app
churchey360 said:
Are you opening the file in the pda section of odin then flashing?
Click to expand...
Click to collapse
.....
cruise350 said:
Next, are you loading it in the PDA slot on odin 3.07 or the AP slot on 3.09?
Click to expand...
Click to collapse
Hssarth said:
Yes, the file was extracted and loaded into those slots.
Click to expand...
Click to collapse
TL;DR: Yes.
Was the windows 7 the same computer or a different computer than the windows 8.1? You definitely have an odd problem. This new motherboard must have a usb controller that is incompatible with the samsung drivers or something. I have used odin with windows 7, 8, and 8.1 with no problems. Have you tried on another computer? Maybe it is the usb port on the phone that is bad. I sure wish I could help with your situation but I am at a loss for the common problems that usually occur with an odin flash. Lastly, have you tried to download the tar file from a different source?
cruise350 said:
Was the windows 7 the same computer or a different computer than the windows 8.1? You definitely have an odd problem. This new motherboard must have a usb controller that is incompatible with the samsung drivers or something. I have used odin with windows 7, 8, and 8.1 with no problems. Have you tried on another computer? Maybe it is the usb port on the phone that is bad. I sure wish I could help with your situation but I am at a loss for the common problems that usually occur with an odin flash. Lastly, have you tried to download the tar file from a different source?
Click to expand...
Click to collapse
Yes, I've tried a different computer as well as different sources. Just now, I tried the CF auto-flash to make sure there wasn't some lingering flag that got reset. Unfortunately, it has the same result as everything else.
Is there by any chance some way to load these in via adb instead? Or, should I bite the bullet, take the OTA and try to root that?
Edit: Actually, using the Odin that came with the autoroot, I'm now getting this:
Code:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Actually, using the Odin that came with the autoroot, I'm now getting this:
Click to expand...
Click to collapse
So you aren't using 3.07 or 3.09 as some suggested. You are continuing to do the same thing and expect different results.
How about trying Odin 3.07 or 3.09?!
How about trying SafeRoot - It works on our phone, I just used it yesterday on a new Sprint 4.3
Please take some time and try the suggestions we post.
Then do some searching and reading. Then some more searching and reading.
Good luck.
leaderbuilder said:
So you aren't using 3.07 or 3.09 as some suggested. You are continuing to do the same thing and expect different results.
How about trying Odin 3.07 or 3.09?!
How about trying SafeRoot - It works on our phone, I just used it yesterday on a new Sprint 4.3
Please take some time and try the suggestions we post.
Then do some searching and reading. Then some more searching and reading.
Good luck.
Click to expand...
Click to collapse
No. If you had read my posts, you would know that I did use both of those versions. Since this came with a third, I tried it just to see what would happen.
Sorry sport did read your post and saw the 'used what came with cf-autroot' and that is 1.85.
Did you try saferoot yet?
leaderbuilder said:
Sorry sport did read your post and saw the 'used what came with cf-autroot' and that is 1.85.
Did you try saferoot yet?
Click to expand...
Click to collapse
Just now. It ran just fine, but did not fix the problems with Odin.
Edit: In an attempt to further narrow it down, I just ran TriangleAway to reset my flash counter. No change.
Hssarth said:
Just now. It ran just fine, but did not fix the problems with Odin.
Click to expand...
Click to collapse
Ok well you're rooted anyways.
Hssarth said:
Just now. It ran just fine, but did not fix the problems with Odin.
Edit: In an attempt to further narrow it down, I just ran TriangleAway to reset my flash counter. No change.
Click to expand...
Click to collapse
IF you took the OTA or in any way updated the bootloader to 4.3 you CANNOT remove the knox counter. End of story (for now anyways).
This too has been discussed ad naseum here in these forums.
Now that your're rooted though you can do plenty.
Spend some time here, read study, and read some more. You won't be sorry.
leaderbuilder said:
IF you took the OTA or in any way updated the bootloader to 4.3 you CANNOT remove the knox counter. End of story (for now anyways).
This too has been discussed ad naseum here in these forums.
Now that your're rooted though you can do plenty.
Spend some time here, read study, and read some more. You won't be sorry.
Click to expand...
Click to collapse
I've /been/ rooted, since day one. The earlier rooting was to make sure everything was still functioning properly. I'm currently on the MF9 Negalite BluRom.
Here's the thing though. In December, I tried upgrading to MK2 -- the flash seemed to take. I then put philz on. Both sacs and the newer negalite ROM bootlooped. So I went back to the rooted stock MF9 ROM/firmware (without issue) and reloaded the ROM I have now via TWRP.
I know you bought a new cable, but every thing that you have reported so far still leads me to believe it is a cabling or port issue. The only cable that is sure to work is the samsung cable. If you bought a cable of ebay or amazon it may not be up to spec. Samsung's cable is the most reliable for our phone. Since your motherboard in your pc is new it may be the actual port on your phone. When you hook your phone up to your computer in mtp mode try transferring a large file 2-3gb to your sdcard to see if it transfers without any errors. This will give you a test if it is odin or the connection between your pc and your phone.
Well, I got it to work. You know that other W7 system I said I had tried? It's a laptop. For grins, I tried using a different USB port on it, specifically the one it'll supply power to if the system is otherwise turned off. Even though the other port on the device seemed to recognize it just the same, that one change seemed to make all the difference.
Long story short.. I guess this process needs to be done in W7 on a port it's happy with.
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I used ODIN to flash (What I'm very confident is) 4.3 Stock in the same manner I flashed the custom ROM.
I feel like that isn't specific enough for you though. I used Odin3 v3.09 first and then after several failures switched to Odin3 v1.85 as demonstrated in a few tutorials I've seen.
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Let me attempt this thread's instructions before I make more of a fool of myself. Thank you for the assistance so far. I really appreciate it.
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Seedeh,
The errors still continued as usual even with the explicit following of the linked directions. It appears that during the process:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that the "NAND Write Start" step isn't really even trying to write before it fails.
Kies "Emergency Firmware Recovery" also yields no success due to "Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.", which does persist each time I attempt to do so.
If you have any more suggestions, I'd be more than happy to attempt them.
Thank you.
AmpGuitarChase said:
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
Click to expand...
Click to collapse
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
John The Rhino said:
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
Click to expand...
Click to collapse
John The Rhino,
Thank you for you assistance. I will surely give credit where credit is due
I've attempted the XDA Full Odin Tar MK2 link's instructions three times on two separate computers (one w8 and one w7) to no avail. I've triple-checked the instructions, but my Odin always fails when attempting to Complete(Write).
NAND Write Start!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
Complete(Write) Operation Failed
All threads completed. (succeed 0 / failed 1)
Odin settings: Auto Reboot checked, F. Reset Time checked, PDA = I337MK2_Full_Odin_Tar.tar file, nothing else is checked.
Device: Dev mode activated, USB debugging active, this is all verified after a recovery-initiated factory reset, device is in download mode.
Computer(s): Samsung Android ADB Interface drivers are installed, Odin does show a yellow bar upon device connection. MicroUSB cable is the default one that came with the device, all USB ports have been tried with the same results.
I tried to be as thorough as possible with my setup. I'll see if my process is correct now just in case that will help.
[Fixing Device to Working Status w/o wifi/data permissions] Flashed AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 via Odin
Automatic Reboot via Odin
[Device is back to working status w/o data/wifi permissions (No reset has been done)]
Power off
Reboot in Recovery Mode (Volume up + Home + Power)
Wipe data/factory reset command
Wipe cache (just in case)
Reboot
[Phone is now factory reset 4.3 MK2 (WiFi/Data permissions denied still]
Enable developer options
Enable USB debugging and Screen Stay Awake during charging
Power off
Boot into download mode (Volume down + Home + Power)
Open Odin3 v1.85
Bar in Odin for COM Port is yellow
Auto reboot & F. Reset Time are both checked
Load I337MK2_Combined_Odin_Tar\I337MK2_Full_Odin_Tar.tar.md5 in PDA slot
Screenshot of Odin before "START" http://i.imgur.com/oXufVNQ.png
Odin START
Wait for Odin to check .md5 compatibility
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Back to where these points began
Apologies for the length, but again I wanted to be as thorough as possible. My WiFi still won't turn on due to permissions issues and Data is on, but no 3g/4g/LTE comes through.
Surely I'm just missing an essential step or two.
Can you offer any further advice on this matter?
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
The bootloader on MK2 and later is encrypted and without the key it will always fail. ODIN sees the ABOOT is locked and cannot flash the complete image. AT&T and Verizon have chosen this method to keep you off their cheaper competitors. I had to take my I337 to Best Buy Samsung experience to have it re flashed so that it would boot after a refused OTA from MDL and now it is a paperweight.
jd1639 said:
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
Click to expand...
Click to collapse
I don't think Odin is the issue as it flashes what I like to call "The cure-firmware" .md5 AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5) file just fine every time with no issues with Odin. Only when I try to flash that file, it works. I wish there was a way to tell what exactly is going wrong with the other files. I also can't seem to find where I located this file, but whatever it's doing works on my S4. I'd like to find either a 4.2.2 or 4.4.2 version of this stock OS that would work.
I'm beginning to wonder if it'd be more worthwhile to reroot, reset the flag binary counter, reset, and drive an hour and a half away to the closest AT&T store and see if they can fix my device. Does this sound like it may be my best course of action?
Again, thanks for all the help guys. I means a lot.
There is no way to downgrade to 4.2.2 from MK2. The bootloader is locked. Read the guide for MK2 it will help you.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Check your APN settings re enter according to correct settings posted on XDA.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Loki does not work with MF3 and up
Congrats!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
John The Rhino said:
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
Click to expand...
Click to collapse
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
AmpGuitarChase said:
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
Click to expand...
Click to collapse
You're welcome. I'm glad it all worked out for you. As they say in the construction business, measure twice, cut once. Well same here, except I'd recommend as do others to read thrice (3x) FLASH once. Then you'll rarely have issues. Enjoy.
i337 same issue as original post
i have done the same research as posted in this link and read exhaustively every means google XDA and all the other pages dealing with rooting and flashing my AT&T s4 i337. I have ended up in the same boat as this guy with:
Baseband version - I337UCUFNB1
Build Number - JSS15J.I337UCUEMK2
i have attempted Kingo Loki, Motochopper, Odin(4 or 5 versions) adb flash in Linux(2 builds) and Winblows 7. My original desire was to have this build
https://www.youtube.com/watch?v=mJLKX_QWSpc
which got my hopes up immensely, as having wasted days upon days several times over the course of the last 9 months rooting this i337. The guy in the vid says he was able to get UT up and running following guidance from XDA. I want to be able to flash a twrp-like dual boot recovery to my device maintaining Andy functionality using UT as a daily driver.
I have read, as reading saves phones, everything I can glean from the aforementioned posts and forms, researched this thing to death and neded up with a phone with the knox-? security message listed in the original post. I have no Idea where to go from here, but know you guys do, as like a myriad of others, I worship this site like a god.
Please help an old retired disabled veteran of most of the sandy wars in the past 25 years. All I have now are my devices which bring me some comfort to my days.
I really need your help, as I've tried seemingly all and have a semi-dead i337.
buxtor, aka, Chief
I have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU
You are on the latest OTA of BOG5. The bootloader is completely locked down and you cannot root, downgrade, or flash anything. You are stuck with the phone as is. You will have to find the BOG5 full stock firmware .tar file and flash that through ODIN to get your phone back.
Damn!!!!
do you know any links from where i can download the BOG5 firmware from?
I am having the exact same issue. Any help is appreciated!
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
So I managed to get mine back working by using the VZW-G900VVRU2BOG5-20150813111348.zip firmware downloaded from Sammobile.com and flashing using Odin3.
Used the first firmware on Sammobile firmware page for model SM-G900V
Unzipped the file and flashed the .md5
Back up and running.
Hope this helps someone.
wgafsck said:
I am having the exact same issue. Any help is appreciated!
Click to expand...
Click to collapse
jac1985 said:
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
Click to expand...
Click to collapse
smn216 said:
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
Click to expand...
Click to collapse
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
landshark68 said:
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
Click to expand...
Click to collapse
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Seriously, do none of you have even the basic, simple ability to look through these forums at all?
Click to expand...
Click to collapse
Same here, in fact it was my first time posting and I was also kind of lost. In any case, thanks for the lesson and the links.
wgafsck said:
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Click to expand...
Click to collapse
Understood. It just gets very old and frustrating answering the same questions over and over again, and questions for which the answer is already readily available. Glad you got it straightened out, and that you realized more research before embarking on your adventure would have helped. When it comes to messing around with an expensive piece of hardware like these smart phones, it's best to think of the carpentry line - measure twice, cut once. Read, read, read, and make sure you know what you are doing before you do it when it comes to rooting and modding your phone.
Thanks a million! I thought my phone is toasted.
Before I start my explanation, this phone is NOT rooted and never has been (every article I have found so far relates to the phone being rooted)
I have a N910F Galaxy Note 4 mobile phone. Until yesterday morning it worked fine when I started experiencing major lag up until the point where the phone would become unresponsive. To get the phone to work again I had to take the battery out and put it back in 4/5 times before the phone would come back on but after a few minutes the lag returned. Then after it had happened a few times the phone restarted itself and went into download mode with two messages in the top left corner, one reading 'could not do normal boot' and the other 'ddi: mmc_read failed'. After taking the battery out again I got the phone to boot normally again but the lagging and freezing kept happening. I downloaded the stock firmware from sam mobile overnight and tried to flash it using Odin but got a 'failed' message immediately after starting the process.
I then used Samsung Kies to download and reinstall Touchwiz. I thought I had solved the problem but it has not, I barely got through the initial setup before the lag started again. I booted into recovery mode and noticed a red message at the bottom reading 'dm_verify verification failed'. I decided to reboot the phone but it has now restarted itself back into download mode with the mmc_read error message again.
Can any of the wise people on here help me out? As previously mentioned this phone has never been rooted (KNOX warranty 0x0) and until yesterday it functioned perfectly fine. I've spent the last 24 hours searching the internet with the hope that I wouldn't have to reach out for help but found nothing that could help
neils0911 said:
Before I start my explanation, this phone is NOT rooted and never has been (every article I have found so far relates to the phone being rooted)
I have a N910F Galaxy Note 4 mobile phone. Until yesterday morning it worked fine when I started experiencing major lag up until the point where the phone would become unresponsive. To get the phone to work again I had to take the battery out and put it back in 4/5 times before the phone would come back on but after a few minutes the lag returned. Then after it had happened a few times the phone restarted itself and went into download mode with two messages in the top left corner, one reading 'could not do normal boot' and the other 'ddi: mmc_read failed'. After taking the battery out again I got the phone to boot normally again but the lagging and freezing kept happening. I downloaded the stock firmware from sam mobile overnight and tried to flash it using Odin but got a 'failed' message immediately after starting the process.
I then used Samsung Kies to download and reinstall Touchwiz. I thought I had solved the problem but it has not, I barely got through the initial setup before the lag started again. I booted into recovery mode and noticed a red message at the bottom reading 'dm_verify verification failed'. I decided to reboot the phone but it has now restarted itself back into download mode with the mmc_read error message again.
Can any of the wise people on here help me out? As previously mentioned this phone has never been rooted (KNOX warranty 0x0) and until yesterday it functioned perfectly fine. I've spent the last 24 hours searching the internet with the hope that I wouldn't have to reach out for help but found nothing that could help
Click to expand...
Click to collapse
Is your phone still under warranty?
Sent from my SM-N910G using Tapatalk
neils0911 said:
Before I start my explanation, this phone is NOT rooted and never has been (every article I have found so far relates to the phone being rooted)
I have a N910F Galaxy Note 4 mobile phone. Until yesterday morning it worked fine when I started experiencing major lag up until the point where the phone would become unresponsive. To get the phone to work again I had to take the battery out and put it back in 4/5 times before the phone would come back on but after a few minutes the lag returned. Then after it had happened a few times the phone restarted itself and went into download mode with two messages in the top left corner, one reading 'could not do normal boot' and the other 'ddi: mmc_read failed'. After taking the battery out again I got the phone to boot normally again but the lagging and freezing kept happening. I downloaded the stock firmware from sam mobile overnight and tried to flash it using Odin but got a 'failed' message immediately after starting the process.
I then used Samsung Kies to download and reinstall Touchwiz. I thought I had solved the problem but it has not, I barely got through the initial setup before the lag started again. I booted into recovery mode and noticed a red message at the bottom reading 'dm_verify verification failed'. I decided to reboot the phone but it has now restarted itself back into download mode with the mmc_read error message again.
Can any of the wise people on here help me out? As previously mentioned this phone has never been rooted (KNOX warranty 0x0) and until yesterday it functioned perfectly fine. I've spent the last 24 hours searching the internet with the hope that I wouldn't have to reach out for help but found nothing that could help
Click to expand...
Click to collapse
Welcome to XDA!. Hope this helps, let the forum know one way or other. Gl https://forum.xda-developers.com/showpost.php?p=70652492&postcount=10
hello pls help
[/PHP]hello my name is salem i have galaxy note 4 n910f n my phone get masseges error n then i flash new room from odin but the rrom not work n when i open download manger there is masseges that mmc read failde
n when i need to install any room in odin type me this
ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXS1DPC2_N910FOXA1DPB5_N910FXXU1DPB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
after that i put the pit file n the same
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
pleas help me pls :crying::crying::crying::crying::crying::crying::crying:
Amar.B said:
Is your phone still under warranty?
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
No unfortunately it isn't. I'll have to approach Samsung for help if I can't figure it out but they will charge me for the repair.
neils0911 said:
No unfortunately it isn't. I'll have to approach Samsung for help if I can't figure it out but they will charge me for the repair.
Click to expand...
Click to collapse
Yeah you will pay fees for the entire motherboard plus service .. there's workground for this problem in general fourms..
Found it
https://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
Sent from my SM-N910G using Tapatalk
Amar.B said:
Yeah you will pay fees for the entire motherboard plus service .. there's workground for this problem in general fourms..
Found it
https://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice I may try this method, I'm just not sure it would work as Odin instantly failed when I tried using it the first time. I just can't help thinking that one error is causing the other so I'm not which one I should actually be trying to fix. I even saw a video on YouTube that claimed that one of the errors is a hardware fault with the charging flex cable inside the phone. Who knows he may be right.
Thanks again I might try odin again but if it fails again I will have to restore Touchwiz via Samsung Keis again just to get the phone into a bootable state
neils0911 said:
Thanks for the advice I may try this method, I'm just not sure it would work as Odin instantly failed when I tried using it the first time. I just can't help thinking that one error is causing the other so I'm not which one I should actually be trying to fix. I even saw a video on YouTube that claimed that one of the errors is a hardware fault with the charging flex cable inside the phone. Who knows he may be right.
Thanks again I might try odin again but if it fails again I will have to restore Touchwiz via Samsung Keis again just to get the phone into a bootable state
Click to expand...
Click to collapse
Download repair firmware for your model from www.tsar3000.com this repair firmware comes with pit file.
Before flashing firmware put your device in freezer without battery for atleast 1 hour.i know it sounds crazy but it really solve the issue.
Flash firmware and do factory reset from stock revovery and your device will be completely fine.
Trex888 said:
Download repair firmware for your model from www.tsar3000.com this repair firmware comes with pit file.
Before flashing firmware put your device in freezer without battery for atleast 1 hour.i know it sounds crazy but it really solve the issue.
Flash firmware and do factory reset from stock revovery and your device will be completely fine.
Click to expand...
Click to collapse
That is a strange one but I'll give anything a go, i'll try this method when I get home from work today...if you don't mind me asking why place the phone in the freezer? and do you know what causes these issues?
neils0911 said:
That is a strange one but I'll give anything a go, i'll try this method when I get home from work today...if you don't mind me asking why place the phone in the freezer? and do you know what causes these issues?
Click to expand...
Click to collapse
Motherboard sometimes acting crazy because note 4 has heating issues all the time because of 1440p 2k screen with old snapdragon 805 processor.i am not exactly sure why it works when put in freezer but many users successful with this even they fix their hard bricked devices and emmc_fail devices.
So give it a try and be patiant.tty this again and again when you have enough time once it wotks do a factory reset from recovery and your device will be normal.
Ok there seems to be quite a few new threads regarding this issue in the last few days. I'm downloading the repair firmware now from the website you recommended so i'm going to put my phone in the freezer once it has finished
Trex888 said:
Motherboard sometimes acting crazy because note 4 has heating issues all the time because of 1440p 2k screen with old snapdragon 805 processor.i am not exactly sure why it works when put in freezer but many users successful with this even they fix their hard bricked devices and emmc_fail devices.
So give it a try and be patiant.tty this again and again when you have enough time once it wotks do a factory reset from recovery and your device will be normal.
Click to expand...
Click to collapse
Sorry noob question here, do I not flash the PIT file? I've only ever used Odin to root phones before or flash full a full 'all in one' firmware file
neils0911 said:
Sorry noob question here, do I not flash the PIT file? I've only ever used Odin to root phones before or flash full a full 'all in one' firmware file
Click to expand...
Click to collapse
You have to load pit file along with firmware same time together you cannot flash pit file alone.
In odin there is PIT tab click on it and upload pit file then go to odin options check "nand eraseall" then upload firmware AP tab after that go to device download mode and connect device to pc viab usb cable and HIT START IN ODIN.
once odin pass go to stock revovery and wipe cache wipe data factory reset.
That all you have to do.
Trex888 said:
You have to load pit file along with firmware same time together you cannot flash pit file alone.
In odin there is PIT tab click on it and upload pit file then go to odin options check "nand eraseall" then upload firmware AP tab after that go to device download mode and connect device to pc viab usb cable and HIT START IN ODIN.
once odin pass go to stock revovery and wipe cache wipe data factory reset.
That all you have to do.
Click to expand...
Click to collapse
What about BL, CSC and CP files? Do I need to put those in or just the AP? Ive put the pit file into that tab
neils0911 said:
What about BL, CSC and CP files? Do I need to put those in or just the AP? Ive put the pit file into that tab
Click to expand...
Click to collapse
Looks like you have 4 files repair firmware.
In odin load each file saprately
Load BL,AP,CP,CSC, all 1 by 1 and for PIT there is a tab on top PIT file you can load.
Trex888 said:
Looks like you have 4 files repair firmware.
In odin load each file saprately
Load BL,AP,CP,CSC, all 1 by 1 and for PIT there is a tab on top PIT file you can load.
Click to expand...
Click to collapse
Yeah I have all of them as it was one zip file from the website. Sorry to bother you again
neils0911 said:
Yeah I have all of them as it was one zip file from the website. Sorry to bother you again
Click to expand...
Click to collapse
It failed this was the bottom log from from odin:
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
neils0911 said:
Ok there seems to be quite a few new threads regarding this issue in the last few days. I'm downloading the repair firmware now from the website you recommended so i'm going to put my phone in the freezer once it has finished
Click to expand...
Click to collapse
Try post #3, it did worked for me.
mangui said:
Try post #3, it did worked for me.
Click to expand...
Click to collapse
I'll give it a go but it sounds like the same process I've now done twice using Keis. It allows the firmware to reinstall but then the lagging/error messages continue. I'll try it anyway though, thanks
neils0911 said:
I'll give it a go but it sounds like the same process I've now done twice using Keis. It allows the firmware to reinstall but then the lagging/error messages continue. I'll try it anyway though, thanks
Click to expand...
Click to collapse
Well, it worked for me when Odin failed. Unless you actually have harware damage there should be a way to recover. GL