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
Related
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.
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
Followed these steps: http://www.android.gs/root-galaxy-a7-on-android-5-0-2-lollipop-os-using-pre-rooted-kernel/
After running the steps in ODIN, disconnecting and trying to reboot, it sits at the Samsung screen. I was able to hold POWER+VolDown to force it to reboot, gets stuck again. I did POWER+VolDown again to force a reboot then quickly switch to POWER+VolUp+HOME to get into recovery and did a full wipe, and after reboot, gets stuck again. Any ideas?
Edit: Mine is a SM-T280NZKAXAR; further reading elsewhere tells me I may have not used an image file appropriate for my device, and that this version is possibly not even able to be rooted. I think it is boned. I tried another image, but now it is stuck saying there was a problem updating and to use the recovery function of Samsung's Smart Switch software, but that doesn't work either... Gonna see if the store will exchange it and I play ignorant.
fermunky said:
Followed these steps: http://www.android.gs/root-galaxy-a7-on-android-5-0-2-lollipop-os-using-pre-rooted-kernel/
After running the steps in ODIN, disconnecting and trying to reboot, it sits at the Samsung screen. I was able to hold POWER+VolDown to force it to reboot, gets stuck again. I did POWER+VolDown again to force a reboot then quickly switch to POWER+VolUp+HOME to get into recovery and did a full wipe, and after reboot, gets stuck again. Any ideas?
Edit: Mine is a SM-T280NZKAXAR; further reading elsewhere tells me I may have not used an image file appropriate for my device, and that this version is possibly not even able to be rooted. I think it is boned. I tried another image, but now it is stuck saying there was a problem updating and to use the recovery function of Samsung's Smart Switch software, but that doesn't work either... Gonna see if the store will exchange it and I play ignorant.
Click to expand...
Click to collapse
No need.
I have this device and have been trying to build root and custom recovery for it but at the moment seems impossible.
I've tried everything I know.
Unfortunately it has a locked bootloader, so no unsigned recovery or kernel can be flashed.
However I have managed to flash a modified ROM.
You are only soft bricked. All you need do is flash the stock firmware to recover. Flashing this with ODIN should fix the issue: https://www.mediafire.com/?1p4bpp6n3vxzfxz
If not go to Sammobile.com and download the appropriate firmware and then flash it with ODIN or use one of the links below.
https://samsung-firmware.org/downlo...0, Wi-Fi)/l731/XAR/T280XXU0APC5/T280XAR0APC5/
http://samsung-updates.com/details/63958//SM-T280/XAR/T280XXU0APC5.html
By the way your device is called the Tab A 6. It is not related to the A series phones.
ashyx said:
No need.
I have this device and have been trying to build root and custom recovery for it but at the moment seems impossible.
I've tried everything I know.
Unfortunately it has a locked bootloader, so no unsigned recovery or kernel can be flashed.
However I have managed to flash a modified ROM.
You are only soft bricked. All you need do is flash the stock firmware to recover. Flashing this with ODIN should fix the issue: https://www.mediafire.com/?1p4bpp6n3vxzfxz
If not go to Sammobile.com and download the appropriate firmware and then flash it with ODIN or use one of the links below.
https://samsung-firmware.org/downlo...0, Wi-Fi)/l731/XAR/T280XXU0APC5/T280XAR0APC5/
http://samsung-updates.com/details/63958//SM-T280/XAR/T280XXU0APC5.html
By the way your device is called the Tab A 6. It is not related to the A series phones.
Click to expand...
Click to collapse
I'll give that one a shot. I had seen those sites but the models didn't exactly match mine and none of them seemed like regions that were for mine. I do see "XAR" in one of them though, so maybe that one will work. At work now and cannot run ODIN on the work laptop so it will have to be later when I return from work. Thanks!
In my case, I had installed the rom manager app, and tried to flash clockwork using it. I had thought rooting would be good enough, but I had forgotten to bypass the Verizon BS.
I had tried to boot to the recovery using the option in the app, which greeted me with that error, which will probably happen any time I try to boot into the device's stock recovery. I needed a quick solution, and managed to find it. If you just tried to manually enter recovery and it looped it, the results will likely be the same.
This doesn't look like it will work, and looks like pay bait, but it isn't. You can use the free trial to do the fix (which I have just wasted before I attempted to install my rom I wanted) and it will work without data loss. I didn't even lose root, which I would have using the popular method of re-flashing stock with ODIN.
Get this download, and follow the instructions. You will need a PC and you will need to have your phone hooked up to it and in download mode. It's quick and easy. The loading time seems long, but be patient as that could be a hard brick if you just unplug it (I'd give it at least 20min, but it took about 5 for me)
I don't know if it fixes the recovery, or really what it does, but it'll get you up and running in a pinch. Helped me, could help others with this issue.
https://www.fonepaw.com/bricked/recovery-is-not-seandroid-enforcing.html
Wrong forum this is not Verizon model forum .