Database Users

GPS fixed on Captivate. Combination of 2 methods + detailed steps

This is how I fixed my GPS issue on Captivate. It would not lock on, not even after 5 minutes of me standing still.
Found this thread - http://forum.xda-developers.com/showthread.php?t=786486
Was trying to follow the steps and realized I wished it was spelled out more. So this is what I am doing in this thread, to make it easier for everyone else, if they decide to try. After an hour of googling commands and trial and error - its done, and my phone's GPS locks on under 10 seconds.
I downloaded that zip file. Then installed Droid Explorer on my PC. I already had USB drivers installed for the Galaxy S, so during install I unchecked it. When I opened Droid Explorer I realized I cant write to the /system/bin and the other two. The Write permissions for the system folder were not set, so when I dragged files over - they wouldnt copy over to my phone. It would kinda "refresh" but files wouldnt show up in there.
Easy way seemed to be to buy and install Root Explorer on my phone from the market. And click on Mount R/W for the system folder. However I am waiting for credit card replacement in the mail and was so fed up with GPS that I wanted to do it NOW, and was not gonna stop until its done. Today.
So the other way to make /system/bin , /system/etc and /system/lib folders writable was thru command prompt.
First off my phone has Cog 5.5 on it so it is rooted.
1. set phone in usb debugging mode and connect to pc
2. navigated to my sdk/tools directory on my hard drive. In my case it looked like this
Code:
cd c:\sdk\tools
<hit enter> but it depends on where you downloaded and unzipped your android SDK folder
3. typed
Code:
adb shell
<hit enter> then
Code:
su
<hit enter> to give me root access to the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone will ask if you want to grant permissions to unknown, hit Yes.
4. Now we need to set system as writable. While googling commands it seemed that the command should be
Code:
mount -o rw,remount /system
But in my case that didnt work, telling me location was invalid. I obviously was missing something. Duh! correct location! So -
type
Code:
mount
<hit enter> It will list the root directory. We need t locate exactly where system is on the phone. In my case it was /dev/block/st19 /system
So the command should be then
Code:
mount -o rw,remount /dev/block/st19 /system
<enter>
then
Code:
chmod 777 /system
<enter>
Code:
chmod 777 /system/bin
<enter>
Code:
chmod 777 /system/etc
<enter>
Code:
chmod 777 /system/lib
<enter>
Code:
exit
<enter>
and one more time
Code:
exit
<enter>
The folders are now writable.
5. Opened Droid Explorer, copied files over, lbstestmode launch app was already installed on my phone. So it didnt have to do that step, as it was in j101399j's thread
6. Rebooted the phone, opened lbstestmode, deleted GPS data.
Started testing. It wouldnt lock. Went to Get Position Test in lbstestmode app. It would see the sattellites, 8 of them but wouldnt give me my lat/long! So I remembered this post - http://forum.xda-developers.com/showpost.php?p=9150551&postcount=7862 by cnewsgrp
and changed
3. In the LBSTestMode menu change “Operation Mode” to MS Based
4. In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl)
Click to expand...
Click to collapse
Didnt even have to reboot. Went to Get Position Test again and it saw like 8 or 9 satellites and had * next to 4 of them in 10 seconds. Give me my lat/long with precision. Wanted to mention that I tried cnewsgrp 's method a week ago, just by itself, and it gave me no results.
So to summarize. Combination of those 2 fixes worked wonders for me. And the Captivates GPS issue is definitely not hardware based.
I do have a question however,lol, how do I revoke write settings for my system folder, and go back to how it was? Would that be
Code:
chmod 755
?
I hope these detailed instructions help someone.

And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.

chmod 777???
NO THANK YOU!!

zerojay said:
And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.
Click to expand...
Click to collapse
it didnt change file settings inside folders, just folder setting

also this is where I got chmod 777 from - http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://karuppuswamy.com/wordpress/2009/04/25/mounting-system-partition-in-read-write-mode-in-android/
was obviously for android.

There's a reason why 777 permissions weren't there to begin with
also I love how there are currently 7 views and 6 replies. which means almost everyone is going - Aaah!!!!! NOOO!!! Must post and warn her!!!

