Hey guys... So I'm REALLY new at this whole rooting thing, so please forgive me if I am not aware of any terms related to rooting and such.
So basically what happened was this:
I decided to root my Galaxy S4 (sgh-i337 --- AT&T) using the towelroot method. I had to use this method because my phone is currently running Android 4.4.4 KitKat (TouchWiz) and it worked fine. SuperSU was installed, Root Checker said my phone was rooted, it was good. I tried to install CWM using Odin, and I got the "RESET" or "PASS" from Odin, which I thought that it meant that it worked. However, when I tried to go into Recovery Mode, it went into Stock Recovery Mode. I started to look at other tutorials, and I came across another one that involved flashing your phone's respective CWM .img file from your phone itself (transfer the .img to your phone's SD, and then flash it from your phone using the app, Flashify). But when I tried to go into Recovery mode to see if it worked, it gave me the yellow triangle with an error message, "System software is unauthorized by AT&T" or something like that. I tried to look at other posts, and there was a general idea that I needed to flash the stock Kernel. Now, the way I rooted the phone in the first place, I already had two different ones downloaded. One was flashed, towelroot was used, and then the second kernel (which was the one that originally on my phone before rooting) was flashed. After that, it was rooted. So me, being the complete noob I am at rooting, decided to re-flash both, in order, to see if that cleared up the error message when trying to get into Recovery Mode. This did not solve the problem either.
Again, I would like to apologize for my lack of knowledge on rooting and such, so please forgive me for my incompetence. And yes, I know that there are other threads on topics like this, but I have tried several things and it has not worked. Any help on how to fix this problem (and how to install CWM properly on my phone - since it is updated to 4.4.4 TouchWiz - or if I should use TWRP instead, because I intend on downloading the Kangapop GPE ROM(and how to install that for my specific model/software version)) is greatly appreciated, thanks!
Related
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
First off, I have an Samsung Galaxy S4 ATT SGH-1337. I have lurked around these forums and have come to understand the rooting / recovery flash processes. Getting root on the phone is no problem using the following method: http://forum.xda-developers.com/showthread.php?t=2387577
Where my issue lies is within the recovery mode. I have tried GooManager / RomManager / CASUAL /ODIN and nothing I try seems to work. It short when I use CWM or GooManager or CASUAL everything works correctly and I receive no errors. When I first tried this i used GooManager and when it went to reboot into recovery mode It said COULD NOT DO NORMAL BOOT and put me in download mode - in short my stock recovery mode is gone/corrupted.
No matter what I try via (STOCK FW load for example) ODIN i always get a FAIL and can not get it to work. It should be noted that I have the correct USB driver installed also official USB cable and I've tried many versions of ODIN with the same result. It looks like it always fails on write. When I re-try the other methods to install a custom recovery they seem to work but I end up with the same COULD NOT DO NORMAL BOOT.
I thought I was stuck in this download mode until I rebooted the phone manually put in download mode and smashed VOL-DOWN. When I did this the phone booted up.
The strange part is that I have root, and can get into the OS, but all the recovery methods seem to fail. I have even tried the DD method via TWRP page with no luck.
I do not understand why this is the case, or why when I first did this with Goomanager it hosed my recovery mode. I am literally out of ideas, and have tired everything I can think of to get a recovery mode installed.
It should be noted that all the "gotya's" are enabled such as USB Debugging, and version verification. I do notice that when download mode appears, and i see COULD NOT DO NORMAL BOOT it does say "WRITE PROTECTION ENABLED". From my Googleing it would appear this is ok.
I have also made sure I was using the LOKI exploit; but it simply seems that my bootloader is locked no matter what I try.
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Ya5e said:
Hi all -
Model SAMSUNG-SGH-1337
Baseband: 1337UCUAMF3
Build: JDQ39.1337UCUAMF3
If anyone has any ideas I would greatly appreciate it.
Thanks
-Ya5e
Click to expand...
Click to collapse
One thing I could think of trying is taking a look at this video here on how to install CWM Recovery on the ATT Galaxy S4. As you watch the video make sure you've done everything exactly as he has done in the video, this way you can determine if you have overlooked or missed any steps.
Thanks for the video link. However it looks like this won't work due to the MF3 firmware.
Q6: I have a AT&T S 4 (OTA MF3) and I have rooted my device can I install a custom rom or a custom recovery?
The answer is "NO" you can not install a custom recovery or a rom at this moment.
Click to expand...
Click to collapse
I found the above in this thread http://forum.xda-developers.com/showthread.php?t=2413746&nocache=1
My phone came with MF3; I would assume this is the issue.
=(
Hey guys, after much digging I've been unable to find a solution to my problem. It may be my lack of technical knowledge or a unique issue, either way please bare with me.
I have a Galaxy S3 SPH-L710 that I have been attempting to root. In short, I used Odin to flash a CF Auto-Root tool. Unfortunately, it didn't quite do the trick because when I enter SuperSU, I'm given the prompt to update binarys and manually re-root. I know that's common, my issue is that when I attempt to enter recovery mode AFTER this I am presented a screen with a red android logo that says CF Auto-Root at the top. No recovery mode, no way to factory reset, seems as if my device is half rooted. Do I need to flash a stock rom through Odin to resolve this? If so, where can I find a current 4.3 version?
What I'd really like is to successfully root and load a custom ROM on this device which should be easy but has only proven to be a difficult process. As an aside could anyone possibly provide an updated guide to do this? Every one I follow has lead me to issues/incomplete rooting.
Thanks guys, I hope this isn't beating a dead horse too much.
xwm said:
Hey guys, after much digging I've been unable to find a solution to my problem. It may be my lack of technical knowledge or a unique issue, either way please bare with me.
I have a Galaxy S3 SPH-L710 that I have been attempting to root. In short, I used Odin to flash a CF Auto-Root tool. Unfortunately, it didn't quite do the trick because when I enter SuperSU, I'm given the prompt to update binarys and manually re-root. I know that's common, my issue is that when I attempt to enter recovery mode AFTER this I am presented a screen with a red android logo that says CF Auto-Root at the top. No recovery mode, no way to factory reset, seems as if my device is half rooted. Do I need to flash a stock rom through Odin to resolve this? If so, where can I find a current 4.3 version?
What I'd really like is to successfully root and load a custom ROM on this device which should be easy but has only proven to be a difficult process. As an aside could anyone possibly provide an updated guide to do this? Every one I follow has lead me to issues/incomplete rooting.
Thanks guys, I hope this isn't beating a dead horse too much.
Click to expand...
Click to collapse
You can just flash a recovery from odin and then flash a custom rom with su.Seems that the half-root hasnt damaged your recovery partition.
piano13 said:
You can just flash a recovery from odin and then flash a custom rom with su.Seems that the half-root hasnt damaged your recovery partition.
Click to expand...
Click to collapse
I was able to flash Philz Touch Recovery and through that fully root my device. I am now running CyanFox and so far pretty happy with it. Thanks for the advice!
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...
I've followed all the threads I can find here, and I've had no luck. Here's the situation. I had my S4 set up with root and the Stang5litre rom for a very long time. I wanted to put Xposed on it, and I completely forgot that it's not Odin friendly. First, I wanted to put TWRP on there, and that's where I messed up. I used the TWRP Manager app, and it said it was successful. On reboot I got the "Software Update Failed" screen. I can't get into recovery, but I can still get into download mode. Odin fails with everything I try saying either "Fail (Auth)" or that line 2012 could not be read. I found a thread here that looked very promising, but the files are no longer available, and I'm not even 100% sure that this is the best solution for me. I'd be happy with getting stock back, with the goal of later getting root and Xposed back on there. I've never been stumped with this before, but now I finally have to admit I need some help. I'd post an Odin log, but I want to know what I SHOULD be flashing, what settings to use, etc., and I'll send that log when I get it if it fails.
Valkrist said:
I've followed all the threads I can find here, and I've had no luck. Here's the situation. I had my S4 set up with root and the Stang5litre rom for a very long time. I wanted to put Xposed on it, and I completely forgot that it's not Odin friendly. First, I wanted to put TWRP on there, and that's where I messed up. I used the TWRP Manager app, and it said it was successful. On reboot I got the "Software Update Failed" screen. I can't get into recovery, but I can still get into download mode. Odin fails with everything I try saying either "Fail (Auth)" or that line 2012 could not be read. I found a thread here that looked very promising, but the files are no longer available, and I'm not even 100% sure that this is the best solution for me. I'd be happy with getting stock back, with the goal of later getting root and Xposed back on there. I've never been stumped with this before, but now I finally have to admit I need some help. I'd post an Odin log, but I want to know what I SHOULD be flashing, what settings to use, etc., and I'll send that log when I get it if it fails.
Click to expand...
Click to collapse
Why can't you go to Sammobile and download all your system files there, then flash them with Odin and start from square one? Or just use google to look for the required system files. Just put everything back the way you had or want it. I picked up an SGH 1337 AT&T phone and had to reflash everything to it with Odin. Yes, it was ponderous but it taught me a few things and steps which is why I hang out here anyway. Let me know if I can assist.
Valkrist said:
I've followed all the threads I can find here, and I've had no luck. Here's the situation. I had my S4 set up with root and the Stang5litre rom for a very long time. I wanted to put Xposed on it, and I completely forgot that it's not Odin friendly. First, I wanted to put TWRP on there, and that's where I messed up. I used the TWRP Manager app, and it said it was successful. On reboot I got the "Software Update Failed" screen. I can't get into recovery, but I can still get into download mode. Odin fails with everything I try saying either "Fail (Auth)" or that line 2012 could not be read. I found a thread here that looked very promising, but the files are no longer available, and I'm not even 100% sure that this is the best solution for me. I'd be happy with getting stock back, with the goal of later getting root and Xposed back on there. I've never been stumped with this before, but now I finally have to admit I need some help. I'd post an Odin log, but I want to know what I SHOULD be flashing, what settings to use, etc., and I'll send that log when I get it if it fails.
Click to expand...
Click to collapse
whatever android version your using or had, you can only odin back to that version an up. no downgrading. id think thats why your getting an auth failure. as for the twrp, far as i know, you cant have any custom recovery on a locked bootloader. however, you can use flashfire app to flash a required file to get xposed. i have tried it and works perfectly on the i545. you just get the alpha 3 i think apk of xposed and then get the zip of arter and be sure it matches your architecture. in my case it was krait. so i downloaded the krait zip and flashed using flashfire. took ten minutes or so to rebuild the cache. then all xposed worked perfectly. i believe there is a guide somewhere on here explaining it all. just be careful for if you flash the wrong zip, you get force closes in apps and the uninstall zip to correct it didnt work so i had to start over
The only thing that you can do is use odin to restore the stock firmware which you had beforehand.
Before I begin, I wish to apologize for my naivete, as I am just starting to scratch the surface.
Well, I'm stuck with my wife's old stupid verizon bootloader OF1 stuck junk. I have managed (with help from other posts on this forum) to root my phone using kingroot, switch root to supersu, and load all the necessary files for flashing step for step from http://forum.xda-developers.com/gal...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009. I also tried using rom from http://galaxys4root.com/t-mobile-galaxy-s4-roms/android-6-0-root-for-galaxy-s4-jdc-team/2/, to no avail. For whatever reason, the device wipes properly, installs the software, gives no error messages, and then just reboots into startup just like factory reset with the stock firmware (still rooted thank goodness). I made sure that I verified the root before proceeding, that it was supersu binary, and that all the files were stored and backed up on my external sd card. Flashfire was loaded in the order specified on the tutorial and I followed them to the letter. I'm just very lost at this, since I have rooted many devices, but never tried to flash a rom and it just factory reset.... very odd. On the plus side it didn't brick it so there's that glimmer of hope. Anyways, I really hope that someone could help me out on this one, or just tell me I'm crazy and there's no way it can be done on this firmware.
wstefan20 said:
Before I begin, I wish to apologize for my naivete, as I am just starting to scratch the surface.
Well, I'm stuck with my wife's old stupid verizon bootloader OF1 stuck junk. I have managed (with help from other posts on this forum) to root my phone using kingroot, switch root to supersu, and load all the necessary files for flashing step for step from http://forum.xda-developers.com/gal...ort-albe95-s6-port-4-5-updt-23-09-15-t3234009. I also tried using rom from http://galaxys4root.com/t-mobile-galaxy-s4-roms/android-6-0-root-for-galaxy-s4-jdc-team/2/, to no avail. For whatever reason, the device wipes properly, installs the software, gives no error messages, and then just reboots into startup just like factory reset with the stock firmware (still rooted thank goodness). I made sure that I verified the root before proceeding, that it was supersu binary, and that all the files were stored and backed up on my external sd card. Flashfire was loaded in the order specified on the tutorial and I followed them to the letter. I'm just very lost at this, since I have rooted many devices, but never tried to flash a rom and it just factory reset.... very odd. On the plus side it didn't brick it so there's that glimmer of hope. Anyways, I really hope that someone could help me out on this one, or just tell me I'm crazy and there's no way it can be done on this firmware.
Click to expand...
Click to collapse
*UPDATE* for anyone experiencing the aforementioned issue, I found a solution. Not quite sure which one of these actually fixed it, but my bet is on disabling Samsung's locked and found. Anyways, here's what I did:
1. Disabled Samsung locked and found.
2. Factory reset and cleared dalvik and all cache and the sdcard (internal and external).
3. Re-set up phone making sure not to enable Samsung locked and found.
4. Rooted with Kingroot
5. Switched root from kingroot to supersu
6. Enabled default in supersu to allow vs prompt
7. Downloaded required files to ext sdcard
8. Used flashfire to load rom in EXACT order as first post specifies with wipe first
9. Let it do it's thing (for whatever reason, my load took hours not minutes to complete so be patient)
10. Laugh at everyone on every other forum who says this can't be done
Again, this is on Samsung Galaxy S4 Verizon running 5.0.1 OF1 Firmware originally unrooted. IT IS POSSIBLE!!!
All files must be on device storage if u planning to use flash fire. for example in a download folder. Do not use SD card. I used Albe95 rom 4.7 port. Works very good and smooth. All u need is of1 wifi fix.zip
Thanks Sashaua04, but I have to disagree, as I tried it multiple times and that is the only way I got it to work. Again, not sure which of those steps worked for me, but I most certainly DID use my external sd card to store and flash the zip and that is the only way I got it to work. I tried using downloads folder on internal storage and it did not work. It did however work on ext. I say do whatever works for you. I'd love to hear from a pro why this is the case and why this happened like it did. I was thinking my binary was unofficial, but I checked in download mode each time and it was official, but it said something about Samsung lock active, and after disabling and making aforementioned changes, it worked. Maybe that had something to do with it. Strange... maybe I had a bad download or
something...