Related
supercurio has reported:
SpeedMod based (Doc's ROM and others) and every other Universal Lagfix corrupt badly /system
It means that as long as they don't restore a /system with Odin, they're stuck on kernels using broken mount options.
If you want to verify, try to boot a stock Samsung kernel. Depends on how much it is corrupt it will boot, or not, or with unexpected errors
Want proof?
http://bit.ly/bq2oXg
Highlighted line is using wrong and corruption mount points
lack of check=no which causes corruption. Every Samsung mount uses check=no
Second Issue:
Even with NO RFS Config selected... RFS is still used in /system mounts... means phone are slowly Dying of corruption..
please fix linky - I want to know more about this:
That page doesn't exist!
Click to expand...
Click to collapse
thanks !
zacharias.maladroit said:
please fix linky - I want to know more about this:
thanks !
Click to expand...
Click to collapse
Fixed XD Sorry for that
Not 100% sure on this, since I have not used or looked at sztupy's lagfix very much, but that line you are pointing out is not a problem.
If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.
The following line would then mount it correctly.
Basically, this seems to be totally false. More evidence please.
EDIT: Okay, OP was updated with better information. Lack of check=no means that the FAT32 check *may* be running on the /system, which would cause corruption.
Probably a good idea to confirm if the filesystem check is actually happening though!
In case that supercurio is right (I hope he’s not for obvious reasons), I guess that it wont affect to users that are running harcore kernel without any lagfix applied, right?
RyanZA said:
If /system is EXT4, then calling mount -t rfs on it will simply return an error message, and not mount it. It will do exactly nothing.
The following line would then mount it correctly.
Click to expand...
Click to collapse
That is correct, however /system is not EXT4, but RFS.
good catch.
but im sure sztupy can fix this with a small patch, although i agree the priority should be flagged 'critical'...
as always, good work supercurio
NetCopAD said:
That is correct, however /system is not EXT4, but RFS.
Click to expand...
Click to collapse
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.
In case that supercurio is right (I hope he’s not for obvious reasons), I guess that it wont affect to users that are running harcore kernel without any lagfix applied, right?
Click to expand...
Click to collapse
It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!
If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
RyanZA said:
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.
It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!
If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
Click to expand...
Click to collapse
Maybe I am wrong but there is no settings in sztupy's kernel which convert /system
Lagfix only convert /data, /cache and /dbdata
Mopral said:
Maybe I am wrong but there is no settings in sztupy's kernel which convert /system
Lagfix only convert /data, /cache and /dbdata
Click to expand...
Click to collapse
Yeah i just looking further system is still mounted as
/sbin/busybox mount -t rfs /dev/block/stl9 /system - Possible corruption happens here without check=no
RyanZA said:
Thanks, I thought this was referring to a problem when /system is converted, rather than when it isn't. Which means that if you are running sztupy's kernel with one of the settings that convert /system then it should be fine.
It would actually affect you in this case, as the problem occurs when the lagfix is NOT applied, rather than when it is applied!
If it even is a problem, and the fat32 check runs rather than the system trying to do fsck.rfs and failing.
Click to expand...
Click to collapse
Yes this would affect the speedmod kernel as well, if it indeed is a problem. ULFK does not change /system in any lagfix scheme. So, its always mounted as rfs, apparently "wrongly".
I am testing an updated speedmod (shall we say, K9-pre) with the changed mount option. At the very least it should do no harm. And trying to get in touch with curio but over at IRC they say he's probably sleeping now after a coding binge!
Hmm and I found a minor 'bug' in the post-init.sh that was not properly setting /system to read-only after its done.... mainly because the logfile is being written to /system!
Method to test if this is a problem:
Replace your fsck_msdos (this is the only fat32 fsck in the filesystem) with a script file. Inside the script put the following:
Code:
echo "$?" > /somewhere
Then reboot your phone a lot of times. If the check is being called, then you will now get a log message instead of the check happening.
Will also affect checking of /sdcard though.
As far as I know though, fsck_msdos is only ever called by vold, and therefore check=no in /system may not have any effect, and this could be a false alarm. Anyway as hardcore says, can't hurt to fix it!
EDIT: Just wanted to add that running fsck_msdos even once on my /system (using the awesome pre-init scripts from z4mod!) made my phone immediately unbootable (damnit!). Not a big sample size, but I believe that if this was really a problem, we would be seeing many many reports of the sztupy kernel breaking devices! Since we don't have these reports, I'm gonna put this myth down as 'likely to be busted soon!'
RyanZA said:
Method to test if this is a problem:
Replace your fsck_msdos (this is the only fat32 fsck in the filesystem) with a script file. Inside the script put the following:
Code:
echo "$?" > /somewhere
Then reboot your phone a lot of times. If the check is being called, then you will now get a log message instead of the check happening.
Will also affect checking of /sdcard though.
As far as I know though, fsck_msdos is only ever called by vold, and therefore check=no in /system may not have any effect, and this could be a false alarm. Anyway as hardcore says, can't hurt to fix it!
Click to expand...
Click to collapse
Well the intention of this post is to show the issue for it to be fixed So let hope it does not do too much damage :S
deathst said:
Well the intention of this post is to show the issue for it to be fixed So let hope it does not do too much damage :S
Click to expand...
Click to collapse
Looks like this may have been a bit too sensationalist!
More checking, less guessing is always good! (And I could learn a lot from that motto myself!! )
RyanZA said:
Looks like this may have been a bit too sensationalist!
More checking, less guessing is always good! (And I could learn a lot from that motto myself!! )
Click to expand...
Click to collapse
Well we could check it by running it on RFS and reboot alot of time and then flashing a original Kernel
RyanZA said:
Looks like this may have been a bit too sensationalist!
More checking, less guessing is always good! (And I could learn a lot from that motto myself!! )
Click to expand...
Click to collapse
yeah when i saw that post my balls shrank.. thinking that by precious phone may be 'slowly dying of corruption'
not like there is a repair file system tool to use
Code:
/dev/block/stl9 /system rfs ro,noatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
K8, u had a short life... looks like its time for K9
Important thing to note is that this is the way stock kernels mount /system: read-only, and we see the option log_off too.
The thing I noticed this way is that if u do a mount -o remount,rw /system and modify stuff... it may corrupt /system. All modifications to /system should then ideally be done via CWM or update.zip only.
deathst said:
Well we could check it by running it on RFS and reboot alot of time and then flashing a original Kernel
Click to expand...
Click to collapse
Why would flashing an original kernel make a difference? Original kernel will mount /system in exactly the same way, so any corruption in /system would be seen on both the original kernel and on the sztupy kernel before the reflash.
Reflash or not has nothing to do with it.
Only method would be to reboot (or remount) enough times to hit the unclean filesystem check parameter (which rfs might not even have?), or wait long enough for the unclean check time to elapse. Not really sure how you would check what this parameter is - maybe tune2fs could be used? RFS is a bit of a black box!
RyanZA said:
Why would flashing an original kernel make a difference? Original kernel will mount /system in exactly the same way, so any corruption in /system would be seen on both the original kernel and on the sztupy kernel before the reflash.
Reflash or not has nothing to do with it.
Only method would be to reboot (or remount) enough times to hit the unclean filesystem check parameter (which rfs might not even have?), or wait long enough for the unclean check time to elapse. Not really sure how you would check what this parameter is - maybe tune2fs could be used? RFS is a bit of a black box!
Click to expand...
Click to collapse
It may mount correctly with Original Kernel..If it does quite a damage to the /system the phone might report errors even it is will not be able to boot.
deathst said:
It may mount correctly with Original Kernel..If it does quite a damage to the /system the phone might report errors even it is will not be able to boot.
Click to expand...
Click to collapse
No, that doesn't make sense. The difference between stock and sztupy is that sztupy's mount is telling the system to try and check the drive. If /system works fine in the sztupy kernel, it will still work fine in the stock kernel, because the only difference is that the stock kernel DOESN'T check. Well, testing so far seems to be showing that neither check, and the check option does nothing at all.
Hello to all in comunity.
Galaxy s has only 30MB of cache size. And this is bad because some apps on the market can't be installed, since market uses this cache partition for the downloads. Is there a way to increase this size or to symlink it on some bigger partition like /data or somewhere else?
Sent from my GT-I9000 using XDA App
Anybody? I heard that's a way to symlink cache anywhere else, but i can't do it, everytime i try a message saying "resource busy" or something like this appears on Terminal Emulator. I'm trying to symlink cache to /data.
Do you have ext4 lagfix enabled?
Sent from my GT-I9000 using XDA App
No. Do i need to enable it?
Sent from my GT-I9000 using XDA App
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Sent from my Galaxy S/CM7 using XDA App
avary said:
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Click to expand...
Click to collapse
And what version of speedmod are you using? I'm on K12-T 500Hz....if i enable ext4 lagfix on cache, will i get the 100MB too?
And also, were you using CM7 already?
Thanks!!
I tried to symlink the cache to a folder i created ala hardcore's suggestion (Thanks again hardcore!), but unfortunately I got the same sized partition as the original cache folder, which kinda makes sense. Hopefully Samsung or one of the guys on XDA (yeah, they'll probably get a fix out before Sammy does) will have a solution.
avary said:
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Sent from my Galaxy S/CM7 using XDA App
Click to expand...
Click to collapse
I call bull****.
So there isn't a way to do it right now? I guess we need supercurio's or hardcore's help. Please people, help to contact them. Thx!!
Sent from my GT-I9000 using XDA App
I agree
snapper.fishes said:
I call bull****.
Click to expand...
Click to collapse
So do I. I tried using the latest speedmod, and no change. Think the only solution would be to have the cache size changed in the internals. Definitely out of my league; I don't want to try changing a setting and lose the use of my phone. Hopefully someone gets a fix in; battle bears is calling...
Definitely we need to move this thread to android development and see if someone there with enough skills can help us. I think it's an urgent problem. What about battle bears? And what if gameloft start to sell their games on android market now?
Sent from my GT-I9000 using XDA App
Thanks!!!!
gangpe said:
I tried to symlink the cache to a folder i created ala hardcore's suggestion (Thanks again hardcore!), but unfortunately I got the same sized partition as the original cache folder, which kinda makes sense. Hopefully Samsung or one of the guys on XDA (yeah, they'll probably get a fix out before Sammy does) will have a solution.
Click to expand...
Click to collapse
lucbl1 said:
Anybody? I heard that's a way to symlink cache anywhere else, but i can't do it, everytime i try a message saying "resource busy" or something like this appears on Terminal Emulator. I'm trying to symlink cache to /data.
Click to expand...
Click to collapse
How do you guys exactly try to symlink it? I guess more people could help out if they knew exactly what you are doing and what the error messages exactly say.
I'm not really interested in getting a bigger cache partition since I don't use really big apps, but this would probably be thay way I'd do it:
(you could type these command either through adb shell or directly on the device using a terminal emulator -- WARNING: these commands are not tested and may horribly break something)
Code:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache
shantzu said:
How do you guys exactly try to symlink it? I guess more people could help out if they knew exactly what you are doing and what the error messages exactly say.
I'm not really interested in getting a bigger cache partition since I don't use really big apps, but this would probably be thay way I'd do it:
(you could type these command either through adb shell or directly on the device using a terminal emulator -- WARNING: these commands are not tested and may horribly break something)
Code:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache
Click to expand...
Click to collapse
I was just using the same code you posted. But i think that for symlinking, /system and /data must be in Ext2/3 or 4 format, am i right? I'll be testing it in the weekend!
I mentioned this issue to supercurio who is looking into it.
Sent from my GT-I9000 using XDA App
lucbl1 said:
I was just using the same code you posted. But i think that for symlinking, /system and /data must be in Ext2/3 or 4 format, am i right? I'll be testing it in the weekend!
Click to expand...
Click to collapse
well, tbqh I didn't work much with RFS, so I am not sure if it supports symlinks, I guess it can't hurt to try though...
If it doesn't work on RFS you'd have to try some ext FS (ext2, ext4, whatever you prefer).
rlorange said:
I mentioned this issue to supercurio who is looking into it.
Click to expand...
Click to collapse
So maybe supercurio can fix it. Let's hope! Any news please report here.
Sent from my GT-I9000 using XDA App
Problem fixed on last speedmod kernel!
Sent from my GT-I9000 using XDA App
can someone plz help me? i got the problem and its rly annoying..i have 2.3.3 xxjvo with cf_root how do i fix this ****?!
romdroid. said:
can someone plz help me? i got the problem and its rly annoying..i have 2.3.3 xxjvo with cf_root how do i fix this ****?!
Click to expand...
Click to collapse
If rou are rooted just folow this commands in terminal...
su
mkdir /sdcard/tempcache
mount -o bind /sdcard/tempcache /cache
This is temporary, after reboot cache will return normal and you can delete tempcache in sdcard...
Cheers
Thread closed.
Thread closed.
Yank555 said:
Hi,
REMEMBER
FIRST OF ALL, do a Nandroid backup, as well as a backup of your sd-card content !
You're doing this at your very own risk, I'm not to be held responsible if something goes wrong
Now that said, let's get going
In case somebody wants to check it out, here is the swap activation script I wrote (attached) as well as explanations on how to make it all work :
1) Partition your sd-card (Minitool Partition Wizard, 4ext, CWM...)
2) Boot your system with the partitionned sd-card
3) If necessary customize the 99swap script (attached to this post) and then put it onto your sd-card's root folder, you'll need it while executing the commands in step 4.
4) Open a terminal and type the following
NB: Change "mkswap /dev/block/mmcblk0p3" accordingly to point to the swap partition you've created in step 1.
5) Reboot your phone, start a terminal again and type free, you'll need to see something different than 0 in your swap line, look at the attached print-screen
Swappiness will be set to 50 by the script, which is a rather conservative swap use, made sense to me since SD-swap is slower than ram, better not to use it too agressively. Feel free to experiment with the swappiness variable in the script (values between 0 and 100, 0 meaning "try not to swap", 100 meaning "try to swap all the time")
If you want to try and have a question, just let me know !
JP.
PS: You can find the thread for hard swap for the htc Sensation / XE here.
Click to expand...
Click to collapse
Hi JP,
This is a gem of a post! Thanks alot for the script and the detailed breakdown. Before I get into it though, I must warn you that I am more of a beginner with no coding/scripting experience (I don't know how to use adb or anything)...
Here's what I'm trying to do: I'm trying to activate hard-swap on my hd2 (currently) running the ParanoidAndroid by Xylograph. I've created 3 partitions on my 16gb class 6 sd card: first, fat32 (32k cluster), next, 1GB ext2 (default), 500MB swap.
Procedure:
1. I extracted the script and copied it directly to system/etc/init.d folder of the Rom (I looked at the terminal commands you posted and the first few lines looked like copying the file from the sd root to the init.d folder (it was just a guess though), so I figured might as well put it into the rom before I flash it)
2. Flashed the rom
3. To activate it, I typed the following into the terminal:
su
mount -o remount,rw /system
mkswap /dev/block/mmcblk0p3
mount -o remount,ro /system
exit
after the mkswap command, I did get an activation notification that a certain amount was assigned to swap. But my celebrations were cut short after I rebooted and used the free command to check. The entire swap row still read 0.
I was wondering if you can point me in the right direction... thanks!
Also, is there a way to create a cwm flashable version?
bullcrapr said:
Hi JP,
This is a gem of a post! Thanks alot for the script and the detailed breakdown. Before I get into it though, I must warn you that I am more of a beginner with no coding/scripting experience (I don't know how to use adb or anything)...
Here's what I'm trying to do: I'm trying to activate hard-swap on my hd2 (currently) running the ParanoidAndroid by Xylograph. I've created 3 partitions on my 16gb class 6 sd card: first, fat32 (32k cluster), next, 1GB ext2 (default), 500MB swap.
Procedure:
1. I extracted the script and copied it directly to system/etc/init.d folder of the Rom (I looked at the terminal commands you posted and the first few lines looked like copying the file from the sd root to the init.d folder (it was just a guess though), so I figured might as well put it into the rom before I flash it)
2. Flashed the rom
3. To activate it, I typed the following into the terminal:
su
mount -o remount,rw /system
mkswap /dev/block/mmcblk0p3
mount -o remount,ro /system
exit
after the mkswap command, I did get an activation notification that a certain amount was assigned to swap. But my celebrations were cut short after I rebooted and used the free command to check. The entire swap row still read 0.
I was wondering if you can point me in the right direction... thanks!
Also, is there a way to create a cwm flashable version?
Click to expand...
Click to collapse
Thanx
In fact you understood correctly that is was about copying the file to init.d.
By the way, these commands do the following :
mount -o remount,rw /system - Mount system partition in read-write
mount -o remount,ro /system - Mount system partition in read-only
So to format the swap partition "mkswap /dev/block/mmcblk0p3" there was no need for it, but it didn't harm in any way, so you're fine there
I guess what is missing is the "chmod 755 /system/etc/init.d/99swap" command which will set the correct file access to the script so it can get executed at boot.
You might do the following in a terminal :
su
mount -o remount,rw /system
chmod 755 /system/etc/init.d/99swap
mount -o remount,ro /system
exit
It should be fine then.
Alternatively you could set the rights with your file explorer (in root explorer mode), they must be "rwxr-xr-x" (which is Read-Write-Execute, Read-Execute, Read-Execute), most file-manager will allow you to do that as well.
I've been working on the script variant for htc Sensation, it is more advanced, dynamic so it can find the swap partition by itself.
I'll make a CWM flashable as soon as I get to it that will handle everything except partitioning the SD card, obviously, for both devices.
As soon as I'm done I'll post the HD2 version here as well (very little change, between both devices, just the access path to the sd-card partitons to change (=1 line in the script).
JP.
Edit ------------------------------------------------
I just reread your post, if in fact you put it into the ROM zipfile, then file access should be correct !?
Could you post the following file (if it exists) :
/data/swap.0.log ?
JP.
Yank555 said:
Thanx
In fact you understood correctly that is was about copying the file to init.d.
By the way, these commands do the following :
mount -o remount,rw /system - Mount system partition in read-write
mount -o remount,ro /system - Mount system partition in read-only
So to format the swap partition "mkswap /dev/block/mmcblk0p3" there was no need for it, but it didn't harm in any way, so you're fine there
I guess what is missing is the "chmod 755 /system/etc/init.d/99swap" command which will set the correct file access to the script so it can get executed at boot.
You might do the following in a terminal :
su
mount -o remount,rw /system
chmod 755 /system/etc/init.d/99swap
mount -o remount,ro /system
exit
It should be fine then.
Alternatively you could set the rights with your file explorer (in root explorer mode), they must be "rwxr-xr-x" (which is Read-Write-Execute, Read-Execute, Read-Execute), most file-manager will allow you to do that as well.
I've been working on the script variant for htc Sensation, it is more advanced, dynamic so it can find the swap partition by itself.
I'll make a CWM flashable as soon as I get to it that will handle everything except partitioning the SD card, obviously, for both devices.
As soon as I'm done I'll post the HD2 version here as well (very little change, between both devices, just the access path to the sd-card partitons to change (=1 line in the script).
JP.
Edit ------------------------------------------------
I just reread your post, if in fact you put it into the ROM zipfile, then file access should be correct !?
Could you post the following file (if it exists) :
/data/swap.0.log ?
JP.
Click to expand...
Click to collapse
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
bullcrapr said:
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
Click to expand...
Click to collapse
Hi,
You're welcome
The file '/data/swap.0.log' is a text-file containing info on the execution of the script...
If it's not there, then the script didn't run at all...
I should have a little time later today, will try to make the CWM flashable solution for you, should be a no fuss solution, as long as the sd-card has a swap partition
How did you partition the card ? CWM ?
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
I created a 256Gb partition...
Click to expand...
Click to collapse
man thats a helluva sd card ya have there! hehe.
samsamuel said:
man thats a helluva sd card ya have there! hehe.
Click to expand...
Click to collapse
Haha I noticed that too :') I want one of those now
Nigeldg said:
Haha I noticed that too :') I want one of those now
Click to expand...
Click to collapse
Thanx for pointing that out Mb of course, but in a few years that might be possible
My first hdd had 60Mb, and that's not soooo long ago
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
heh, my first was a 20mb HDD mounted on a pcb card and plugged into an ISA slot, took up the full length of the PC, weighed LOADS, could have beaten burglars to death with it.
bullcrapr said:
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
Click to expand...
Click to collapse
+1 with this (also on Paranoid Rom 1.1a) but I think that it's something with the ROM coz on earlier build v1 this method worked verry good I hope that Yank will find a solution coz it reallly helps wit our 576 ram
samsamuel said:
heh, my first was a 20mb HDD mounted on a pcb card and plugged into an ISA slot, took up the full length of the PC, weighed LOADS, could have beaten burglars to death with it.
Click to expand...
Click to collapse
Mine was huge at the time, was on of the first to have such a big one, even partitioned it into 3 since it was just too big And it was an external device, the size of a pizza-box (it was en Atari Megafile 60, I still have it !!).
triggaz said:
+1 with this (also on Paranoid Rom 1.1a) but I think that it's something with the ROM coz on earlier build v1 this method worked verry good I hope that Yank will find a solution coz it reallly helps wit our 576 ram
Click to expand...
Click to collapse
I'm working on the CWM flashable right now, should be done within 1-2 hours at most
Yank555 said:
Hi,
You're welcome
The file '/data/swap.0.log' is a text-file containing info on the execution of the script...
If it's not there, then the script didn't run at all...
I should have a little time later today, will try to make the CWM flashable solution for you, should be a no fuss solution, as long as the sd-card has a swap partition
How did you partition the card ? CWM ?
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
Click to expand...
Click to collapse
Hi JP, once you told me it was the address to the file, i just navigated there using my explorer and lo and behold!, there it was (attached). If you must know, in my earlier post, the idiot in me just typed it in the terminal and the terminal replied not found.
I made my partition using freeware called Minitool partition wizard. Is 500mb too big for swap in your opinion? I was thinking of compensating for zram, and hence the size... thanks for your speedy responses...
edit...
and hey! whadya know? in the meantime, this place is coming alive!!
bullcrapr said:
Hi JP, once you told me it was the address to the file, i just navigated there using my explorer and lo and behold!, there it was (attached). If you must know, in my earlier post, the idiot in me just typed it in the terminal and the terminal replied not found.
I made my partition using freeware called Minitool partition wizard. Is 500mb too big for swap in your opinion? I was thinking of compensating for zram, and hence the size... thanks for your speedy responses...
edit...
and hey! whadya know? in the meantime, this place is coming alive!!
Click to expand...
Click to collapse
Hmm ... strange, the content of the file looks like a logcat ?! Not what I was expecting to see
Give me a little hour, and I think I should be done with the flashable hard-swap and we'll go from there
Minitool is excellent, but did you pay attention to only create "primary" partition ? If it is a logical partition it won't work...
Can you insert your SD card into your card reader, start Minitool an post a print screen of it ?
JP.
EDIT :
About size ... I believe 256Mb is enough, even read somewhere t shouldn't be more than 256, but I think there was no specific reason given.
Yank555 said:
Hmm ... strange, the content of the file looks like a logcat ?! Not what I was expecting to see
Give me a little hour, and I think I should be done with the flashable hard-swap and we'll go from there
Minitool is excellent, but did you pay attention to only create "primary" partition ? If it is a logical partition it won't work...
Can you insert your SD card into your card reader, start Minitool an post a print screen of it ?
JP.
EDIT :
About size ... I believe 256Mb is enough, even read somewhere t shouldn't be more than 256, but I think there was no specific reason given.
Click to expand...
Click to collapse
Here we go...
Minitool image attached... I typically pay attention to the partition type and made sure both of them were primary
About the logcat, I suspect you're right... I was trying to do one from my pc for the first time using adb and tried the only few commands I know (mkswap...), I think that's what you saw then...
Incidentally, do you feel if I reduce the swap size, the script has a better chance at surviving the boot?
bullcrapr said:
Here we go...
Minitool image attached... I typically pay attention to the partition type and made sure both of them were primary
About the logcat, I suspect you're right... I was trying to do one from my pc for the first time using adb and tried the only few commands I know (mkswap...), I think that's what you saw then...
Incidentally, do you feel if I reduce the swap size, the script has a better chance at surviving the boot?
Click to expand...
Click to collapse
Don't bother, I will test 500Mb and let you know if that is the issue
JP.
I have 512mb partition and it worked without problems as I mentioned earlier so I think that opposite to the "size does matter" in this case it doesn't plus I used it with zram from marc1706.
triggaz said:
I have 512mb partition and it worked without problems as I mentioned earlier so I think that opposite to the "size does matter" in this case it doesn't plus I used it with zram from marc1706.
Click to expand...
Click to collapse
Hi triggaz, are you using the built in zram on Para1.1a? Or have you applied a script from elsewhere? I enabled the built-in zram, but get a "not found" reply when i try zram_stats in the terminal. Can you tell me how you got zram working? thanks...
bullcrapr said:
Hi triggaz, are you using the built in zram on Para1.1a? Or have you applied a script from elsewhere? I enabled the built-in zram, but get a "not found" reply when i try zram_stats in the terminal. Can you tell me how you got zram working? thanks...
Click to expand...
Click to collapse
https://www.dropbox.com/s/xr3z102gxiw2f62/marc1706_zram_100MB.zip
all credits to Dorimanx for ZRAM mod and mark1706 for modifications
I flashed this and then used the compcashe options in Paranoid (set to 26%)
No mount scrip
System cm10 build 6
Please help form this error
Swap 256
Sdext 1024 ext4
You have to clear up some space in the system. Oh and next time search first this has been asked and answered numerous times in both related threads. The whole solution is described there.
Swyped from my P509 on Tmobile.
With Swype and Flash, why would anyone choose the iPhone?
not working
mrlamo said:
You have to clear up some space in the system. Oh and next time search first this has been asked and answered numerous times in both related threads. The whole solution is described there.
Swyped from my P509 on Tmobile.
With Swype and Flash, why would anyone choose the iPhone?
Click to expand...
Click to collapse
[mode google translator on]
thanks for replying
it´s a clean installation, full wipe and wipe fo all partition, one by one... and try repair partition, and try creating partition and convert ext2 to ext3 and ext3 to ext4
I will find the solutions already published, but with the installation of other roms no problems, even with CM10 build 5
I use cwm 5.0.27 n it works.256 ext4 and 64 swap.
cwm
bao_loc106 said:
I use cwm 5.0.27 n it works.256 ext4 and 64 swap.
Click to expand...
Click to collapse
I already downloaded it.
how to install this application?
already installed, but the error continues
not working
sermaudu said:
I already downloaded it.
how to install this application?
already installed, but the error continues
Click to expand...
Click to collapse
Clockworkmod Recovery v5.0.2.7
E:Bad boot message
"recovery "
sermaudu said:
Clockworkmod Recovery v5.0.2.7
E:Bad boot message
"recovery "
Click to expand...
Click to collapse
What?
Delete one unused app from the /system partition. You should be able to do so within Link2SD. Just filter the system apps and remove one (make sure that something doesn't rely on it!) If you don't use app E-Mail (not Gmail) you can remove it, only the E-mail and not the provider. That should work, I have done it this way too.
--
P>
Sent from my LG-P500 using xda app-developers app
not working
paul.n said:
What?
Delete one unused app from the /system partition. You should be able to do so within Link2SD. Just filter the system apps and remove one (make sure that something doesn't rely on it!) If you don't use app E-Mail (not Gmail) you can remove it, only the E-mail and not the provider. That should work, I have done it this way too.
--
P>
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
hi,
sorry by english but...
I returned to partition, reinstall the OS and link2sd works, still shows the same error does not mount the script, when I go into recovery mode get the error mentioned above ....
Delete partitions, resizing, formatting and nothing
sermaudu said:
hi,
sorry by english but...
I returned to partition, reinstall the OS and link2sd works, still shows the same error does not mount the script, when I go into recovery mode get the error mentioned above ....
Delete partitions, resizing, formatting and nothing
Click to expand...
Click to collapse
Hmm, Link2SD works but it won't work?
You need to delete some files in /system/ in order to create the mount script. Our system parition is too tall. So delete some files you don't need from system.
Example:
If you don't like E-Mail, delete Email.apk from /system/app/
And so on!
Recovery: That's normal! It isn't a problem, it's on every LG-P500!
Sent from my LG-P500 running Protos 0.0.1
not working
CodingDroid said:
Hmm, Link2SD works but it won't work?
You need to delete some files in /system/ in order to create the mount script. Our system parition is too tall. So delete some files you don't need from system.
Example:
If you don't like E-Mail, delete Email.apk from /system/app/
And so on!
Recovery: That's normal! It isn't a problem, it's on every LG-P500!
Sent from my LG-P500 running Protos 0.0.1
Click to expand...
Click to collapse
thanks
CM9 installed without problems(link2sd working smoothly), reinstall CM10 when more stable
sermaudu said:
Clockworkmod Recovery v5.0.2.7
E:Bad boot message
"recovery "
Click to expand...
Click to collapse
This not an error, a working recovery SHOULD show this.
Sorry for my bad English.
Sent from my LG-P500
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