Related
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
This is my easy-rooter for the Thunderbolt. I do not personally have a thunderbolt but I have tested it and fixed as many problems as I could. As far as I'm aware this will only work with firmware versions lower than version 1.12.605.9.
If adb does not see your device try installing the htc sync drivers. If that doesn't wok install PDA.net. If it still does not register please post here. If you have a 64-bit version of windows replace the files in the rar with these
THIS IS A WINDOWS-ONLY PROGRAM. You must have windows or a windows VM to use this.
As always there is a small chance of bricking your phone.
DISCLAIMER: AndIRC is not affiliated with this program and by using it you agree that neither AndIRc nor myself is responsible for any damages caused by this program.
This provides all necessary files and gives you in-program instructions.
Please read this before using this.
Known bugs:
Sometimes you need to redo step 3. If the phone does not reboot on its own simply press the step 3 button again.
Issues:
The files take a long time to push. It could be anywhere from 3-10 minutes.
Once you have completed step one do not redo it for any reason! If it flashes only continue from step 2!
Credits:
Team AndIRC - for developing the root method found here
XDA - for giving me the chance to make programs like this
me - for making it
Donations:
Please donate to charity first and myself only if you want to. Please make donations in AndIRC's name as well as your own. You can donate here, to the Japan Relief Fund, or any other worthy charity.
since I just saw jcase's thing about my donation link (apparently I'm blind) here it is for those of you who wish to donate to me.
Downloads:
http://www.megaupload.com/?d=28H4U0QS
mirrors:
Instructions:
For those of you who can't follow or understand the directions in the program here is a pdf with instructions.
For anyone having problems getting steps 1 and 2 to work the first time through here's something to try.
lado44 said:
Hey man, I'm new so can't post in dev forum.
Your method worked for me - one thing I found. It was hanging at step 1 like some folks have reported, pushing the files (could see .ZIP on SD card), but would fail to reboot. This happened several times with Fast Boot enable under Settings>Applications. When I unchecked Fast Boot and re-ran Step 1 it worked first try. Couldn't tell you why or if just coincidence, but might help others.
Cheers.
Click to expand...
Click to collapse
For those of you who are interested in how this method works, here's the explanation. I will be focusing on what the program does,not user interaction so much except where necessary.
Push busybox, psneuter,and misc.img to /data/local/
Push PG05IMG_downgrade.zip to /sdcard and rename to PG05IMG.zip
chmod psneuter and busybox
execute psneuter
check the md5 hash of misc.img
flash misc.img to /dev/block/mmcblk0p17 if the hash is c88dd947eb3b36eec90503a3525ae0de
reboot into the bootloader
press power to enter bootloader and flash PG05IMG.zip (done by user)
once back in android:
remove PG05IMG.zip
push busybox, psneuter, and wpthis to /data/local
chmod all 3 files
run psneuter
run wpthis
push the engineering hboot(hbooteng.nb0) to /data/local/
check the md5 of the hboot file (it should be 6991368ee2deaf182048a3ed9d3c0fcb)
if it is flash hbooteng.nb0 to /dev/block/mmcblk0p18
push the PG05IMG.zip file to /sdcard
reboot into the bootloader
again press power and flash PG05IMG.zip (done by user)
push su, busybox, and psneuter to /data/local
chmod psneuter and busybox
run psneuter
mount /system as read/write (rw)
copy su to /system/xbin/su
chown and chmod su
install superuser and RomManager
Click to expand...
Click to collapse
I do recommend learning ADB as it is quite helpful but I realize that for some people that is a daunting task at first glance. I remember being a n00b and this will allow you to fully utilize your phone while still learning at your own pace on the side.
I am attaching just the updated exe.
Great idea showing what happens. Cool that you put something together for TBOLT owners, I just hope people will try and figure out what is going on when they use this.
After seeing a lot of issues people having with setting up adb I guess I should share this link... ADB For Dummies by AndroidSamurai
Even has an app to set everything up in the right spot.
This is a great thread on altering the android_winusb.inf for compatibility with Thunderbolt (adb driver).
<open>Can of Worms</open>
Thanks for the hard work.
One of the conditions for release was that I explain what happend. Hope this helps people out.
Nicely done. thanks for your hard work and knowledge. Now to get adb up and running finally.
You're welcome, and if the program functions properly you shouldn't need to setup adb beforehand as it comes with the necessary files for interaction. If it doesn't work properly try the debugging steps I posted in the OP and if that doesn't work setting up adb as a system command (adding the tools folder to PATH) should fix things.
^Thank you kind sir. I plan on giving this a spin tonight.
Ooking o walk a friend through this.later on tonight. And he camt boot into to the bootloader so im anxious to hear any feedback about this. If u guys dont mind please post anything you feel needs to be known about this, or just post that it rocks ass
Sent from my ADR6400L using XDA App
Hey guys, I didn't think about it when I created the thread but I want to have a bit of a poll here. If it works post here letting us know, and I'm fairly certain if there's a problem I'll hear about it so I don't think I need to say anything about posting them
Don't let dbzfanatic marginalize himself, don't forget some donations for him. (kinda hard to find his link in his post).
I hope it won't brick any phones. You're up on AP now - http://www.androidpolice.com/2011/0...en-tried-and-true-meets-new-and-blazing-fast/
I saw that. In my test group I had no reports of bricks, just random quirks which I have sense fixed (except those listed in the OP).
need to find an excuse to get off work early now...
Is firmware version the same as software number ? . My software number is 1.12.605.6 .
Yes it's the same, you should be fine to use this.
Looks awesome, but I'll still wait until all of the kinks have been worked out.
Since this uses the same method as manual root, it SHOULD continue to work until gingerbread.
awesome, cant wait to get outta work!
Does this wipe the phone like the manual adb does?
Yes, it's exactly the same method, just automated to make things easier.
BTW what do you mean "ADB needs to be setup as a system command"?
My ADB works properly and I can see the device so I assume that's the one I'd need to download and not the one that says "ADB need not be previously setup"?
Shamelessly stolen from another forum, editing is mine.
If someone gets the update, can you please do this before you accept it. and post the logcat.txt? Please this may help rooting.
How to get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
Code:
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
Code:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/
You should see a link in the file like
Code:
https://android.clients.google.com/u.../partner/*****
Click to expand...
Click to collapse
indeed, also for a good file manager to pull the zip, use estrongs its free lets you browse / just cant write to it (which isnt what we are looking to do)
great info. I remember seeing this process posted way back when, thanks for the refresher.
What if you have a mac though, w/o any boot camp either?
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
Credit to barnacles10 and lithid-cm
*NOTE: Anything in brackets is either description of what is happening or an action you need to perform; don't type in anything in brackets*
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Apparently some people had issues with the first link, so I uploaded it again. Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Alternate method:
For those that don't like using the terminal emulator, you can do it via adb:
navigate to your adb folder via commanda prompt, then issue the following commands:
adb remount
adb shell
cd /sdcard
ls [will list files, you should see bootsnd.sh]
sh bootsnd.sh
Like in the emulator, you will be returned with a # sign. Then place the audio file in the folder I specified. Just decided like posting an alt method. Enjoy.
Nice post I'm going to do this now!
Sent from my PC36100 using XDA Premium App
Well I do hope you enjoy it.
Excellent, trying this now!
Edit: Works great on CM7 7.0.2.1!!! Nice find!
.........at 8 am today someone poisons the coffee....do not drink the coffee. More instructions will follow.
Cordially,
Future Dwight
teh roxxorz said:
Well I do hope you enjoy it.
Click to expand...
Click to collapse
And I must say it has worked flawlessly.. I maintain a small network off friends rooted phones and this is one off the "hit" fixed so far everybody loves it. Thanks again for the help with this the other day..
Sent from my PC36100 using XDA Premium App
I really want this.. I just found this thread after searching and searching for an answer.. I just about gave up but I think I still my have a problem. My hboot version is 2.10 and dont think this will allow me to use pushboot.... any ideas
opps.. guess I should have read the whole post..... I am bout to give it a try
frikin awesome thanks a bunch.. I dont know what that little file did but it worked .. wooohoooooooooooo
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse
@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...
youdoofus said:
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. Download that file, place on your sdcard.
that download just shows up as a text file... am i doin it wrong?
Click to expand...
Click to collapse
The file should save as a .sh. If it doesn't show up as .sh when you are saving it, save it as all file types, and that should work as well.
If you double click it, it should prompt you with the "no program found...do you want to...blah blah" And it should show bootsound.sh
Click to expand...
Click to collapse
gReeNzZz said:
@teh roxxorz: Thanks a lot man. I had to search a longtime to find this. You're the man. Seems like CM7.02.1 doesn't have that bootsnd.sh file embedded. Maybe the latest stable has it. If I wasn't new to the forum I'd know how to hit you with a "Thank You"...
Click to expand...
Click to collapse
Well AOSP roms [i.e CM7] wasn't designed to have boot souns, so it probably won't be integrated [my speculation].
And if you ever want to "thank" anyone, at the bottom of every post, you'll see a "thanks" button, and then you have "thanked" them, and the user can see it.
Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App
chefrjd33 said:
Can't get this flashed. I tried to rename what I had downloaded from cyan's web site, Droid eye audio.zip, even tried to just flash it. A little help please
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Well if its a zip file. Extract the file, it should be an mp3 inside. Rename that file to android_auido [should have .mp3 extension already].
It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App
chefrjd33 said:
It launches rom manager and tells me its a operating system. Did I get the wrong file.
Sent from my ERIS ADR6200 using XDA App
Click to expand...
Click to collapse
Where are you opening the file that its making it open from rom manager?
teh roxxorz said:
Another user asked for this, and I helped him through it, so I decided to post it here so everyone can have access to it. I didn't create the file, just came across it one day being bored..I digress.
What you need to do to get a boot sound on CM7/AOSP is the following.
1. http://dl.dropbox.com/u/19699565/bootsnd.sh Download that file, place on your sdcard.
2. Take whatever sound you want and rename it to: android_audio.mp3 [needs to be mp3 format] and then place in your adb tools folder.
3. On your phone, open terminal emulator, and type in the following:
su [enter]
cd /sdcard [enter]
ls [to list all files, you should see bootsnd.sh]
sh bootsnd.sh [enter]
You won't see a confirmation, or message, it just runs, and returns you to a # sign.
From your computer, adb push the android_audio.mp3 to the /system/media folder, reboot, and you'll have a sound.
If you don't like / know how to use adb, using root explorer and placing the android_audio.mp3 in the system/media folder works just as well. Reboot, and enjoy your boot sound.
*NOTE*
If you flash / change roms, you'll have to re-run the process to enable the boot sound again. If you get tired of it / don't want it, you can use root explorer and delete the file.
Click to expand...
Click to collapse
Ok just tried this without using adb as I think its million times better to just use a ftp app and get this done in seconds. But I dont know why its not working. I check the name to make sure I wasnt putting in the .mp3 twice and for some reason it wont play the file. And its in MP3 format.
I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO
Or tell me what steps udid do.
Kings GB Destroyed EVO
cmurray77 said:
I had some that wouldn't play for some reason too. Try a different mp3 file and see id it work. If not did u get the bootsnd file placed on the root of sd card and pushed the file with adb. Or my preferred method terminal emulator.
Kings GB Destroyed EVO
Click to expand...
Click to collapse
Really well I actually tried the audio from the driod just to see but I try a couple more. Yeah the problem with using those they are more timely and both USB ports are beyond ****ed right lol. But I should just be able to do this over FTP. Was there anything similar to the ones that worked to the ones that did.
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
This may look complicated, but is super easy. If you don't feel comfortable using this method, you can use this automated tool (yes, it works on 4.5.141). It won't be as satisfying, or even feel good. You won't learn anything, but you will be rooted. Download tool here (link in OP is broken).
Pre-work:
1) Read the xda Atrix Beginners Guide (then read it again)! (Link)
2) Download and install 7zip. (Link)
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. (Link)
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
You can simply copy each command and paste in to the command prompt.
If you encounter any errors after entering a command, just ignore and keep going (assuming you entered the command properly).
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down until you see "fastboot".
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
17) Open a terminal emulator, then type "su" and hit enter. You should see "#" if you are rooted. Or, download Root Checker from the Play Store.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Note: If you experience problems with updating superuser after rooting, try going in to Manage Applications and clear Superuser data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Downloads:
My Atrix AFH Folder
*****
Thanksssss
Just want to show my appreciation. Your guide followed step by step worked flawlessly on my atrix. Ive been trying to root this darn thing for about a week and a half with no luck. found your guide and worked perfect first time around. Thanks..
David
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
upndwn4par said:
Having just purchased another Atrix that was running stock Gingerbread 2.3.6 (4.5.141), I was frustrated by the lack of a complete rooting guide and appropriate files. There is a guide in this forum (Link) which is based on an article from Android Advice (Link), but I noticed that both lack a lot of basic information for the inexperienced user. Also, the zip file available from Android Advice was missing a key file (Superuser!). So, I made a guide.
Remember to click THANKS if this guide helped you!
Pre-work:
1) Read the xda Atrix Noob Guide (then read it again)! Link
2) Download and install 7zip. Link
3) If they are not already installed on your PC, download and install the Atrix drivers for Windows. Link.
4) Download the attached files (sorry, had to break them in to two files due to forum size constraints). Create a new folder on your hard drive named "Android" (c:\Android). Extract both attached zip files to this folder (all the files need to be in "Android", not in a sub folder).
5) On your phone go to Settings, Applications, Development, then tick USB Debugging.
Notes:
Do not type quotes.
After each command hit enter.
Be mindful of spaces.
Work:
1) Attach your phone to the PC via USB. In the USB settings make sure USB Mass Storage is selected.
2) Reboot phone while holding volume down.
3) Press volume up to initiate fastboot.
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type "cd c:/android"
6) "fastboot.exe flash preinstall preinstall.img"
7) "fastboot.exe reboot"
8) Wait for phone to reboot.
9) "adb shell"
10) "/preinstall/dosu". If you get an error (I did), type "/preinstall/su"
11) "/bin/mount -o remount,rw /system"
12) cp /preinstall/su /system/bin/"
13) "chmod 6755 /system/bin/su"
14) "PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk"
15) Reboot phone.
16) On your phone go to your apps and make sure the Superuser icon is there. Open the app, go to settings, then update the SU binary.
My phone rebooted itself after step 11, so I had to re-open the adb shell.
I copied and pasted the text from the command prompt for reference (attached).
If I missed anything or have any errors, let me know and I will update the post.
Good luck!
Click to expand...
Click to collapse
RE super user pkg.
aksma said:
Thanks for the information. Just wanted to do this, and while reading the procedure, I found that there is no Superuser.apk in the attachments. Do I have to get it from some other place.
Thanks
Click to expand...
Click to collapse
Well for me what happen is down at the bottom he has two links for two of the files you need to zip. in one of those, there is a superuser file. When doing the cmd commands at the end you will end up installing the superuser. The best thing to do which really helped me was to download the command prompt text file, that way you can mimic exactly what you see. Hope this helps.
-David
Thanks David, I just started doing the same. Lets see how it goes.
good luck
aksma said:
Thanks David, I just started doing the same. Lets see how it goes.
Click to expand...
Click to collapse
no problem. Believe me i was in the same position. I must of tried rooting mine like 15 times to no avail ,then i found this thread and it worked.
Worked like a Champ!! Thanks David... Was quick and easy.. ..
excellent
aksma said:
Worked like a Champ!! Thanks David... Was quick and easy.. ..
Click to expand...
Click to collapse
Good deal. So glad i found this thread haha.
Glad I could help!
good one.
Thanks a lot
was so expected that this guide
Going to give it a try
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Thanks!
Rooted phone
dmacdog said:
I read through everything and think I have somewhat of a clue on what I need to do..LOL. Whatever the results I will post back and let you know. I have had my atrix since it was first released and have never had the time to root it as I cannot be without a phone couldn't take a chance.
I retire soon so hopefully will have more time to get invovled in things as this is a great forum.
Mac
Click to expand...
Click to collapse
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
thanks
that was cool!
very usefull!! thank you!
very useful
Sent from my MB860 using xda premium
condor7272 said:
that was cool!
Click to expand...
Click to collapse
Yes it is. Awesome feeling to look in your app drawer and see this:
THANKS!!
upndwn4par said:
Welcome to the wonderful world of messing with your phone!
You really can't harm your phone trying to root it. If you type a command wrong, just re-type it. No worries. There are lots of good guides out there for whatever you want to do. The noob guide (linked on the first page) is a great place to start. And there are plenty of members willing to help.
Let us know how things go!
Click to expand...
Click to collapse
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
1iJakk said:
followed the directions and am now rooted!!
next to look for boot load unlock - not sure why but 'im gonna figure it out - and then an ics rom or wait for the q3 'official' motorola release . . . decisions
Click to expand...
Click to collapse
Don't unlock your bootloader if you think you will want official Moto ICS update (major hard brick risk).