Everything is working in my kingdroid v3.0
but when i install chainfire it asks for installation of driver
and could not write to /system
i used root explorer and everything else but the /system r/o cant be changed to
its stuck at R/W and i cannot copy or do whatever ...
i try to set permissions but it says read-only .... how can i change this into R/O mode????????
Related
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Metatronx said:
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Click to expand...
Click to collapse
try
Code:
adb remount
What would the syntax be for remounting the core.jar and is it possible to do in terminal? Thank you especially for the quick response\!
From your other thread..
The entire /system partition is always read-only, unless you tell your phone to remount it read-write.
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
But for your problem.. You shouldn't really need to manually tweak files in /system if you flash another ROM. The new ROM will replace that entire partition. Have you wiped? What ROM are you trying to flash?
Kudos for using logcat and trying to jump in yourself though.
Hi guys
I'm new to deodexing, following a guide for XUltimate.
I copied my system\app dir to a folder called origi_app, and my system\framework to a folder called origi_frame on my int SD card, then copied these two folders to my PC XUltimate dir.
Ran option 3, then 4, both finished with sucessful.
This gave me two new folders in the XUltimate dir...
done_app & done_frame
I copied these back to my int SD card, then following the guide, ran ADB from cmd prompt..
Typed: ADB Shell
Got a $
Typed: SU
This gave me a Permission Denied ??
So as per the guide, I tried Root Explorer...
Selected All the .apps in done_App, selected copy and then tried to paste into the system\app dir.... this then gave me a failed to copy due to lack of space error and the phone started to vibrate and com.android force closing repeatedly...
Were did I go wrong, why did I get permission denied trying to get the SU cmd?
The full adb guide was as follows:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk1p21 /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /dev/block/mmcblk1p21 /system
reboot
As above, got as far as SU then got permission denied!
So thankfully I did a nandroid backup before and am currently restoring it...
EDIT: My Backup has just finished restoring from CWM... rebooted but it is now on original startup setup and getting force closes for lots of apps???
Had to re add my APN settings to re download MY Backup and am currently restoring apps and data from it now! Fingers crossed. I thought the whole point of a cwm back up was to create an exact image of the whole system, files, date and settings etc?
Well, restored via My Backup, but rom manager and Sky news kept force closing, so wiped the whole thing and flash a custom js8 from from Doc's kitchen... glad I did... just miss the cirlce battery mod I had before.
In case it's unclear, I have CM7 on eMMC and am setting up a Honeycomb/Phiremod dual-boot on SD, and would like all three ROMs to use the storage partition (7th in this case) on the card. The following post suggests to me that it's possible:
racks11479 said:
No need to root your stock nook. If you have a CM7 sdcard, root explorer or file expert(free from market), and a terminal emulator app. Which you should have with cm7. Try the following steps.
-using root explorer or file expert. Mount system as R/W
-open up a terminal emulator and run the following commands
Code:
$ su
# mkdir /mnt/nooksys
# mount /dev/block/mmcblk0p5 /mnt/nooksys
-now exit out of terminal emulator
-open up root explorer/file expert
-navigate to /mnt/nooksys
-you should now be able to see the stock nook system partition
-open up the /etc directory
-long press the vold.fstab file.
-it should give you an option to open with text editor
-change the line where it mounts the /sdcard from auto to 4
-exit out of root explorer
-reboot to stock
-it should now mount the 4th partition of your sdcard
Click to expand...
Click to collapse
The file path specified, however, did not work, and I don't know enough about linux in general or the specific file structures to figure out the necessary changes. The system I want to redirect is the CM7.1 beta running dalingren's 5/13 OC kernel.
I also don't know for sure whether the above works for redirecting a stock 1.2 install.
Alright.. I wanted the Note 8 version of gallery and i went into system/app folder and deleted the SecGallery2_Galaxy.apk but before deleting i saw that its size was 0.00 kb lol ..
But when i tried tried to copy and pasted in the extsd it pasted and showed 13mb..
Now i deleted the file and copied the Note 8 Galley and pasted in the system/app folder only to get an error " Operation failed " and i realized only 7 mb free space is there in the partition by going into the android emulator!
Now i also found out that, full size SecGallery2_Galaxy.apk was in the preload partition and i instead of replacing that i deleted the file in system/app..
Now how do i get back that file in system/app?.. is that what they call deodexed file?.. Please help..
Thanks a lot in advance
Just copy it from other rom, that You can explore with winrar.
Sent from galaxy n7105
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
nokiamodeln91 said:
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
Click to expand...
Click to collapse
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
CustomRomAddicts said:
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
Click to expand...
Click to collapse
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
nokiamodeln91 said:
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
Click to expand...
Click to collapse
It says read only file system
I even changed the permission of the file in preload to 644 ( rw-r--r-- )
still the same message?.. any idea what it might be?.
Thanks in advance
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
nokiamodeln91 said:
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
Click to expand...
Click to collapse
Honestly i just now searched in google for adb shell and it says to run windows but when i download and double click the adb.exe it runs and exits!.. Please help..
Will mounting the preload and system in recovery and rebooting the device and running the script again in android emulator work?..
Keep in recovery and mount both.. Then run....
nokiamodeln91 said:
Keep in recovery and mount both.. Then run....
Click to expand...
Click to collapse
I tried in adb shell too.. but its not working
Do u guys have the symlink file?.. can u share with me?.. will it work?..
Thanks in advance
Oh Yeah! SOLVED IT!!
I installed Root explorer and created symlink via that and Voila it worked!
Although i dont know why when i open a photo in gallery i experience FC!
There have been quite a bit of people with issues with Systemless root, there are some apps that are not recognizing root, i had this issue with my Oneplus One on COS 13.1 and now the same thing works with our OnePlus 3 on OxygenOS
I had come across this on another forum, i don't recall where so i don't want to take the credit for this, i just want to provide the fix for people who have this phone and having issues
Download Terminal from app store and type
Code:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
I belive it creates a dummy file bc some apps require it to show as a system file
SDMU said:
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
Click to expand...
Click to collapse
Code:
1. su
2. mount -o remount,rw /system
3. touch /system/bin/su
4. mount -o remount,ro /system
5. reboot
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Squabl said:
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Click to expand...
Click to collapse
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
candiesdoodle said:
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
Click to expand...
Click to collapse
Yes, it "disables" systemless root and afterwards it is just a root and banking apps and ota updates etc will fail. I don't need systemless root so I have modified my system partition to get some poorly coded apps to function. This method is not recommended if you need systemless root and it's a good thing that you pointed that out!