[Q] Hyperdrive Build Prop causing issues with Play Store - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hey there,
So I just installed Hyperdrive 17.1 via Safestrap onto my AT&T Galaxy S4. Everything is going smoothly, except one key issue. The build prop is entirely Verizon based and that has somehow confused the Google Play Store into not allowing me to install the following apps I need and use:
Hello SMS
WhatsApp
AT&T Visual Voicemail
Starbucks
GoWallet
It says that these apps don't support my version of Android, which ostensibly is 4.4.2, but something in the build prop must be fooling the Play Store into thinking that it's incompatible.
So, I guess I should edit the build prop. I've looked in the Hyperdrive thread for someone who had the same problem as I did, to no avail. Then I tried to find a stock build prop for an AT&T GS4 running NC1, but to no avail. And besides, I'd rather just edit one entry if that would be easier and give me a better chance of solving the problem without bricking my phone. I believe the entry most likely to help me would be ro.build.description? What would that entry read on stock NC1?
Thanks for your help!

Try the AT&T build.prop/APN file found here:
http://forum.xda-developers.com/showpost.php?p=51112381&postcount=9
However, be aware that when I flashed that file over Hyperdrive 17.1, it interfered with Hyperdrive Tweaks (which would then force close when trying to open). I'm not sure if the dev has fixed that problem... I moved on to a different ROM because at the time there wasn't a known solution I could find to the "+ being added to incoming/outgoing calls" issue (app Prefixer seems to be the solution most commonly mentioned, now).
I encountered the same problems with downloading apps based on the phone identification that you are seeing, and I did change one build.prop item manually (I forget which one), but it wasn't enough to get the store to properly recognize the phone. I think there are a few of them that need to be changed, and I didn't invest time to figure it out.
You will probably fix it if you go through the ATT build.prop file line by line and adjust on your phone just the items that refer to phone model ID... that would probably not break Hyperdrive Tweaks.
Marc

Related

[Q] Wifi Problems [Solved]

Phone: Samsung S4 mini SGH-I257m (Canada Rogers)
Android 4.2.2 I257MVLUAMK5
I used an app called "Wifi Pass Recovery & Backup" and it killed my wifi. It tries to turn on and fails. I could redo my phone completely but I would rather fix it.
I have tried many things:
I made a backup with the app before doing anything and restoring that did nothing. Using the in app "reset wifi settings" button also did nothing but remove my saved networks.
Using ES File Explorer I have looked at the /system/bin/wps_supplicant, /data/misc/wifi/wps_supplicant.conf, /system/etc/wifi/wps_supplicant.conf. Played around with permissions, owner and checked MD5 with backed up versions. One thing I noticed was that the permissions seemed to reset when I would reboot.....
I used logcat and couldn't gain any ground there.
Some post I saw said something about replacing /system/bin/wps_supplicant with the one from the stock firmware, but i couldn't figure out how to find the files in the firmware I downloaded. I did find a factory image from google and was able to extract the files I was looking for, but they didn't work either. No surprise there.
I would love some help this as you guys are the experts!
Thanks!
Are there any other files that have to do with wifi? They might be worth checking out.
Solved
Ok....So, I was able to fix the problem by going back to the stock ROM. Not what I was wanting but whatever.
In an effort to try to figure out what happened, I cross-checked the stock files with the the ones I had before.
- the MD5 checksum of /system/bin/wpa_supplicant was identical
- /system/etc/wifi/wps_supplicant.conf was identical
- /data/misc/wifi/wps_supplicant.conf had a difference with config_methods. Stock was 'physical_display', old was 'physical_display virtual_push_button keypad'
So as far as I can tell.....that one entry was the problem.

[Q] (Help) Change Model Number Back!

