yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] caine0001:
Sorry it didn't work for you. It isn't surprising though. If they removed the files from the phone it was for a reason. It was a shot in the dark to give it a try. I am glad that I got mine while these files were still on there. It makes it so easy to revert back to the stock recovery just having to rename a file and reboot. Maybe they removed it for that reason. If you mess with the phone they don't want to make it easy to erase what you have done, or they thought that by using those files it would prevent us from being able to use custom recoveries but once a workaround was discovered it made it useless to keep going through the extra effort to set the phone up like that. Either way, it seems that now the only way to get back to stock recovery is to actually install one once you find a copy.

---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------

Are you saying that if we downgrade to ICS and then upgrade back to JB that we will not be able to access LTE anymore? Or do you think that it was just something about your phone itself?

---------- Post added at 07:48 PM ---------- Previous post was at 07:27 PM ----------

I have officially tried turning off Auto Reject, wifi, and cellular data in order to fix the not ringing on some phone calls. None of them worked. It is interesting that I had my wife's phone and kept calling trying different things and it wouldn't ring. It just logged that she tried to call but if I hadn't been looking at the phone I would not have known that her phone had called. UNTIL, I assigned a custom ringtone to her contact and now EVERY time her phone calls it rings. Weird, huh? Anyone get any ideas from that as to what is the problem?

I will say that on the subject of getting your phone to be more responsive and to run faster, I simply applied a nandroid backup that I made about a week ago and all of a sudden the phone is running faster and better than it ever has. I didn't do anything else. It seems from this experience and from the one mentioned a few posts ago, that when you install a backup it seems to sometimes do something that makes the phone "wake up", for a lack of a better phrase. My battery life is even extended far beyond what it was before. The weird part is that the backup contains the same settings and apps as the phone did when I decided to install the backup. Go figure...
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
When I was on ICS, I still had LTE. The upgrade to JB or "master reset" AT&T did is what killed the LTE connection. I strongly suspect it did something to the bond between the phone and the SIM. I'm using GoPhone and I understand that the SIM "sticks" to the phone for 6 months or so.

So, custom ringtones are helping with the missed calls?
[Android Q&A, Help & Troubleshooting] caine0001:
I have not missed another call from my wife since. But you can't assign a custom ringtone to people you don't know are going to call. But it does fix the not ringing problem on my phone for those in my contact list that it wasn't ringing for anyway.

EDIT: I am now finishing my third day and I have not missed another call from anyone that I used to. And all I did was give them a custom ringtone. Go figure. I don't have problems with everybody, just certain callers.
[Android Q&A, Help & Troubleshooting] screamingatawall:
sorry, i don't have time to search through the whole thread

i already have jellybean - i just want to root to be able to uninstall all the att/samsung bloat crap - i know most people's reason is to get jellybean would i be wise to root if i already have it? would i need to do anything special to keep it, or will i just see it when i get root uninstaller and i'll know not to uninstall it?

also - at unlock root - is it unlock flash free that i want? i don't see an unlock root pro to download for free
[Android Q&A, Help & Troubleshooting] caine0001:
Most people's reason for rooting isn't to get JellyBean. There are a whole host of reasons for rooting. If you have the i437 Express with JellyBean on it, you can use the motochopper method for rooting.That is what I did and I already had JB. You won' have to do anything special to keep JB. Rooting will just give you su access to the filesystem. Here is the link to the motochopper zip file: http://vulnfactory.org/public/motochopper.zip

Just unzip it and run the file "run.bat" from the command line after you make sure you have the Samsung drivers installed and USB Debugging checked in your settings under Developer Options on the phone. Just in case you don't know how to do it, you need to put the phone into Download mode. You do this by pressing the Home button, Power button, and the Volume Down button at the same time while booting up. Then connect the phone and run the rooting file mentioned above.
[Android Q&A, Help & Troubleshooting] screamingatawall:
and the launcher and any apps i already have will still work the same?
[Android Q&A, Help & Troubleshooting] caine0001:
Yes. Some apps (depending on which ones you have) may have extended abilities. But all of them will still work at least like they do now if not better.
[Android Q&A, Help & Troubleshooting] screamingatawall:
well i thought i had to drivers installed cuz its worked when i connected it before - but when i plugged it in after download mode, it said drivers not found - the root program says daemon started succesfully tho - am i screwed? - can i just download the drivers now from somewhere?

