yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] caine0001:
I don't think anyone is having any problem rooting. The issue was installing CWM and getting it to remain as the recovery for the Express i437. I have been rooted for months and he mentioned that he was rooted already also. He just can't find a file on his Express i437 that is on every one of them when they come out of the box.
[Android Q&A, Help & Troubleshooting] 1whttcdreamer:
My experience....

For what it's worth, I rooted and installed CWM on my son's express after I got it just a mere three weeks ago from AT&T and last I checked the CWM recovery was working rather than the stock recovery and I for one NEVER found the file everyone is talking of...... I serarched the phone inside and out and never did find it...... :confused: but as I said CWM was the recovery being used last I checked..... In a side note many thanks to everyone for their hard work and information........ :highfive:
[Android Q&A, Help & Troubleshooting] caine0001:
I find that very interesting. I wonder if the phones that have been sold since the JellyBean update do not have the files? Without them CWM would install perfectly and remain your recovery. The only downside is that to get back to stock you would have to use a stock recovery image instead of just being able to do it by naming the file back to its original name. For that reason, I am glad that mine has the files. I don't mean to be redundant, but I find this little revelation to be quite interesting. Why would they stop putting that file on the phone?

Oh well anyway, do you mind me asking what method you used to root your phone? Did you use the motochopper.zip file or some other method? I am asking because I am wondering what all the script contained that ran to root the phone. I used motochopper's rooting file to do mine. Do you mind telling me what method you used?

---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------

I also wonder if you were to put those files on your phone, if they would serve the same purpose as they do on my i437?
[Android Q&A, Help & Troubleshooting] aureljared:
I quite agree with the non-existence of the sh file. I can't find it anywhere. Straight out of the box too.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
I definitely had trouble with the HTC Thunderbolt 4G doing an OTA with CWM, which that phone was also a REAL piece of work :). I can't remember any other phones at the moment. I remember accepting OTAs with the Galaxy Nexus with CWM and it was smooth. I just assumed that you had to have a stock recovery on certain phones in certain situations. That's why I asked for clarification.

I bought this phone directly from a corporate AT&T store and it had Jelly Bean from day one, I didn't have to update at all. Granted, I got this as a GoPhone promo so maybe they are a different batch from Samsung. I originally rooted the phone with Motochopper. I rerooted with SuperSU after a factory reset (slowness issue), even though I probably could have used Voodoo to reroot (I like SuperSU better). I don't have the "recovery-from-boot.p" file in my system folder.

I'll test the file out in my phone and see what happens.
[Android Q&A, Help & Troubleshooting] caine0001:
Are you saying you want the file? If so, tell me where to send it. If not, explain what you mean by that last sentence, please.

---------- Post added at 12:04 PM ---------- Previous post was at 12:01 PM ----------

Have you been talking about the 8730 all this time? I noticed that is in your sig. Because there are differences between the 8730 and the 437 which is what I have been talking about all this time.

---------- Post added at 12:08 PM ---------- Previous post was at 12:04 PM ----------

This would support my theory that they eliminated the files on phones sold with JellyBean factory installed.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Yes, I'll test it out.
[Android Q&A, Help & Troubleshooting] caine0001:
Since I can't attach anything to a PM on this forum here are the links to both files, "install-recovery.sh.old" and "recovery-from-boot.p.old".

https://docs.google.com/file/d/0B5Z4Qi00TO4PSE1xYk9oX0J1c2s/edit?usp=sharing

https://docs.google.com/file/d/0B5Z4Qi00TO4PZzc2Y0kzd2tWTUk/edit?usp=sharing

All you have to do is place them in the proper folder on the phone and then rename them to "install-recovery.sh" and "recovery-from-boot.p". I didn't want to do any renaming as I was moving them around because I didn't want to take the chance that they would get compromised being renamed on a different Operating System. So anyway, put "install-recovery.sh.old" in the /system/etc/ folder on the phone and rename it back to its original name by removing the .old and put "recovery-from-boot.p.old" in the /system/ folder on the phone and rename it to its original name by removing the .old. Once they are both in the proper folder and named back to their original names just turn off your phone and reboot into recovery mode (Power, Home, and Volume Up buttons) and you should get a message that will be your first clue that it is restoring the original stock recovery. Just let it do its thing and you should boot into the stock recovery that originally came on the phone. That is, if it works on your phones like it did on mine. Please let me know what happens.

I think you just have to do the turning off and then reboot into recovery the first time. But now that I think about it, you might have to let the phone reboot once without going into the recovery mode to let it pick up on the newly named files. Then turn it off and boot into recovery.