my phone's GPS locks on under 10 seconds
Click to expand...
Click to collapse
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads

sinoth said:
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads
Click to expand...
Click to collapse
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
Yes there is a
"a reason why 777 permissions weren't there to begin with"
Click to expand...
Click to collapse
It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.

bmvik said:
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.
Click to expand...
Click to collapse
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
I agree. I'll let you know regarding tracking as I test. Before however, not only it would take 5 min to lock on, but would lose me while I was driving, constantly. Accuracy was jumping to 200 meters or so. So instant lock was a good sign to me.

bmvik said:
Yes there is a It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
Wow, the cluelessness.

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
For me it does. I have been using GPS with any issues for past few days. And to give credit what ever steps I have posted have been around for a long time just search for "Vibrant GPS fix". The only reason I needed to do that was my GPS stopped working after applying Cog 2.4 ROM with is Vibrant ROM. I applied Vibrant GPS fix and voila GPS now works!!
I must stress here that I have had no GPS issues with any of the Captivate ROMS or Stock ROMS. I usually get lock in 10 - 30 seconds and it tracks well for me. I used GPS test and I an see around 8-9 satellites with S/N ratio of 35 and accuracy of 16.5 regularly.

Oh the boogeyman
I also would like to add, had anything went wrong during these steps - I would've just reflashed my phone to another Cognition ROM and started from scratch. Voila!

bmvik said:
Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
bmvik said:
Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Click to expand...
Click to collapse
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.

installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
Thank you. I mean, really.
fatttire said:
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.
Click to expand...
Click to collapse
Let me spell it out for you. In this thread http://forum.xda-developers.com/showthread.php?t=786486 OP suggests
2. Using root explorer or droid explorer, copy the files from each folder.
Click to expand...
Click to collapse
For root explorer to be able to write to system folder it would HAVE to change that folders permissions. I didnt have the app, so changed them manually, then used droid explorer. Then changed permissions right back to 755.
cnewsgrp said:
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.
Click to expand...
Click to collapse
Well I just copied the files from the zip file I linked to in the OP, over to the system/bin, /etc and /lib I dont know how screenshot would help

aaaand uhhhhhh can you non-haters vote the thread up, plz? some 5 haters hit 1 star

OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App

skinien said:
OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol stop using the samsung keyboard the period is in the wrong spot.
btw op can you plz post some tracking results with mytracks or something. Locking on is not the problem, tracking is.
If you do ill vote this thread up

Editing build.prop tutorial

I haven't seen a guide for this yet...but if there is mods please delete this.
Your build.prop is what tells android what your phone is. A Nexus S a Motorola Droid, or a Samsung Epic. Knowing how to change it can be EXTREMELY useful from tweaking your phone to faking it to run netflix.
There's 3 ways to modify your build.prop. You must have root (and busybox) for all of them, but I beleive if you want to you can unroot and it will stick.
ADB
Adb is a part of the android sdk, and is more for advanced users then novices. You can modify your build.prop by using adb and pulling it, editing it on your computer, and putting it back. Not the simplest way.
Type in adb:
Code:
adb pull /system/build.prop C:\Users\user\Desktop
Always replace "user" with your windows username
You should see a file named "build.prop" on your desktop. Open it with WORDPAD, not notepad. Change what you want. When your done, type this:
Code:
adb push C:\Users\user\Desktop\build.prop /sdcard/build.prop
This will put the build.prop on your sd card, since we cannot directly push to /system
Code:
adb shell
This should give you a shell. A shell is where you can run commands. After you have a shell, type:
Code:
su
mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system
You have successfully changed your build.prop!
File Expert (or other free file managers) and text edit
This involves two apps, File Expert (or similar) and Text Edit. They can be found on the market here: File Expert and Text Edit
After you install these two apps, open File Expert. Click the menu button (the one on the phone), more, and Settings. Click on File Explorer Settings and click Root Explorer. It should request root, allow it. Press back twice to go back to your sd card. Then press back twice again. Click on /system. Press the menu button, more, and click mount. Select "Mount as Read Write". Now long click on build.prop and select File Operations. Click permission. A menu should pop-up, check the boxes so it looks like this
Code:
X X []
X X []
X X []
and click apply. Now, click on build.prop and it should say open as. Click text, then Text Edit.
Feel free to edit as you please! Once your done, click menu, then save. Then close the application. Don't forget to go to file expert and unmount system as rw, do this by going to the system folder and clicking menu, more, Mount, Mount as Read Only. Your done!
The easy way
Go buy an app. Really, some are worth the trouble. Two apps that will help edit your build.prop are Absolute System and Root Explorer
Thats about it. Any suggestions on how to edit, I'll add in this op. So be sure to leave them!

