I am now on 4.4.2 NC5 and was able to root using CFroot.
However, any recovery I try to install has about the same result: the screen right before recovery bootloops. I must take out the battery, boot into odin and cancel. Then it boots normally.
I even went so far as to use GooManager to install twrp. Same deal.
This also happened on 4.3 MJ4.
I have tried odin 1.86 anf 3.07. I have a feeling it is on the phone, I mean, I can do a hard reset into recovery. Android recovery is there with a android on his back with a red exclamation.
At this point, I am unable to flash anything
rosystreasures said:
I am now on 4.4.2 NC5 and was able to root using CFroot.
However, any recovery I try to install has about the same result: the screen right before recovery bootloops. I must take out the battery, boot into odin and cancel. Then it boots normally.
I even went so far as to use GooManager to install twrp. Same deal.
This also happened on 4.3 MJ4.
I have tried odin 1.86 anf 3.07. I have a feeling it is on the phone, I mean, I can do a hard reset into recovery. Android recovery is there with a android on his back with a red exclamation.
At this point, I am unable to flash anything
Click to expand...
Click to collapse
Thought I would try to odin the nc5 bootloader. It gave me the kernel upload error message. I am now reinstalling nc5 oneclick restore.
rosystreasures said:
I am now on 4.4.2 NC5 and was able to root using CFroot.
However, any recovery I try to install has about the same result: the screen right before recovery bootloops. I must take out the battery, boot into odin and cancel. Then it boots normally.
I even went so far as to use GooManager to install twrp. Same deal.
This also happened on 4.3 MJ4.
I have tried odin 1.86 anf 3.07. I have a feeling it is on the phone, I mean, I can do a hard reset into recovery. Android recovery is there with a android on his back with a red exclamation.
At this point, I am unable to flash anything
Click to expand...
Click to collapse
Try using twrp version 2.7.0.1 and Odin 3.09...never had any problems with those. When you used cfroot, you did get the screen with the red pirate android saying it rooted?
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Try using twrp version 2.7.0.1 and Odin 3.09...never had any problems with those. When you used cfroot, you did get the screen with the red pirate android saying it rooted?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yes, I saw the red pirate android
I will find odin 3.09 and try that.
I am confused about installing twrp in odin. Do I want the .img file or the .img.tar file?
I always use the tar file and works. Your phone is fine though, just need to get the root and recovery to stick. When all else fails though..rj's one clicks are life savers and at least get you back to stock.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Try using twrp version 2.7.0.1 and Odin 3.09...never had any problems with those. When you used cfroot, you did get the screen with the red pirate android saying it rooted?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
FInally got 3.09 installed. I believe I use AP??
rosystreasures said:
FInally got 3.09 installed. I believe I use AP??
Click to expand...
Click to collapse
Yea, use the ap box.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Yea, use the ap box.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
OMG!! It worked!!! I got twrp!!!
ty!!!
rosystreasures said:
OMG!! It worked!!! I got twrp!!!
ty!!!
Click to expand...
Click to collapse
Glad it worked, make sure to flash SU...and then you'll be golden!
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Glad it worked, make sure to flash SU...and then you'll be golden!
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
got that too!! I Am sssooo excited!!!
rosystreasures said:
got that too!! I Am sssooo excited!!!
Click to expand...
Click to collapse
Now that you have all that done...make a backup in twrp..I always make one right after I root and install recovery so if I ever have to go back to the start, I use that instead of having to use the one click method. If you haven't used twrp, I always make a backup of the boot, data, and system and save to the card.
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
Now that you have all that done...make a backup in twrp..I always make one right after I root and install recovery so if I ever have to go back to the start, I use that instead of having to use the one click method. If you haven't used twrp, I always make a backup of the boot, data, and system and save to the card.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am doing it right now. oops, just finished.
Related
Hello,
I have a Verizon Galaxy S4. Today I rooted it. It all went fine, but I wanted to install a custom recovery. I followed a tutorial online, which lead me to downloading the Goo manager, and installing TWRP via that. I rebooted, and it went straight into download mode. It would not leave download mode, it continuously loops back to that. I connected it up to Odin, and downloaded the stock firmware to flash. The progress bar came up, loaded for a few minutes. Then, I got a big FAIL message. (Using 3.04). Now, its still in DL mode, but it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Tried flashing the stock firmware again, but keeps failing. Tried different USB ports, but keeps failing. Any suggestions?
Try flashing another recovery via odin
Sent from my GT-I9300 using xda premium
Jamiew1977 said:
Try flashing another recovery via odin
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
On it.
It happened to me with my s3, installed twrp with goo and I had no recovery. Flashed a different recovery with Odin and all was sweet, Hope you fix it.
Sent from my GT-I9300 using xda premium
Jamiew1977 said:
It happened to me with my s3, installed twrp with goo and I had no recovery. Flashed a different recovery with Odin and all was sweet, Hope you fix it.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can't find a tar file flashable via Odin. All I can find is the Loki method, which I cannot do because I'm stuck in DL mode. Waiting on a download of a different stock firmware.
Dont think there is any recoveries flashable via odin. Were you on me7 by chance?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Dont think there is any recoveries flashable via odin. Were you on me7 by chance?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Nope.
Turn your phone all the way off and then use the button combo for odin, decline and it should boot. DoubleCheck your firmware version because what youre describing is what happens when you flash a recovery on me7, which you cant.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Turn your phone all the way off and then use the button combo for odin, decline and it should boot. DoubleCheck your firmware version because what youre describing is what happens when you flash a recovery on me7, which you cant.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Didn't work. Went right back into DL mode after I declined.
When you were flashing the firmware via odin did it error when it was going to flash aboot?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
When you were flashing the firmware via odin did it error when it was going to flash aboot?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yes. It says FAIL! (Auth) right after aboot.mbn
Do you have a link to the root method you used?
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Do you have a link to the root method you used?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yep here it is: http://forum.xda-developers.com/showthread.php?t=2380325
PS: Thank you so much for sticking with me so far
Not a problem. Yep youre on the me7 firmware like I thought. Im guessing your trying to flash the mdk firmware thru odin? Me7 wont let you flash anything prior is why youre getting the errors. Youll have to download the me7 odin file (in dev section) and flash again. Once you get your phone booted again you cant flash a custom recovery or else itll do the same again. Theres a few people working on unlocking/bypassing the bootloader so hopefully it wont be much longer until me7 has custom recovery.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Not a problem. Yep youre on the me7 firmware like I thought. Im guessing your trying to flash the mdk firmware thru odin? Me7 wont let you flash anything prior is why youre getting the errors. Youll have to download the me7 odin file (in dev section) and flash again. Once you get your phone booted again you cant flash a custom recovery or else itll do the same again. Theres a few people working on unlocking/bypassing the bootloader so hopefully it wont be much longer until me7 has custom recovery.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You are a savior my man. Thank you.
Not a problem
Sent from my SCH-I545 using Tapatalk 2
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
Hey guys. So thanks to Micmars I was able to break myself out of a terrible boot loop. The only real solution at the time was to use an exe file to push me into the NAB update. My goal was to then to go ahead and push a custom recovery and use SuperSU to root the device, followed by installing NABD. Problem is that it seems that the current stock recovery is unable to flash any of these updates. The broken android comes up when I enter stock recovery. Flashing a custom recovery fails as well.
Here are my goals:
1. Root
2. Flash TWRP
3. Install one of the latest and greatest custom ROM.
I need your help fellas. Any help is greatly appreciated and big shutout to Micmars for saving me from bricking my phone.
Sent from my SM-N900P using xda app-developers app
You will need to root with CF root you can find it in the forums. If you do that you will lose Knox warranty.
Sent from my SM-N900P using xda app-developers app
Put the phone in odin aka download mode. Flash recovery from there. Works fine. Trips knox. But for me I didn't care. Your milage will vary.
Sent From My 0x1 Note 3.i love tep....
wgorham said:
You will need to root with CF root you can find it in the forums. If you do that you will lose Knox warranty.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I looked at several different stock roms and or recoveries. What exactly is a CF Root? My phone has already tripped Knox so I'm not worried about that.
Sent from my SM-N900P using xda app-developers app
kaos420 said:
Put the phone in odin aka download mode. Flash recovery from there. Works fine. Trips knox. But for me I didn't care. Your milage will vary.
Sent From My 0x1 Note 3.i love tep....
Click to expand...
Click to collapse
Now which recovery are you referring to? Is it the stock? I have tried multiple times with Odin to flash the stock recovery but it won't because it already has the NAB recovery installed and its not letting it do anything else because its saying that the operating system has been modified. so it's basically trying to box with me a bit.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
Now which recovery are you referring to? Is it the stock? I have tried multiple times with Odin to flash the stock recovery but it won't because it already has the NAB recovery installed and its not letting it do anything else because its saying that the operating system has been modified. so it's basically trying to box with me a bit.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Why are you trying to flash stock recovery? ?? It already has stock unless you flashed twrp or philz
Go get the NAB tar file and flash back to Stock and then do what you want .... root with chain fire cf auto root for 9005 ... international note 3 ... Then flash twrp the newest is 2.7 ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
KoolCharisma said:
Hey guys. So thanks to Micmars I was able to break myself out of a terrible boot loop. The only real solution at the time was to use an exe file to push me into the NAB update. My goal was to then to go ahead and push a custom recovery and use SuperSU to root the device, followed by installing NABD. Problem is that it seems that the current stock recovery is unable to flash any of these updates. The broken android comes up when I enter stock recovery. Flashing a custom recovery fails as well.
Here are my goals:
1. Root
2. Flash TWRP
3. Install one of the latest and greatest custom ROM.
I need your help fellas. Any help is greatly appreciated and big shutout to Micmars for saving me from bricking my phone.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
To Start,
1. Remove any cases from phone.
2. Put Chainfire latest superuser on your phone,
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
3. Put TWRP 2.7.0.0 for TouchWiz KitKat on your PC,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
4. Using PC Odin (3.07 is fine), flash TWRP,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
[Unzip to your PC, run Odin as administrator, shut down your phone, put phone in download mode (volume down + home + power, then volume up to confirm), load TWRP tar into PDA slot, plug phone into PC using same USB port as one you've used before, keep automatically restart checked in Odin, hold phone in palm of your hand, get ready to hold volume up + home, hit start on PC Odin, hit start on PC Odin, when file finishes flashing, hit those buttons quickly, since the recovery file flashes in like 5-10 seconds, your now in recovery.]
5. Inject root,
Tap install from the TWRP, navigate to the location on your phone you put that superuser file, flick the knob, reboot.
You are now rooted with custom recovery.
From here, the world is your own. Lots of roms from which to choose, I recommend looking around the dev forums, you'll find something that's right for you. Might want to start with a TouchWiz rom, just because they are built from stock and they'll function as you'd expect. Try AOSP if you like, but those roms tend to take a bit more diligence on your end. No problem with that, but this will get you started with the least effort.
I hope this helps.
Good luck!
Follow the OP instructions prior to flashing.
Sent from my SM-N900P using Xparent BlueTapatalk 2
KoolCharisma said:
Now which recovery are you referring to? Is it the stock? I have tried multiple times with Odin to flash the stock recovery but it won't because it already has the NAB recovery installed and its not letting it do anything else because its saying that the operating system has been modified. so it's basically trying to box with me a bit.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
So NAB is stock essentially? Why am I constantly having warnings of modification and app crashes constantly.
Further the current recovery is broken. You know, the beat up droid on the ground. It won't allow me to install root. Is it possible I need an older root request?
TWRP 2.07 don't flash through Odin. We'll get it though. Let's keep at it.
Sent from my SM-N900P using xda app-developers app
micmars said:
To Start,
1. Remove any cases from phone.
2. Put Chainfire latest superuser on your phone,
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
3. Put TWRP 2.7.0.0 for TouchWiz KitKat on your PC,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
4. Using PC Odin (3.07 is fine), flash TWRP,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
[Unzip to your PC, run Odin as administrator, shut down your phone, put phone in download mode (volume down + home + power, then volume up to confirm), load TWRP tar into PDA slot, plug phone into PC using same USB port as one you've used before, keep automatically restart checked in Odin, hold phone in palm of your hand, get ready to hold volume up + home, hit start on PC Odin, hit start on PC Odin, when file finishes flashing, hit those buttons quickly, since the recovery file flashes in like 5-10 seconds, your now in recovery.]
5. Inject root,
Tap install from the TWRP, navigate to the location on your phone you put that superuser file, flick the knob, reboot.
You are now rooted with custom recovery.
From here, the world is your own. Lots of roms from which to choose, I recommend looking around the dev forums, you'll find something that's right for you. Might want to start with a TouchWiz rom, just because they are built from stock and they'll function as you'd expect. Try AOSP if you like, but those roms tend to take a bit more diligence on your end. No problem with that, but this will get you started with the least effort.
I hope this helps.
Good luck!
Follow the OP instructions prior to flashing.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Micmars! How good to see you again you old chap. Obviously since we last spoke I haven't had much progress. You really helped me getting to this point. We built a whole thread together and saved me $150 in insurance money to get me out of the brick. I don't have a computer on me but I've certainly tried a lot. If stick recovery is simply broken, how do I get of this mess?
I'm confident we'll have that new ROM in no time.
Sent from my SM-N900P using xda app-developers app
This is the message that keeps popping up on my screen. I also have an icon up top with a triang. I feel as though if I were running stock and if I've gone back to the original state of the phone it should
not have this message. I am I correct?
Sent from my SM-N900P using xda app-developers app
Stanard Knox Notifications..
KoolCharisma said:
This is the message that keeps popping up on my screen. I also have an icon up top with a triang. I feel as though if I were running stock and if I've gone back to the original state of the phone it should
not have this message. I am I correct?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Dude, those are standard Knox notifications. If you have successfully rooted your device, just get rid of the damn things. Install freeza's Knox-free Stockish DeOdex or Odex NABD rom and be done with it.
micmars said:
Dude, those are standard Knox notifications. If you have successfully rooted your device, just get rid of the damn things. Install freeza's Knox-free Stockish DeOdex or Odex NABD rom and be done with it.
Click to expand...
Click to collapse
That's just the problem. The stock recovery seems to be broken and I can not actively flash TWRP to the device neither clockworkmod. That's why I'm having the current problem. I can't do anything without having root obviously.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
That's just the problem. The stock recovery seems to be broken and I can not actively flash TWRP to the device neither clockworkmod. That's why I'm having the current problem. I can't do anything without having root obviously.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
My friend, I'm at a loss. There's really nothing I can go at this point. Broken stock recovery makes no sense to me, but that doesn't mean it's not possible.
Flashing working recovery that is custom would replace a stock recovery, working or not. At least one could speculate.
You obviously need to install root.
Go hit the qbking77 video on rooting this device and follow the instructions.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
christianstudebaker said:
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
Click to expand...
Click to collapse
Have actually research what firmware you have and what recovery can be used. You do know that unless you have mdk...you can't use goomanger or twrp or Cwm right?
Sent from my SCH-I545 using Tapatalk
decaturbob said:
Have actually research what firmware you have and what recovery can be used. You do know that unless you have mdk...you can't use goomanger or twrp or Cwm right?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
How many times do you think this same question has been asked and answered?
Sent from my NCC-1701
riker147 said:
How many times do you think this same question has been asked and answered?
Sent from my NCC-1701
Click to expand...
Click to collapse
Countless times....not even 15 mins of reading anything...
Sent from my SCH-I545 using Tapatalk
christianstudebaker said:
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
Click to expand...
Click to collapse
I believe you are going to have to go with SafeStrap 3.72. You don't have an unlocked bootloader but Safestrap isn't bad. You can still install some really good roms
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
christianstudebaker said:
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is a stickie in general forum that all new S4 people should be required to read...I can not imagine how some one ignores a thread when its titled
What you need to know before, during and after modifying your verizon S4
http://forum.xda-developers.com/showthread.php?t=2606501
christianstudebaker said:
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if you can get into download mode and have Odin, flash a full wipe or a no wipe tar and start over.
http://forum.xda-developers.com/showthread.php?t=2735172
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. :/