Well, that is it. If it works you will have a very simple quick way to move back to stock recovery like I can. Give it a whirl and let me know what happens.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Anyone experience periodic random reboots on this phone? I seem to get one every week, sometimes less though.
[Android Q&A, Help & Troubleshooting] caine0001:
Yes quite often actually. I also experience quite often times when someone will call but the phone doesn't ring even though the incoming call is recorded in the logs. They are not in the Auto Reject list and the ringer is set to the default ringer and works on most calls. It is just that sometimes it doesn't ring for some reason. Also, some of the alarms that I have set do not go off or if they do it is just for a second and then they stop, but when the snooze goes off they work right. It isn't all of the alarms, just sometimes on certain ones it seems, but I can't figure out what is the commonality between the ones that act like this. These are the 3 problems I have found with this phone in my experience.
[Android Q&A, Help & Troubleshooting] @ARC-S@:
Hi everyone, here's a software which MAY root the Samsung Galaxy Express. (I do not own this device YET, I will get my unit by September)

Link: https://www.dropbox.com/s/jnwl5r3fnsssbuu/Eroot_V1.3.4.exe

IMPORTANT!!!!

1. Remember to tick "allow" for Unknown Sources in security settings!!!

2. USB Debugging MUST be enabled!!!

3. USB connection must be in MASS STORAGE MODE!!!

4. ADB drivers MUST be installed on your computer!!! (I don't know where to get these, sorry)

1) Connect your phone to PC and wait for the adb drivers to be installed. If these drivers don't get installed, phone would not be detected by Eroot.

Make sure nothing else is running on your PC in the background.

2)It should now detect your phone and show an option to "-root". Just click on it, wait till it finishes

3)Rooting done ( For confirmation see if any Super User app has been installed )

4) If by chance it fails for the first time, give it another go. it won't harm your phone in any way.
[Android Q&A, Help & Troubleshooting] aureljared:
Why do you need to suggest another rooting method when there are two methods discussed within this thread beforehand?
[Android Q&A, Help & Troubleshooting] caine0001:
I don't understand the need for another rooting method when we already have a couple of options that require much less work than what this description depicts. For instance, I used motochopper's method and all it required was being in USB debugging mode and having the Samsung drivers installed. You don't need any of the other steps described here. And what is better is the fact that we know that these couple of methods work for sure, whereas this is a big MAYBE, which is potentially dangerous.
[Android Q&A, Help & Troubleshooting] tmdeee:
This forum should help with the phone ringing problem, and maybe the other problems, too. Save yourself some time and look at the latest post and work your way back. I am not allowed to post links yet, so you will have to enter manually, sorry! If you find it useful, maybe you can re-post it as a link.

forums[dot]att[dot]com/t5/Android-Discussion-and-Support/Samsung-Galaxy-S3-Not-Receiving-Calls-Phone-issue-or-Android/td-p/3270741
[Android Q&A, Help & Troubleshooting] @ARC-S@:
It's just a suggestion. And the method does NOT harm your device in any way, it's NOT dangerous. I was just trying to help, for me this method seems just as easy. By the way, I don't see how adding another rooting method is bad, I don't see how this is dangerous, I don't see how testing is dangerous, neither do i think it's hard to connect your phone to your computer and click on the "root" button. I just see you giving me all these negative bullsh*t.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
I read through the forum article and the suggestions for missing calls were turning off LTE, rooting and upgrading to 4.2.2 (not possible without a developer), or turning off the auto reject list.

Taken from the forum by another poster...

"For all of those who have this problem with your samsung smartphone. what happens is that samsung has an auto reject list function on their smartphones which automatically blocks some contacts to which you deny calls from. This function is activated by defaul, but you can always go to the phone icon on your SG. Then hit the "MENU" key and scroll down to the "CALL SETTINGS" then go to "CALL REJECTION" and set "AUTO REJECT MODE" to OFF. You can always check your auto reject list."

I turned mine off as a safe measure. I didn't experience it as much as others have. I originally attributed it to Google Voice and ported out to GoPhone, but Google Voice was buggy for me anyways. I haven't observed the missed call issue since porting into AT&T either so we'll see.
[Android Q&A, Help & Troubleshooting] caine0001:
First of all, why the foul language? I only posted that because you said yourself that it MAY work. For those that do not have great skills when it comes to using all of these tools or from recovering from mistakes, it isn't going to be a good thing if it bricks their phone or does something else bad. There are already 2 proven methods that work for sure, so I was just pointing that out. But in this post you say there is no danger at all and no harm. How do you know if you have never tested it and do not even have one of the phones? Surely you can see the trepidation others might feel at a post that MAY work that has not been tested by the poster who does not even have the phone. And even if my post was irresponsible, which it wasn't, there certainly is no need for foul language to relay a point.