thanks for this! I have it bookmarked but where can i find common build prop edits?

You can also use ROM Toolbox to edit some items on the build.prop

For version 2 above, I use ES File Explorer and its built in ES Text Editor. One app instead of two. Same effect.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"

tq, nice info
Sent from my SCH-I500 using XDA App

awesome post. comes in handy

Is it not just possible to take the zip from a custom rom and modify it with Notepad++?

zanderman112 said:
For version 2 above, I use ES File Explorer and its built in ES Text Editor. One app instead of two. Same effect.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
Click to expand...
Click to collapse
I came to say the exact same thing.
Sent from my SPH-D700 using Tapatalk

You may want to add quotes for the desktop directory in case their user name is "John Smith"
Sent from my SPH-D700 using Tapatalk

ugothakd said:
File Expert (or other free file managers) and text edit
This involves two apps, File Expert (or similar) and Text Edit. They can be found on the market here: File Expert and Text Edit
After you install these two apps, open File Expert. Click the menu button (the one on the phone), more, and Settings. Click on File Explorer Settings and click Root Explorer. It should request root, allow it. Press back twice to go back to your sd card. Then press back twice again. Click on /system. Press the menu button, more, and click mount. Select "Mount as Read Write". Now long click on build.prop and select File Operations. Click permission. A menu should pop-up, check the boxes so it looks like this
Code:
X X []
X X []
X X []
and click apply. Now, click on build.prop and it should say open as. Click text, then Text Edit.
Click to expand...
Click to collapse
If anyone has any problems, MAKE SURE you're using TEXT EDIT. That solved my problem! =D

Actually Z, root explorer will let you edit the text.
Sent from a phone with kNOw CIQ

So I got the editing part down, how about potential options. Like what identifies the device to the market? I wanna be able to increase my app compatibility and I'm wondering if changing from an ei22 fingerprint to something else may help?
sent from the other woman

bryanfritz1 said:
So I got the editing part down, how about potential options. Like what identifies the device to the market? I wanna be able to increase my app compatibility and I'm wondering if changing from an ei22 fingerprint to something else may help?
sent from the other woman
Click to expand...
Click to collapse
I'm not sure but I think it's your build I.d. Just woke up and still learning.
Via OG Epic 4g Cm9 & NYGiants 2012 Champions!!!!!

So here is my build.prop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. The part about ei22 and test keys can that be updated to something different (newer) and would that play a part in the market apps not being compatible? Thx guys just trying to understand how it all works together.
sent from the other woman

Hi!I have xperia mini with ICS.My device wake up if I push the volume button(unlock).I edit the build.prop.I writing this line:ro.config.hwfeature_wakeupkey = 0.
But this not working just with radio.Its not good with Proplayer.
Any solution?

My huawei 8650 sonic freeze after i do your steps because i forgot to install the busybox any idea what i can do ?
sry for my english...

Thank you so much!!!!!!:victory::victory::victory: o/

Nice OP!

Pure Awesomeness
Thanks a million! :good:

hey guys i need a big help whit that i was tweaking the build.prop of my pantech flex is already rooted but it get stock into the logo of att i mean it got brick so i decide to modifited the build.prop to the original i mean just erasing the lines i added to it but i was just fine doing the abd pull and the push to the sdcard build.prop but i get failed doing (su
mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system) in the cmd it stay doing anything

