Hey guys. For those of you who are having problems of no sound on your Lumia after trying to enable root access and have no SBL3 for your phone eg lumia 720, you're in luck.
Firstly a big thanks to @Heathcliff74 for WPinternals tool and @Riyad_ for list of changes to the registry.
Lets get started!!!
1. Flash your phone with the original ROM and there after unlock the bootloader(You don't need SBL3 ).
2. Using WPinternals, dump EFIESP, MainOS and Data partitions.
3. Mount EFIESP and MainOS with OSFMount or similar software.
4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition.
5. Locate mounted MainOS and navigate to Windows\Packages\RegistryFiles. Here you will find SOFTWARE.reg. Copy it to you desktop.
6. Open 7-zip and double click on the SOFTWARE.reg file. Right click on the file named SOFTWARE inside it and select Edit.
7. Copy and paste the contents of the attachment below into the SOFTWARE file then save and exit. 7-zip will give a message, just click OK.
8. Delete the SOFTWARE.reg from your MainOS and copy the modded SOFTWARE.reg from your desktop to you mounted MainOS. Once you have done this, unmount EFIESP and MainOS drives.
9. Go back to WPinternals and now flash all 3 partitions.
10. Wait for phone to flash and reboot then go to "about" in settings and reset your phone and enjoy interop/cap unlocked phone.
so we can't use mass storage mode with this TUT?
mybabysexy said:
so we can't use mass storage mode with this TUT?
Click to expand...
Click to collapse
Unfortunately not becoz there's no SBL3
are you adding tweak in this reg file? and adding your wallapers, sounds and etc for your mainOs?
this is basis for custom rom(backup rom, as huawei w1) with wpinternals(flashed).
reksden said:
are you adding tweak in this reg file? and adding your wallapers, sounds and etc for your mainOs?
this is basis for custom rom(backup rom, as huawei w1) with wpinternals(flashed).
Click to expand...
Click to collapse
Yes the SOFTWARE.reg file is being modified. I haven't added any wallpapers or sounds to my MainOS as yet.
Rivo17 said:
Yes the SOFTWARE.reg file is being modified. I haven't added any wallpapers or sounds to my MainOS as yet.
Click to expand...
Click to collapse
okay.
MainOS.bin\PROGRAMS\CommonFiles\ - sounds and other( replace the names on the modified files).
i'm waiting to flashing plat( change image on the run).
@Rivo17
Sound has always working if Root-access not installed (with or without SBL3)
titi66200 said:
@Rivo17
Sound has always working if Root-access not installed (with or without SBL3)
Click to expand...
Click to collapse
Yeah but now you will have root access and sound working. Most people had problems of no sound with root access.
Sorry but with This
"4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition."
You don't have root Access
titi66200 said:
Sorry but with This
"4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition."
You don't have root Access
Click to expand...
Click to collapse
Yes, you have to do this so you can flash the modded MainOS. Read WPinternals tool.
titi66200 said:
Sorry but with This
"4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition."
You don't have root Access
Click to expand...
Click to collapse
Yes, you have to do this so you can flash the modded MainOS(which contains the changes for root access). Read WPinternals tool.
sounds great for phones which doesn't has sbl3 partition but suppoted in wpinternals..
I have a problem, when I go to Windows Phone Internals and enable root access at EFIESP, the program say enable root access... but it is in a loop, it is loading.... Sorry For my english...
Related
Hello,
i need some help.. the gps in my phone takes alot time to lock(?)...
someone created a gps.conf to replace the original file in system folder.. however i cannot replace the file neither edit it (i have root and tried it with ES Explorer)..
am i doing anything wrong? and how can i access the filesystem by usb? i tried booting the phone with power+vol up/down.. but there (pink screen) no drive was mounted..
thanks and sorry for possible english errors!
if you are using ES File Explorer, you need enable 'root' option and 'mount / /system as read/write' option to replace the gps.conf file
I have same problem.
I had rooted and flashed CW to get 2.2.1 -> Official 2.3 -> ICS
But on step 2. what needs to root and CW to get ICS it is impossible to get the system rooted and flashed again.
When going with + - on boot to magenta screen, Windows (Or Linux) does not recognize any drives to be mounted. Were there a external MicroSD card in slot or not.
I have now rooted device two different way and both say that device is rooted. Even the phone itself says that it is rooted. But no sudo is working so I can not even enable SE Manager root functions or to re-mount any partition as read-write mode because applications does not have root rights.
lovetide said:
if you are using ES File Explorer, you need enable 'root' option and 'mount / /system as read/write' option to replace the gps.conf file
Click to expand...
Click to collapse
i forgot the rw option! i've mounted / but forgot w permissions
thanks a lot, lovetide!
and about the usb mount of /?
when i am in the pink screen and connect the usb shouldn't i see the 3 drives (fs, internal sd, sd)?
No, only image folder.
Sent from my ragelis
Done it. Replaced the file
For this to work you will need to be rooted with twrp installed.
This is for people who are on the stock rom or a rom without init.d support.
1. Download the wp_mod.ko file from @flar2's thread http://forum.xda-developers.com/showthread.php?t=2701816
and copy it over to your SD card (either internal or external)
2. Boot into twrp
3. Select the "Mount" option on the main menu and tick system
4. Go back to the main menu and then go into the "Advanced" option. There will be a "File Manager" option
5. Navigate to the folder you saved the .ko file in and copy it (just touch the file and it will bring up the menu)
6. now navigate to /system/lib/modules and copy the file there by hitting the "select" button on the bottom right.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
8. reboot the device
9. Once booted fully open up Terminal emulator and type:
su
insmod /system/lib/modules/wp_mod.ko
10. Once that's done open up a file manager app with root access and mount as r/w and navigate to /system/etc and look for the file install-recovery.sh
11. edit the file using a text editor, adding the line insmod /system/lib/modules/wp_mod.ko towards the bottom of the file
12. reboot and enjoy r/w on boot without running the command every time
13. profit
I don't have my hands on mine yet (ordered a Dev edition from Amazon), but I greatly appreciate your work here! R/W was a massive pain for me on my M7, and this seems much more simple and easy. Thanks again!
Hi graffixnyc,
Thanks for the explanation, but the link to the file is not working ....
link
flaxjef said:
Hi graffixnyc,
Thanks for the explanation, but the link to the file is not working ....
Click to expand...
Click to collapse
+1
CC
Should be fixed now.. I don't know why it cut off some of it
http://forum.xda-developers.com/showthread.php?t=2701816
Thanks for the turorial, but this isn't working for me
The file can't be executed (even after chmod) - and if i try to execute this file in an other directory, my terminal says that this file can't be found..
Any ideas?
So my device simply ignores Step 7 .... :crying:
graffixnyc said:
For this to work you will need to be rooted with twrp installed.
7. Navigate to /system/lib/modules and insure the file is there. Now touch it to bring up the menu. select "Chmod" option and enter in 644
Click to expand...
Click to collapse
I know I am being a grammar nazi, but I am fairly certain you mean "ensure". I tried to just leave it alone, but I can't not say something. It's a curse.
Fenny said:
I know I am being a grammar nazi, but I am fairly certain you mean "ensure". I tried to just leave it alone, but I can't not say something. It's a curse.
Click to expand...
Click to collapse
It is ironic that a "grammar nazi" would use a double negative while pointing out a grammatical error...
noimjosh said:
It is ironic that a "grammar nazi" would use a double negative while pointing out a grammatical error...
Click to expand...
Click to collapse
lol... yeah, would have been better to say: "but I'm compelled to say something"
Oh well, no biggie though.
Don't know how I missed this thread though, thanks graffixnyc.
noimjosh said:
It is ironic that a "grammar nazi" would use a double negative while pointing out a grammatical error...
Click to expand...
Click to collapse
Indeed, it is ironic.
thank you
412070391 said:
thank you
Click to expand...
Click to collapse
Does this work if the phone is still s-on? (unlocked/rooted but no s-off)
Sorry, but will this fix my little niggling issue with MX player? I keep my Stewart/Colbert files on the extSD card, but I can't delete them when done watching them using MX Player's delete command. I have to remember which files are watched and then use ES File Explorer to delete them. A silly second step in my opinion. Yes I am rooted, s-on, with TWRP.
I'm staying stock hoping a firewater solves my s-on issue, but yes I should probably do a custom ROM to solve this and a few other things.
Will this make SD card writeable to all apps?
Will this make external micro SD card writeable to all apps?
Sn8kbordin said:
Will this make external micro SD card writeable to all apps?
Click to expand...
Click to collapse
MAN, NO DOUBLE POSTS. but yea it should do it...if not there is another way
In Terminal Emulator it says "Failed Exec Format Error". Any ideas?
I followed the 1st post directions without errors for Sense 6.0, Andoid 4.4.3. When I tried to:
1. When I tried editing and saving system/customize/ACC/default.xml in ES File Explorer phone rebooted on save and default.xml went back to stock
2. When I copied default.xml to extSD card, edited it, and tried overwriting system/customize/ACC/default.xml with edited default.xml in TWRP recovery phone also rebooted
I want to do this mod http://forum.xda-developers.com/htc-one-m8/general/enable-built-music-channelroot-t2818128
What IS this post about?
Firmware restore of 4.4.4 using RSD Lite, but for unlocked boots, the recovery flashed is custom & the logo used is the normal M-multi color rather than the warning version. Comes in Philz & Twrp flavors. Upon rebooting, Philz or TWRP will root for you.
User data is retained, not erased.
Note: After this restore you may notice problems because you kept data-just wipe data from recovery & reboot. Keeping data like this is non standard.
The logo used is from here.
First 2 attachments are about 10 MBs. There are 3 modded files to extract: MOD...xml (RSD instructions), recovery & logo to paste into your unzipped/extracted FXZ/XML folder. You may want to rename the stock recovery & logo so they will not be overwritten. Here is the usual fxz Source, which you may have already.
Do not paste the source xml folder contents into mine.
The 2 last attachments are modded full FXZs, 900 MB.
Choose the mod xml from RSD Lite 615. Moto drivers are here. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. So use of the modded or source FXZ will leave user data alone.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Faster Mega server full versions can be downloaded for regular use on locked xt-1080s as each modded Full fxz can be easily put back to normal. Recovery.img.orig 10.5 MB & logo.bin.orig 2.6 MB just need renaming, as well as the modded ones renamed: recovery.img.mod Philz: 10.4 MB, TWRP: 8.6 MB & logo.bin.mod 2.6 MB. Then run the original xml (included)(not the one labeled MOD). Again there is no data wipe in this original firmware.
A better backup
Full 444 xml with Philz recovery is up.
It is easily converted back to the normal fxz for locked boot users.
But why? Mega is much faster than the sbf/xml storehouse site.
So if your un Rooted this is useful how?
PILLMUZIK3600 said:
So if your un Rooted this is useful how?
Click to expand...
Click to collapse
Just a faster download of the fxz, is all. Then you must convert the xml folder to normal.
Thanx
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK
dschewchenko said:
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK
Click to expand...
Click to collapse
How did this help keep WP off?
I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?
aviwdoowks said:
How did this help keep WP off?
Click to expand...
Click to collapse
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed
luisdev said:
I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?
Click to expand...
Click to collapse
No way but a boot unlock. 444 has no exploit for rooting.
This helps unlocked phones only.
dschewchenko said:
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed
Click to expand...
Click to collapse
Why don't you share all the details here.
Solution
aviwdoowks said:
Why don't you share all the details here.
Click to expand...
Click to collapse
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
Click to expand...
Click to collapse
Do you have a locked or unlocked bootloader?
aviwdoowks said:
Do you have a locked or unlocked bootloader?
Click to expand...
Click to collapse
I have locked verizon moto droid ultra
dschewchenko said:
I have locked verizon moto droid ultra
Click to expand...
Click to collapse
What build did it come with? Please post all info & steps!! Did you use any exploits?
aviwdoowks said:
What build did it come with? Please post all info & steps!! Did you use any exploits?
Click to expand...
Click to collapse
I have Verizon XT1080 with Locked BL, on 4.4.2 was root and WP off, after WiFi updating to 4.4.4 all was broken, and after that I wrote upper I'm now with root and system read/write permission, but safestrap see that WP ON and crashes after tapping somewhere. After updating SuperSU root will be lost.
For system R/W you may go to Terminal and run:
- su
- mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
and than with mount command check if /system have rw. After reboot you may to remount
P.S. Sorry for my english, I'm from Ukraine =)
Very bad that Moto with cutted language pack =(
dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
Click to expand...
Click to collapse
-Install RSD and drivers
- do solutions from head from head
???
- download file from 1 attach
Was that the small?
- replace files
This must have been recovery, logo & the mod.XML.
- flash it and see on phone error about size of recovery
Details?
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.
aviwdoowks said:
-Install RSD and drivers
- do solutions from head
???
in head of this thread
Here is an alternate method to flash 444 "pre-recovery'ed" and thereby pre-rooted. Comes in Philz & Twrp flavors.
3 modded files: ...xml (RSD instructions), recovery & logo to paste into your unzipped FXZ/XML folder. Source.
Flash from RSD Lite 615. Moto drivers. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. Added custom recovery & stock (boot) logo.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Paste the 3 files to your xml folder. You may want to rename the stock recovery & logo so they will not be overwritten.
Faster Mega server (but slow uploads, 1 a day. 2 Ultra & 2 X) full versions soon. 10 MB vs 900 MB.
Note for locked users: each modded Full fxz can be easily put back to normal. Recovery.img.orig & logo.bin.orig just need renaming. Then run the original xml (included). Again there is no data wipe in this original firmware.
A better backup
ATTACHED FILES
File Type: txt Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt - [Click for QR Code] (112 Bytes, 9 views)
File Type: txt Twrp-2.8.0.1_NO ERASE_user.data_stkBOOTlogo-1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.txt - [Click for QR Code] (111 Bytes, 13 views)
File Type: txt Full_Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo1FF-obake_verizon-user-4.4.4-SU4.21.xml.zip.txt - [Click for QR Code] (110 Bytes, 3 views)
Click to expand...
Click to collapse
- download file from 1 attach
Was that the small?
this -> "Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt"
- replace files
This must have been recovery, logo & the mod.XML.
files from downloaded archive
- flash it and see on phone error about size of recovery
Details?
-standart flashing with RSD-Lite. When recovery uploading , on phone screen was error about incorrect size of recovery, and then I reboot phone to recovery(stock with VOL-DOWN and POWER), then I do full wipe, thenreboot to clean system, in menu I see SuperSU, then download and run Terminal, tap in Terminal "su", all OK, try to remount system to RW, all OK, then download Root Explorer, root permission applied and go to system for manipulate with files =)
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.
Click to expand...
Click to collapse
=)
dschewchenko said:
=)
Click to expand...
Click to collapse
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.
aviwdoowks said:
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.
Click to expand...
Click to collapse
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz
dschewchenko said:
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz
Click to expand...
Click to collapse
Just to be clear, I intended the attachments to overwrite the source. You overwrote the attachment with the source!! (If I read you right)
The Q is did you achieve something good by your mistake?
I have here, two packages.
The twrp one is meant for those who have already flashed twrp, the other is for first time root via EDL.
Both flash System RW, updated TWRP and magisk.
TWRP package will not wipe Data, You will loose no data
NOTE - You may have to mount the system RW.
NOTE - The above will be fixed via a future custom rom.
Without further ado, here are the instructions.
Initial Root Instructions
Prep: You must have a Pin screen lock set on your device to prevent data loss.
On your phone go to
Settings>Security>Screen Lock>PIN
and set a pin.
USB Debugging and OEM Unlocking have to be enabled to make this work.
On Your phone go to
Setting>About phone
Then tap on build number 10 time to unlock Developer Settings
Now go to
Settings>Developer Options
Then toggle usb debugging and oem unlocking.
1. Download this package B20 Via QFIL
2. Unzip the file to your desktop.
3. Right click on RunasAdmin_TestSignON.bat and run as administrator.
4. Let your machine reboot.
5. Run Run This.bat
6. Install everything it tells you to install.
NOTE Select WWAN-DHCP when asked
7. RTFM and flash (All the files your need for qfil are in the B20 Folder!!!!)
8. Profit
Then
9.Press and hold Vol+ and Power
10.Once the ZTE screen shows, let go of power while continuing to hold vol+
This will get you into twrp
11.Plug you phone into your computer and from your adb directory, run these commands.
12.adb shell
13.setenforce 0
14.exit
Now on your phone, in twrp
15.Swipe to allow midification
16.Tap Backup
17.check data
18.tap select storage
19.Select microsdcard
20.tap ok
21.Swipe to backup
22.Tap home
23.Tap wipe
24.Tap Format Data
25.Enter yes and tap the blue checkmark
26.Tap home
27.Tap Power off
28.Turn your phone on.
For those who have TWRP already on their device, follow these instructions.
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 5/253/19
Updated boot.img z982_boot_magisk.img
Update Magisk root "Already obsolete"
Fixes ADB not authorized issues
Update twrp recovery.img z982_recovery_twrp.img
Fixes selinux enforcing related issues related to /data folder
Fixes backup related issues
Fixes zip install related issues
Do you think this will work with my hard bricked phone?
so if our system is still ro, all we have to do is mount rw every time? I was hoping that we would only need to mount it like one time, because im basically doing the same thing I was doing before.
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Chickenaa said:
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Click to expand...
Click to collapse
will do. are all the files already in place.
bootanimation worked, but sound still didnt
evtoofly said:
will do. are all the files already in place.
bootanimation worked, but sound still didnt
Click to expand...
Click to collapse
Upload the build.prop
Chickenaa said:
Do you think this will work with my hard bricked phone?
Click to expand...
Click to collapse
As long as you get the driver working, it should no problem.
xxMoon said:
As long as you get the driver working, it should no problem.
Click to expand...
Click to collapse
Im thinking about reinstalling windows. Do you think i should give it a try?
Chickenaa said:
Im thinking about reinstalling windows. Do you think i should give it a try?
Click to expand...
Click to collapse
I would.
Before you reinstall.. if ur able try on another PC.
xxMoon said:
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
Click to expand...
Click to collapse
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
JasonSec said:
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
Click to expand...
Click to collapse
thought I was the only one, I just stopped trying, if I need to go mount rw, i just use root explorer . Even that freezes sometimes though smh. Some people just got it better than we do
B25
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
AjtheLAF said:
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
Click to expand...
Click to collapse
No issues for me.
Emerl said:
No issues for me.
Click to expand...
Click to collapse
Did your system become rw?
evtoofly said:
Did your system become rw?
Click to expand...
Click to collapse
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Emerl said:
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Click to expand...
Click to collapse
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
evtoofly said:
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
Click to expand...
Click to collapse
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
I personally use root explor to chmod files, I dont think es can do it, however es has its own perks as well, so I just keep both just in case
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
Lol, actually you can put init.d scripts in /sbin/.magisk/img/.core/service.d/ and they will do it on boot.
Try my attachment.
I
OSS 9.0.15
Magisk 19.3
Magisk Manager 7.3.2
Can't write in root folder cause says that root folder has 0 byte space available
Example: if i try to Copy a file in root\system\media
Total Commander report error cause 0 byte available
Mixpolorer, solid Explorer etc Copy file buy with 0 dimension
What's wrong ?
Fil76 said:
What's wrong ?
Click to expand...
Click to collapse
OnePlus.
They filled the /system partition, if you want to copy/move something, you will have to delete something first.
Did u give root permission.?
I guess u haven't
All file Explorer asked and i give permission
How can i check ?
Btw see message before your
Edit: for root checker it's all ok
onliner said:
OnePlus.
They filled the /system partition, if you want to copy/move something, you will have to delete something first.
Click to expand...
Click to collapse
Bad news
I have 10 MB of free space, but the system claims there's none. My build.prop is currently a 0 byte file after I tried to edit it. I can manage the file in any way except increase it's size. I wonder if this would be the case under twrp as well. I'm afraid to reboot until I have access to my PC in case I need to re-flash the ROM if I can't restore my build.prop.
Did you fix it dude, I have the same problem. =/