Related
The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium
I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.
the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.
Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.
hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.
Hi all,
I have kind of a strange problem with my girlfriends Galaxy Mini S5570.
It was bought with Android 2.2.1 installed, later on I flashed a 2.3.4 Stock ROM with Odin.
What I try to achieve now is using a CustomROM and so far I've tried to flash CM7.2 and emanoN 6, both without luck. Here comes what I did and what happens for both ROMs:
using Odin 4.42 and without SIM or SD installed, I flashed a Stock 2.3.6 (XWKTN) (PASS)
also with Odin I flashed CWM 4 (PASS)
in order to flash the CustomROM of my choice I wiped everything on the Galaxy (data/cache/DalvikCache)
SD card has a 256MB ext4 partition that is mounted later as /sd-ext
using zip installation I flashed CM7.2 stable or later emanoN 6, flashing went fine
at time of reboot it always gets stuck
Everytime I try to boot one of the CustomROMs it shows the initial Model information, then the boot animation that ends with the shiny SAMSUNG text, then screens turns black but backlight still on and every couple of minutes the phone vibrates very short.
The phone can be accessed by adb and responds fine there but screen is always black with dimmed backlight. All relevant volumes are mounted. data partition has some 10,000kB on it which varies up and down by some kB.
Code:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 143016 32 142984 0% /dev
tmpfs 143016 0 143016 0% /mnt/asec
tmpfs 143016 0 143016 0% /mnt/obb
/dev/stl14 25436 4200 21236 17% /cache
/dev/stl13 182672 10668 172004 6% /data
/dev/stl12 211400 166728 44672 79% /system
/dev/block/mmcblk0p2 245692 4236 241456 2% /sd-ext
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/sdcard
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/secure/asec
Code:
# ls /system
ls /system
T9DB bin etc lib misc xbin
TEAM build.prop fonts lost+found usr
app cameradata framework media wifi
# ls /data
ls /data
aeqcoe.txt dalvik-cache lost+found system
anr data misc system_ordered
app data_ordered property tombstones
app-private dontpanic radio zipalign.db
backup gps sd_ordered zipalign.log
cache local secure
cache_ordered log soundbooster.txt
# ls /sd-ext
ls /sd-ext
lost+found
# ls /mnt/sdcard
ls /mnt/sdcard
Android LOST.DIR
DCIM emanoNROM-v6-signed.zip
When trying emanoN 6 after CM7.2 failed, of course I went through the full procedure again, starting with Stock ROM via Odin. Also I tried using CWM 5 which I zip-installed from within CWM 4. Both ROMs hav the exact same behavior and I have no idea what causes it.
I can always access CWM or Download mode, nothing looks bricked to me. When I flash a Stock ROM again, no matter which, it just boots and runs fine.
Now it's my hope that anybody has seen this before and can point me to where the problem is.
Thanks and very best regards,
Peter
Did u root your your device
Sent from my GT-S5570 using Tapatalk 2
Did u do a full wipe ?
Sent from my GT-S5570 using Tapatalk 2
Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter
PeBo75 said:
Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter
Click to expand...
Click to collapse
For me i rooted my device first then i installed CMW i don't have any problem when flash roms
Sent from my GT-S5570 using Tapatalk 2
I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?
roofrider said:
I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?
Click to expand...
Click to collapse
Hi roofrider,
I used XWKTN and also XWKTH, both are 2.3.6. I did because that is told to be the base ROM for the emanoN. In his TUT parasmi says any 2.3.x would do as base but I tried XWKTH many times as well which is the one he mentions in his changelog.
When booting after flash I tried both, with and without SIM inserted. Makes no difference.
Is there anything I can check via adb to see where the phone gets stuck?
Where can I find the OS log files? Would like to have a look at them.
This it what it shows in dmesg every now and then:
Code:
<3>[ 1547.963619] kgsl kgsl: |kgsl_yamato_waittimestamp| Device hang detected wh
ile waiting for timestamp: 6, last submitted(rb->timestamp): 7, wptr: 87
ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c
wipe is also needed after flash, so wipe two times before installing and after ibstalling
dheeraj (dhlalit11) said:
wipe is also needed after flash, so wipe two times before installing and after ibstalling
Click to expand...
Click to collapse
not mandatory (i mostly don't do), but if things don't work, sure why not.
roofrider said:
ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c
Click to expand...
Click to collapse
Thanks, I did that now during a full boot until the first time it vibrated after a couple of minutes.
Condition: no SIM, SD with Ext4fs and VFAT, data/cache/dalvik cache wiped -> first boot of emanoN v6
As soon as the phone booted up I fired adb logcat, even before adb was ready. First response was "- waiting for device -", then it captured as per attachment.
Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
but then this is just a warning..
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Also it vibrating once just after the bootanimation(or end stage of bootanimation) is normal.
roofrider said:
Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Click to expand...
Click to collapse
Pulling battery is the only way to get out of it. At next reboot the same happens again.
This log was from emanoN v6. It checks if there is a custom bootanimation on SD card, if not it shows the Samsung default. You can see this in early stages of booting in the log.
Anyway, I have not confirmed the details via log file but the behavior was exactly the same when CM7.2 was flashed.
The vibration is not at this early stage but after having it some minutes on the table... untouched. In the log a whole lot of things happens again then. Could this be caused by a partly restart of something? Also it vibrates not once but endless times if I just leave it in this state. (Sorry, I still have the 5 minutes time barrier for editing/posting)
Now what could cause this message which appears a thousand times?
@dheeraj: I have wiped so many times: before, after and also before + after flashing. I'm sure it's nothing that can be solved with another wipe.
I'm exactly not sure..but googling this error helps a little...try searching maybe u'll find something.
--sry.
try running logcat longer and check..that should tell a little more.
possible reasons:
-try booting without SD card, it could be cos of a2sd (just a blind guess).
-maybe a certain app that is included is the culprit (again just a guess).
--OT--
U've been a member since 2010 and this is the 1st time ur posting!
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?
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
swaderade said:
How are you able to edit the hosts file in systemless route? I used SuperSU 2.66 flashed on MMB29S build. All I want to do is set up some redirects and possibly adaway.
Click to expand...
Click to collapse
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
TonikJDK said:
You have to make some space. Is not systemless root that is the problem. Changes in marshmallow made the system partition full. Reboot into twrp, mount system in rw and delete some unneeded apps in system/apps
Korean and Hindu keyboards for example. But dont delete the latin one. Or some google apps that can be added back in from the store.
Click to expand...
Click to collapse
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
swaderade said:
I deleted sheets using Titanium, so it must be the mounting. Time to go search on how to do that. Thanks!
Trying `adb shell mount -o rw,remount /system` and get `mount: can't find /system in /proc/mounts`.
Click to expand...
Click to collapse
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
TonikJDK said:
They look like they are deleting in TI, but they don't delete. I just flashed the January update today and that is what happened to me. I have seen that twice now. Cant help you with the adb command, I just used twrp to mount and delete.
Click to expand...
Click to collapse
Since checking mount system does nothing, I went into Advanced > Terminal and did an `rm -rf GoogleHindiIME` and still can't edit the hosts file.
swaderade said:
Totally didn't even see that option. You just reboot after checking it? Every time I go back to it, it's unchecked.
Click to expand...
Click to collapse
I mount in twrp. Delete hindu and korean with the file manager in twrp. Reboot, install adaway and it works. I have never manually edited it.
No, the system mount in twrp does not stick on reboot. Mounting system with systemless root is tricky as I understand it. So I just avoid it.
You can't mount system as rw in a booted Android system unless you have a permissive kernel, and you should not have a permissive kernel.
Had the same problem and didn't want to remove things from /system. You can follow the steps here: http://forum.xda-developers.com/showthread.php?t=3266107
Systemless root on 6.0.1 - How to edit build.prop
Sent from my Nexus 6 using Tapatalk
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
same here. anyone please help us
quiks11ver said:
i have did adb remount and also mount -o rw,remount,rw /system on terminal in my phone....did mounted the system partion in twrp ( but it jus goes off again after i turn on my phone ) someone please help me
Click to expand...
Click to collapse
delete unneeded system apps from /system/app/ then reboot and try again
simms22 said:
delete unneeded system apps from /system/app/ then reboot and try again
Click to expand...
Click to collapse
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
quiks11ver said:
Hi when i try to delete, it shows a read only message, and i went root explorer to turn RW it automatically turn it off
Click to expand...
Click to collapse
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
simms22 said:
ok, i understand whats happening now.. youre going to have to reroot. just boot into twrp and flash supersu 2.6x again.
Click to expand...
Click to collapse
Hi, jus a simple question..will my phone be wiped?
quiks11ver said:
Hi, jus a simple question..will my phone be wiped?
Click to expand...
Click to collapse
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
simms22 said:
if you just flash the latest SuperSU, then no. I flashed SuperSU 2.65 today, that works if you don't see a newer version.
Click to expand...
Click to collapse
Ty simms22, i just realise my phone has no supersu, but quite odd, kernel auditor works haha...using elite kernel, i may flash later and try
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
quiks11ver said:
okay, so i flashed the supersu 2.46 into my phone and it still doesnt show the supersu in apps drawer, but in setting/apps there is supersu and i still cannot manage to change write to system, in root explorer of es file manager after changing to RW, it automatic reset to Read only again
Click to expand...
Click to collapse
2.46 is very old now, you want 2.65 or above. google SuperSU 2.65, and you'll get it.
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
quiks11ver said:
Okay bro, i already flash a supersu 2.66 but in my apps drawer i find no supersu apps and i still cant write to system
Click to expand...
Click to collapse
wtf? lol! you can try to start over and reroot. thats what i would recommend, and its probably the right thing to do as well.
How to reroot? I oledi reflash but still cant
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
quiks11ver said:
simms22, is it that i have a kernel or rom that resists me from writing to system, i can do it last time but i keep reflashing kernel making my system crash, then i restore from last backup afterward i cant write to system anymore
Click to expand...
Click to collapse
what kernel are you trying? try elementalx.
---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------
oh, BTW, reroot = flash factory image via fastboot, flash twrp via fastbpot as well. then flash SuperSU 2.65 and boot up.
i'm using elite kernel, what is factory image?? i'm kind of a newbie just unlocking and rooting watching youtube videos. please help me!!
where can i find factory image??
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
quiks11ver said:
okay, i will try elementalX kernel, but 1 question...do i have to do anything before i flash another kernel? cause i used to flash many kernel after and after each1, then my phone keep restarting...so i restored the 1 i backed up
Click to expand...
Click to collapse
factory images https://developers.google.com/android/nexus/images?csw=1#yakju
you have a nexus 6, so you need a factory image for shamu
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
x-530 said:
hey i have an problem too everytime i try to push files in my system folder (like bootanimations) the es explorer sais i havent enough space every other explorer too, or when i try to change my density from 560 to 493 it sais the same, not enough space; i dont understand that... the phone is unlocked its rooted, i wiped everything a few times but nothing helps... :crying:
Click to expand...
Click to collapse
delete whatever system apps you don't need from /system/app/ then reboot. it will clear up enough space. google did that on purpose, made it read that its full, this will clear up the space.