[Boot Animation]Droid Prime

Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and have been waiting patiently ever since. I posted about it already now its ready for the wild.
I did not create this. I have only edited the desc.txt so it will run on our phones. All credit goes to BootAnimator on RootzWiki. Again I did not create this so please thank the creator BootAnimator on RootzWiki
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unzip the file then follow the instructions below.
http://www.mediafire.com/?7tmnb3u7axbu2u0
Root Explorer method:
1. Rename your bootanimation to bootanimation (if not already named this)
2. Put it on your SD card
3. Open Root Explorer and copy bootanimation.zip to /system/media. This will replace the existing boot animation
4. Reboot your phone
ADB method:
1. Make sure you have downloaded android sdk
2. Put android sdk in C:\
3. Set the directory of command prompt to C:\android-sdk-windows\platform-tools. Click here for a video tutorial.
4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools
5. Open cmd
6. Type in order:
-adb remount
-adb push bootanimation.zip /system/media/bootanimation.zip
-adb reboot
Click to expand...
Click to collapse
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
Originally Posted by hockeyfamily737
0. It's recommended to do a nandroid backup first!
1. Download the "bootsnd.sh" file and put it on the root of your sd card.
2. Using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media
3. Open Terminal Emulator and type the following commands using the stock keyboard. Press enter after each line:
su
cd /sdcard
sh
sh bootsnd.sh
reboot
4. As the device boots up you will hear the transformers sound bite sound. You are now free to replace the android_audio.mp3 file in /system/media with any .mp3 file you like as long as you rename it to "android_audio.mp3"
5. DO NOT ATTEMPT TO OUTSMART THESE DIRECTIONS OR YOU WILL BE RESTORING YOUR NANDROID BACKUP!
6. Enjoy
Click to expand...
Click to collapse
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Here is how to fix it.
Make sure you are mounting in r/w mode on each of these steps.
Using a app like root explorer, goto /system/bin and delete the file bootsound.
Back out to /system now open build.prop in text editor mode, look for this text.
Code:
ro.config.play.bootsound=1
Delete it from the build.prop and save and exit.
This is optional but recommened.
Reboot phone.
Verify no sound is playing.
Now run the script again and reboot.
You should have a boot sound again.
Click to expand...
Click to collapse

Sent from LGE XDA phone

eollie said:
Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and have been waiting patiently ever since. I posted about it already now its ready for the wild.
I did not create this. I have only edited the desc.txt so it will run on our phones. All credit goes to BootAnimator on RootzWikiAgain I did not create this so please thank the creator BootAnimator on RootzWiki
Unzip the file then follow the instructions below.
http://www.mediafire.com/?7tmnb3u7axbu2u0
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Click to expand...
Click to collapse
Umm... It never work... I tried this for 7 times...
Sent from LGE XDA phone

Do this plug your phone in via the usb and open adb window.
Type "adb shell bootanimation".
It will say "mmap failed:errno 19 no such device" and play the animation on your phone screen.
If it says anything else post it here and I can figure out what the problem is.

Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk

lekhwani said:
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
+1 Same... 40 times I tried ur method...
Sent from LGE XDA phone

lekhwani said:
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
dax4182 said:
+1 Same... 40 times I tried ur method...
Sent from LGE XDA phone
Click to expand...
Click to collapse
Im sorry its probably your phone. I see dax is using a P500. Some phones just wont play the boot sound.Ive seen it happen on the V no reason just refuses to play.

eollie said:
Im sorry its probably your phone. I see dax is using a P500. Some phones just wont play the boot sound.Ive seen it happen on the V no reason just refuses to play.
Click to expand...
Click to collapse
But on the official ginger is able to play the bootsound as is original manfacturered...
Sent from LGE XDA phone

DaxElectro said:
But on the official ginger is able to play the bootsound as is original manfacturered...
Sent from LGE XDA phone
Click to expand...
Click to collapse
Where is the bootsound located on the official gingerbread release?
I only say some phone just wont play it because Ive tried to help several people on android central get it working and their phone just wont play it no matter what we did. Im sure somebody with more knowledge than I have on this would be able to figure it out, however Im not sure why it wont work. I was told that on CM rom the kernel was trimmed and bootsound was removed that is why you have to run the script I link to.