---------- Post added at 07:56 PM ---------- Previous post was at 07:46 PM ----------

i installed the drivers - should i just close the command window and re-run it?
[Android Q&A, Help & Troubleshooting] caine0001:
Disconnect the phone and then reinstall the drivers that you had on there before that worked. Then put your phone in Download mode and attach to USB. Then run "run.bat".
[Android Q&A, Help & Troubleshooting] aureljared:
Yay
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
So, was this a custom ringtone for everyone, ie changing to a non-official ringtone in Settings. Or was this a regular ringtone that you specified for individual individuals?
[Android Q&A, Help & Troubleshooting] caine0001:
I just simply had to apply a ringtone. It could be anything even the default ringtone, just as long as it was officially assigned and it didn't just say "Default" under Ringtone for that contact.
[Android Q&A, Help & Troubleshooting] MkVsTheWorld:
Interesting. I'll have to do that.

---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------

If anyone is looking for TPU S-Line cases for this phone, they are finally available on EBay. I just ordered a 3-pack for myself and the seller was communicative as well as versed in English (Hong Kong seller shipping to the US). Here is the listing...

http://www.ebay.com/itm/8-colors-S-...Cell_Phone_PDA_Cases&var=&hash=item5d4128f91d
[Android Q&A, Help & Troubleshooting] Everhez:
Yeah!!! CM 10.1!!! Please Begin a Thread!!!

Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
[Android Q&A, Help & Troubleshooting] jt1134:
Here's an updated version of CWM for the Express. Sorry it took so long to upload. Real life sucks sometimes.

It seems to work fine for me, I've been using it to switch back and forth from stock to CM10.1 test builds, and haven't had any issues.

No ETA on anything additional, particularly any CM variants as there are still plenty of technical hurdles to overcome as far as the kernel goes.

http://www.mediafire.com/download/pi61tbbgl5wegdd/CWM-6.0.3.4-SGH-I437.tar

md5sum: 7360dd1211dc382193adabd1d36f3b0d

This will only work on the SGH-I437 for AT&T. It will NOT work on the GT-I8730 international version. These 2 devices are fundamentally different and there was no reason for Samsung to name them both "Express".
[Android Q&A, Help & Troubleshooting] jt1134:
I will when it's the worth the trouble to do so :p
[Android Q&A, Help & Troubleshooting] aureljared:
Aww. That's so unfair. Any chance you would develop for the Express? Like ask for a build.prop or a recovery.fstab or something. Please :(
[Android Q&A, Help & Troubleshooting] Everhez:
how do I install it if I have the version of OUHDS? just flash again the recovery?

Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
[Android Q&A, Help & Troubleshooting] caine0001:
The same way that you installed the other version. Use ODIN and the new .tar file and you are walking down Happy Street....

**EDIT** Make sure you create your Nandroid first with the other version just in case you have a mishap.
[Android Q&A, Help & Troubleshooting] Everhez:
as do the nandroid?

Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
[Android Q&A, Help & Troubleshooting] caine0001:
Sorry but I don't understand what you mean?
[Android Q&A, Help & Troubleshooting] Everhez:
you say you need to do the nandroid with the previous version but I only did that of OUHDS than once, I have no backup of the original recovery

Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
[Android Q&A, Help & Troubleshooting] caine0001:
What I said was the "other" version. I meant other than the 6.0.3.3 version that you are putting on. So that would be the OUDHS version you have now. Do your backup with it just in case you run into a problem installing 6.0.3.3.
[Android Q&A, Help & Troubleshooting] Everhez:
Ok thanks

Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
[Android Q&A, Help & Troubleshooting] aureljared:
Oh my gosh how did you get CM 10.1?

Edit: Lol I realized that the CM repo is bundled with CWM.

Also, I don't see much defference between the values of my log and your log. Except for the device name. Why does everyone say the two phones are "fundamentally different"? Anyone please explain.
[Android Q&A, Help & Troubleshooting] BlushNine:
If I have followed the thread correctly, I believe he's only got a barebones kernel running without any functionality. But I guess he can answer that more precisely, but just in case he's busy and doesn't respond immediately, last time I checked this thread he didn't have a dialer nor camera or anything like that working yet. If anyone has tried it let the rest of us know. I think a few of us are anxious to hear any progress.

