So I forgot to freeze/remove KNOX from my S4 when I flash CWM recovery. I ended up with the "System software not authorized by AT&T has been found on your phone" message. I tried to download the firmware from Samsung and flash it with Odin, but Odin failed to work. Right now my phone is a useless brick and nothing I can find has any effect. Is there a way to remove KNOX or change my recovery back to stock? How do I make Odin work properly?
What is the error that you are getting? The issue is that the phone has a locked bootloader, so you are unable to use custom recoveries like CWM or TWRP.
es0tericcha0s said:
What is the error that you are getting? The issue is that the phone has a locked bootloader, so you are unable to use custom recoveries like CWM or TWRP.
Click to expand...
Click to collapse
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_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>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Nynten said:
So I forgot to freeze/remove KNOX from my S4 when I flash CWM recovery. I ended up with the "System software not authorized by AT&T has been found on your phone" message. I tried to download the firmware from Samsung and flash it with Odin, but Odin failed to work. Right now my phone is a useless brick and nothing I can find has any effect. Is there a way to remove KNOX or change my recovery back to stock? How do I make Odin work properly?
Click to expand...
Click to collapse
If Odin fails to work when you try to flash the firmware, then try to flash the ROM again, but without closing Odin. Sometimes we have to try like 5 times for it to work.
It's failing at flashing the aboot, then this is typically a result of trying to downgrade to an earlier version that is not supported after a more current bootloader has already been installed. Repeatedly flashing is not going to help. You will need to download a firmware that is the same or newer than the currently installed version.
es0tericcha0s said:
It's failing at flashing the aboot, then this is typically a result of trying to downgrade to an earlier version that is not supported after a more current bootloader has already been installed. Repeatedly flashing is not going to help. You will need to download a firmware that is the same or newer than the currently installed version.
Click to expand...
Click to collapse
I downloaded this firmware off of Samsung's website, I didn't think that it would be out of date.
Nynten said:
I downloaded this firmware off of Samsung's website, I didn't think that it would be out of date.
Click to expand...
Click to collapse
Most likely it is out of date since that update is 4.2.2 and I believe the one the phone shipped with. Most phones have been updated since then.
http://forum.xda-developers.com/showpost.php?p=53758259&postcount=2
NB1 is the last official full firmware to be able to restore. After that, you can update via OTA or follow the links in that post to update to newer versions of Kit Kat or Lollipop.
es0tericcha0s said:
Most likely it is out of date since that update is 4.2.2 and I believe the one the phone shipped with. Most phones have been updated since then.
http://forum.xda-developers.com/showpost.php?p=53758259&postcount=2
NB1 is the last official full firmware to be able to restore. After that, you can update via OTA or follow the links in that post to update to newer versions of Kit Kat or Lollipop.
Click to expand...
Click to collapse
Thanks, worked perfectly.
:good::highfive::victory:
Related
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
I tried again using I9300XXEMC3 stock rom, but odin 3.04 says
<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> tz.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)
Click to expand...
Click to collapse
And fails. My phone says "unsupported dev_type" in red.
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
zhinkk said:
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
TheoDores said:
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
Click to expand...
Click to collapse
I tried following those instructions. I managed to flash the .PIT file. Now I don't see the error message at boot, my screen is just black. BUT I can "sorta" boot into recovery mode (starting recovery message shows for one second, then black screen again). So I'm still stuck.
I can STILL boot into download mode though. And if I try to use CF-Root Odin fails again (same error) and my phone says "unsupported_devtype".
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
JJEgan said:
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
Click to expand...
Click to collapse
Everytime I flash the stock rom odin fails and phone says "unsupported dev_type". In Download mode it says my phone model is T999, but it's actual GT-I9300.
And I don't think I did. I think I had clockwork mod recovery, I'm not too sure though.
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
boomboomer said:
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
Click to expand...
Click to collapse
That really depresses me. Are you sure this is the only solution? Because I remember when my phone WAS working I booted into download mode once and it said the same "T999 Model" and I could still use it. This only happened after I tried flashing the stock i9300 stock rom.
I think it's the cyanogenmod installer that flashed this T999 bootloader for me. When I used the cyanogenmod installer it detected my phone as a AT&T phone and I was dumb enough to click "install" thinking it would work for all galaxy S3's.
I think this guide is exactly what I need (since it restores bootloader), but I can't seem to complete all the steps: http://forum.xda-developers.com/showthread.php?t=2535367
I get to #5 but once I try to install CF-ROOT through odin it says the same unsupported dev type error on my phone.
This is the error I get when trying to use CF-ROOT through Odin3 v1.85:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
(along with the red "Unsupported dev_type" on my phone in download mode).
I think it was already rooted though, maybe someone could help me reinstall the recovery (cwm) so I can install the bootloader from that guide I just linked?
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Will this delete my EFS? I remember I backed up efs with this guide: http://forum.xda-developers.com/showthread.php?t=1852255
I did: "adb reboot nvbackup"
By restoring to "complete" factory settings, won't this efs be deleted? Can I still backup my efs in my 'soft brick' mode I'm in?
Alright, I've tried using the rescure firmware and all the files, but every time I try I get it a FAIL on odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And my phone says in red "SECURE CHECK FAIL : PIT".
I've spent 12 hours on this now...
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
DualJoe said:
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
Click to expand...
Click to collapse
I tried Kies on two different computers, but whenever I connect my S3 it just says "connecting" forever and never connects to my phone. Tried solutions online, couldn't get it to work.
And I have root access, but can't boot into recovery (says "recovery booting" for a few seconds then goes black screen). So I don't know if I can flash the bootloader manually, unless I did it with odin.
And those seem like busy developers, would they really have time for me? I don't even know what I would ask. :S
Sorry I seem so clueless, I'm just upset/sad/confused/everything right now. Saved up for this phone for a while.
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
DualJoe said:
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
Click to expand...
Click to collapse
Hmm when I had a functional phone it said I had the ZSEMC1 stock rom, so the "bootLoader_ZSEMC1.tar.md5" flashed from odin should work? I got it off this thread: http://forum.xda-developers.com/showthread.php?t=2189063
But I don't know if I'm still on ZSEMC1 since I flashed XXEMC3 with odin (but I think it failed) and I got soft bricked.
What could go wrong? Could I hard brick it by installing that bootloader?
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
DualJoe said:
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
Click to expand...
Click to collapse
I tried the ZSEMC1 and XXEMC3 and XXEMG5 bootloaders from this thread and they didn't work: http://forum.xda-developers.com/showthread.php?t=2189063
(shows unsupported dev type)
How do I get the 'latest' boot loader? That thread is the only one I could really find.
And also I did try installing cwm through odin. It didn't "fail" but it doesn't work when I try to boot into recovery. I'm guessing this has to do with my locked bootloader?
Really don't know what to do at this point. :/
New motherboard if you have tried the fixes .
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
DualJoe said:
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
Click to expand...
Click to collapse
I tried cwm and twrp. They both install successfully on odin but have the same "recovery starting...." message and they don't work. I've tried connecting the USB when it's in this "recovery" mode but my computer doesn't detect it so I can't start up adb and interface with it.
And also, I doubt I'm going to be able to find any in northwest ohio.I wonder if this service is any good?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Looks promising for $50.
Sorry I've been on this problem for so long guys, I'm just stubborn and can't get over the fact that it's a software brick and I need to replace hardware. :/
How can I fix this? I want to go back to stock. No root. Please see below.
<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> 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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
I need help with this ASAP.
If you haven't found it already, go to Droidstyle's Restore Guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ). Section 1b has step by step instructions on how to restore the phone. Make sure you use the pit file with the correct firmware version when doing the restore.
Unless you have a Note 2 that never had a firmware update since the phone's release in 2012, then you can't use the VRALJB stock restore image. Droidstyle warned that it would fail at sboot.bin if you try it. Also, if you ever upgraded to 4.4.2, then you can't downgrade back to 4.3 or 4.1.2 because of bootloader issues.
If your phone is currently on 4.1.2 bootloader, then you can restore back to that firmware version. If it's on 4.3 bootloader, then restore back to that... and if it's on 4.4.2, then restore back to that. After returning the phone to Stock, boot into recovery and wipe cache & do a factory reset... as Odin doesn't seem to fully wipe everything.
Droidstyle's link for 4.1.2 looks to be down.... but recognized XDA Developer imnuts has the 4.1.2 VRAMC3 Odin file on his Android File Host site here: https://www.androidfilehost.com/?fid=23159073880932932
Also...if needed, here's a link to the Verizon stock 4.4.2 firmware: ( http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/ ).
Good luck!!
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
GiantsFan91 said:
I can't get in bootloader. I press up vol + home button + power. No good.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Volume up+home+power button would put phone in Recovery mode if it was functioning properly.
You need to use Volume Down+Home+Power button to put the phone back into Odin mode (aka Download mode). From there, you can Odin flash the appropriate firmware to restore the phone. If you're not sure what version of Android you had on the phone before you tried to restore it... then I'm not sure which version you should use.
I used 4.1.1 Jelly bean.
GiantsFan91 said:
I used 4.1.1 Jelly bean.
Click to expand...
Click to collapse
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
I downloaded CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar and fail! I put sch-i605-16gb.pit and CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar. No good.
mattnmag said:
But that attempt to flash 4.1.1 failed at sboot.bin... so you'll need to restore to whatever version you were on before to tried that.
Click to expand...
Click to collapse
How? I have no recovery. I can't get in recovery.
You need to put phone into download mode to restore with ODIN... not into recovery.
I did..i restore with ODIN. No good.
You tried to restore back to 4.1.1. It will fail at sboot.bin every time and won't work. You need to restore back to a different firmware version.... whatever version you were on before you tried to Odin flash the 4.1.1 firmware. If your phone was updated to the newest 4.4.2 firmware them you will only be able to restore back to that firmware version because the bootloader is locked.
Bricked Galaxy Note 2 while updating to 4.3
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
christherock said:
Hello I am a new member i recently tried to update the Galaxy Note 2 to Android 4.3 through Odin using stock firmware i downloaded from Sammobile.com and it went through successfully but the phone is now stuck on the Samsung logo and will not go any further, I need some help with this ASAP as the phone does not belong to me, I was trying to update it for a friend like i updated mine but i have not run into an issue like this before. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
tried that
mattnmag said:
Try to boot the phone into Stock recovery by holding volume up+home button +power buttons all together until it boots into the stock recovery. Then wipe cache and do a factory reset. Hopefully that will fix things.
Click to expand...
Click to collapse
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
<ID:0/004> Added!!
<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> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i used file name I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5
and i used pit file sch-i605-16gb.pit
as stated before im still kind of new at this so any information you could provide me would help a ton.
christherock said:
i tried to do that but the phone will not allow me to enter recovery mode, only 2 screens i seem to be able to access is the Odin download screen and the perpetual Samsung Galaxy NoteII screen, i did the update through Odin 3.9.0 and it took the update on Odin just fine but the phone wont boot up all the way, this is the script from Odin
Click to expand...
Click to collapse
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
the phone was on 4.1.2 before i attempted the update
mattnmag said:
If the phone was on 4.4.2 before you tried to Odin flash 4.3, then you will need to reflash 4.4.2 back onto the phone. You can not downgrade the phone to any previous Android versions because of the locked bootloader on the SCH-I605.
The log from Odin looks ok to me, so it sounds like something must be corrupted on the phone. Since you can't get into Stock recovery to wipe things.... then you might try 4.4.2 since 4.3 won't seem to work.
4.4.2 is not as easy to root as 4.3, but there is a root method called GhettoRoot that works on 4.4.2.
Click to expand...
Click to collapse
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
christherock said:
i am not interested in rooting it im more concerned on getting it to boot up all the way, i get all of my firmware from sammobile but i cant seem to find the firmware for 4.4.2 on there, if you have a link of where i could find it that would be very helpful as well. please im kinda desperate here lol
Click to expand...
Click to collapse
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW/
found it
mattnmag said:
On the sammobile website, you should be able to click Firmware, then enter GALAXY Note II and pick (SCH-I605).
Here's a direct link that should work:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
christherock said:
ok just found it its downloading ill keep you posted if it works or not, i doubled checked and it is a 16gb, do i need to use the .pit file or no?
Click to expand...
Click to collapse
I would still use the pit file. If you follow Droidstyle's Restore guide, (but just use the ODIN 3.10 version and the 4.4.2 firmware from Sammobile)... that will hopefully help you to get it restored.
The Sammobile site says not to have the repartition box checked.... but if you use the pit file, it automatically ticks the repartition box (which is what it's supposed to do.... so leave it ticked when using the pit file).
PS: Also make sure you're right clicking on ODIN and running it as Administrator....and disable all antivirus programs and close other running programs in the background when running Odin.
If your friend doesn't want the phone on 4.4.2 and it was never on 4.4.2 previously, then you could try reflashing 4.3 onto the phone using Odin 3.10 just to see if it would work with the newer Odin version. If it doesn't work, you could try 4.4.2.
Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.
I had this problem with ODIN 3.10.6
Log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925IDVU2COF8_G925IODD2COF8_G925IDVU2COF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I want to update my firmware to Lollipop 5.1.1, I have Lollipop 5.0.2 and my carrier is WIND MOBILE (Canada).
I´ve used the Indian stock rom from sammmobile and I´ve tried with other pc, other port usb, other cable and always is the same problem. What can I do? Please help me. Thanks.
Is the phone still locked?? Is the same csc that you're trying to flash??
marcochapita said:
Is the phone still locked?? Is the same csc that you're trying to flash??
Click to expand...
Click to collapse
No, I´m using Stock rom from India and my stock rom is from Canada, so, is not the same CSC. And are you talking about that my phone is locked to others companies? If is that, the reply is YES, still locked.
jonmagia said:
No, I´m using Stock rom from India and my stock rom is from Canada, so, is not the same CSC. And are you talking about that my phone is locked to others companies? If is that, the reply is YES, still locked.
Click to expand...
Click to collapse
if you are using a ROM form a different country, it could be built for a different Variant.
Try a Canadian Stock 5.1.1 ROM.
Word of warning, you cannot Downgrade from 5.1.1 to 5.0.2
Mischala said:
if you are using a ROM form a different country, it could be built for a different Variant.
Try a Canadian Stock 5.1.1 ROM.
Word of warning, you cannot Downgrade from 5.1.1 to 5.0.2
Click to expand...
Click to collapse
Yeah, the problem is: We haven´t Lollipop 5.1.1 in Canada yet.
Odin stuck in NAND Write
I m also having same problem Odin stuck in NAND Write.
I have used odin 3.10.6 and 3.10.7 that too on 2 PCs and also tried rebooting PC but nothing worked.
I tried flashing Original FW as well as Upgrade ie 5.1.1. but result is still Fail in NAND write. Smart switch says G9250 doesn't support initialisation
Plz help
My phone is SM-G9250, CSC-TGY.
This might sound crazy but I had the same problem and I had a defective new Samsung USB cable!
I spent hours trying to flash stock firmware!
Only when I used another cable Odin 3.10.6 passed first time!
Solution!
Try to wipe everything on your phone via CUSTOM RECOVERY, DONT WIPE YOUR SDCARD!!! (do not touch the odin settings unless you exactly know what they do!)
Try TWRP:
TWRP: twrp.me/Devices/
This will most likely work because then it will clean flash/install your rom.
jonmagia said:
No, I´m using Stock rom from India and my stock rom is from Canada, so, is not the same CSC. And are you talking about that my phone is locked to others companies? If is that, the reply is YES, still locked.
Click to expand...
Click to collapse
If you have the phone locked, i think that you can't flash anything unless you unlock the bl. Try to flash the stock rom with a oldest version of ODIN (ex 3.07/3.00 or oldest...)
Hi guys. I have a galaxy s6 that I tried to flash with official firmware 5.1.1 via odin. I was rooted before that. The flash failed and now it says to use Verizon's software utility to restore the phone. That utility doesn't work and the reps at the store had never heard of it.I literally can't fix the thing. No amount of flashing in download mode helps. It always fails.
Anyway, I went to Verizon and they are sending me a replacement in two days. In download mode it still says that the firmware is official. However it also says samsung custom. (Assuming the root) I don't know if Verizon will backcharge me for this. Is there any way to get rid of the custom status? When I put it in the box to return it I'll leave it on the System Software Update Failed screen.
Remember I can't flash via odin, that just fails. Samsung smartswitch doesn't recognize the device. Recovery mode is a no go.
Thanks for the help!
What's the error message in Odin?
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
es0tericcha0s said:
What's the error message in Odin?
Click to expand...
Click to collapse
in seems to always fail. I can go back to download mode or be instructed to restore via Verizon's software assistant. Here is what odin has to say. It fails at the system.img Verizon G920V
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mrao said:
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
Click to expand...
Click to collapse
I was not on 5.1.1 at the time. I downloaded 5.1.1 from sammobile or one of the other firmware hosting sites. I also tried 5.0.2 but that gives me a nand error.
Would perhaps flashing a pit file work? The problem is the the one firmware I originally tried to flash (5.1.1) doesn't have a pit file. The other firmware 5.0.2 does have one but it's only 4kb. I'm not sure if that's right.
Just in case anyone finds this in the future. I figured out how to fix this. I had have a working phone to install verizon's upgrade assitant. It would not work from the exe I found on the internet. From there I had to install it in a virtual machine because it did not like Win 10. From there I simply plugged in my device and it restored it. Use this method if odin doesn't work. I WILL NEVER ROOT AGAIN!
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
es0tericcha0s said:
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
Click to expand...
Click to collapse
Odin failed a flash and I could not reflash with odin again. I don't ever want to have that happen again. It wasn't the firmware I triple verified it before I flashed it. It was the correct firmware.