[GUIDE][XT1254]Getting Xposed Working

Guide: Getting Xposed Running​This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.

Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.

ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.

i dont need it but its a great guide, easy, short and with pictures!

Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.

Thanks so much man, about to flash. Will let you know how it goes.

Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours

It did not work for xposedbridge.jar

aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated

savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app

I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?

After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?

I am having same problem as u smokie

smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.

Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!

Thanks for this , works great , now we just need one with busybox preinstalled

Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse

so will doing this enable gravitybox to work on the turbo?

hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces

rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!

[Root] Complete Stock PH1 Setup with Root - Everything working

Verizon
I am not responsible for anything that happens to your device by doing this! If you break it, brick it or just plain blow it up. it is your phone and your responsibility for what happens to it.
Here it is. Full Verizon With Root - since this is Verizon based all bands should work as well
This is Based on the Verizon PH1 Firmware and is Completely Stock and Unmodified
To Avoid Repeat Questons. READ! READ IT AGAIN! and then READ it once more! if you do not Understand any part of this. Do Not Continue!!!
This Guide assumes you have some basic knowledge and can at least copy and paste for the most part! It is Intended for advanced users!!!!!!!!
This Guide also Assumes you have an sdcard inserted in your phone(however some of you may not and this will not work.)
This Does NOT Trip Knox.
Read this entire post before doing anything to avoid issues and FOLLOW Directions - if you don't things will not work right.
Note! if at anytime during the following steps you see the samsung boot animation before step 11. start over cause you screwed up!
Step 1. Initial PreSetup Requirements and Downloads
Make Sure your ExtSDCard(the one you put in your sim tray) is formated exfat(backup your card before you do this in windows or linux(whichever you use))
https://www.androidfilehost.com/?fid=24651430732237653 bbx.rar
https://www.androidfilehost.com/?fid=24723785898787028 Verizon_System.rar
https://www.androidfilehost.com/?fid=24713784966775399 Verizon Bootloader
https://www.androidfilehost.com/?fid=24713784966775400 Verizon Modem
Step 2. extract system.rar and bbx.rar and then copy system.img and bbx to your extsdcard(the sdcard you inserted into your phone)
Step 3. odin sprint userdebug firmware available here. http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
Step 4. Directly after odin is done with the sprint file you will immidiatly be presented with an update screen
Step 4a when this process of erasing your phone is finished it will reboot(this is the point you want to do the next step)
Step 4b. press and hold power, home and vol up to enter recovery
Step 4c If you see the samsung boot animation. you did NOT do this right and i would suggest you start over
Step 5. open a command prompt in your adb folder and do the following steps 1 at a time(these are case sensative)
Step 5a. adb shell
Step 5b. su
Step 5c. setenforce 0
Step 5d. export PATH=$PATH:/sbin
Step 5e. mount -o remount,rw /
Step 5f. on your phone, go to apply update from sdcard(this will mount your extsdcard as /sdcard and you should see the system.img file and the bbx file) do not select anything, go back to adb and continue(it is not a big deal if those files don't show. we just needed the extsdcard mounted as sdcard - the files exist, just continue to the next step)
Step 5g. cp /sdcard/bbx /sbin/bbx
Step 5h. chmod 777 /sbin/bbx
Step 5i. cd /sbin
Step 5j. ./bbx --install /sbin
Step 5k. umount -l /system
Step 5l. /sbin/dd if=/sdcard/Verizon_System.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
Note. you will see a blinking cursor. just be patient
Step 7. when it is done you will see something similar to this
11161600+0 records in
11161600+0 records out
5714739200 bytes (5.3GB) copied, 268.668086 seconds, 20.3MB/s
Step 8. if all went well you should be at your prompt and not in adb anymore
Step 9. from your command prompt simply type
Step 9a. adb reboot bootloader
Step 10. open odin and click the bl button and select this file - BL_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10b. now click the cp button and select this file - CP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10c. now click start. it will reboot when done let it fully boot this time.
Step 11. once booted and you have setup your phone, first we need to enable usb debugging
Step 11a. to do this go to settings>about device or device information and tap the build number repeatedly until it says dev options enabled, now backout of about and go into dev options and enable usb debugging
Step 11b. Now we need to add the root files or supersu as most of you know it
Note! pertaining to Step 12. these instructions were taken Explicitly from @freeza thread which is listed in step 3
Step 12. Now we need to add supersu and the needed files for it to work
Step 12a. download this file - https://www.androidfilehost.com/?fid=24651430732236679
Step 12b. Extract the sun7 file to your adb folder making sure the files are in a folder called sun7(mine looks like this - c:/adb/sun7 and contains 4 files)
Step 12c. Open a command prompt where your ADB executable and sun7 folder are.
Step 12d. adb shell
Step 12e. su - Note! if your adb prompot changes from a $ to #(you are good and have root access)
Step 12f. type exit twice to get back to the command prompt. - Your Phone should be fully booted when you do this
Step 12g. adb push sun7 /data/local/tmp/su
Step 12h. adb shell chmod 0777 /data/local/tmp/su/*
Step 12i. adb shell
Step 12j. cd data/local/tmp/su
Step 12k. su
Step 12l. ./root.sh - Note. this command begins with a . do not leave it out
Step 12m. Your Phone will now reboot
Step 13. when booted back up go to playstore and install busybox on rails or a similar app and install busybox to /system/xbin(if your given an option of where to install it)
Step 14. Thats Pretty Much it. most of all enjoy it
Additional Notes!
If for any reason you do a factory reset. you will break root and need to redo this method to get it back
If you use shealth do not update it or allow playstore or galaxy appstore to auto update it or it will break it
Enjoy and FOLLOW Directions - if you don't things will not work right.
thank you to the following:
@freeza - for posting the original userdebug file
@ted77usa - for testing
@bajasur - for the initial idea which ultimately led to this
@Surge1223 - for the busybox installer and the adb help and android commands that make this work
@galaxyuser88 - for testing this and pointing out some flaws
@Hashcode - for inspiration
and anyone i missed
this was a complete collaboration and is only available because of those mentioned so be sure to give them thanks
ScreenShots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
screenshots provided by @ohblindone

This Method Completely replaces the Sprint files with verizons. with exception to the kernel, recovery and the su binary. so everything once complete is now verizon and not sprint with verizon touchs thrown in to make it work.
as we don't have an unlocked bootloader, there is no twrp recovery. but flashfire takes it place. so any changes you want to make are basically done the same way as they would be for twrp except they are now flashed through flashfire.
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
If you don't see the Verizon_System.img and bbx files after doing the apply update from sdcard on your phone. try this as it has worked for some on t-mobile
create 3 folders on your sdcard
create "files" inside of that, create one called "image" and then inside of that crate one called "file" so on your sdcard you would have /files/image/file and place the 2 files into it, you have to do this with the phone in recovery so just pop out your sim tray. plug the sdcard into your pc and create the folders and move the files into it, then force your phone into recovery(basically reboot your phone and instantly go into recovery) and start step 5 again. hopefully the files now appear and you can continue
now when you get to step 5g step 5l, you will need to modify them to reflect the new path to the files so it would now look like this
step 5g. cp /sdcard/files/image/file/bbx /sbin/bbx
step 5l. /sbin/dd if=/sdcard/files/image/file/Verizon_System.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
and continue on with the guide

Here's a video Tutorial done by @TechBSwift to help if you have any questions on how this works.
https://m.youtube.com/watch?v=Oi-tuA_EIxA

Tested and working on my VZW Note 7 w/PH1 Firmware.
When you get to step 13, if you decide to go the route of using Busybox on Rails (free app) to install busybox then do the following (also see screenshot):
> Step 13a. If you're installing busybox on rails, it will ask you what you want to do and how you want to do it. Select "Cleanup & Install" and "Normal Method", then click "Next."
If you see "Custom" on screen while booting, don't worry, it doesn't indicate a tripped knox. It should go away after next reboot (after ./root.sh step).
You will probably get an annoying "Security notice" type notification after root (this is triggered by the root itself), if you want to gt rid of this download a root explorer (e.g. root explorer, root browser, etc.) and navigate to /system/app and delete the folder securitylogagent. Reboot and you should be good to go!

?
Sent from my SM-N930T using XDA-Developers mobile app

Xposed install instruction has been moved to :
http://forum.xda-developers.com/showthread.php?t=3461305
If you have any questions or comments about my instructions for xposed, please leave them in the link above.
Want to keep this thread here on topic with @OvrDriVE's new root method.
Thanks

Here we go again..... nice work guys.[emoji106]
Sent from my SM-N920T using Tapatalk

nice ..just have to wait for my replacemant and it's a GO GO GO
Sent from my SM-N930V using XDA-Developers mobile app

How long should you see a blinking curser at step 5L?
Been sitting there blinking for 5 minutes or so.

Wait another 10
Sent from my SM-N930T using XDA-Developers mobile app

nu2droid said:
How long should you see a blinking curser at step 5L?
Been sitting there blinking for 5 minutes or so.
Click to expand...
Click to collapse
It depends, but you should be looking at a roughly 10 minute wait time. Just be patient.
Don't do anything until the blinking cursor goes away.

gotcha, waiting....
just seemed long. thank you.

nu2droid said:
How long should you see a blinking curser at step 5L?
Been sitting there blinking for 5 minutes or so.
Click to expand...
Click to collapse
just wait. when it's done you will see something similar to what i have in instructions
sdcard speed can slow down or speed up that step

Hmmmm... root, fully functionality and doesn't trip Knox. I see myself trading my S7 Duos for a Samsung refurbished Note 7 in the near future!

OvrDriVE said:
just wait. when it's done you will see something similar to what i have in instructions
sdcard speed can slow down or speed up that step
Click to expand...
Click to collapse
Got it... I am good to go..
Setting up and trying everything..
thank you and all the others who helped bringing this to us...

nu2droid said:
Got it... I am good to go..
Setting up and trying everything..
thank you and all the others who helped bringing this to us...
Click to expand...
Click to collapse
Glad you got it working!
Have fun!

bajasur said:
Wait another 10
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
yea i would say like 10-12 mins also for everyone if you cant get past the very first part with adb and the files on the sd card and you know your sd card is formatted and did everything right its simply your sd card is carpped out in the sense of it shows in a computer but a phone wont notice it so throw that pos out and use diff one lmao other then that issue i had this **** is the easiest thing to do
---------- Post added 14th September 2016 at 12:09 AM ---------- Previous post was 13th September 2016 at 11:55 PM ----------
o also if the files dont show up on your phone when you hit apply update from sdcard dont worry their there just glitches out for some reason and doesnt show then only issue was the faulty sdcard i had which didnt show them either and then the new sdcard didnt as well so they may or may not pop up just continue

Once rooted, is it possible to implement the apps/features that Verizon removed and/or replaced when they decided to neuter our phone (Smart Manager, Force Touch, Samsung Cloud, Smart Caller ID, System Settings, etc.)? Personally, that's greatest impetus for me to root.

raneym305 said:
Once rooted, is it possible to implement the apps/features that Verizon removed and/or replaced when they decided to neuter our phone (Smart Manager, Force Touch, Samsung Cloud, Smart Caller ID, System Settings, etc.)? Personally, that's greatest impetus for me to root.
Click to expand...
Click to collapse
@OvrDriVE made Debloater.zip that you can flash using flashfire after you rooted for TMO .... he might be able to make for Verizon but might need to adjust the script little bit to compatible with Verizon device..... No more TMO bloatwares, less Samsung apps and knox free and still 0×00.[emoji4]
TWIST3D_N930T

Just to confirm.. its says doesnt trip knox.. does samsung pay still work?
Sent from my SM-N930V using Tapatalk