Hey, I recently rooted my 4.4.3 ATT Galaxy S4 using towelroot and got a little too excited/didn't do enough reading and tried to install CWM via rom manager like an idiot. Now whenever I boot my phone into recovery it says "No Command" and then "Error" when I reboot. Before I do anything further and potentially brick my phone, I want to ask a few questions.
1. Is it still possible for me to install SafeStrap, and is this a thing that I should even try to do at this point.
2. Did I screw up my phone's recovery/bootloader?
a. Is this repairable, and if not, is there anything I can do to avoid further damage?
3. Is there anything I can do to avoid further damage?
Thanks for your help!
The phone is completely repairable. The stock recovery on the phone is useless for us.
Safestrap is the only working recovery for our phone. It is different from other recoveries as it does not replace the stock one.
You can flash the full NB1 ROM in Odin if you really want to fix this. You really don't need to as the phone will work even without the stick recovery available.
Sent from my SGH-I337 running GPE using Tapatalk
Related
So here's a scrub question... I'm worried about possibly bricking my S4 and all that, as it's my only one. I want to see if Android Kitchen will work the jfltespr variant of the S4 after the update, so what I did was take a SlimBean ROM that I already know works on my phone as it, and I loaded it in the kitchen, then recompiled it again so I can flash it.
The only difference is now it's a "kitchen" ROM, so it has the potential to not work.
So with that said... if I attempt to flash a ROM with TWRP and something bad happens, what's the worst that could happen to my phone? I'll always be able to get back to recovery and flash again, right? Or can a custom ROM screw up have the potential to destroy my phone?
As long as you can get it to boot into download mode you can always fix any disaster. If you find a way to hard brick it through flashing you will be in new territory..
This phone is very hard to brick. You are always good if you can get into download mode or recovery. There are possibilities of losing a Meid # or something, but I don't see that happening, but I guess it could be possible depending on what you are doing.
Sent from my Sprint Galaxy S4 using Tapatalk 4 Beta
Before I get jumped, YES, I did do countless readings to the point of going blind with information overload! Rooting phone was a confirmed success after the OTA update, and I did not do any bootloader roms, but now I can't get pass the download screen while booting up the phone. When I was trying to boot into recovery mode after I did a few quick restarts in a row after rooting phone, to install a debloater .zip, it came to this screen only (see screenshot), quickly (Samsung logo comes up before with the blue corner text) before this, and it's all that it does now. I think I might have pulled the battery a couple times when I saw the first image, my dumbass fault, as a quick power button push wasn't doing anything to reboot. Thinking it's a soft brick as this screen is the only thing that keeps coming up after Samsung Logo with no unlock/lock symbol, when I try to reboot the phone in various ways. I know I can't use Odin to reflash back to stock MDL after the June OTA update, as I tried with no luck came up failed like I knew it would. Plug in via usb to computer, PC doesn't recognize it, so I can't check / access anything on the phone. Pulling straws here. Just looking to get her back to normal
UPDATE
Plugged stock USB cable/Phone in another USB slot, Odin picked it up (See pics), of course I can't downgrade to MDL from MF3.... failure.
US ATT SGH-1337 Jelly Bean 4.2.2
(Last night) Stock Firm: I337UCUAMDL
(This morning) OTA Firm: I337UCUAMF3
You tried to install a custom recovery from what you are describing, yet not really saying.
You wanted to flash a debloat zip... How would one go about doing that? A custom recovery. Unfortunately, there is none for the MF3 update. The only way you would be in this situation is by trying to flash one. So... You're screwed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
You tried to install a custom recovery from what you are describing, yet not really saying.
You wanted to flash a debloat zip... How would one go about doing that? A custom recovery. Unfortunately, there is none for the MF3 update. The only way you would be in this situation is by trying to flash one. So... You're screwed.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured I was, was hanging on by chance for a bypass, that I might have a chance on getting the phone to boot normally again, by trying a method I hadn't tried / known yet... :crying:
l33t_killa said:
I figured I was, was hanging on by chance for a bypass, that I might have a chance on getting the phone to boot normally again, by trying a method I hadn't tried / known yet... :crying:
Click to expand...
Click to collapse
You can try what this guy did and see if it helps...
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
If it doesn't work i would say you screwed yourself.
Maybe when you "read yourself blind" you missed the Numerous warnings throughout the MF3 root thread and the rest of the forum about MF3 not being able to use custom recoveries or flashing anything?
Good luck.
scott14719 said:
You can try what this guy did and see if it helps...
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
If it doesn't work i would say you screwed yourself.
Maybe when you "read yourself blind" you missed the Numerous warnings throughout the MF3 root thread and the rest of the forum about MF3 not being able to use custom recoveries or flashing anything?
Good luck.
Click to expand...
Click to collapse
,
Yep, I missed that tidbit of info, I did try your suggestion from another member via this thread http://forum.xda-developers.com/showthread.php?t=2407443 as I'm getting closer as per my updates there. Going to try out ou812bkewl's method here http://forum.xda-developers.com/showthread.php?t=2360859
MF3 Nandroid Backup
I was able to get a full Nandroid Backup for AT&T S4 with the MF# firmware using an app called OBackup. Im not real sure if any of the files would be helpful to those stuck after trying to install a custom recovery. I think if you could get into download mode and in Odin, these .tar files might be helpful.
Hello! I am hoping the brains on this forum might be able to help me out here....
I ran the CF AutoRoot and was able to successfully boot the phone. I then flashed the TWRP recovery via Odin and rebooted with the plan of entering recovery mode. Unfortunately the phone merely displayed the tiny text message stating it was recovery booting in the upper left corner, then rebooted. I was afraid I had a boot loop but the phone happily loaded Android and had no issues. Since then I have tried the tried the Philz, CM, and TWRP installs via Odin but the issue remains. I tried re-running the CF AutoRoot too. I have tried 2 versions of Odin(1.8(?) and 3.09). Kies does not recognize the phone and will not update it.
I have a spare Note 3 that I have been testing out these files on. Each of the installs that seems not to work on my primary phone works perfectly on the spare. Both phones are Sprint SM-N900P models.
So, just to restate, the phone works perfectly except I cannot get recovery mode to load.
So...any suggestions on what I can try next? I will not be able to log back in to check messages for a few days (moving) but would like to thank you all in advance for any assistance you may be able to offer.
Well I doubt I can assist you since I'm having the same issue! I've tried methods advised by another member and still will not boot into recovery. It does the boot loop every time I flash anything after rooting. I couldn't even get recovery after flashing the Wootever kernel. So my thinking is I may have to unroot and flash the stock firmware and then root again and start over. My other guess is it may have something to do with not wiping dalvik and cache? All I know is before I updated to KK, I wasn't having any boot loops on JB with
CM11. I'm also wondering if wiping out the system would possibly help. Ugh frustrated beyond belief and wish I never updated to KK
sent from my beast Galaxy Note 3 N900T
You need the correct recovery for 4.4 or 4.3.it seems you have the wrong recovery
Gesendet von meinem SM-N9005 mit Tapatalk
Assistance is needed.
I do not have bootloop, but when I try to enter recovery mode the phone it says: Secure Fail Recovery. Then below the yellow triangle it says, System software not authorized by Verizon Wireless has not been found on your phone. Please turn off your phone and go to the nearest store for help. I was installing CWM for the Note 3. Anyone know how to fix this and install a custom recovery? I cannot enter recovery at all. Everything else works. But I really need to fix this somehow as getting into recovery is critical. Any takers on this?
Ammoguy36 said:
I do not have bootloop, but when I try to enter recovery mode the phone it says: Secure Fail Recovery. Then below the yellow triangle it says, System software not authorized by Verizon Wireless has not been found on your phone. Please turn off your phone and go to the nearest store for help. I was installing CWM for the Note 3. Anyone know how to fix this and install a custom recovery? I cannot enter recovery at all. Everything else works. But I really need to fix this somehow as getting into recovery is critical. Any takers on this?
Click to expand...
Click to collapse
You have Sprint phones but you're getting Verizon warnings? Sounds like you installed software/recovery designed for the Verizon SM-N900V rather than the Sprint SM-N900N
Sent from my Note 3 via Tapatalk
donc113 said:
You have Sprint phones but you're getting Verizon warnings? Sounds like you installed software/recovery designed for the Verizon SM-N900V rather than the Sprint SM-N900N
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
It's a N900V I've been with Verizon 9 years. Im not worried about it now. Getting a replacement phone and root it, but keep a stock rom on it. learned a lesson trying to put a custom recovery on it.
Hello everyone! I'm brand new to the forums so if I am breaking any rule or regulation, just give me a heads up. So, some basic information about my predicament.
- own a Samsung Galaxy Note 3 from Verizon.
- I use t-mobile network. Works great with no problems.
- phone was successfully rooted via towel root.
I was looking to get cynagenmod on the phone so I started looking up guides and such. Only thing I wasn't aware of was that carrier branded versions can't have their recovery flashed. That said, I used flashify and the clockwork apk. The app did its job, killed the stock recovery, but couldn't load the new one. Now the phone says error, no recovery when trying to access it during boot.
It should be said that the phone still boots and works normally but I really want to get the recovery working so I can at least try again the right way to get cynagenmod working.
My question is, is it possible to get my hands on the stock recovery for my phone and just flash it back to how it was? Basically, how do I fix this problem I put myself in. Of course, I didn't make backups. During the whole process, I figured "if I follow this tutorial word for word, why bother with backups?" look how wrong I was
Any help would be sincerely appreciated. I'm posting this from my replacement phone, not my note 3.
Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
One thing you might try here, and another here.
dvandam said:
Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
Click to expand...
Click to collapse
There are flashable zips of TWRP floating around to update and the TWRP thread in our section says to use the TWRP Manager app on the Play Store. As far as using ODIN, you won't be bricked. The unlock icon shows up when it detects the system files aren't stock/root is in place. Your bootloader should still be in tact, and if you can still boot into recovery that confirms it. Either way, you just need to use a different method to update TWRP and you should be fine.
Well I feel like a f-ing nimrod..
I failed to mention in my description that when I first tried to install, not only did I get the Unlock icon, but I got the "Software not authorized by AT&T..." error message that prevented me from doing anything. However, I thought this was related to my phone being carrier locked. I found out later that my phone was unlocked a while ago so that wasn't it. Had I looked more closely at the error I would have seen that it was a Kernel error. Turns out I had to install a LOKI'd Kernel. Not exactly sure why, but that was the only one that worked. Now the new ROM is installed and I'm restoring my apps now.
If nothing else, I got my TWRP updated finally, so I like to think this wasn't all for naught. Thanks for the insight anyways. This was easier than doing an ODIN back and forth.
This is because you're on the MDL bootloader. You need to search the forums for your phone in regard to the MDL bootloader and loki'd ROMs. When you see the "software not authorized. .." message, it just means you need to flash a loki'd kernel for your device. Search for Jeeboo's Recovery and Kernel and you should be right a rain. Good luck.
Edit: I was half awake when I tried to answer your question, and somehow missed that you had discovered the loki'd kernel already. The reason for this is because the MDL bootloader is susceptible to the loki exploit, which for all intents and purposes is the equivalent of unlocking the bootloader. I've been using Jeeboo's recovery for a year or so and never had an issue with any ROM I tried. The kernel cones in handy for those that need a loki'd kernel. There's a ton of easy to find info in the forums to help you get a better understanding of the MDL and how loki applies to it.