Hi all,
Some time ago, I was troubleshooting one of the many ossues I have had with my phone. During the troubleshooting, one of the steps was to change the Note 3 model number to that of an S4. That would have effectively resolved the issue.
Now some time has passed, and having the phone identified as an S4 is causing other problems. I cant find the original thread though, and I cant remember which file I changed.
I remember going into Root Browser, and looking up a file. I opened the file in text editor, and changed SM900W8 to SMH I337 or something like that.
Anyone know where that file is? I need to change my model back because of compatibility issues
4DM said:
Hi all,
Some time ago, I was troubleshooting one of the many ossues I have had with my phone. During the troubleshooting, one of the steps was to change the Note 3 model number to that of an S4. That would have effectively resolved the issue.
Now some time has passed, and having the phone identified as an S4 is causing other problems. I cant find the original thread though, and I cant remember which file I changed.
I remember going into Root Browser, and looking up a file. I opened the file in text editor, and changed SM900W8 to SMH I337 or something like that.
Anyone know where that file is? I need to change my model back because of compatibility issues
Click to expand...
Click to collapse
/system/build.prop?
Yep! That's exactly what I was looking for. Thanks!

[Q] Samsung Galaxy Tab 4 8.0 AT&T SM-T337A Root but NO Recovery

Hi Devs,
I've just joined and am uncertain of the proper place for this thread. Apologies if inaccurately posted.
I have the T337A, which I have rooted on ANF4, but I cannot find a recovery. I have read and read but am not finding the solution to my little project. I would like to get a safestrap on this locked bootloader so that I can install and learn to write custom ROMs. I have tried a safestrap but it was not for this specific device and did not work. I have also installed and purchased CWM Recovery and TWRP Recovery, in my learning process. The problem with the recovery is that there is no custom recovery written for this device and the bootloader is locked, as this is the AT&T WiFi/LTE version. So it looks to me like I need to figure out the partitioning image somehow in order to make a safestrap work on this device...as step 1. Is there anything else that I can do with this locked bootloader? I would love to have some help in writing a custom recovery and ROM for this device but I am a tiny tiny noob here and not a hard core programmer. If I could get some feedback on places to start for such a daunting task, it would be great. I guess one thing that I do not understand is why I cannot make my current rooted ROM the default recovery in TWRP. It asks me to choose from the list of supported devices. I understand that it goes: NAND --> aboot.img/bootloader --> recovery/or/kernel --> OS/or/ROM? If this is close to accurate then I would have to write something to the NAND?, which I'm not sure what is yet, in order to hijack the factory bootloader and then write the partitions on the sdCard for the ROM, like the safestrap folks wrote? It looks to me like they also included a version of TWRP touch which I used on the S4 yesterday and was really cool, so I guess that would be needed as well and is also why TWRP does not work for me now...it cannot hijack the locked bootloader. How do I hijack this hard headed thing? fastboot does not work to this device. In the process of this project, I have also run into a roadblock trying to update the /system/framework/framework-res.apk, in the manner that a flash needs to be done, I think. I want to change the /res/values/bools/bools.xml switch "voice_capeable" to true. AT&T or Samsung disable this on this version of the tablet, I guess to sell tethering or something else I'm not familiar with...but the way it looks to me, everything is configured on the device and I have a phone number provisioned for data at least. Why can't I turn on this switch and use the phone portion of the device? Any time I tickle the running framework-res.apk, it kills the OS. I tried compiling an update.zip aligned and signed with test keys or something like that but when I flash it, it fails with wrong footer and invalid signature...then it wipes me back to the stone ages. I warned I was a noob..! ...but not scared to brick some shtuff in order to learn this and write some custom solutions. An after thought...is there a solution for a bootable extSdCard for Android? This might lead to some options if it is possible.
Gathering phone info...
Collecting information. Be patient! Do NOT disconnect the phone!
Model: SM-T337A
Android Version: 4.4.2
Sales Code: ATT
PDA Version: T337AUCU1ANF4
Phone Version: T337AUCU1ANF4
CSC Version: T337AATT1ANF4
Product Code: SM-T337AZWAATT
HIDSw Version: T337AUCU1ANF4/T337AATT1ANF4/T337AUCU1ANF4/T337AUCU1ANF4
Board Platform: MSM8226
Serial Number: R32FA00PMRF
Imei: 3534.............
Unique Number: C1604.......
Connections: AT,MTP,MTP
Battery Status: 4.28V (94%)
Network Type: GSM
SuperSU Pro v2.40
TWRP donate latest
CWM donate v5.5.3.7
BusyBox Stericson donate v1.23.0
Titanium Backup Pro latest
xPosed v2.7.1
Wanam xPosed v3.3.1
NinjaMorph Pro v2.8.2
ROM Toolbox Pro v6.0.6.5
RootLogger Pro v1.9
Nandroid Backup v4.4.5
Next Launcher 3D Shell v3.20
Root Firewall Pro v2.1
SetCPU v3.1.2
w/respect. PitPin
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
pre4speed said:
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
Click to expand...
Click to collapse
Thanks pre4speed. I am taking a look at the two tasks again tonight and decided to take the res/bool = voice_capable issue on first since this will determine how brickable this device can be for me. If I can use it as a regular modem phone then I might be a bit more careful with the bootloader project I did some more tinkering with the framework-res.apk ...specifically the /res/values/bools/bools.xml resource and tried the following:
-------
Factory wipe
Flashed sammobile.com T337AATT1ANF4 firmware
Rooted
SuperSU
Busybox
Froze AT&T update service and others involved
Titanium backup and pulled a good backup
Online Nandroid and pulled a good backup
Installed my XDA app. of course..!
-------
Framework-res.apk:
Used total commander to copy the running apk off to the sdCard and then my PC.
Decompilled in APKStudio2.0.3b-Windows (I am also using Ubuntu 14.04 if there is a better way here..also Android Studio on both OS...just learning).
Edited my value.
Recompiled with zip align/sign option.
***Now here in lies the problem, if I haven't already created one above ***
The random article I dug up said that in order to get past the wrong footer and signature issue, and stone-age wipe, when attempting this via abd sideload with an update.zip, is to now copy the edited file back into the original APK using 7zip in order to retain the original signing keys. When I open the original APK archive, it does not show the resource folders deemed "important and I should not jack with them" in the compiled APK (mainly values/* folder). The article mentioned the resource folders such as res/values/bools are compiled and hidden and that I needed to copy over the new resources.arsc file. I see this in the newly compiled APK I made but it also put the Manifest.xml and /res folder in there. Do I need to copy all of that or just the compiled resources.arsc file? I did all and it boot looped me so I'm guessing that I either did something wrong or this was not the right answer. The last part was to chmod the new APK, use total commander to mount the folder as rw, copy over the file, and reboot. All of that worked and I had to reboot many many times...loop.
That is where I am on the modem part and am going to attempt copying just the resources.arsc in a few. I will post more on the bootloader side soon, as I've been researching what goes on from the time I push the power button until the time I swipe the first screen. Lots of reading
w/respect - PitPin
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
PitPin said:
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
Click to expand...
Click to collapse
Stalled out temporarily on the tab project as laptop hard drive bought the farm. Back in action and made some progress on the tab voice_capable issue. Everything appears to be there and in working order but the SMS modules. I think this has something to do with why the contacts app is blowing up but not sure yet. GoSMS and EXDialer seem to work together without blowing up but the dialer taps the modem and then dies. Taking a break from this to start a thread on rooting the AT&T Alpha. I'm about half way through the exploit on that project. Any input on what might be my SMS problem on the tab 4 would be appreciated. Attached are a few screens.
Does anyone know how to removed the caution sign on the left corner it keep telling me unauthorized action have been detected.
I am in the same boat, I so wish this would come through because I do love this little tab.
same boat
/baker said:
I am in the same boat, I so wish this would come through because I do love this little tab.
Click to expand...
Click to collapse
so did you finally get it going or what?I have been wanting to get my Tab going as well. I've Rooted it and paid for an unlock even, which worked fantastic by the way...Thanx XDA!!! The rooting guide I got from here was right on point,no problem at all!!But anyways, I have it on metro pcs now on the unlimited $60 plan which is awesome (.REAL unlimited internet with NO THROTTLING ) for me because now at home I run pda.net, which gives me very good, fulltime, internet for my home computers as well as the ability to stream everything onto a large screen or even via windows when we want to watch with all the bells and whistles! No lag at all usually,and I don't use my hotspot because of the usb internet connect on pda.net. When I do use the wireless connect, it doesn't take any of the allotted hotspot usage up either!!All in all it's a great deal for me. I just got a new sim for it, called in the imei to metro ,which in turn gave me a phone number and data account, and presto!Been on the net ever since! Now that I've had it for over a month ,I wanna get the voice capability to work as well, being that I am paying for 2 lines now. Although I can use the old trusty hangouts dialer with the GoogleVoice easily enough. I want to be able to use my metro number mainly because these phone companies charge and charge and charge, never caring about us,or our need to have communication at our disposal at all times.Cell phones are by far not inexpensive and the internet wasn't started for us to pay aan arm and a leg to use.Anytime I come out good while dealing with a wireless company. it's a stupendous event,I'm telling you!! Heck ,I'm writing from my home computer now, going through the Tab at this very moment! Nevertheless, I'm wanting for the devs, to come through as well. With maybe even a new rom,sans the at&t stuff, of course, since I do now have a different carrier? Heck, the Tab is even great for when we travel! 24/7 unlimited internet /streaming , and the screen size is much better than the phone screen ever was!I just really wanted to thank XDA for the work they put in to help us part - timers out,Ive been rooting and unlocking and bricking and un-bricking for quite some time now,I even repair phones now actually,but the programming and the putting it all out here for guys like me to have fun and tinker with these phones would be entirely impossible without the DEV'S and their hard work for SURE...Thanx Guys!!You ROCK!

G900i & nfc?

Hey there, I'm Australian.
My G900I is from Telstra. Right now, I have cm12 installed.
The problem I have is that when I flash roms, NFC is jammed on and doesn't work which causes massive battery drain.
The only way I've found to solve this is to flash KToonsez Kernel which has some kind of "NFC fix" as I've seen it called.
Is there any way to get the NFC fix standalone? Is there some way to make NFC work in the first place?
More details upon request, thank you XDA <3
if already searched, should have mentioned this in your thread:
http://forum.xda-developers.com/galaxy-s5/help/nfc-fix-900i-varients-running-900f-base-t3008439
This is the one I'm now using... which is from Neatrom for 900f...
this seems to work at first... but then I can get the actual NFC tag to read. It reads... but then makes a https://mega.co.nz/#!3EVjDJaA!Qr__QPWD-Ay9aXGr0sSbjgW_sp3gBi8abcEf5Sh1x90 fail sound
I noticed that after replacing files manually it was actually the libs that made the difference to stop the "NFC service has stopped" message.
These are the related files:
Code:
\system\app\NfcNci
\system\app\NfcNci\NfcNci.apk
\etc\libnfc-brcm-20791b04.conf
\system\etc\libnfc-brcm-20791b05.conf
\system\etc\libnfc-brcm.conf
\system\lib\hw
\system\lib\libnfc-nci.so
\system\lib\libnfc_nci_jni.so
\system\lib\hw\nfc_nci.bcm2079x.MSM8974.so
as I say... I went through manually changing these one by one and the apk and odex made no difference, etc files also, just the libs. I didn't get to try changing the file in hw. I'd like to know what that file directory is - is this the kernel driver right?

Re: new "developer's edition" N910V ROM compatability

Re: new "developer's edition" N910V ROM compatability
From the few ROMs I've tried to flash so far, I've gotten a lot of error 7s in TWRP
As far as I can tell from some googling, this means that the updater-script in the ROM isn't allowing it to be installed on the device because it's not one of the ones in it's approved list based on some prop file somewhere
I think the fix to this is to edit the updater-script file by making it a .txt doc, deleting some amount of lines after the "assert," and changing it back to a file before putting it back into the ROM... so I'm trying to learn enough about coding to find out where exactly I should stop the deletion at. Or, alternatively, what I'd have to add.
It's also possible that I'm totally wrong and I'm getting this error for another reason entirely.
If anyone knows what they're doing here, I'd definitely be open to suggestions. If this is what the problem is, I imagine it won't be hard for devs to edit though.

Categories

Resources