Samsung screwed up and labeled two very different phone models, i437 and i8730, Galaxy "Express". They liked the name so they decided to use it again. Result: customer confusion. If you have an i437 don't use stuff for the i8730. If you have an i8730 don't use stuff for the i437. They are just different phones that look the same on the outside.

And please don't quote such a long post, especially if it serves no purpose to copy it. I think I just wore out my mouse scroll wheel :P
[Android Q&A, Help & Troubleshooting] pc boy:
We would be more than thankful if you could just develop a working CWM for I8730!

Please:(
[Android Q&A, Help & Troubleshooting] jt1134:
I have an i437 device, not an i8730. You see the dilemma.

Blind-developing for specific devices is difficult enough, and these 2 devices have completely different boards making it even more difficult to port things back and forth. There was no reason at all for Samsung to call both devices "Express". But, it's Samsung, they do stupid **** like that all the time.

It's typically not difficult to port CWM to devices, particular unlocked qcom devices. The code for everything I'm doing is on my github[1], anyone can get an idea for what's going on if they have a different device and the initiative.

[1]:

https://github.com/jt1134/android_device_samsung_expressatt
[Android Q&A, Help & Troubleshooting] jt1134:
Thanks to Samsung's awesome QA in their development department, they've released broken source code for yet another device. The source code for the SGH-I437P (prepaid, "GO" version of the I437, exact same hardware...) is completely broken. Don't use it. This cost me quite alot of time. Thanks Samsung, it would've been easy enough for you to fix it first, yourselves.

If you would like to try compiling custom kernels for the I437, you may start here. That codebase works well with stock Samsung 4.1.2 ROMs. It's old and dated and boring though, so I'm working on porting the i437 drivers into the d2 (SGS3) kernel codebase[1]. This allows the use of a muuuuuuch newer (3.4.54) kernel, userland drivers, and ongoing baseline support (a la MSM8960 variants common base). This is a tedious process, but it's going well so far, steadily including each bit of hardware support :) The device tree I am currently using is also on my github, for anyone who wants to mess with it.[2]

I'm not releasing anything yet, nor starting a thread as only very basic hardware currently works. I'm also extremely busy, and posting on forums is boring, staring at code is more entertaining. Essentially all progress was lost when switching to the new kernel base, but features are getting fixed, and it will make things much easier in the long run (eg: 4.3+). So far the touchscreen, audio, sdcard, LED flash, usb/mtp, and charging are working. Everything else is broken or only partially functional.

[1] https://github.com/jt1134/android_kernel_samsung_d2/commits/express

[2] https://github.com/jt1134/android_device_samsung_expressatt
[Android Q&A, Help & Troubleshooting] oldnoob:
Thank you for taking the time to develop for our device, your talents are greatly appreciated.

Just stumbled on another update Samsung released for it, but I think it's only a modem update though I437UCDMG3.
[Android Q&A, Help & Troubleshooting] caine0001:
Is there a link to it?
[Android Q&A, Help & Troubleshooting] Everhez:
first of all thank you friend thank the hassle to develop for our phone as we need to exploit the potential, really thank you very much

Enviado desde mi SAMSUNG-SGH-I437 usando Tapatalk 2
[Android Q&A, Help & Troubleshooting] caine0001:
Once again, can you post the update file or the link to it, please? Or does anyone else know about this and could post it up? It definitely seems to be an upgrade to our modem, because the Baseband version that is currently installed with the JB update is I437UCCMB3. I for one would like to give it a whirl unless any of the experts and highly knowledgeable people here know of a reason that I shouldn't. I have my CWM backups so I believe that I would be covered if it didn't work. Thanks.

---------- Post added at 12:50 PM ---------- Previous post was at 11:52 AM ----------

I am rooted and have CWM installed just so that we have that out of the way. Anyway, I was attempting to install the new AT&T update from July 31, 2013 (yesterday). It is 80.04MB. Here is the info from AT&T on the update:

"How to verify the update

From the Home screen, drag the notification bar, and then tap Settings.

Scroll down and tap About phone. The following information will be displayed:

Android version: 4.1.2

Baseband version:

For Galaxy Express (i437), I437UCBMG3

For Galaxy Express (i437p), I437PUCBMG3

Build number:

For Galaxy Express (i437), JZ054K.I437UCDMG3

For Galaxy Express (i437p), JZ054K.I437PUCBMG3"

Well anyway I did a temporary unroot and went to install the update. It downloaded 99% then took about 5 minutes to download the last 1%. But it did it and said it would reboot and install the update. It rebooted into CWM recovery and attempted to install it but I got this message:

E: Invalid command argument

Finding update package...

Opening update package...

Verifying update package...

E: failed to verify whole-file signature

E: signature verification failed

Now at this point CWM asked if I wanted to go ahead and install anyway even with unknown signature and I said "yes". Then it continued and this is what I got next:

Installing update...

Verifying current system...

assert failed: getprop ("ro.secure")=="1"

E: error in /cache/fota/2400258.cfg

( Status 7)

Installation aborted.

So needless to say that the update did not install on the phone. Can anyone tell me exactly what the problem is? Why did the signature fail? And why did it fail to install? Was it because of CWM, being rooted even though unrooted temporarily, that caused the signature to be unknown and also to fail to install? I would sure appreciate any answer from one of the experts here, please. Thank you.
[Android Q&A, Help & Troubleshooting] invert_nexus:
You have an insecure kernel?
[Android Q&A, Help & Troubleshooting] oldnoob:
Guess you found it already, but in case anybody else wants info on it:

http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00051307&fm_seq=56779

It doesn't link to the software, you have to get it OTA.

---------- Post added at 01:45 PM ---------- Previous post was at 01:28 PM ----------

Sounds like the same error I had on the last update. It didn't like CWM, I had to revert to the stock recovery to get it installed.

I have a different problem now, my "Update software" button doesn't work. Maybe I froze one too many things with Titanium Backup, maybe it doesn't like the custom counter in download mode. Guess I have to play around some to figure out what I broke.
[Android Q&A, Help & Troubleshooting] caine0001:
Yes, shabbypenguin told me that I have to revert back to stock recovery. I did. But the Software Update button was froze for a minute and then when it worked again it said my software was current and to check back in 24 hours. So now I am afraid that my phone is thinking it has been updated when it hasn't been (I checked the Build and Baseband version numbers to verify that the update did not work). But I am hoping that since it downloaded the whole thing that it doesn't think that the update is done.

---------- Post added at 02:00 PM ---------- Previous post was at 01:49 PM ----------

did you have the same problem of trying to do the OTA with CWM first and then when you realized the problem you reverted to stock and tried again and then had to wait or 24 hours to try again? Just asking because as you can see from my previous post, that is what has happened to me.
[Android Q&A, Help & Troubleshooting] oldnoob:
On one of my previous Samsung AT&T phones there was a trick to trying the software update again. If you cleared the cache from recovery it would let you download again. Haven't tested it on the Express, but if you're impatient like me you may want to give it a try.
[Android Q&A, Help & Troubleshooting] jt1134:
Update files are typically downloaded to /cache. They usually have a very long, strange file name also, making them easy to identify. It can be pulled from the device with adb, etc.
[Android Q&A, Help & Troubleshooting] oldnoob:
Thanks for the info. Always wondered where those files went. Also wondered why clearing the cache worked. Guess 2+2 isn't my strong point :)
[Android Q&A, Help & Troubleshooting] jt1134:
Lol totally missed this part. The update file is stored at /cache/fota/2400258.cfg. Sneaky Samsung, no one would ever find the zip file if it's named cfg :rolleyes:

Someone should pull the file and post it up somewhere.
[Android Q&A, Help & Troubleshooting] caine0001:
After the error message I went to get the file in /cache/fota/ but there were no files there at all.
[Android Q&A, Help & Troubleshooting] oldnoob:
Not quite. My experience with that error was the first day I had the phone and managed to screw up a bunch of stuff. I'm talented that way :) I Odin'd back to stock and then did the upgrade. In your case I would suggest restoring stock recovery, then going into recovery and wiping "cache", then reboot. You should be able to re-download the update immediately after that.

Mu current problem was that I froze the AT&T OTA Update app with Titanium Backup. Defrosted it and the update went well (I was already on stock recovery). The update loses root, so I would suggest installing OTA RootKeeper first, or have motochopper ready.
[Android Q&A, Help & Troubleshooting] caine0001:
Got both of them ready to go. I am anxious to see if RootKeeper works for this. But if not, I have motochopper standing by at the ready. Thank you for the advice though. Sometimes we don't think ahead and suffer for it.

---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------

Wiped the cache using the stock recovery but no go. It still says I have to wait 24 hours (well now 19 hours) before I can try again. I checked the /cache folder and it is cleaned out. I guess that don't work for the Express.
[Android Q&A, Help & Troubleshooting] invert_nexus:
Set your system time ahead one day manually.
[Android Q&A, Help & Troubleshooting] caine0001:
Did you just wipe the cache partition or also the davlik cache when you got it to work?
[Android Q&A, Help & Troubleshooting] oldnoob:
Just cache, but it was a while ago on an Infuse running Android 2.x. You can try the date thing as was suggested by invert_nexus, it sounds like it has potential. You also have PM.
[Android Q&A, Help & Troubleshooting] caine0001:
Gonna try the clock thing. And I replied to the PM. Hoping something works. Hate waiting. But don't we all?...

---------- Post added at 05:58 PM ---------- Previous post was at 05:22 PM ----------

I set the date ahead a couple of days after I reverted to stock recovery and used OTA RootKeeper to do a Temp unroot. Worked like magic. Thank you for the suggestion. Reminds me of back in the day, before programmers eliminated the ability to do it, we used to manipulate the dates on our computers so that we could use demo programs without them expiring. But adding the registry and other methods they have pretty much eliminated that little trick. Anyway, does anyone know if there are any new settings we can manipulate with this update or was it just an update to provide those 2 channels for LTE?

---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------

I need to hear from anyone else that has applied this update. I need to know if this is really happening. My phone is lightning fast since the update. I have never seen it this responsive since the day I bought it. There is absolutely no lag between screens and apps are starting incredibly fast. Anyone else have this happen? If not, it is probably an anomaly and will disappear soon, probably after a reboot or two.

---------- Post added at 06:15 PM ---------- Previous post was at 06:06 PM ----------

It is booting up extremely fast too. I am in kind of a state of shock right now. Every screen jumps at you. I didn't think the Express had this kind of speed. I know I sound excited, but I am. I hope this lasts. I have rebooted twice so far and still doing great. :D

---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------

Next on my wishlist is that maybe, just maybe, this fixed the problem with my phone not always ringing when receiving a call.
[Android Q&A, Help & Troubleshooting] BlindArtisan:
I'm sure if it is a pseudo effect or if it is actually faster. I have noticed though that when using the keyboard and voice to text the input is more responsive.

Even though this was only a 80mb patch it does hold some content. I haven't had time to look at the files in-depth, but I'll take try to look into what was actually changed this weekend.
[Android Q&A, Help & Troubleshooting] jt1134:
Custom kernel

Here [1] is a custom kernel for folks to play with. I got bored today and fixed up Samsung's code to automate the compile process, and made a few small tweaks. The source code is on my github [2]. This kernel has been tested with the stock 4.1.2 ROM on my device and works well. It should work on any 4.1.2 ROM (_should_ work).

The following changes have been made:

* permanent adb root and insecure boot (ro.secure=0)

* init.d script support

* KSM support

* enabled interactive and conservative CPU governors

That's it. That's all I plan on doing with it. If you are adventurous, you may download the source code and tweak it to your liking. I've included a build script with the source code, running it will install the necessary toolchain, compile the kernel, and spit out a flashable zip file in one step. It should work on any Linux distro, I've only tested on Ubuntu.

Make a nandroid backup. Flash the zip in CWM. Don't blame me if it doesn't work.

[1] http://www.mediafire.com/download/vdmja7exh7ra63c/kernel_update-0801.zip

[2] https://github.com/jt1134/android_kernel_samsung_expressatt/commits/samsung