---------- Post added at 09:50 AM ---------- Previous post was at 09:45 AM ----------

Turning off AUTO REJECT does not work for me. I have turned off cellular data to experiment with that. If it doesn't work, my next step is to try turning off Wifi until needed. All of these steps are based on suggestions made by others. I will let you know if any of them work. It will take a few days to try them all though since I have to wait for calls to come in to test it. And since it is a random thing, I have to try each method possibly for days. But I will report in and let you know.

---------- Post added at 10:01 AM ---------- Previous post was at 09:50 AM ----------

Just so that you know, neither I nor anyone else that posted about your rooting, meant anything negative in a bad way towards you. I am sorry if it came out that way. I just noted that you said it MAY work and I thought about those that are new to this and if it goes bad for them. It would put them in a panic for sure and they don't know how to recover like you might or I might. Please don't think anybody was ganging up on you. And no matter what, I believe that you could have made your point without the foul language. I am sorry you took my post so badly. Again, I didn't mean to upset you or make you mad.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Kinda going off topic with this but I figured I'd share this in case anyone wants to improve performance on their Express:

I observed periodic slowness that got really bad on this phone. It wasn't until I made a bunch of adjustments that I noticed a significant improvement. I also rooted the phone and did a factory reset, didn't help that much. I followed the suggestions from both sources below and the Express is now a zippy phone...

http://www.androidauthority.com/samsung-galaxy-s4-tips-tricks-207516/

http://xdaforums.com/showthread.php?t=1932366

Mind you that these suggestions are for different Samsung phones but nonetheless, the information can be adapted for utilization on this phone too.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Silly question, but did you restart your phone after making that change and still observe the issue?

I wonder if 4.2.2 (or 4.3) would resolve that issue. Anyone know if Samsung plans to upgrade the i437 to it? After reading the thread, I also wonder if part of the issue lies with a infrastructure issue on AT&T's network that needs to be addressed. Heck, it could be congestion.
[Android Q&A, Help & Troubleshooting] caine0001:
Yes I have restarted it and didn't make a difference. I am betting that 4.2.2 will fix it for us too. So I hope they will roll it out for the Express too.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Hey, so I flashed back to stock last night and was unable to upgrade it from ICS to JB no matter what I tried. I initially did a ODIN restore to ICS and was unable to use wifi. Then, I hooked the i437 up to my PC and did a restore with Kies. After it rebooted, wifi worked but I am still unable to get the device to pull an update to JB. In addition, Kies will only update this phone up to ICS. Does anyone know what gives? I'm kinda stuck unless AT&T would upgrade the firmware for me. This is making me nervous about this phone...
[Android Q&A, Help & Troubleshooting] oldnoob:
After messing with my phone I was having trouble getting the upgrade also. I wound up downloading the full ICS stock image from sammobile and flashing it through Odin to really get it back to stock, only then was I able to upgrade OTA.
[Android Q&A, Help & Troubleshooting] caine0001:
When my Express is hooked up to Kies it reports that this phone's firmware is not able to be upgraded by means of Kies. It has said that from the day I bought it. I got a second Express and it says the same thing. It doesn't matter if it is rooted or unrooted. Why is this feature not available for the Express??
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Just an update, nothing would allow this phone to do an OTA nor Kies update to 4.1.2. I ended up just going to an AT&T device repair store and they were able to do the firmware update, which is not desirable as it takes time out my schedule to do that. But, it makes no sense why Kies nor the OTA feature couldn't find the upgrade file. I'm hoping that the AT&T software gave the phone a little kick so that next time it won't have an issue. I REALLY don't like being dependent on AT&T for firmware updates. Anyone know where we can get a legit stock update file?

I contacted Samsung regarding the matter. They state that they only have firmware updates up to 4.04 for this phone and that AT&T is the only source to get the update and that they should have the update eventually. I don't know who at AT&T to report that the OTA to 4.1.2 is no longer available.
[Android Q&A, Help & Troubleshooting] caine0001:
If you want to update from ICS to JB 4.1.2 then go here: http://xdaforums.com/showthread.php?t=2240989&page=9 and halfway down the page melkis has posted that he solved the problem. It seems to work. It is a legitimate working fix. He includes the link to the update file and gives instructions on how to apply it. I think it should fix your problem.
[Android Q&A, Help & Troubleshooting] jt1134:
Been in the market for a new device for a while, saw an Express on sale at wal-mart for $150 on prepaid...msm8960, good price, etc, so I snagged it, why not. It came with 4.1.2, and I've made backup images of the device, I'll probably upload them at some point so other users can use them.

Here are some pictures I took of my device, I figured at least a few folks would find them interesting :)

http://imgur.com/KWjos9U

