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
Related
http://www.youtube.com/watch?v=b7TbLlzFzsU
Wow why is it so hard to embed a Youtube video on here
The startup sound of the HTC Evo 4G is one of the few things I find annoying about the phone. The fact that even plugging headphones into the Evo does not stop the sound is lame. Here's how you can disable it.
Fast and Easy Way for Froyo:
Root your device, use a File Browser (like Root Explorer) and rename the /system/customize/resource/SPC_animation_final.mp3 file.
Requirements
Your phone must be rooted with Toast's method
You must be familiar with ADB and Toast's custom recovery.
If you need more information on Toast's root and recovery, read this {tutorial} how to root \0/ - xda-developers
Disable Startup Sound
Connect your Evo to your computer thru usb and Enable USB debugging on the Evo.
Reboot into recovery. In a commandline do: adb reboot recovery
Start toast's custom recovery by running recovery-windows.bat as Administrator (or the equivalent for Linux and Mac). Do this by right-clicking on the recovery-windows.BAT file and choose Run as Administrator.
Use a different commandline and do: adb shell
Mount the system partition by doing: mount /system
Skip to #9 if you are on 2.2 Froyo
Go into first folder: cd /system/media
rename the mp3 file: mv android_audio.mp3 android_audio.mp3.bak
Go into 2nd director: cd /system/customize/resource
Rename the mp3 file: mv SPC_animation_final.mp3 SPC_animation_final.mp3.bak
You're done! Reboot: reboot
The Making Of
{
"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"
}
Physical split screen.
My "tripod"
The stage
Nice one pingpongboss! Come to think of it, modders can tailor made (if they haven't done so. sorry if they have. i'm a n00b.) this procedure to load their own custom sounds and animation during startup.
joackie27 said:
Nice one pingpongboss! Come to think of it, modders can tailor made (if they haven't done so. sorry if they have. i'm a n00b.) this procedure to load their own custom sounds and animation during startup.
Click to expand...
Click to collapse
Yup, that's right. I think BuglessBeast does that for the Moto Droid. You can also replace these files with your own files manually.
Thanks for the howto! Definitely glad to remove the sound.
thanks! Naive question, though. Why can't you just to rename the files directly in the evo using a file manager? I thought i'd ask before i try and mess things up .
bkofman said:
thanks! Naive question, though. Why can't you just to rename the files directly in the evo using a file manager? I thought i'd ask before i try and mess things up .
Click to expand...
Click to collapse
That is because when you boot into android, /system becomes NAND locked. So you cannot write anything in /system
You can only write to /system in recovery mode.
Does anyone have the stock sprint start up sound SPC_animation_final.mp3 that can upload it here?
I flashed Fresh 0.2 rom and I don't like the startup sound that goes FRESHHHHHHHH. =/
Thank you pingpongboss! It was driving me crazy!
Ketty said:
Does anyone have the stock sprint start up sound SPC_animation_final.mp3 that can upload it here?
I flashed Fresh 0.2 rom and I don't like the startup sound that goes FRESHHHHHHHH. =/
Click to expand...
Click to collapse
Haha I was really scared the first time I heard that sound
yeah so how do you enable it if it's gone???
You can also set your phone sound profile to silent before you shut off your phone and it Disables the HTC Evo 4G Startup Sound.
hotboy8628 said:
yeah so how do you enable it if it's gone???
Click to expand...
Click to collapse
If you did it yourself, then just redo all the steps, but rename all the files back to .mp3.
If your Rom cane with no sounds then you can probably stick your own mp3 into the right folder.
pingpongboss said:
If you did it yourself, then just redo all the steps, but rename all the files back to .mp3.
If your Rom cane with no sounds then you can probably stick your own mp3 into the right folder.
Click to expand...
Click to collapse
it said it was read only when i go to the folder
is this procedure different for froyo?
i get to...
6. Go into first folder: cd /system/media
7. rename the mp3 file: mv android_audio.mp3 android_audio.mp3.bak
Click to expand...
Click to collapse
and the android_audio.mp3 file doesn't exist?
cjohnson said:
is this procedure different for froyo?
i get to...
and the android_audio.mp3 file doesn't exist?
Click to expand...
Click to collapse
Its very well possible that they may have changed the location of the bootup sound. Is the SPC_animation_final.mp3 still there? And does sound go away when you rename that.
Code:
C:\android-sdk-windows\tools>adb reboot recovery
C:\android-sdk-windows\tools>adb shell
/ # mount /system
mount /system
/ # cd /system/media
cd /system/media
/system/media # mv android_audio.mp3 android_audio.mp3.bak
mv android_audio.mp3 android_audio.mp3.bak
mv: cannot rename 'android_audio.mp3': No such file or directory
/system/media # ls
ls
audio
/system/media # find / -name android_audio.mp3
find / -name android_audio.mp3
/system/media # find / -name SPC_animation_final.mp3
find / -name SPC_animation_final.mp3
/system/customize/resource/SPC_animation_final.mp3
/system/media # cd /system/customize/resource
/system/customize/resource # mv SPC_animation_final.mp3 SPC_animation_final.mp3.bak
mv SPC_animation_final.mp3 SPC_animation_final.mp3.bak
/system/customize/resource # ls
ls
BigBen.jpg htc_wallpaper_small_12.jpg
CCInfo.txt htc_wallpaper_small_13.jpg
Colosseum.jpg htc_wallpaper_small_14.jpg
EiffelTower.jpg htc_wallpaper_small_15.jpg
SPC_animation_final.mp3.bak htc_wallpaper_small_16.jpg
SPC_wallpaper.jpg htc_wallpaper_small_17.jpg
StatueOfLiberty.jpg htc_wallpaper_small_18.jpg
bootanimation.zip htc_wallpaper_small_19.jpg
htc_wallpaper_01.jpg htc_wallpaper_small_20.jpg
htc_wallpaper_02.jpg htc_wallpaper_small_21.jpg
htc_wallpaper_03.jpg htc_wallpaper_small_22.jpg
htc_wallpaper_04.jpg m1b586a02.jpg
htc_wallpaper_05.jpg m2dcca705.jpg
htc_wallpaper_06.jpg m43a4ec7b.jpg
htc_wallpaper_07.jpg m43b340e3.jpg
htc_wallpaper_08.jpg m4d5e5f0e.jpg
htc_wallpaper_09.jpg m512d806c.jpg
htc_wallpaper_10.jpg m53b5efe7.jpg
htc_wallpaper_11.jpg m6f42e22c.jpg
htc_wallpaper_12.jpg mbd5dc6f8.jpg
htc_wallpaper_13.jpg mc8a1ff6b.jpg
htc_wallpaper_14.jpg md32a3a14.jpg
htc_wallpaper_15.jpg mdcdc890d.jpg
htc_wallpaper_16.jpg mfac50f3a.jpg
htc_wallpaper_17.jpg mfca3085e.jpg
htc_wallpaper_18.jpg resource
htc_wallpaper_19.jpg s1b586a02.jpg
htc_wallpaper_20.jpg s2dcca705.jpg
htc_wallpaper_21.jpg s43a4ec7b.jpg
htc_wallpaper_22.jpg s43b340e3.jpg
htc_wallpaper_small_01.jpg s4d5e5f0e.jpg
htc_wallpaper_small_02.jpg s512d806c.jpg
htc_wallpaper_small_03.jpg s53b5efe7.jpg
htc_wallpaper_small_04.jpg s6f42e22c.jpg
htc_wallpaper_small_05.jpg sbd5dc6f8.jpg
htc_wallpaper_small_06.jpg sc8a1ff6b.jpg
htc_wallpaper_small_07.jpg sd32a3a14.jpg
htc_wallpaper_small_08.jpg sdcdc890d.jpg
htc_wallpaper_small_09.jpg sfac50f3a.jpg
htc_wallpaper_small_10.jpg sfca3085e.jpg
htc_wallpaper_small_11.jpg
/system/customize/resource #
seems as though they did away with "android_audio.mp3" in froyo on the evo. if you skip steps 6 and 7 (and the bit about toast's recovery in my case since i have amon_ra's installed) everything will work fine.
I would just like to add how I did it.
I rooted using another method but I found a simpler way that works on the EVO 2.2. I downloaded Root Explorer (paid app) for removing bloatware, but I used it to navigate to /system/customize/resource just find SPC_animation_final.mp3 and add .bak to the end of that.
Done and done.
Thanks for the info on which file it was!
chjade84 said:
I would just like to add how I did it.
I rooted using another method but I found a simpler way that works on the EVO 2.2. I downloaded Root Explorer (paid app) for removing bloatware, but I used it to navigate to /system/customize/resource just find SPC_animation_final.mp3 and add .bak to the end of that.
Done and done.
Thanks for the info on which file it was!
Click to expand...
Click to collapse
Is there any free application that can do this? I don't see the directory when I use ES File Explorer. I'm guessing it is hidden somehow?
edit: Nevermind, I found it with ES. No file manager I've tried will allow me to edit the file. What is Root Explorer doing that is so special? Just giving itself superuser? Can't we do that manually?
edit2: I did it via ADB but I'm still wondering the answer to my question above. Also, has anyone noticed if it takes longer to boot? It seems to sit at the white screen for longer than before. Maybe it's spending time looking for the mp3 file before on? Or maybe it's just my imagination.
Minjin said:
Is there any free application that can do this? I don't see the directory when I use ES File Explorer. I'm guessing it is hidden somehow?
edit: Nevermind, I found it with ES. No file manager I've tried will allow me to edit the file. What is Root Explorer doing that is so special? Just giving itself superuser? Can't we do that manually?
edit2: I did it via ADB but I'm still wondering the answer to my question above. Also, has anyone noticed if it takes longer to boot? It seems to sit at the white screen for longer than before. Maybe it's spending time looking for the mp3 file before on? Or maybe it's just my imagination.
Click to expand...
Click to collapse
Sorry for the long delay but it looks like you've figured it out.
IDK what makes root explorer do what it does, but in order to edit anything you have to click the button near the top (once you are in the directory you are working in) that says 'Mount R/W' to make the files read/write instead of read/only. It locks the files as read only by default.
I haven't noticed any longer boot times or anything on mine... dunno.
Blah
This sounds to complicated just turn your volume down before you shut it down.
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
INFO
This fix/hack mounts second ext3 partition of your EXTERNAL SD card at startup and binds /data/data and /data/dalvik-cache to it. This will give you ~1400 Quadrant score on the stock ROM with AT&T bloatware.
This fix/hack is based on the anomalous3 info posted here
anomalous3 said:
An explanation of how this was done:
When looking through the init.rc, I realized that there was only one thing running as root that could safely be replaced; the boot logo player. So, all this does is replace the boot logo player with a script that calls userinit.sh from /data/local and then calls the (now renamed) bootlogo player for those of you who want that nifty startup screen
A super simple (and slightly dirty) hack but I figured it might come in handy for those of us who are impatient and would like to do our own tweaks.
Click to expand...
Click to collapse
PREREQUISITES
1. This guide was tested on complete STOCK ROM. If you need to revert use Odin3 One-Click Downloader
2. You will need root on your device. [How To] Root
3. Make sure you have latest busybox (I have v1.17.1), search market for "busybox" or use this qrcode:
{
"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"
}
4. You should have adb working until someone will help me figuring out how to pack in handy update.zip
5. You need sdcard with first partition fat32 and second partition ext3. I use 6.5Gb fat and 1.5Gb ext3 (I never tested, but it was mentioned in Mimocan thread DO NOT CREATE BIGGER THAN 1.9Gb EXT PARTITION)
HOW-TO
Step -1. I strongly advise to Backup your ROM (Use Rom Manager)
Step 1. Download and Unpack attached lagfix.zip
Step 2. Copy into root of Internal sdcard or push files using adb:
Code:
adb push playlogos1 /sdcard
adb push userinit.sh /sdcard
Step 3. Backup stock boot logo using adb:
Code:
adb pull /system/bin/playlogos1 playlogos1.bak
Step 4. ADB shell to device and became a root
Code:
adb shell
$ su
#
Step 5. Remount root filesystem as rw
Code:
busybox mount -o remount,rw -t rootfs /
Someone please advise if this step is necessary
Step 6. Rename stock boot logo:
Code:
mv /system/bin/playlogos1 /system/bin/playlogosnow
Step 7. Copy playlogos1 and userinit.sh and fix permissions:
Code:
cp /sdcard/playlogos1 /system/bin/playlogos1
cp /sdcard/userinit.sh /system/bin/userinit.sh
chmod 755 /system/bin/playlogos1
chmod 755 /system/bin/userinit.sh
Step 8. Remount root filesystem as ro
Code:
busybox mount -o remount,ro -t rootfs /
Step 9. Reboot and verify fix:
Code:
$ su
# ls /sd-ext
data
dalvik-cache
TROUBLESHOOTING
- If you do not have /sd-ext after reboot - script is not working
- If content of /sd-ext is empty I bet you are using old busybox
REVERT FIX
Note: Due to userinit script, I have to play with it in order to revert script changes. Will do it this weekend.
Code:
adb shell
$ su
busybox mount -o remount,rw -t rootfs /
cd /system/bin/
rm playlogos1
mv /system/bin/playlogosnow /system/bin/playlogos1
busybox mount -o remount,ro -t rootfs /
Thanks to everyone involved including, but not limited to: designgears, Koush, anomalous3 and NukaCola
Change log:
06/08/2010 Added revert step
06/08/2010 Initial release
Okay, am i the only person having problems creating partitions for sd on ubuntu everytime i try it says card damaged error.
Gparted boot disk works for me....
Does this script have shutdown scripts in it or no? I guess it is just like the Vibrant script?
Is there also a 130MB limit for apps like in the other fix?
Any other gotchas?
mykenyc said:
Okay, am i the only person having problems creating partitions for sd on ubuntu everytime i try it says card damaged error.
Click to expand...
Click to collapse
Hm... I never did this way but it should work.
Try to do so with ROM Manager:
Choose Partition SD card.
Choose your ext size (I suggest 512Mb)
Choose swap as 0.
Let me know if it works for you.
I used parted to create fat and ext2 and then upgraded to ext3 under ubuntu.
alphadog00 said:
Does this script have shutdown scripts in it or no? I guess it is just like the Vibrant script?
Is there also a 130MB limit for apps like in the other fix?
Any other gotchas?
Click to expand...
Click to collapse
All the script do is injects call to userinit and then call usual boot logo player.
userinit provided is from justanothercrowd work or even from app2sd earlier.
It is completely uncanged from the vibrant version and it looks great.
This script is:
1. /sd-ext if needed
2. mounts mmcblk1p2 to it
3. if not here binds /data/data as /sd-ext/data
4. if not here binds /data/dalvik-cacheas /sd-ext/dalvik-cache
magic done.
Also, there is only possible 2gb limit (mentioned in mimocan thread at modaco, I never tried to create more then 2Gb)
XorZone said:
All the script do is injects call to userinit and then call usual boot logo player.
userinit provided is from justanothercrowd work or even from app2sd earlier.
It is completely uncanged from the vibrant version and it looks great.
This script is:
1. /sd-ext if needed
2. mounts mmcblk1p2 to it
3. if not here binds /data/data as /sd-ext/data
4. if not here binds /data/dalvik-cacheas /sd-ext/dalvik-cache
magic done.
Also, there is only possible 2gb limit (mentioned in mimocan thread at modaco, I never tried to create more then 2Gb)
Click to expand...
Click to collapse
I was reading the last page of the vibrant thread, and he mentioned still wanting to add unmount commands and such for shutdown.
I am assuming that there is not mic issue as in the other version?
Has anyone tested yet with real DB IO? The other fix had boosted Quadrant scores, but still had terrible.
Just curious if anyone did any real world tests yet.
Thanks i appreciate everyone work but i give up on this lag fix stuff/gps fix/or antenna issues that's not working for me. I'm just going to get the blackberry torch, and when Samsung update everything or we get more development i will be back. And i will use my second line to buy another captivate. So be back soon my android brothers happy hacking!
alphadog00 said:
I was reading the last page of the vibrant thread, and he mentioned still wanting to add unmount commands and such for shutdown.
I am assuming that there is not mic issue as in the other version?
Has anyone tested yet with real DB IO? The other fix had boosted Quadrant scores, but still had terrible.
Just curious if anyone did any real world tests yet.
Click to expand...
Click to collapse
I will update it as soon as they will add more info or update a script.
I didn't and probably will not do any "realworld" testing as I fill it is boosted and better.
It's up to you if to use it.
No mic problems because kernel is stock.
mykenyc said:
Thanks i appreciate everyone work but i give up on this lag fix stuff/gps fix/or antenna issues that's not working for me. I'm just going to get the blackberry torch, and when Samsung update everything or we get more development i will be back. And i will use my second line to buy another captivate. So be back soon my android brothers happy hacking!
Click to expand...
Click to collapse
Well. I do not have any issues with GPS/MIC and lag now.
Pretty happy with the device. Only kernel source problem annoying, but never thought to regret the deal.
It's your decision. Farewell. Take it easy, there are more important things then cell phones
XorZone said:
Well. I do not have any issues with GPS/MIC and lag now.
Pretty happy with the device. Only kernel source problem annoying, but never thought to regret the deal.
It's your decision. Farewell. Take it easy, there are more important things then cell phones
Click to expand...
Click to collapse
No i'm not bashing this, trust me cell phones not my life. But for me this is my second captivate my antenna is my biggest problem it goes up and down like wild fire trying to be put out. My dad own a BB on ATT and his bars never go crazy in our apartment. I was trying to hold out to see if we would have a fix by now but its effecting my livelihood, and once that happens then i got to make a change. I don't get the lag but i do get times where text messages literally take (upon power on) 20 minutes to shoot in, i tried different sims and this my second captivate like i said. But i'm not going to hijack your thread just wanted to say i appreciate the attempts.
but hey if something happens before the torch come out i will def stay...
good luck bro
Has anyone confirmed voice quality still good after this mod?
Sent from my SAMSUNG-SGH-I897 using XDA App
larry996 said:
Has anyone confirmed voice quality still good after this mod?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I don't see any reason why there would be. You're still using the stock kernel. All the voice quality problems come from building a custom kernel. The kernels we were given by Samsung weren't entirely proper, so we're seeing some errors...
Fortune090 said:
I don't see any reason why there would be. You're still using the stock kernel. All the voice quality problems come from building a custom kernel. The kernels we were given by Samsung weren't entirely proper, so we're seeing some errors...
Click to expand...
Click to collapse
Thx for help with elaboration.
Btw, did you successfully applied fix through this guide?
I just applied your fix and I was using a stock rom. Everything went ok and it does feel quicker. I am getting some kernel crashes but only really when you reboot the phone. I would write what the quadrant score is but it never finishes the tests, it sticks on part 3 of the I/O tests.
Just did this and got a Quadrant score of 1439!
Thank youuu!!!!
I had a ton of trouble with apps f/c-ing, but reinstalls help.
To all attempting: Just flash to stock and save yourself the trouble.
You won't have to deal with all the trouble of your apps not working, and you can just reinstall them later. I had to do a ROM recovery to remove launcher pro's permissions so I wouldn't get stuck in a constant f/c loop...
BUT! It's working now! Many thanks!!
Nevermind I just let quadrant run for a while and it finished. Got a score of 1389! But I am still getting these kernel crashes. Specifically process com.google.process.gapps
illspyder said:
I just applied your fix and I was using a stock rom. Everything went ok and it does feel quicker. I am getting some kernel crashes but only really when you reboot the phone. I would write what the quadrant score is but it never finishes the tests, it sticks on part 3 of the I/O tests.
Click to expand...
Click to collapse
Sounds strange.
I'll do number of reboots to verify.
Could you check under linux (ubuntu or other) that you ext is ext3 and second check it with e2fsck if it's healthy
Fortune090 said:
Just did this and got a Quadrant score of 1439!
BUT! It's working now! Many thanks!!
Click to expand...
Click to collapse
Glad to hear!
mykenyc said:
No i'm not bashing this, trust me cell phones not my life. But for me this is my second captivate my antenna is my biggest problem it goes up and down like wild fire trying to be put out. My dad own a BB on ATT and his bars never go crazy in our apartment. I was trying to hold out to see if we would have a fix by now but its effecting my livelihood, and once that happens then i got to make a change. I don't get the lag but i do get times where text messages literally take (upon power on) 20 minutes to shoot in, i tried different sims and this my second captivate like i said. But i'm not going to hijack your thread just wanted to say i appreciate the attempts.
but hey if something happens before the torch come out i will def stay...
good luck bro
Click to expand...
Click to collapse
bars mean nothing. I could have 0 bars on my captivate and still hold a call better than when I had an iPhone 4. If you are constantly dropping calls on your captivate and not on your dad's Blackberry, then you should be worried, otherwise, you should not.
Either follow this lag fix or the NAND lag fix (http://forum.xda-developers.com/showthread.php?t=737829), and it will solve most of your problems
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
Hi guys.
First of all, all credits go to @ZeroPDA. The processo is from him. Im just making this tut for everyone to see.
Requirements - root
1-download root explorer and terminal emulator
2-download universal init.d
3-go in the universal init.d APP and turn it on.
4- go in root explorer, go to etc/init.d and create a filé named deviceidle. Note that you have to give all permissionários to etc folder and init.d folder in order to be allowed to creat the file.
5-open the file that you just created, deviceidle, with a text editor, and write the line "dumpsys deviceidle disable". Save. Nós erase everything else from the folder init.d.
VERY IMPORTANT - BEFORE THE BELOW 6 STEP, GO TO SETTINGS, ADMIN PERMISSIONS, AUTO INICIALIZE APPS AT BOOT, AMD GIVE PERMISSION TO UNISERSAL iNIT.D
6-reboot your phone.
7-please allow some seconds when it boots, to see the message that universal init.d has been granted with supersu permissionários. This may take 30 seconds after boot.
8-when you see the message, go in terminal emulator and type "su"
9-type "dumpsys deviceidle enabled". If it returns 0 your good to go. If it returns 1 you've done something wrong.
Gonna include a video recorded imeadiatly after boot
New video with steps
https://youtu.be/-FJ6YsVJgxM
Did not work, getting 1 and I redid and followed every step.
Thank you for recognizing my efforts. I decided to make it even more clearer with reference to the apps
Requirements - root
Download root explorer and Terminal Emulator for Android
Download Universal Init.d
Go in the Universal init.d app and turn it on.
Go in root explorer, go to /etc/init.d and create a file named deviceidle with permissions rw- --- --- (Only Owner can Read and Write).
Open the file that you just created, deviceidle, with a text editor, and write the line dumpsys deviceidle disable. Save. You can delete everything else from the folder /etc/init.d Just leave one file deviceidle there (You can also leave 99SuperSUDaemon if it is present)
Reboot your phone.
Please allow some seconds when it boots, to see the message that Universal init.d has been granted with supersu permissions. This may take 30 seconds after boot.
After seeing the message, go to the terminal emulator and type "su"
Type "dumpsys deviceidle enabled". If it returns 0 your good to go. If it returns 1 you've done something wrong.
New vídeo with the steps
https://youtu.be/-FJ6YsVJgxM
I did these exact steps, does still not work..
MFRCNS said:
I did these exact steps, does still not work..
Click to expand...
Click to collapse
do it again. sometimes you have to check the permissions again. at first, with me, i had to check them twice. also, put all permissions in the file created. when yoiu reboot, please allow a few seconds till the message "universal init.d has been granted su privileges"
I writed a new step. its very importan and might be the reason some people arent being sucessfull with this.
before you reboot the phone, GO TO SETTINGS, ADMIN PERMISSIONS, AUTO INICIALIZE APPS AT BOOT, AnD GIVE PERMISSION TO UNISERSAL iNIT.D
For some reason this method does not work for me
I donwload and install everything, but when i try to go through the steps this is what happens:
I open universal init.d and nothing happens , no way to turn it on!
Then, in Root Browser i have no init.d folder inside etc and if i try to create it, the browser gets stuck and no folder is created!!! Please Help
maurosch said:
For some reason this method does not work for me
if i try to create it, the browser gets stuck and no folder is created!!! Please Help
Click to expand...
Click to collapse
Probably either you are not rooted or not given root permissions.
ZeroPDA said:
Probably either you are not rooted or not given root permissions.
Click to expand...
Click to collapse
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
What kind of notification doesn't work? GMail, WhatsApp, Viber? All of them?
Sent from my HUAWEI M2-A01L using Tapatalk
maurosch said:
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
Click to expand...
Click to collapse
give permissions to etc folder and also to init.d folder. when you create the deviceidle file, before you write anything, save the file without nothing and give also full permissions to that file
nosidefcp said:
give permissions to etc folder and also to init.d folder. when you create the deviceidle file, before you write anything, save the file without nothing and give also full permissions to that file
Click to expand...
Click to collapse
i have been usinf this method for awhile, and has worked perfectly.
but since i am on a different firmware now, i had to redo it, and yes it still works...
BUT, only for some time and then it reverts back. (so when checking in Terminal it reads 0, and stays like that for an hour or two, and then automatically turns to 1)
Sent from my HUAWEI NXT-AL10 using XDA Labs
I tried it the first time did not work. Then I opened the Universal Init app and it showed ON and below were the scripts, so I went to SuperSu app to make sure Init app gained permissions, and that was the problem it didn't work in the beginning because did not gain Root. So, went back to the Init app and click the TEST button at the bottom, and there appeared the SuperSu window asking for Root permissions, so, granted permissions, rebooted the phone and opened terminal to make sure it worked this time. SUCCESS, it showed 0 this time. I don't know if it changes back to 1 like someone mentioned above, but I'll check and come back here. Good luck
maurosch said:
thank you for your reply. I am rooted and permissions for the etc folder are 777 all clicked!!!i want to do this cause i really miss notifications!!!! at first they work, but after a while i have to reboot the phone to start getting them again!!!
Click to expand...
Click to collapse
Freeze phone manager. I'm not sure how people are reporting success with this when doze is a feature for all Marshmallow devices and none have this issue. I have no doubt that the problem is with phone manager and I'm sure if we were able to decompile the file properly there would already be a solution.
On B321 after selecting keep wifi on during sleep and keep mobile data on during sleep I have zero notification issues. I don't even have to move any apps to system/app anymore.
The problem is that there is no B321 for L29 officially. Any try to flash B321 to L29 is connected with risk to brick the phone. And there is no reliable guidance how to return back to B180 from B321 if someone doesn't like it.
ajsmsg78 said:
On B321 after selecting keep wifi on during sleep and keep mobile data on during sleep I have zero notification issues. I don't even have to move any apps to system/app anymore.
Click to expand...
Click to collapse
I couldnt find "keep mobile data on during sleep" option. Where is it?
hi my friend
testing this tip
for lock app after sleep facebook line email etc. show noti. but drain batt'
unlock after sleep not show noti. but save batt.
making by wipe down lock frist wipe down unlock second make in recent app
looking at image
{
"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"
}
b180 fixed the gmail notification issue for me, it is already stated in the official change log that it fixes gmail notification.
That's maybe why the report for b180 drains more battery, doze is half disabled on b180 but so far the notification is working like it should.
Hey guys, recently a member from Discord channel (ikkun) showed me steps on how to root Phoenix OS by just placing the su binary in the system folder. This method is so much easier and convenient than replacing the system.img, that it should be the main way to root your Phoenix OS installation.
Advantages:
No need to wait to download and extract a 500MB system.img. Instead, download a 5MB .zip file
No need to do a fresh install. You can root an existing installation without removing all your data.
Play store and Google Calendar sync work
Tested and works with:
v2.2.0 64-bit
v2.2.1 64-bit
v2.5.0 64-bit
v2.5.3.64 64-bit
v2.5.7.348 64-bit (Tested myself)
(Probably works on your system too. Why not test it and post your results below?)
Instructions:
Download and extract the .zip file. For the purposes of the tutorial, I'm going to assume that you extract it in the Download folder and rename the SuperSU folder to su. Inside su, you should see META-INF, x64, x86, etc folders.
{
"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"
}
Open the terminal by pressing Alt+F1
If you have Phoenix OS 32-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x86/[B]su.pie[/B] su
chmod 4751 su
su --install
su --daemon
If you have Phoenix OS 64-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x64/[B]su[/B] [B].[/B]
chmod 4751 su
su --install
su --daemon
This screenshot is for 64-bit:
Note 1:
If after typing in the mv su su.orig command, you get an error saying:
mv: rename su to su.orig: No such file or directory
Click to expand...
Click to collapse
That means your Phoenix OS installation does not come with the su binary. Skip the mv command and proceed to the next step since there is nothing to make a backup of.
I usually install my Phoenix OS using the .exe installer and always see the su file in that folder during the rooting process so I never see this error. It was never clear to me why people are missing the su binary, but my observations tell me it could be because people are installing it using the ISO file or using 32-bit. I never had the opportunity to test this out, but if you have this error, please post your Phoenix OS version, architecture, and installation method.
Click to expand...
Click to collapse
Note 2:
Make sure you type in the commands exactly as provided. I saw other people were having trouble because they typed in the command incorrectly; they were missing a period after a space. It should be with a period and a space after the command (if you're rooting x64):
Code:
cp /sdcard/Download/su/x64/su [B].[/B]
and not:
Code:
cp /sdcard/Download/su/x64/su
The dot simply tells the cp command to place the file in the working directory (which was set earlier by the cd /system/xbin command). Alternatively, you can replace the dot with the current directory, the new command being:
Code:
cp /sdcard/Download/su/x64/su /system/xbin
It's just easier to type a dot then type out the whole directory, especially considering the fact that you can't copy-paste in the terminal (as far as I know, could be wrong)
Click to expand...
Click to collapse
Close the console by pressing Alt+F7. (If you have trouble exiting the console, post below with your Phoenix OS version and architecture. Then, try pressing Ctrl+Alt+F7)
Phoenix OS might crash and restart. Using the File Manager, go to the Download folder. Navigate to su>common> and install Superuser.apk
Launch SuperSU app from the app drawer. Press Continue, then select Normal to update the binary normally. Exit out of the app after the update is successful.
Launch Security app from the app drawer. Click AutoRun.
Toggle SuperSU to enable it so that it can automatically run when other apps request Superuser access. Exit out of the app.
History:
Added notes for common errors people were having
Added another keystroke to exit console (Ctrl+Alt+F7)
Added screenshots. Removed unnecessary steps. Fixed grammar mistakes.
These instructions were posted in the Phoenix OS Discord Server by ikkun. Thanks to Chainfire for SuperSU.
Instructions ported from tutorial Installing SuperSU on Remix OS 2.0
Attached zip file in case their website is down.
Thanks, it works
jamarita said:
Thanks, it works
Click to expand...
Click to collapse
Thank you for the confirmation! What device do you have and what GPU does it come with?
Does not work on hp 655 32 bit
lomax84 said:
Does not work on hp 655 32 bit
Click to expand...
Click to collapse
First of all, what kind of a computer is an "hp 655"? Second, can you provide more details to what exactly doesn't work? What step are you failing at?
Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.
ariadnejro said:
Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.
Click to expand...
Click to collapse
Awesome, thanks for letting us know!
The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.
This method still causing the Play Services sync problems with Gmail, etc. Any fix?
mic1000s said:
The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.
Click to expand...
Click to collapse
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
jbardi said:
This method still causing the Play Services sync problems with Gmail, etc. Any fix?
Click to expand...
Click to collapse
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.
It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2
mic1000s said:
It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2
Click to expand...
Click to collapse
Oh okay, thank you for the guide, I hope others find it useful. The other reply was to another user, not to you. Phoenix OS has a Gmail sync issue. So if you try to install and sign into the Gmail app, you will not be able to synchronize your mail. You actually do have a synchronization issue, it's just that you haven't experienced it yet because you haven't tried using the Gmail app.
meanhacker said:
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.
Click to expand...
Click to collapse
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS
Seanie280672 said:
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS
Click to expand...
Click to collapse
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire
meanhacker said:
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire
Click to expand...
Click to collapse
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.
Seanie280672 said:
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.
Click to expand...
Click to collapse
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps
meanhacker said:
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps
Click to expand...
Click to collapse
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.
Seanie280672 said:
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.
Click to expand...
Click to collapse
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.
meanhacker said:
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.
Click to expand...
Click to collapse
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.
Seanie280672 said:
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.
Click to expand...
Click to collapse
I'm glad you got it to work! I will update the OP with the new information. What made it work? Was it the fact that you could now escape the terminal or letting Superuser in AutoRun?