Okay, A little background quick! I just signed up for XDA because I have been lurking all day, and everyone seems to have their problems solved fairly quickly. Unfortunately none of the fixes here have helped me.
I was running KitKat for a while on my Verizon Galaxy Note 2 SCH-I605. I started having trouble with my SD card and it seemed my only route to fixing it was to root. Initially I was ignorant and used some one click solution. It certainly rooted my device, but it did not unlock my bootloader and when I tried accessing CWM Recovery my phone soft bricked. I proceeded to download ODIN and my phone's stock firmware. I flashed it and fixed my phone.
At this point I should have said goodbye to rooting, but I am a stupid stupid man. I flashed a rooted stock for my phone and it worked, but once again running CWM soft bricked me. I tried a few different things, rooting and trying to get things to work - flashing stock whenever I soft bricked again. Eventually, for whatever reason, ODIN froze when flashing STOCK. This was right around where I was giving up on the whole escapade. I an Install Firmware error and a message for KIES to repair it. I looked online, but none of the methods seemed to fix it. VZW Upgrade Assistant didn't help, and KIES won't either.
The Crux of the Problem:
I managed to get my phone in download mode and in a state of relief flashed stock to fix my phone and leave this all behind. Odin flashed, it all went well. I was very careful to follow the proper steps to ensure a proper flash of stock. Odin went through all its steps, my phone went to reboot. This time odin said PASS! before my phone finished rebooting. Now my phone is just sitting on the screen that says "Samsung GALAXY Note II". I can get to the download screen still, but I can not get to recovery to factory reset.
I know I screwed up on this, please don't tell me everything I should and shouldn't have done. I know i shouldn't have done any of this. I just want some help putting this behind me, whatever the cost. Please help me out guys!
Guys
Please help! I absolutely need my phone, and my only alternative is buying a new one. My older phones have batteries that last 5 minutes tops. Please help me here! I don't have Almost a grand for a new phone!
OMG
I got it! Fixed! After 7 hours of deep searching and experimentation I found the cure for my phone! All the things I was doing! It was so simple! Unfortunately it landed me back with KitKat Stock (Whatever, I'll deal with it), but it saved me. I flashed 4.3 Stock that I got from SamFirmware!
This is a newer firmware than I had before, but so be it! I'm so estatic!
Thank you guys! A lot of the info I found tonight was throughout the forums. No one thing here fixed my issue, but a combination of the threads here brought me to this conclusion! You guys are the bomb! Have a wonderful day!
Good job man
Sent from my SCH-I605 using Tapatalk
And your method was???? lol... I was helping my friend unroot from stock rooted with twrp, and my method was to start fresh with a stock 4.3 i found at samsfirmware. I used odin 3.09 and all went well until it finished and was boot looping (more of a flash). I tried the normal go to recovery and wipe davlik and factory reset but i cant get into recovery. So next i tried to re flash and once that didnt work i made sure my note 2 drivers were up to date. And here I am still cant flash and cant figure anything out and still cant flash. Below is what it shows for me, but yea if you could share what you did it would be so helpful!
:<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Related
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Fuzz21 said:
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Click to expand...
Click to collapse
Yeah, I'm reading this now. I just did what it said, but still no dice.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
I had a problem with mine where Odin wasn't doing anything at all. It would start but never finished. I changed the USB port and was good after that. Weird because my sgs2 and sgs3 international were fine using the one USB port. Just a thought to try a different port if it stops or fails
Sent from my SGH-I747M using xda app-developers app
brfield said:
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
Click to expand...
Click to collapse
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Problem solved!
JibbsIsMe said:
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Click to expand...
Click to collapse
OK, I got it. First, I followed this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I stopped right after step 8. I then put my Ext SD into my old phone, formatted it, and put on this: http://forum.xda-developers.com/showthread.php?t=1732191
Then I went into recovery, and flashed that ROM. Then rebooted, and I'm fine now! YAY!
I almost wasted $730....
--Jeremy
Awesome stuff !!
Mine is still a 500$ paper weight, LOL hopefully I can fix it :S
Good luck, I would hate to lose my phone on it's first day...
JibbsIsMe said:
Good luck, I would hate to lose my phone on it's first day...
Click to expand...
Click to collapse
Thanks budd
I really hope I can resurrect it from the Dead.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
I hate to threadjack, but this is the only thread I can find mention of this error with the sgs3 with.
mine did the same thing last night, thought I bricked.. but it didnt brick, used the phone all day today with no problems, tried to root again today with at&t method with odin, and I keep getting the same error. Its a bell i747m using odin 3.0.7
Any ideas?
Edit: Also I have tried several usb ports and a couple different cables.
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dmonger11b said:
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2280680
Sent from my SCH-I605 using XDA Premium HD app
dmonger11b said:
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Click to expand...
Click to collapse
It's been a while since I've done any troubleshooting, but checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
larry_thagr81 said:
It's been a while since I've done any troubleshooting, but checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
Click to expand...
Click to collapse
Awesome thank you. Worked perfectly. I feel kinda embarrassed I didn't look in Adam's thread. But the issue was caused by something a little different than what he warned against. Either way phone booted back up. Definitely irritated I didn't look better,
Glad I could point you in the right direction.
Hello to all the devs in the forum and thanks in advance for the help that you will give me. Please bear with me, trust me I have made sure that seeking for help was my last resort seeing as I don't want to be just another guy with a bricked phone problem. Fortunately the forum has been quite educational and I have all you guys to thank you for that.
Now then, last night I decided to root my phone because it was running a bit slow and decided it was time to do it.
Everything went fine, I managed to root it successfully, installed Clockwork Recovery and all that, although when it said that backing up the image I think was an error, I sort of just disregarded it. I booted up my phone and everything is fine, I installed Titanium Backup Pro and deleted some of the bloatware that was in my phone.
Now this probably where my phone got on its way to being bricked.
Along with the bloatware that was deemed safe on the website, I also mindlessly uninstalled the Samsung Home and probably the stock keyboard app.
I deemed them unnecessary because I was running Go Launcher EX app as my launcher and Swiftkey as my keyboard app.
What I didn't know is that all the custom roms are probably going to be using those stock apps as base. Did I assume this correctly?
So then I tried to flash the custom rom that I found appealing, followed the steps in the guide that accompanied it, and when rebooted it, it was stuck in the Samsung logo screen.
Fortunately I planned ahead a bit, although not as much as I'd hope for, I knew that I can restore through CWM but unfortunately, the restore point that it created presented with an error and I can't restore it.
So I resorted to flashing a stock rom through ODIN and followed the steps in unbricking the phone.
I encountered some difficulties with regard to the drivers and all that but I managed to have the correct ones installed.
Now comes the final problem
As I am trying to have ODIN flash the stock rom, it wouldn't continue as it does in the videos that I watched. It would always stop in about 10 seconds and say that it failed.
I tried another stock rom from a different location and it still wouldn't work.
I have also run ODIN as an administrator, and this presented:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iDXMC1_S5830iOLBLD1_S5830iDXMC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> BcmCP.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Again it only took about 10 seconds to stop.
I am running ODIN 3 v1.85
I have also uninstalled KIES.
Whenever I would cleared all the cache and mount everything sometimes it would bring me to the android setup at startup, but if I try to type there is no keyboard that would popup. And if I choose skip it, it's just black, but if I lock it, the blue stock lockscreen appears. Nothing else after that.
I decided to post as a last resort and knowing that I have done all in my ability to repair it.
So there it is, I tried to be as specific as possible to the things that I have done throughout the day,
A couple of solutions I found as I searched was to try to flash a stock rom through CWM, another suggested to use a different version of ODIN.
If someone could please point me to the right direction as to how to repair my device, it would be hugely appreciated.
Thank you very much for your time.
UPDATE: While I'm writing this I tried the latest version of ODIN and it still won't work. Same issue. Please help
See first of all Split the Firmware into 3 Parts PDA & MODEM & CSC then use pit file also ..
Ok now follow these
1.Go into recovery mod do wipe data/Cache
2.Get into CWM again do wipe data/cache
3.Now take down it into download mode and flash the Stock firmware .
Hope these works .
Hitesh2626 said:
See first of all Split the Firmware into 3 Parts PDA & MODEM & CSC then use pit file also ..
Ok now follow these
1.Go into recovery mod do wipe data/Cache
2.Get into CWM again do wipe data/cache
3.Now take down it into download mode and flash the Stock firmware .
Hope these works .
Click to expand...
Click to collapse
Hello Hitesh! Thank you so much for your correspondence. I've been seeing your consistent replies to people who have the same problem as I had.
As for my phone, I managed to unbrick it yesterday by flashing a different custom ROM through CWM. I am currently running Extremis 2.1 from destructo570
Again thank you very much for your help.
As an advice to anyone who will have the same problem in the future, make sure that before you install a custom ROM to clear the cache and all that. Good luck!
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!