So here's the deal; I had my phone rooted with ForceROM before the recent OTA update. When the update came out, I couldn't install it because of the root. The constant notification to update was annoying me so I unrooted and installed the update (which may have been my downfall). Today, I tried to re-root using CWM (this method) and install TriForceROM, but my phone will not boot into recovery mode to finish the job. It goes to the Samsung screen with the "Recovery Booting..." in the top left corner, goes blank, and reboots as normal. I tried going completely bare-bones stock (unrooted then did a factory reset) and doing it from there but same results.
Is this something to do with the new update? Did I miss a step? Any help is appreciated. I'm just glad the phone isn't totally bricked.
Caffeinatrix said:
So here's the deal; I had my phone rooted with ForceROM before the recent OTA update. When the update came out, I couldn't install it because of the root. The constant notification to update was annoying me so I unrooted and installed the update (which may have been my downfall). Today, I tried to re-root using CWM (this method) and install TriForceROM, but my phone will not boot into recovery mode to finish the job. It goes to the Samsung screen with the "Recovery Booting..." in the top left corner, goes blank, and reboots as normal. I tried going completely bare-bones stock (unrooted then did a factory reset) and doing it from there but same results.
Is this something to do with the new update? Did I miss a step? Any help is appreciated. I'm just glad the phone isn't totally bricked.
Click to expand...
Click to collapse
So you are on MF9 then?
If so, go to the 'how to root video' thread, follow the instructions there on how to use CF Autoroot. Then Download goomanger and use it to install custom recovery.
Then you will have a recovery that you can use to flash what ever it is you are looking for.
However I really suggest you spend some time here, at xda, reading throug the stickies and how tos. Then go through the ROM threads and read some more before you turn you nice pretty phone into a paperweight.
Good luck.
leaderbuilder said:
So you are on MF9 then?
If so, go to the 'how to root video' thread, follow the instructions there on how to use CF Autoroot. Then Download goomanger and use it to install custom recovery.
Then you will have a recovery that you can use to flash what ever it is you are looking for.
However I really suggest you spend some time here, at xda, reading throug the stickies and how tos. Then go through the ROM threads and read some more before you turn you nice pretty phone into a paperweight.
Good luck.
Click to expand...
Click to collapse
Yes, I'm on MF9 xP I'll try that! Thanks
And I've done rooting and flashing ROM stuff since I've had a smartphone, I just couldn't figure this one out with the update and it being tricky enough to get root on this phone to begin with x_x
Here's some more info
leaderbuilder said:
Here's some more info
Click to expand...
Click to collapse
Yup, everything works perfectly now Thanks again ^_^
How to you mark a thread as solved? Or does a mod do that?
Caffeinatrix said:
Yup, everything works perfectly now Thanks again ^_^
How to you mark a thread as solved? Or does a mod do that?
Click to expand...
Click to collapse
Just go to first/original post and eidt/modify title should do it.
Related
Hello ladies and gents,
So I'm a total noob and I think I bricked my phone.
I got root by using the motochopper tool
then I went for custom recovery, but I think I flashed the verizon version instead of the ATT version (I was trying to install the Google Wallet fix with a custom rom)
Rebooted the phone, I get an unlock symbol and samsung custom
I can boot into recovery mode and I still have root access / command line.
The phone either boots to black screen with a oscillating blue light or if I go into the other mode it says 'downloading'
Anything I can do to get my phone back working? Did I totally brick it?
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
TheAxman said:
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
Click to expand...
Click to collapse
Do you have any type backup? Have you tried, power off phone. hold down power button and volume up at same time, when it vibrates, let go of the power button, it should go into recovery, and lets try restoring your backup.
Your problem is you have the wrong kernel loading, flash a ATT kernel once in the recovery, it will boot.
willenglishiv said:
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
blyndfyre said:
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
Click to expand...
Click to collapse
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
sloanster said:
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
Click to expand...
Click to collapse
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
blyndfyre said:
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
Click to expand...
Click to collapse
But he can adb so he can push the kernel onto his phone and flash in recovery
Edit: my bad, he did say he can't boot into recovery. Odin is his best bet.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
TheAxman said:
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
Click to expand...
Click to collapse
Hope it gets it worked out!!!
The main thing is he's got options...:angel:
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.
Hey guys,
So once upon a time, actually about a month ago, I had this great idea to root and flash CM on my AT&T GS4 on 4.3. Well I used Kingo Root and it went fine. But then came the flashing part. I went through all of the steps to get CM, until I saw to the "Downloading" Odin Mode screen and quickly realized the tutorial I used, did not take into the account I had a locked bootloader.. (Thanks AT&T..) Well I finally got out of that and quickly unrooted because I was scared of causing more damage.
Then came along the 4.4 KitKat OTA update which I desperately want. 4.3 is a disaster on my GS4. Anyways, after it downloaded and started to install, it restarted to the Odin Screen!! And so I got out of that.. again.. And now I'm back on 4.3 with no current issues. Except that I figured a factory reset would help me. Once again, it took me to the Odin screen and apparently I'm not going to be factory resseting either..
I really want to go to the exact way I got it. So I can start fresh and get the 4.4 update. I had seen where you could go into the recovery screen and select to wipe all data, but I'm not sure and do NOT want to lose my phone because it works right now.
So any thoughts?
Kwwolves2012 said:
Hey guys,
So once upon a time, actually about a month ago, I had this great idea to root and flash CM on my AT&T GS4 on 4.3. Well I used Kingo Root and it went fine. But then came the flashing part. I went through all of the steps to get CM, until I saw to the "Downloading" Odin Mode screen and quickly realized the tutorial I used, did not take into the account I had a locked bootloader.. (Thanks AT&T..) Well I finally got out of that and quickly unrooted because I was scared of causing more damage.
Then came along the 4.4 KitKat OTA update which I desperately want. 4.3 is a disaster on my GS4. Anyways, after it downloaded and started to install, it restarted to the Odin Screen!! And so I got out of that.. again.. And now I'm back on 4.3 with no current issues. Except that I figured a factory reset would help me. Once again, it took me to the Odin screen and apparently I'm not going to be factory resseting either..
I really want to go to the exact way I got it. So I can start fresh and get the 4.4 update. I had seen where you could go into the recovery screen and select to wipe all data, but I'm not sure and do NOT want to lose my phone because it works right now.
So any thoughts?
Click to expand...
Click to collapse
The best way to prepare your previously rooted phone for the OTA official update is to Odin back to stock your current firmware.
http://forum.xda-developers.com/showthread.php?t=2621279
Good luck.
John The Rhino said:
The best way to prepare your previously rooted phone for the OTA official update is to Odin back to stock your current firmware.
http://forum.xda-developers.com/showthread.php?t=2621279
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, from what I have read, I think this going to help me.
Kwwolves2012 said:
Thanks for the reply, from what I have read, I think this going to help me.
Click to expand...
Click to collapse
I hope it does. Either way post your results. Also if you need more help it's here on XDA. Good luck.
So far so good
John The Rhino said:
I hope it does. Either way post your results. Also if you need more help it's here on XDA. Good luck.
Click to expand...
Click to collapse
This has seemingly completely reset my phone to factory settings which is what I wanted. I have not tried the OTA update yet, but I will try to post the results of that after I see how it goes.
Kwwolves2012 said:
This has seemingly completely reset my phone to factory settings which is what I wanted. I have not tried the OTA update yet, but I will try to post the results of that after I see how it goes.
Click to expand...
Click to collapse
Yup. Odin back to stock is the best way to go. Even if you decide not to take the official Kit Kat OTA update, you now have a fresh factory firmware installed. You can root, install Safestrap recovery & back up your stock rom (which I highly recommend) and flash custom roms, of which there is now some 30 + for our beloved MK2 S4. Either path you chose, you are going to be fine.
Here's some background. I rooted with towel root and went easy enough. Then I used flashify to flash cwm and here's where my problem begins. It apeares as though I no longer have a working recovery. I can reboot just fine but it I step to go to recovery I get a waning screen telling my to go to the nearest Verizon. Volume down/home and power bring me to another screen asking me if I want to install custom os or reboot. I reboot from there and all is good. Where do I go from here? After doing this a light bulb turned on in my head and I remembered I need to be unlocked for custom so now I need some help thanks.
someolddude said:
Here's some background. I rooted with towel root and went easy enough. Then I used flashify to flash cwm and here's where my problem begins. It apeares as though I no longer have a working recovery. I can reboot just fine but it I step to go to recovery I get a waning screen telling my to go to the nearest Verizon. Volume down/home and power bring me to another screen asking me if I want to install custom os or reboot. I reboot from there and all is good. Where do I go from here? After doing this a light bulb turned on in my head and I remembered I need to be unlocked for custom so now I need some help thanks.
Click to expand...
Click to collapse
Have you tried to use ODIN to go back to start? Go to this thread and try to go back, if I'm not mistaken the package also flashes the stock recovery. All the instructions you need are there.
http://forum.xda-developers.com/showthread.php?t=2483380
Atrizzain said:
Have you tried to use ODIN to go back to start? Go to this thread and try to go back, if I'm not mistaken the package also flashes the stock recovery. All the instructions you need are there.
http://forum.xda-developers.com/showthread.php?t=2483380
Click to expand...
Click to collapse
Haven't tried that but I did see it. I'm thinking I might have to give that a try doesn't look all that involved. Saturday evening or Sunday I should have time thanks.
OK so Oden is a bust nothing but virus and Spyware when trying to find a working tool. My wife discovered something way better through Verizon. The have an upgrade and repair tool for Samsung that works in one clock. No drama just sit back and wait. It completely restored my phone to new condition and got rid of the annoying custom notification and unlocked logo.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie