stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
I had same problem tried almost everything and in the last had to flash stock GB to start over again.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Flash back to GB and root and then come to CM9 or CM10.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Had you tried the rooting method of dr ketan. http://forum.xda-developers.com/showthread.php?t=1329360
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Maybe the problem lies with busybox. Try getting busybox binary updated. I've read some people can do it by installing busybox from Google Play. For my case usually I inject busybox directly via CWM, but it is potentially dangerous so I won't share it here.
When I had this prob, I tried everything bo no luck, so flashed gb again.
Sent from my GT-N7000
lee yun khong said:
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I am having exactly this problem.
I have tried everything over and over and still partial root.
I would REALLY appreciate your help with getting full root on my note.
u need to give more details. what rom are u on?
I'm currently on 4.2.2 on a locked bootloader & I've managed to create an ftf (of both 4.2.2 & 4.3) using the guides. I don't want to unlock the boot loader as I prefer to stick with the stock rom & only root.
I'm sorry if this is stupid / wrong way to go about thing but Is this possible ?
1) I update all the partitions except /system using flashtool.
2) since I have root, Mount /system on my phone as rw.
3) extract /system from the 4.3 ftf and push the entire content of system manually (keeping root in the process)
4) Reboot ?
Is this possible ?
I'm sure this procedure needs to be fine tuned as I'm sure the permissions of the files pushed might be wrong.
Any help / tips ?
http://forum.xda-developers.com/showthread.php?t=2590174
,
Read @sijav 's Instructions and you will create your own Pre-Root Rom
I am using slim 2.2 which is 5.1.1 .I heard that there is a problem about system r w.Cant I flash custom rom or mods via recovery ? Any effect for flashing these ?
Up
Maybe something from here helps: http://forum.xda-developers.com/z3-compact/help/problem-flashing-rom-t3167966
Usually the recovery should have R/W access on /system unless a kernel protection prevents from mounting it R/W.
Hi,
When i install custom font in my rooted HTC one M7, font works fine. but new font does not exists after reboot. can any one help me to fix the issue ?. Please refer following procedure I followed.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /system/fonts
dd if=/sdcard/NotoSansSinhala-Bold.ttf of=/system/fonts/NotoSansMyanmar-Bold.ttf
dd if=/sdcard/NotoSansSinhala-Regular.ttf of=/system/fonts/NotoSansMyanmar-Regular.ttf
reboot.
regards
Duleep
Duleept said:
Hi,
When i install custom font in my rooted HTC one M7, font works fine. but new font does not exists after reboot. can any one help me to fix the issue ?. Please refer following procedure I followed.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /system/fonts
dd if=/sdcard/NotoSansSinhala-Bold.ttf of=/system/fonts/NotoSansMyanmar-Bold.ttf
dd if=/sdcard/NotoSansSinhala-Regular.ttf of=/system/fonts/NotoSansMyanmar-Regular.ttf
reboot.
regards
Duleep
Click to expand...
Click to collapse
/system is write protected by the stock kernel. Everything added or removed in /system from a booted rom running the stock kernel will be reverted back to stock after a reboot. You can write to /system when booted in a custom recovery since the stock kernel isn't booted at this stage or you can flash a custom kernel to remove the write protection when booted in the rom.
alray said:
/system is write protected by the stock kernel. Everything added or removed in /system from a booted rom running the stock kernel will be reverted back to stock after a reboot. You can write to /system when booted in a custom recovery since the stock kernel isn't booted at this stage or you can flash a custom kernel to remove the write protection when booted in the rom.
Click to expand...
Click to collapse
Hi,
what do you mean is, if i want to add new font , it is required to flash custom kernel (just rooting not enough) or need to do same operation (font installation) after each reboot.
regards,
Duleep
Duleept said:
Hi,
what do you mean is, if i want to add new font , it is required to flash custom kernel (just rooting not enough) or need to do same operation (font
Click to expand...
Click to collapse
Exactly, root doesn't remove the /system write protection, only a custom kernel will. You also have the option of using a custom recovery to copy your fonts on the /system partition since the stock kernel isn't booted in recovery mode (/system isn't write protected when in recovery)
alray said:
Exactly, root doesn't remove the /system write protection, only a custom kernel will. You also have the option of using a custom recovery to copy your fonts on the /system partition since the stock kernel isn't booted in recovery mode (/system isn't write protected when in recovery)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=40174803
Maybe this could help with stock kernel?
Hi everyone
I was struggling to get back to stock because my phone is S-ON so i used guru reset and updated this rom to the final M7 OTA. To flash this rom you have to extract TWRP folder from zip file and put it in your internal memory, while in TWRP go to advanced wipe and wipe your data, cache and system. Then go and restore the backup system and boot partitions. This is not a flashable ZIP!
Info:
Version: 7.19.401.51 - Latest
Kernel: Stock
Security: For both S-ON and S-OFF
To do after flash:
Update all HTC and Google apps
Bugs:
This is pure stock HTC rom, no changes made so no bugs.
Root and Tips:
After restoring backup, you can download https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip and flash it to ROOT it.
To prevent random reboots associated with SeLinux when rooted you need to change it to permisive, download this app:
http://forum.xda-developers.com/devdb/project/dl/?id=12506
Grant root access and set to permisive and reboot.
DOWNLOAD:
https://mega.nz/#!YxBxmbZS!gPMccMYNjGnuBv8ENhLkNiTZUIPDDXznjABrsAYPPeM
magix01 said:
Hi everyone
I was struggling to get back to stock because my phone is S-ON so i used guru reset and updated this rom to the final M7 OTA. To flash this rom you have to extract TWRP folder from zip file and put it in your internal memory, while in TWRP go to advanced wipe and wipe your data, cache and system. Then go and restore the backup system and boot partitions. This is not a flashable ZIP!
Info:
Version: 7.19.401.51 - Latest
Kernel: Stock
Security: For both S-ON and S-OFF
To do after flash:
Update all HTC and Google apps
Bugs:
This is pure stock HTC rom, no changes made so no bugs.
Root and Tips:
After restoring backup, you can download https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip and flash it to ROOT it.
To prevent random reboots associated with SeLinux when rooted you need to change it to permisive, download this app:
http://forum.xda-developers.com/devdb/project/dl/?id=12506
Grant root access and set to permisive and reboot.
DOWNLOAD:
https://mega.nz/#!YxBxmbZS!gPMccMYNjGnuBv8ENhLkNiTZUIPDDXznjABrsAYPPeM
Click to expand...
Click to collapse
You should also change the /TWRP/BACKUPS/SH********** to your serial number otherwise TWRP will not recognize it
ps. if it fails first time, like with mine, copy the system.ext4.win000 separately to the TWRP folder as it corrupted when i batch transferred it due to it's large file size.
and thanks for this, very useful to those who cant gain S-OFF