Hey guys, I just got GW working for my unlocked and rooted SGS3 i9300 by combining the how-to from GW for US variants (HERE) and MoDaCo latest patched GW (HERE). So here are the steps (obviously your phone has to be rooted and is using TW; not sure about other roms; I'm using the latest JB leak LI8):
1. Nandroid backup
2. Using Root Explorer (ES will not work as reported from other source), modify the /system/build.prop:
LOOK FOR THESE LINES:
Code:
ro.build.model=GT-I9300
ro.product.name=m0xx
ro.product.device=m0
TO
Code:
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Then save it. RE will automatically backup the old one as build.prop.bak.
3. Download the latest GW from HERE to sd card
4. Move the GW.apk to system/app
5. Restart the phone
6. Start GW, sign in, add your cards, etc
7. Back to RE, delete the new build.prop, and then change the old build.prop.bak to build.prop, so S-voice can work properly (or else you'll get network error)
8. Restart the phone again
9. Enjoy your GW at 711 or elsewhere (I had it work at 711)
10. Another nandroid backup would be useful
11. Don't restore this GW by Titanium Backup whenever installing a new TW-based rom. Instead, reset (in-app setting) and delete GW from the phone. Flash a TW rom, then follow the steps again.
PS: I assume most of you know how to work with RE and nandroid; you can search xda for instructions.
Disclaimer: I'm not sure if this method works with other JB leaks, ICS, or other custom roms (don't mention CM, since it's another whole world )
Credit: ogdobber (GW for US variants), PaulOBrien (Patched GW)
No replies? Wow.
Thanks for posting this. I'm running the latest Wanamlite ROM, which is based on Touchwiz JB. I know that one of the modifications is a "modified build.prop" file for increased market compatibility. Do you think that it not being 100% stock ROM will prevent me from trying this?
Maybe because there's similar thread in themes and apps section.
And I think its even older than oggdober thread and op has been the first to figure out HTC_jewel thingy.
Sure it dealt with UK customers in the title, but the rest is identical. Then they blacklisted us (the test of the world) and we stopped caring.
All said it does not mean in its current form it is not usefull for us customers (only).
Testing JKay alpha on GT-I9300
got this set up yesterday but haven't had a chance to test it out yet at a store.
I have done the procedure similar to this with my S2 so I figured this shouldnt be that hard. Well I follow the Instructions and it gets all set up however when i got o add my debit card it says "Request Failed, Please try again" and no mat7ter how many times i try to do it it still wont go through. Any ideas as to why?
Hi!
Just a few hours after upgrading to 4.4.2 (OTA official) I started to notice some "flaws" in the new OS. Of course there are lot´s of new good things too, but wouldn´t be better if we could eliminate some of the flaws too?
That´s why I´m creating this thread - with the purpose of exchanging experiences regarding the issues and solutions found in order to improve 4.4.2 usability.
I´m starting by sharing my experience with one of the most annoying drawbacks (at least in my opinion): the way external SD card is being used. 4.4.2 simply doesn´t allow data exchange between user installed programs (and data) and external SD card. I´m an user of FX File Manager (in my opinion one of the best file managers I ever seen).
When I opened for the first time in the new OS, the following message appeared: "Your SD Card may now be read only. This device is running Android 4.4 or later and appears to have both an internal storage area and external storage. Google imposed new restrictions in the Android 4.4 KitKat Update: applications that you install yourself ar no longer allowed to write to the "secondary external" storage (the MicroSD card). Applications installed by Google, the device manufacturer, and/or your mobile carrier ar exempt from this restriction. Only applications you choose to install are restricted. Some devices may not enforce this restriction, and other may have a means of disabling it. If you find yourself unable to write to your external SD card, please contact either your mobile carrier or device´s manufacturer support.This problem can be worked around if you have superuser access. Please refer to websites/forums related to your specific device for information."
Awkward!!!
I tried to move some files from my internal download to external SD card and no transfer was possible...
After searching for some workaround, the only way I could manage this situation was by installing ES File Explorer, which found a way to overcome this limitation for file transfer. Of course it solves the issue very partially, since no other programs (including photo / film software) will be able to overcome this problem.
I invite everyone who have/had an issue with 4.4.2 to use this as a way to exchange information, creating a single thread that will make easier to find issues and solutions (if available).
Fixing in general section. It was bug in leaked version but never thought they didn't fix it in OTA version? Flash 3rd kernel would pretty much solve problem I guess. But either way needs root access which means probably avoid warranty due to KNOX
来自我的 GT-I9505 上的 Tapatalk
1. Worse battery management than JB
2. More lagging in games and UI
Generally much ado about nothing imho
I am not installed yet the 4.4.2 update in my GT-I9505 because my carrier sure be the last one to adjust the base to post the update. (Venezuela - DIGITEL).
Regarding some of your issues, particulary the access to the SD Card, I recently read in one post on Questions section with two alternatives to activate the access to the card.
Check it and let us now if reallly working before the rest of the members take the adventure to install the 4.4.2 Kit Kat version.
Good look
what's up igruberger
I use X-plore on my S4, I can transfer files but I cant read newly transferred Mp3's from my external sd since kitcat 4.4 why has this stupid restriction being put in place!!!!! royally pissed off!!!!! and are you aware of any work around yet?? its not the phones manufacturer that can fix the problem, its the android software developers as its a software issue not hardware.
Problem whit my LTE
after the update i could not receive 3G or H or H+ or LTE only Edge someone know how to fix this i'm living in Belgium my carrier is Proximus
build I9505XXUGNF1
Baseband-version I9505XXUFNBA
Thx in advantage
Hey guys. I bought this 64gig micro sd card and I couldnt manage to make it work on my Note 3 (It works on my S3 mini) I started to worry if this is a software issue. I can't write anything but it reads whatever in it. Can you please help me? Thanks!
It's a new "feature" in KitKat, which renders sd cards useless. If you are rooted you can try the xposed module "HandleExternalStorage".
GalaxyInABox said:
It's a new "feature" in KitKat, which renders sd cards useless. If you are rooted you can try the xposed module "HandleExternalStorage".
Click to expand...
Click to collapse
or you can modify your platform.xml file and add read write permissions for media.
http://forum.xda-developers.com/showthread.php?t=1458021
Note: The system can still use the external SD card so you can still move an app to the SD card I believe.
What ROM are you using?
Ah, I forgot something really important. If you have root access, download something like Terminal Emulator and execute:
"su" to get root access and after that:
"restorecon -v -R /data/media"
This often fixes the problem!
Thanks a lot for your help but the issue is I'm still on stock. I couldn't figure out how to root and not void warranty I saw something like triangle away but if that's going to work about warranty bit how am I going to unroot without seeing the warranty bit 1?
Most big apps have been updated to work with the bew permissions. ES file explorer, Quickpic..
No need to root for that.
Sent from my SM-N9005 using Tapatalk 2
Having this problem with mp3dit. I emailed the programmer and he said that there is nothing that can be done. Somehow I didn't believe that so I'm here searching for a way around it.
Hello,
I just got a new S 5 with build: KOT49H.G900FXXU1ANE2
Background:
- Rooted via Towelroot: o.k.
- Installed SuperSU: o.k
- Installed BusyBox Pro: o.k.
- Restore Titanium backup files (NO system data) with Pro version: worked fine
- installed SD card fix with this guide with total commander file editor:
-- Use a root-enabled file manager and navigate to /system/etc/permissions
-- Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
-- Add an additional group definition for this permission: <group gid=”media_rw” />
-- Save the changes and restart your device
-- You are now able to write on your external SD card again
After restarting device, many system apps were crashing over and over like:
samsung data cloud relay, samsung account, google account, ....
Steps did so far:
- Connecting via USB cable: No access to internal / external SD card > File explorer shows only internal and external SD card with no files
- Tried to copy/move/backup files from internal to external SD card: failed, files like photos, downloads are gone
- Factory reset: done, still app crashes
- Firmware flashed: done, initial configuration not possible due to app crashes, hangs in the form where to fill in my name
Any solutions, hints, to fix this ?
I would be very gratefull for constructive solutions.
Thanks in advance !
verona said:
Hello,
I just got a new S 5 with build: KOT49H.G900FXXU1ANE2
Background:
- Rooted via Towelroot: o.k.
- Installed SuperSU: o.k
- Installed BusyBox Pro: o.k.
- Restore Titanium backup files (NO system data) with Pro version: worked fine
- installed SD card fix with this guide with total commander file editor:
-- Use a root-enabled file manager and navigate to /system/etc/permissions
-- Edit platform.xml and find “WRITE_EXTERNAL_STORAGE“
-- Add an additional group definition for this permission: <group gid=”media_rw” />
-- Save the changes and restart your device
-- You are now able to write on your external SD card again
After restarting device, many system apps were crashing over and over like:
samsung data cloud relay, samsung account, google account, ....
Steps did so far:
- Connecting via USB cable: No access to internal / external SD card > File explorer shows only internal and external SD card with no files
- Tried to copy/move/backup files from internal to external SD card: failed, files like photos, downloads are gone
- Factory reset: done, still app crashes
- Firmware flashed: done, initial configuration not possible due to app crashes, hangs in the form where to fill in my name
Any solutions, hints, to fix this ?
I would be very gratefull for constructive solutions.
Thanks in advance !
Click to expand...
Click to collapse
Hmm... I've never seen a problem like this in my experience. The only thing I would suggest is going into your recovery and fixing permissions. Beyond that, I wouldn't know how to fix this without recommending you flash a new ROM after fixing permissions. If that still doesn't work, it may very well be a bad SD card or a bad SD card reader. For your sake, I hope it isn't either of these problems, as it would take longer to fix. Good luck!
BJSerpas said:
Hmm... I've never seen a problem like this in my experience. The only thing I would suggest is going into your recovery and fixing permissions. Beyond that, I wouldn't know how to fix this without recommending you flash a new ROM after fixing permissions. If that still doesn't work, it may very well be a bad SD card or a bad SD card reader. For your sake, I hope it isn't either of these problems, as it would take longer to fix. Good luck!
Click to expand...
Click to collapse
Bevor doing a firmware flash, I restored the originally settings for SD card permissions without solution.
If you think this is a persmission issue, how to fix this ?
Any further solutions, hints, tips ?
Greetings
verona said:
Bevor doing a firmware flash, I restored the originally settings for SD card permissions without solution.
If you think this is a persmission issue, how to fix this ?
Any further solutions, hints, tips ?
Greetings
Click to expand...
Click to collapse
Maybe anyone has a solution for how to fix permission as posted above ?
Thanks in advance.
EXACT same problem here
Hello Verona, I have EXACT the same problem here. Same hardware, same configuration, same setup, same symptomatic.And also the same: no solution in sight! :crying:
It sounds like a permissions issue. That could be time consuming to track down and fix. I'd suggest restoring your backup to restore your phone to a stable baseline. Then do the SD card write mod following the instructions in one of the proven threads that have a lot of feedback indicating that the method is sound.
Alternately if you don't care about the Knox flag, you could install a custom recovery like TWRP. TWRP has a option to fix permissions for key files with one click. Which may resolve your issues. I rather prefer the former option myself.
Good luck.
.
permission problem
fffft said:
It sounds like a permissions issue. That could be time consuming to track down and fix. I'd suggest restoring your backup to restore your phone to a stable baseline. Then do the SD card write mod following the instructions in one of the proven threads that have a lot of feedback indicating that the method is sound.
Alternately if you don't care about the Knox flag, you could install a custom recovery like TWRP. TWRP has a option to fix permissions for key files with one click. Which may resolve your issues. I rather prefer the former option myself.
Good luck.
.
Click to expand...
Click to collapse
Hello fffft,
Verona already installed a new firmware! Where is here the place for remaining permission problems? I always though that then everyting is written new to the system. I have no nandroid backup because I rooted only with towelroot and it could not be written to the external SDcard....where we are again at the beginning of the story.
Now I can take the decision to bring the S5 without knox flag to the service as it is or to take the risk, that the permission reset with a recovery doen't fix the problem WITH Knox flag.I see no clear way here to make it right
brachypelma said:
Where is here the place for remaining permission problems? I always though that then everyting is written new to the system. I have no nandroid backup because I rooted only with towelroot and it could not be written to the external SDcard....where we are again at the beginning of the story.
Now I can take the decision to bring the S5 without knox flag to the service as it is or to take the risk, that the permission reset with a recovery doen't fix the problem WITH Knox flag.I see no clear way here to make it right
Click to expand...
Click to collapse
It's not clear what you are describing or asking.
It would help if you elaborated in more detail. If I understand you, you are not willing to use TWRP because you don't want to increment the Knox counter. And want an alternative to TWRP to repair your messed up permissions.
I don't recommend that. Permissions are a key characteristic of an OS. If you mess them up in any non-obvious way, your OS is unlikely to ever be 100% stable again. Notwithstanding TWRP's great job in scripting a recursive fix script, I wouldn't want to trust an OS that had to be fixed that way. If you insist, try searching for an app that fixes OS permissions. Or alternately you could extract the script from TWRP and run it from a root command line.
If your OS permissions are a mess, the better solution is reinstalling your OS (firmware). So I'd recommend that you reinstall a full stock firmware image and wipe the data partition to get back to a stable system. Then do a backup before putting your phone at risk again. If not a Nandroid, then the next best thing e.g. Titanium. Then if you wish, do the SD permissions "fix" again, but follow the instructions from a thread that has abundant positive feedback. Meaning that you should succeed this time. And if not for any reason, then you can fall back on your backup.
.
Restored the original platforms.xml file, installed TWRP via Odin (no internet access on S5) and resetted the permissions. No effect at all.
What's now the next step? Wiping what can be wiped and re-flashing the T-Mobile firmware?
brachypelma said:
Restored the original platforms.xml file, installed TWRP via Odin (no internet access on S5) and resetted the permissions. No effect at all.
What's now the next step? Wiping what can be wiped and re-flashing the T-Mobile firmware?
Click to expand...
Click to collapse
Sorry to hear that your phone is still giving you problems. But you haven't taken my advice yet. I did not recommend the TWRP "fix". Merely mentioned that it was a possibility. I further added that it could not be expected to work in all cases.
It wasn't a complete loss though. TWRP is an outstanding backup method and invaluable for miscellaneous maintenance tasks.
As to resolving the permissions issues, I recommended Odin flashing a full stock firmware + wiping the data partition. That will revert you to 99%+ stock and give you a stable base to proceed from. It will also wipe your user files, so backup anything of value that isn't already backed up first.
.
back to life....
fffft said:
Sorry to hear that your phone is still giving you problems. But you haven't taken my advice yet. I did not recommend the TWRP "fix". Merely mentioned that it was a possibility. I further added that it could not be expected to work in all cases.
It wasn't a complete loss though. TWRP is an outstanding backup method and invaluable for miscellaneous maintenance tasks.
As to resolving the permissions issues, I recommended Odin flashing a full stock firmware + wiping the data partition. That will revert you to 99%+ stock and give you a stable base to proceed from. It will also wipe your user files, so backup anything of value that isn't already backed up first.
.
Click to expand...
Click to collapse
fffft, I'm back to a normal behaviour of my S5 now. Thx! Flashing stock rom !+! factory reset brougt it back. TWRP was also gone afterwards, but now with an already set knox counter I'm in a "stressless" situation because this decision is done now forever. Of course I lost 4 weeks of mobile configuration and I would like to investigate a little bit more on the original problem, because my SDcard is still write protected.
When I edited the platform.xml I forgot to the set the permissions to 664 before I rebooted. It was on 755 (don't remember exactly don't know the default umask by heart). A correction in a second loop didn't already help. Could this caused the problem?
You wrote, that I should try the modification with the platform.xml again and take instructions from a reliable source. We have indeed different information in the net.
Variant 1:
add media_rw to WRITE_EXTERNAL_STORAGE
Variant 2:
add media_rw to WRITE_EXTERNAL_STORAGE
add sdcard_rw to WRITE_MEDIA_STORAGE
Variant 3:
add media_rw to WRITE_READ_STORAGE
add media_rw to WRITE_EXTERNAL_STORAGE
add sdcard_rw to WRITE_MEDIA_STORAGE
Which mechanism created deviated problems? Otherwise the system should be ok after restornig the original file.
I could also imagine that the file coding has changed. The files was saved in UNIX mode (LF only), because I modified it with vi in a local root shell. Or that the indenting was done with TAB instead of blanks or someting like that.
Any ideas?
Is there any explanation what happend there and how this can be prevented with the next try?
brachypelma said:
Is there any explanation what happend there and how this can be prevented with the next try?
Click to expand...
Click to collapse
Good to hear that your system is stable again.
Make sure that you make a backup while it's still stable. What happened to you is that you made changes that had unexpected results. That's not a problem per se.. it can happen to anyone. The irredeemable problem is if you have no backup to revert to. Which caused you grief trying to sort it out and get back to a stable base.
The actual problem from your app's perspective was probably that they still didn't have as much SD access as they expected and they didn't cope well with that..
So, first thing - make sure that you make a backup. Opinions vary on how much access to give to the SD card. I'll give you a fairly liberal example that will probably work for you. If not, you can extend or restrict access to suit your situation. Just make sure you have a backup to restore if things go sideways.
The file being edited is /system/etc/permissions/platform.xml
Code:
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
.
.
To get another result, I decided to send my S5 back for warranty to the distributor.
The feedback will be posted in this thread.
The basic question is, what is the best way for backing up the specific model with its ROM to be on the safe way.
The only difference between branchypalma and me was, that I flashed the firmware and did a factory reset, but every app was crashing straight away.
Maybe branchypalma used another ROM (what exact version?) or something internal broke down.
Before having issues, I used titanium backup for backing up files after setting up the mobile, but it was inaccessible in every tried way.
Maybe someone has another idea for the case, the warranty is being denied. Maybe I used a wrong stock Rom.
What would you suggest (Rom, in this situation) ?
verona said:
To get another result, I decided to send my S5 back for warranty to the distributor.
The feedback will be posted in this thread.
The basic question is, what is the best way for backing up the specific model with its ROM to be on the safe way.
The only difference between branchypalma and me was, that I flashed the firmware and did a factory reset, but every app was crashing straight away.
Maybe branchypalma used another ROM (what exact version?) or something internal broke down.
Before having issues, I used titanium backup for backing up files after setting up the mobile, but it was inaccessible in every tried way.
Maybe someone has another idea for the case, the warranty is being denied. Maybe I used a wrong stock Rom.
What would you suggest (Rom, in this situation) ?
Click to expand...
Click to collapse
Feedback as promised: The device has been successfully repaired & returned.
Everything solved for me
verona said:
Feedback as promised: The device has been successfully repaired & returned.
Click to expand...
Click to collapse
Hello verona,
I downloaded the firmware from sammobile.com/firmwares and select my T-Mobile brand and flashed it with odin. After that I did a factory reset which solved my problem. Afterwards I installed towelroot again and with root access I reflashed the TWRP recovery again because the stock firmware brought the old one back.
To solve the original SD card problem I downloaded the SD KitKat Fixer from JRummy Apps Inc. which creates a perfect written platform.xml compared to the tool from NextApp with wrong alignment.
With TWRP I'm now able to make my desired nandroid backup as well as TitaniumBackup on my SD card. I'm with all Samsung devices already with knox flag on so I do not care at all about it meanwhile.
Now I'm there were I want to be and everything is fine. Hope you get it also working for you!
brachypelma
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