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
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've run custom ROMs on every Android I've owned, and have never bricked a phone with even the sketchiest of ROMs. Then, I decide to sell my i337 jfltecan, but the buyer wants stock (instead of my CM nightlies - a fair request). So I download a stock image and try to flash with ODIN. Flash fails, and now nothing else will flash back onto it either. Can't get recovery to load, I just get an error saying to attempt recovery in Kies. Kies just hands at "Connecting...."
It's not urgent, because as mentioned, I'm selling the phone, not relying on it for my daily use. But - have I bricked it permanently?
Here's the ODIN error I get when trying to flash TWRP:
----
<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> Removed!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Try downloading and flashing the files via Odin from the Mega link on this page:
http://forum.xda-developers.com/showthread.php?t=2504311
If all else fails, take it down to best buy, play stupid, and they might flash stock for you.
What firmware were you on prior to flashing?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
This is one of those solutions that I never believe when I read it....
I tried four different USB ports....one of them, on a hub, worked. Case ports, and motherboard ports didn't. But one lone port on a hub did.
I even reproduced this phenomena on another Samsung phone out of pure curiosity. Same results. Must be a magic port! I can't explain this.
Side note - BestBuy can flash phones? I'm usually lucky if the staff at my BestBuy know the difference between megabytes and megapixels.
rhd-android said:
This is one of those solutions that I never believe when I read it....
I tried four different USB ports....one of them, on a hub, worked. Case ports, and motherboard ports didn't. But one lone port on a hub did.
I even reproduced this phenomena on another Samsung phone out of pure curiosity. Same results. Must be a magic port! I can't explain this.
Side note - BestBuy can flash phones? I'm usually lucky if the staff at my BestBuy know the difference between megabytes and megapixels.
Click to expand...
Click to collapse
Trust us who have been there. Now you're one of us
Astrophysicist789 said:
Try downloading and flashing the files via Odin from the Mega link on this page:
http://forum.xda-developers.com/showthread.php?t=2504311
If all else fails, take it down to best buy, play stupid, and they might flash stock for you.
Click to expand...
Click to collapse
Does anyone happen to know if Canadian Best buy's offer this service?
I've been searching and found many threads but none that said what to do next in this situation.
I was trying out different roms and then it would not load past the sammy logo. This kept me from loading safestrap and fixing it.
I tried using odin to install stock rom.
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After that I tried different cables, usb ports, restarting the pc / phone, wiping cashe, factory reset and reinstalling kies. I made sure kies was not working in the background.
So far this is what I got from reading many different threads. Any Ideas?
I know you guys get stories like this a lot and it does get tiresome, but it would mean a lot to me if you help me out. Thanks.
So is my nand messed up? What does that mean?
Here is a thread that is similar but I don't think it will work for me.
http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867
I'll try my best to help out...I just Odin back to stock 5 minutes ago... what files are you using for Odin and what Odin version do you have?
Have you look at this thread? This help me out a lot
http://forum.xda-developers.com/showthread.php?t=2926642
stric85 said:
I'll try my best to help out...I just Odin back to stock 5 minutes ago... what files are you using for Odin and what Odin version do you have?
http://forum.xda-developers.com/showthread.php?t=2926642
Click to expand...
Click to collapse
I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5
Odin3v185
Thank you very much for your help.
Trying out the files in the thread you posted. Odin is definitely different and the stock rom probably is too.
Wow worked like a charm! Thanks bro! I guess I had the wrong files? funny because I got them from galaxys4root and I have never had a problem before.
Got a paypal? I would have been willing to pay someone to fix this. It wont be much but I want to say thanks.
darkmx-6 said:
Wow worked like a charm! Thanks bro! I guess I had the wrong files? funny because I got them from galaxys4root and I have never had a problem before.
Got a paypal? I would have been willing to pay someone to fix this. It wont be much but I want to say thanks.
Click to expand...
Click to collapse
Glad it worked! I just pointed you to the thread I used to Odin to stock on my s4, you did the rest.[emoji1] Thanks for letting me know I could be of little help!
I think I need some help from someone. I have a Galaxy S7 Edge (tmo) with the rom of a G935U from last year i believe It was originally a G935T from the store. I flashed a G935U Rom and it was all fine and dandy. Now, I want to go back to stock, so i downloaded TMB_G935TUVU3APG1 firmware and used Odin 3.12 Prince Comsy version and loaded up the AP, BL, CSC, CP. (I have the Samsung USB Drivers installed)
I then clicked on "start" and then got this error: constantly bootloop the "recovery booting"
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to use a different firmware version and now my phone says "An error has occured while updating device software. Use the emergency recovery function in Smart Switch PC Software"
I installed Smart Switch, loaded it up, plugged in my phone, and Its saying "Unsupported Device"
I tried going into Emergency Software Recovery but I don't think it works (or im not doing it right). I click on "device initialization" tab and enter my phone model "SM-G935T" without quotes and it keeps telling me "please check the model name and enter it"
I am so stuck. I really hope someone can help me out. I have never had any issues before this.
EDIT: Still stuck, but got into Smart Switch and it was able to download a new rom, but when it tried to apply the rom to my phone, it came back with an error " Failed to update software due to an error. Do you want to run emergency Software Recovery?" and when i click "Emergency Recovery" nothing happens.
EDIT 2 : Retried with latest firmware. Error details below.
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well, first off you're flashing old firmware. Download the latest firmware (Which for the 935U is QD2: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/), not just any random firmware you find.
Get back into DL mode and flash again using the modded Odin. Hold power, home and volume down. Eventually it'll restart in Download mode.
For best reults, Flash the QD2 files in Odin but for CP use the QE1 modem. (I made a thread with a link to DL from my Google Drive. Yes, you'll need to DL 2 firmwares. One U and One T firmware but all you want is the CP file from the QE1. Yes, it'll flash fine and it will give you much better signal. Latest U firmwares have had **** signal.)
joe3681 said:
Well, first off you're flashing old firmware. Download the latest firmware (Which for the 935U is QD2: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/), not just any random firmware you find.
Get back into DL mode and flash again using the modded Odin. Hold power, home and volume down. Eventually it'll restart in Download mode.
For best reults, Flash the QD2 files in Odin but for CP use the QE1 modem. (I made a thread with a link to DL from my Google Drive. Yes, you'll need to DL 2 firmwares. One U and One T firmware but all you want is the CP file from the QE1. Yes, it'll flash fine and it will give you much better signal. Latest U firmwares have had **** signal.)
Click to expand...
Click to collapse
So what is the newest firmware for the 935T? Because after using Smart Switch and having it attempt to fix my phone, it now reads as a 935T in Download mode. Do i still want both firmwares if I am going back to stock?
EDIT: After doing some quick searching, 930TUVS4BQC1 looks like the latest 935T firmware. So I would flash all but the CP from the 930TUVS4BQC1 and then flash the CP from the QE1 firmware? Not sure if it makes a difference, but I was NOT on Nougat when this issue occured.
Forkinator said:
So what is the newest firmware for the 935T? Because after using Smart Switch and having it attempt to fix my phone, it now reads as a 935T in Download mode. Do i still want both firmwares if I am going back to stock?
Click to expand...
Click to collapse
Doesn't matter, you can still flash U fw. If you want completely stock TMobile, find my thread of QE1. It's the latest, bone stock TMobile firmware.
joe3681 said:
Doesn't matter, you can still flash U fw. If you want completely stock TMobile, find my thread of QE1. It's the latest, bone stock TMobile firmware.
Click to expand...
Click to collapse
Alright I have a decent internet connection so i did as you said, Used the modem (CP) from QE1 and the BD, CSC, AP from QD2. At least this error was different. I don't normally have these issues so I am so lost and worried right now.
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
1. Try a better/different cable or port
2. Remove the .md5 off the end of each file name and try again
joe3681 said:
1. Try a better/different cable or port
2. Remove the .md5 off the end of each file name and try again
Click to expand...
Click to collapse
WTF!
Dude seriously wtf. It worked! I changed ports, and used a different cable.
I am in awe right now. I don't know what to say besides THANK YOU, YOU GLORIOUS BASTARD!
On a serious note, I don't know why that would have worked. I have always used the port/cable to flash roms. Thanks man, I went to T-mobile earlier and they said i would have to wait till tuesday for a new phone. Going to call them and tell them my phone fixed itself
You really saved me man. I wish there were more people like you. Definitely gonna donate to you.
Forkinator said:
WTF!
Dude seriously wtf. It worked! I changed ports, and used a different cable.
I am in awe right now. I don't know what to say besides THANK YOU, YOU GLORIOUS BASTARD!
On a serious note, I don't know why that would have worked. I have always used the port/cable to flash roms. Thanks man, I went to T-mobile earlier and they said i would have to wait till tuesday for a new phone. Going to call them and tell them my phone fixed itself
You really saved me man. I wish there were more people like you. Definitely gonna donate to you.
Click to expand...
Click to collapse
Thank you!!! I definitely appreciate it! Glad I could get you goin again!
joe3681 said:
Thank you!!! I definitely appreciate it! Glad I could get you goin again!
Click to expand...
Click to collapse
Seriously dude. When you go to bed tonight, remember, you helped a dumbass get his phone working(I know you have helped a lot of people)! Should give you warm fuzzies.
Hope that donation went through. Have a good one!
I'm just reading your message and can say I have a s7 cord and it won't even charge my phone anymore so yes
"WACK CORDS MATTER" when it comes to flashing.
g1-and-only said:
I'm just reading your message and can say I have a s7 cord and it won't even charge my phone anymore so yes
"WACK CORDS MATTER" when it comes to flashing.
Click to expand...
Click to collapse
This is so strange though. It must have happened between the last time I changed firmware and now. I always keep my cords in excellent condition and use the ones that came with the phone if possible.