Related
This is a follow-up of the thread " [Q] can't locate /mnt/sdcard/ ". That thread is now locked.
I was able to get ES File Explorer to display /mnt/ in the path to /sdcard/. But now, while in /mnt/sdcard/, I do not see /system/bin/. The routines that root the A100 require access to /system/xbin/.
I looked in ES File Explorer - Settings - File Settings - for an obvious solution but found none. "Show Hidden Files" is already checked.
I suspect that maybe the lines entered via the command prompt (like /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`' or /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`') will somehow unlock or allow access to /system/xbin/ but I'm not sure. I guess I could just plow ahead and see what happens but I much prefer to anticipate and prevent problems beforehand rather than try to fix things after I've screwed it up.
So 3 questions:
1. Will the command line entries automatically be able to write to /system/xbin/?
2. If yes, will I then be able to read and write to /system/xbin/ using ES File Explorer?
3. If not, how do I gain access to /system/xbin/?
I think your trying to make things more complicated for yourself than what they really are, of course it helps to know a little Linux when doing things like this.
1. Will the command line entries automatically be able to write to /system/xbin/?
Yes, that's what the mount -o remount,rw /system does in the command you run.
2. If yes, will I then be able to read and write to /system/xbin/ using ES File Explorer?
No, this is not needed as the commands handle this for you.
3. If not, how do I gain access to /system/xbin/?
You don't... just run the commands for rooting via the terminal and everything is done for you.
The ONLY thing you need to do with ES is to extract the downloaded su file and put the su file itself in /mnt/sdcard. Once you've done that, open the terminal emulator and run those 3 commands.
I do tend to over think things! haha But as I said, I much rather spend extra (possibly useless) time anticipating problems while my piece of equipment works than scratching my head with a brick in my hand.
Thanks for the tutoring, I shall plow ahead with confidence! ... right after I fix my water heater. Now there's a non-working piece of equipment one really can't do without!
ricknau said:
This is a follow-up of the thread " [Q] can't locate /mnt/sdcard/ ". That thread is now locked.
I was able to get ES File Explorer to display /mnt/ in the path to /sdcard/. But now, while in /mnt/sdcard/, I do not see /system/bin/. The routines that root the A100 require access to /system/xbin/.
I looked in ES File Explorer - Settings - File Settings - for an obvious solution but found none. "Show Hidden Files" is already checked.
Click to expand...
Click to collapse
Just a quick note for future reference: the /system/xbin directory isn't located under /mnt/sdcard.... its located under root.
Sent from my A100 using Tapatalk
Crap! Didn't work for me
I did all the steps ...
Extracted the su file (using Winzip on my PC), copied it to /mnt/sdcard/, then entered the commands lines with a terminal emulator. But the program Root Checker says I am not rooted. The Busybox installer program says the same.
I figured out how to display /system/xbin/ (in root ). And I can see the su file in /system/xbin/. It is 25.71 KB. So I figure my command lines ran OK. What could be wrong?
I've tried the process several times. I used a signed su (whatever that means). After each attempt the "modified" date and time stamp of the su file in /xbin/ matches the date and time of the attempt.
Busybox error screen said if I think I am rooted to "go into Superuser app and click on Busybox installer and then click "Forget" and restart this app". I guess I could try that even thought Root Checker agrees with the "not rooted" condition. Is it OK to attempt to install Superuser if you aren't rooted?
The good news is that so far the tablet is still working fine.
Any ideas anybody?
Im having this exact same problem, and havnt found a fix yet for it.
I finally got it!
Oh man I got it! I'm such a dumbass! I wasn't reading carefully enough. The Superuser app from the market is the key. Superuser must be installed first and opened before Busybox can even be installed. Now I have Busybox installed and Root Checker says I have root!
Thanks to all the smart and helpful people who provide the great info here and in the other forums to help us less learned ones make full use of these great tools!
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE
Awesome!
does not work for me...
Worked perfect here, that fixes my only serious issue with the ICS rom.
I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.
Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.
Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!
Can anyone help me with this via step by step?
I could use a little help as well
Sent from my SGH-I927 using xda app-developers app
Yea, i could use some help too, after re-writing over the existing file didn't work
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch
ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man
LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?
Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister
Hummm is their gonna b a flashable zip for this ?
Hi! From a few months, since I started flashing new ROMs, my gnex became slower and very laggy. The real problem is that it is very slow even when flashing ROMs and other stuffs in recovery mode. I'm currently using CM10 with Franco kernel and ClockworkMod recovery. Changing kernel and wiping didn't solved anything. What could be the reason?
Try to download eMMC brickbug check, is an app that check if your memory chip is affected by a factory bug (since there's a series of chip afflicted), this bug slow down all the system and makes it very laggy. Try to take a shot, and if the result is that you are afflicted in the forum there's the solution!
No bug and no errors in memory test
1 - Backup all files on your SD card .dont include /android/ Directory.
2 - Flash Google Factory Image for 4.1.2
2.1 - Flash Latest TWRP
3 - Download "Forever Gone"
4 - Start it and let it run through your empty SD card (it'll overwrite it with 0s, it helped fix a problem on the nexus 7 and helped me with some SD card IO lags, And it removes all traces of what once was, so...)
5 - Download Rasbeanjelly 11-6 (the 4.1.2 version ) It's pure AOSP, Blazing fast and the standby drain is amazing (and notifications don't delay even when asleep )
6 - Download Trinity Kernel latest stable (Link http://goo.gl/jl1Ga )
7 - Flash the above and set up your ROM.
SECTION TWO
8 - Go to Google maps >> Location settings & turn everything off.
8.1 - If you still want location history use backitude instead of latitude
9 - Use one chat app instead of many (especially FB messenger it sucks battery big time, use IMO . It's the best, has file transfer, audio/video call, lovely interface and supports most networks even skype.
10 - Sign out of Google talk
11 - Turn off Google+ Sync
12 - Turn off Google Backup
13 - If you don't use it, Turn off Google now (i think it's nice actually).
14 - Install Betterbatterystats & BatteryMonitorWidget to keep watch of any batter hogs should they come along.
15 - Install Velis Auto Brightness
Trust me on this one with trinity & rasbeanjelly
Set the CPU to 1000thingy max/600 thingy minimum
I believe that when i get a quality phone for this kind of cash i shouldn't compromise functionality c: so i don't use battery saving apps, i need my data on and always, I get about 17 hours with ~3 hours screen time, Pm me if you need anything else ^_^
[Edit] Optional : Turn off screen touch sounds/Vibration, if you want to...
-----------------------------------------------------------------------------------
Silencing maps (preventing non user caused wakelocks)
1. Sign out and /or freeze latitude.
That's it!
Additional information:
-manual startup of maps will work anyhow, don't worry,
-navigation still works
-toggling gps on will show your current position on the map
Do you format partition cache and Dalvik cache before flashing ROM?If no then this is the problem you are facing..coz i've flashed 100's of ROMs but no problem yet!!
Wait wait wait (xD)..it's very slow even WHILE FLASHING anything (or making backups) in recovery mode (when there's the green android with the rotating blue frame inside). I can't see how changing ROM or changing settings inside the OS can solve the problem...I'm not an expert but I think it's a problem at a lower lever..like kernel, drivers, chips..something like that :silly:
..anyway..cause not an expert I tried the Trinity kernel and didn't make any difference..and I will try to use Forever Gone after I made a backup and restored to factory image..
This may and probably applies.
http://forum.xda-developers.com/showthread.php?t=1971852
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
This may and probably applies.
http://forum.xda-developers.com/showthread.php?t=1971852
Click to expand...
Click to collapse
Ok I made a bench and I had horrible results. This night I'll try to fix this...
Restore all to stock and these are the results:
Seems that you have the same buggy eMMC chip of type V3U00M.
The phone might slowdown again after writing some data on it. You should add discard to your mount options.
Guide (filling the partition using dd and rm is optional for you)
I don't know how to run the code of the step 3: I tried to install Android Termina Emulator and run the commands here..."su" worked and the dialog box of SuperSU appeared asking me the permission, but when I wrote "mount -o remount,discard /data" nothing appened. Sorry men..I don't know what I'm doing
He says:
Type the following commands in a Terminal or preferably an adb shell:
Click to expand...
Click to collapse
and than
Therefore using adb would be better... Some users also reported a speedup when this is done in recovery mode (CWM/TWRP) via adb.
Click to expand...
Click to collapse
How can I do that? Like...reboot into recovery mode, connect the phone to the pc, move to the folder of adb.exe and run the command as "adb su" and "adb mount -o remount,discard /data" ? ...I don't think :silly:
nicari92 said:
I don't know how to run the code of the step 3: I tried to install Android Termina Emulator and run the commands here..."su" worked and the dialog box of SuperSU appeared asking me the permission, but when I wrote "mount -o remount,discard /data" nothing appened. Sorry men..I don't know what I'm doing
Click to expand...
Click to collapse
The command did add the discard option, but it is not showing any output
nicari92 said:
[...] How can I do that? Like...reboot into recovery mode, connect the phone to the pc, move to the folder of adb.exe and run the command as "adb su" and "adb mount -o remount,discard /data" ? ...I don't think :silly:
Click to expand...
Click to collapse
Nearly right: You have to open an adb shell (using the command adb shell) and then type the commands
Well, as you don't really know what you're doing, I think that it's not such a great idea to experiment with the command line in superuser mode...
You can get the same results doing the following:
Install Script Manager from Play Store.
Download the following text file to your internal memory: remount.sh
Browse to the script in Script Manager and add it to be run at boot (Open as... Script/Executable). Make sure you check both the Boot and Su options, then press Save and Run.
Now you should be done if you don't already experience huge slowdowns of your memory (0.4-0.5 MiB/s random write is OK)
If you HAVE slowdowns, install Forever Gone. Fill your sdcard (aka securely erase deleted files) and then free the filled space. Done.
Install and run LagFix (fstrim) from Play Store. Done.
---
FYI: The code in remount.sh is the following:
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
Ok thanks!
Do I have to relaunch the command (or recreate the script) every time I flash a new ROM?
nicari92 said:
Ok thanks!
Do I have to relaunch the command (or recreate the script) every time I flash a new ROM?
Click to expand...
Click to collapse
After a full wipe you have to re-install the app and configure the script again to make sure it is launched on every boot.
Install seeder v1.4 too.
Look for it in XDA(free) or the Play store(paid)
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
AW: [Q] Very slow and laggy Nexus
I don't think that waiting for the random source is the problem here...
The thread I linked has an app that can run the trim command which should help io.
Sent from my Galaxy Nexus using Tapatalk 2
Direct Link
You can use it instead of dd&rm / Forever Gone. The tool does this job better and is faster, I would say it's the preferred method now.
Doesn't permanently solve the problem, though (unless you run it periodically) ...
So maybe the best is using the discard init script plus this app once.
once you have run the remount script why do you need the lagfree app?
ph4zrd said:
The command did add the discard option, but it is not showing any output
Nearly right: You have to open an adb shell (using the command adb shell) and then type the commands
Well, as you don't really know what you're doing, I think that it's not such a great idea to experiment with the command line in superuser mode...
You can get the same results doing the following:
Install Script Manager from Play Store.
Download the following text file to your internal memory: remount.sh
Browse to the script in Script Manager and add it to be run at boot (Open as... Script/Executable). Make sure you check both the Boot and Su options, then press Save and Run.
Now you should be done if you don't already experience huge slowdowns of your memory (0.4-0.5 MiB/s random write is OK)
If you HAVE slowdowns, install Forever Gone. Fill your sdcard (aka securely erase deleted files) and then free the filled space. Done.
Install and run LagFix (fstrim) from Play Store. Done.
---
FYI: The code in remount.sh is the following:
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
Click to expand...
Click to collapse
Thanks a million... Works like a charm.
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
Step 1: Setting up stuff
Find and download a suitable file explorer that allows you to modify and browse system files. I recommend Root Explorer. (Optional)
Download and install Terminal Explorer from the Google Play Store.
Download and install Script Manager from the Google Play Store. (Optional)
Step 2: Walking the path
Open Terminal Emulator and type in
Code:
su
Your root manager should request you for permission. Grant the app superuser permission.
Type in
Code:
vold
Press enter
Type in
Code:
mount -t vfat -o umask:0000,uid=1000,gid=1023 /dev/block/vold/179:33 /storage/sdcard0
Press enter.
Type in
Code:
mount -o bind /data/media /storage/sdcard1
Press enter.
Click to expand...
Click to collapse
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
not work in FW XM Dual
how to swap internal and external in FW XMD ?
@gadgetroid , will it work in Xperia M Dual 4.2 ?
It Worked!!!
gadgetroid said:
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
Click to expand...
Click to collapse
Worked for me
13 GB internal storage
aerialus said:
not work in FW XM Dual
how to swap internal and external in FW XMD ?
Click to expand...
Click to collapse
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Code:
mount > mount
Then, on the computer, open a command prompt window (or terminal on Linux) and type in
Code:
adb pull /partitions
Code:
adb pull /mount
Put these two files in the zip along with the vold folder and post them here. I will look into it and provide you the guide.
jereMarfil24 said:
@gadgetroid , will it work in Xperia M Dual 4.2 ?
Click to expand...
Click to collapse
Since it runs 4.2, I can't be very sure, as Sony may have changed device names. Once the above user submits the files, I will look into it and post the guide.
gadgetroid said:
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Click to expand...
Click to collapse
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Did u written su above?
Sent from my C1904 using Tapatalk 4
aerialus said:
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
gadgetroid said:
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
Click to expand...
Click to collapse
my device is already rooted and have Busybox installed,,
please look at my attachment
aerialus said:
my device is already rooted and have Busybox installed,,
please look at my attachment
Click to expand...
Click to collapse
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
aerialus said:
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
gadgetroid said:
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
Click to expand...
Click to collapse
in XM Dual no need use rootfixer anymore,,
just root with tools and success full root,,
magicw said:
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
Click to expand...
Click to collapse
ok i will try :fingers-crossed:
Yes. That is exactly what it does. It works if you put in sdcard
Script
I have created a script for this. If OP gives me permission i can publish it.
pull partitions and mounts success,,
but when i try to pull folder "/dev/block/vold"
the result is " 0 files pulled, 0 files skipped"
see my attachment
icoolguy1995 said:
I have created a script for this. If OP gives me permission i can publish it.
Click to expand...
Click to collapse
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
gadgetroid said:
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
Click to expand...
Click to collapse
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
icoolguy1995 said:
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
Click to expand...
Click to collapse
I'll add it to the op soon. BTW, if you place the script in /data folder and set it to rw-r--r--, it will be easier. That way, the script won't be in the wrong drive after it's been switched.
No it will not work unless all the options are ticked on permission setting.
icoolguy1995 said:
No it will not work unless all the options are ticked on permission setting.
Click to expand...
Click to collapse
It works for me with rw-r--r--
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.