Hey guys, I had my phone rooted on 4.3 mk2 and I ended up removing it. But right now when I boot the phone, I have the custom splash screen. So I want to know if it's okay for me to take the update or do I have to Odin back to stock? I know there is no root for kitkat yet and I know everyone is against it but I am not worried about all of that.
Sent from my SCH-I545 using XDA Free mobile app
damnyouwaffles said:
Hey guys, I had my phone rooted on 4.3 mk2 and I ended up removing it. But right now when I boot the phone, I have the custom splash screen. So I want to know if it's okay for me to take the update or do I have to Odin back to stock? I know there is no root for kitkat yet and I know everyone is against it but I am not worried about all of that.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Hi I had the same issue. mk2, removed root. If you want to take the kit kat OTA update just follow the steps below. Beware you will lose root if you already havent. Kies does give you the option to back up your info if you want.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
Sent from my SCH-I545 using Tapatalk
Domvillan said:
Hi I had the same issue. mk2, removed root. If you want to take the kit kat OTA update just follow the steps below. Beware you will lose root if you already havent. Kies does give you the option to back up your info if you want.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Do I take the update from kies onto my phone? Or will that brick the whole thing?
Sent from my SCH-I545 using XDA Free mobile app
damnyouwaffles said:
Do I take the update from kies onto my phone? Or will that brick the whole thing?
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
When I tried Kies it said my firmware was up to date. I just reinstalled that. Not sure if Kies now has the update for 4.4
Sent from my SCH-I545 using Tapatalk
So could I just take the update? I want to restore to stock on with Odin and then take it but I have virtually no access to a computer that can run Odin because mine is fried.
Sent from my SCH-I545 using XDA Free mobile app
Related
I was rooted with TWRP. I flashed stock using VRUAMDK_NoWipe.tar. Phone boots and runs fine, but when in stock recovery I see a red triangle in the androids belly, When trying to install the new update, I get a update failed, error 402. Any ideas?
edlowjr said:
I was rooted with TWRP. I flashed stock using VRUAMDK_NoWipe.tar. Phone boots and runs fine, but when in stock recovery I see a red triangle in the androids belly, When trying to install the new update, I get a update failed, error 402. Any ideas?
Click to expand...
Click to collapse
All I know is that you need to be COMPLETELY STOCK. My assumption would be that NoWipe is leaving something behind that may be causing the problem. Otherwise it could be the flash count. I was getting the same problem and didn't want to risk trying triangle away so I called it quits.
Sent from my SCH-I545 using xda app-developers app
edlowjr said:
I was rooted with TWRP. I flashed stock using VRUAMDK_NoWipe.tar. Phone boots and runs fine, but when in stock recovery I see a red triangle in the androids belly, When trying to install the new update, I get a update failed, error 402. Any ideas?
Click to expand...
Click to collapse
I was stock rooted with cwm....I was also getting 402 after using no wipe..I wound up biting the bullet and flashed the full stock kernel...lost all my settings...hooked up the phone to the pc and installed the verizon update program...the new update came down with no problem....I did of course have to re customize my phone..no biggie since im a firm believer that you should do a factory restore after each update anyway
I was completely stock and rooted and updated whole retaining root.
Sent from my SCH-I545 ME7 Rooted using xda app-developers app
I'm having the same issue. Had the pre-release kernel and stock root just to freeze apps. Got the error on the update so did no wipe which didn't work. Tried doing complete .tar and .pit restore then update and still getting the error. Checked the count in TA and it was at 0. Tried tether update and failed. Now i'm trying the tether repair tool which is currently running.
Forgot i even tried installing just the stock kernel as well with no effect.
Delakit said:
I was completely stock and rooted and updated whole retaining root.
Sent from my SCH-I545 ME7 Rooted using xda app-developers app
Click to expand...
Click to collapse
Luck of the draw I guess. Not sure why it would work for me and no one else.
...sent from my SCH-I545 ME7 Rooted using xda app-developers app
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
james581 said:
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
Click to expand...
Click to collapse
Safestrap doesn't root, so there's things that you've done that you're not telling us. How did you root your phone? What else did you do after you rooted?
The "firmware detected issues" usually means that you tried to flash recovery, custom kernel, etc. Did you try to flash custom recovery?
james581 said:
Have a sch-i545 from verizon.it updated to mk2 . Went to safe strap root it and after if rebooted twice all the phone will do is go to download mode or stay on screen that says firmware has detected issues with software please go to Kies and update firmware. I did many times from different computers and every time it would download and stop and freeze computers. Anyone have any help.
Click to expand...
Click to collapse
How did u root your phone?
safestrap enabled, Hyperdrive driven
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
james581 said:
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Why were you in odin? What were you flashing?
james581 said:
I used get root link. Not safe strap my fault guys. I used Odin 3.7 and the o lyrics thing I did was put the tar.md5. Hit start and it had 1 fail but the phone did reboot twice and now says firmware needs updated.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I don't really know what's going on here as you're a little confusing but figured I'd chime in here..
If you were on mk2 then you should just rooted the phone using SafeRoot, very easy and reliable and Safe!
Then you should have installed SafeStrap by simply downloading the. Apk file from that thread. Boooom you'd be all set and ready to flash.
None of that requires Odin. Unless I missed the post where you said you were trying to Odin back for a fresh start??!!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
I don't really know what's going on here as you're a little confusing but figured I'd chime in here..
If you were on mk2 then you should just rooted the phone using SafeRoot, very easy and reliable and Safe!
Then you should have installed SafeStrap by simply downloading the. Apk file from that thread. Boooom you'd be all set and ready to flash.
None of that requires Odin. Unless I missed the post where you said you were trying to Odin back for a fresh start??!!
Click to expand...
Click to collapse
I used Odin because the get root string wasn't working it rooted phone then after a reboot it rebooted itself twice and went to screen saying firmware issue detected. but I b no longer have that phone I have a replacement one that followed safe root and everything working good to the best of my knowledge. . I am a noob and have a lot to learn. thanks for all the feedback.
Sent from my SCH-I545 using XDA Premium 4 mobile app[/QUOTE]
james581 said:
I used Odin because the get root string wasn't working it rooted phone then after a reboot it rebooted itself twice and went to screen saying firmware issue detected. but I b no longer have that phone I have a replacement one that followed safe root and everything working good to the best of my knowledge. . I am a noob and have a lot to learn. thanks for all the feedback.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
[/QUOTE]
a sticky thread is set up and is a WIP for S4 people in the general section to assist those who wish to mod their phones
http://forum.xda-developers.com/showthread.php?p=49335074
If you are on mk2 and want kitkat you know all about the OTA update fails with error 402. Below is a guide I threw together to walk you thru the process that worked for me.
******BEWARE YOU WILL LOSE ROOT*****
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC. (KIES gives an option to back up your data if you want to do that you can)
3. Once rebooted search for system update.(restore data from backup if you backed up your data)
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
Sent from my SCH-I545 using Tapatalk
Domvillan said:
If you are on mk2 and want kitkat you know all about the OTA update fails with error 402. Below is a guide I threw together to walk you thru the process that worked for me.
******BEWARE YOU WILL LOSE ROOT*****
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC. (KIES gives an option to back up your data if you want to do that you can)
3. Once rebooted search for system update.(restore data from backup if you backed up your data)
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Been looking for a solution, because Verizon update keeps giving me an error.
I will try when I get home to my holy Samsung USB cable, don't have one here at work.
will update when I know if it works. Thanks!
Anyone else try this? I am just rooted, no roms or anything on MK2
no modem flashes either or ss? the kies update should work fine. keep us posted!
i was on nc5. i accidentally installed this rom [ROM][TW 4.4.2 KitKat XXUFNE5 for MDK or SS] Updated 5-21-14 in the stock rom slot. so im ****ed now. no wifi no root and can't install safestrap. anyone have any ideas
Download a new ROM from some other device or computer and transfer it manually then flash it on top. If you still have an custom recovery you're fine but if not figure out a way to root
Sent from my Nexus 7 using XDA Premium 4 mobile app
no i dont have a custom recovery. i did a full wipe and then booted into the new rom. so without root i cant get safestrap re-installed to flash anything else
Go to this thread http://forum.xda-developers.com/showthread.php?t=2726868
And follow instructions for downgrading to mk2.
Then root again with saferoot, install safestrap and if you wish upgrade back to nc5.
Sent from my SCH-I545 using Tapatalk
is step 1 flashed in recovery or odin? also the file download cannot find a mirror
Step 1 is just telling you what files to download. Don't try to jump ahead.
If you follow the instructions exactly as he had them you won't have any problems.
Also afh has had problems for the past day or two.
Just keep refreshing. I want able to download a rom I was testing last night until almost lunch time today
Sent from my SCH-I545 using Tapatalk
thank you klabit i am now back to 4.3 trying to root using saferoot and it wont work. it says adb service out of date killing and waiting for phone to appear i am ready to just say **** root and update to 4.4 from verizon jesus ****ing christ
truckapillar said:
thank you klabit i am now back to 4.3 trying to root using saferoot and it wont work. it says adb service out of date killing and waiting for phone to appear i am ready to just say **** root and update to 4.4 from verizon jesus ****ing christ
Click to expand...
Click to collapse
Probably be best to take that question to the saferoot thread.
I only had to use it once before.
Sent from my SCH-I545 using Tapatalk
truckapillar said:
thank you klabit i am now back to 4.3 trying to root using saferoot and it wont work. it says adb service out of date killing and waiting for phone to appear i am ready to just say **** root and update to 4.4 from verizon jesus ****ing christ
Click to expand...
Click to collapse
Try using "adb kill-server" before running the Saferoot install.bat. If that doesn't work, post a question in the Saferoot thread with the full error messages that you're seeing.
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
jeffysonp said:
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
Click to expand...
Click to collapse
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
aircooledbusses said:
Alright, I know this is not the help/question/noob thread, but I'm I'm a pickle. Redirect me if you must. Verizon s4 that was on nc5 baseband-i don't know the bootloader, but it was 4.4.2 if that helps. Rooted with towel root and twrp through too manager. Yeah, I know that's where the problem came from. So now the phone is (hopefully) in a soft brick state stuck in down load or Odin mode. Odin recognizes the phone. I don't care to keep DAT or retain root, I just was it to function. Is the nc5 full wipe with the pit my correct next step? Thank you in advance, razz me if you must, I deserve it
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's definitely hope. If Odin can't bring you back I bet Heimdall could. It's a little more involved but obviously worth it.
Sent from my SCH-I545 using Tapatalk
Awesome! I've never used hemidal yet, but have recently been doing much better with adb commands, so I'm totally willing to learn. I'll post back here in a few days
Sent from my Nexus 7 using XDA Premium 4 mobile app
I was trying to flash Hyperdrive and ended up having to update to NC5, I can't remember what my phone was out of the box, I will be able to tell you in a few hours when I get my box. I just got the phone last week, so probably 4.3.
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
decaturbob said:
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
also odin is very touchy with using usb cables, usb ports and computers
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
Yep, from the thread you suggest.......... "The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases."
Sent from my GT-I9070 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NC5 is in this thread
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Slowbalt said:
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
jeffysonp said:
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
Click to expand...
Click to collapse
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Also once you're back to stock run Tri Angle Away to get rid of that annoying CUSTOM screen at boot lol can't stand that thing and on my phone it can make getting into CWM a pain as well.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't seem to get into stock recovery either. I tried re-flashing and I still get the same results, when I try to boot into recovery I get the Samsung logo with the unlocked padlock, and then it just shuts down. :/