I don't know about the other variants, but on the T-Mobile flavor of the LG G2 the default TTS is LG's. It sounds better than Pico, for sure, but it's still too robotic and mispronounces a few things. I couldn't put up with that. I set off to figure out how to get GoogleTTS back. It took a lot of google-fu, but in the end I had achieved my goal, to have that sweet voice talking to me again.
Before you begin, know that you'll need root access to continue.
Step 1: Download the latest GAPPS for your device (as of writing this, it's gapps-jb-20130812-signed.zip): http://goo.im/gapps
NOTE: gapps-jb-20130813-signed.zip IS FOR ANDROID 4.3! WATCH WHAT YOU DOWNLOAD!
Step 2: Unzip the zip to your computer or your phone's sdcard. Alternatively, if you have an application like Solid Explorer installed on your phone, you can simply browse the zip for the files I mention below without unzipping the whole thing.
Step 3: Mount /system as read/write
Step 4: Copy system/lib/libpatts_engine_jni_api.so and system/lib/libspeexwrapper.so to /system/lib/ and copy system/app/GoogleTTS.apk to /system/app/
Step 5: Fix the permissions of the above files to 644 and change the ownership to root:root
Step 6: Mount /system as read only
Step 7: Reboot
Step 8: Set Google TTS as your new TTS engine (under Language & input -> Text-to-speech output)
Step 9: ???
Step 10: Profit
TL;DR:
Download GAPPS
Unzip GAPPS to /sdcard/gapps/
Run the following commands:
Code:
# mount -o remount,rw /system
# cp /sdcard/gapps/system/lib/libpatts_engine_jni_api.so /system/lib/
# cp /sdcard/gapps/system/lib/libspeexwrapper.so /system/lib/
# cp /sdcard/gapps/system/app/GoogleTTS.apk /system/app/
# chmod 644 /system/lib/libpatts_engine_jni_api.so /system/lib/libspeexwrapper.so /system/app/GoogleTTS.apk
# chown root:root /system/lib/libpatts_engine_jni_api.so /system/lib/libspeexwrapper.so /system/app/GoogleTTS.apk
# mount -o remount,ro /system
Reboot
Set Google TTS as your TTS engine
EDIT:
If you simply want Google Maps to say street names there's no need to install GoogleTTS (even though it sounds loads better). Simply do the following:
Clear Google Maps data (Settings -> Apps -> Google Maps)
Uninstall Google Maps updates (In Google Play, go to Google Maps)
Update Google Maps
Excellent write up.
Fortunately for us Verizon had chosen to mange dine actually useful mods to this phone, for a change. We have the the Google tts.
Crashspeeder said:
I don't know about the other variants, but on the T-Mobile flavor of the LG G2 the default TTS is LG's. It sounds better than Pico, for sure, but it's still too robotic and mispronounces a few things. I couldn't put up with that. I set off to figure out how to get GoogleTTS back. It took a lot of google-fu, but in the end I had achieved my goal, to have that sweet voice talking to me again.
Before you begin, know that you'll need root access to continue.
Step 1: Download the latest GAPPS for your device (as of writing this, it's gapps-jb-20130812-signed.zip): http://goo.im/gapps
NOTE: gapps-jb-20130813-signed.zip IS FOR ANDROID 4.3! WATCH WHAT YOU DOWNLOAD!
Step 2: Unzip the zip to your computer or your phone's sdcard. Alternatively, if you have an application like Solid Explorer installed on your phone, you can simply browse the zip for the files I mention below without unzipping the whole thing.
Step 3: Mount /system as read/write
Step 4: Copy system/lib/libpatts_engine_jni_api.so and system/lib/libspeexwrapper.so to /system/lib/ and copy system/app/GoogleTTS.apk to /system/app/
Step 5: Fix the permissions of the above files to 644 and change the ownership to root:root
Step 6: Mount /system as read only
Step 7: Reboot
Step 8: Set Google TTS as your new TTS engine (under Language & input -> Text-to-speech output)
Step 9: ???
Step 10: Profit
TL;DR:
Download GAPPS
Unzip GAPPS to /sdcard/gapps/
Run the following commands:
Code:
# mount -o remount,rw /system
# cp /sdcard/gapps/system/lib/libpatts_engine_jni_api.so /system/lib/
# cp /sdcard/gapps/system/lib/libspeexwrapper.so /system/lib/
# cp /sdcard/gapps/system/app/GoogleTTS.apk /system/app/
# chmod 644 /system/lib/libpatts_engine_jni_api.so /system/lib/libspeexwrapper.so /system/app/GoogleTTS.apk
# chown root:root /system/lib/libpatts_engine_jni_api.so /system/lib/libspeexwrapper.so /system/app/GoogleTTS.apk
# mount -o remount,ro /system
Reboot
Set Google TTS as your TTS engine
Click to expand...
Click to collapse
I made a flashable Zip for TWRP...
https://docs.google.com/file/d/0BxsDZT2VS-_2dVRPOXNWb00xYXc/edit?usp=docslist_api
Sent from my LG-D800 using xda app-developers app
sublimejosh2000 said:
I made a flashable Zip for TWRP...
https://docs.google.com/file/d/0BxsDZT2VS-_2dVRPOXNWb00xYXc/edit?usp=docslist_api
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Excellent! Thanks for taking the time.
EDIT: Are you sure the zip will flash? I'm looking at the updater script and it looks like it requires busybox. Also, it deletes files as if it were flashing a full GAPPS package, which this isn't so that may not be best. Finally, it attempts to extract a non-existent file (install-optional.sh, which is normally included with GAPPS, but not this zip). Don't get me wrong, thanks for creating this, but I'm not sure it'll work.
sublimejosh2000 said:
I made a flashable Zip for TWRP...
https://docs.google.com/file/d/0BxsDZT2VS-_2dVRPOXNWb00xYXc/edit?usp=docslist_api
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I don't see the zip...
canecbr600 said:
I don't see the zip...
Click to expand...
Click to collapse
That is the zip. Apparently Google drive is allowing you to view the contents. Just hit File->Download or press CTRL+S (CMD+S if on a mac) to download it. It looks like this zip includes the PICO TTS files, which you don't need, though.
Thanks for posting this. I kind of liked the LG TTS sample voice, but as I mentioned in my thread a few days ago, it wouldn't do street names. That said, I'm not looking to root just yet, but this will be one of the first things I do when I feel like rooting. Thanks.
WheresTrent said:
Thanks for posting this. I kind of liked the LG TTS sample voice, but as I mentioned in my thread a few days ago, it wouldn't do street names. That said, I'm not looking to root just yet, but this will be one of the first things I do when I feel like rooting. Thanks.
Click to expand...
Click to collapse
I had the same issue with street names, but it's not LG TTS, it's Google Maps. I cleared all data for Google Maps, uninstalled all updates for Google Maps, then updated it again. It then started working (I've had this happen before on other phones as well). The thing that kills me about LG's TTS is it can't pronounce "street", it says "suh-treet". That gets REALLY annoying when you're naving.
As for rooting, it's actually dead easy. It takes longer to download the zip file with everything you need than it does to actually root, and since you don't have to unlock the bootloader or anything there's no hint that you've done anything to your phone and everything is reversible by simply flashing the stock ROM back on (or even just a factory reset).
Crashspeeder said:
I had the same issue with street names, but it's not LG TTS, it's Google Maps. I cleared all data for Google Maps, uninstalled all updates for Google Maps, then updated it again. It then started working (I've had this happen before on other phones as well). The thing that kills me about LG's TTS is it can't pronounce "street", it says "suh-treet". That gets REALLY annoying when you're naving.
As for rooting, it's actually dead easy. It takes longer to download the zip file with everything you need than it does to actually root, and since you don't have to unlock the bootloader or anything there's no hint that you've done anything to your phone and everything is reversible by simply flashing the stock ROM back on (or even just a factory reset).
Click to expand...
Click to collapse
Oh yeah, I've rooted before. I had to in order to get my E4GT to last my two-year contract (minus two weeks). I'm still in my 14-day period with T-Mobile, and I'm testing both the phone and the network. So far, both are very good. After that, I'll consider it. This and a few other tips I've picked up in the forums seem like things I'd like to add to the phone. And certainly if we're not slated to get KitKat for an extended period, as the E4GT took forever to get ICS.
Good to hear that it is working for you again.
works good on tmo thank you
Crashspeeder said:
Excellent! Thanks for taking the time.
EDIT: Are you sure the zip will flash? I'm looking at the updater script and it looks like it requires busybox. Also, it deletes files as if it were flashing a full GAPPS package, which this isn't so that may not be best. Finally, it attempts to extract a non-existent file (install-optional.sh, which is normally included with GAPPS, but not this zip). Don't get me wrong, thanks for creating this, but I'm not sure it'll work.
Click to expand...
Click to collapse
It uses the Gapps script. It works fine. I flashed before I posted.
Up on google play now. Just installed it.
https://play.google.com/store/apps/details?id=com.google.android.tts
Sent from my SM-N900T using Tapatalk
I see problem with google tts from months. I use it in my automagic scipts as voice interface. Very often saying something finishing an unknown error in tts module. It is not connected to custom ROM, I see it in los, havoc and arrow, in los 18.1 and 16. It is even in miui.
Does any other see similar problems?
Related
I tried and failed with Seesmic so far.
[INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Update:
Twitter and Tweetdeck also fail to install (didn't verify the error).
Update2:
Seems like others had noticed this before:
http://forum.samdroid.net/f38/cant-install-seesmic-after-kitchen-v2-1949/#post45656
I do have GMaps installed, though ...
Update3:
Figured out the problem.
Need to push the missing files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
Then reboot and it should be fixed (Twitter, Seesmic, Tweetdeck now install).
Update4:
It seems that this fix may apply to any app that used Google location services. (More useful than I thought )
Also see here (post 10) for the Quick Howto:
http://forum.xda-developers.com/showpost.php?p=9657322&postcount=10
Update5:
Don't forget to remount the /system parition (else, you will get messages about read-only issues).
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
twidroyd is perfect. its probably the single best running app on my NC, all things considered.
cabbieBot said:
twidroyd is perfect. its probably the single best running app on my NC, all things considered.
Click to expand...
Click to collapse
I installed the official Twitter (v1.0.5) client right from the applanet market. Works perfectly
Touiteur is my favorite app and it works just fine on the NC.
Sent from my Nook Color
cabbieBot said:
twidroyd is perfect. its probably the single best running app on my NC, all things considered.
Click to expand...
Click to collapse
Agreed, Twidroyd is awesome! I'll stick with it.
feisty_noodle said:
Update3:
Figured out the problem.
Need to push the missing files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
Then reboot and it should be fixed (Twitter, Seesmic, Tweetdeck now install).
Click to expand...
Click to collapse
I assume you got these files from a GApps archive somewhere. Could you point out which one? Would love to have Tweetdeck on my NC.
kerobaros said:
I assume you got these files from a GApps archive somewhere. Could you point out which one? Would love to have Tweetdeck on my NC.
Click to expand...
Click to collapse
I was able to pull them from my Android phone. I'm not sure the legality of posting those here (proprietary software maybe?)
kerobaros said:
I assume you got these files from a GApps archive somewhere. Could you point out which one? Would love to have Tweetdeck on my NC.
Click to expand...
Click to collapse
You can extract the necessary files from any of a number of GApps floating around (like this one):
http://goo-inside.me/google-apps/gapps-mdpi-20101020-signed.zip
That fix actually enables a whole slew of other apps -- basically all the things which wouldnt work because they lacked location services (i.e. all the good stuff). You should seriously post that in another post as a generic non-installing app fix.
I just got Parallel Kingdoms running, so my NC experience is complete.
quick how-to
remount rw so we can modify /system
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
copy over the two files from the zip:
Code:
adb push com.google.android.maps.xml /system/etc/permissions/com.google.android.maps.xml
adb push com.google.android.maps.jar /system/framework/com.google.android.maps.jar
reboot the device
Code:
adb shell
reboot
This should be working, I've done very limited tests to confirm that it's accurate
feisty_noodle said:
I tried and failed with Seesmic so far.
[INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Update:
Twitter and Tweetdeck also fail to install (didn't verify the error).
Update2:
Seems like others had noticed this before:
http://forum.samdroid.net/f38/cant-install-seesmic-after-kitchen-v2-1949/#post45656
I do have GMaps installed, though ...
Update3:
Figured out the problem.
Need to push the missing files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
Then reboot and it should be fixed (Twitter, Seesmic, Tweetdeck now install).
Click to expand...
Click to collapse
How do you push the files?
feisty_noodle said:
Update3:
Figured out the problem.
Need to push the missing files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
Then reboot and it should be fixed (Twitter, Seesmic, Tweetdeck now install).
Click to expand...
Click to collapse
Thanks for this. I have the two missing files, but can't figure out how to frame the push command. Can someone help please.
So weather apps and twitter apps are the main beneficiaries of this hack? Anything other noteworthy apps that come to mind?
Thanks for the step by step guide !!
This tutorial worked perfectly. Pushed the two files, rebooted, and Tweetdeck installed. Works like a charm. Thanks, folks!
Also, what gapps bundle did you get those out of, the one linked earlier in the thread? Going to try to push some more files out of it, try to get Gmail and Google Reader working.
I must be missing something. I just tried this and it responded with:
failed to copy <file> to <location> : Read-only file system
Do I need to do the superuser stuff first?
mad5427 said:
I must be missing something. I just tried this and it responded with:
failed to copy <file> to <location> : Read-only file system
Do I need to do the superuser stuff first?
Click to expand...
Click to collapse
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
then push your file
califrag said:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
then push your file
Click to expand...
Click to collapse
Thank you. Having adb shell and the mount line in the same command worked perfectly.
I cant get it to work at all @[email protected]
Can I do this with root explorer? My comp took a dirt nap on me yesterday.
Or terminal emulator?
Sent from my Droid using XDA App
chuffykow said:
reboot the device
Code:
adb shell
reboot
This should be working, I've done very limited tests to confirm that it's accurate
Click to expand...
Click to collapse
Its not necessary to get into shell to reboot the device..
U can do this
Code:
adb reboot
New Market (2.2.11) on Nookie Froyo 0.6.6
Update 2/7/2011: Updated for Nooke Froyo 0.6.6. Please READ THE NOTES.
There are 2 methods: Pushing to existing system (just Market) and pushing to new system (all gapps, working Market & Youtube especially)
Notes:
You should exercise caution and make sure you match the case exactly as I have posted. For example, if you push vending.apk instead of Vending.apk, you'll still see the old one, etc. You may also be ignoring a failure message when you copy/paste a command. Report any failure messages.
There are now two sections: Updating and install of Market, and Fresh NookieFroyo/Fresh Market.
Method 1: You have an existing, older market, and you use SD Nookie Froyo. I will note that I started from a format of my SD card, and a fresh image. Report if you used an upgraded NF.
Steps to installing:
1. Download Vending_2_2_11.zip from below
2. Extract Vending_2_2_11.apk to somewhere on your computer. Note the location (eg C:\users\name\blabla\Vending_2_2_11.apk) as yours will be different.
3. Open up a command/termal
4. Use ADB as usual, and run the following commands:
Code:
adb shell
# mount –o remount,rw /dev/block/mmcblk1p2 /system
(should get a confirmation, it will say exactly what you entered)
# exit
adb push C:\users\name\blabla\Vending_2_2_11.apk /system/app/Vending.apk
5. Now, open Settings --> Applications --> Manage Applications --> All --> Market
6. Clear *cache*, and then Force stop
7. Press back
8. Select Google Services Framework
9. Clear *data*, and then Force Stop
10. Reboot
11. Open market
12. Insert credentials & accept agreement (if needed)
13. *Confirm new market. If you don't have it, stop here.
14. Download something
15. ??? Profit!
Method 2: You just installed Nookie Froyo, you use the SD card version, and you have no gapps.
***EXPERIMENTAL. Gnomes ahead!***
What I have done here is I have taken the nookie devs gapps zip, and changed out the market & youtube apks for known working apks.
1. Download nookie-froyo-gapps-20110207 from here:
(mirror 1 (likely dead) http://rapidshare.com/files/446788041/nookie-froyo-gapps-20110207.zip )
(mirror 2 http://rapidshare.com/files/446835767/nookie-froyo-gapps-20110207.zip )
(mirror 3 http://www.multiupload.com/RFP7W72EVS )
(mirror 4 http://www.multiupload.com/72F253U21B)
2. Unzip. Note the location (C:\Users\name\blabla\nookie-froyo-gapps-20110207)
3. Open up a command/terminal
Code:
adb shell
#mount -o remount,rw /dev/block/mmcblk1p2 /system
(should get a confirmation, it will say exactly what you entered)
# exit
adb push C:\users\name\PathToUnzippedGoogleApps\system system/
(should see each file push individually, followed by ## pushed successfully)
adb reboot
4. Open market
5. Enter credentials, accept eula
6. Download something, report success/failure of method 2.
7. ??? Profit? Thank me?
If it "freezes" at a loading screen, you may need to reboot.
Credit to the folks at XDA who have done this before on other devices. I just tried it and it worked. Also credit to http://aliwaqas.info/download-and-install-new-android-market-version-2-2-11-guide/ for the vending 2.2.11 apk
General Questions
How to get ADB or Nook Color ADB Drivers
http://nookdevs.com/NookColor_USB_ADB
I installed ADB & Drivers, but it isn't working!!!
Make sure that "USB Debugging" is enabled under Settings > Applications > Development > USB Debugging (check)
I can't see "x" app, or all apps
You need to change your build.prop
http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Access_Protected_market_apps
Neither method worked! Can't download apps. (after trying a reboot)
Please answer the following:
What version of Nookie Froyo (v.#x.#y.#z)
What type of Nooke Froyo (SD card, eMMC)
Which method (one or two)
Post a log of the commands you typed, and the output. Screenshots or copy/paste work best.
I tried it using rootEx since my ADB wasn't installed on a different PC. It did not work once adding to system/app or installing with r/w.
Worked Using ADB
I tried it with ADB, and it worked. Now Need for Speed Shift shows up. I tried everything before, but could not get it to show.
mattphoner said:
I tried it using rootEx since my ADB wasn't installed on a different PC. It did not work once adding to system/app or installing with r/w.
Click to expand...
Click to collapse
So double checking here:
/system was mounted R/W
you copied it in as Vending.apk (NOT Vending_2_2_11.apk)
you rebooted
And you still have the old market (with the gray bar)?
Tried again over ADB, that worked!! Not sure if RootEx is the way to go or not.
Anyone know if this will work on regular (nootered) 2.1?
Installed via Root Explorer, and it worked for me. Here's what I did:
Renamed it to: Vending.apk
Mounted System as R/W
Copied Vending.apk to: /System/app/
Rebooted NC then installed Vending.apk from /System/app/
Tested and working.
I tried installing it before rebooting and it just said that it didn't install.
JESTERDEV: on Froyo or 2.1?
sent from my nook color using XDA App
JesterDev said:
Installed via Root Explorer, and it worked for me. Here's what I did:
Renamed it to: Vending.apk
Mounted System as R/W
Copied Vending.apk to: /System/app/
Rebooted NC then installed Vending.apk from /System/app/
Tested and working.
I tried installing it before rebooting and it just said that it didn't install.
Click to expand...
Click to collapse
Maybe this is where I went wrong. I tried installing it BEFORE rebooting, not after.
I am unable to install from either method, RootExplorer or ADB.
With ADB everything went fine, but after reboot I had no Market installed. I checked the system directory, and the apk file was there, but trying to do anything with it resulted in "Unable to Parse Package" errors.
I tried manually with RootExplorer as well, and received the same errors.
EDIT: I even loaded my backup from RomManager to see if that would allow me to try again, but I am still receiving the same errors. Once again the ADB push method works fine to get the file in as Vending.apk in RW mode to system, but then upon reboot there is no market installed anymore.
The apk file is in the system/app directory, but it's not installed for some reason. Any attempt to do so results in the parse errors.
Not working on 2.1.
I haven't been willing to root my nook because all of my school books are on there. Just been using Nookie on SD. I'll update the OP later with some updated directions based on additional feedback tonight. Plus, I need to write a "from stock" tutorial that would be nice to have on the wiki.
Especially curious to know about it working on 2.1. Keep the feedback on that coming please
cybertimber2007 said:
I haven't been willing to root my nook because all of my school books are on there. Just been using Nookie on SD. I'll update the OP later with some updated directions based on additional feedback tonight. Plus, I need to write a "from stock" tutorial that would be nice to have on the wiki.
Especially curious to know about it working on 2.1. Keep the feedback on that coming please
Click to expand...
Click to collapse
You can keep your school books when you root the device. Just sayin'
Sent from my Nooted friend...
Tried to download something from the Market this morning, and it will not let me. I don't remember the exact error, but I will post when I get home. It worked just fine yesterday.
@hetzbh, Froyo.
JesterDev said:
Tried to download something from the Market this morning, and it will not let me. I don't remember the exact error, but I will post when I get home. It worked just fine yesterday.
@hetzbh, Froyo.
Click to expand...
Click to collapse
Not having a problem here. Anyone else?
Obviously there is something I'm doing wrong... I tried installing the new market with ADB and nothing happened...
What options do I have to install this correctly?
I didn't get any errors in ADB while installing
hetzbh said:
JESTERDEV: on Froyo or 2.1?
sent from my nook color using XDA App
Click to expand...
Click to collapse
no the it doesnt work on 2.1... but the 2.2.7 market works on the 2.1 system
djkns said:
no the it doesnt work on 2.1... but the 2.2.7 market works on the 2.1 system
Click to expand...
Click to collapse
Heh, funny. 'Cause originally I was going to post 2.2.7, but the IRC chat informed me that 2.2.11 was available. Did you use the same directions, but with the 2.2.7 vending instead of 2.2.11? I wouldn't mind posting that up there for 2.1 users.
bassrebel said:
Obviously there is something I'm doing wrong... I tried installing the new market with ADB and nothing happened...
What options do I have to install this correctly?
I didn't get any errors in ADB while installing
Click to expand...
Click to collapse
What exactly did you do, what happened (I guess you still have a gray top-bar market), did you reboot, and are you on Nookie Froyo?
Note that unlike most apks, you don't "install" (adb install <file>). You just push the file (adb push /system/app/Vending.apk). Also, there is case sensitivity. vending.apk and Vending.apk are two different files in *nix.
cybertimber2007 said:
What exactly did you do, what happened (I guess you still have a gray top-bar market), did you reboot, and are you on Nookie Froyo?
Note that unlike most apks, you don't "install" (adb install <file>). You just push the file (adb push /system/app/Vending.apk). Also, there is case sensitivity. vending.apk and Vending.apk are two different files in *nix.
Click to expand...
Click to collapse
Well... i booted froyo... then i installed the adb on my computer, opened superuser and followed the instructions, i didnt see an error msg, but when i try to check i dont see qmny market in my apps
This is how i managed to install the Google Maps 5.7.0 ownhere/Brut.all MOD which enables Navigation in countries where originally you cnt use this app. this is a modified version that seamlessly replaces the original app.
i tried to follow the instructions provided in the original thread but i kept facing problems and errors like "Application not installed" when trying to install the app, and "remount failed: no such file or directories", among others.
i also dnt have the Maps app availble in the market in my country, i can only sideload it.
it took me few days of googling to finally make it work on my Galaxy Ace. i'm running a rooted stock 2.2.1
it's simple once you got the right instructions. but as usual, i'm not responsible if your phone just decides to go brain dead on its own
for this you need ROOT access, Superuser, ADB and Titanium Backup
in Titanium Backup, choose Maps and back it up (app+data).
in case things dnt work out, you can always use this backup to restore the original app and data.
in Titanium Backup, choose Maps and wipe data then uninstall.
in Titanium Backup, choose Street View, wipe data and uninstall.
use whatever way to place the maps5.7.0-ownhere.apk file in the root of your sd card.
(i dnt know what's the diffrence between maps5.7.0-ownhere and maps5.7.0-ownhere-testkeyresign. i used the first and it's working fine.)
now connect your phone to your computer and make sure you keep your screen on. that's very important for the next step to work.
launch ADB and enter these commands:
adb shell (in the next line, a $ will appear)
su (when you inter this, Superuser in your phone will prompt you to grant root access. confirm it. a # will appear in the next line)
mount -t rfs -o remount,rw /dev/block/stl9 /system (this will remount your system in Read/Write mode)
cp /sdcard/maps5.7.0-ownhere.apk /system/app/maps5.7.0-ownhere.apk
mount -t rfs -o remount,ro /dev/block/stl9 /system (remount system back in ReadOnly mode)
exit
exit
Maps should appear in your app drawer.
you can now reinstall Street View.
if anything is not clear enough, just ask
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Sent from your phone
is it working
an0nym0us_ said:
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Click to expand...
Click to collapse
that was the first thing that came to my mind when installing didnt work. i copied the file with root explorer but the Maps app didnt show up in the app drawer.
i only speak from my own experience, i'm no expert.
thank you for the contrbution
imranaryan said:
is it working
Click to expand...
Click to collapse
it is working on my phone
I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
smnfriend said:
I saw a post in this thread about getting the promotional space on AT&T S4 without flashing TMobile roms. I gave it a try, and it worked just fine. So I thought of sharing the files with you. I pulled them out of a deodexed TMobile rom.
Download the attached file. You need to push Dropbox.apk and DropboxOOBE.apk into system/app and fix permission. Then you need to push com.dropboxpartner into system/framework and again fix permission.
Then, you need to modify the build.prop using a root explorer. Find the following lines and modify them as follow:
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
Reboot your device, open the Dropbox app, and log in with your existing account, or create a new account. You will receive an email, and after fulfilling 5 of the 7 tasks, you will receive the 48 GB promotional space. After fulfilling the tasks, you can restore your build.prop to its original state.
Attached Files:
http://d-h.st/fZJ
Click to expand...
Click to collapse
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device, but do not use the "stop" command below if you are using an emulator on the device.
Performed the following commands (after running "adb shell" from a command line on the computer):
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Worked for me:thumbup: Thanks! Now what to do after the two year promo period ends...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I'm already up to 50GB on doing something like this before. I'm not sure if it'll work again but I'll give it a whirl sometime today. Will report back if I find myself up to 98GB.
Perfectly working.
Followed general instructions (used FX root explorer instead of Android Terminal for dropping apks in designated locations) and this worked just fine without a hitch. I appreciate the straightforward and simple instructions.
All I did was flash Wicked (T-Mobile ROM) then KTOONSEZ touchjizz kernel. After getting my free dropbox space, I flashed back.
Sent from my SGH-I337 using xda premium
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Slade8525 said:
lol same here with GOLD3N3Y3 rom; any non-ATT rom works if you DL and activate it. i have my own server so im letting everyone in my family use it for our stuff.
Click to expand...
Click to collapse
i can confirm that this works on vzw.
Thanks, worked great on my VZW S4.
Aou said:
Worked great for me, thanks! I already had 12GB and had completed the 5 Getting Started steps long ago. When I signed into the DropBox app and got it setup, I suddenly had 60GB for 24months and an email from DropBox.
Here's the instructions I followed:
Cleared cache of, cleared data of, and uninstalled the DropBox app I already had.
Reminder: backup your build.prop
I ended up using this build.prop Editor. When you open it, use the menu key to make a backup before touching anything. Then scroll through and make the changes prescribed in the OP.
Downloaded the file attached in OP.
Extracted files using my computer to my internal sdcard. Possible to do this with apps on your phone (various file explorers or unzip programs), but I found it easier to just do it over USB/MTP.
Fired up ADB Shell - could also use a terminal emulator from the device...
Performed the following commands:
Code:
$ su
# mount -o rw,remount /system
# stop
# cp /sdcard/Dropbox.apk /system/app
# cp /sdcard/DropboxOOBE.apk /system/app
# cp /sdcard/com.dropboxpartner.jar /system/framework
# reboot recovery
Device rebooted into TWRP, where I used the Advanced menu to Fix Permissions.
Rebooted back into the System like normal.
Opened the DropBox app and signed in. Setup the camera sync again of course (awesome feature).
Checked my mail - Woot.
Used the build.prop editor to restore my build.prop
Closed the build.prop editor and re-opened. For some reason after restoring the backup, the restored changes were not reflected until I restarted the editor. Whatever, but it worked.
Click to expand...
Click to collapse
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
You need to do it from your computer terminal/shell using adb shell command through the USB, not using a terminal emulator on the device. Stop does exactly what it says, it stops the device from running I think , or maybe just pauses.
You should be able to copy the files without stop though, it's probably riskier, and then you need to use reboot. You just need to copy the files into the right locations and then fix the permissions.
Cinosinu said:
Using terminal emulator, after using #stop, device screen goes black... what do I do, just wait?
Click to expand...
Click to collapse
These are linux commands. Stop, stops your device, and you cannot use it unless you reboot it. You can punch in the commands through your computer (this way, you need to install android sdk. Then, open the installed folder, and go to sdk\platform-tools. Here, you should hold shift, right click and select "open command window here", and punch the commands). Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Just pull the battery and reboot. It happened to me also.
Sent from my SGH-M919 using xda premium
smnfriend said:
Also, you can simply use a root explorer, and manually move the files to their folders and fix permissions
Click to expand...
Click to collapse
What does this mean? I have ES fie explorer, trying to move the files I get a rewrite error. Do i need to fix the permissions first? What is the adb command?
thanks
I got it!!! :victory:
Why didn't someone tell me you must use the command 'ADB Shell' to start?
I'm no expert with ADB obviously. Knew it was something trivial. Hope someone else finds my comment helpful. :highfive:
Thank you OP and all! XDA rocks!
Thanks for pointing these things out. Yes, "stop" should only be used if doing this from an ADB shell. I've updated my instructions a tad bit to reflect this.
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
kalparker said:
How can i do this for multiple accounts? I logged out and in and no luck.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
xrabbitfootx said:
did you do a factory reset, re-install of your ROM, then the steps again? that may help by giving you a different device ID (you may have had this warning before in TiBU), which i'm guessing DB is looking for to limit 1 upgrade per device ID.
-rf
Click to expand...
Click to collapse
That might work. In TiBu, I have the option to create a new, random device ID - might be a Pro feature only. Check your menu key, and near the bottom you can Manager your Device ID...
I would advise a nandroid backup first - this may screw up some of your other accounts, including Google. I've personally never tried it, but I would imagine it could cause some amount of chaos.
thanks!
Tried every method...but I'm unable you protect my backups in titanium backup
To protect*
How I solved this problem on my Moto G LTE
Shantanu Baviskar said:
Tried every method...but I'm unable you protect my backups in titanium backup
Click to expand...
Click to collapse
I carefully read this thread: [Help] Titanium Backup PRO - protected archive not working.
So I modified file /system/etc/permissions/platform.xml according http://jrummy-apps.com/fix-sdcard-on-kitkat/ and make new file /data/local/userinit.sh with this content:
Code:
#!/system/bin/sh
busybox mount -o remount,rw /
chmod 770 /mnt/media_rw
See the attached archive root.zip which I made for you it is pretty straightforward.
You should have move your TiB backup folder on this path: /mnt/media_rw/sdcard1/TitaniumBackup
You will be able to protect backup archives in Titanium Backup Pro then.
PS: If /data/local/userinit.sh doesn't start automatically in your ROM you can use for example Scripter feature in ROM Toolbox Pro and import userinit.sh script and set it as Start at boot.
_jis_ said:
I carefully read this thread: [Help] Titanium Backup PRO - protected archive not working.
So I modified file /system/etc/permissions/platform.xml according http://jrummy-apps.com/fix-sdcard-on-kitkat/ and make new file /data/local/userinit.sh with this content:
Code:
#!/system/bin/sh
busybox mount -o remount,rw /
chmod 770 /mnt/media_rw
See the attached archive root.zip which I made for you it is pretty straightforward.
You should have move your TiB backup folder on this path: /mnt/media_rw/sdcard1/TitaniumBackup
You will be able to protect backup archives in Titanium Backup Pro then.
PS: If /data/local/userinit.sh doesn't start automatically in your ROM you can use for example Scripter feature in ROM Toolbox Pro and import userinit.sh script and set it as Start at boot.
Click to expand...
Click to collapse
Although in the case of Note 4 it didn't work right off the bat, I made it work a little different thanks to your idea. For some weird reason the script just doesn't get executed at boot (neither the *.sh file, nor as a script, through ROM Toolbox) but I was able to use the 2 lines in the script and made a task (in Tasker) which executes the shell command at boot. Everything else is straight forward and TiBu can now protect backups.
As a mention for those interested in replicating all these: the suggested SD card fix made by rummy applies EXACTLY the same changes as the SDFix so you can use either of them. Again, thanks for your reply and the great idea! :good:
nacos said:
I was able to use the 2 lines in the script and made a task (in Tasker) which executes the shell command at boot. Everything else is straight forward and TiBu can now protect backups.
Click to expand...
Click to collapse
Great, this is another example how to execute script at boot
I solved this problem on all my phones (Moto G LTE and Samsung Galaxy Note 2 and Samsung Galaxy W) but not on my tablet Nexus 7 2013 nor on internal emulated SD card nor on attached OTG USB flash disk. This is example where pure Stock Google Android ROM sucks
_jis_ said:
Great, this is another example how to execute script at boot
I solved this problem on all my phones (Moto G LTE and Samsung Galaxy Note 2 and Samsung Galaxy W) but not on my tablet Nexus 7 2013 nor on internal emulated SD card nor on attached OTG USB flash disk. This is example where pure Stock Google Android ROM sucks
Click to expand...
Click to collapse
This update addresses the issue mentioned before about init'd scripts not executing at boot. OK, here is the issue (specific to Qualcomm's Snapdragon) and the working solution - thanks to alexndr. I've tested it and it's working, however it doesn't work directly with <X.sh> text files, instead the script must be packaged in a flashable zip and flashed from recovery. Once I did that, it worked like a charm! The 98mediarw file in the screenshot uses the same script as previously mentioned; The 98 before the file name assigns a higher execution priority - I used 98 for testing purposes, it clearly doesn't need that. :good:
nacos said:
OK, here is the issue (specific to Qualcomm's Snapdragon) and the working solution - thanks to alexndr.
Click to expand...
Click to collapse
Oh, at first I thought that you post something what helps me with my tablet:
_jis_ said:
I solved this problem on all my phones but not on my tablet Nexus 7 2013 nor on internal emulated SD card nor on attached OTG USB flash disk.
Click to expand...
Click to collapse
But this is just another example how to execute script at boot
none of these methods are working. Is it because I'm using a Custom ROM?
What are you trying to achieve? What exactly is your environment?
nacos said:
What are you trying to achieve? What exactly is your environment?
Click to expand...
Click to collapse
I have Motorola Moto E (CM11 Stable build by percy_g2) and I'm trying to protect my backups in TiB but I'm getting error "Sorry, the operation failed." It used to be the same in stock ROM. And one more question, is this bug fixed in Lollipop versions of Android?
To answer you questions, no, this is not a bug, it's by design, also it's not happening because you're using a custom ROM, but rather because all OEM's (Google being probably the worst of all) are pushing towards more and more restrictive software & hardware environments, also supported by laws meant to discourage the users from modifying original configurations. Why? Dirty politics, I won't get into that but if you keep your eyes wide open you'll see and understand A LOT! Oh, by the way...to expect for Lollipop to be less restrictive and more fun (to customize) would be naive! Nuff said, let's have some fun!
There are multiple parts to this fix/diagnostic. Don't skip any point and follow these instructions rigorously, otherwise it won't work!!! Let's take them one by one:
Is you platform.xml file (under system/etc) modified to allow read/write access to media_rw (mnt/media_rw)? If not, apply the patch using SDFix from Google Store.
TiBu backup folder must be set to mnt/media_rw/externalSD/Titaniumxxx (if you don't have externalSD than use your internal storage instead, pointing to TiBu folder) - but, for right now, you won't be able to set this path because currently TiBu doesn't have access to media_rw, due to media_rw not being given the right permissions by the system. That's exactly what mediarw script does.
In order for init.d to execute the mediarw script at every boot, you need to insure that you do have init.d support AND it's working. This is how you verify:
(3a) Do you see the folder system/etc/init.d? If yes, go to (3b), if no, you don't have init.d support! That's another fix entirely.
(3b) If you see the 00test file in the init.d folder navigate to /data and open up the file called Test.log - that tells you that init.d is installed and working. If you have a Qualcomm's Snapdragon and you do have the init.d folder but it doesn't execute any script at boot, see the fix in post #6.
(3c) If you don't care about setting up init.d support, you can still run the script at boot, as a shell command using Tasker - see post #4
Once you're sure that all the above are set correctly, flash the attached file from recovery. Reboot, navigate to system/etc/init.d and confirm the presence of the mediarw script in the init.d folder
Reboot again, then navigate to mnt/media_rw and check that permissions for media_rw have been set to 770 - :fingers-crossed: mission accomplished, my friend! :fingers-crossed: If, on the other hand, the permissions for media_rw are still set at 700, then something went wrong. Go back and check every step again, otherwise...
Open up TiBu, set the backup folder path as instructed in #2 and verify that your backups can be protected. Voila!!
nacos said:
To answer you questions, no, this is not a bug, it's by design, also it's not happening because you're using a custom ROM, but rather because all OEM's (Google being probably the worst of all) are pushing towards more and more restrictive software & hardware environments, also supported by laws meant to discourage the users from modifying original configurations. Why? Dirty politics, I won't get into that but if you keep your eyes wide open you'll see and understand A LOT! Oh, by the way...to expect for Lollipop to be less restrictive and more fun (to customize) would be naive! Nuff said, let's have some fun!
There are multiple parts to this fix/diagnostic. Don't skip any point and follow these instructions rigorously, otherwise it won't work!!! Let's take them one by one:
Is you platform.xml file (under system/etc) modified to allow read/write access to media_rw (mnt/media_rw)? If not, apply the patch using SDFix from Google Store.
TiBu backup folder must be set to mnt/media_rw/externalSD/Titaniumxxx (if you don't have externalSD than use your internal storage instead, pointing to TiBu folder) - but, for right now, you won't be able to set this path because currently TiBu doesn't have access to media_rw, due to media_rw not being given the right permissions by the system. That's exactly what mediarw script does.
In order for init.d to execute the mediarw script at every boot, you need to insure that you do have init.d support AND it's working. This is how you verify:
(3a) Do you see the folder system/etc/init.d? If yes, go to (3b), if no, you don't have init.d support! That's another fix entirely.
(3b) If you see the 00test file in the init.d folder navigate to /data and open up the file called Test.log - that tells you that init.d is installed and working. If you have a Qualcomm's Snapdragon and you do have the init.d folder but it doesn't execute any script at boot, see the fix in post #6.
(3c) If you don't care about setting up init.d support, you can still run the script at boot, as a shell command using Tasker - see post #4
Once you're sure that all the above are set correctly, flash the attached file from recovery. Reboot, navigate to system/etc/init.d and confirm the presence of the mediarw script in the init.d folder
Reboot again, then navigate to mnt/media_rw and check that permissions for media_rw have been set to 770 - :fingers-crossed: mission accomplished, my friend! :fingers-crossed: If, on the other hand, the permissions for media_rw are still set at 700, then something went wrong. Go back and check every step again, otherwise...
Open up TiBu, set the backup folder path as instructed in #2 and verify that your backups can be protected. Voila!!
Click to expand...
Click to collapse
(Please ignore that screenshot. I didn't properly read your msg in blue text)
I couldn't understand post #4 so can you please describe it more deeply? :crying: btw I don't have 00test but a file named 00banner. And can you tell me how to use tasker properly?
Sorry for butting in on this thread. I found it by searching because I too can no longer protect a backup in my tibu Pro. I used to be able to but not anymore and I'm not sure why.
I'm on a rooted nexus 5 running stock 4.4.4.
Reading your instructions I went looking for platform.xml and found it. When I checked its properties I got, see screenshot. Don't know what to modify to mount it as you say. I'm in ES Explorer.
Can you help?
Thanks.
And here is a screenshot in root Explorer
Update your tb to 7.0.1 and now you can protect backups ? this thread should get closed now
Closed? Why? Just because a shortcut is available doesn't mean there is nothing to learn from wondering around, my friend!
After all, this is exactly what XDA is: a huge data base available to those who are willing to learn and dare to wonder around, wouldn't you agree?