Database Users

Noob Here Needing Major Help! Unrooting and Rooting

Okay, so I have rooted my Droid eris several times and have downloaded and installed kaosfroyo, vanilla, and plain Jane. I have reverted back to the "stock" Rom with this program on the computer. I have clockwork mod on this because i have seen this name in the text while it installed. So now I think I'm on the stock but I'm not fully sure. I want to unroot this phone completely and make it back to how it was when you would open up a brand new box. Then i was to go through and install the, in your opinion, the best rom out there. Now for the probem, when I go to install a new Rom, I turn off the phone completely, hold down volume down and end buttons, then when the menu comes up I push up on the volume button and i get the picture of an Eris with a red triangle and an exclamation point. That disables me from doing anything. It does the same thing when I turn the phone off and hold volume up with the end button. To fix it, I just turn off the phone and let it boot up normal. Is there any fix for this? Please keep in mind that i am a super dummy when it comes to this stuff so I don't fully understand the technical terms and would appreciate explanations.
Thank you so much for your time and help.

Time To Shine said:
Okay, so I have rooted my Droid eris several times and have downloaded and installed kaosfroyo, vanilla, and plain Jane. I have reverted back to the "stock" Rom with this program on the computer. I have clockwork mod on this because i have seen this name in the text while it installed. So now I think I'm on the stock but I'm not fully sure. I want to unroot this phone completely and make it back to how it was when you would open up a brand new box. Then i was to go through and install the, in your opinion, the best rom out there. Now for the probem, when I go to install a new Rom, I turn off the phone completely, hold down volume down and end buttons, then when the menu comes up I push up on the volume button and i get the picture of an Eris with a red triangle and an exclamation point. That disables me from doing anything. It does the same thing when I turn the phone off and hold volume up with the end button. To fix it, I just turn off the phone and let it boot up normal. Is there any fix for this? Please keep in mind that i am a super dummy when it comes to this stuff so I don't fully understand the technical terms and would appreciate explanations.
Thank you so much for your time and help.
Click to expand...
Click to collapse
By program on the computer do you mean you ran the ruu from verizon to put the stock software back on the phone? If that's the case I beleive you have probably unrooted the phone and will need to re root. I may be wrong but I think the ruu also flashes the original recovery which is why your not able to boot into it.

Conap said:
By program on the computer do you mean you ran the ruu from verizon to put the stock software back on the phone? If that's the case I beleive you have probably unrooted the phone and will need to re root. I may be wrong but I think the ruu also flashes the original recovery which is why your not able to boot into it.
Click to expand...
Click to collapse
I would assume that's what it was. I know it is rooted now because i went through this process to root it after i ran tht program. I don't remember what one it was specifically however i know it had a progress bar on the top right while it installed and had the screen of holding down volume and end button to turn on the phone.

if you are rooted then under your program list you should have superuser permissions icon .. if you dont then you may still be rooted but not likely .. if you do not see that, you can simply go to the market and download a program for root users only and if it doesnt work on your phone then you know you are not rooted .. happy hunting

duccicucci said:
if you are rooted then under your program list you should have superuser permissions icon .. if you dont then you may still be rooted but not likely .. if you do not see that, you can simply go to the market and download a program for root users only and if it doesnt work on your phone then you know you are not rooted .. happy hunting
Click to expand...
Click to collapse
Even if you re rooted afterwards you may need to reinstall recovery...i reccomend you use amons recovery. You can find directions in one of the how-to root threads around here.

problm solved

Problem after using goomanager

I have the att s4 with the mf3 build which I received via an ota update. I recently did the root for this build which worked perfectly, afterwards I read through 47 pages of forums and was trying to do the work around djrbliss put out, around page 40 someone says if your phone is rooted just download goomanager and installscriptrecovery. then reboot recovery. I downloaded goomanager then installed script, after this I hit the reboot recovery and the phone went into download mode. and it will stay there. If i restart it returns to download mode. Any Ideas?

Im not 100% but u may hve read wrong. This has happened to everyone who has tryed to flash a recovery on mf3. You can only have root there is no custom recovery for this build. Ok now this is wat you do take your phone to bestbuy tell them kies f'd ur phone up nd they can reflash mf3.at this moment mf3 isnt available to general public
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Yeah, read the forums. I mean seriously, almost every other post, including the one you read, tells you that drjbliss's exploit was patched in mf3, and can brick your device if you attempt to install a custom recovery. It is, quite literally, the biggest topic in the S4 forums. Also, there is no odin flashable image for mf3, so you cannot return to stock without taking it to bestbuy. Read more in the q&a section, as this same mistake has been made and asked about at least a hundred times. Literally.
In conclusion, you have a paperweight till you take it to get it flashed back to normal.

