I am trying to unroot my verizon s4 and i tried 2 different files and each of them fail in ODIN. Can somone PM or reply with a link for a stock ROM so i can unroot my S4, i need to sell it tomorrow. It won't let me do a factory reset when im rooted. IDK if this matters i originally rooted when i was on MDK then took the OTA update to ME7 so im currently on ME7. Now i cant turn my phone on it just boots to the screen that says "firmware upgrade encountered an issue. please select recovery mode in Kies & try again."
svtcobra said:
I am trying to unroot my verizon s4 and i tried 2 different files and each of them fail in ODIN. Can somone PM or reply with a link for a stock ROM so i can unroot my S4, i need to sell it tomorrow. It won't let me do a factory reset when im rooted. IDK if this matters i originally rooted when i was on MDK then took the OTA update to ME7 so im currently on ME7. Now i cant turn my phone on it just boots to the screen that says "firmware upgrade encountered an issue. please select recovery mode in Kies & try again."
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301259
That should be all you need.
Related
I picked up a Verizon Galaxy S4 today, and it installed the OTA update.
Tonight I tried to root the phone, and it did not work, and now I can't get the phone to start back up. It gives me the "firmware update encountered an issue message."
I can get the phone into download mode, but I haven't been able to install a stock rom using ODIN. I think maybe I'm using the wrong ROM.
What should I be doing?
Mechachrome said:
I picked up a Verizon Galaxy S4 today, and it installed the OTA update.
Tonight I tried to root the phone, and it did not work, and now I can't get the phone to start back up. It gives me the "firmware update encountered an issue message."
I can get the phone into download mode, but I haven't been able to install a stock rom using ODIN. I think maybe I'm using the wrong ROM.
What should I be doing?
Click to expand...
Click to collapse
You're probably using the wrong ROM.
Which OTA? What baseband were you on prior to and after the OTA? What errors did you see in ODIN and on the phone.
If you were on MJ7 and updated to MK2, then you should be able to flash the MJ7 no-wipe ROM to recover.
Failing that, install Samsung Kies and use it to recover your phone.
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
cfales25 said:
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
Click to expand...
Click to collapse
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
es0tericcha0s said:
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
Click to expand...
Click to collapse
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
cfales25 said:
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
Click to expand...
Click to collapse
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
es0tericcha0s said:
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
Click to expand...
Click to collapse
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
cfales25 said:
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
Click to expand...
Click to collapse
You'll either need to use Heimdall or the http://casual-dev.com/2014/01/04/jodin3-web-browser-or-offline-flashing-tool/
Ok so i rooted my phone a bit back but i keep getting firmware upgrade notifications so i just wanted to unroot and be vanilla firmware. well i tried with Odin and it didnt work so im stuck in Odin mode and i cant get back to using the phone. Please HELP!
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Bascotie said:
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Click to expand...
Click to collapse
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
BluGuy said:
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
Click to expand...
Click to collapse
Good question. He doesn't really know as he was even newer to this than I am (I've done it on a couple phones in the past only a few times, so I do kinda have the hang of it, but this phone's a bit different).
Can I just try flashing 4.3 or above and see if that works? What would be the way to go if I don't know what was flashed previously?
I have the Verizon Galaxy s4 and I rooted it and attempted to install the cm-12.1 custom rom. I could not get CWM to work so I went to the safestrap route. My phone got stuck booting into recovery so I flashed stock everything VIA Odin. It failed. So now I'm stuck with the message at start up "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Please HELP.
P.S It is the SCH-I545 model.
WarCrazy said:
I have the Verizon Galaxy s4 and I rooted it and attempted to install the cm-12.1 custom rom. I could not get CWM to work so I went to the safestrap route. My phone got stuck booting into recovery so I flashed stock everything VIA Odin. It failed. So now I'm stuck with the message at start up "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Please HELP.
P.S It is the SCH-I545 model.
Click to expand...
Click to collapse
What were you on... CM-12 does not work on any bootloader besides MDK. It does not work with safestrap. It will not work with CWM. Odin with a FULL NC5 WIPE. If that does not work, its bricked. Possibly JTG, but I doubt it. Read more before you do something. This could have been avoided.
XxD34THxX said:
What were you on... CM-12 does not work on any bootloader besides MDK. It does not work with safestrap. It will not work with CWM. Odin with a FULL NC5 WIPE. If that does not work, its bricked. Possibly JTG, but I doubt it. Read more before you do something. This could have been avoided.
Click to expand...
Click to collapse
Well, I did everything from a different site instructions. But I appreciate the reply. I did thankfully fix my phone by connecting it to Kies which restored firmware. Problem now, I lost root access and I upgraded to 5.0.1 lollipop from 4.2.2 kitkat and I now can't seem to find a rooting option now. Running SCH-I545 VRUGOC1.
Can you point me to the right direction? I've decently looked around, don't see any way to do it?
WarCrazy said:
Well, I did everything from a different site instructions. But I appreciate the reply. I did thankfully fix my phone by connecting it to Kies which restored firmware. Problem now, I lost root access and I upgraded to 5.0.1 lollipop from 4.2.2 kitkat and I now can't seem to find a rooting option now. Running SCH-I545 VRUGOC1.
Can you point me to the right direction? I've decently looked around, don't see any way to do it?
Click to expand...
Click to collapse
No root for OC1. No downgrade either as a qfuse has been blown.