Has anyone managed to auto power-on the device when its charging ?
I have rooted my device with magisk , and i can't mount the / partition to edit the .rc file within the /system/etc folder
just to clarify i try to create a file within /system/etc/init
Related
Hey Guys,
i have unlocked, rooted and flashed my Phone with Hassons ToolKit.
I have a problem getting full write access to my system folder, and all other folders / files which are in same path where system folder is.
I have just rights in SdCard Folder..
THis is the path where i dont have any permission to change something: is this normal?
If yes, so how can i push an apk to system folder then, if i need a new keyboard for instance...?!
acct
cache
config
d
data
dev
devlog
etc
mnt
proc
rca
rfs
root
sbin
sdcard (just in this one i have rights)
storage
sys
system
vendor
...
some files...
Ropb said:
Hey Guys,
i have unlocked, rooted and flashed my Phone with Hassons ToolKit.
vendor
...
some files...
Click to expand...
Click to collapse
Are you using adb or some Android based file manager to copy the file?
If it is adb = use adb remount, this normally solves the problem. If you are using some file manager - make sure system is mounted in RW mode..
Ropb said:
Hey Guys,
i have unlocked, rooted and flashed my Phone with Hassons ToolKit.
I have a problem getting full write access to my system folder, and all other folders / files which are in same path where system folder is.
I have just rights in SdCard Folder..
THis is the path where i dont have any permission to change something: is this normal?
If yes, so how can i push an apk to system folder then, if i need a new keyboard for instance...?!
acct
cache
config
d
data
dev
devlog
etc
mnt
proc
rca
rfs
root
sbin
sdcard (just in this one i have rights)
storage
sys
system
vendor
...
some files...
Click to expand...
Click to collapse
i guess you want to acces those folders with a file explorer? afaik it is normal that you don't have acces to other folders than sdcard, you have to use a file explorer with root capability to acces/write the other folders.
I'd recommend you to use ES File Explorer, very good app for me.
To grant root acces for it:
open the app -> press menu -> Tools -> Root Explorer (now the app should ask for root acces) -> Mount R/W -> set the paths where you want write acces to RW
now you should be able to write to the other folders.
If you want to use adb push (USB Debugging mus be enabled):
- copy the desire file or apk to your adb/fastboot folder
- connect your phone to your computer, open command line, navigate to adb/fastboot folder on your pc if necessary
- type "adb devices" (to see if your phone is recognized)
- type "adb push <name_of_your_file.file_extension> /path_of_your_destination_folder/<name_of_your_file.file_extension>"
Example: adb push example.apk /folder1/folder2/example.apk
Hello,
i have a Wiko PULP 3G, without a working root method.
I take a look at the Firmware files, there seems no CRC Protection. Even a Satellite Receiver or a TV Firmware have such.
I changed Text in the image with a HEX Editor(ro.sys.usb.storage.type) to get Massstorage. I flashed the modified image.
The Program just done it. Okay i have still no Massstorage. But on the Mobile i can see the build.prop has really changed
like i edit it.
I wonder if i can change Textfiles, it may possible to mount system as r/w.
Its a 1.9GB image difficult to find the Init/fstab.
Questions:
1. What do i need to modify to get mass_storage ?
2. How are the typical Textlines for a phone to make system read-only?
3. If i have write access to /system i can put a "su" file(any?) to system install SuperSU and have root?
Okay i have modified a boot.img, repack it and flashed it.
I set ro.secure=0, ro.debuggable=1 and massstorage in build.prop.
I got masstorage )))))
But how do i get the su to xbin. In the extracted Boot.img or Recovery.img there is no xbin.
Other .img files cant be xtracted.
With adb push this dont work, no permission.
Ideas?
If this is a raw system partition ext4 image, you can just mount it (with -o loop) on your Linux PC and modify the contents.
_that said:
If this is a raw system partition ext4 image, you can just mount it (with -o loop) on your Linux PC and modify the contents.
Click to expand...
Click to collapse
Thanks, but its not a raw image. I think its Android Sparse Image Format.
Linux cant mount it. Yaffey is not able to handle it.
I wonder why there i no tool where you can put a Firmware in and click on "Root it" and ready is the new one?!
Now i found tools to depack/pack the system image.
But the Phone dont boot, it starts and restart in Recovery.
If i do a root filecheck in Recovery it says 1 file added and 1 file changed - FAIL.
There must be something like a modify protection
I run into following problem. I have successfully rooted my phone and installed magisk. Now what I try is to replace the bootanimation.zip...
But it fails at permissions. I granted superuser access via Magisk to the app (Es file explorer) and I also toggled the root option to in in this app. But whichever I try it fails neither can I delete or write to the system. I also tried different root explorers facing the same issue.
Those someone know how to solve this?
Thanks in advance
Graru1
Same issue here.
Sadly don't know an solution
Your /system partition where you want to replace the file is read only. Flash a custom rom or use this automatic script from this thread to rebuild your /system partition as read-write and you will be able to replace the files.
Hi
I have spent hours trying to fix a problem on my Android TV box and I have gotten nowhere.
The issue is that generic.kl reset to 0 bytes and now whatever I do, I cannot edit the file.
I have set it to read-write 777 and all sorts of combinations. I have set the partition to read-write mounted.
I have used a root explorer to copy and paste a working version of the file over the top, it does not give an error and the file is there, again it is empty at 0 bytes.
I have tried to run a text editor itself as root but SuperSU will not run - saying the SU Binary is occupied. I did a factory reset and the issue is still there. There is no way to do a full flash reset on this model.
No matter what I do, I cannot seem to actually edit or replace this generic.kl file
Any ideas or suggestions?
Cheers
is it a system partition file ? probably the only way for now would be to modify the file before creating a system image for you to flash. I'm not even sure that's a doable thing actually.
no recovery is a PITA
Yeah, the file is in the System partition in the USR folder.
Do you think there is no way to fix this then? I.e. I can never use a physical keyboard with this unit again as the file controls the key mapping..
Scott
devices that start out with android 10 have a read only system partition. if you have the know-how magisk can still create overlays of system files, you'd need to write a module or get one requested from someone.
@Electron2k it might be worth talking to the dev or asking in this thread
https://forum.xda-developers.com/apps/magisk/module-1controller-1-module-to-support-t3865889
if you've created your new file already maybe there's a way to incorporate it into this module to do what you want. I'm not saying they'll change the module for you, but he or she might help to do it yourself.
Hi there, if you can track down the firmware for your box get the img file and extract it.
Locate the generic.kl file from the extracted rom and copy it over using a file manager, remove the null generic file and reboot your device. All should be working then.
##edit ## just noticed you've already tried replacing the file with a filemanager sorry
Electron2k said:
Yeah, the file is in the System partition in the USR folder.
Do you think there is no way to fix this then? I.e. I can never use a physical keyboard with this unit again as the file controls the key mapping..
Scott
Click to expand...
Click to collapse
Pls send the module or the solution if you have it
Hi all,
I am trying to edit a file on /system (/system/etc/init/hw/init.rc), to allow my powered off phone to be turned on when plugged into a power source.
I have successfully gained root, however, /system is unable to be mounted as read/write. I have attempted this many ways such as re-mounting /system via FX File Explorer and root explorer or trying to remount via terminal, but I receive the error that /system can not be mounted as Read/Write.
I attempted to edit the file via TWRP file editor, and was able to successfully save, but the file reverts itself when the phone is booted. Strangely , the "HW" directory when booted into android has several *.rc files, however when viewing the directory in TWRP the only file seen is the init.rc, which differs in content than the booted version. This makes me think boot.img is writing these files each time the phone boots.
I have edited this file successfully on the 6T, which allows you to mount /system in R/W mode.
Any advice on how to edit the file, or another workaround to allow the phone to bootup when plugged into a power source?
Thanks!
Turn off secureboot
kwell24 said:
Turn off secureboot
Click to expand...
Click to collapse
Great suggestion, according to Fastboot screen Secure Boot is enabled. I googled around how to disable but the only oneplus specific suggestion was in the security settings, and this option is not listed in the Nord 200. Other suggestions also did not seem to work. Do you know how to turn off Secure Boot?
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
Or manually, either way I don't recommend messing with the system. Better trying to achieve it with Magisk systemless-ly
I finally figured out how to edit init.rc to allow automatic powering on when connected to a charger.
Converted T-Mobile phone to stock rom via https://forum.xda-developers.com/t/...thout-msm-tool-credit-to-summersofar.4339037/
Unpack the sys.img from the stock rom using CRB tool https://forum.xda-developers.com/t/tool-windows-kitchen-crb-v3-0-0-beta8b.3947779/
Edit init.rc according to https://forums.oneplus.com/threads/how-to-boot-oneplus-one-when-charger-connected.1170454/
Repack system.img using CRB tool
flash system.img back onto phone
Now my powered off phone will boot up when plugged into a power source! Steps 1 and 2 can probably be reversed so you just flash the edited system.img to the phone.