I move app to system (via file manager) and reboot.
Then I got bluescreen instead bootanimation, but phone boot in a few secs. I'm little panicked. I'm scared to power off/reboot phone again. What this can be?
You're forget to set permissions properly)))
Try to do it trought recovery
App works, so I think its set properly. Thanks anyway
I set them via file manager (like other system app) to rwxrwxr-x and root.root and seems its good.
Related
I'm using Root Explorer.
Everything I select the systems directory and check the "write" boxes and press okay, nothing happens. I still can't transfer files in there. I'm trying to change the bootup and startup audio sounds in the system folder.
And while im in the systems folder, I try to press "Mount R/W" and nothing happens. The toggle works when I'm in the / directory though, just not in the /system/.
Also, I'm trying to flash the new version of the MTM keyboard. I launch CWM through Rom Manager, and try to flash the zip file, but it says installation aborted. But I go to "advanced" and select "Fix Permissions," and try again, it installs successfully. But when I reboot my phone, my keyboard stays the same as the old one and the new version is no where to be found.
Any help is appreciated!
So i edited the android info.txt file in PH198. Now when I try to boot my phone into bootloader, it comes up with a screen saying volume up for update, volume down for no update, and then I just have to power off. Any suggestions?
Edit: Sorry if I was unclear, but when I update, my phone gets stuck on the white HTC screen.
Edit: I got it working thanks for the advice guys
nkd94 said:
So i edited the android info.txt file in PH198. Now when I try to boot my phone into bootloader, it comes up with a screen saying volume up for update, volume down for no update, and then I just have to power off. Any suggestions?
Click to expand...
Click to collapse
Umm it's supposed to do that to load the kernel. Then you boot up to your rom and first thing delete that file off the SD card
Just boot up Rom like normal then delete using a file explorer like es file or root explorer. If it won't reboot to your rom, then pull battery remove sd card and boot . Once your booted up then reinstall SD card and delete the ph file.
nkd94 said:
So i edited the android info.txt file in PH198. Now when I try to boot my phone into bootloader, it comes up with a screen saying volume up for update, volume down for no update, and then I just have to power off. Any suggestions?
Click to expand...
Click to collapse
What are you flashing? There's a lot of renaming things to the PHzip file name.
Actually, in any case, if you are being asked for update you should press volume up to select update, then if it says to press the power button that should be your "yes" answer to allow it to proceed. I think it says that.
Then once it is done reboot the phone if it didn't do it already and, as mjh68 mentioned above, use a file explorer like ES File Explorer or Root Explorer to delete that PHzip file. Then you should be good to go. Or you can then connect to your pc and delete the file that way, or power down and take the card out and put it in the pc and delete the file. If you don't delete that file then every time you boot up your phone it will go to flash it again.
feralicious said:
What are you flashing? There's a lot of renaming things to the PHzip file name.
Actually, in any case, if you are being asked for update you should press volume up to select update, then if it says to press the power button that should be your "yes" answer to allow it to proceed. I think it says that.
Then once it is done reboot the phone if it didn't do it already and, as mjh68 mentioned above, use a file explorer like ES File Explorer or Root Explorer to delete that PHzip file. Then you should be good to go. Or you can then connect to your pc and delete the file that way, or power down and take the card out and put it in the pc and delete the file. If you don't delete that file then every time you boot up your phone it will go to flash it again.
Click to expand...
Click to collapse
I am flashing CleanRom 2.3 except with the nonstandard kernel. I will try removing the microsd and putting back the standard kernel then updating again. Thanks
EDIT: When I boot my phone it goes straight to the update screen not to the bootloader. Is there any way to boot the phone into recovery with my computer?
If you have a backup, and have adb just type adb reboot recovery to restore or wipe and flash a new Rom. Make sure the Rom matches the kernel
Sent from my ADR6425LVW using xda premium
Hey so I'm attempting to re-root my Nexus S 4G (now at stock 4.0.4), but when I reboot, it says I'm rooted....however when I try to reboot back into recovery, it goes to stock recovery. I'm not too sure, but I'm wondering if they put the safety feature from 2.3.1 back in the 4.0.4......
P.S.- I'm also havingtrouble getting ROM Manager to work (because Clockwork doesn't exhist in the recovery...I'm guessing)
There is a file that you have to delete using a file manager...I think it is in the recovery folder called "set on boot". Let me check around and see if I can get the exact location and name.
Edit: Here you go. http://www.theandroidsoul.com/install-touch-based-clockworkmod-cwm-recovery-on-galaxy-nexus/
Step 1 shows the file to delete. That file automatically pushes you to the stock recovery.
The problem is SuperUser isn't responding as "rooted" I don't have the permission to Mount R/W.....I'm not sure where to go from here...
So, I was changing my boot animation and I foolishly removed the execute permissions of my system folder from users and groups and it made everything crash in a cascade. Now I am unable to boot beyond the bootloader or protocols that don't rely on the system folder. I can load fastboot on the Photon but adb cannot see the phone since I cannot boot it. If I choose 'BP Tools' from the boot loader, I can get a shell connection with my phone for about 5 seconds before it crashes, however, the permission is denied. If anyone knows a command that would bypass permissions and allow me to quickly run a shell command to change the system folder permissions back to normal I'd be so very relieved and grateful.
Here's the message when I run adb shell during that 5 second window:
exec '/system/bin/sh' failed: Permission Denied (13)
I need a quick sudo-chmod something or another to ninja that /system folder's permissions back to where they should be. I am terrible with linux so I'm hoping theres a fix as simple as the problem really is. I can do a master boot if I need to but I don't see why the whole system should turn unrecoverable because of ticking 2 little green check boxes that consist of only a few bytes... omg...
K I did a factory reset and I apparently have to flash the entire ROM because the system folder isnt touched by the wipe.
Ugh, another 10 hours to walk in the dark cause Im terrible at this stuff.
Can you boot into recovery?
If so try Recovery -> advanced -> fix permissions reboot.
Sent from my MB855 using xda app-developers app
I guess I'm a moron and can't figure this out :v
Using stock rooted Oreo, Magisk, edXposed, everything that goes with them. TWRP 3.2.3-7.
Lately, I've been using my headphones while driving to work. I need a touch more volume over stock to deal with wind noise.
The problem is, I absolutely can't get /system/vendor/etc into a writable state.
Attempts to modify mixer_paths_tavil.xml whilst booted up fail, either resulting in an unreadable file (Total Commander) or just not working (Root Explorer).
Trying to flash a modified zip (just grabbed a dual-speaker mod and replaced the xml) in TWRP results in no file being created; it doesn't seem to throw an error, just silently fails.
Manually copying the xml to /system/vendor/etc using TWRP's file manager ~appears~ to work, but attempts to set permissions results in error code 1. The file doesn't exist upon reboot.
Remounting manually as RW in TWRP's terminal doesn't seem to help. And yes, "mount System as read-only" is unchecked.
I can make build.prop changes, so I know /system is writable. The only way I can get anything written to /system/vendor/etc is restoring a full system backup.
I've modified this file before; I manually tweaked the call volume higher and enabled "fake" high-impedance mode.
So I'm sure I'm doing something really stupid here. Help.
Septfox said:
I guess I'm a moron and can't figure this out :v
Using stock rooted Oreo, Magisk, edXposed, everything that goes with them. TWRP 3.2.3-7.
Lately, I've been using my headphones while driving to work. I need a touch more volume over stock to deal with wind noise.
The problem is, I absolutely can't get /system/vendor/etc into a writable state.
Attempts to modify mixer_paths_tavil.xml whilst booted up fail, either resulting in an unreadable file (Total Commander) or just not working (Root Explorer).
Trying to flash a modified zip (just grabbed a dual-speaker mod and replaced the xml) in TWRP results in no file being created; it doesn't seem to throw an error, just silently fails.
Manually copying the xml to /system/vendor/etc using TWRP's file manager ~appears~ to work, but attempts to set permissions results in error code 1. The file doesn't exist upon reboot.
Remounting manually as RW in TWRP's terminal doesn't seem to help. And yes, "mount System as read-only" is unchecked.
I can make build.prop changes, so I know /system is writable. The only way I can get anything written to /system/vendor/etc is restoring a full system backup.
I've modified this file before; I manually tweaked the call volume higher and enabled "fake" high-impedance mode.
So I'm sure I'm doing something really stupid here. Help.
Click to expand...
Click to collapse
Don't know, but tonight or tomorrow I'll shoot you a file to test.
ChazzMatt said:
Don't know, but tonight or tomorrow I'll shoot you a file to test.
Click to expand...
Click to collapse
Appreciated, but I think something's going pear-shaped and I just need to reflash the ROM; setting up for the drive home last night, it seems I've lost the ability to use direct output in Poweramp. I don't know how, since the system+system image backup I restored is known-good and audio is otherwise working.
Good ol' bitrot, I suppose.
Septfox said:
Appreciated, but I think something's going pear-shaped and I just need to reflash the ROM; setting up for the drive home last night, it seems I've lost the ability to use direct output in Poweramp. I don't know how, since the system+system image backup I restored is known-good and audio is otherwise working.
Good ol' bitrot, I suppose.
Click to expand...
Click to collapse
See my PM.