http://imgur.com/3WEw88t

http://imgur.com/QT5IT8m

http://imgur.com/4LFV6XK
[Android Q&A, Help & Troubleshooting] caine0001:
I see that you have CWM 6.0.3.3. According to a well respected member here, I was told that the only CWM we could use on the Express was the OUDHS based version 1.0.3.3 and that there was no CyanogenMod available for it. So you installed them both and they work ok?

---------- Post added at 04:38 PM ---------- Previous post was at 04:35 PM ----------

According to your pictures you also have version 4.2.2 installed. How have you done all this when I haven't found anybody else that has been able to do any of them? Just asking because I would like to have 4.2.2 installed on mine too.
[Android Q&A, Help & Troubleshooting] jt1134:
I didn't get these files from someone else, I ported both CWM and CM10.1 to the device myself. The pictures are taken from the first initial build. As of right now, I'm the only one who has the files ;)

CWM works perfectly fine AFAICT, CM10.1 needs a lot of work, at the moment hardly any hardware works.
[Android Q&A, Help & Troubleshooting] caine0001:
Well, I can honestly tell you that I am jealous, but I am happy for you. It has to be nice to have 4.2.2. I was wanting it because a lot of people said it would probably fix the Express not ringing sometimes. And congrats on the CyanogenMod. Although you are the only one to have them, it does give the rest of us hope that someone is going to port it for the rest of us. It is the first glimmer of light we have had. Again, I am glad for you. Enjoy!

---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------

I tried the CWM 6.0.3.3 on my Express JB 4.1.2 and I just get a black screen. Either something is wrong with my phone or maybe it is just going to work with 4.2.2 on the Express. Guess I will be sticking with the OUDHS based version. According to your pics though I don't see any features that are on the 6.0.3.3 that aren't on the OUDHS version. So I am good with that, but I am excited that we may get 4.2.2 someday.
[Android Q&A, Help & Troubleshooting] jt1134:
Lol well don't be too jealous. As I said, these pictures are from the very first build. The only functional hardware is the touchscreen and the accelerometer. You can't make/receive calls/sms/mms, can't use the camera or anything else that relies on the sdcard, audio does not work, etc, etc. It's not usable in any manner right now other than development.

When a usable build has been completed, it will be published for other users. If I can get it stable enough, it will be submitted upstream for official CyanogenMod support and builds. I only made my initial posts because I was happy with the rate of success thus far (only had the phone for 2 days) and wanted to share :)
[Android Q&A, Help & Troubleshooting] caine0001:
Still, your efforts deserve recognition. No one else is making much of a public splash about trying to do much for the Express. So I for one am elated to have some legitimate talent working on it. Thank you.

On a slightly different subject, did you have to put 4.2.2 on your phone for CWM 6.0.3.3 to work, or did it work while you still had 4.1.2 still on it? I won't bother you with a bunch of questions, I promise. But I just have to know the answer to that one because of how my phone is doing.
[Android Q&A, Help & Troubleshooting] jt1134:
Thanks. The main obstacle at this point is the bootloader. There's a few options for that, but still a work in progress. Once when can flash custom kernels the rest will be a piece of cake ;)

I can't really speak to issues with other recoveries and what not that are floating around, as I've only flashed images that I've personally prepared. CWM should work fine with any firmware, I used it with 4.1.2 with no problems. I'll upload a copy of my CWM image when I get home from work tonight.
[Android Q&A, Help & Troubleshooting] caine0001:
That would be great. Thanks. I was wondering if there was ever going to be a little more up-to-date version that I could use with my Express. If it works that will be great. If not, I don't lost anything, I just go back to the OUDHS version 1.0.3.3. Oh, and sorry I bothered you at work. I will keep an eye out for your post later. Thanks again.
[Android Q&A, Help & Troubleshooting] caine0001:
In other posts I read that JellyBean grabs a chunk of memory and keeps it in order to be able to run new commands faster. The total memory usage you see isn't what is being used. It is a total of what is being used as well as the amount JB is holding in reserve for its use. According to what I have read the purpose is to make things happen faster since the OS already has control of the memory in its reserve. Don't flame me if this is wrong. If you look hard enough you will find it is in print on this forum somewhere.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
In case anyone is interested, the downgrade to ICS and upgrade to JB (AT&T assisted) seems to have cleared up the random reboot and overall slowness issue I was having. Those links I posted a few days back helped but kicking the phone back to ICS cleared something that a factory reset or a dalvik and cache wipe doesn't. I don't know what it was but my phone is much more responsive and seems MUCH better.

I should also mention that they also replaced my SIM card because I couldn't access LTE anymore.

I tried this out even while downgraded to ICS and it did not revert to stock recovery.