ok thanks for the help

cooljg said:
ok thanks for the help
Click to expand...
Click to collapse
Read this thread. Best buy can flash the stock mf3 firmware and get your recovery back. http://forum.xda-developers.com/showthread.php?p=45457012

Either that or J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Hey guys thanks for chiming in. I want to give a thank you to those who have gave me a serious answer. I will go back to best buy and try again, but I sent my wife up there and she said the cell phone department told her they do not flash firmware there. She said she asked them if the service section did and the lady told her no again. I am fairly familiar with flashing the firmware on an s3 I just haven't messed with the s4 that much,and obviously I didn't read as well as I thought I did or it wouldn't be bricked. I do have one other question tho if Best Buy can flash it back to stock firmware, is it safe to assume at some point I should be able to flash it back via odin when the mf3 build is released by sammobile? Either way if best buy doesn't flash it back i'm screwed on this one and i'll just have to pick up another s4 tomorrow. I just want to know if this one can be fixed i'd really hate to waste a perfectly good phone.

If and when mf3 firmware is available you should be able to flash with odin. Best buy seems to be using a new software package other than Odin so who knows if an odin package will be available.

I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.

~wolverine~ said:
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
Click to expand...
Click to collapse
Correct

Question on brick fix
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.

cooljg said:
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
Click to expand...
Click to collapse
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?

Sounds like a simple factory reset...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

haremmon said:
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Click to expand...
Click to collapse
He originally plugged my phone up when I gave it to him but it wouldn't come on so he unplugged it and replaced the battery. The battery I had was completely dead. After he replaced the battery he turned it on and it went to the download screen with the little green alien. After that he held some buttons and kept looking at the back and then the front of the phone. I couldn't really see what he hit but shortly afterwards it came up with my lock screen picture. After that he said it doesn't need flashing but he would flash the firmware if I wanted so I said ok and he did. I have the phone now working great but it doesn't show rooted anymore.

Omg how do people not know this already. I have had my S4 for 2 days even i know better and I cant believe people dont read

[Q]SOLVED Phone not booting into recovery mode?

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.

[Q] Phone has no recovery and other issues.

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

Successful Root of BOK3, but then I messed up, any help would be appreciated.

Hello,
I followed the guide for the Working Root Method For 5.0 Lollipop ROms and I was on BOK3 and everything actually worked and the phone was rooted, good to go. I was able to start the phone, installed busybox and safestrap, everything mentioned on the page, phone was good and working. However, I made a mistake. When I went to wipe the data so I could install a ROM I somehow managed to format, or wipe something I was not supposed to. Now, everytime I turn the power on it sticks on the Samsung Galaxy S5 page with the "Custom" wording and the open lock. I have been able to get to the download mode and when I tried to Odin to G900VVRU2BOK3_G900VVZW2BOK3_G900VVRU2BOK3_HOME.tar it says it passes, but still freezes on the "Custom" power on page. I honestly don't know what else I can do to try to get the device to power on/restore it, I've tried the N2 Kernal from the same page as the the tar and it doesn't get me anywhere, though it also says it passes. I'll be up for work in a few hours and if you have anything for me to try or requests for additional information I'll see what I can.
I have attempted to run the root bat file, just to see if it works, but that will not even list the phone.
Thank you,
Dale.

If you flash NK2 kernel and try to boot into lollipop, you're definitely going to freeze on boot because lollipop can't boot with a kitkat kernel.
Flash BOK3 stock image in Odin again. That image has the kernel in it also, so you don't need to flash anything else. Then boot into stock recovery (hold vol+UP and power), clear cache, then reboot.
If that doesn't work, boot back into stock recovery, clear cache and factory reset, then reboot.
That may work.

Thanks for the help. I don't know what I was thinking last night/this morning. All set now! For some reason now it didn't root when I went back through the procedures, but that is a problem to solve at a different time. I appreciate your calm response to my panic.

dhessjr2291 said:
Thanks for the help. I don't know what I was thinking last night/this morning. All set now! For some reason now it didn't root when I went back through the procedures, but that is a problem to solve at a different time. I appreciate your calm response to my panic.
Click to expand...
Click to collapse
You're welcome