I've noticed that I'm unable to mount /system using adb to pull or push files. Whether I use adb remount or mount -o rw,remount blahblahblah /system through adb or terminal.
If I open root explorer and mount system rw, it will then let me pull or push.
I've read its because of not having insecure adb. Now this seems to be only on a stock ROM or my stock rooted.
I sent it through the kitchen again and unpacked the kernel, chose the adb insecure option, repacked ...rebuilt...flashed...and still the same.
How can I get around this?
Sent from my SAMSUNG-SM-G870A using Tapatalk
Nickovtyme said:
I've noticed that I'm unable to mount /system using adb to pull or push files. Whether I use adb remount or mount -o rw,remount blahblahblah /system through adb or terminal.
If I open root explorer and mount system rw, it will then let me pull or push.
I've read its because of not having insecure adb. Now this seems to be only on a stock ROM or my stock rooted.
I sent it through the kitchen again and unpacked the kernel, chose the adb insecure option, repacked ...rebuilt...flashed...and still the same.
How can I get around this?
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
you can't change anything in the kernel ramdisk, Locked BL prevents that. :crying:
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.
I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.
I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!
MIne is Nexus one. It's just rooted.
http://forum.xda-developers.com/showthread.php?t=611829 the newest Ra recovery for n1 is here.
There was a note:
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android).
I tried on my n1 and I booted back to stock recovery......
How could I fix it?
philanini said:
MIne is Nexus one. It's just rooted.
http://forum.xda-developers.com/showthread.php?t=611829 the newest Ra recovery for n1 is here.
There was a note:
Install
Pre-Requirements :
Root
Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android).
I tried on my n1 and I booted back to stock recovery......
How could I fix it?
Click to expand...
Click to collapse
after you flash the recovery, without rebooting, just run these two commands:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
gravufo said:
after you flash the recovery, without rebooting, just run these two commands:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
Thank you friend.
I used the fastboot-windows.exe in cmd to flashed the recovery ,and I don't know where to run your cammands.
philanini said:
Thank you friend.
I used the fastboot-windows.exe in cmd to flashed the recovery ,and I don't know where to run your cammands.
Click to expand...
Click to collapse
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Eeeeeek - sorry!
gravufo said:
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Click to expand...
Click to collapse
Thank you man! I will post the result.
gravufo said:
Alright, open a command prompt into adb shell (or use terminal emulator from your phone) and run the following. Note that you don't need to run the first command if you're doing it from the terminal emulator on the phone.
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
After you run these commands, you should flash the recovery again and you should have no problem!
Good luck!
Click to expand...
Click to collapse
Thank you my friend. I tried what you've told me, unfortunately,and it said not found there.
However, I tried MiuiRomInstaller.apk ,it flashed a clorkworkmod recovery. Then I flashed RA recovery back, luckily I succeeded!
I could use that change my rom now.
Thank you Gravufo.
philanini said:
Thank you my friend. I tried what you've told me, unfortunately,and it said not found there.
However, I tried MiuiRomInstaller.apk ,it flashed a clorkworkmod recovery. Then I flashed RA recovery back, luckily I succeeded!
I could use that change my rom now.
Thank you Gravufo.
Click to expand...
Click to collapse
Your welcome, glad it worked one way or the other
gravufo said:
Your welcome, glad it worked one way or the other
Click to expand...
Click to collapse
Man~I restored and tried your way again, This ok now.Thank you!
I have a verizon Samsung Galaxy tab. I would like to use clockwork recovery. The tab is rooted and I used ROM manager from the marketplace to flash the recovery for a Samsung Tab (Verizon). When I flash the ROM everything is successful. However, when I boot into recovery the Android System Recovery <3e> shell loads which doesn't allow nandroid backups etc... all the neat recovery tools that come with clockwork recovery.
I searched around the forum and saw a thread titled how to replace Android System Recovery with a Custom ROM. These were the commands
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
I went into abd shell I tried the commands but by the time I got to the third line I keep getting permission errors before I can even finish typing the command. I cut and paste the command string from "mount-->" thinking I just wasn't typing fast enough and it still doesn't work.
Is there another way to remove the Android system recovery so that ROM manager will work properly?
Have a look at installing boushh's kernel, it probably going to be the best option around for you.
Sent from my X10i using XDA App
I don't know what that is?
I have also same problem ı tryed many flashes ı coudnt fix it yet.if you allready fixed could you please share thanks.....
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!